draft-ietf-ips-fcmgmt-mib-04.txt   draft-ietf-ips-fcmgmt-mib-05.txt 
Internet Draft Keith McCloghrie Internet Draft Keith McCloghrie
Cisco Systems, Inc Cisco Systems, Inc
24 February 2003 17 July 2004
Fibre Channel Management MIB Fibre Channel Management MIB
draft-ietf-ips-fcmgmt-mib-05.txt
draft-ietf-ips-fcmgmt-mib-04.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions of By submitting this Internet-Draft, I certify that any applicable patent
Section 10 of RFC2026. 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 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.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
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.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
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) for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes managed objects for information related to particular, it describes managed objects for information related to
Fibre Channel. Fibre Channel.
Table of Contents Table of Contents
1 Introduction .................................................... 3 1 Introduction .................................................... 3
2 The Internet-Standard Management Framework ...................... 4 2 The Internet-Standard Management Framework ...................... 3
3 Short Overview of Fibre Channel ................................. 4 3 Short Overview of Fibre Channel ................................. 3
4 MIB Overview .................................................... 5 4 MIB Overview .................................................... 4
5 Relationship to Other MIBs ...................................... 7 4.1 The fcmInstanceBasicGroup group ............................... 4
5.1 The Interfaces Group MIB ...................................... 7 4.2 The fcmSwitchBasicGroup group ................................. 4
5.2 Entity MIB .................................................... 10 4.3 The fcmPortBasicGroup group ................................... 4
5.3 Host Resources MIB ............................................ 11 4.4 The fcmPortStatsGroup group ................................... 5
6 Definitions ..................................................... 12 4.5 The fcmPortClass23StatsGroup group ............................ 5
7 Intellectual Property ........................................... 63 4.6 The fcmPortLcStatsGroup group ................................. 5
8 Acknowledgements ................................................ 63 4.7 The fcmPortClassFStatsGroup group ............................. 5
9 Normative References ............................................ 63 4.8 The fcmPortErrorsGroup group .................................. 5
10 Informative References ......................................... 65 4.9 The fcmSwitchPortGroup group .................................. 5
11 Security Considerations ........................................ 66 4.10 The fcmSwitchLoginGroup group ................................ 6
12 Comparison to draft-ietf-ipfc-fcmgmt-int-mib-07.txt ............ 68 4.11 The fcmLinkBasicGroup group .................................. 6
12.1 Problems with draft-ietf-ipfc-fcmgmt-int-mib-07.txt .......... 68 5 Relationship to Other MIBs ...................................... 6
12.2 Detailed Changes ............................................. 69 5.1 The Interfaces Group MIB ...................................... 6
12.3 Name Server objects .......................................... 73 5.2 Entity MIB .................................................... 9
12.4 Additional objects ........................................... 74 5.3 Host Resources MIB ............................................ 10
13 Comparison to RFC 2837 ......................................... 75 6 Definitions ..................................................... 11
14 Author's Address ............................................... 76 7 Intellectual Property ........................................... 62
15 Full Copyright Statement ....................................... 76 8 Acknowledgements ................................................ 62
9 Normative References ............................................ 62
10 Informative References ......................................... 64
11 Security Considerations ........................................ 65
12 IANA Considerations ............................................ 66
12.1 OID Assignment ............................................... 66
12.2 FC Port Type Registry ........................................ 66
13 Comparison to draft-ietf-ipfc-fcmgmt-int-mib-07.txt ............ 69
14 Comparison to RFC 2837 ......................................... 76
15 Author's Address ............................................... 77
16 Full Copyright Statement ....................................... 77
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) for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes managed objects for information related to particular, it describes managed objects for information related to
Fibre Channel. Fibre Channel.
1.1. Change Log
This section to be deleted before publication as an RFC.
1.1.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.
1.1.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.
1.1.3. Changes made in draft-ietf-ips-fcmgmt-mib-02.txt
- aligned the meanings of bits of the FcUnitFunctions TC with the latest
update to the meanings in the GS-4 specification.
- broadened the scope of the fcmEPortTable to apply to any type of port
connected to an inter-swithc link, and changed its descriptor to
fcmISPortTable.
- changed the fcmLinkTable to be optional.
- fixed some minor typos
1.2. Changes made in draft-ietf-ips-fcmgmt-mib-03.txt
- 'storageDevice' was added as an enumeration of the FcUnitFunctions TC
for compatibility with the latest proposal in T11.
- fcmISPortClassFCredit was changed to have a MAX-ACCESS of read-write,
but the minimum compliance was kept as read-only.
- several auxiliary objects were changed to exclude 0 as a possible
value (as recommended in section 7.7 of RFC 2578).
- the OIDs of the columnar objects in the fcmPortErrorsTable were
renumbered so as to be consecutive.
1.2.1. Changes made in draft-ietf-ips-fcmgmt-mib-04.txt
- updated boilerplate as required by the publication of RFCs 3410
through 3418.
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 Internet-Standard Management Framework, please refer to section 7 of RFC
RFC 3410 [RFC3410]. 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed the
the Management Information Base or MIB. MIB objects are generally Management Information Base or MIB. MIB objects are generally accessed
accessed through the Simple Network Management Protocol (SNMP). through the Simple Network Management Protocol (SNMP). Objects in the
Objects in the MIB are defined using the mechanisms defined in the MIB are defined using the mechanisms defined in the Structure of
Structure of Management Information (SMI). This memo specifies a MIB Management Information (SMI). This memo specifies a MIB module that is
module that is compliant to the SMIv2, which is described in STD 58, compliant to the SMIv2, which is described in STD 58, RFC 2578
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
[RFC2580].
3. Short Overview of Fibre Channel 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.
skipping to change at page 5, line 33 skipping to change at page 4, line 24
identifiers are dynamic and are assigned by a switch. 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 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. In
order to represent such multiple Fibre Channel management instances
within the same SNMP context (see section 3.3.1 of [RFC3411]), all
tables in this MIB are INDEX-ed by fcmInstanceIndex which is defined as
an arbitrary integer to uniquely identify a 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.
skipping to change at page 12, line 11 skipping to change at page 11, line 11
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.)
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, mib-2 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 "200209250000Z" LAST-UPDATED "200403250000Z"
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 "200209250000Z"
Copyright (C) The Internet Society (2004). This version of
this MIB module is part of RFC yyyy; see the RFC itself for
full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200403250000Z"
DESCRIPTION DESCRIPTION
"Initial version of the Fibre Channel Mgmt MIB module, "Initial version of the Fibre Channel Mgmt MIB module."
published as RFC xxxx." -- (to be assigned by RFC Editor) ::= { transmission nnn } -- IANA, please enter the value you assign here
::= { mib-2 999999 } -- to be assigned by IANA
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 circumstances
where the WWN is unassigned/unknown." where the WWN is unassigned/unknown."
SYNTAX OCTET STRING (SIZE(0 | 8 | 16)) SYNTAX OCTET STRING (SIZE(0 | 8 | 16))
FcAddressId ::= 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 address space of a Fabric. The zero-length string value
is used in circumstances where the WWN is
unassigned/unknown."
SYNTAX OCTET STRING (SIZE(0 | 3)) SYNTAX OCTET STRING (SIZE(0 | 3))
DomainIdOrZero ::= 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 a FC switch), or zero if the no Domain Id
has been assigned." 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." "The type of a Fibre Channel port, as indicated by the use
SYNTAX INTEGER { of the appropriate value assigned by IANA."
unknown(1), REFERENCE
other(2), -- none of the below "The IANA-maintained registry for
dynamic(3), -- determined dynamically Fibre Channel port types. "
nPort(4), -- IANA, please extend the text inside the immediately
nlPort(5), -- preceeding quotes to include a location at which a
fPort(6), -- reader can ascertain the latest assigned values
flPort(7), SYNTAX Unsigned32
ePort(8),
bPort(9)
}
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 16, line 17 skipping to change at page 16, line 5
bridge(3), bridge(3),
gateway(4), gateway(4),
host(5), host(5),
storageSubsys(6), storageSubsys(6),
storageAccessDev(7), storageAccessDev(7),
nas(8), nas(8),
wdmux(9), wdmux(9),
storageDevice(10) storageDevice(10)
} }
PhysicalIndexOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The index value for a physical entity's row in the Entity
MIB's entPhysicalTable. A zero value indicates that no row
in the entPhysicalTable is applicable."
REFERENCE
"entPhysicalTable is defined in the Entity MIB, RFC 2737."
SYNTAX Integer32 (0..2147483647)
HrSWInstalledIndexOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The index value for a software module's row in the Host
Resources MIB's hrSWInstalledTable. A zero value indicates
that no row in the hrSWInstalledTable is applicable."
REFERENCE
"hrSWInstalledTable is defined in the Host Resources MIB,
RFC 2790."
SYNTAX Integer32 (0..2147483647)
MilliSeconds ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Time units in milliseconds."
SYNTAX Unsigned32
MicroSeconds ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Time units in microseconds."
SYNTAX Unsigned32
--******************************** --********************************
-- MIB object definitions -- MIB object definitions
-- --
fcmInstanceTable OBJECT-TYPE fcmInstanceTable OBJECT-TYPE
SYNTAX SEQUENCE OF FcmInstanceEntry SYNTAX SEQUENCE OF FcmInstanceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about the local Fibre Channel management "Information about the local Fibre Channel management
skipping to change at page 18, line 33 skipping to change at page 16, line 33
"A list of attributes for a particular local Fibre Channel "A list of attributes for a particular local Fibre Channel
management instance." management instance."
INDEX { fcmInstanceIndex } INDEX { fcmInstanceIndex }
::= { fcmInstanceTable 1 } ::= { fcmInstanceTable 1 }
FcmInstanceEntry ::= FcmInstanceEntry ::=
SEQUENCE { SEQUENCE {
fcmInstanceIndex Unsigned32, fcmInstanceIndex Unsigned32,
fcmInstanceWwn FcNameIdOrZero, fcmInstanceWwn FcNameIdOrZero,
fcmInstanceFunctions FcUnitFunctions, fcmInstanceFunctions FcUnitFunctions,
fcmInstancePhysicalIndex PhysicalIndexOrZero, fcmInstancePhysicalIndex Integer32,
fcmInstanceSoftwareIndex HrSWInstalledIndexOrZero, fcmInstanceSoftwareIndex Integer32,
fcmInstanceStatus INTEGER, fcmInstanceStatus INTEGER,
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 which uniquely identifies this
instance amongst all local Fibre Channel management instance amongst all local Fibre Channel management
instances. instances.
It is mandatory that this value remain constant between It is mandatory to keep this value constant between restarts
restarts of the agent, and desirable that it remain constant of the agent, and to make every possible effort to keep it
across restarts. (but note, it is unrealistic to expect it constant across restarts (but note, it is unrealistic to
to remain constant across all re-configurations of the local expect it to remain constant across all re-configurations of
system and across all replacements of non-volatile the local system, e.g., across the replacement of all non-
storage)." volatile storage)."
::= { fcmInstanceEntry 1 } ::= { fcmInstanceEntry 1 }
fcmInstanceWwn OBJECT-TYPE fcmInstanceWwn OBJECT-TYPE
SYNTAX FcNameIdOrZero SYNTAX FcNameIdOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the instance has one (or more) WWN(s), then this object "If the instance has one (or more) WWN(s), then this object
contains that (or one of those) WWN(s). contains that (or one of those) WWN(s).
skipping to change at page 19, line 35 skipping to change at page 17, line 35
fcmInstanceFunctions OBJECT-TYPE fcmInstanceFunctions OBJECT-TYPE
SYNTAX FcUnitFunctions SYNTAX FcUnitFunctions
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"One (or more) Fibre Channel unit functions being performed "One (or more) Fibre Channel unit functions being performed
by this instance." by this instance."
::= { fcmInstanceEntry 3 } ::= { fcmInstanceEntry 3 }
fcmInstancePhysicalIndex OBJECT-TYPE fcmInstancePhysicalIndex OBJECT-TYPE
SYNTAX PhysicalIndexOrZero 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), then component (or to a hierarchy of physical components)
this object's value is the value of the entPhysicalIndex of identified by the Entity-MIB, then this object's value is
that component (or of the component at the root of that the value of the entPhysicalIndex of that component (or of
hierarchy). If there is no correspondence to a physical the component at the root of that hierarchy). If there is
component (or no component which has an entPhysicalIndex no correspondence to a physical component (or no component
value), then the value of this object is zero." which has an entPhysicalIndex value), then the value of this
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 HrSWInstalledIndexOrZero 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, then this object's value is the value of software module identified in the Host Resources MIB, then
the hrSWInstalledIndex of that module. If there is no this object's value is the value of the hrSWInstalledIndex
correspondence to an installed software module (or no module of that module. If there is no correspondence to an
which has a hrSWInstalledIndex value), then the value of installed software module (or no module which has a
this object is zero." hrSWInstalledIndex value), then the value of this object is
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),
ok(2), -- able to operate correctly ok(2), -- able to operate correctly
warning(3), -- needs attention warning(3), -- needs attention
skipping to change at page 22, line 8 skipping to change at page 20, line 8
DESCRIPTION DESCRIPTION
"Information about a particular Fibre Channel switch which "Information about a particular Fibre Channel switch which
is managed by the management instance given by is 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 DomainIdOrZero, fcmSwitchDomainId FcDomainIdOrZero,
fcmSwitchPrincipal TruthValue fcmSwitchPrincipal TruthValue
} }
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 which 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
of the agent, and to make every possible effort to keep it
constant across restarts."
::= { fcmSwitchEntry 1 } ::= { fcmSwitchEntry 1 }
fcmSwitchDomainId OBJECT-TYPE fcmSwitchDomainId OBJECT-TYPE
SYNTAX DomainIdOrZero SYNTAX FcDomainIdOrZero
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Domain Id of this switch. A value of zero indicates "The Domain Id of this switch. A value of zero indicates
that a switch has not (yet) been assigned a Domain Id." that a switch has not (yet) been assigned a Domain Id."
::= { fcmSwitchEntry 2 } ::= { fcmSwitchEntry 2 }
fcmSwitchPrincipal OBJECT-TYPE fcmSwitchPrincipal OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 24, line 26 skipping to change at page 22, line 30
"The World Wide Name of the Node which contains this port, "The World Wide Name of the Node which contains this port,
or the zero-length string if the port does not have a node or 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. Each port "The administratively desired type of this port."
will typically only be able to support a subset of these
types."
::= { fcmPortEntry 4 } ::= { fcmPortEntry 4 }
fcmPortOperType OBJECT-TYPE fcmPortOperType OBJECT-TYPE
SYNTAX FcPortType SYNTAX FcPortType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current operational type of this port." "The current operational type of this port."
::= { fcmPortEntry 5 } ::= { fcmPortEntry 5 }
skipping to change at page 28, line 26 skipping to change at page 26, line 28
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of statistics for Fibre Channel ports." "A list of statistics for Fibre Channel ports."
::= { fcmgmtObjects 4 } ::= { fcmgmtObjects 4 }
fcmPortStatsEntry OBJECT-TYPE fcmPortStatsEntry OBJECT-TYPE
SYNTAX FcmPortStatsEntry SYNTAX FcmPortStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry containing statistics for a Fibre Channel port." "An entry containing statistics for a Fibre Channel port.
If any counter in this table suffers a discontinuity, the
value of ifCounterDiscontinuityTime (defined in the IF-MIB)
must be updated."
REFERENCE "The Interfaces Group MIB, RFC 2863, June 2000."
AUGMENTS { fcmPortEntry } AUGMENTS { fcmPortEntry }
::= { fcmPortStatsTable 1 } ::= { fcmPortStatsTable 1 }
FcmPortStatsEntry ::= FcmPortStatsEntry ::=
SEQUENCE { SEQUENCE {
fcmPortBBCreditZeros Counter64, fcmPortBBCreditZeros Counter64,
fcmPortFullInputBuffers Counter64, fcmPortFullInputBuffers Counter64,
fcmPortClass2RxFrames Counter64, fcmPortClass2RxFrames Counter64,
fcmPortClass2RxOctets Counter64, fcmPortClass2RxOctets Counter64,
fcmPortClass2TxFrames Counter64, fcmPortClass2TxFrames Counter64,
skipping to change at page 34, line 38 skipping to change at page 32, line 43
-- Port Low-capacity Statistics -- Port Low-capacity Statistics
-- --
-- these are Counter32 "low-capacity" counters for systems -- these are Counter32 "low-capacity" counters for systems
-- which do not support Counter64's -- which 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 which are a shadow of "A list of Counter32-based statistics for systems which do
the Counter64 statistics in the fcmPortStatsTable, for not support Counter64."
systems which do 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." statistics for a Fibre Channel port. If any counter in this
table suffers a discontinuity, the value of
ifCounterDiscontinuityTime (defined in the IF-MIB) must be
updated."
REFERENCE "The Interfaces Group MIB, RFC 2863, June 2000."
AUGMENTS { fcmPortEntry } AUGMENTS { fcmPortEntry }
::= { fcmPortLcStatsTable 1 } ::= { fcmPortLcStatsTable 1 }
FcmPortLcStatsEntry ::= FcmPortLcStatsEntry ::=
SEQUENCE { SEQUENCE {
fcmPortLcBBCreditZeros Counter32, fcmPortLcBBCreditZeros Counter32,
fcmPortLcFullInputBuffers Counter32, fcmPortLcFullInputBuffers Counter32,
fcmPortLcClass2RxFrames Counter32, fcmPortLcClass2RxFrames Counter32,
fcmPortLcClass2RxOctets Counter32, fcmPortLcClass2RxOctets Counter32,
fcmPortLcClass2TxFrames Counter32, fcmPortLcClass2TxFrames Counter32,
skipping to change at page 40, line 22 skipping to change at page 38, line 27
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Error counters for Fibre Channel ports." "Error counters for Fibre Channel ports."
::= { fcmgmtObjects 6 } ::= { fcmgmtObjects 6 }
fcmPortErrorsEntry OBJECT-TYPE fcmPortErrorsEntry OBJECT-TYPE
SYNTAX FcmPortErrorsEntry SYNTAX FcmPortErrorsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Error counters for a Fibre Channel port." "Error counters for a Fibre Channel port. If any counter in
this table suffers a discontinuity, the value of
ifCounterDiscontinuityTime (defined in the IF-MIB) must be
updated."
REFERENCE "The Interfaces Group MIB, RFC 2863, June 2000."
AUGMENTS { fcmPortEntry } AUGMENTS { fcmPortEntry }
::= { fcmPortErrorsTable 1 } ::= { fcmPortErrorsTable 1 }
FcmPortErrorsEntry ::= FcmPortErrorsEntry ::=
SEQUENCE { SEQUENCE {
fcmPortRxLinkResets Counter32, fcmPortRxLinkResets Counter32,
fcmPortTxLinkResets Counter32, fcmPortTxLinkResets Counter32,
fcmPortLinkResets Counter32, fcmPortLinkResets Counter32,
fcmPortRxOfflineSequences Counter32, fcmPortRxOfflineSequences Counter32,
fcmPortTxOfflineSequences Counter32, fcmPortTxOfflineSequences Counter32,
skipping to change at page 41, line 7 skipping to change at page 39, line 18
fcmPortDelimiterErrors Counter32, fcmPortDelimiterErrors Counter32,
fcmPortEncodingDisparityErrors Counter32, fcmPortEncodingDisparityErrors Counter32,
fcmPortOtherErrors Counter32 fcmPortOtherErrors Counter32
} }
fcmPortRxLinkResets OBJECT-TYPE fcmPortRxLinkResets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Link resets (LR primitives) received." "The number of Link Reset (LR) Primitive Sequences
received."
::= { fcmPortErrorsEntry 1 } ::= { fcmPortErrorsEntry 1 }
fcmPortTxLinkResets OBJECT-TYPE fcmPortTxLinkResets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Link resets (LRs primitive) transmitted." "The number of Link Reset (LR) Primitive Sequences
transmitted."
::= { fcmPortErrorsEntry 2 } ::= { fcmPortErrorsEntry 2 }
fcmPortLinkResets OBJECT-TYPE fcmPortLinkResets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times the reset link protocol was initiated "The number of times the reset link protocol was initiated
on this port. This includes the number of Loop on this port. This includes the number of Loop
Initialization Primitive (LIP) events on an arbitrated loop Initialization Primitive (LIP) events on an arbitrated loop
port." port."
::= { fcmPortErrorsEntry 3 } ::= { fcmPortErrorsEntry 3 }
fcmPortRxOfflineSequences OBJECT-TYPE fcmPortRxOfflineSequences OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Offline Primitive OLS received at this port." "The number of Offline (OLS) Primitive Sequences received at
this port."
::= { fcmPortErrorsEntry 4 } ::= { fcmPortErrorsEntry 4 }
fcmPortTxOfflineSequences OBJECT-TYPE fcmPortTxOfflineSequences OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Offline Primitive OLS transmitted by this "The number of Offline (OLS) Primitive Sequences transmitted
port." by this port."
::= { 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
skipping to change at page 45, line 30 skipping to change at page 43, line 42
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 }
FcmFxPortEntry ::= FcmFxPortEntry ::=
SEQUENCE { SEQUENCE {
fcmFxPortRatov MilliSeconds, fcmFxPortRatov Unsigned32,
fcmFxPortEdtov MilliSeconds, fcmFxPortEdtov Unsigned32,
fcmFxPortRttov MilliSeconds, fcmFxPortRttov Unsigned32,
fcmFxPortHoldTime MicroSeconds, fcmFxPortHoldTime Unsigned32,
fcmFxPortCapBbCreditMax FcBbCredit, fcmFxPortCapBbCreditMax FcBbCredit,
fcmFxPortCapBbCreditMin FcBbCredit, fcmFxPortCapBbCreditMin FcBbCredit,
fcmFxPortCapDataFieldSizeMax FcDataFieldSize, fcmFxPortCapDataFieldSizeMax FcDataFieldSize,
fcmFxPortCapDataFieldSizeMin FcDataFieldSize, fcmFxPortCapDataFieldSizeMin FcDataFieldSize,
fcmFxPortCapClass2SeqDeliv TruthValue, fcmFxPortCapClass2SeqDeliv TruthValue,
fcmFxPortCapClass3SeqDeliv TruthValue, fcmFxPortCapClass3SeqDeliv TruthValue,
fcmFxPortCapHoldTimeMax MicroSeconds, fcmFxPortCapHoldTimeMax Unsigned32,
fcmFxPortCapHoldTimeMin MicroSeconds fcmFxPortCapHoldTimeMin Unsigned32
} }
fcmFxPortRatov OBJECT-TYPE fcmFxPortRatov OBJECT-TYPE
SYNTAX MilliSeconds SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Resource_Allocation_Timeout Value configured for this "The Resource_Allocation_Timeout Value configured for this
Fx_Port. This is used as the timeout value for determining Fx_Port. This is used as the timeout value for determining
when to reuse an Nx_Port resource such as a when to reuse an Nx_Port resource such as a
Recovery_Qualifier. It represents the Error_Detect_Timeout Recovery_Qualifier. It represents the Error_Detect_Timeout
value (see fcmFxPortEdtov) plus twice the maximum time that value (see fcmFxPortEdtov) plus twice the maximum time that
a frame may be delayed within the Fabric and still be a frame may be delayed within the Fabric and still be
delivered." delivered."
::= { fcmFxPortEntry 1 } ::= { fcmFxPortEntry 1 }
fcmFxPortEdtov OBJECT-TYPE fcmFxPortEdtov OBJECT-TYPE
SYNTAX MilliSeconds SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Error_Detect_Timeout value configured for this Fx_Port. "The Error_Detect_Timeout value configured for this Fx_Port.
This is used as the timeout value for detecting an error This is used as the timeout value for detecting an error
condition." condition."
::= { fcmFxPortEntry 2 } ::= { fcmFxPortEntry 2 }
fcmFxPortRttov OBJECT-TYPE fcmFxPortRttov OBJECT-TYPE
SYNTAX MilliSeconds 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 Loss of
Synchronization." Synchronization."
::= { fcmFxPortEntry 3 } ::= { fcmFxPortEntry 3 }
fcmFxPortHoldTime OBJECT-TYPE fcmFxPortHoldTime OBJECT-TYPE
SYNTAX MicroSeconds 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
before discarding the frame if it is unable to deliver the before discarding the frame if it is unable to deliver the
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 }
skipping to change at page 48, line 20 skipping to change at page 46, line 35
fcmFxPortCapClass3SeqDeliv OBJECT-TYPE fcmFxPortCapClass3SeqDeliv OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of whether this Fx_Port is capable of "An indication of whether this Fx_Port is capable of
supporting Class 3 Sequential Delivery." supporting Class 3 Sequential Delivery."
::= { fcmFxPortEntry 10 } ::= { fcmFxPortEntry 10 }
fcmFxPortCapHoldTimeMax OBJECT-TYPE fcmFxPortCapHoldTimeMax OBJECT-TYPE
SYNTAX MicroSeconds SYNTAX Unsigned32
UNITS "microseconds" UNITS "microseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum holding time that this Fx_Port is capable of "The maximum holding time that this Fx_Port is capable of
supporting." supporting."
::= { fcmFxPortEntry 11 } ::= { fcmFxPortEntry 11 }
fcmFxPortCapHoldTimeMin OBJECT-TYPE fcmFxPortCapHoldTimeMin OBJECT-TYPE
SYNTAX MicroSeconds SYNTAX Unsigned32
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 Inter-Switch Port Table -- The Fibre Channel Inter-Switch Port Table
skipping to change at page 51, line 18 skipping to change at page 49, line 22
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 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.
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
assigned to the same Nx_Port, or, after a reset of the value
of the relevant instance of ifCounterDiscontinuityTime."
REFERENCE "The Interfaces Group MIB, RFC 2863, June 2000."
::= { fcmFLoginEntry 1 } ::= { fcmFLoginEntry 1 }
fcmFLoginPortWwn OBJECT-TYPE fcmFLoginPortWwn OBJECT-TYPE
SYNTAX FcNameIdOrZero SYNTAX FcNameIdOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The port name of the attached Nx_Port, or the zero-length "The port name of the attached Nx_Port, or the zero-length
string if unknown." string if unknown."
::= { fcmFLoginEntry 2 } ::= { fcmFLoginEntry 2 }
skipping to change at page 54, line 24 skipping to change at page 52, line 34
fcmLinkIndex Unsigned32, fcmLinkIndex Unsigned32,
fcmLinkEnd1NodeWwn FcNameIdOrZero, fcmLinkEnd1NodeWwn FcNameIdOrZero,
fcmLinkEnd1PhysPortNumber Unsigned32, fcmLinkEnd1PhysPortNumber Unsigned32,
fcmLinkEnd1PortWwn FcNameIdOrZero, fcmLinkEnd1PortWwn FcNameIdOrZero,
fcmLinkEnd2NodeWwn FcNameIdOrZero, fcmLinkEnd2NodeWwn FcNameIdOrZero,
fcmLinkEnd2PhysPortNumber Unsigned32, fcmLinkEnd2PhysPortNumber Unsigned32,
fcmLinkEnd2PortWwn FcNameIdOrZero, fcmLinkEnd2PortWwn FcNameIdOrZero,
fcmLinkEnd2AgentAddress SnmpAdminString, fcmLinkEnd2AgentAddress SnmpAdminString,
fcmLinkEnd2PortType FcPortType, fcmLinkEnd2PortType FcPortType,
fcmLinkEnd2UnitType FcUnitFunctions, fcmLinkEnd2UnitType FcUnitFunctions,
fcmLinkEnd2FcAddressId FcAddressId 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 which 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."
skipping to change at page 56, line 10 skipping to change at page 54, line 19
DESCRIPTION DESCRIPTION
"The port WWN of end2, or the zero-length string if "The port WWN of end2, or the zero-length string if
unknown." unknown."
::= { fcmLinkEntry 7 } ::= { fcmLinkEntry 7 }
fcmLinkEnd2AgentAddress OBJECT-TYPE fcmLinkEnd2AgentAddress OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of the SNMP agent for the Fibre Channel "The address of the management agent for the Fibre Channel
Interconnect Element or Platform of which end2 is a part. Interconnect Element or Platform of which end2 is a part.
If the address is unknown, the value of this object is the The GS-3 specification provides example values of URLs which
zero-length string." indicate an SNMP, HTTP or XML agent. If the address is
unknown, the value of this object is the zero-length
string."
REFERENCE REFERENCE
"FC-GS-3 Rev 7.01, 28 Nov 2000, sect 6.1.2.1.7" "FC-GS-3 Rev 7.01, 28 Nov 2000, sect 6.1.2.1.7"
::= { fcmLinkEntry 8 } ::= { fcmLinkEntry 8 }
fcmLinkEnd2PortType OBJECT-TYPE fcmLinkEnd2PortType OBJECT-TYPE
SYNTAX FcPortType SYNTAX FcPortType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The port type of end2." "The port type of end2."
skipping to change at page 56, line 41 skipping to change at page 55, line 6
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of/function(s) performed by the Fibre Channel "The type of/function(s) performed by the Fibre Channel
Interconnect Element or Platform of which end2 is a part." Interconnect Element or Platform of which end2 is a part."
REFERENCE REFERENCE
"FC-GS-3 Rev 7.01, 28 Nov 2000, sections 6.1.2.1.2 "FC-GS-3 Rev 7.01, 28 Nov 2000, sections 6.1.2.1.2
and 6.1.2.3.2" and 6.1.2.3.2"
::= { fcmLinkEntry 10 } ::= { fcmLinkEntry 10 }
fcmLinkEnd2FcAddressId OBJECT-TYPE fcmLinkEnd2FcAddressId OBJECT-TYPE
SYNTAX FcAddressId SYNTAX FcAddressIdOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Fibre Channel Address ID of end2, or the zero-length "The Fibre Channel Address ID of end2, or the zero-length
string if unknown." string if unknown."
::= { fcmLinkEntry 11 } ::= { fcmLinkEntry 11 }
--******************************** --********************************
-- Conformance Section -- Conformance Section
-- --
skipping to change at page 58, line 16 skipping to change at page 57, line 16
"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 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 which manage Fibre Channel
switches." switches."
GROUP fcmLinkBasicGroup
DESCRIPTION
"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."
OBJECT fcmInstanceSoftwareIndex OBJECT fcmInstanceSoftwareIndex
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 40 skipping to change at page 62, line 40
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.
9. Normative References 9. Normative References
[RFC2434]
Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", BCP:26, RFC 2434, October 1998.
[RFC2578] [RFC2578]
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.
and S. Waldbusser, "Structure of Management Information Version 2 and S. Waldbusser, "Structure of Management Information Version 2
(SMIv2)", STD 58, RFC 2578, April 1999. (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] [RFC2579]
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.
and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC
2579, April 1999. 2579, April 1999.
skipping to change at page 64, line 22 skipping to change at page 63, line 27
December 1999. December 1999.
[RFC2790] [RFC2790]
Waldbusser, S., and P. Grillo, "Host Resources MIB", RFC 2790, Waldbusser, S., and P. Grillo, "Host Resources MIB", RFC 2790,
March 2000. March 2000.
[RFC2863] [RFC2863]
McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB", RFC McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB", RFC
2863, Cisco Systems, Argon Networks, June 2000. 2863, Cisco Systems, Argon Networks, June 2000.
[RFC3411]
Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Describing Simple Network Management Protocol (SNMP) Management
Frameworks", STD 58, RFC 3411, December 2002.
[FC-AL] [FC-AL]
"Information Technology - Fibre Channel - Arbitrated Loop (FC-AL)", "Information Technology - Fibre Channel - Arbitrated Loop (FC-AL)",
ANSI X3.272, 1996. ANSI X3.272, 1996.
[FC-AL-2] [FC-AL-2]
"Fibre Channel - Arbitrated Loop (FC-AL-2)", ANSI NCITS 332-1999, "Fibre Channel - Arbitrated Loop (FC-AL-2)", ANSI INCITS 332-1999,
1999. 1999.
[FC-BB] [FC-BB]
ANSI NCITS xxx-200x, "Fibre Channel - Backbone (FC-BB), T11/Project "Fibre Channel - Backbone (FC-BB)" ANSI INCITS 342-2001, 2001.
1238D/Rev 4.8", February 2001.
[FCP] [FCP]
"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 INCITS
TR-20-1998, 1998. TR-20-1998, 1998.
[FC-FS]
"Fibre Channel - Framing and Signaling (FC-FS)" ANSI INCITS
373-2003, April 2003.
[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)" ANSI INCITS
T11/Project 1356-D/Rev 7.01, 28 November 2000. 348-2001, 2001.
[FC-MI] [FC-MI]
"Fibre Channel - Methodologies for Interconnects Technical Report "Fibre Channel - Methodologies for Interconnects Technical Report
(FC-MI)" T11/Project 1377-DT/Rev 1.92, 4 December 2001. (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 INCITS 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)", ANSI INCITS
1305D/Rev 5.3, ANSI NCITS xxx-200x, June 2001. 355-2001, June 2001.
10. Informative References 10. Informative References
[RFC2741] [RFC2741]
Daniele, M., Wijnen, B., Ellison, M., and D. Francisco. "Agent Daniele, M., Wijnen, B., Ellison, M., and D. Francisco. "Agent
Extensibility (AgentX) Protocol Version 1", RFC 2741, January 2000. Extensibility (AgentX) Protocol Version 1", RFC 2741, January 2000.
[RFC2837] [RFC2837]
Teow, K., "Definitions of Managed Objects for the Fabric Element in Teow, K., "Definitions of Managed Objects for the Fabric Element in
Fibre Channel Standard", RFC 2837, May 2000. Fibre Channel Standard", RFC 2837, May 2000.
skipping to change at page 66, line 20 skipping to change at page 65, line 32
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 network
environments. For example, the ability to change network topology or environments. For example, the ability to change network topology or
network speed may afford an attacker the ability to obtain better network speed may afford an attacker the ability to obtain better
performance at the expense of other network users. The support for SET performance at the expense of other network users; setting
operations in a non-secure environment without proper protection can fcmSwitchDomainId to an invalid value could lead to denial of service in
have a negative effect on network operations. some configurations. The support for SET operations in a non-secure
environment without proper protection can have a negative 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 to
even encrypt the values of these objects when sending them over the even encrypt the values of these objects when sending them over the
network via SNMP. In particular, these objects provide information on network via SNMP. In particular, these objects provide information on
network topology: network topology:
fcmLinkEnd1NodeWwn fcmLinkEnd1NodeWwn
skipping to change at page 68, line 5 skipping to change at page 66, line 30
and privacy). and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED.
Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic
security. It is then a customer/operator responsibility to ensure that security. It is then a customer/operator responsibility to ensure that
the SNMP entity giving access to an instance of this MIB module is the SNMP entity giving access to an instance of this MIB module is
properly configured to give access to the objects only to those properly configured to give access to the objects only to those
principals (users) that have legitimate rights to indeed GET or SET principals (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
12. Comparison to draft-ietf-ipfc-fcmgmt-int-mib-07.txt 12. IANA Considerations
12.1. Problems with draft-ietf-ipfc-fcmgmt-int-mib-07.txt 12.1. OID Assignment
IANA is requested to make a MIB OID assignment under the transmission
branch. Specifically, for { transmission 56 } to be assigned as the OID
for fcMgmtMIB. This sub-identifier is requested because this MIB
contains the media-specific definitions which correspond to the ifType
value of fibreChannel(56).
12.2. FC Port Type Registry
IANA is requested to establish a registry for Fibre Channel Port Types.
The registry is to be split into disjoint subset ranges:
1) a 'standard' range for Fibre Channel Port Types which have been
standardized by the InterNational Committee for Information
Technology Standards (INCITS)'s Technical Committee T11 (see
http://www.incits.org/tc_home/t11.htm and
http://www.t11.org/index.htm). This range will be subject to the
'Expert Review' and 'Specification Required' policies described in
[RFC2434], with the following provisions:
- the Expert Reviewer is to be appointed by the IESG.
- the Expert Reviewer shall obtain approval (or rejection) from
INCITS Technical Committee T11 via the chair of that Committee.
Rejected values shall not be added to the registry.
- if the addition is approved, the Expert shall advise IANA of how
to record the reference to the T11 specification document which
describes the newly added port type(s), and which is considered
to be the "other permanent and readily available reference"
required by [RFC2434].
The initial assignments in the 'standard' range will be as follows:
Assigned
Value Type Meaning
-------- ------ -------
1 unknown for use when the type is not known,
or is "unidentified" as specified in
section 5.1.2.10 of [FC-GS-3]
2 other used for types without assigned values
3 -- an obsolete value, not to be re-assigned
4 N_Port see [FC-FS]
5 NL_Port see [FC-FS]
6 F_Port see [FC-FS]
7 FL_Port see [FC-FS]
8 E_Port see [FC-FS]
9 B_Port see [FC-FS]
10 G_Port see [FC-SW-3]
11 GL_Port see [FC-SW-3]
12 F/NL_Port see [FC-AL-2]
It is suggested that the above range can be extended up to a maximum
of 9,999.
2) a range which is assigned under the "Private Use" policy described in
[RFC2434] and is for values intended for private use by one party or
among mutually consenting parties. It is suggested that values in
this range extend from 10,000 to 99,999. IANA is instructed not to
make any allocations from this range.
3) values larger than 99,999 be RESERVED.
13. Comparison to draft-ietf-ipfc-fcmgmt-int-mib-07.txt
13.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 69, line 5 skipping to change at page 70, 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.
12.2. Detailed Changes 13.2. Detailed Changes
12.2.1. Removal of Sensor-related objects 13.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
12.2.2. Removal of Trap-registration objects 13.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)
12.2.3. Removal of Event-related objects 13.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
12.2.4. Removal of inventory-related information 13.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
12.2.5. Removal of revision numbers 13.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
12.2.6. Removal of other not FC-specific information 13.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
12.2.7. Clean-up of ambiguous/obsolete definitions 13.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)
12.2.8. Use of an ifTable entry 13.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 72, line 13 skipping to change at page 73, 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
12.2.9. Removed because of AgentX difficulty 13.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
12.2.10. FC Management Instance 13.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 73, line 9 skipping to change at page 74, 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".
12.2.11. Counter Syntax 13.2.11. Counter Syntax
All packet and octet counters have been changed to be Counter64's (but 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). Counter32 versions of them are also included for use by old agents).
The error counters have been changed to Counter32's. (In the probably 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
occurrence of errors, even on a 10Gbs Fibre Channel interface, might occurrence of errors, even on a 10Gbs Fibre Channel interface, might
wrap faster than a hour, the fact that errors are occurring will almost wrap 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.)
12.2.12. Obsolete/Little-Used Fibre Channel features 13.2.12. Obsolete/Little-Used Fibre Channel features
Information relating to Fibre Channel features which are obsolete or not Information relating to Fibre Channel features which are obsolete or not
widely-implemented has been deleted. (For more information, see section widely-implemented has been deleted. (For more information, see section
6.2.1 and section 6.2.2 of [FC-MI].) 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
skipping to change at page 73, line 42 skipping to change at page 74, line 42
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 these objects:
connUnitPortStatCountFBSYFrames connUnitPortStatCountFBSYFrames
connUnitPortStatCountPBSYFrames connUnitPortStatCountPBSYFrames
connUnitPortStatCountFRJTFrames connUnitPortStatCountFRJTFrames
connUnitPortStatCountPRJTFrames connUnitPortStatCountPRJTFrames
have been deleted. 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 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.
12.4. Additional objects 13.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 counters,
has been added. has been added.
13. Comparison to RFC 2837 14. 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.
14. Author's Address 15. 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
15. Full Copyright Statement 16. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2004). 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
or references to the Internet Society or other Internet organizations, or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in except as needed for the purpose of developing Internet standards in
 End of changes. 

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