draft-ietf-ips-fcmgmt-mib-06.txt   rfc4044.txt 
Internet Draft Keith McCloghrie Network Working Group K. McCloghrie
Cisco Systems, Inc Request for Comments: 4044 Cisco Systems, Inc
17 December 2004 Obsoletes: 2837 May 2005
Category: Standards Track
Fibre Channel Management MIB Fibre Channel Management MIB
draft-ietf-ips-fcmgmt-mib-06.txt
Status of this Memo
By submitting this Internet-Draft, I certify that any applicable patent
or other IPR claims of which I am aware have been disclosed, and any of
which I become aware will be disclosed, in accordance with RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Status of This Memo
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference material
or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at This document specifies an Internet standards track protocol for the
http://www.ietf.org/shadow.html. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community. In for use with network management protocols in the Internet community.
particular, it describes managed objects for information related to In particular, it describes managed objects for information related
Fibre Channel. to the Fibre Channel.
Table of Contents Table of Contents
1 Introduction .................................................... 3 1. Introduction ................................................. 2
2 The Internet-Standard Management Framework ...................... 3 2. The Internet-Standard Management Framework ................... 2
3 Short Overview of Fibre Channel ................................. 3 3. Short Overview of the Fibre Channel .......................... 2
4 MIB Overview .................................................... 4 4. MIB Overview ................................................. 3
4.1 The fcmInstanceBasicGroup group ............................... 4 4.1. The fcmInstanceBasicGroup Group ........................ 3
4.2 The fcmSwitchBasicGroup group ................................. 4 4.2. The fcmSwitchBasicGroup Group .......................... 4
4.3 The fcmPortBasicGroup group ................................... 4 4.3. The fcmPortBasicGroup Group ............................ 4
4.4 The fcmPortStatsGroup group ................................... 5 4.4. The fcmPortStatsGroup Group ............................ 4
4.5 The fcmPortClass23StatsGroup group ............................ 5 4.5. The fcmPortClass23StatsGroup Group ..................... 4
4.6 The fcmPortLcStatsGroup group ................................. 5 4.6. The fcmPortLcStatsGroup Group .......................... 4
4.7 The fcmPortClassFStatsGroup group ............................. 5 4.7. The fcmPortClassFStatsGroup Group ...................... 4
4.8 The fcmPortErrorsGroup group .................................. 5 4.8. The fcmPortErrorsGroup Group ........................... 4
4.9 The fcmSwitchPortGroup group .................................. 5 4.9. The fcmSwitchPortGroup Group ........................... 5
4.10 The fcmSwitchLoginGroup group ................................ 6 4.10. The fcmSwitchLoginGroup Group .......................... 5
4.11 The fcmLinkBasicGroup group .................................. 6 4.11. The fcmLinkBasicGroup Group ............................ 5
5 Relationship to Other MIBs ...................................... 6 5. Relationship to Other MIBs ................................... 5
5.1 The Interfaces Group MIB ...................................... 6 5.1. The Interfaces Group MIB ............................... 5
5.2 Entity MIB .................................................... 9 5.2. Entity MIB ............................................. 8
5.3 Host Resources MIB ............................................ 10 5.3. Host Resources MIB ..................................... 9
6 Definitions ..................................................... 11 6. Definitions .................................................. 9
7 Intellectual Property ........................................... 63 7. Acknowledgements ............................................. 57
8 Acknowledgements ................................................ 63 8. Normative References ......................................... 57
9 Normative References ............................................ 63 9. Informative References ....................................... 58
10 Informative References ......................................... 65 10. Security Considerations ...................................... 59
11 Security Considerations ........................................ 66 11. IANA Considerations .......................................... 60
12 IANA Considerations ............................................ 67 11.1. OID Assignment ......................................... 60
12.1 OID Assignment ............................................... 67 11.2. FC Port Type Registry .................................. 60
12.2 FC Port Type Registry ........................................ 67 12. Comparison to the Fibre Channel Management Integration MIB ... 62
13 Comparison to draft-ietf-ipfc-fcmgmt-int-mib-07.txt ............ 70 12.1. Problems with the Fibre Channel Management Integration
14 Comparison to RFC 2837 ......................................... 77 MIB .................................................... 62
15 Author's Address ............................................... 78 12.2. Detailed Changes ....................................... 62
16 Full Copyright Statement ....................................... 78 13. Comparison to RFC 2837 ....................................... 67
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community. In for use with network management protocols in the Internet community.
particular, it describes managed objects for information related to In particular, it describes managed objects for information related
Fibre Channel. to the Fibre Channel.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of RFC Internet-Standard Management Framework, please refer to section 7 of
3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed
Management Information Base or MIB. MIB objects are generally accessed the Management Information Base or MIB. MIB objects are generally
through the Simple Network Management Protocol (SNMP). Objects in the accessed through the Simple Network Management Protocol (SNMP).
MIB are defined using the mechanisms defined in the Structure of Objects in the MIB are defined using the mechanisms defined in the
Management Information (SMI). This memo specifies a MIB module that is Structure of Management Information (SMI). This memo specifies a MIB
compliant to the SMIv2, which is described in STD 58, RFC 2578 module that is compliant to the SMIv2, which is described in STD 58,
[RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
3. Short Overview of Fibre Channel 3. Short Overview of the Fibre Channel
The Fibre Channel (FC) is logically a bidirectional point-to-point The Fibre Channel (FC) is logically a bidirectional point-to-point
serial data channel, structured for high performance capability. The serial data channel, structured for high performance capability. The
Fibre Channel provides a general transport vehicle for higher level Fibre Channel provides a general transport vehicle for higher level
protocols such as Intelligent Peripheral Interface (IPI) and Small protocols such as Intelligent Peripheral Interface (IPI) and Small
Computer System Interface (SCSI) command sets, the High-Performance Computer System Interface (SCSI) command sets, the High-Performance
Parallel Interface (HIPPI) data framing, IP (Internet Protocol), IEEE Parallel Interface (HIPPI) data framing, IP (Internet Protocol), IEEE
802.2, and others. 802.2, and others.
Physically, Fibre Channel is an interconnection of multiple Physically, the Fibre Channel is an interconnection of multiple
communication points, called N_Ports, interconnected either by a communication points, called N_Ports, interconnected either by a
switching network, called a Fabric, or by a point-to-point link. A switching network, called a Fabric, or by a point-to-point link. A
Fibre Channel "node" consists of one or more N_Ports. A Fabric may Fibre Channel "node" consists of one or more N_Ports. A Fabric may
consist of multiple Interconnect Elements, some of which are switches. consist of multiple Interconnect Elements, some of which are
An N_Port connects to the Fabric via a port on a switch called an switches. An N_Port connects to the Fabric via a port on a switch
F_Port. When multiple FC nodes are connected to a single port on a called an F_Port. When multiple FC nodes are connected to a single
switch via an "Arbitrated Loop" topology, the switch port is called an port on a switch via an "Arbitrated Loop" topology, the switch port
FL_Port, and the nodes' ports are called NL_Ports. The term Nx_Port is is called an FL_Port, and the nodes' ports are called NL_Ports. The
used to refer to either an N_Port or an NL_port. The term Fx_Port is term Nx_Port refers to either an N_Port or an NL_port. The term
used to refer to either an F_Port or an FL_port. A switch port, which Fx_Port refers to either an F_Port or an FL_port. A switch port,
is interconnected to another switch port via an Inter Element Link which is interconnected to another switch port via an Inter Element
(IEL), is called an E_Port. A B_Port connects a bridge device with an Link (IEL), is called an E_Port. A B_Port connects a bridge device
E_Port on a switch; a B_Port provides a subset of E_Port functionality. with an E_Port on a switch; a B_Port provides a subset of E_Port
functionality.
Many Fibre Channel components, including the fabric, each node, and most Many Fibre Channel components, including the fabric, each node, and
ports, have globally-unique names. These globally-unique names are most ports, have globally-unique names. These globally-unique names
typically formatted as World Wide Names (WWNs). More information on are typically formatted as World Wide Names (WWNs). More information
WWNs can be found in [WWN1] and [WWN2]. WWNs are expected to be on WWNs can be found in [WWN1] and [WWN2]. WWNs are expected to be
persistent across agent and unit resets. persistent across agent and unit resets.
Fibre Channel frames contain 24-bit address identifiers which identify Fibre Channel frames contain 24-bit address identifiers that identify
the frame's source and destination ports. Each FC port has an address the frame's source and destination ports. Each FC port has an
identifier and a WWN. When a fabric is in use, the FC address address identifier and a WWN. When a fabric is in use, the FC
identifiers are dynamic and are assigned by a switch. address identifiers are dynamic and are assigned by a switch.
4. MIB Overview 4. MIB Overview
This MIB contains the notion of a Fibre Channel management instance, This MIB contains the notion of a Fibre Channel management instance,
which is defined as a separable managed instance of Fibre Channel which is defined as a separable managed instance of Fibre Channel
functionality. Fibre Channel functionality may be grouped into Fibre functionality. Fibre Channel functionality may be grouped into Fibre
Channel management instances in whatever way is most convenient for the Channel management instances in whatever way is most convenient for
implementation(s). For example, one such grouping accommodates a single the implementation(s). For example, one such grouping accommodates a
SNMP agent having multiple AgentX [RFC2741] sub-agents, with each sub- single SNMP agent having multiple AgentX [RFC2741] sub-agents, with
agent implementing a different Fibre Channel management instance. In each sub-agent implementing a different Fibre Channel management
order to represent such multiple Fibre Channel management instances instance. To represent such multiple Fibre Channel management
within the same SNMP context (see section 3.3.1 of [RFC3411]), all instances within the same SNMP context (see section 3.3.1 of
tables in this MIB are INDEX-ed by fcmInstanceIndex which is defined as [RFC3411]), all tables in this MIB are INDEX-ed by fcmInstanceIndex,
an arbitrary integer to uniquely identify a particular Fibre Channel which is defined as an arbitrary integer to uniquely identify a
management instance. particular Fibre Channel management instance.
This MIB contains eleven MIB groups, as follows. This MIB contains eleven MIB groups, as follows.
4.1. The fcmInstanceBasicGroup group 4.1. The fcmInstanceBasicGroup Group
This group contains basic information about a Fibre Channel managed This group contains basic information about a Fibre Channel managed
instance, including its name and description, the Fibre Channel instance, including its name and description, the Fibre Channel
function(s) it performs, and optional pointers to hardware and/or function(s) it performs, and optional pointers to hardware and/or
software components. software components.
4.2. The fcmSwitchBasicGroup group 4.2. The fcmSwitchBasicGroup Group
This group contains basic information about a Fibre Channel switch, This group contains basic information about a Fibre Channel switch,
including its domain-id and whether it is the principal switch of its including its domain-id and whether it is the principal switch of its
fabric. fabric.
4.3. The fcmPortBasicGroup group 4.3. The fcmPortBasicGroup Group
This group contains basic information about a Fibre Channel port, This group contains basic information about a Fibre Channel port,
including its port name (WWN), the name of the node (if any) of which it including its port name (WWN), the name of the node (if any) of which
it is a part, the type of port, the classes of service it supports,
is a part, the type of port, the classes of service it supports, its its transmitter and connector types, and the higher level protocols
transmitter and connector types, and the higher level protocols it it supports.
supports.
Each Fibre Channel port is represented by an entry in the ifTable (see Each Fibre Channel port is represented by an entry in the ifTable
below). The tables relating to ports in this MIB are indexed by the (see below). The tables relating to ports in this MIB are indexed by
port's value of ifIndex. the port's value of ifIndex.
4.4. The fcmPortStatsGroup group 4.4. The fcmPortStatsGroup Group
This group contains traffic statistics, which are not specific to any This group contains traffic statistics, which are not specific to any
particular class of service, for Fibre Channel ports. particular class of service, for Fibre Channel ports.
4.5. The fcmPortClass23StatsGroup group 4.5. The fcmPortClass23StatsGroup Group
This group contains traffic statistics which are specific to Class 2 or This group contains traffic statistics that are specific to Class 2
Class 3 traffic on Fibre Channel ports, including class-specific frame or Class 3 traffic on Fibre Channel ports, including class-specific
and octet counters and counters of busy and reject frames. frame and octet counters and counters of busy and reject frames.
4.6. The fcmPortLcStatsGroup group 4.6. The fcmPortLcStatsGroup Group
Some of the statistics in the fcmPortClass23StatsGroup can increase Some of the statistics in the fcmPortClass23StatsGroup can increase
rapidly enough to warrant them being defined using the Counter64 syntax. rapidly enough to warrant them being defined using the Counter64
However, some old SNMP systems do not (yet) support Counter64 objects. syntax. However, some old SNMP systems do not (yet) support
Thus, this group defines low-capacity (Counter32-based) equivalents for Counter64 objects. Thus, this group defines low-capacity
the Counter64-based statistics in the fcmPortClass23StatsGroup group. (Counter32-based) equivalents for the Counter64-based statistics in
the fcmPortClass23StatsGroup group.
4.7. The fcmPortClassFStatsGroup group 4.7. The fcmPortClassFStatsGroup Group
This group contains traffic statistics which are specific to Class F This group contains traffic statistics that are specific to Class F
traffic on the E_Ports of a Fibre Channel switch. traffic on the E_Ports of a Fibre Channel switch.
4.8. The fcmPortErrorsGroup group 4.8. The fcmPortErrorsGroup Group
This group contains counters of various error conditions which can occur This group contains counters of various error conditions that can
on Fibre Channel ports. occur on Fibre Channel ports.
4.9. The fcmSwitchPortGroup group 4.9. The fcmSwitchPortGroup Group
This group contains information about ports on a Fibre Channel switch. This group contains information about ports on a Fibre Channel
For an Fx_Port, it includes the port's timeout values, its hold-time, switch. For an Fx_Port, it includes the port's timeout values, its
and its capabilities in terms of maximum and minimum buffer-to-buffer hold-time, and its capabilities in terms of maximum and minimum
credit allocations, maximum and minimum data field size, and support for buffer-to-buffer credit allocations, maximum and minimum data field
class 2 and class 3 sequenced delivery. For an E_Port or B_Port, it sizes, and support for class 2 and class 3 sequenced delivery. For
includes the buffer-to-buffer credit allocation and data field size. an E_Port or B_Port, it includes the buffer-to-buffer credit
allocation and data field size.
4.10. The fcmSwitchLoginGroup group 4.10. The fcmSwitchLoginGroup Group
This group contains information, known to a Fibre Channel switch, about This group contains information, known to a Fibre Channel switch,
its attached/logged-in Nx_Ports and the service parameters which have about its attached/logged-in Nx_Ports and the service parameters that
been agreed with them. have been agreed with them.
4.11. The fcmLinkBasicGroup group 4.11. The fcmLinkBasicGroup Group
This group contains information, known to a local Fibre Channel This group contains information known to a local Fibre Channel
management instance, about Fibre Channel links, including links which management instance, and concerning Fibre Channel links including
terminate locally. those which terminate locally.
5. Relationship to Other MIBs 5. Relationship to Other MIBs
This MIB is a replacement for two other MIBs: RFC 2837, and the Fibre This MIB is a replacement for two other MIBs: RFC 2837, and the
Channel Management Integration MIB which was originally submitted as an Fibre Channel Management Integration MIB which was originally
Internet Draft to the IETF's IPFC Working Group as draft-ietf-ipfc- submitted as an Internet Draft to the IETF's IPFC Working Group, and
fcmgmt-int-mib-0n.txt. is now available as [MIB-FA].
5.1. The Interfaces Group MIB 5.1. The Interfaces Group MIB
The Interfaces Group MIB [RFC2863] contains generic information about The Interfaces Group MIB [RFC2863] contains generic information about
all lower layer interfaces, i.e., interfaces which are (potentially) all lower layer interfaces, i.e., interfaces which are (potentially)
below the internet layer. Thus, each Fibre Channel port should have its below the internet layer. Thus, each Fibre Channel port should have
own row in the ifTable, and that row will contain the generic its own row in the ifTable, and that row will contain the generic
information about the interface/port. The Interfaces Group MIB information about the interface/port. The Interfaces Group MIB
specifies that additional information which is specific to a particular specifies that additional information which is specific to a
type of interface media, should be defined in a media-specific MIB. particular type of interface media, should be defined in a media-
This MIB is the media-specific MIB for Fibre Channel ports/interfaces. specific MIB. This MIB is the media-specific MIB for Fibre Channel
ports/interfaces.
Section 4 of [RFC2863] requires that a media-specific MIB clarify how Section 4 of [RFC2863] requires that a media-specific MIB clarify how
the generic definitions apply for the particular type of media. The the generic definitions apply for the particular type of media. The
clarifications for Fibre Channel interfaces are as follows. clarifications for Fibre Channel interfaces are as follows.
5.1.1. Layering Model 5.1.1. Layering Model
The Interfaces Group MIB permits multiple ifTable entries to be defined The Interfaces Group MIB permits multiple ifTable entries to be
for interface sub-layers, and for those multiple entries to be arranged defined for interface sub-layers, and for those multiple entries to
in a stack. be arranged in a stack.
For Fibre Channel interfaces, no sublayers are defined and a Fibre For Fibre Channel interfaces, no sublayers are defined and a Fibre
Channel interface will typically have no other ifTable rows stacked on Channel interface will typically have no other ifTable rows stacked
top of it, nor underneath it. on top of it, nor underneath it.
5.1.2. Virtual Circuits 5.1.2. Virtual Circuits
This Fibre Channel MIB does not deal with virtual circuits. This Fibre Channel MIB does not deal with virtual circuits.
5.1.3. ifRcvAddressTable 5.1.3. ifRcvAddressTable
The ifRcvAddressTable does not apply to Fibre Channel interfaces. The ifRcvAddressTable does not apply to Fibre Channel interfaces.
5.1.4. ifType 5.1.4. ifType
The value of ifType for a Fibre Channel interface is 56. The value of ifType for a Fibre Channel interface is 56.
5.1.5. ifXxxOctets 5.1.5. ifXxxOctets
The definitions of ifInOctets and ifOutOctets (and similarly, The definitions of ifInOctets and ifOutOctets (and similarly,
ifHCInOctets and ifHCOutOctets) specify that their values include ifHCInOctets and ifHCOutOctets) specify that their values include
framing characters. For Fibre Channel interfaces, they include all the framing characters. For Fibre Channel interfaces, they include all
octets contained in frames between the Start-of-Frame and End-of-Frame the octets contained in frames between the Start-of-Frame and End-
delimiters (excluding the delimiters). of-Frame delimiters (excluding the delimiters).
5.1.6. Specific Interface Group MIB Objects 5.1.6. Specific Interface Group MIB Objects
The following table provides specific implementation guidelines for The following table provides specific implementation guidelines for
applying the objects defined in the Interfaces Group MIB to Fibre applying the objects defined in the Interfaces Group MIB to Fibre
Channel interfaces. For those objects not listed here, refer to their Channel interfaces. For those objects not listed here, refer to
generic definitions in [RFC2863]. (RFC 2863 takes precedence over these their generic definitions in [RFC2863]. (RFC 2863 takes precedence
guidelines in the event of any conflict.) over these guidelines in the event of any conflict.)
Object Guidelines Object Guidelines
ifType 56 ifType 56
ifMtu The MTU as seen by a higher layer ifMtu The MTU as seen by a higher layer
protocol, like IP. That is, when IP is protocol, like IP.
running over the interface, this object is That is, when IP is running over the
the size of the largest IP datagram that interface, this object is the size of the
can be sent/received over the interface. largest IP datagram that can be
sent/received over the interface.
ifSpeed For 1Gbs, this will be 1,000,000,000; for ifSpeed For 1Gbs, this will be 1,000,000,000;
2Gbs, it will be 2,000,000,000. If auto- for 2Gbs, it will be 2,000,000,000. If
negotiation is implemented and enabled on auto-negotiation is implemented and
an interface, and the interface has not enabled on an interface, and the
yet negotiated to an operational speed, interface has not yet negotiated an
this object SHOULD reflect the maximum operational speed, this object SHOULD
speed supported by the interface. reflect the maximum speed supported by
the interface.
ifPhysAddress The interface's 24-bit Fibre Channel ifPhysAddress The interface's 24-bit Fibre Channel
Address Identifier, or the zero-length Address Identifier, or the zero-length
string if no Address Identifier has been string if no Address Identifier has been
assigned to the interface. assigned to the interface.
ifAdminStatus Write access is not required, and support ifAdminStatus Write access is not required, and support
for 'testing' is not required. for 'testing' is not required.
ifOperStatus Support for 'testing' is not required. ifOperStatus Support for 'testing' is not required.
skipping to change at page 8, line 18 skipping to change at page 7, line 27
assigned to the interface. assigned to the interface.
ifAdminStatus Write access is not required, and support ifAdminStatus Write access is not required, and support
for 'testing' is not required. for 'testing' is not required.
ifOperStatus Support for 'testing' is not required. ifOperStatus Support for 'testing' is not required.
The value 'dormant' has no meaning for The value 'dormant' has no meaning for
Fibre Channel interfaces. Fibre Channel interfaces.
ifInOctets The number of octets of information ifInOctets The number of octets of information
ifHCInOctets contained in received frames between the ifHCInOctets contained in received frames between the
Start-of-Frame and End-of-Frame delimiters Start-of-Frame and End-of-Frame
(excluding the delimiters). delimiters (excluding the delimiters).
ifInUcastPkts The number of unicast frames received, ifInUcastPkts The number of unicast frames received,
ifHCInUcastPkts i.e., the number of Start-of-Frame ifHCInUcastPkts i.e., the number of Start-of-Frame
delimiters received for unicast frames. delimiters received for unicast frames.
ifInErrors The sum for this interface of ifInErrors The sum for this interface of
fcmPortLossofSynchs fcmPortLossofSynchs
fcmPortLossofSignals fcmPortLossofSignals
fcmPortPrimSeqProtocolErrors fcmPortPrimSeqProtocolErrors
fcmPortInvalidTxWords fcmPortInvalidTxWords
fcmPortInvalidCRCs fcmPortInvalidCRCs
skipping to change at page 8, line 39 skipping to change at page 7, line 50
fcmPortLossofSignals fcmPortLossofSignals
fcmPortPrimSeqProtocolErrors fcmPortPrimSeqProtocolErrors
fcmPortInvalidTxWords fcmPortInvalidTxWords
fcmPortInvalidCRCs fcmPortInvalidCRCs
fcmPortAddressErrors fcmPortAddressErrors
fcmPortDelimiterErrors fcmPortDelimiterErrors
fcmPortTruncatedFrames fcmPortTruncatedFrames
fcmPortEncodingDisparityErrors fcmPortEncodingDisparityErrors
plus any errors in fcmPortOtherErrors plus any errors in fcmPortOtherErrors
which were input errors. that were input errors.
ifOutOctets The number of octets of information ifOutOctets The number of octets of information
ifHCOutOctets contained in transmitted frames between ifHCOutOctets contained in transmitted frames between
the Start-of-Frame and End-of-Frame the Start-of-Frame and End-of-Frame
delimiters (excluding the delimiters). delimiters (excluding the delimiters).
ifOutUcastPkts The number of frames transmitted, ifOutUcastPkts The number of frames transmitted,
ifHCOutUcastPkts i.e., the number of start-of-frame ifHCOutUcastPkts i.e., the number
delimiters transmitted for unicast frames. of start-of-frame delimiters transmitted
for unicast frames.
ifOutErrors This is the number of errors in ifOutErrors This is the number of errors in
fcmPortOtherErrors which were output fcmPortOtherErrors that were output
errors. errors.
ifInMulticastPkts These counters are not incremented ifInMulticastPkts These counters are not incremented
ifInBroadcastPkts (unless a proprietary mechanism for ifInBroadcastPkts (unless a proprietary mechanism for
ifOutMulticastPkts multicast/broadcast is supported). ifOutMulticastPkts multicast/broadcast is supported).
ifOutBroadcastPkts ifOutBroadcastPkts
ifHCInMulticastPkts ifHCInMulticastPkts
ifHCInBroadcastPkts ifHCInBroadcastPkts
ifHCOutMulticastPkts ifHCOutMulticastPkts
ifHCOutBroadcastPkts ifHCOutBroadcastPkts
ifLinkUpDownTrapEnable Refer to [RFC2863]. Default is 'enabled' ifLinkUpDownTrapEnable Refer to [RFC2863]. Default is 'enabled'
skipping to change at page 9, line 26 skipping to change at page 8, line 37
ifHCOutBroadcastPkts ifHCOutBroadcastPkts
ifLinkUpDownTrapEnable Refer to [RFC2863]. Default is 'enabled' ifLinkUpDownTrapEnable Refer to [RFC2863]. Default is 'enabled'
ifHighSpeed The current operational speed of the ifHighSpeed The current operational speed of the
interface in millions of bits per second. interface in millions of bits per second.
For 1Gbs, this will be 1000; for 2Gbs, it For 1Gbs, this will be 1000; for 2Gbs, it
will be 2000. If auto-negotiation is will be 2000. If auto-negotiation is
implemented and enabled on an interface, implemented and enabled on an interface,
and the interface has not yet negotiated and the interface has not yet negotiated
to an operational speed, this object an operational speed, this object SHOULD
SHOULD reflect the maximum speed supported reflect the maximum speed supported by
by the interface. the interface.
ifPromiscuousMode This will normally be 'false' ifPromiscuousMode This will normally be 'false'
ifConnectorPresent This will normally be 'true'. ifConnectorPresent This will normally be 'true'.
5.2. Entity MIB 5.2. Entity MIB
The Entity MIB [RFC2737] contains information about individual physical The Entity MIB [RFC2737] contains information about individual
components and any hierarchical relationship which may exist between physical components and any hierarchical relationship that may exist
them. Any Fibre Channel management instance with a relationship to a between them. Any Fibre Channel management instance with a
physical component (or to a hierarchy of physical components) will have relationship to a physical component (or to a hierarchy of physical
its value of the fcmInstancePhysicalIndex object contain a pointer to components) will have its value of the fcmInstancePhysicalIndex
the relevant row in the Entity MIB. If there is no correspondence to a object contain a pointer to the relevant row in the Entity MIB. If
physical component (or said component does not have a row in the Entity there is no correspondence with a physical component (or said
MIB), then the value of fcmInstancePhysicalIndex is zero. (Note that an component does not have a row in the Entity MIB), then the value of
implementation is not required to support a non-zero value of fcmInstancePhysicalIndex is zero. (Note that an implementation is
not required to support a non-zero value of
fcmInstancePhysicalIndex.) fcmInstancePhysicalIndex.)
5.3. Host Resources MIB 5.3. Host Resources MIB
The Host Resources MIB [RFC2790] includes information about installed The Host Resources MIB [RFC2790] includes information about installed
software modules. Any Fibre Channel management instance with a software modules. Any Fibre Channel management instance with a
correspondence to a software module, will have its value of the correspondence to a software module, will have its value of the
fcmInstanceSoftwareIndex object contain a pointer to the relevant row in fcmInstanceSoftwareIndex object contain a pointer to the relevant row
the Host Resources MIB. If there is no correspondence to a software in the Host Resources MIB. If there is no correspondence to a
module (or said software module does not has a row in the Host Resources software module (or said software module does not have a row in the
MIB), then the value of fcmInstanceSoftwareIndex is zero. (Note that an Host Resources MIB), then the value of fcmInstanceSoftwareIndex is
agent implementation is not required to support a non-zero value of zero. (Note that an agent implementation is not required to support
fcmInstanceSoftwareIndex.) a non-zero value of fcmInstanceSoftwareIndex.)
6. Definitions 6. Definitions
FC-MGMT-MIB DEFINITIONS ::= BEGIN FC-MGMT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Integer32, Unsigned32, Counter32, Counter64, transmission Integer32, Unsigned32, Counter32, Counter64, transmission
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TruthValue, TEXTUAL-CONVENTION TruthValue, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
ifIndex FROM IF-MIB ifIndex FROM IF-MIB
SnmpAdminString FROM SNMP-FRAMEWORK-MIB; SnmpAdminString FROM SNMP-FRAMEWORK-MIB;
fcMgmtMIB MODULE-IDENTITY fcMgmtMIB MODULE-IDENTITY
LAST-UPDATED "200412140000Z" LAST-UPDATED "200504260000Z" -- 26 April 2005
ORGANIZATION "IETF IPS (IP-Storage) Working Group" ORGANIZATION "IETF IPS (IP-Storage) Working Group"
CONTACT-INFO CONTACT-INFO
" Keith McCloghrie " Keith McCloghrie
Cisco Systems, Inc. Cisco Systems, Inc.
Tel: +1 408 526-5260 Tel: +1 408 526-5260
E-mail: kzm@cisco.com E-mail: kzm@cisco.com
Postal: 170 West Tasman Drive Postal: 170 West Tasman Drive
San Jose, CA USA 95134 San Jose, CA USA 95134
" "
DESCRIPTION DESCRIPTION
"This module defines management information specific to "This module defines management information specific to
Fibre Channel-attached devices. Fibre Channel-attached devices.
Copyright (C) The Internet Society (2004). This version of Copyright (C) The Internet Society (2005). This version
this MIB module is part of RFC yyyy; see the RFC itself for of this MIB module is part of RFC 4044; see the RFC
full legal notices." itself for full legal notices."
REVISION "200412140000Z" REVISION "200504260000Z" -- 26 April 2005
DESCRIPTION DESCRIPTION
"Initial version of the Fibre Channel Mgmt MIB module." "Initial version of the Fibre Channel Mgmt MIB module."
::= { transmission nnn } -- IANA, please enter the value you assign here ::= { transmission 56 }
fcmgmtObjects OBJECT IDENTIFIER ::= { fcMgmtMIB 1 } fcmgmtObjects OBJECT IDENTIFIER ::= { fcMgmtMIB 1 }
fcmgmtNotifications OBJECT IDENTIFIER ::= { fcMgmtMIB 2 } fcmgmtNotifications OBJECT IDENTIFIER ::= { fcMgmtMIB 2 }
fcmgmtNotifPrefix OBJECT IDENTIFIER ::= { fcmgmtNotifications 0 } fcmgmtNotifPrefix OBJECT IDENTIFIER ::= { fcmgmtNotifications 0 }
fcmgmtConformance OBJECT IDENTIFIER ::= { fcMgmtMIB 3 } fcmgmtConformance OBJECT IDENTIFIER ::= { fcMgmtMIB 3 }
--******************************** --********************************
-- Textual Conventions -- Textual Conventions
-- --
FcNameIdOrZero ::= TEXTUAL-CONVENTION FcNameIdOrZero ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The World Wide Name (WWN) associated with a Fibre Channel "The World Wide Name (WWN) associated with a Fibre Channel
(FC) entity. WWNs were initially defined as 64-bits in (FC) entity. WWNs were initially defined as 64-bits in
length. The latest definition (for future use) is 128-bits length. The latest definition (for future use) is 128-bits
long. The zero-length string value is used in circumstances long. The zero-length string value is used in
where the WWN is unassigned/unknown." circumstances in which the WWN is unassigned/unknown."
SYNTAX OCTET STRING (SIZE(0 | 8 | 16)) SYNTAX OCTET STRING (SIZE(0 | 8 | 16))
FcAddressIdOrZero ::= TEXTUAL-CONVENTION FcAddressIdOrZero ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A Fibre Channel Address ID, a 24-bit value unique within "A Fibre Channel Address ID, a 24-bit value unique within
the address space of a Fabric. The zero-length string value the address space of a Fabric. The zero-length string value
is used in circumstances where the WWN is is used in circumstances in which the WWN is
unassigned/unknown." unassigned/unknown."
SYNTAX OCTET STRING (SIZE(0 | 3)) SYNTAX OCTET STRING (SIZE(0 | 3))
FcDomainIdOrZero ::= TEXTUAL-CONVENTION FcDomainIdOrZero ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Domain Id (of a FC switch), or zero if the no Domain Id "The Domain Id (of an FC switch), or zero if the no Domain
has been assigned." Id has been assigned."
SYNTAX Integer32 (0..239) SYNTAX Integer32 (0..239)
FcPortType ::= TEXTUAL-CONVENTION FcPortType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of a Fibre Channel port, as indicated by the use "The type of a Fibre Channel port, as indicated by the use
of the appropriate value assigned by IANA." of the appropriate value assigned by IANA."
REFERENCE REFERENCE
"The IANA-maintained registry for "The IANA-maintained registry for
Fibre Channel port types. " Fibre Channel port types (http://www.iana.org/)."
-- IANA, please extend the text inside the immediately
-- preceeding quotes to include a location at which a
-- reader can ascertain the latest assigned values
SYNTAX Unsigned32 SYNTAX Unsigned32
FcClasses ::= TEXTUAL-CONVENTION FcClasses ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of Fibre Channel classes of service." "A set of Fibre Channel classes of service."
REFERENCE REFERENCE
"Classes of service are described in FC-FS Section 13." "Classes of service are described in FC-FS Section 13."
SYNTAX BITS { classF(0), class1(1), class2(2), class3(3), SYNTAX BITS { classF(0), class1(1), class2(2), class3(3),
class4(4), class5(5), class6(6) } class4(4), class5(5), class6(6) }
skipping to change at page 14, line 9 skipping to change at page 12, line 9
FcDataFieldSize ::= TEXTUAL-CONVENTION FcDataFieldSize ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Receive Data Field Size associated with an FC port." "The Receive Data Field Size associated with an FC port."
SYNTAX Integer32 (128..2112) SYNTAX Integer32 (128..2112)
FcUnitFunctions ::= TEXTUAL-CONVENTION FcUnitFunctions ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A set of functions that a Fibre Channel Interconnect "A set of functions that a Fibre Channel Interconnect
Element or Platform might perform. A value with no bits Element or Platform might perform. A value with no bits set
set, indicates the function(s) are unknown. The individual indicates the function(s) are unknown. The individual bits
bits have the following meanings: have the following meanings:
other - none of the following. other - none of the following.
hub - a device that interconnects L_Ports, but does not hub - a device that interconnects L_Ports, but does not
operate as an FL_Port. operate as an FL_Port.
switch - a fabric element conforming to the Fibre Channel switch - a fabric element conforming to the Fibre Channel
switch fabric set of standards (e.g., FC-SW, FC-SW-2). switch fabric set of standards (e.g., [FC-SW-3]).
bridge - a device that encapsulates Fibre Channel frames bridge - a device that encapsulates Fibre Channel frames
within another protocol (e.g., FC-BB, FC-BB-2). within another protocol (e.g., [FC-BB], FC-BB-2).
gateway - a device that converts an FC-4 to another protocol gateway - a device that converts an FC-4 to another protocol
(e.g., FCP to iSCSI). (e.g., FCP to iSCSI).
host - a computer system that provides end users services host - a computer system that provides end users with
such as computation and storage access. services such as computation and storage access.
storageSubsys - an integrated collection of storage storageSubsys - an integrated collection of storage
controllers, storage devices, and necessary software, that controllers, storage devices, and necessary software that
provides storage services to one or more hosts. provides storage services to one or more hosts.
storageAccessDev - a device that provides storage management storageAccessDev - a device that provides storage management
and access for heterogeneous hosts and heterogeneous devices and access for heterogeneous hosts and heterogeneous devices
(e.g., medium changer). (e.g., medium changer).
nas - a device that connects to a network and provides file nas - a device that connects to a network and provides file
access services. access services.
wdmux - a device that modulates/demodulates each of several wdmux - a device that modulates/demodulates each of several
skipping to change at page 16, line 46 skipping to change at page 14, line 10
fcmInstanceTextName SnmpAdminString, fcmInstanceTextName SnmpAdminString,
fcmInstanceDescr SnmpAdminString, fcmInstanceDescr SnmpAdminString,
fcmInstanceFabricId FcNameIdOrZero fcmInstanceFabricId FcNameIdOrZero
} }
fcmInstanceIndex OBJECT-TYPE fcmInstanceIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer value which uniquely identifies this "An arbitrary integer value that uniquely identifies this
instance amongst all local Fibre Channel management instance amongst all local Fibre Channel management
instances. instances.
It is mandatory to keep this value constant between restarts It is mandatory to keep this value constant between restarts
of the agent, and to make every possible effort to keep it of the agent, and to make every possible effort to keep it
constant across restarts (but note, it is unrealistic to constant across restarts (but note, it is unrealistic to
expect it to remain constant across all re-configurations of expect it to remain constant across all re-configurations of
the local system, e.g., across the replacement of all non- the local system, e.g., across the replacement of all non-
volatile storage)." volatile storage)."
::= { fcmInstanceEntry 1 } ::= { fcmInstanceEntry 1 }
skipping to change at page 17, line 45 skipping to change at page 15, line 5
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this management instance corresponds to a physical "If this management instance corresponds to a physical
component (or to a hierarchy of physical components) component (or to a hierarchy of physical components)
identified by the Entity-MIB, then this object's value is identified by the Entity-MIB, then this object's value is
the value of the entPhysicalIndex of that component (or of the value of the entPhysicalIndex of that component (or of
the component at the root of that hierarchy). If there is the component at the root of that hierarchy). If there is
no correspondence to a physical component (or no component no correspondence to a physical component (or no component
which has an entPhysicalIndex value), then the value of this that has an entPhysicalIndex value), then the value of this
object is zero." object is zero."
REFERENCE REFERENCE
"entPhysicalIndex is defined in the Entity MIB, RFC 2737." "entPhysicalIndex is defined in the Entity MIB, RFC 2737."
::= { fcmInstanceEntry 4 } ::= { fcmInstanceEntry 4 }
fcmInstanceSoftwareIndex OBJECT-TYPE fcmInstanceSoftwareIndex OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If this management instance corresponds to an installed "If this management instance corresponds to an installed
software module identified in the Host Resources MIB, then software module identified in the Host Resources MIB, then
this object's value is the value of the hrSWInstalledIndex this object's value is the value of the hrSWInstalledIndex
of that module. If there is no correspondence to an of that module. If there is no correspondence to an
installed software module (or no module which has a installed software module (or no module that has a
hrSWInstalledIndex value), then the value of this object is hrSWInstalledIndex value), then the value of this object is
zero." zero."
REFERENCE REFERENCE
"hrSWInstalledIndex is defined in the Host Resources MIB, "hrSWInstalledIndex is defined in the Host Resources MIB,
RFC 2790" RFC 2790"
::= { fcmInstanceEntry 5 } ::= { fcmInstanceEntry 5 }
fcmInstanceStatus OBJECT-TYPE fcmInstanceStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
skipping to change at page 19, line 14 skipping to change at page 16, line 19
DESCRIPTION DESCRIPTION
"A textual description of this management instance and the "A textual description of this management instance and the
Fibre Channel entity/entities that it is managing." Fibre Channel entity/entities that it is managing."
::= { fcmInstanceEntry 8 } ::= { fcmInstanceEntry 8 }
fcmInstanceFabricId OBJECT-TYPE fcmInstanceFabricId OBJECT-TYPE
SYNTAX FcNameIdOrZero SYNTAX FcNameIdOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The globally unique Fabric Identifier which identifies the "The globally unique Fabric Identifier that identifies the
fabric to which the Fibre Channel entity/entities managed by fabric to which the Fibre Channel entity/entities managed by
this management instance are connected, or, of which they this management instance are connected, or, of which they
are a part. This is typically the Node WWN of the principal are a part. This is typically the Node WWN of the principal
switch of a Fibre Channel fabric. The zero-length string switch of a Fibre Channel fabric. The zero-length string
indicates that the fabric identifier is unknown (or not indicates that the fabric identifier is unknown (or not
applicable). applicable).
In the event that the Fibre Channel entity/entities managed In the event that the Fibre Channel entity/entities managed
by this management instance is/are connected to multiple by this management instance is/are connected to multiple
fabrics, then this object records the first (known) one." fabrics, then this object records the first (known) one."
skipping to change at page 19, line 36 skipping to change at page 16, line 41
--******************************** --********************************
-- The Fibre Channel Switch Table -- The Fibre Channel Switch Table
-- --
fcmSwitchTable OBJECT-TYPE fcmSwitchTable OBJECT-TYPE
SYNTAX SEQUENCE OF FcmSwitchEntry SYNTAX SEQUENCE OF FcmSwitchEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of information about Fibre Channel switches which "A table of information about Fibre Channel switches that
are managed by Fibre Channel management instances. Each are managed by Fibre Channel management instances. Each
Fibre Channel management instance can manage one or more Fibre Channel management instance can manage one or more
Fibre Channel switches." Fibre Channel switches."
::= { fcmgmtObjects 2 } ::= { fcmgmtObjects 2 }
fcmSwitchEntry OBJECT-TYPE fcmSwitchEntry OBJECT-TYPE
SYNTAX FcmSwitchEntry SYNTAX FcmSwitchEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a particular Fibre Channel switch which "Information about a particular Fibre Channel switch that is
is managed by the management instance given by managed by the management instance given by
fcmInstanceIndex." fcmInstanceIndex."
INDEX { fcmInstanceIndex, fcmSwitchIndex } INDEX { fcmInstanceIndex, fcmSwitchIndex }
::= { fcmSwitchTable 1 } ::= { fcmSwitchTable 1 }
FcmSwitchEntry ::= FcmSwitchEntry ::=
SEQUENCE { SEQUENCE {
fcmSwitchIndex Unsigned32, fcmSwitchIndex Unsigned32,
fcmSwitchDomainId FcDomainIdOrZero, fcmSwitchDomainId FcDomainIdOrZero,
fcmSwitchPrincipal TruthValue, fcmSwitchPrincipal TruthValue,
fcmSwitchWWN FcNameIdOrZero fcmSwitchWWN FcNameIdOrZero
} }
fcmSwitchIndex OBJECT-TYPE fcmSwitchIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer which uniquely identifies a Fibre "An arbitrary integer that uniquely identifies a Fibre
Channel switch amongst those managed by one Fibre Channel Channel switch amongst those managed by one Fibre Channel
management instance. management instance.
It is mandatory to keep this value constant between restarts It is mandatory to keep this value constant between restarts
of the agent, and to make every possible effort to keep it of the agent, and to make every possible effort to keep it
constant across restarts." constant across restarts."
::= { fcmSwitchEntry 1 } ::= { fcmSwitchEntry 1 }
fcmSwitchDomainId OBJECT-TYPE fcmSwitchDomainId OBJECT-TYPE
SYNTAX FcDomainIdOrZero SYNTAX FcDomainIdOrZero
skipping to change at page 22, line 33 skipping to change at page 19, line 30
DESCRIPTION DESCRIPTION
"The World Wide Name of the port, or the zero-length string "The World Wide Name of the port, or the zero-length string
if the port does not have a WWN." if the port does not have a WWN."
::= { fcmPortEntry 2 } ::= { fcmPortEntry 2 }
fcmPortNodeWwn OBJECT-TYPE fcmPortNodeWwn OBJECT-TYPE
SYNTAX FcNameIdOrZero SYNTAX FcNameIdOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The World Wide Name of the Node which contains this port, "The World Wide Name of the Node that contains this port, or
or the zero-length string if the port does not have a node the zero-length string if the port does not have a node
WWN." WWN."
::= { fcmPortEntry 3 } ::= { fcmPortEntry 3 }
fcmPortAdminType OBJECT-TYPE fcmPortAdminType OBJECT-TYPE
SYNTAX FcPortType SYNTAX FcPortType
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administratively desired type of this port." "The administratively desired type of this port."
::= { fcmPortEntry 4 } ::= { fcmPortEntry 4 }
skipping to change at page 24, line 20 skipping to change at page 21, line 12
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The module type of the port connector. This object refers "The module type of the port connector. This object refers
to the hardware implementation of the port. It will be to the hardware implementation of the port. It will be
'embedded' if the hardware equivalent to Gigabit interface 'embedded' if the hardware equivalent to Gigabit interface
card (GBIC) is part of the line card and is unremovable. It card (GBIC) is part of the line card and is unremovable. It
will be 'glm' if it's a gigabit link module (GLM). It will will be 'glm' if it's a gigabit link module (GLM). It will
be 'gbicSerialId' if the GBIC serial id can be read, else it be 'gbicSerialId' if the GBIC serial id can be read, else it
will be 'gbicNoSerialId'. It will be 'sfpSerialId', if the will be 'gbicNoSerialId'. It will be 'sfpSerialId' if the
small form factor (SFP) pluggable GBICs serial id can be small form factor (SFP) pluggable GBICs serial id can be
read, else it will be 'sfpNoSerialId'." read, else it will be 'sfpNoSerialId'."
REFERENCE REFERENCE
"FC-GS-3, section 6.1.2.2.4" "FC-GS-3, section 6.1.2.2.4"
::= { fcmPortEntry 9 } ::= { fcmPortEntry 9 }
fcmPortSerialNumber OBJECT-TYPE fcmPortSerialNumber OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 25, line 44 skipping to change at page 22, line 33
loop(1), loop(1),
fabric(2), fabric(2),
scsi(3), scsi(3),
tcpIp(4), tcpIp(4),
vi(5), vi(5),
ficon(6) ficon(6)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A bit mask specifying the higher level protocols which are "A bit mask specifying the higher level protocols that are
capable of being running over this port. Note that for capable of running over this port. Note that for generic
generic Fx_Ports, E_Ports and B_Ports, this object will Fx_Ports, E_Ports, and B_Ports, this object will indicate
indicate all protocols." all protocols."
::= { fcmPortEntry 13 } ::= { fcmPortEntry 13 }
fcmPortOperProtocols OBJECT-TYPE fcmPortOperProtocols OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
unknown(0), unknown(0),
loop(1), loop(1),
fabric(2), fabric(2),
scsi(3), scsi(3),
tcpIp(4), tcpIp(4),
vi(5), vi(5),
ficon(6) ficon(6)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A bit mask specifying the higher level protocols which are "A bit mask specifying the higher level protocols that are
currently operational on this port. For Fx_Ports, E_Ports currently operational on this port. For Fx_Ports, E_Ports,
and B_Ports, this object will typically have the value and B_Ports, this object will typically have the value
'unknown'." 'unknown'."
::= { fcmPortEntry 14 } ::= { fcmPortEntry 14 }
--******************************** --********************************
-- Port Statistics -- Port Statistics
-- --
fcmPortStatsTable OBJECT-TYPE fcmPortStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF FcmPortStatsEntry SYNTAX SEQUENCE OF FcmPortStatsEntry
skipping to change at page 33, line 4 skipping to change at page 29, line 27
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Class F frames that were discarded upon "The number of Class F frames that were discarded upon
reception at this port." reception at this port."
::= { fcmPortStatsEntry 25 } ::= { fcmPortStatsEntry 25 }
--******************************** --********************************
-- Port Low-capacity Statistics -- Port Low-capacity Statistics
-- --
-- these are Counter32 "low-capacity" counters for systems -- these are Counter32 "low-capacity" counters for systems
-- that do not support Counter64's
fcmPortLcStatsTable OBJECT-TYPE fcmPortLcStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF FcmPortLcStatsEntry SYNTAX SEQUENCE OF FcmPortLcStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of Counter32-based statistics for systems which do "A list of Counter32-based statistics for systems that do
not support Counter64." not support Counter64."
::= { fcmgmtObjects 5 } ::= { fcmgmtObjects 5 }
fcmPortLcStatsEntry OBJECT-TYPE fcmPortLcStatsEntry OBJECT-TYPE
SYNTAX FcmPortLcStatsEntry SYNTAX FcmPortLcStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry containing low-capacity (i.e., based on Counter32) "An entry containing low-capacity (i.e., based on Counter32)
statistics for a Fibre Channel port. If any counter in this statistics for a Fibre Channel port. If any counter in this
skipping to change at page 40, line 34 skipping to change at page 37, line 13
::= { fcmPortErrorsEntry 5 } ::= { fcmPortErrorsEntry 5 }
fcmPortLinkFailures OBJECT-TYPE fcmPortLinkFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of link failures. This count is part of FC-PH's "The number of link failures. This count is part of FC-PH's
Link Error Status Block (LESB)." Link Error Status Block (LESB)."
REFERENCE REFERENCE
"FC-PH, rev 4.3, 1 June 1994, section 29.8." "FC-PH, rev 4.3, 1 June 1994, section 29.8 [FC-PH]."
::= { fcmPortErrorsEntry 6 } ::= { fcmPortErrorsEntry 6 }
fcmPortLossofSynchs OBJECT-TYPE fcmPortLossofSynchs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of instances of synchronization loss detected at "The number of instances of synchronization loss detected at
this port. This count is part of FC-PH's Link Error Status this port. This count is part of FC-PH's Link Error Status
Block (LESB)." Block (LESB)."
skipping to change at page 41, line 46 skipping to change at page 38, line 22
(LESB)." (LESB)."
REFERENCE REFERENCE
"FC-PH, rev 4.3, 1 June 1994, section 29.8." "FC-PH, rev 4.3, 1 June 1994, section 29.8."
::= { fcmPortErrorsEntry 10 } ::= { fcmPortErrorsEntry 10 }
fcmPortInvalidCRCs OBJECT-TYPE fcmPortInvalidCRCs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames received with invalid CRC. This count "The number of frames received with an invalid CRC. This
is part of FC-PH's Link Error Status Block (LESB)." count is part of FC-PH's Link Error Status Block (LESB)."
REFERENCE REFERENCE
"FC-PH, rev 4.3, 1 June 1994, section 29.8." "FC-PH, rev 4.3, 1 June 1994, section 29.8."
::= { fcmPortErrorsEntry 11 } ::= { fcmPortErrorsEntry 11 }
fcmPortInvalidOrderedSets OBJECT-TYPE fcmPortInvalidOrderedSets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of invalid ordered sets received at this port." "The number of invalid ordered sets received at this port."
::= { fcmPortErrorsEntry 12 } ::= { fcmPortErrorsEntry 12 }
fcmPortFrameTooLongs OBJECT-TYPE fcmPortFrameTooLongs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames received at this port where the frame "The number of frames received at this port for which the
length was greater than what was agreed to in FLOGI/PLOGI. frame length was greater than what was agreed to in
This could be caused by losing the end of frame delimiter." FLOGI/PLOGI. This could be caused by losing the end of
frame delimiter."
::= { fcmPortErrorsEntry 13 } ::= { fcmPortErrorsEntry 13 }
fcmPortTruncatedFrames OBJECT-TYPE fcmPortTruncatedFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames received at this port where the frame "The number of frames received at this port for which the
length was less than the minimum indicated by the frame frame length was less than the minimum indicated by the
header - normally 24 bytes, but it could be more if the frame header - normally 24 bytes, but it could be more if
DFCTL field indicates an optional header should have been the DFCTL field indicates an optional header should have
present." been present."
::= { fcmPortErrorsEntry 14 } ::= { fcmPortErrorsEntry 14 }
fcmPortAddressErrors OBJECT-TYPE fcmPortAddressErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of frames received with unknown addressing; for "The number of frames received with unknown addressing; for
example, an unknown SID or DID." example, an unknown SID or DID."
::= { fcmPortErrorsEntry 15 } ::= { fcmPortErrorsEntry 15 }
fcmPortDelimiterErrors OBJECT-TYPE fcmPortDelimiterErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of invalid frame delimiters received at this "The number of invalid frame delimiters received at this
port. An example is a frame with a class 2 start and a class port. An example is a frame with a class 2 start and a
3 at the end." class 3 at the end."
::= { fcmPortErrorsEntry 16 } ::= { fcmPortErrorsEntry 16 }
fcmPortEncodingDisparityErrors OBJECT-TYPE fcmPortEncodingDisparityErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of encoding disparity errors received at this "The number of encoding disparity errors received at this
port." port."
::= { fcmPortErrorsEntry 17 } ::= { fcmPortErrorsEntry 17 }
fcmPortOtherErrors OBJECT-TYPE fcmPortOtherErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of errors which were detected on this port but "The number of errors that were detected on this port but
which were not counted by any other error counter in this not counted by any other error counter in this row."
row."
::= { fcmPortErrorsEntry 18 } ::= { fcmPortErrorsEntry 18 }
--******************************** --********************************
-- The Fibre Channel Fx_Port Table -- The Fibre Channel Fx_Port Table
-- --
fcmFxPortTable OBJECT-TYPE fcmFxPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF FcmFxPortEntry SYNTAX SEQUENCE OF FcmFxPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Additional information about Fibre Channel ports which is "Additional information about Fibre Channel ports that is
specific to Fx_Ports. This table will contain one entry for specific to Fx_Ports. This table will contain one entry for
each fcmPortTable entry which represents an Fx_Port." each fcmPortTable entry that represents an Fx_Port."
::= { fcmgmtObjects 7 } ::= { fcmgmtObjects 7 }
fcmFxPortEntry OBJECT-TYPE fcmFxPortEntry OBJECT-TYPE
SYNTAX FcmFxPortEntry SYNTAX FcmFxPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry contains information about a specific Fx_Port." "Each entry contains information about a specific Fx_Port."
INDEX { ifIndex } INDEX { ifIndex }
::= { fcmFxPortTable 1 } ::= { fcmFxPortTable 1 }
skipping to change at page 45, line 31 skipping to change at page 41, line 28
condition." condition."
::= { fcmFxPortEntry 2 } ::= { fcmFxPortEntry 2 }
fcmFxPortRttov OBJECT-TYPE fcmFxPortRttov OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Receiver_Transmitter_Timeout value of this Fx_Port. "The Receiver_Transmitter_Timeout value of this Fx_Port.
This is used by the receiver logic to detect Loss of This is used by the receiver logic to detect a Loss of
Synchronization." Synchronization."
::= { fcmFxPortEntry 3 } ::= { fcmFxPortEntry 3 }
fcmFxPortHoldTime OBJECT-TYPE fcmFxPortHoldTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "microseconds" UNITS "microseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum time that this Fx_Port shall hold a frame "The maximum time that this Fx_Port shall hold a frame
skipping to change at page 46, line 8 skipping to change at page 41, line 50
frame. The value 0 means that this Fx_Port does not support frame. The value 0 means that this Fx_Port does not support
this parameter." this parameter."
::= { fcmFxPortEntry 4 } ::= { fcmFxPortEntry 4 }
fcmFxPortCapBbCreditMax OBJECT-TYPE fcmFxPortCapBbCreditMax OBJECT-TYPE
SYNTAX FcBbCredit SYNTAX FcBbCredit
UNITS "buffers" UNITS "buffers"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of receive buffers which this port is "The maximum number of receive buffers that this port is
capable of making available for holding frames from attached capable of making available for holding frames from attached
Nx_Port(s)." Nx_Port(s)."
::= { fcmFxPortEntry 5 } ::= { fcmFxPortEntry 5 }
fcmFxPortCapBbCreditMin OBJECT-TYPE fcmFxPortCapBbCreditMin OBJECT-TYPE
SYNTAX FcBbCredit SYNTAX FcBbCredit
UNITS "buffers" UNITS "buffers"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum number of receive buffers which this port is "The minimum number of receive buffers that this port is
capable of making available for holding frames from attached capable of making available for holding frames from attached
Nx_Port(s)." Nx_Port(s)."
::= { fcmFxPortEntry 6 } ::= { fcmFxPortEntry 6 }
fcmFxPortCapDataFieldSizeMax OBJECT-TYPE fcmFxPortCapDataFieldSizeMax OBJECT-TYPE
SYNTAX FcDataFieldSize SYNTAX FcDataFieldSize
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 48, line 17 skipping to change at page 43, line 46
-- --
fcmISPortTable OBJECT-TYPE fcmISPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF FcmISPortEntry SYNTAX SEQUENCE OF FcmISPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Additional information about E_Ports, B_Ports, and any "Additional information about E_Ports, B_Ports, and any
other type of Fibre Channel port to which inter-switch links other type of Fibre Channel port to which inter-switch links
can be connected. This table will contain one entry for can be connected. This table will contain one entry for
each fcmPortTable entry which represents such a port." each fcmPortTable entry that represents such a port."
::= { fcmgmtObjects 8 } ::= { fcmgmtObjects 8 }
fcmISPortEntry OBJECT-TYPE fcmISPortEntry OBJECT-TYPE
SYNTAX FcmISPortEntry SYNTAX FcmISPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry contains information about a specific port "Each entry contains information about a specific port
connected to an inter-switch link." connected to an inter-switch link."
INDEX { ifIndex } INDEX { ifIndex }
skipping to change at page 48, line 41 skipping to change at page 44, line 26
SEQUENCE { SEQUENCE {
fcmISPortClassFCredit FcBbCredit, fcmISPortClassFCredit FcBbCredit,
fcmISPortClassFDataFieldSize FcDataFieldSize fcmISPortClassFDataFieldSize FcDataFieldSize
} }
fcmISPortClassFCredit OBJECT-TYPE fcmISPortClassFCredit OBJECT-TYPE
SYNTAX FcBbCredit SYNTAX FcBbCredit
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of Class F data frames which can be "The maximum number of Class F data frames that can be
transmitted by the inter-switch port without receipt of ACK transmitted by the inter-switch port without receipt of ACK
or Link_Response frames." or Link_Response frames."
::= { fcmISPortEntry 1 } ::= { fcmISPortEntry 1 }
fcmISPortClassFDataFieldSize OBJECT-TYPE fcmISPortClassFDataFieldSize OBJECT-TYPE
SYNTAX FcDataFieldSize SYNTAX FcDataFieldSize
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Receive Data Field Size which the inter-switch port has "The Receive Data Field Size that the inter-switch port has
agreed to support for Class F frames to/from this port. The agreed to support for Class F frames to/from this port. The
size specifies the largest Data Field Size for an FT_1 size specifies the largest Data Field Size for an FT_1
frame." frame."
::= { fcmISPortEntry 2 } ::= { fcmISPortEntry 2 }
--******************************** --********************************
-- The Fabric Login table -- The Fabric Login table
-- --
-- This table contains the information held by FC switches -- This table contains the information held by FC switches
-- about the Nx_Ports that are logged-in/attached to their
-- Fx_Ports -- Fx_Ports
fcmFLoginTable OBJECT-TYPE fcmFLoginTable OBJECT-TYPE
SYNTAX SEQUENCE OF FcmFLoginEntry SYNTAX SEQUENCE OF FcmFLoginEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table that contains one entry for each Nx_Port logged- "A table that contains one entry for each Nx_Port logged-
in/attached to a particular Fx_Port in the switch. Each in/attached to a particular Fx_Port in the switch. Each
entry contains the services parameters established during entry contains the services parameters established during
skipping to change at page 50, line 16 skipping to change at page 46, line 10
fcmFLoginClass2DataFieldSize FcDataFieldSize, fcmFLoginClass2DataFieldSize FcDataFieldSize,
fcmFLoginClass3SeqDelivAgreed TruthValue, fcmFLoginClass3SeqDelivAgreed TruthValue,
fcmFLoginClass3DataFieldSize FcDataFieldSize fcmFLoginClass3DataFieldSize FcDataFieldSize
} }
fcmFLoginNxPortIndex OBJECT-TYPE fcmFLoginNxPortIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer which uniquely identifies an Nx_Port "An arbitrary integer that uniquely identifies an Nx_Port
amongst all those attached to the Fx_Port indicated by amongst all those attached to the Fx_Port indicated by
ifIndex. ifIndex.
After a value of this object is assigned to a particular After a value of this object is assigned to a particular
Nx_Port, that value can be re-used when and only when it is Nx_Port, that value can be re-used when and only when it is
assigned to the same Nx_Port, or, after a reset of the value assigned to the same Nx_Port, or, after a reset of the value
of the relevant instance of ifCounterDiscontinuityTime." of the relevant instance of ifCounterDiscontinuityTime."
REFERENCE "The Interfaces Group MIB, RFC 2863, June 2000." REFERENCE "The Interfaces Group MIB, RFC 2863, June 2000."
::= { fcmFLoginEntry 1 } ::= { fcmFLoginEntry 1 }
skipping to change at page 51, line 24 skipping to change at page 47, line 14
transmitted to the attached Nx_Port. These buffers are for transmitted to the attached Nx_Port. These buffers are for
buffer-to-buffer flow control in the direction from Fx_Port buffer-to-buffer flow control in the direction from Fx_Port
to Nx_Port." to Nx_Port."
::= { fcmFLoginEntry 5 } ::= { fcmFLoginEntry 5 }
fcmFLoginClassesAgreed OBJECT-TYPE fcmFLoginClassesAgreed OBJECT-TYPE
SYNTAX FcClasses SYNTAX FcClasses
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Classes of Service which the Fx_Port has agreed to "The Classes of Service that the Fx_Port has agreed to
support for this Nx_Port." support for this Nx_Port."
::= { fcmFLoginEntry 6 } ::= { fcmFLoginEntry 6 }
fcmFLoginClass2SeqDelivAgreed OBJECT-TYPE fcmFLoginClass2SeqDelivAgreed OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of whether the Fx_Port has agreed to support "An indication of whether the Fx_Port has agreed to support
Class 2 sequential delivery for this Nx_Port. This is only Class 2 sequential delivery for this Nx_Port. This is only
meaningful if Class 2 service has been agreed." meaningful if Class 2 service has been agreed upon."
::= { fcmFLoginEntry 7 } ::= { fcmFLoginEntry 7 }
fcmFLoginClass2DataFieldSize OBJECT-TYPE fcmFLoginClass2DataFieldSize OBJECT-TYPE
SYNTAX FcDataFieldSize SYNTAX FcDataFieldSize
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Receive Data Field Size which the Fx_Port has agreed to "The Receive Data Field Size that the Fx_Port has agreed to
support for Class 2 frames to/from this Nx_Port. The size support for Class 2 frames to/from this Nx_Port. The size
specifies the largest Data Field Size for an FT_1 frame. specifies the largest Data Field Size for an FT_1 frame.
This is only meaningful if Class 2 service has been agreed." This is only meaningful if Class 2 service has been agreed
upon."
::= { fcmFLoginEntry 8 } ::= { fcmFLoginEntry 8 }
fcmFLoginClass3SeqDelivAgreed OBJECT-TYPE fcmFLoginClass3SeqDelivAgreed OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of whether the Fx_Port has agreed to support "An indication of whether the Fx_Port has agreed to support
Class 3 sequential delivery for this Nx_Port. This is only Class 3 sequential delivery for this Nx_Port. This is only
meaningful if Class 3 service has been agreed." meaningful if Class 3 service has been agreed upon."
::= { fcmFLoginEntry 9 } ::= { fcmFLoginEntry 9 }
fcmFLoginClass3DataFieldSize OBJECT-TYPE fcmFLoginClass3DataFieldSize OBJECT-TYPE
SYNTAX FcDataFieldSize SYNTAX FcDataFieldSize
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Receive Data Field Size which the Fx_Port has agreed to "The Receive Data Field Size that the Fx_Port has agreed to
support for Class 3 frames to/from this Nx_Port. The size support for Class 3 frames to/from this Nx_Port. The size
specifies the largest Data Field Size for an FT_1 frame. specifies the largest Data Field Size for an FT_1 frame.
This is only meaningful if Class 3 service has been agreed." This is only meaningful if Class 3 service has been agreed
upon."
::= { fcmFLoginEntry 10 } ::= { fcmFLoginEntry 10 }
--******************************** --********************************
-- The Link table -- The Link table
-- --
-- This table is intended to assist management applications -- This table is intended to assist management applications
-- in determining the topology of the network. The table -- in determining the topology of the network. The table
-- contains any recent information the known to the agent
-- about Fibre Channel links, not only those that terminate at
-- a local port but also any others for which information
-- is known. -- is known.
fcmLinkTable OBJECT-TYPE fcmLinkTable OBJECT-TYPE
SYNTAX SEQUENCE OF FcmLinkEntry SYNTAX SEQUENCE OF FcmLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing any Fibre Channel link information which "A table containing any Fibre Channel link information that
is known to local Fibre Channel managed instances. One end is known to local Fibre Channel managed instances. One end
of such a link is typically at a local port, but the table of such a link is typically at a local port, but the table
can also contain information on links for which neither end can also contain information on links for which neither end
is a local port. is a local port.
If one end of a link terminates locally, then that end is If one end of a link terminates locally, then that end is
termed 'end1'; the other end is termed 'end2'." termed 'end1'; the other end is termed 'end2'."
::= { fcmgmtObjects 10 } ::= { fcmgmtObjects 10 }
fcmLinkEntry OBJECT-TYPE fcmLinkEntry OBJECT-TYPE
SYNTAX FcmLinkEntry SYNTAX FcmLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry containing information which a particular Fibre "An entry containing information that a particular Fibre
Channel managed instance has about a Fibre Channel link. Channel managed instance has about a Fibre Channel link.
The two ends of the link are called 'end1' and 'end2'." The two ends of the link are called 'end1' and 'end2'."
INDEX { fcmInstanceIndex, fcmLinkIndex } INDEX { fcmInstanceIndex, fcmLinkIndex }
::= { fcmLinkTable 1 } ::= { fcmLinkTable 1 }
FcmLinkEntry ::= FcmLinkEntry ::=
SEQUENCE { SEQUENCE {
fcmLinkIndex Unsigned32, fcmLinkIndex Unsigned32,
fcmLinkEnd1NodeWwn FcNameIdOrZero, fcmLinkEnd1NodeWwn FcNameIdOrZero,
skipping to change at page 53, line 38 skipping to change at page 49, line 25
fcmLinkEnd2PortType FcPortType, fcmLinkEnd2PortType FcPortType,
fcmLinkEnd2UnitType FcUnitFunctions, fcmLinkEnd2UnitType FcUnitFunctions,
fcmLinkEnd2FcAddressId FcAddressIdOrZero fcmLinkEnd2FcAddressId FcAddressIdOrZero
} }
fcmLinkIndex OBJECT-TYPE fcmLinkIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer which uniquely identifies one link "An arbitrary integer that uniquely identifies one link
within the set of links about which a particular managed within the set of links about which a particular managed
instance has information." instance has information."
::= { fcmLinkEntry 1 } ::= { fcmLinkEntry 1 }
fcmLinkEnd1NodeWwn OBJECT-TYPE fcmLinkEnd1NodeWwn OBJECT-TYPE
SYNTAX FcNameIdOrZero SYNTAX FcNameIdOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The node name of end1, or the zero-length string if "The node name of end1, or the zero-length string if
skipping to change at page 57, line 24 skipping to change at page 52, line 24
DESCRIPTION DESCRIPTION
"Describes the requirements for compliance to this Fibre "Describes the requirements for compliance to this Fibre
Channel Management MIB." Channel Management MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { fcmInstanceBasicGroup, MANDATORY-GROUPS { fcmInstanceBasicGroup,
fcmPortBasicGroup, fcmPortBasicGroup,
fcmPortErrorsGroup } fcmPortErrorsGroup }
GROUP fcmPortStatsGroup GROUP fcmPortStatsGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for all systems which "This group is mandatory for all systems that
are able to support the Counter64 date type." are able to support the Counter64 date type."
GROUP fcmPortClass23StatsGroup GROUP fcmPortClass23StatsGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for systems which "This group is mandatory only for systems that
keep class-specific traffic statistics on Class 2 keep class-specific traffic statistics on Class 2
on Class 3 traffic and are able to support the and Class 3 traffic and are able to support the
Counter64 date type." Counter64 date type."
GROUP fcmPortClassFStatsGroup GROUP fcmPortClassFStatsGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for FC switches which "This group is mandatory only for FC switches that
keep statistics on Class F traffic." keep statistics on Class F traffic."
GROUP fcmPortLcStatsGroup GROUP fcmPortLcStatsGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for agents which can not "This group is mandatory only for agents that can not
support the Counter64 data type and/or need to provide support the Counter64 data type and/or need to provide
information accessible by SNMPv1 applications." information accessible by SNMPv1 applications."
GROUP fcmSwitchBasicGroup GROUP fcmSwitchBasicGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for Fibre Channel "This group is mandatory only for Fibre Channel
managed instances which manage Fibre Channel managed instances that manage Fibre Channel
switches." switches."
GROUP fcmSwitchPortGroup GROUP fcmSwitchPortGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for Fibre Channel "This group is mandatory only for Fibre Channel
managed instances which manage Fibre Channel managed instances that manage Fibre Channel
switches." switches."
GROUP fcmSwitchLoginGroup GROUP fcmSwitchLoginGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for Fibre Channel "This group is mandatory only for Fibre Channel
managed instances which manage Fibre Channel managed instances that manage Fibre Channel
switches." switches."
GROUP fcmLinkBasicGroup GROUP fcmLinkBasicGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional."
OBJECT fcmInstancePhysicalIndex OBJECT fcmInstancePhysicalIndex
SYNTAX Integer32 (0) SYNTAX Integer32 (0)
DESCRIPTION DESCRIPTION
"Implementation of a non-zero value is not required." "Implementation of a non-zero value is not required."
skipping to change at page 63, line 5 skipping to change at page 57, line 19
fcmLinkEnd2PhysPortNumber, fcmLinkEnd2PortWwn, fcmLinkEnd2PhysPortNumber, fcmLinkEnd2PortWwn,
fcmLinkEnd2AgentAddress, fcmLinkEnd2PortType, fcmLinkEnd2AgentAddress, fcmLinkEnd2PortType,
fcmLinkEnd2UnitType, fcmLinkEnd2FcAddressId } fcmLinkEnd2UnitType, fcmLinkEnd2FcAddressId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about Fibre Channel links." "Information about Fibre Channel links."
::= { fcmgmtGroups 11 } ::= { fcmgmtGroups 11 }
END END
7. Intellectual Property 7. Acknowledgements
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or
might not be available; neither does it represent that it has made any
effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and standards-
related documentation can be found in BCP-11. Copies of claims of
rights made available for publication and any assurances of licenses to
be made available, or the result of an attempt made to obtain a general
license or permission for the use of such proprietary rights by
implementors or users of this specification can be obtained from the
IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights
which may cover technology that may be required to practice this
standard. Please address the information to the IETF Executive
Director.
8. Acknowledgements
This memo is partly based on the information contained in the original
submission of the Fibre Channel Management Integration MIB to the IETF's
IPFC Working Group as draft-ietf-ipfc-fcmgmt-int-mib-0n.txt, and partly
based on RFC 2837.
Feedback has been incorporated into this document based on the comments
of the following: Sudhir Pendse, SimpleSoft; Steve Senum, Cisco Systems;
and Kha Sin Teow, Brocade.
9. Normative References
[RFC2434] This memo is partly based on the information contained in the
Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA original submission of the Fibre Channel Management Integration MIB
Considerations Section in RFCs", BCP:26, RFC 2434, October 1998. to the IETF's IPFC Working Group (now available as [MIB-FA]) and
obsoletes RFC 2837.
[RFC2578] Feedback has been incorporated into this document based on comments
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. from the following: Sudhir Pendse, SimpleSoft; Steve Senum, Cisco
and S. Waldbusser, "Structure of Management Information Version 2 Systems; and Kha Sin Teow, Brocade.
(SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] 8. Normative References
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.
and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC
2579, April 1999.
[RFC2580] [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. IANA Considerations Section in RFCs", BCP 26, RFC 2434,
and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC October 1998.
2580, April 1999.
[RFC2737] [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
McCloghrie, K., and A. Bierman, "Entity MIB (Version 2)", RFC 2737, "Structure of Management Information Version 2 (SMIv2)",
December 1999. STD 58, RFC 2578, April 1999.
[RFC2790] [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual
Waldbusser, S., and P. Grillo, "Host Resources MIB", RFC 2790, Conventions for SMIv2", STD 58, RFC 2579, April 1999.
March 2000.
[RFC2863] [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB", RFC "Conformance Statements for SMIv2", STD 58, RFC 2580, April
2863, Cisco Systems, Argon Networks, June 2000. 1999.
[RFC3411] [RFC2737] McCloghrie, K. and A. Bierman, "Entity MIB (Version 2)",
Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for RFC 2737, December 1999.
Describing Simple Network Management Protocol (SNMP) Management
Frameworks", STD 58, RFC 3411, December 2002.
[FC-AL] [RFC2790] Waldbusser, S. and P. Grillo, "Host Resources MIB", RFC
"Information Technology - Fibre Channel - Arbitrated Loop (FC-AL)", 2790, March 2000.
ANSI X3.272, 1996.
[FC-AL-2] [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
"Fibre Channel - Arbitrated Loop (FC-AL-2)", ANSI INCITS 332-1999, MIB", RFC 2863, June 2000.
1999.
[FC-BB] [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
"Fibre Channel - Backbone (FC-BB)" ANSI INCITS 342-2001, 2001. Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002.
[FCP] [FC-AL-2] "Fibre Channel - Arbitrated Loop (FC-AL-2)", ANSI INCITS
"SCSI-3 Fibre Channel Protocol (FCP)", ANSI X3.269, 1996. 332-1999, 1999.
[FC-FLA] [FC-BB] "Fibre Channel - Backbone (FC-BB)" ANSI INCITS 342-2001,
"Fibre Channel - Fabric Loop Attachment (FC-FLA)", ANSI INCITS 2001.
TR-20-1998, 1998.
[FC-FS] [FC-FS] "Fibre Channel - Framing and Signaling (FC-FS)" ANSI INCITS
"Fibre Channel - Framing and Signaling (FC-FS)" ANSI INCITS
373-2003, April 2003. 373-2003, April 2003.
[FC-GS-3] [FC-GS-3] "Fibre Channel - Generic Services - 3 (FC-GS-3)" ANSI
"Fibre Channel - Generic Services - 3 (FC-GS-3)" ANSI INCITS INCITS 348-2001, 2001.
348-2001, 2001.
[FC-MI] [FC-MI] "Fibre Channel - Methodologies for Interconnects Technical
"Fibre Channel - Methodologies for Interconnects Technical Report Report (FC-MI)" INCITS TR-30-2002, 2002.
(FC-MI)" INCITS TR-30-2002, 2002.
[FC-PH] [FC-PH] "Information Technology - Fibre Channel Physical and
"Information Technology - Fibre Channel Physical and Signaling Signaling Interface (FC-PH)", ANSI X3.230, 1994.
Interface (FC-PH)", ANSI X3.230, 1994.
[FC-SW] [FC-SW-3] "Fibre Channel - Switch Fabric - 3 (FC-SW-3)", ANSI INCITS
"Fibre Channel - Switch Fabric (FC-SW)", ANSI INCITS 321-1998, 384-2004, June 2004.
1998.
[FC-SW2] 9. Informative References
"Fibre Channel - Switch Fabric - 2 (FC-SW-2)", ANSI INCITS
355-2001, June 2001.
10. Informative References [RFC2741] Daniele, M., Wijnen, B., Ellison, M., and D. Francisco,
"Agent Extensibility (AgentX) Protocol Version 1", RFC
2741, January 2000.
[RFC2741] [RFC2837] Teow, K., "Definitions of Managed Objects for the Fabric
Daniele, M., Wijnen, B., Ellison, M., and D. Francisco. "Agent Element in Fibre Channel Standard", RFC 2837, May 2000.
Extensibility (AgentX) Protocol Version 1", RFC 2741, January 2000.
[RFC2837] [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
Teow, K., "Definitions of Managed Objects for the Fabric Element in "Introduction and Applicability Statements for Internet-
Fibre Channel Standard", RFC 2837, May 2000. Standard Management Framework", RFC 3410, December 2002.
[RFC3410] [RFC3433] Bierman, A., Romascanu, D., and K.C. Norseth, "Entity
Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Sensor Management Information Base", RFC 3433, December
Applicability Statements for Internet-Standard Management 2002.
Framework", RFC 3410, December 2002.
[WWN1] [MIB-FA] "INCITS Technical Report for Information Technology - Fibre
Snively, R., "New identifier formats based on IEEE registration", Channel - Management Information Base - FA (MIB-FA)",
http://standards.ieee.org/regauth/oui/tutorials/fibreformat.html, INCITS, TR-32-2003.
16 January 2001.
[WWN2] [WWN1] Snively, R., "New identifier formats based on IEEE
Snively, R., "Use of the IEEE Registration Authority assigned registration", http://standards.ieee.org/regauth/oui/
'company_id' with the ANSI X3.230 FC-PH Fibre Channel specification tutorials/fibreformat.html, 16 January 2001.
and its extensions",
http://standards.ieee.org/regauth/oui/tutorials/fibrecomp_id.html,
24 February 1997.
[SENSOR] [WWN2] Snively, R., "Use of the IEEE Registration Authority
Bierman, A., Romascanu, D., and KC Norseth, "Entity Sensor assigned 'company_id' with the ANSI X3.230 FC-PH Fibre
Management Information Base", Internet Draft, working draft, 16 Channel specification and its extensions",
October 2002. http://standards.ieee.org/regauth/oui/tutorials/
fibrecomp_id.html, 24 February 1997.
11. Security Considerations 10. Security Considerations
There are a number of management objects defined in this MIB that have a There are a number of management objects defined in this MIB that
MAX-ACCESS clause of read-write: have a MAX-ACCESS clause of read-write:
fcmInstanceTextName fcmInstanceTextName
fcmInstanceDescr fcmInstanceDescr
fcmSwitchDomainId fcmSwitchDomainId
fcmPortAdminType fcmPortAdminType
fcmPortAdminSpeed fcmPortAdminSpeed
fcmISPortClassFCredit fcmISPortClassFCredit
Such objects may be considered sensitive or vulnerable in some network Such objects may be considered sensitive or vulnerable in some
environments. For example, the ability to change network topology or network environments. For example, the ability to change network
network speed may afford an attacker the ability to obtain better topology or network speed may afford an attacker the ability to
performance at the expense of other network users; setting obtain better performance at the expense of other network users;
fcmSwitchDomainId to an invalid value could lead to denial of service in setting fcmSwitchDomainId to an invalid value could lead to denial of
some configurations. The support for SET operations in a non-secure service in some configurations. The support for SET operations in a
environment without proper protection can have a negative effect on non-secure environment without proper protection can have a negative
network operations. effect on network operations.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly to control even GET and/or NOTIFY access to these objects and possibly
even encrypt the values of these objects when sending them over the to even encrypt the values of these objects when sending them over
network via SNMP. In particular, these objects provide information on the network via SNMP. In particular, these objects provide
network topology: information on network topology:
fcmLinkEnd1NodeWwn fcmLinkEnd1NodeWwn
fcmLinkEnd1PhysPortNumber fcmLinkEnd1PhysPortNumber
fcmLinkEnd1PortWwn fcmLinkEnd1PortWwn
fcmLinkEnd2NodeWwn fcmLinkEnd2NodeWwn
fcmLinkEnd2PhysPortNumber fcmLinkEnd2PhysPortNumber
fcmLinkEnd2PortWwn fcmLinkEnd2PortWwn
fcmLinkEnd2AgentAddress fcmLinkEnd2AgentAddress
fcmLinkEnd2PortType fcmLinkEnd2PortType
fcmLinkEnd2UnitType fcmLinkEnd2UnitType
fcmLinkEnd2FcAddressId fcmLinkEnd2FcAddressId
SNMP versions prior to SNMPv3 did not include adequate security. Even SNMP versions prior to SNMPv3 did not include adequate security.
if the network itself is secure (for example by using IPSec), even then, Even if the network itself is secure (for example by using IPSec),
there is no control as to who on the secure network is allowed to access even then, there is no control as to who on the secure network is
and GET/SET (read/change/create/delete) the objects in this MIB module. allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementors consider the security features as It is RECOMMENDED that implementors consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), including provided by the SNMPv3 framework (see [RFC3410], section 8),
full support for the SNMPv3 cryptographic mechanisms (for authentication including full support for the SNMPv3 cryptographic mechanisms (for
and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Further, deployment of SNMP versions prior to SNMPv3 is NOT
Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
security. It is then a customer/operator responsibility to ensure that enable cryptographic security. It is then a customer/operator
the SNMP entity giving access to an instance of this MIB module is responsibility to ensure that the SNMP entity giving access to an
properly configured to give access to the objects only to those instance of this MIB module is properly configured to give access to
principals (users) that have legitimate rights to indeed GET or SET the objects only to those principals (users) that have legitimate
(change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
12. IANA Considerations 11. IANA Considerations
12.1. OID Assignment 11.1. OID Assignment
IANA is requested to make a MIB OID assignment under the transmission IANA has made a MIB OID assignment under the transmission branch.
branch. Specifically, for { transmission 56 } to be assigned as the OID Specifically, transmission 56 has been assigned as the OID for
for fcMgmtMIB. This sub-identifier is requested because this MIB fcMgmtMIB. This sub-identifier was requested because this MIB
contains the media-specific definitions which correspond to the ifType contains the media-specific definitions that correspond to the ifType
value of fibreChannel(56). value of fibreChannel(56).
12.2. FC Port Type Registry 11.2. FC Port Type Registry
IANA is requested to establish a registry for Fibre Channel Port Types. IANA has established a registry for Fibre Channel Port Types. The
The registry is to be split into disjoint subset ranges: registry is split into disjointed subset ranges:
1) a 'standard' range for Fibre Channel Port Types which have been 1) a 'standard' range for Fibre Channel Port Types that have been
standardized by the InterNational Committee for Information standardized by the InterNational Committee for Information
Technology Standards (INCITS)'s Technical Committee T11 (see Technology Standards (INCITS)'s Technical Committee T11. This
http://www.incits.org/tc_home/t11.htm and range will be subject to the 'Expert Review' and 'Specification
http://www.t11.org/index.htm). This range will be subject to the Required' policies described in [RFC2434], with the following
'Expert Review' and 'Specification Required' policies described in provisions:
[RFC2434], with the following provisions:
- the Expert Reviewer is to be appointed by the IESG. - the Expert Reviewer is to be appointed by the IESG.
- the Expert Reviewer shall obtain approval (or rejection) from - the Expert Reviewer shall obtain approval (or rejection) from
INCITS Technical Committee T11 via the chair of that Committee. INCITS Technical Committee T11 via the chair of that Committee.
Rejected values shall not be added to the registry. Rejected values shall not be added to the registry.
- if the addition is approved, the Expert shall advise IANA of how - if the addition is approved, the Expert shall advise IANA of
to record the reference to the T11 specification document which how to record the reference to the T11 specification document
describes the newly added port type(s), and which is considered that describes the newly added port type(s), and that is
to be the "other permanent and readily available reference" considered to be the "other permanent and readily available
required by [RFC2434]. reference" required by [RFC2434].
The initial assignments in the 'standard' range will be as follows: The initial assignments in the 'standard' range will be as follows:
Assigned Assigned
Value Type Meaning Value Type Meaning
-------- ------ ------- -------- ------ -------
1 unknown for use when the type is not known, 1 unknown for use when the type is not known,
or is "unidentified" as specified in or is "unidentified" as specified in
section 5.1.2.10 of [FC-GS-3] section 5.1.2.10 of [FC-GS-3]
2 other used for types without assigned values 2 other used for types without assigned values
skipping to change at page 68, line 41 skipping to change at page 61, line 35
4 N_Port see [FC-FS] 4 N_Port see [FC-FS]
5 NL_Port see [FC-FS] 5 NL_Port see [FC-FS]
6 F_Port see [FC-FS] 6 F_Port see [FC-FS]
7 FL_Port see [FC-FS] 7 FL_Port see [FC-FS]
8 E_Port see [FC-FS] 8 E_Port see [FC-FS]
9 B_Port see [FC-FS] 9 B_Port see [FC-FS]
10 G_Port see [FC-SW-3] 10 G_Port see [FC-SW-3]
11 GL_Port see [FC-SW-3] 11 GL_Port see [FC-SW-3]
12 F/NL_Port see [FC-AL-2] 12 F/NL_Port see [FC-AL-2]
It is suggested that the above range can be extended up to a maximum The above range extends up to a maximum of 9,999.
of 9,999.
2) a range which is assigned under the "Private Use" policy described in 2) a range assigned under the "Private Use" policy described in
[RFC2434] and is for values intended for private use by one party or [RFC2434] for values intended for private use by one party or
among mutually consenting parties. It is suggested that values in among mutually consenting parties.
this range extend from 10,000 to 99,999. IANA is instructed not to Values in this range extend from 10,000 to 99,999. IANA will not
make any allocations from this range. make any allocations from this range.
3) values larger than 99,999 be RESERVED. 3) values larger than 99,999 are RESERVED.
13. Comparison to draft-ietf-ipfc-fcmgmt-int-mib-07.txt 12. Comparison to the Fibre Channel Management Integration MIB
13.1. Problems with draft-ietf-ipfc-fcmgmt-int-mib-07.txt 12.1. Problems with the Fibre Channel Management Integration MIB
The Fibre Channel Management Integration MIB had the following major The Fibre Channel Management Integration MIB [MIB-FA] had the
problems: following major problems:
- It wasn't formatted using SMIv2, which is mandatory. - It wasn't formatted using SMIv2, which is mandatory.
- The MIB seemed to have been defined with the notion that it would - The MIB seemed to have been defined with the notion that it would
be the only MIB that a Fibre Channel product will require. The be the only MIB that a Fibre Channel product will require. The
notion of an agent implementing just a single MIB was abandoned by notion of an agent implementing just a single MIB was abandoned by
the IETF in 1992 as being non-scaleable. Rather, a Fibre Channel the IETF in 1992 as being non-scalable. Rather, a Fibre Channel
MIB needed to be another MIB in the continuing series of MIBs MIB needed to be another MIB in the continuing series of MIBs
defined by the IETF, and thus, it needed to be consistent with its defined by the IETF, and thus, it needed to be consistent with its
predecessors. In other words, there are existing MIBs which all predecessors. In other words, there are existing MIBs that all
SNMP agents must support, even if the support of Fibre Channel SNMP agents must support, even if the support of Fibre Channel
interfaces is the only functionality that they have. Thus, it was interfaces is the only functionality that they have. Thus, it was
essential that the Fibre Channel Integration MIB contained only essential that the Fibre Channel Integration MIB contained only
objects for information which is specific to Fibre Channel. All objects for information that is specific to Fibre Channel. All
objects relevant to non-Fibre Channel environments needed to be objects relevant to non-Fibre Channel environments needed to be
removed. This issue applied to a large fraction of the objects removed. This issue applied to a large fraction of the objects
defined in the MIB. defined in the MIB.
- The MIB had some but not complete overlap in functionality with RFC - The MIB had some but not complete overlap in functionality with
2837. RFC 2837.
- Every SNMP agent must implement the ifTable. The ifTable counters - Every SNMP agent must implement the ifTable. The ifTable counters
are the MIB objects most well-used by administrators in SNMP are the MIB objects most well-used by administrators in SNMP
management. SNMP agents need to implement a row in the ifTable for management. SNMP agents need to implement a row in the ifTable
each of their network interfaces, including their Fibre Channel for each of their network interfaces, including their Fibre
interfaces. The IF-MIB requires a media-specific MIB to specify Channel interfaces. The IF-MIB requires a media-specific MIB to
how that type of interface uses the ifTable (see section 4 in RFC specify how that type of interface uses the ifTable (see section 4
2863). RFC 2837 doesn't do that, and nor did the Fibre Channel in RFC 2863). [RFC2837] doesn't do that, nor did the Fibre
Integration MIB. Channel Integration MIB.
- It incorrectly used the OCTET STRING syntax (instead of Counter32 - It incorrectly used the OCTET STRING syntax (instead of Counter32
or Counter64) for counters. or Counter64) for counters.
13.2. Detailed Changes 12.2. Detailed Changes
13.2.1. Removal of Sensor-related objects 12.2.1. Removal of Sensor-Related Objects
Information about sensors is not specific to Fibre Channel, and Information about sensors is not specific to Fibre Channel, and
therefore should not be in this MIB. (At the time of writing, the the therefore should not be in this MIB. (At the time of writing, the
IETF's ENTITY MIB Working Group has produced a first draft of a Sensor IETF's ENTITY MIB Working Group has produced a first draft of a
MIB, see [SENSOR].) This removed the need for: Sensor MIB, see [RFC3433].) This removed the need for:
connUnitSensorTable (and all its contents) connUnitSensorTable (and all its contents)
connUnitNumSensors connUnitNumSensors
connUnitSensorStatusChange connUnitSensorStatusChange
13.2.2. Removal of Trap-registration objects 12.2.2. Removal of Trap-registration Objects
Information about registering "traps" is not specific to Fibre Channel, Information about registering "traps" is not specific to Fibre
and therefore should not be in this MIB. (For similar functionality, Channel, and therefore should not be in this MIB. (For similar
see SNMP-NOTIFICATION-MIB and SNMP-TARGET-MIB in RFC 2573). This functionality, see SNMP-NOTIFICATION-MIB and SNMP-TARGET-MIB in RFC
removed the need for: 2573). This removed the need for:
trapMaxClients trapMaxClients
trapClientCount trapClientCount
trapRegTable (and all its contents) trapRegTable (and all its contents)
13.2.3. Removal of Event-related objects 12.2.3. Removal of Event-Related Objects
Information about generic events is not specific to Fibre Channel, and Information about generic events is not specific to Fibre Channel,
therefore should not be in this MIB. (For similar functionality, see and therefore should not be in this MIB. (For similar functionality,
the Event group in RFC 2819 and the Notification Log MIB in RFC 3014; see the Event group in RFC 2819 and the Notification Log MIB in RFC
the SNMP-NOTIFICATION-MIB provides for the filtering of notifications.) 3014; the SNMP-NOTIFICATION-MIB provides for the filtering of
This removed the need for: notifications.) This removed the need for:
connUnitEventTable (and all its contents) connUnitEventTable (and all its contents)
connUnitEventFilter connUnitEventFilter
connUnitNumEvents connUnitNumEvents
connUnitMaxEvents connUnitMaxEvents
connUnitEventCurrID connUnitEventCurrID
connUnitEventTrap connUnitEventTrap
13.2.4. Removal of inventory-related information 12.2.4. Removal of Inventory-Related Information
Aspects of hardware (physical) components are represented in the Entity Aspects of hardware (physical) components are represented in the
MIB (RFC 2737); aspects of software modules are represented in the Host Entity MIB (RFC 2737); aspects of software modules are represented in
Resources MIB (RFC 2790). Two new objects provide indexing from this the Host Resources MIB (RFC 2790). Two new objects provide indexing
MIB into those MIBs: one having the value of PhysicalIndex (or zero) and from this MIB into those MIBs: one having the value of PhysicalIndex
the other having the value of hrSWInstalledIndex (or zero). These (or zero) and the other having the value of hrSWInstalledIndex (or
replaced the need for: zero). These replaced the need for:
connUnitNumports connUnitNumports
connUnitRevsTable (and all its contents) connUnitRevsTable (and all its contents)
connUnitNumRevs connUnitNumRevs
connUnitPortRevision connUnitPortRevision
connUnitPortVendor connUnitPortVendor
connUnitProduct connUnitProduct
connUnitInfo connUnitInfo
connUnitSn connUnitSn
connUnitModuleId connUnitModuleId
connUnitVendorId connUnitVendorId
connUnitDeletedTrap connUnitDeletedTrap
13.2.5. Removal of revision numbers 12.2.5. Removal of Revision Numbers
The forward/backward compatibility rules of how to evolve MIBs are The forward/backward compatibility rules of how to evolve MIBs are
designed such that MIBs do not have revision numbers. This removed the designed such that MIBs do not have revision numbers. This removed
need for: the need for:
revisionNumber revisionNumber
13.2.6. Removal of other not FC-specific information 12.2.6. Removal of Other Not FC-Specific Information
Other information was removed because it was not specific to Fibre Other information was removed because it was not specific to Fibre
Channel: Channel:
systemURL systemURL
statusChangeTime statusChangeTime
configurationChangeTime configurationChangeTime
connUnitUrl connUnitUrl
connUnitUpTime connUnitUpTime
connUnitState connUnitState
connUnitContact connUnitContact
connUnitLocation connUnitLocation
connUnitProxyMaster connUnitProxyMaster
connUnitControl connUnitControl
connUnitStatus connUnitStatus
connUnitStatusChange connUnitStatusChange
13.2.7. Clean-up of ambiguous/obsolete definitions 12.2.7. Clean-up of Ambiguous/Obsolete Definitions
Some information in the FC Management integration was obsolete or Some information in the FC Management integration was obsolete or
ambiguous: ambiguous:
statusChangeTime (obsolete) statusChangeTime (obsolete)
configurationChangeTime (obsolete) configurationChangeTime (obsolete)
connUnitTableChangeTime (obsolete) connUnitTableChangeTime (obsolete)
connUnitStatusChangeTime (obsolete) connUnitStatusChangeTime (obsolete)
connUnitConfigurationChangeTime (obsolete) connUnitConfigurationChangeTime (obsolete)
connUnitNumZones (obsolete) connUnitNumZones (obsolete)
connUnitZoneTable (referenced but not defined) connUnitZoneTable (referenced but not defined)
connUnitLinkCurrIndex (badly defined) connUnitLinkCurrIndex (badly defined)
13.2.8. Use of an ifTable entry 12.2.8. Use of an ifTable Entry
The following objects were removed because they duplicated existing IF- The following objects were removed because they duplicated existing
MIB objects: IF-MIB objects:
redundant object existing object(s) redundant object existing object(s)
---------------- ------------------ ---------------- ------------------
connUnitPortStatCountError ifInErrors & ifOutErrors connUnitPortStatCountError ifInErrors & ifOutErrors
connUnitPortStatCountTxObjects ifOutUcastPkts & connUnitPortStatCountTxObjects ifOutUcastPkts &
ifHCOutUcastPkts ifHCOutUcastPkts
connUnitPortStatCountRxObjects ifInUcastPkts & connUnitPortStatCountRxObjects ifInUcastPkts &
ifHCInUcastPkts ifHCInUcastPkts
connUnitPortStatCountTxElements ifOutOctets & connUnitPortStatCountTxElements ifOutOctets &
ifHCOutOctets ifHCOutOctets
skipping to change at page 74, line 13 skipping to change at page 65, line 38
connUnitPortFCId ifPhysAddress connUnitPortFCId ifPhysAddress
connUnitPortControl ifAdminStatus connUnitPortControl ifAdminStatus
connUnitPortState ifAdminStatus connUnitPortState ifAdminStatus
connUnitPortHWState ifOperStatus connUnitPortHWState ifOperStatus
connUnitPortStatus ifOperStatus connUnitPortStatus ifOperStatus
connUnitPortName ifAlias connUnitPortName ifAlias
connUnitPortStatObject ifSpecific connUnitPortStatObject ifSpecific
connUnitNumports ifNumber connUnitNumports ifNumber
connUnitPortStatusChange linkUp/linkDown connUnitPortStatusChange linkUp/linkDown
13.2.9. Removed because of AgentX difficulty 12.2.9. Removed Because of AgentX Difficulty
An AgentX environment [RFC2741] consists of a master agent and several An AgentX environment [RFC2741] consists of a master agent and
sub-agents. It is not difficult to implement the same MIB in several several sub-agents. It is not difficult to implement the same MIB in
such sub-agents if all of the MIB's tables have a common index variable several such sub-agents if all of the MIB's tables have a common
as the first auxiliary object in their INDEX clauses. However, any index variable as the first auxiliary object in their INDEX clauses.
scalars which the MIB contains pose a problem for the AgentX However, any scalars that the MIB contains pose a problem for the
environment. All the (remaining) scalars were therefore removed: AgentX environment. All the (remaining) scalars were therefore
removed:
revisionNumber revisionNumber
uNumber uNumber
systemURL systemURL
13.2.10. FC Management Instance 12.2.10. FC Management Instance
The term "connectivity unit" was changed to "FC management instance". The term "connectivity unit" was changed to "FC management instance".
The term "connectivity unit" was not properly defined in draft-ietf- The term "connectivity unit" was not properly defined in [MIB-FA],
ipfc-fcmgmt-int-mib-07.txt, and its usage provided a confused mixture of and its usage provided a confused mixture of indications to the
indications to the implementor: implementor:
- the definition of FcUnitType suggested it was functional; - the definition of FcUnitType suggested it was functional;
- the definition of uNumber suggested it was physical; - the definition of uNumber suggested it was physical;
- the definition of connUnitProduct suggested it was a vendor's product;
- etc.
The common implementation strategy for "connectivity unit" was whatever - the definition of connUnitProduct suggested it was a vendor's
grouping was easiest in providing access to the management product;
functionality. (One such grouping accommodates a single SNMP agent
having multiple AgentX [RFC2741] sub-agents, each supporting a separate
implementation of the MIB.)
In fact, this scenario is not new; in practice, a "connectivity unit" - etc.
will have the same semantics as a management "instance" in other MIBs,
e.g., the IPS WG's own iSCSI MIB. For this MIB, its meaning is: "a
separable managed instance of Fibre Channel functionality". Given this
definition, then "FC management instance" is a better name because it is The common implementation strategy for the "connectivity unit" was
more accurate and more representative of the definition, than is which ever grouping provided access to the management functionality
"connectivity unit". the easiest. (One such grouping accommodates a single SNMP agent
having multiple AgentX [RFC2741] sub-agents, each supporting a
separate implementation of the MIB.)
13.2.11. Counter Syntax In fact, this scenario is not new; in practice, a "connectivity unit"
will have the same semantics as a management "instance" in other
MIBs, e.g., the IPS WG's own iSCSI MIB. For this MIB, its meaning
is: "a separable managed instance of Fibre Channel functionality".
Given this definition, the "FC management instance" is a better name
because it is more accurate and more representative of the definition
than is "connectivity unit".
All packet and octet counters have been changed to be Counter64's (but 12.2.11. Counter Syntax
Counter32 versions of them are also included for use by old agents).
The error counters have been changed to Counter32's. (In the probably
impossible, and at most improbable, circumstances that the rate of
occurrence of errors, even on a 10Gbs Fibre Channel interface, might
wrap faster than a hour, the fact that errors are occurring will almost
certainly be apparent from other MIB objects.)
13.2.12. Obsolete/Little-Used Fibre Channel features All packet and octet counters have been changed to be Counter64's
(but Counter32 versions of them are also included for use by old
agents). The error counters have been changed to Counter32's. (In
the probably impossible, and at most improbable, circumstances that
the rate of occurrence of errors, even on a 10Gbs Fibre Channel
interface, might wrap faster than an hour, the fact that errors are
occurring will almost certainly be apparent from other MIB objects.)
Information relating to Fibre Channel features which are obsolete or not 12.2.12. Obsolete/Little-Used Fibre Channel Features
widely-implemented has been deleted. (For more information, see section
6.2.1 and section 6.2.2 of [FC-MI].)
Information relating to Fibre Channel features that are obsolete or
not widely-implemented has been deleted. (For more information, see
section 6.2.1 and section 6.2.2 of [FC-MI].)
- Class 1 service, - Class 1 service,
- Intermix Mode, - Intermix Mode,
- Stacked Conn Mode. - Stacked Conn Mode.
- PH version numbers - PH version numbers
Note that with support for Class 1 service being deleted, only class 2 Note that with support for Class 1 service being deleted, only class
now needs F_BSY, F_RJT, P_BSY and P_RJT counters, and thus they no 2 now needs F_BSY, F_RJT, P_BSY, and P_RJT counters, and thus they no
longer need to be counted for all classes as well as for class 2, and longer need to be counted for all classes as well as for class 2, and
therefore these objects: therefore the following objects have been deleted:
connUnitPortStatCountFBSYFrames connUnitPortStatCountFBSYFrames
connUnitPortStatCountPBSYFrames connUnitPortStatCountPBSYFrames
connUnitPortStatCountFRJTFrames connUnitPortStatCountFRJTFrames
connUnitPortStatCountPRJTFrames connUnitPortStatCountPRJTFrames
have been deleted. 12.3. Name Server Objects
13.3. Name Server objects
A table of Name Server information was present in draft-ietf-ipfc- A table of Name Server information was present in
fcmgmt-int-mib-07.txt. That information is not currently represented in the Fibre Channel Management Integration MIB [MIB-FA].
this MIB, because this MIB is already quite large, and a set of Name That information is not currently represented in this MIB
Server objects are expected to be defined in a separate (new) MIB. because this MIB is already quite large,
and a set of Name Server objects are expected to be
defined in a separate (new) MIB.
13.4. Additional objects 12.4. Additional Objects
Support for Class F traffic, including 32-bit octet and frame counters, Support for Class F traffic, including 32-bit octet and frame
has been added. counters, has been added.
14. Comparison to RFC 2837 13. Comparison to RFC 2837
This MIB is a superset of RFC 2837, except for the following: This MIB is a superset of RFC 2837, except for the following:
- the fcFeClass1AccountingGroup group is obsolete, - the fcFeClass1AccountingGroup group is obsolete,
- fcFxPortConnectedNxPort, fcFxPortFcphVersionHigh, - fcFxPortConnectedNxPort, fcFxPortFcphVersionHigh,
fcFxPortFcphVersionLow, fcFxPortFcphVersionAgreed, fcFxPortFcphVersionLow, fcFxPortFcphVersionAgreed,
fcFxPortStackedConnModeAgreed, fcFxPortIntermixSuppAgreed, fcFxPortStackedConnModeAgreed, fcFxPortIntermixSuppAgreed,
fcFxPortCapStackedConnMode and fcFxPortCapIntermix are obsolete, fcFxPortCapStackedConnMode, and fcFxPortCapIntermix are obsolete,
- fcFxPortBbCredit and fcFxPortRxBufSize are per attached Nx_Port, - fcFxPortBbCredit and fcFxPortRxBufSize are per attached Nx_Port,
- fcFxPortBbCreditAvailable is ephemeral, - fcFxPortBbCreditAvailable is ephemeral,
- fcFeModuleTable is mostly contained in the entPhysicalTable, - fcFeModuleTable is mostly contained in the entPhysicalTable,
- fcFxPortPhysAdminStatus, fcFxPortPhysOperStatus, and - fcFxPortPhysAdminStatus, fcFxPortPhysOperStatus, and
fcFxPortPhysLastChange have equivalents in the ifTable. fcFxPortPhysLastChange have equivalents in the ifTable.
15. Author's Address Author's Address
Keith McCloghrie Keith McCloghrie
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA USA 95134 San Jose, CA USA 95134
Phone: +1 408-526-5260 Phone: +1 408-526-5260
Email: kzm@cisco.com EMail: kzm@cisco.com
16. Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005).
This document and translations of it may be copied and furnished to This document is subject to the rights, licenses and restrictions
others, and derivative works that comment on or otherwise explain it or contained in BCP 78, and except as set forth therein, the authors
assist in its implementation may be prepared, copied, published and retain all their rights.
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in
which case the procedures for copyrights defined in the Internet
Standards process must be followed, or as required to translate it into
languages other than English.
The limited permissions granted above are perpetual and will not be This document and the information contained herein are provided on an
revoked by the Internet Society or its successors or assigns. "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
This document and the information contained herein is provided on an "AS Intellectual Property
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
"Copyright (C) The Internet Society (2004). This document is subject to The IETF takes no position regarding the validity or scope of any
the rights, licenses and restrictions contained in BCP 78, and except as Intellectual Property Rights or other rights that might be claimed to
set forth therein, the authors retain all their rights." pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
"This document and the information contained herein are provided on an Copies of IPR disclosures made to the IETF Secretariat and any
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR assurances of licenses to be made available, or the result of an
IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, The IETF invites any interested party to bring to its attention any
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE copyrights, patents or patent applications, or other proprietary
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED rights that may cover technology that may be required to implement
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/