draft-ietf-ips-fcmgmt-mib-00.txt   draft-ietf-ips-fcmgmt-mib-01.txt 
Internet Draft Keith McCloghrie Internet Draft Keith McCloghrie
Cisco Systems, Inc Cisco Systems
22 January 2002 28 February 2002
Fibre Channel Management MIB Fibre Channel Management MIB
draft-ietf-ips-fcmgmt-mib-00.txt draft-ietf-ips-fcmgmt-mib-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026 [RFC2026]. provisions of Section 10 of RFC2026 [RFC2026].
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts. may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
time. It is inappropriate to use Internet- Drafts as reference material time. It is inappropriate to use Internet- Drafts as reference material
or to cite them other than as "work in progress". or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Distribution of this document is unlimited. Please send comments to Distribution of this document is unlimited. Please send comments to
authors. author.
1. Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
2. 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 informantion related to In particular, it describes managed objects for informantion related
Fibre Channel. to Fibre Channel.
3. Table of Contents Table of Contents
1 Copyright Notice ................................................ 1 1 The SNMP Network Management Framework ........................... 3
2 Abstract ........................................................ 2 2 Change Log ...................................................... 4
3 Table of Contents ............................................... 2 3 Short Overview of Fibre Channel ................................. 4
4 The SNMP Network Management Framework ........................... 3 4 MIB Overview .................................................... 5
5 Overview ........................................................ 4 5 Relationship to Other MIBs ...................................... 7
6 MIB Overview .................................................... 5 5.1 The Interfaces Group MIB ...................................... 7
7 Relationship to Other MIBs ...................................... 6 5.2 Entity MIB .................................................... 10
7.1 The Interfaces Group MIB ...................................... 6 5.3 Host Resources MIB ............................................ 11
7.2 Entity MIB .................................................... 10 6 Definitions ..................................................... 12
7.3 Host Resources MIB ............................................ 10 7 Intellectual Property ........................................... 61
8 Definitions ..................................................... 11 8 Acknowledgements ................................................ 61
9 Intellectual Property ........................................... 51 9 References ...................................................... 61
10 Acknowledgements ............................................... 51 10 Security Considerations ........................................ 65
11 References ..................................................... 51 11 Comparison to draft-ietf-ipfc-fcmgmt-int-mib-07.txt ............ 67
12 Security Considerations ........................................ 55 11.1 Problems with draft-ietf-ipfc-fcmgmt-int-mib-07.txt .......... 67
13 Comparison to draft-ietf-ipfc-fcmgmt-int-mib-07.txt ............ 57 11.2 Detailed Changes ............................................. 68
13.1 Problems with draft-ietf-ipfc-fcmgmt-int-mib-07.txt .......... 57 11.2.1 Removal of Sensor-related objects .......................... 68
13.2 Detailed Changes ............................................. 58 11.2.2 Removal of Trap-registration objects ....................... 68
13.2.1 Removal of Sensor-related objects .......................... 58 11.2.3 Removal of Event-related objects ........................... 68
13.2.2 Removal of Trap-registration objects ....................... 58 11.2.4 Removal of inventory-related information ................... 69
13.2.3 Removal of Event-related objects ........................... 58 11.2.5 Removal of revision numbers ................................ 69
13.2.4 Removal of inventory-related information ................... 59 11.2.6 Removal of other not FC-specific information ............... 69
13.2.5 Removal of revision numbers ................................ 59 11.2.7 Clean-up of ambiguous/obsolete definitions ................. 70
13.2.6 Removal of other not FC-specific information ............... 59 11.2.8 Use of an ifTable entry .................................... 70
13.2.7 Clean-up of ambiguous/obsolete definitions ................. 60 11.2.9 Removed because of AgentX difficulty ....................... 71
13.2.8 Use of an ifTable entry .................................... 60 11.2.10 FC Management Instance .................................... 71
13.2.9 Removed because of AgentX difficulty ....................... 61 11.2.11 Counter Syntax ............................................ 72
13.2.10 FC Management Instance .................................... 61 11.2.12 Obsolete/Little-Used Fibre Channel features ............... 72
13.2.11 Counter Syntax ............................................ 62 11.3 Name Server objects .......................................... 72
13.2.12 Obsolete Fibre Channel features ........................... 62 11.4 Additional objects ........................................... 73
13.3 Name Server objects .......................................... 62 12 Comparison to RFC 2837 ......................................... 74
14 Comparison to RFC 2837 ......................................... 63 13 Author's Address ............................................... 75
15 Author's Address ............................................... 64 14 Full Copyright Statement ....................................... 75
16 Full Copyright Statement ....................................... 64
4. The SNMP Network Management Framework 1. The SNMP Network Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [RFC2571]. o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
RFC 1155 [RFC1155], RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. RFC 1155 [RFC1155], RFC 1212 [RFC1212] and RFC 1215 [RFC1215].
skipping to change at page 4, line 9 skipping to change at page 4, line 9
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
5. Overview 2. Change Log
This section to be deleted before publication as an RFC.
2.1. Initial version: draft-ietf-ips-fcmgmt-mib-00.txt
Initial version derived from draft-ietf-ipfc-fcmgmt-int-mib-07.txt and
RFC 2837, and published on 22 January 2002.
2.2. Changes made in draft-ietf-ips-fcmgmt-mib-01.txt
- support added for Class F traffic.
- the description of Class 1 changed to "not widely-implemented"
(instead of "obsolete"), and a reference to FC-MI added.
- Counter32 objects added in order to support old SNMPv1-only systems
which cannot support standard Counter64 objects.
3. Short Overview of 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, Fibre Channel is an interconnection of multiple
skipping to change at page 5, line 5 skipping to change at page 5, line 17
E_Port on a switch; a B_Port provides a subset of E_Port functionality. 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 most
ports, have globally-unique names. These globally-unique names are ports, have globally-unique names. These globally-unique names are
typically formatted as World Wide Names (WWNs). More information on typically formatted as World Wide Names (WWNs). More information on
WWNs can be found in [WWN1] and [WWN2]. WWNs are expected to be WWNs can be found in [WWN1] and [WWN2]. WWNs are expected to be
persistent across agent and unit resets. Fibre Channel frames contain persistent across agent and unit resets. Fibre Channel frames contain
24-bit addresses identifers which identify the frame's source and 24-bit addresses identifers which identify the frame's source and
destination ports. destination ports.
6. 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 the
implementation(s). For example, one such grouping accommodates a single implementation(s). For example, one such grouping accommodates a single
SNMP agent having multiple AgentX [RFC2741] sub-agents, with each sub- SNMP agent having multiple AgentX [RFC2741] sub-agents, with each sub-
agent implementing a different Fibre Channel management instance. agent implementing a different Fibre Channel management instance.
This MIB contains eight MIB groups, as follows. This MIB contains eleven MIB groups, as follows.
6.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.
6.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.
6.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, its is a part, the type of port, the classes of service it supports, its
transmitter and connector types, and the higher level protocols it transmitter and connector types, and the higher level protocols 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 (see
below). The tables relating to ports in this MIB are indexed by the below). The tables relating to ports in this MIB are indexed by the
port's value of ifIndex. port's value of ifIndex.
6.4. The fcmPortStatsGroup group 4.4. The fcmPortStatsGroup group
This group contains traffic statistics for Fibre Channel ports, This group contains traffic statistics, which are not specific to any
including frame and octet counters for class 2 and class 3 traffic, and particular class of service, for Fibre Channel ports.
counters of busy and reject frames.
6.5. The fcmPortErrorsGroup group 4.5. The fcmPortClass23StatsGroup group
This group contains traffic statistics which are specific to Class 2 or
Class 3 traffic on Fibre Channel ports, including class-specific frame
and octet counters and counters of busy and reject frames.
4.6. The fcmPortLcStatsGroup group
Some of the statistics in the fcmPortClass23StatsGroup can increase
rapidly enough to warrant them being defined using the Counter64 syntax.
However, some old SNMP systems do not (yet) support Counter64 objects.
Thus, this group defines low-capacity (Counter32-based) equivalents for
the Counter64-based statistics in the fcmPortClass23StatsGroup group.
4.7. The fcmPortClassFStatsGroup group
This group contains traffic statistics which are specific to Class F
traffic on the E_Ports of a Fibre Channel switch.
4.8. The fcmPortErrorsGroup group
This group contains counters of various error conditions which can occur This group contains counters of various error conditions which can occur
on Fibre Channel ports." on Fibre Channel ports."
6.6. The fcmSwitchPortGroup group 4.9. The fcmSwitchPortGroup group
This group contains information about a port on a Fibre Channel switch, This group contains information about ports on a Fibre Channel switch.
including its timeout values, its hold-time, and its capabilities in For an Fx_Port, it includes the port's timeout values, its hold-time,
terms of maximum and minimum buffer-to-buffer credit allocations, and its capabilities in terms of maximum and minimum buffer-to-buffer
maximum and minimum data field size, and support for class 2 and class 3 credit allocations, maximum and minimum data field size, and support for
sequenced delivery. class 2 and class 3 sequenced delivery. For an E_Port, it includes the
buffer-to-buffer credit allocation and data field size.
6.7. 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, about
its attached/logged-in Nx_Ports and the service parameters which have its attached/logged-in Nx_Ports and the service parameters which have
been agreed with them. been agreed with them.
6.8. 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, about Fibre Channel links, including links which
terminate locally. terminate locally.
7. 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 Fibre
Channel Management Integration MIB which was originally submitted as an Channel Management Integration MIB which was originally submitted as an
Internet Draft to the IETF's IPFC Working Group as draft-ietf-ipfc- Internet Draft to the IETF's IPFC Working Group as draft-ietf-ipfc-
fcmgmt-int-mib-0n.txt. fcmgmt-int-mib-0n.txt.
7.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 its
own row in the ifTable, and that row will contain the generic 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 particular
type of interface media, should be defined in a media-specific MIB. type of interface media, should be defined in a media-specific MIB.
This MIB is the media-specific MIB for Fibre Channel ports/interfaces. This MIB is the media-specific MIB for Fibre Channel ports/interfaces.
skipping to change at page 7, line 4 skipping to change at page 7, line 37
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 its
own row in the ifTable, and that row will contain the generic 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 particular
type of interface media, should be defined in a media-specific MIB. type of interface media, should be defined in a media-specific MIB.
This MIB is the media-specific MIB for Fibre Channel ports/interfaces. 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.
7.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 defined
for interface sub-layers, and for those multiple entries to be arranged for interface sub-layers, and for those multiple entries to be arranged
in a stack. 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 on
top of it, nor underneath it. top of it, nor underneath it.
7.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.
7.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.
7.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.
7.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 the
octets contained in frames between the Start-of-Frame and End-of-Frame octets contained in frames between the Start-of-Frame and End-of-Frame
delimiters (excluding the delimiters). delimiters (excluding the delimiters).
7.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 their
generic definitions in [RFC2863]. (RFC 2863 takes precedence over these generic definitions in [RFC2863]. (RFC 2863 takes precedence over these
guidelines in the event of any conflict.) guidelines in the event of any conflict.)
Object Guidelines Object Guidelines
ifType 56 ifType 56
skipping to change at page 10, line 14 skipping to change at page 10, line 34
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 to an operational speed, this object
SHOULD reflect the maximum speed supported SHOULD reflect the maximum speed supported
by the interface. by 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'.
7.2. Entity MIB 5.2. Entity MIB
The Entity MIB [RFC2737] contains information about individual physical The Entity MIB [RFC2737] contains information about individual physical
components and any hierarchical relationship which may exist between components and any hierarchical relationship which may exist between
them. Any Fibre Channel management instance with a relationship to a them. Any Fibre Channel management instance with a relationship to a
physical component (or to a hierarchy of physical components) will have physical component (or to a hierarchy of physical components) will have
its value of the fcmInstancePhysicalIndex object contain a pointer to its value of the fcmInstancePhysicalIndex object contain a pointer to
the relevant row in the Entity MIB. If there is no correspondence to a the relevant row in the Entity MIB. If there is no correspondence to a
physical component (or said component does not have a row in the Entity physical component (or said component does not have a row in the Entity
MIB), then the value of fcmInstancePhysicalIndex is zero. (Note that an MIB), then the value of fcmInstancePhysicalIndex is zero. (Note that an
implementation is not required to support a non-zero value of implementation is not required to support a non-zero value of
fcmInstancePhysicalIndex.) fcmInstancePhysicalIndex.)
7.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 in
the Host Resources MIB. If there is no correspondence to a software the Host Resources MIB. If there is no correspondence to a software
module (or said software module does not has a row in the Host Resources module (or said software module does not has a row in the Host Resources
MIB), then the value of fcmInstanceSoftwareIndex is zero. (Note that an MIB), then the value of fcmInstanceSoftwareIndex is zero. (Note that an
implementation is not required to support a non-zero value of implementation is not required to support a non-zero value of
fcmInstanceSoftwareIndex.) fcmInstanceSoftwareIndex.)
8. 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, experimental Integer32, Unsigned32, Counter32, Counter64, experimental
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 "200201170000Z" LAST-UPDATED "200202280000Z"
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."
REVISION "200201170000Z" REVISION "200202280000Z"
DESCRIPTION DESCRIPTION
"Initial version of the Fibre Channel Management MIB "Initial version of the Fibre Channel Management MIB
module." module."
::= { experimental 999999 } -- unassigned ::= { experimental 999999 } -- unassigned
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 }
skipping to change at page 13, line 24 skipping to change at page 14, line 24
DESCRIPTION DESCRIPTION
"The buffer-to-buffer credit of an FC port." "The buffer-to-buffer credit of an FC port."
SYNTAX Integer32 (0..32767) SYNTAX Integer32 (0..32767)
FcBbCreditModel ::= TEXTUAL-CONVENTION FcBbCreditModel ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The buffer-to-buffer credit model of an Fx_Port." "The buffer-to-buffer credit model of an Fx_Port."
SYNTAX INTEGER { regular(1), alternate (2) } SYNTAX INTEGER { regular(1), alternate (2) }
FcRxDataFieldSize ::= TEXTUAL-CONVENTION FcDataFieldSize ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The receive data field size of 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, indicates the function(s) are unknown." set, indicates the function(s) are unknown."
SYNTAX BITS { SYNTAX BITS {
other(0), -- none of the following other(0), -- none of the following
skipping to change at page 26, line 7 skipping to change at page 27, line 7
fcmPortClass2RxFrjtFrames Counter64, fcmPortClass2RxFrjtFrames Counter64,
fcmPortClass2RxPrjtFrames Counter64, fcmPortClass2RxPrjtFrames Counter64,
fcmPortClass2TxFbsyFrames Counter64, fcmPortClass2TxFbsyFrames Counter64,
fcmPortClass2TxPbsyFrames Counter64, fcmPortClass2TxPbsyFrames Counter64,
fcmPortClass2TxFrjtFrames Counter64, fcmPortClass2TxFrjtFrames Counter64,
fcmPortClass2TxPrjtFrames Counter64, fcmPortClass2TxPrjtFrames Counter64,
fcmPortClass3RxFrames Counter64, fcmPortClass3RxFrames Counter64,
fcmPortClass3RxOctets Counter64, fcmPortClass3RxOctets Counter64,
fcmPortClass3TxFrames Counter64, fcmPortClass3TxFrames Counter64,
fcmPortClass3TxOctets Counter64, fcmPortClass3TxOctets Counter64,
fcmPortClass3Discards Counter64 fcmPortClass3Discards Counter64,
fcmPortClassFRxFrames Counter32,
fcmPortClassFRxOctets Counter32,
fcmPortClassFTxFrames Counter32,
fcmPortClassFTxOctets Counter32,
fcmPortClassFDiscards Counter32
} }
fcmPortBBCreditZeros OBJECT-TYPE fcmPortBBCreditZeros OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of transitions in/out of the buffer-to-buffer "The number of transitions in/out of the buffer-to-buffer
credit zero state. The other side is not providing any credit zero state. The other side is not providing any
credit." credit."
skipping to change at page 30, line 23 skipping to change at page 31, line 29
fcmPortClass3Discards OBJECT-TYPE fcmPortClass3Discards OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Class 3 frames that were discarded upon "The number of Class 3 frames that were discarded upon
reception at this port." reception at this port."
::= { fcmPortStatsEntry 20 } ::= { fcmPortStatsEntry 20 }
fcmPortClassFRxFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Class F frames received at this port."
::= { fcmPortStatsEntry 21 }
fcmPortClassFRxOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets contained in Class F frames received
at this port."
::= { fcmPortStatsEntry 22 }
fcmPortClassFTxFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Class F frames transmitted out of this port."
::= { fcmPortStatsEntry 23 }
fcmPortClassFTxOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets contained in Class F frames
transmitted out of this port."
::= { fcmPortStatsEntry 24 }
fcmPortClassFDiscards OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Class F frames that were discarded upon
reception at this port."
::= { fcmPortStatsEntry 25 }
--********************************
-- Port Low-capacity Statistics
--
-- these are Counter32 "low-capacity" counters for systems
-- which do not support Counter64's
fcmPortLcStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF FcmPortLcStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of Counter32-based statistics which are a shadow of
the Counter64 statistics in the fcmPortStatsTable, for
systems which do not support Counter64."
::= { fcmgmtObjects 4 }
fcmPortLcStatsEntry OBJECT-TYPE
SYNTAX FcmPortLcStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry containing low-capacity (i.e., based on Counter32)
statistics for a Fibre Channel port."
AUGMENTS { fcmPortEntry }
::= { fcmPortLcStatsTable 1 }
FcmPortLcStatsEntry ::=
SEQUENCE {
fcmPortLcBBCreditZeros Counter32,
fcmPortLcFullInputBuffers Counter32,
fcmPortLcClass2RxFrames Counter32,
fcmPortLcClass2RxOctets Counter32,
fcmPortLcClass2TxFrames Counter32,
fcmPortLcClass2TxOctets Counter32,
fcmPortLcClass2Discards Counter32,
fcmPortLcClass2RxFbsyFrames Counter32,
fcmPortLcClass2RxPbsyFrames Counter32,
fcmPortLcClass2RxFrjtFrames Counter32,
fcmPortLcClass2RxPrjtFrames Counter32,
fcmPortLcClass2TxFbsyFrames Counter32,
fcmPortLcClass2TxPbsyFrames Counter32,
fcmPortLcClass2TxFrjtFrames Counter32,
fcmPortLcClass2TxPrjtFrames Counter32,
fcmPortLcClass3RxFrames Counter32,
fcmPortLcClass3RxOctets Counter32,
fcmPortLcClass3TxFrames Counter32,
fcmPortLcClass3TxOctets Counter32,
fcmPortLcClass3Discards Counter32
}
fcmPortLcBBCreditZeros OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of transitions in/out of the buffer-to-buffer
credit zero state. The other side is not providing any
credit."
::= { fcmPortLcStatsEntry 1 }
fcmPortLcFullInputBuffers OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of occurrences when all input buffers of a port
were full and outbound buffer-to-buffer credit transitioned
to zero, i.e., there became no credit to provide to other
side."
::= { fcmPortLcStatsEntry 2 }
fcmPortLcClass2RxFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Class 2 frames received at this port."
::= { fcmPortLcStatsEntry 3 }
fcmPortLcClass2RxOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets contained in Class 2 frames received
at this port."
::= { fcmPortLcStatsEntry 4 }
fcmPortLcClass2TxFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Class 2 frames transmitted out of this port."
::= { fcmPortLcStatsEntry 5 }
fcmPortLcClass2TxOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets contained in Class 2 frames
transmitted out of this port."
::= { fcmPortLcStatsEntry 6 }
fcmPortLcClass2Discards OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Class 2 frames that were discarded upon
reception at this port."
::= { fcmPortLcStatsEntry 7 }
fcmPortLcClass2RxFbsyFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times that F_BSY was returned to this port as
a result of a Class 2 frame that could not be delivered to
the other end of the link. This can occur when either the
fabric or the destination port is temporarily busy. Note
that this counter will never increment for an F_Port."
::= { fcmPortLcStatsEntry 8 }
fcmPortLcClass2RxPbsyFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times that P_BSY was returned to this port as
a result of a Class 2 frame that could not be delivered to
the other end of the link. This can occur when the
destination port is temporarily busy."
::= { fcmPortLcStatsEntry 9 }
fcmPortLcClass2RxFrjtFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times that F_RJT was returned to this port as
a result of a Class 2 frame that was rejected by the fabric.
Note that this counter will never increment for an F_Port."
::= { fcmPortLcStatsEntry 10 }
fcmPortLcClass2RxPrjtFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times that P_RJT was returned to this port as
a result of a Class 2 frame that was rejected at the
destination N_Port."
::= { fcmPortLcStatsEntry 11 }
fcmPortLcClass2TxFbsyFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times that F_BSY was generated by this port
as a result of a Class 2 frame that could not be delivered
because either the Fabric or the destination port was
temporarily busy. Note that this counter will never
increment for an N_Port."
::= { fcmPortLcStatsEntry 12 }
fcmPortLcClass2TxPbsyFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times that P_BSY was generated by this port
as a result of a Class 2 frame that could not be delivered
because the destination port was temporarily busy. Note
that this counter will never increment for an F_Port."
::= { fcmPortLcStatsEntry 13 }
fcmPortLcClass2TxFrjtFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times that F_RJT was generated by this port
as a result of a Class 2 frame being rejected by the fabric.
Note that this counter will never increment for an N_Port."
::= { fcmPortLcStatsEntry 14 }
fcmPortLcClass2TxPrjtFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times that P_RJT was generated by this port
as a result of a Class 2 frame being rejected at the
destination N_Port. Note that this counter will never
increment for an F_Port."
::= { fcmPortLcStatsEntry 15 }
fcmPortLcClass3RxFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Class 3 frames received at this port."
::= { fcmPortLcStatsEntry 16 }
fcmPortLcClass3RxOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets contained in Class 3 frames received
at this port."
::= { fcmPortLcStatsEntry 17 }
fcmPortLcClass3TxFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Class 3 frames transmitted out of this port."
::= { fcmPortLcStatsEntry 18 }
fcmPortLcClass3TxOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of octets contained in Class 3 frames
transmitted out of this port."
::= { fcmPortLcStatsEntry 19 }
fcmPortLcClass3Discards OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Class 3 frames that were discarded upon
reception at this port."
::= { fcmPortLcStatsEntry 20 }
--******************************** --********************************
-- Port Error Counters -- Port Error Counters
-- --
fcmPortErrorsTable OBJECT-TYPE fcmPortErrorsTable OBJECT-TYPE
SYNTAX SEQUENCE OF FcmPortErrorsEntry SYNTAX SEQUENCE OF FcmPortErrorsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Error counters for Fibre Channel ports." "Error counters for Fibre Channel ports."
skipping to change at page 36, line 11 skipping to change at page 43, line 37
::= { fcmFxPortTable 1 } ::= { fcmFxPortTable 1 }
FcmFxPortEntry ::= FcmFxPortEntry ::=
SEQUENCE { SEQUENCE {
fcmFxPortRatov MilliSeconds, fcmFxPortRatov MilliSeconds,
fcmFxPortEdtov MilliSeconds, fcmFxPortEdtov MilliSeconds,
fcmFxPortRttov MilliSeconds, fcmFxPortRttov MilliSeconds,
fcmFxPortHoldTime MicroSeconds, fcmFxPortHoldTime MicroSeconds,
fcmFxPortCapBbCreditMax FcBbCredit, fcmFxPortCapBbCreditMax FcBbCredit,
fcmFxPortCapBbCreditMin FcBbCredit, fcmFxPortCapBbCreditMin FcBbCredit,
fcmFxPortCapRxDataFieldSizeMax FcRxDataFieldSize, fcmFxPortCapDataFieldSizeMax FcDataFieldSize,
fcmFxPortCapRxDataFieldSizeMin FcRxDataFieldSize, fcmFxPortCapDataFieldSizeMin FcDataFieldSize,
fcmFxPortCapClass2SeqDeliv TruthValue, fcmFxPortCapClass2SeqDeliv TruthValue,
fcmFxPortCapClass3SeqDeliv TruthValue, fcmFxPortCapClass3SeqDeliv TruthValue,
fcmFxPortCapHoldTimeMax MicroSeconds, fcmFxPortCapHoldTimeMax MicroSeconds,
fcmFxPortCapHoldTimeMin MicroSeconds fcmFxPortCapHoldTimeMin MicroSeconds
} }
fcmFxPortRatov OBJECT-TYPE fcmFxPortRatov OBJECT-TYPE
SYNTAX MilliSeconds SYNTAX MilliSeconds
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 37, line 45 skipping to change at page 45, line 25
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 which 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 }
fcmFxPortCapRxDataFieldSizeMax OBJECT-TYPE fcmFxPortCapDataFieldSizeMax OBJECT-TYPE
SYNTAX FcRxDataFieldSize SYNTAX FcDataFieldSize
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum size in bytes of the Data Field in a frame that "The maximum size in bytes of the Data Field in a frame that
this Fx_Port is capable of receiving from an attached this Fx_Port is capable of receiving from an attached
Nx_Port." Nx_Port."
::= { fcmFxPortEntry 7 } ::= { fcmFxPortEntry 7 }
fcmFxPortCapRxDataFieldSizeMin OBJECT-TYPE fcmFxPortCapDataFieldSizeMin OBJECT-TYPE
SYNTAX FcRxDataFieldSize SYNTAX FcDataFieldSize
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum size in bytes of the Data Field in a frame that "The minimum size in bytes of the Data Field in a frame that
this Fx_Port is capable of receiving from an attached this Fx_Port is capable of receiving from an attached
Nx_Port." Nx_Port."
::= { fcmFxPortEntry 8 } ::= { fcmFxPortEntry 8 }
fcmFxPortCapClass2SeqDeliv OBJECT-TYPE fcmFxPortCapClass2SeqDeliv OBJECT-TYPE
skipping to change at page 39, line 16 skipping to change at page 47, line 6
SYNTAX MicroSeconds SYNTAX MicroSeconds
UNITS "microseconds" UNITS "microseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum holding time that this Fx_Port is capable of "The minimum holding time that this Fx_Port is capable of
supporting." supporting."
::= { fcmFxPortEntry 12 } ::= { fcmFxPortEntry 12 }
--******************************** --********************************
-- The Fibre Channel E_Port Table
--
fcmEPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF FcmEPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Additional information about Fibre Channel E_Ports. This
table will contain one entry for each fcmPortTable entry
which represents an E_Port."
::= { fcmgmtObjects 7 }
fcmEPortEntry OBJECT-TYPE
SYNTAX FcmEPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry contains information for about a specific
E_Port."
INDEX { ifIndex }
::= { fcmEPortTable 1 }
FcmEPortEntry ::=
SEQUENCE {
fcmEPortClassFCredit FcBbCredit,
fcmEPortClassFDataFieldSize FcDataFieldSize
}
fcmEPortClassFCredit OBJECT-TYPE
SYNTAX FcBbCredit
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum number of Class F data frames which can be
transmitted by the E_Port without receipt of ACK or
Link_Response frames."
::= { fcmEPortEntry 1 }
fcmEPortClassFDataFieldSize OBJECT-TYPE
SYNTAX FcDataFieldSize
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Receive Data Field Size which the E_Port has agreed to
support for Class F frames to/from this port. The size
specifies the largest Data Field Size for an FT_1 frame."
::= { fcmEPortEntry 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 which are logged-in/attached to their -- about the Nx_Ports which 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
the most recent Fabric Login, explicit or implicit. Note the most recent Fabric Login, explicit or implicit. Note
that an Fx_Port may have one or more Nx_Ports attached to that an Fx_Port may have one or more Nx_Ports attached to
it." it."
::= { fcmgmtObjects 7 } ::= { fcmgmtObjects 8 }
fcmFLoginEntry OBJECT-TYPE fcmFLoginEntry OBJECT-TYPE
SYNTAX FcmFLoginEntry SYNTAX FcmFLoginEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry containing service parameters established from a "An entry containing service parameters established from a
successful Fabric Login." successful Fabric Login."
INDEX { ifIndex, fcmFLoginNxPortIndex } INDEX { ifIndex, fcmFLoginNxPortIndex }
::= { fcmFLoginTable 1 } ::= { fcmFLoginTable 1 }
FcmFLoginEntry ::= FcmFLoginEntry ::=
SEQUENCE { SEQUENCE {
fcmFLoginNxPortIndex Unsigned32, fcmFLoginNxPortIndex Unsigned32,
fcmFLoginPortWwn FcNameIdOrZero, fcmFLoginPortWwn FcNameIdOrZero,
fcmFLoginNodeWwn FcNameIdOrZero, fcmFLoginNodeWwn FcNameIdOrZero,
fcmFLoginBbCreditModel FcBbCreditModel, fcmFLoginBbCreditModel FcBbCreditModel,
fcmFLoginBbCredit FcBbCredit, fcmFLoginBbCredit FcBbCredit,
fcmFLoginClassesAgreed FcClasses, fcmFLoginClassesAgreed FcClasses,
fcmFLoginClass2SeqDelivAgreed TruthValue, fcmFLoginClass2SeqDelivAgreed TruthValue,
fcmFLoginClass2RxDataFieldSize FcRxDataFieldSize, fcmFLoginClass2DataFieldSize FcDataFieldSize,
fcmFLoginClass3SeqDelivAgreed TruthValue, fcmFLoginClass3SeqDelivAgreed TruthValue,
fcmFLoginClass3RxDataFieldSize FcRxDataFieldSize fcmFLoginClass3DataFieldSize FcDataFieldSize
} }
fcmFLoginNxPortIndex OBJECT-TYPE fcmFLoginNxPortIndex OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
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 which 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."
skipping to change at page 41, line 35 skipping to change at page 50, line 30
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."
::= { fcmFLoginEntry 7 } ::= { fcmFLoginEntry 7 }
fcmFLoginClass2RxDataFieldSize OBJECT-TYPE fcmFLoginClass2DataFieldSize OBJECT-TYPE
SYNTAX FcRxDataFieldSize 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 which 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."
::= { 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."
::= { fcmFLoginEntry 9 } ::= { fcmFLoginEntry 9 }
fcmFLoginClass3RxDataFieldSize OBJECT-TYPE fcmFLoginClass3DataFieldSize OBJECT-TYPE
SYNTAX FcRxDataFieldSize 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 which 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."
::= { fcmFLoginEntry 10 } ::= { fcmFLoginEntry 10 }
--******************************** --********************************
skipping to change at page 42, line 44 skipping to change at page 51, line 40
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing any Fibre Channel link information which "A table containing any Fibre Channel link information which
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 8 } ::= { fcmgmtObjects 9 }
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 which 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'."
skipping to change at page 46, line 24 skipping to change at page 55, 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,
fcmPortStatsGroup, fcmPortStatsGroup,
fcmPortErrorsGroup, fcmPortErrorsGroup,
fcmLinkBasicGroup } fcmLinkBasicGroup }
GROUP fcmPortClassStatsGroup GROUP fcmPortClass23StatsGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for systems which "This group is mandatory only for systems which
keep traffic statistics on individual classes of keep class-specific traffic statistics on Class 2
service." on Class 3 traffic."
GROUP fcmPortClassFStatsGroup
DESCRIPTION
"This group is mandatory only for FC switches which
keep statistics on Class F traffic."
GROUP fcmPortLcStatsGroup
DESCRIPTION
"This group is mandatory only for agents which
do not provide Counter64 counters."
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 which 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
skipping to change at page 48, line 46 skipping to change at page 57, line 46
::= { fcmgmtGroups 3 } ::= { fcmgmtGroups 3 }
fcmPortStatsGroup OBJECT-GROUP fcmPortStatsGroup OBJECT-GROUP
OBJECTS { fcmPortBBCreditZeros, fcmPortFullInputBuffers } OBJECTS { fcmPortBBCreditZeros, fcmPortFullInputBuffers }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Traffic statistics, which are not specific to any one class "Traffic statistics, which are not specific to any one class
of service, for Fibre Channel ports." of service, for Fibre Channel ports."
::= { fcmgmtGroups 4 } ::= { fcmgmtGroups 4 }
fcmPortClassStatsGroup OBJECT-GROUP fcmPortClass23StatsGroup OBJECT-GROUP
OBJECTS { fcmPortClass2RxFrames, fcmPortClass2RxOctets, OBJECTS { fcmPortClass2RxFrames, fcmPortClass2RxOctets,
fcmPortClass2TxFrames, fcmPortClass2TxOctets, fcmPortClass2TxFrames, fcmPortClass2TxOctets,
fcmPortClass2Discards, fcmPortClass2RxFbsyFrames, fcmPortClass2Discards, fcmPortClass2RxFbsyFrames,
fcmPortClass2RxPbsyFrames, fcmPortClass2RxPbsyFrames,
fcmPortClass2RxFrjtFrames, fcmPortClass2RxFrjtFrames,
fcmPortClass2RxPrjtFrames, fcmPortClass2RxPrjtFrames,
fcmPortClass2TxFbsyFrames, fcmPortClass2TxFbsyFrames,
fcmPortClass2TxPbsyFrames, fcmPortClass2TxPbsyFrames,
fcmPortClass2TxFrjtFrames, fcmPortClass2TxFrjtFrames,
fcmPortClass2TxPrjtFrames, fcmPortClass3RxFrames, fcmPortClass2TxPrjtFrames, fcmPortClass3RxFrames,
fcmPortClass3RxOctets, fcmPortClass3TxFrames, fcmPortClass3RxOctets, fcmPortClass3TxFrames,
fcmPortClass3TxOctets, fcmPortClass3Discards } fcmPortClass3TxOctets, fcmPortClass3Discards }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Traffic statistics for particular classes of service on "Traffic statistics for Class 2 and Class 3 traffic on Fibre
Fibre Channel ports." Channel ports."
::= { fcmgmtGroups 5 } ::= { fcmgmtGroups 5 }
fcmPortClassFStatsGroup OBJECT-GROUP
OBJECTS { fcmPortClassFRxFrames,
fcmPortClassFRxOctets,
fcmPortClassFTxFrames,
fcmPortClassFTxOctets,
fcmPortClassFDiscards }
STATUS current
DESCRIPTION
"Traffic statistics for Class F traffic on Fibre Channel
ports."
::= { fcmgmtGroups 6 }
fcmPortLcStatsGroup OBJECT-GROUP
OBJECTS { fcmPortLcBBCreditZeros, fcmPortLcFullInputBuffers,
fcmPortLcClass2RxFrames, fcmPortLcClass2RxOctets,
fcmPortLcClass2TxFrames, fcmPortLcClass2TxOctets,
fcmPortLcClass2Discards, fcmPortLcClass3Discards,
fcmPortLcClass3RxFrames, fcmPortLcClass3RxOctets,
fcmPortLcClass3TxFrames, fcmPortLcClass3TxOctets,
fcmPortLcClass2RxFbsyFrames,
fcmPortLcClass2RxPbsyFrames,
fcmPortLcClass2RxFrjtFrames,
fcmPortLcClass2RxPrjtFrames,
fcmPortLcClass2TxFbsyFrames,
fcmPortLcClass2TxPbsyFrames,
fcmPortLcClass2TxFrjtFrames,
fcmPortLcClass2TxPrjtFrames
STATUS current
DESCRIPTION
"Low-capacity (32-bit) statistics for Fibre Channel ports."
::= { fcmgmtGroups 7 }
fcmPortErrorsGroup OBJECT-GROUP fcmPortErrorsGroup OBJECT-GROUP
OBJECTS { fcmPortRxLinkResets, fcmPortTxLinkResets, OBJECTS { fcmPortRxLinkResets, fcmPortTxLinkResets,
fcmPortLinkResets, fcmPortRxOfflineSequences, fcmPortLinkResets, fcmPortRxOfflineSequences,
fcmPortTxOfflineSequences, fcmPortLinkFailures, fcmPortTxOfflineSequences, fcmPortLinkFailures,
fcmPortLossofSynchs, fcmPortLossofSignals, fcmPortLossofSynchs, fcmPortLossofSignals,
fcmPortPrimSeqProtocolErrors, fcmPortInvalidTxWords, fcmPortPrimSeqProtocolErrors, fcmPortInvalidTxWords,
fcmPortInvalidCRCs, fcmPortInvalidOrderedSets, fcmPortInvalidCRCs, fcmPortInvalidOrderedSets,
fcmPortFrameTooLongs, fcmPortTruncatedFrames, fcmPortFrameTooLongs, fcmPortTruncatedFrames,
fcmPortAddressErrors, fcmPortDelimiterErrors, fcmPortAddressErrors, fcmPortDelimiterErrors,
fcmPortEncodingDisparityErrors, fcmPortEncodingDisparityErrors,
fcmPortOtherErrors } fcmPortOtherErrors }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Error statistics for Fibre Channel ports." "Error statistics for Fibre Channel ports."
::= { fcmgmtGroups 6 } ::= { fcmgmtGroups 8 }
fcmSwitchPortGroup OBJECT-GROUP fcmSwitchPortGroup OBJECT-GROUP
OBJECTS { fcmFxPortRatov, fcmFxPortEdtov, fcmFxPortRttov, OBJECTS { fcmFxPortRatov, fcmFxPortEdtov, fcmFxPortRttov,
fcmFxPortHoldTime, fcmFxPortCapBbCreditMax, fcmFxPortHoldTime, fcmFxPortCapBbCreditMax,
fcmFxPortCapBbCreditMin, fcmFxPortCapBbCreditMin,
fcmFxPortCapRxDataFieldSizeMax, fcmFxPortCapDataFieldSizeMax,
fcmFxPortCapRxDataFieldSizeMin, fcmFxPortCapDataFieldSizeMin,
fcmFxPortCapClass2SeqDeliv, fcmFxPortCapClass2SeqDeliv,
fcmFxPortCapClass3SeqDeliv, fcmFxPortCapClass3SeqDeliv,
fcmFxPortCapHoldTimeMax, fcmFxPortCapHoldTimeMax,
fcmFxPortCapHoldTimeMin } fcmFxPortCapHoldTimeMin,
fcmEPortClassFCredit,
fcmEPortClassFDataFieldSize, }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about ports on a Fibre Channel switch." "Information about ports on a Fibre Channel switch."
::= { fcmgmtGroups 7 } ::= { fcmgmtGroups 9 }
fcmSwitchLoginGroup OBJECT-GROUP fcmSwitchLoginGroup OBJECT-GROUP
OBJECTS { fcmFLoginPortWwn, fcmFLoginNodeWwn, OBJECTS { fcmFLoginPortWwn, fcmFLoginNodeWwn,
fcmFLoginBbCreditModel, fcmFLoginBbCredit, fcmFLoginBbCreditModel, fcmFLoginBbCredit,
fcmFLoginClassesAgreed, fcmFLoginClassesAgreed,
fcmFLoginClass2SeqDelivAgreed, fcmFLoginClass2SeqDelivAgreed,
fcmFLoginClass2RxDataFieldSize, fcmFLoginClass2DataFieldSize,
fcmFLoginClass3SeqDelivAgreed, fcmFLoginClass3SeqDelivAgreed,
fcmFLoginClass3RxDataFieldSize } fcmFLoginClass3DataFieldSize }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information known to a Fibre Channel switch about "Information known to a Fibre Channel switch about
attached/logged-in Nx_Ports." attached/logged-in Nx_Ports."
::= { fcmgmtGroups 8 } ::= { fcmgmtGroups 10 }
fcmLinkBasicGroup OBJECT-GROUP fcmLinkBasicGroup OBJECT-GROUP
OBJECTS { fcmLinkEnd1NodeWwn , fcmLinkEnd1PhysPortNumber, OBJECTS { fcmLinkEnd1NodeWwn , fcmLinkEnd1PhysPortNumber,
fcmLinkEnd1PortWwn, fcmLinkEnd2NodeWwn , fcmLinkEnd1PortWwn, fcmLinkEnd2NodeWwn ,
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 9 } ::= { fcmgmtGroups 11 }
END END
9. Intellectual Property 7. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or 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 might not be available; neither does it represent that it has made any
effort to identify any such rights. Information on the IETF's effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and standards- procedures with respect to rights in standards-track and standards-
related documentation can be found in BCP-11. Copies of claims of related documentation can be found in BCP-11. Copies of claims of
rights made available for publication and any assurances of licenses to rights made available for publication and any assurances of licenses to
skipping to change at page 51, line 27 skipping to change at page 61, line 27
license or permission for the use of such proprietary rights by license or permission for the use of such proprietary rights by
implementors or users of this specification can be obtained from the implementors or users of this specification can be obtained from the
IETF Secretariat. IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights copyrights, patents or patent applications, or other proprietary rights
which may cover technology that may be required to practice this which may cover technology that may be required to practice this
standard. Please address the information to the IETF Executive standard. Please address the information to the IETF Executive
Director. Director.
10. Acknowledgements 8. Acknowledgements
This memo is partly based on the information contained in the original This memo is partly based on the information contained in the original
submission of the Fibre Channel Management Integration MIB to the IETF's 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 IPFC Working Group as draft-ietf-ipfc-fcmgmt-int-mib-0n.txt, and partly
based on RFC 2837. based on RFC 2837.
Feedback has been incorporated into this document based on the comments Feedback has been incorporated into this document based on the comments
of the following: Sudhir Pendse, SimpleSoft; Steve Senum, Cisco Systems; of the following: Sudhir Pendse, SimpleSoft; Steve Senum, Cisco Systems;
and Kha Sin Teow, Brocade. and Kha Sin Teow, Brocade.
11. References 9. References
[RFC1155] [RFC1155]
Rose, M., and K. McCloghrie, "Structure and Identification of Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155, Management Information for TCP/IP-based Internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990. Performance Systems International, Hughes LAN Systems, May 1990.
[RFC1157] [RFC1157]
Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network
Management Protocol", RFC 1157, SNMP Research, Performance Systems Management Protocol", RFC 1157, SNMP Research, Performance Systems
International, Performance Systems International, MIT Laboratory International, Performance Systems International, MIT Laboratory
skipping to change at page 54, line 44 skipping to change at page 64, line 44
"SCSI-3 Fibre Channel Protocol (FCP)", ANSI X3.269, 1996. "SCSI-3 Fibre Channel Protocol (FCP)", ANSI X3.269, 1996.
[FC-FLA] [FC-FLA]
"Fibre Channel - Fabric Loop Attachment (FC-FLA)", ANSI NCITS "Fibre Channel - Fabric Loop Attachment (FC-FLA)", ANSI NCITS
TR-20-1998, 1998. TR-20-1998, 1998.
[FC-GS-3] [FC-GS-3]
"Fibre Channel - Generic Services - 3 (FC-GS-3)" NCITS xxx-200x, "Fibre Channel - Generic Services - 3 (FC-GS-3)" NCITS xxx-200x,
T11/Project 1356-D/Rev 7.01, 28 November 2000. T11/Project 1356-D/Rev 7.01, 28 November 2000.
[FC-MI]
"Fibre Channel - Methodologies for Interconnects Technical Report
(FC-MI)" T11/Project 1377-DT/Rev 1.92, 4 December 2001.
[FC-PH] [FC-PH]
"Information Technology - Fibre Channel Physical and Signaling "Information Technology - Fibre Channel Physical and Signaling
Interface (FC-PH)", ANSI X3.230, 1994. Interface (FC-PH)", ANSI X3.230, 1994.
[FC-SW] [FC-SW]
"Fibre Channel - Switch Fabric (FC-SW)", ANSI NCITS 321-1998, 1998. "Fibre Channel - Switch Fabric (FC-SW)", ANSI NCITS 321-1998, 1998.
[FC-SW2] [FC-SW2]
"Fibre Channel - Switch Fabric - 2 (FC-SW-2)", T11/Project "Fibre Channel - Switch Fabric - 2 (FC-SW-2)", T11/Project
1305D/Rev 5.3, ANSI NCITS xxx-200x, June 2001. 1305D/Rev 5.3, ANSI NCITS xxx-200x, June 2001.
skipping to change at page 55, line 26 skipping to change at page 65, line 30
'company_id' with the ANSI X3.230 FC-PH Fibre Channel specification 'company_id' with the ANSI X3.230 FC-PH Fibre Channel specification
and its extensions", and its extensions",
http://standards.ieee.org/regauth/oui/tutorials/fibrecomp_id.html, http://standards.ieee.org/regauth/oui/tutorials/fibrecomp_id.html,
24 February 1997. 24 February 1997.
[SENSOR] [SENSOR]
Bierman, A., Romascanu, D., and KC Norseth, "Entity Sensor Bierman, A., Romascanu, D., and KC Norseth, "Entity Sensor
Management Information Base", Internet Draft, <draft-ietf-entmib- Management Information Base", Internet Draft, <draft-ietf-entmib-
sensor-mib-00.txt>, 18 January 2002. sensor-mib-00.txt>, 18 January 2002.
12. 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 have a
MAX-ACCESS clause of read-write. Such objects may be considered MAX-ACCESS clause of read-write. Such objects may be considered
sensitive or vulnerable in some network environments. The support for sensitive or vulnerable in some network environments. The support for
SET operations in a non-secure environment without proper protection can SET operations in a non-secure environment without proper protection can
have a negative effect on network operations. have a negative effect on network operations.
There are a number of managed objects in this MIB that contain what There are a number of managed objects in this MIB that contain what
could be considered as sensitive information. In particular, the could be considered as sensitive information. In particular, the
objects which provide information on network topology: objects which provide information on network topology:
skipping to change at page 57, line 5 skipping to change at page 67, line 5
It is recommended that the implementors consider the security features It is recommended that the implementors consider the security features
as provided by the SNMPv3 framework. Specifically, the use of the User- as provided by the SNMPv3 framework. Specifically, the use of the User-
based Security Model RFC 2574 [RFC2574] and the View-based Access based Security Model RFC 2574 [RFC2574] and the View-based Access
Control Model RFC 2575 [RFC2575] is recommended. Control Model RFC 2575 [RFC2575] is recommended.
It is then a customer/user responsibility to ensure that the SNMP entity It is then a customer/user responsibility to ensure that the SNMP entity
giving access to an instance of this MIB, is properly configured to give giving access to an instance of this MIB, is properly configured to give
access to the objects only to those principals (users) that have access to the objects only to those principals (users) that have
legitimate rights to indeed GET or SET (change/create/delete) them. legitimate rights to indeed GET or SET (change/create/delete) them.
13. Comparison to draft-ietf-ipfc-fcmgmt-int-mib-07.txt 11. Comparison to draft-ietf-ipfc-fcmgmt-int-mib-07.txt
This section is expected to be temporary, and removed before this The decision on whether this section is permanent will be made prior to
specification is published as an RFC. publication of this document as an RFC.
13.1. Problems with draft-ietf-ipfc-fcmgmt-int-mib-07.txt 11.1. Problems with draft-ietf-ipfc-fcmgmt-int-mib-07.txt
The Fibre Channel Management Integration MIB had the following major The Fibre Channel Management Integration MIB had the following major
problems: 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-scaleable. Rather, a Fibre Channel
skipping to change at page 58, line 5 skipping to change at page 68, line 5
management. SNMP agents need to implement a row in the ifTable for management. SNMP agents need to implement a row in the ifTable for
each of their network interfaces, including their Fibre Channel each of their network interfaces, including their Fibre Channel
interfaces. The IF-MIB requires a media-specific MIB to specify interfaces. The IF-MIB requires a media-specific MIB to specify
how that type of interface uses the ifTable (see section 4 in RFC how that type of interface uses the ifTable (see section 4 in RFC
2863). RFC 2837 doesn't do that, and nor did the Fibre Channel 2863). RFC 2837 doesn't do that, and nor did the Fibre Channel
Integration MIB. 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 11.2. Detailed Changes
13.2.1. Removal of Sensor-related objects 11.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 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 Sensor
MIB, see [SENSOR].) This removed the need for: MIB, see [SENSOR].) 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 11.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 Channel,
and therefore should not be in this MIB. (For similar functionality, and therefore should not be in this MIB. (For similar functionality,
see SNMP-NOTIFICATION-MIB and SNMP-TARGET-MIB in RFC 2573). This see SNMP-NOTIFICATION-MIB and SNMP-TARGET-MIB in RFC 2573). This
removed the need for: 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 11.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, and
therefore should not be in this MIB. (For similar functionality, see therefore should not be in this MIB. (For similar functionality, see
the Event group in RFC 2819 and the Notification Log MIB in RFC 3014; the Event group in RFC 2819 and the Notification Log MIB in RFC 3014;
the SNMP-NOTIFICATION-MIB provides for the filtering of notifications.) the SNMP-NOTIFICATION-MIB provides for the filtering of notifications.)
This removed the need for: 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 11.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 Entity
MIB (RFC 2737); aspects of software modules are represented in the Host MIB (RFC 2737); aspects of software modules are represented in the Host
Resources MIB (RFC 2790). Two new objects provide indexing from this Resources MIB (RFC 2790). Two new objects provide indexing from this
MIB into those MIBs: one having the value of PhysicalIndex (or zero) and MIB into those MIBs: one having the value of PhysicalIndex (or zero) and
the other having the value of hrSWInstalledIndex (or zero). These the other having the value of hrSWInstalledIndex (or zero). These
replaced the need for: 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 11.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 the
need for: need for:
revisionNumber revisionNumber
13.2.6. Removal of other not FC-specific information 11.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 11.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 11.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 IF-
MIB objects: 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 &
skipping to change at page 61, line 13 skipping to change at page 71, line 13
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 11.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 several
sub-agents. It is not difficult to implement the same MIB in several sub-agents. It is not difficult to implement the same MIB in several
such sub-agents if all of the MIB's tables have a common index variable such sub-agents if all of the MIB's tables have a common index variable
as the first auxiliary object in their INDEX clauses. However, any as the first auxiliary object in their INDEX clauses. However, any
scalars which the MIB contains pose a problem for the AgentX scalars which the MIB contains pose a problem for the AgentX
environment. All the (remaining) scalars were therefore removed: environment. All the (remaining) scalars were therefore removed:
revisionNumber revisionNumber
uNumber uNumber
systemURL systemURL
13.2.10. FC Management Instance 11.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 draft-ietf-
ipfc-fcmgmt-int-mib-07.txt, and its usage provided a confused mixture of ipfc-fcmgmt-int-mib-07.txt, and its usage provided a confused mixture of
indications to the implementor: indications to the 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; - the definition of connUnitProduct suggested it was a vendor's product;
skipping to change at page 62, line 9 skipping to change at page 72, line 9
In fact, this scenario is not new; in practice, a "connectivity unit" In fact, this scenario is not new; in practice, a "connectivity unit"
will have the same semantics as a management "instance" in other MIBs, 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 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 separable managed instance of Fibre Channel functionality". Given this
definition, then "FC management instance" is a better name because it is definition, then "FC management instance" is a better name because it is
more accurate and more representative of the definition, than is more accurate and more representative of the definition, than is
"connectivity unit". "connectivity unit".
13.2.11. Counter Syntax 11.2.11. Counter Syntax
All packet and octet counters have been changed to be Counter64's. The All packet and octet counters have been changed to be Counter64's (but
error counters have been changed to Counter32's. (In the probably 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 impossible, and at most improbable, circumstances that the rate of
occurence of errors, even on a 10Gbs Fibre Channel interface, might wrap occurence of errors, even on a 10Gbs Fibre Channel interface, might wrap
faster than a hour, the fact that errors are occurring will almost faster than a hour, the fact that errors are occurring will almost
certainly be apparent from other MIB objects.) certainly be apparent from other MIB objects.)
13.2.12. Obsolete Fibre Channel features 11.2.12. Obsolete/Little-Used Fibre Channel features
All information relating to obsolete Fibre Channel features has been Information relating to Fibre Channel features which are obsolete or not
deleted; 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 (see FC-FS) - PH version numbers
Note that with Class 1 becoming obsolete, only class 2 now needs F_BSY, Note that with support for Class 1 service being deleted, only class 2
F_RJT, P_BSY and P_RJT counters, and thus they no longer need to be now needs F_BSY, F_RJT, P_BSY and P_RJT counters, and thus they no
counted for all classes as well as for class 2, and therefore these longer need to be counted for all classes as well as for class 2, and
objects: therefore these objects:
connUnitPortStatCountFBSYFrames connUnitPortStatCountFBSYFrames
connUnitPortStatCountPBSYFrames connUnitPortStatCountPBSYFrames
connUnitPortStatCountFRJTFrames connUnitPortStatCountFRJTFrames
connUnitPortStatCountPRJTFrames connUnitPortStatCountPRJTFrames
have been deleted. have been deleted.
13.3. Name Server objects 11.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 draft-ietf-ipfc-
fcmgmt-int-mib-07.txt. That information is not currently represented in fcmgmt-int-mib-07.txt. That information is not currently represented in
this MIB, because this MIB is already quite large, and a set of Name this 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. Server objects are expected to be defined in a separate (new) MIB.
14. Comparison to RFC 2837 11.4. Additional objects
Support for Class F traffic, including 32-bit octet and frame counters,
has been added.
12. 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 13. 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 14. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself 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 may not be modified in any way, such as by removing the copyright notice
 End of changes. 

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