As per Relevance of the word attached, we have this rfc below:
Network Working Group K. S.
Request for Comments: 2837 Brocade Communications Systems, Inc
Category: Standards Track May 2000
Definitions of Managed
for the Fabric Element in Fibre Channel
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This memo defines an extension to the Management Information
(MIB) for use with network management protocols in TCP/IP-
internets. In particular, it defines the objects for managing
operations of the Fabric Element portion of the Fibre
Standards
Table of
1. The SNMP Management Framework ..................................2
2. Overview .......................................................3
2.1 Management View of a Fabric Element ...........................4
2.2 Structure of the Fabric Element MIB ...........................5
3. Object Definitions .............................................6
The Configuration Group ......................................8
The Module Table ...........................................9
The FxPort Configuration Table ............................12
The Status Group ............................................16
The FxPort Status Table ...................................16
The FxPort Physical Level Table ...........................18
The FxPort Fabric Login Table .............................20
The Error Group .............................................24
The Accounting Groups........................................27
The Class 1 Accounting Table ..............................27
The Class 2 Accounting Table ..............................31
The Class 3 Accounting Table ..............................33
The Capability Group ........................................35
Teow Standards Track [Page 1]
RFC 2837 FC Fabric Element MIB May 2000
Conformance information .....................................38
4. Security Considerations .......................................43
5. Intellectual Property .........................................44
6. Acknowledgements ..............................................44
7. References ....................................................45
7.1 IETF References ..............................................45
7.2 Approved ANSI/NCITS References ...............................46
7.3 ANSI/NCITS References Under Development ......................47
8. Editors' Addresses ............................................47
9. Full Copyright Statement ......................................48
1. The SNMP Management
The SNMP Management Framework presently consists of five
components
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for
purpose of management. The first version of this Structure
Management Information (SMI) is called SMIv1 and described in
16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
second version, called SMIv2, is described in STD 58, RFC 2578
[5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].
o Message protocols for transferring management information.
first version of the SNMP message protocol is called SNMPv1
described in STD 15, RFC 1157 [8]. A second version of the
message protocol, which is not an Internet standards
protocol, is called SNMPv2c and described in RFC 1901 [9] and
1906 [10]. The third version of the message protocol is
SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
[12].
o Protocol operations for accessing management information.
first set of protocol operations and associated PDU formats
described in STD 15, RFC 1157 [8]. A second set of
operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2573 [14]
the view-based access control mechanism described in RFC 2575
[15].
A more detailed introduction to the current SNMP Management
can be found in RFC 2570 [16].
Teow Standards Track [Page 2]
RFC 2837 FC Fabric Element MIB May 2000
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the mechanisms defined in the SMI
This memo specifies a MIB module that is compliant to the SMIv2.
MIB conforming to the SMIv1 can be produced through the
translations. The resulting translated MIB must be
equivalent, except where objects or events are omitted because
translation is possible (use of Counter64). Some machine
information in SMIv2 will be converted into textual descriptions
SMIv1 during the translation process. However, this loss of
readable information is not considered to change the semantics of
MIB
2.
A Fibre Channel Fabric is an entity which interconnects Node
(N_Ports) or Node Loop Ports (NL_Ports). It provides transport
routing functions. In essence, a Fabric is a network of N_
and/or NL_Ports to communicate with one another. A Fabric
composed of one or more Fabric Element that are interconnected
Inter-element Links (IEL). A Fabric Element is the smallest unit
a Fabric that meets the definition of a Fabric. It must consist
at least three external ports to connect to either N_Ports, NL_
or other Fabric Elements. In general, a Fabric Element port may
of one of the following types
(1) F_Port, a fabric port to connect to an N_Port ([17], [21], [22]);
(2) FL_Port, a fabric port that also supports a FC Arbitrated
consisting of one or more NL_Ports ([20], [24]).
(3) E_Port, an expansion port to connect to another Fabric
([18], [23]);
This memo shall define objects related to a Fabric Element,
F_Ports and FL_Ports. Objects related to other types of FC
shall be defined in future
For the rest of the document, the term, "FxPort", will be used
refer to both F_Port and FL_Port where the distinction is
necessary. The term, "NxPort" will be used to refer to both N_
and NL_Port in the similar fashion
Teow Standards Track [Page 3]
RFC 2837 FC Fabric Element MIB May 2000
2.1. Management View of a Fabric
From the management perspective, it is helpful to view a
Element to be consisting of multiple "modules". Each module is
grouping, either physical or logical, of one or more ports that
be managed as a sub-entity within the Fabric Element
This module mapping is recommended but optional. A vendor may
to put all ports into a single module, or to divide the ports
modules that do not match physical divisions
The object fcFeModuleCapacity indicates the maximum number of
that a given Fabric Element may contain. This value must
constant from one management restart to the next
Each module is uniquely identified by a module number in the range
1 through fcFeModuleCapacity inclusive. Modules may come and
without causing a management reset (of sysUpTime), and may
sparsely numbered within the Fabric Element. That is, the
numbering is not required to be contiguous. For instance, if
module is mapped physically to a field-replaceable card and in a 13-
card cage Fabric Element, cards 3, 5, 6 and 7 may be installed.
vendor may choose to label them as modules 3, 5, 6 and 7
respectively. In this example, the value of fcFeModuleCapacity
13. Note that the object fcFeModuleLastChange acts as
discontinuity indicator for all counter objects in this MIB
A Fabric Element may also provide a proxy management on behalf
another management entity by presenting it as one of its
Element modules
The object fcFeModuleFxPortCapacity indicates the maximum number
ports that a given module may contain. The value
fcFeModuleFxPortCapacity must not change for a given module
However, a module may be deleted from the Fabric Element and
with a module containing a different number of ports. The value
fcFeModuleLastChange will indicate that a change took place
Each port within the Fabric Element is uniquely identified by
combination of module index and port index, where port index is
integer in the range (1..fcFeModuleFxPortCapacity). As with
within a Fabric Element, ports within a module may be
numbered. That is the port numbering is not required to
contiguous. Likewise, ports may come and go within a module
causing a management reset
Teow Standards Track [Page 4]
RFC 2837 FC Fabric Element MIB May 2000
In terms of attachment, an F_Port will be attached to another N_Port
and an FL_Port will be attached to one or up to 126 NL_Ports.
general, an FxPort may be attached to one or more NxPorts.
NxPort associated with an FxPort will be uniquely identified by
combination of module index, FxPort index and NxPort index.
NxPort index is an integer in the range (1..126). The
diagram illustrates the management view of a Fabric Element
#=======================================================#
# +----------------- - - - -----------------+ #
# | Module 1 [1] . . . [i] | #
# +----------------- - - - -----------------+ #
# o o o #
# +---------------------- - - - --------+ #
# | Module M [1] . . . [n] | #
# +---------------------- - - - -----^--+ #
#=====================================|=================#
|
One or more NxPorts { [1] . . . [L] }<-+
- - - - - - - - -
where "i", "n", "M" and "L" are some arbitrary sample integer values
and "L" must be less than 127.
2.2. Structure of the Fabric Element
This memo assumes that a Fabric Element has an SNMP entity
with its managed objects. The managed objects are divided as follow
- the Configuration
- the Status
- the Error
- the Accounting
- the Capability
In each group, scalar objects and table entries are defined
The Configuration group contains configuration and service
for the Fabric Element, modules and the FxPorts
The Operation group contains the operational status and parameters
an FxPort. The group also contains the service parameters that
been established between the FxPort and its attached NxPort,
applicable
The Error group contains counters tracking various types of
detected by each FxPort. The information may be used for
and/or to derive the quality of the link between an FxPort and one
more attached NxPorts
Teow Standards Track [Page 5]
RFC 2837 FC Fabric Element MIB May 2000
The Accounting group contains statistic data suitable for
accounting and performance information
The Capability group contains parameters indicating the
capability of the Fabric Element and each FxPort
3. Object
FIBRE-CHANNEL-FE-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE
Unsigned32, Counter32, Gauge32, Integer32, mib-2
FROM SNMPv2-
TEXTUAL-CONVENTION, TruthValue,
FROM SNMPv2-
FROM SNMP-FRAMEWORK-MIB -- rfc2571
MODULE-COMPLIANCE, OBJECT-
FROM SNMPv2-CONF
fcFeMIB MODULE-
LAST-UPDATED "200005180000Z
ORGANIZATION "IETF IPFC Working Group
CONTACT-INFO "Kha Sin
Brocade Communications Systems
1901 Guadalupe Parkway
San Jose, CA 95131
U.S.
Tel: +1 408 487 8180
Fax: +1 408 487 8190
Email: khasin@Brocade.
WG Mailing list:ipfc@standards.gadzoox.
To Subscribe: ipfc-request@standards.gadzoox.
In Body: subscribe
DESCRIPTION "The MIB module for Fibre Channel Fabric Element."
REVISION "200005180000Z
DESCRIPTION "Initial revision, published as RFC 2837."
::= { mib-2 75 }
fcFeMIBObjects OBJECT IDENTIFIER ::= { fcFeMIB 1 }
-- Note
-- fcFeMIBConformance OBJECT IDENTIFIER ::= { fcFeMIB 2 }
-- see at the end of the
-- Groups under
Teow Standards Track [Page 6]
RFC 2837 FC Fabric Element MIB May 2000
fcFeConfig OBJECT IDENTIFIER ::= { fcFeMIBObjects 1 }
fcFeStatus OBJECT IDENTIFIER ::= { fcFeMIBObjects 2 }
fcFeError OBJECT IDENTIFIER ::= { fcFeMIBObjects 3 }
fcFeAccounting OBJECT IDENTIFIER ::= { fcFeMIBObjects 4 }
fcFeCapabilities OBJECT IDENTIFIER ::= { fcFeMIBObjects 5 }
-- Textual
MilliSeconds ::= TEXTUAL-
STATUS
DESCRIPTION "Represents time unit value in milliseconds."
SYNTAX Unsigned32
MicroSeconds ::= TEXTUAL-
STATUS
DESCRIPTION "Represents time unit value in microseconds."
SYNTAX Unsigned32
FcNameId ::= TEXTUAL-
STATUS
DESCRIPTION "Represents the Worldwide Name associated
a Fibre Channel (FC) entity."
SYNTAX OCTET STRING (SIZE (8))
FcAddressId ::= TEXTUAL-
STATUS
DESCRIPTION "Represents Fibre Channel Address ID, a 24-
value unique within the address space of a Fabric."
SYNTAX OCTET STRING (SIZE (3))
FcRxDataFieldSize ::= TEXTUAL-
STATUS
DESCRIPTION "Represents the receive data field size of
NxPort or FxPort."
SYNTAX Integer32 (128..2112)
FcBbCredit ::= TEXTUAL-
STATUS
DESCRIPTION "Represents the buffer-to-buffer credit of
NxPort or FxPort."
SYNTAX Integer32 (0..32767)
FcphVersion ::= TEXTUAL-
STATUS
DESCRIPTION "Represents the version of FC-PH supported by
NxPort or FxPort."
SYNTAX Integer32 (0..255)
FcStackedConnMode ::= TEXTUAL-
Teow Standards Track [Page 7]
RFC 2837 FC Fabric Element MIB May 2000
STATUS
DESCRIPTION "Represents an enumerated value used to
the Class 1 Stacked Connect Mode supported
an NxPort or FxPort."
SYNTAX INTEGER {
none(1),
transparent(2),
lockedDown(3)
}
FcCosCap ::= TEXTUAL-
STATUS
DESCRIPTION "Represents the class of service capability of
NxPort or FxPort."
SYNTAX BITS { classF(0), class1(1), class2(2), class3(3),
class4(4), class5(5), class6(6) }
FcFeModuleCapacity ::= TEXTUAL-
STATUS
DESCRIPTION "Represents the maximum number of modules
a Fabric Element."
SYNTAX Unsigned32
FcFeFxPortCapacity ::= TEXTUAL-
STATUS
DESCRIPTION "Represents the maximum number of FxPorts
a module."
SYNTAX Unsigned32
FcFeModuleIndex ::= TEXTUAL-
STATUS
DESCRIPTION "Represents the module index within a conceptual table."
SYNTAX Unsigned32
FcFeFxPortIndex ::= TEXTUAL-
STATUS
DESCRIPTION "Represents the FxPort index within a conceptual table."
SYNTAX Unsigned32
FcFeNxPortIndex ::= TEXTUAL-
STATUS
DESCRIPTION "Represents the NxPort index within a conceptual table."
SYNTAX Integer32 (1..126)
FcBbCreditModel ::= TEXTUAL-
STATUS
DESCRIPTION "Represents the BB_Credit model of an FxPort."
SYNTAX INTEGER { regular(1), alternate (2) }
Teow Standards Track [Page 8]
RFC 2837 FC Fabric Element MIB May 2000
-- The Configuration
-- This group consists of scalar objects and tables
-- It contains the configuration and service
-- of the Fabric Element and the FxPorts
-- The group represents a set of parameters associated
-- the Fabric Element or an FxPort to support its NxPorts
fcFeFabricName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The Name_Identifier of the Fabric to which this
Element belongs."
::= { fcFeConfig 1 }
fcFeElementName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The Name_Identifier of the Fabric Element."
::= { fcFeConfig 2 }
fcFeModuleCapacity OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The maximum number of modules in the Fabric Element
regardless of their current state."
::= { fcFeConfig 3 }
-- The Module Table
-- This table contains one entry for each module
-- information of the modules
fcFeModuleTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A table that contains, one entry for each module in
Fabric Element, information of the modules."
::= { fcFeConfig 4 }
fcFeModuleEntry OBJECT-
Teow Standards Track [Page 9]
RFC 2837 FC Fabric Element MIB May 2000
SYNTAX
MAX-ACCESS not-
STATUS
"An entry containing the configuration parameters of
module."
INDEX { fcFeModuleIndex }
::= { fcFeModuleTable 1 }
FcFeModuleEntry ::=
SEQUENCE {
FcFeModuleIndex
SnmpAdminString
OBJECT IDENTIFIER
INTEGER
TimeStamp
FcFeFxPortCapacity
}
fcFeModuleIndex OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"This object identifies the module within the Fabric
for which this entry contains information. This value
never greater than fcFeModuleCapacity."
::= { fcFeModuleEntry 1 }
fcFeModuleDescr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A textual description of the module. This value
include the full name and version identification of
module."
::= { fcFeModuleEntry 2 }
Teow Standards Track [Page 10]
RFC 2837 FC Fabric Element MIB May 2000
fcFeModuleObjectID OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
"The vendor's authoritative identification of the module
This value may be allocated within the SMI
subtree (1.3.6.1.4.1) and provides a straight-forward
unambiguous means for determining what kind of module
being managed
For example, this object could take the
1.3.6.1.4.1.99649.3.9 if vendor 'Neufe Inc.' was
the subtree 1.3.6.1.4.1.99649, and had assigned
identifier 1.3.6.1.4.1.99649.3.9 to its 'FeFiFo-16
PlugInCard.'"
::= { fcFeModuleEntry 3 }
fcFeModuleOperStatus OBJECT-
SYNTAX INTEGER {
online (1), --
offline (2), -- not
testing (3), -- under
faulty (4) --
}
MAX-ACCESS read-
STATUS
"This object indicates the operational status of the module
online(1) the module is functioning properly
offline(2) the module is not available
testing(3) the module is under testing;
faulty(4) the module is defective in some way."
::= { fcFeModuleEntry 4 }
fcFeModuleLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object contains the value of sysUpTime when the
entered its current operational status. A value of
indicates that the operational status of the module has
changed since the agent last restarted."
::= { fcFeModuleEntry 5 }
fcFeModuleFxPortCapacity OBJECT-
SYNTAX
Teow Standards Track [Page 11]
RFC 2837 FC Fabric Element MIB May 2000
MAX-ACCESS read-
STATUS
"The number of FxPort that can be contained within
module. Within each module, the ports are uniquely
in the range from 1 to fcFeModuleFxPortCapacity inclusive
However, the numbers are not required to be contiguous."
::= { fcFeModuleEntry 6 }
fcFeModuleName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The Name_Identifier of the module."
::= { fcFeModuleEntry 7 }
-- the FxPort Configuration Table
-- This table contains, one entry for each FxPort
-- configuration parameters of the ports
fcFxPortTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A table that contains, one entry for each FxPort in
Fabric Element, configuration and service parameters of
FxPorts."
::= { fcFeConfig 5 }
fcFxPortEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry containing the configuration and service
of a FxPort."
INDEX { fcFeModuleIndex, fcFxPortIndex }
::= { fcFxPortTable 1 }
FcFxPortEntry ::=
SEQUENCE {
FcFeFxPortIndex
FcNameId
Teow Standards Track [Page 12]
RFC 2837 FC Fabric Element MIB May 2000
-- FxPort common service
FcphVersion
FcphVersion
FcBbCredit
FcRxDataFieldSize
MilliSeconds
MilliSeconds
-- FxPort class service
FcCosCap
TruthValue
FcStackedConnMode
fcFxPortClass2
TruthValue
fcFxPortClass3
TruthValue
-- other configuration
}
fcFxPortIndex OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"This object identifies the FxPort within the module.
number ranges from 1 to the value of
for the associated module. The value remains constant
the identified FxPort until the module is re-initialized."
::= { fcFxPortEntry 1 }
fcFxPortName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The World_wide Name of this FxPort. Each FxPort has
unique Port World_wide Name within the Fabric."
::= { fcFxPortEntry 2 }
Teow Standards Track [Page 13]
RFC 2837 FC Fabric Element MIB May 2000
-- FxPort common service
fcFxPortFcphVersionHigh OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The highest or most recent version of FC-PH that the
is configured to support."
::= { fcFxPortEntry 3 }
fcFxPortFcphVersionLow OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The lowest or earliest version of FC-PH that the FxPort
configured to support."
::= { fcFxPortEntry 4 }
fcFxPortBbCredit OBJECT-
SYNTAX
UNITS "buffers
MAX-ACCESS read-
STATUS
"The total number of receive buffers available for
Class 1 connect-request, Class 2 or 3 frames from
attached NxPort. It is for buffer-to-buffer flow
in the direction from the attached NxPort (if applicable
to FxPort."
::= { fcFxPortEntry 5 }
fcFxPortRxBufSize OBJECT-
SYNTAX
UNITS "bytes
MAX-ACCESS read-
STATUS
"The largest Data_Field Size (in octets) for an FT_1
that can be received by the FxPort."
::= { fcFxPortEntry 6 }
fcFxPortRatov OBJECT-
SYNTAX
UNITS "milliseconds
MAX-ACCESS read-
STATUS
Teow Standards Track [Page 14]
RFC 2837 FC Fabric Element MIB May 2000
"The Resource_Allocation_Timeout Value configured for
FxPort. This is used as the timeout value for
when to reuse an NxPort resource such as
Recovery_Qualifier. It represents E_D_TOV (see
object) plus twice the maximum time that a frame may
delayed within the Fabric and still be delivered."
::= { fcFxPortEntry 7 }
fcFxPortEdtov OBJECT-
SYNTAX
UNITS "milliseconds
MAX-ACCESS read-
STATUS
"The E_D_TOV value configured for the FxPort.
Error_Detect_Timeout Value is used as the timeout value
detecting an error condition."
::= { fcFxPortEntry 8 }
-- FxPort class service
fcFxPortCosSupported OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A value indicating the set of Classes of Service
by the FxPort."
::= { fcFxPortEntry 9 }
fcFxPortIntermixSupported OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A flag indicating whether or not the FxPort supports
Intermixed Dedicated Connection."
::= { fcFxPortEntry 10 }
fcFxPortStackedConnMode OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A value indicating the mode of Stacked Connect supported
the FxPort."
Teow Standards Track [Page 15]
RFC 2837 FC Fabric Element MIB May 2000
::= { fcFxPortEntry 11 }
fcFxPortClass2SeqDeliv OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A flag indicating whether or not Class 2
Delivery is supported by the FxPort."
::= { fcFxPortEntry 12 }
fcFxPortClass3SeqDeliv OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A flag indicating whether or not Class 3
Delivery is supported by the FxPort."
::= { fcFxPortEntry 13 }
-- other FxPort
fcFxPortHoldTime OBJECT-
SYNTAX
UNITS "microseconds
MAX-ACCESS read-
STATUS
"The maximum time (in microseconds) that the FxPort
hold a frame before discarding the frame if it is unable
deliver the frame. The value 0 means that the FxPort
not support this parameter."
::= { fcFxPortEntry 14 }
-- the Status
-- This group consists of tables that contains
-- status and established service parameters for the
-- Element and the attached NxPorts
-- The FxPort Status
-- This table contains, one entry for each FxPort
-- the operational status and parameters of the FxPorts
fcFxPortStatusTable OBJECT-
SYNTAX SEQUENCE OF
Teow Standards Track [Page 16]
RFC 2837 FC Fabric Element MIB May 2000
MAX-ACCESS not-
STATUS
"A table that contains, one entry for each FxPort in
Fabric Element, operational status and parameters of
FxPorts."
::= { fcFeStatus 1 }
fcFxPortStatusEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry containing operational status and parameters of
FxPort."
AUGMENTS { fcFxPortEntry }
::= { fcFxPortStatusTable 1 }
FcFxPortStatusEntry ::=
SEQUENCE {
FcAddressId
Gauge32,
INTEGER
}
fcFxPortID OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The address identifier by which this FxPort is
within the Fabric. The FxPort may assign its
identifier to its attached NxPort(s) during Fabric Login."
::= { fcFxPortStatusEntry 1 }
fcFxPortBbCreditAvailable OBJECT-
SYNTAX Gauge32
UNITS "buffers
MAX-ACCESS read-
STATUS
"The number of buffers currently available for
Teow Standards Track [Page 17]
RFC 2837 FC Fabric Element MIB May 2000
frames from the attached port in the buffer-to-buffer
control. The value should be less than or equal
fcFxPortBbCredit."
::= { fcFxPortStatusEntry 2 }
fcFxPortOperMode OBJECT-
SYNTAX INTEGER { unknown(1), fPort(2), flPort(3) }
MAX-ACCESS read-
STATUS
"The current operational mode of the FxPort."
::= { fcFxPortStatusEntry 3 }
fcFxPortAdminMode OBJECT-
SYNTAX INTEGER { fPort(2), flPort(3) }
MAX-ACCESS read-
STATUS
"The desired operational mode of the FxPort."
::= { fcFxPortStatusEntry 4 }
-- the FxPort Physical Level
-- This table contains, one entry for each FxPort in
-- Fabric Element, the physical level status and
-- of the FxPorts
fcFxPortPhysTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A table that contains, one entry for each FxPort in
Fabric Element, physical level status and parameters of
FxPorts."
::= { fcFeStatus 2 }
fcFxPortPhysEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry containing physical level status and parameters
a FxPort."
AUGMENTS { fcFxPortEntry }
::= { fcFxPortPhysTable 1 }
FcFxPortPhysEntry ::=
Teow Standards Track [Page 18]
RFC 2837 FC Fabric Element MIB May 2000
SEQUENCE {
INTEGER
INTEGER
TimeStamp
}
fcFxPortPhysAdminStatus OBJECT-
SYNTAX INTEGER {
online (1), -- place port
offline (2), -- take port
testing (3) -- initiate test
}
MAX-ACCESS read-
STATUS
"The desired state of the FxPort. A management station
place the FxPort in a desired state by setting this
accordingly. The testing(3) state indicates that
operational frames can be passed. When a Fabric
initializes, all FxPorts start with
in the offline(2) state. As the result of either
management action or per configuration
accessible by the Fabric Element,
is then changed to either the online(1) or testing(3)
states, or remains in the offline state."
::= { fcFxPortPhysEntry 1 }
fcFxPortPhysOperStatus OBJECT-
SYNTAX INTEGER {
online (1), -- Login may
offline (2), -- Login cannot
testing (3), -- port is under
linkFailure (4) -- failure after online/
}
MAX-ACCESS read-
STATUS
"The current operational status of the FxPort.
testing(3) indicates that no operational frames can
passed. If fcFxPortPhysAdminStatus is offline(2)
fcFxPortPhysOperStatus should be offline(2).
fcFxPortPhysAdminStatus is changed to online(1)
fcFxPortPhysOperStatus should change to online(1) if
Teow Standards Track [Page 19]
RFC 2837 FC Fabric Element MIB May 2000
FxPort is ready to accept Fabric Login request from
attached NxPort; it should proceed and remain in the link
failure(4) state if and only if there is a fault
prevents it from going to the online(1) state."
::= { fcFxPortPhysEntry 2 }
fcFxPortPhysLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime at the time the FxPort entered
current operational status. A value of zero indicates
the FxPort's operational status has not changed since
agent last restarted."
::= { fcFxPortPhysEntry 3 }
fcFxPortPhysRttov OBJECT-
SYNTAX
UNITS "milliseconds
MAX-ACCESS read-
STATUS
"The Receiver_Transmitter_Timeout value of the FxPort.
is used by the receiver logic to detect Loss
Synchronization."
::= { fcFxPortPhysEntry 4 }
-- The FxPort Fabric Login
--
-- This table contains, one entry for each FxPort in
-- Fabric Element, the Service Parameters that have
-- established from the most recent Fabric Login
-- implicit or explicit
fcFxLoginTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A table that contains, one entry for each NxPort
to a particular FxPort in the Fabric Element,
parameters established from the most recent Fabric Login
explicit or implicit. Note that an FxPort may have one
more NxPort attached to it."
::= { fcFeStatus 3 }
Teow Standards Track [Page 20]
RFC 2837 FC Fabric Element MIB May 2000
fcFxLoginEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry containing service parameters established from
successful Fabric Login."
INDEX { fcFeModuleIndex, fcFxPortIndex, fcFxPortNxLoginIndex }
::= { fcFxLoginTable 1 }
FcFxLoginEntry ::=
SEQUENCE {
FcFeNxPortIndex
FcphVersion
FcBbCredit
FcRxDataFieldSize
FcCosCap
TruthValue
FcStackedConnMode
fcFxPortClass2
TruthValue
fcFxPortClass3
TruthValue
--
FcNameId
FcAddressId
}
fcFxPortNxLoginIndex OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The object identifies the associated NxPort in
attachment for which the entry contains information."
::= { fcFxLoginEntry 1 }
Teow Standards Track [Page 21]
RFC 2837 FC Fabric Element MIB May 2000
fcFxPortFcphVersionAgreed OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The version of FC-PH that the FxPort has agreed to
from the Fabric Login
::= { fcFxLoginEntry 2 }
fcFxPortNxPortBbCredit OBJECT-
SYNTAX
UNITS "buffers
MAX-ACCESS read-
STATUS
"The total number of buffers available for holding Class 1
connect-request, Class 2 or Class 3 frames to
transmitted to the attached NxPort. It is for buffer-to
buffer flow control in the direction from FxPort to NxPort
The buffer-to-buffer flow control mechanism is indicated
the respective fcFxPortBbCreditModel."
::= { fcFxLoginEntry 3 }
fcFxPortNxPortRxDataFieldSize OBJECT-
SYNTAX
UNITS "bytes
MAX-ACCESS read-
STATUS
"The Receive Data Field Size of the attached NxPort.
object specifies the largest Data Field Size for an FT_1
frame that can be received by the NxPort."
::= { fcFxLoginEntry 4 }
fcFxPortCosSuppAgreed OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A variable indicating that the attached NxPort
requested the FxPort for the support of classes of
and the FxPort has granted the request."
::= { fcFxLoginEntry 5 }
fcFxPortIntermixSuppAgreed OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
Teow Standards Track [Page 22]
RFC 2837 FC Fabric Element MIB May 2000
"A variable indicating that the attached NxPort
requested the FxPort for the support of Intermix and
FxPort has granted the request. This flag is only valid
Class 1 service is supported."
::= { fcFxLoginEntry 6 }
fcFxPortStackedConnModeAgreed OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A variable indicating whether the FxPort has agreed
support stacked connect from the Fabric Login. This is
meaningful if Class 1 service has been agreed."
::= { fcFxLoginEntry 7 }
fcFxPortClass2SeqDelivAgreed OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A variable indicating whether the FxPort has agreed
support Class 2 sequential delivery from the Fabric Login
This is only meaningful if Class 2 service has
agreed."
::= { fcFxLoginEntry 8 }
fcFxPortClass3SeqDelivAgreed OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A flag indicating whether the FxPort has agreed to
Class 3 sequential delivery from the Fabric Login. This
only meaningful if Class 3 service has been agreed."
::= { fcFxLoginEntry 9 }
fcFxPortNxPortName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The port name of the attached NxPort."
::= { fcFxLoginEntry 10 }
fcFxPortConnectedNxPort OBJECT-
SYNTAX
Teow Standards Track [Page 23]
RFC 2837 FC Fabric Element MIB May 2000
MAX-ACCESS read-
STATUS
"The address identifier of the destination NxPort with
this FxPort is currently engaged in a either a Class 1
loop connection. If this FxPort is not engaged in
connection, then the value of this object is '000000'H."
::= { fcFxLoginEntry 11 }
fcFxPortBbCreditModel OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object identifies the BB_Credit model used by
FxPort."
::= { fcFxLoginEntry 12 }
-- the Error
-- This group consists of tables that contain information
-- the various types of errors detected. The management
-- may use the information in this group to determine
-- quality of the link between the FxPort and its attached NxPort
-- the FxPort Error
-- This table contains, one entry for each FxPort in the
-- Element, counters recording numbers of errors
-- since the management agent re-initialized
-- The first 6 columnar objects after the port index
-- to the counters in the Link Error Status Block
fcFxPortErrorTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A table that contains, one entry for each FxPort,
that record the numbers of errors detected."
::= { fcFeError 1 }
fcFxPortErrorEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry containing error counters of a FxPort."
AUGMENTS { fcFxPortEntry }
Teow Standards Track [Page 24]
RFC 2837 FC Fabric Element MIB May 2000
::= { fcFxPortErrorTable 1 }
FcFxPortErrorEntry ::=
SEQUENCE {
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32,
Counter32
}
fcFxPortLinkFailures OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of link failures detected by this FxPort."
::= { fcFxPortErrorEntry 1 }
fcFxPortSyncLosses OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of loss of synchronization detected by
FxPort."
::= { fcFxPortErrorEntry 2 }
Teow Standards Track [Page 25]
RFC 2837 FC Fabric Element MIB May 2000
fcFxPortSigLosses OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of loss of signal detected by the FxPort."
::= { fcFxPortErrorEntry 3 }
fcFxPortPrimSeqProtoErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of primitive sequence protocol errors
by the FxPort."
::= { fcFxPortErrorEntry 4 }
fcFxPortInvalidTxWords OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of invalid transmission word detected by
FxPort."
::= { fcFxPortErrorEntry 5 }
fcFxPortInvalidCrcs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of invalid CRC detected by this FxPort."
::= { fcFxPortErrorEntry 6 }
fcFxPortDelimiterErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Delimiter Errors detected by this FxPort."
::= { fcFxPortErrorEntry 7 }
fcFxPortAddressIdErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of address identifier errors detected by
Teow Standards Track [Page 26]
RFC 2837 FC Fabric Element MIB May 2000
FxPort."
::= { fcFxPortErrorEntry 8 }
fcFxPortLinkResetIns OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Link Reset Protocol received by this
from the attached NxPort."
::= { fcFxPortErrorEntry 9 }
fcFxPortLinkResetOuts OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Link Reset Protocol issued by this FxPort
the attached NxPort."
::= { fcFxPortErrorEntry 10 }
fcFxPortOlsIns OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Offline Sequence received by this FxPort."
::= { fcFxPortErrorEntry 11 }
fcFxPortOlsOuts OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Offline Sequence issued by this FxPort."
::= { fcFxPortErrorEntry 12 }
-- Accounting Groups
-- (1) Class 1 Accounting Group
-- (2) Class 2 Accounting Group,
-- (3) Class 3 Accounting Group
-- Each group consists of a table that contains
-- information for the FxPorts in the Fabric Element
-- the Class 1 Accounting
-- This table contains, one entry for each FxPort in the
Teow Standards Track [Page 27]
RFC 2837 FC Fabric Element MIB May 2000
-- Element, Counter32s for certain types of events occurred in
-- the FxPorts since the the management agent has re-initialized
fcFxPortC1AccountingTable OBJECT-
SYNTAX SEQUENCE OF FcFxPortC1
MAX-ACCESS not-
STATUS
"A table that contains, one entry for each FxPort in
Fabric Element, Class 1 accounting information
since the management agent has re-initialized."
::= { fcFeAccounting 1 }
fcFxPortC1AccountingEntry OBJECT-
SYNTAX FcFxPortC1
MAX-ACCESS not-
STATUS
"An entry containing Class 1 accounting information for
FxPort."
AUGMENTS { fcFxPortEntry }
::= { fcFxPortC1AccountingTable 1 }
FcFxPortC1AccountingEntry ::=
SEQUENCE {
fcFxPortC1
Counter32,
fcFxPortC1
Counter32,
fcFxPortC1
Counter32,
fcFxPortC1
Counter32,
fcFxPortC1
Counter32,
fcFxPortC1
Counter32,
fcFxPortC1
Counter32,
fcFxPortC1
Counter32,
fcFxPortC1
Counter32,
fcFxPortC1
}
Teow Standards Track [Page 28]
RFC 2837 FC Fabric Element MIB May 2000
fcFxPortC1InFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 1 frames (other than Class 1 connect
request) received by this FxPort from its attached NxPort."
::= { fcFxPortC1AccountingEntry 1 }
fcFxPortC1OutFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 1 frames (other than Class 1 connect
request) delivered through this FxPort to its
NxPort."
::= { fcFxPortC1AccountingEntry 2 }
fcFxPortC1InOctets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 1 frame octets, including the
delimiters, received by this FxPort from its
NxPort."
::= { fcFxPortC1AccountingEntry 3 }
fcFxPortC1OutOctets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 1 frame octets, including the
delimiters, delivered through this FxPort its
NxPort."
::= { fcFxPortC1AccountingEntry 4 }
fcFxPortC1Discards OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 1 frames discarded by this FxPort."
::= { fcFxPortC1AccountingEntry 5 }
fcFxPortC1FbsyFrames OBJECT-
Teow Standards Track [Page 29]
RFC 2837 FC Fabric Element MIB May 2000
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of F_BSY frames generated by this FxPort
Class 1 connect-request."
::= { fcFxPortC1AccountingEntry 6 }
fcFxPortC1FrjtFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of F_RJT frames generated by this FxPort
Class 1 connect-request."
::= { fcFxPortC1AccountingEntry 7 }
fcFxPortC1InConnections OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 1 connections successfully
in which the attached NxPort is the source of the connect
request."
::= { fcFxPortC1AccountingEntry 8 }
fcFxPortC1OutConnections OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 1 connections successfully
in which the attached NxPort is the destination of
connect-request."
::= { fcFxPortC1AccountingEntry 9 }
fcFxPortC1ConnTime OBJECT-
SYNTAX
UNITS "milliseconds
MAX-ACCESS read-
STATUS
"The cumulative time that this FxPort has been engaged
Class 1 connection. The amount of time is counted
after a connect-request has been accepted until
connection is disengaged, either by an EOFdt or
Reset."
Teow Standards Track [Page 30]
RFC 2837 FC Fabric Element MIB May 2000
::= { fcFxPortC1AccountingEntry 10 }
-- the Class 2 Accounting
-- This table contains, one entry for each FxPort in the
-- Element, Counter32s for certain types of events occurred in
-- the FxPorts since the the management agent has re-initialized
fcFxPortC2AccountingTable OBJECT-
SYNTAX SEQUENCE OF FcFxPortC2
MAX-ACCESS not-
STATUS
"A table that contains, one entry for each FxPort in
Fabric Element, Class 2 accounting information
since the management agent has re-initialized."
::= { fcFeAccounting 2 }
fcFxPortC2AccountingEntry OBJECT-
SYNTAX FcFxPortC2
MAX-ACCESS not-
STATUS
"An entry containing Class 2 accounting information for
FxPort."
AUGMENTS { fcFxPortEntry }
::= { fcFxPortC2AccountingTable 1 }
FcFxPortC2AccountingEntry ::=
SEQUENCE {
fcFxPortC2
Counter32,
fcFxPortC2
Counter32,
fcFxPortC2
Counter32,
fcFxPortC2
Counter32,
fcFxPortC2
Counter32,
fcFxPortC2
Counter32,
fcFxPortC2
Counter32
}
fcFxPortC2InFrames OBJECT-
Teow Standards Track [Page 31]
RFC 2837 FC Fabric Element MIB May 2000
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 2 frames received by this FxPort
its attached NxPort."
::= { fcFxPortC2AccountingEntry 1 }
fcFxPortC2OutFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 2 frames delivered through this
to its attached NxPort."
::= { fcFxPortC2AccountingEntry 2 }
fcFxPortC2InOctets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 2 frame octets, including the
delimiters, received by this FxPort from its
NxPort."
::= { fcFxPortC2AccountingEntry 3 }
fcFxPortC2OutOctets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 2 frame octets, including the
delimiters, delivered through this FxPort to its
NxPort."
::= { fcFxPortC2AccountingEntry 4 }
fcFxPortC2Discards OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 2 frames discarded by this FxPort."
::= { fcFxPortC2AccountingEntry 5 }
fcFxPortC2FbsyFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
Teow Standards Track [Page 32]
RFC 2837 FC Fabric Element MIB May 2000
STATUS
"The number of F_BSY frames generated by this FxPort
Class 2 frames."
::= { fcFxPortC2AccountingEntry 6 }
fcFxPortC2FrjtFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of F_RJT frames generated by this FxPort
Class 2 frames."
::= { fcFxPortC2AccountingEntry 7 }
-- the Class 3 Accounting
-- This table contains, one entry for each FxPort in the
-- Element, Counter32s for certain types of events occurred in
-- the FxPorts since the management agent has re-initialized
fcFxPortC3AccountingTable OBJECT-
SYNTAX SEQUENCE OF FcFxPortC3
MAX-ACCESS not-
STATUS
"A table that contains, one entry for each FxPort in
Fabric Element, Class 3 accounting information
since the management agent has re-initialized."
::= { fcFeAccounting 3 }
fcFxPortC3AccountingEntry OBJECT-
SYNTAX FcFxPortC3
MAX-ACCESS not-
STATUS
"An entry containing Class 3 accounting information for
FxPort."
AUGMENTS { fcFxPortEntry }
::= { fcFxPortC3AccountingTable 1 }
FcFxPortC3AccountingEntry ::=
SEQUENCE {
fcFxPortC3
Counter32,
fcFxPortC3
Counter32,
fcFxPortC3
Teow Standards Track [Page 33]
RFC 2837 FC Fabric Element MIB May 2000
Counter32,
fcFxPortC3
Counter32,
fcFxPortC3
Counter32
}
fcFxPortC3InFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 3 frames received by this FxPort
its attached NxPort."
::= { fcFxPortC3AccountingEntry 1 }
fcFxPortC3OutFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 3 frames delivered through this
to its attached NxPort."
::= { fcFxPortC3AccountingEntry 2 }
fcFxPortC3InOctets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 3 frame octets, including the
delimiters, received by this FxPort from its
NxPort."
::= { fcFxPortC3AccountingEntry 3 }
fcFxPortC3OutOctets OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"The number of Class 3 frame octets, including the
delimiters, delivered through this FxPort to its
NxPort."
::= { fcFxPortC3AccountingEntry 4 }
fcFxPortC3Discards OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
Teow Standards Track [Page 34]
RFC 2837 FC Fabric Element MIB May 2000
STATUS
"The number of Class 3 frames discarded by this FxPort."
::= { fcFxPortC3AccountingEntry 5 }
-- The Capability Group - consists of a table
-- information about what each FxPort is inherently
-- of operating or supporting
-- A capability may be used, as expressed in its
-- object value in the Configuration group
fcFxPortCapTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A table that contains, one entry for each FxPort,
capabilities of the port within the Fabric Element."
::= { fcFeCapabilities 1 }
fcFxPortCapEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry containing the Cap of a FxPort."
AUGMENTS { fcFxPortEntry }
::= { fcFxPortCapTable 1 }
FcFxPortCapEntry ::=
SEQUENCE {
FcphVersion
FcphVersion
FcBbCredit
FcBbCredit
FcRxDataFieldSize
FcRxDataFieldSize
FcCosCap
Teow Standards Track [Page 35]
RFC 2837 FC Fabric Element MIB May 2000
TruthValue
FcStackedConnMode
fcFxPortCapClass2
TruthValue
fcFxPortCapClass3
TruthValue
MicroSeconds
}
fcFxPortCapFcphVersionHigh OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The highest or most recent version of FC-PH that the
is capable of supporting."
::= { fcFxPortCapEntry 1 }
fcFxPortCapFcphVersionLow OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The lowest or earliest version of FC-PH that the FxPort
capable of supporting."
::= { fcFxPortCapEntry 2 }
fcFxPortCapBbCreditMax OBJECT-
SYNTAX
UNITS "buffers
MAX-ACCESS read-
STATUS
"The maximum number of receive buffers available for
Class 1 connect-request, Class 2 or Class 3 frames from
attached NxPort."
::= { fcFxPortCapEntry 3 }
fcFxPortCapBbCreditMin OBJECT-
SYNTAX
UNITS "buffers
MAX-ACCESS read-
STATUS
Teow Standards Track [Page 36]
RFC 2837 FC Fabric Element MIB May 2000
"The minimum number of receive buffers available for
Class 1 connect-request, Class 2 or Class 3 frames from
attached NxPort."
::= { fcFxPortCapEntry 4 }
fcFxPortCapRxDataFieldSizeMax OBJECT-
SYNTAX
UNITS "bytes
MAX-ACCESS read-
STATUS
"The maximum size in bytes of the Data Field in a frame
the FxPort is capable of receiving from its
NxPort."
::= { fcFxPortCapEntry 5 }
fcFxPortCapRxDataFieldSizeMin OBJECT-
SYNTAX
UNITS "bytes
MAX-ACCESS read-
STATUS
"The minimum size in bytes of the Data Field in a frame
the FxPort is capable of receiving from its
NxPort."
::= { fcFxPortCapEntry 6 }
fcFxPortCapCos OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A value indicating the set of Classes of Service that
FxPort is capable of supporting."
::= { fcFxPortCapEntry 7 }
fcFxPortCapIntermix OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A flag indicating whether or not the FxPort is capable
supporting the intermixing of Class 2 and Class 3
during a Class 1 connection. This flag is only valid if
port is capable of supporting Class 1 service."
::= { fcFxPortCapEntry 8 }
fcFxPortCapStackedConnMode OBJECT-
Teow Standards Track [Page 37]
RFC 2837 FC Fabric Element MIB May 2000
SYNTAX
MAX-ACCESS read-
STATUS
"A value indicating the mode of Stacked Connect request
the FxPort is capable of supporting."
::= { fcFxPortCapEntry 9 }
fcFxPortCapClass2SeqDeliv OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A flag indicating whether or not the FxPort is capable
supporting Class 2 Sequential Delivery."
::= { fcFxPortCapEntry 10 }
fcFxPortCapClass3SeqDeliv OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A flag indicating whether or not the FxPort is capable
supporting Class 3 Sequential Delivery."
::= { fcFxPortCapEntry 11 }
fcFxPortCapHoldTimeMax OBJECT-
SYNTAX
UNITS "microseconds
MAX-ACCESS read-
STATUS
"The maximum holding time (in microseconds) that the
is capable of supporting."
::= { fcFxPortCapEntry 12 }
fcFxPortCapHoldTimeMin OBJECT-
SYNTAX
UNITS "microseconds
MAX-ACCESS read-
STATUS
"The minimum holding time (in microseconds) that the
is capable of supporting."
::= { fcFxPortCapEntry 13 }
-- conformance
Teow Standards Track [Page 38]
RFC 2837 FC Fabric Element MIB May 2000
fcFeMIBConformance OBJECT IDENTIFIER ::= { fcFeMIB 2 }
fcFeMIBCompliances OBJECT IDENTIFIER ::= { fcFeMIBConformance 1 }
fcFeMIBGroups OBJECT IDENTIFIER ::= { fcFeMIBConformance 2 }
-- compliance
fcFeMIBMinimumCompliance MODULE-
STATUS
"The minimum compliance statement for SNMP
which implement the FIBRE-CHANNEL-FE-MIB."
MODULE -- this
MANDATORY-GROUPS { fcFeConfigGroup, fcFeStatusGroup
fcFeErrorGroup }
OBJECT
MIN-ACCESS read-
"Write access is not required."
OBJECT
MIN-ACCESS read-
"Write access is not required."
OBJECT
MIN-ACCESS read-
"Write access is not required."
OBJECT
MIN-ACCESS read-
"Write access is not required."
OBJECT
MIN-ACCESS read-
"Write access is not required."
OBJECT
MIN-ACCESS read-
"Write access is not required."
OBJECT
MIN-ACCESS read-
"Write access is not required."
Teow Standards Track [Page 39]
RFC 2837 FC Fabric Element MIB May 2000
::= { fcFeMIBCompliances 1 }
fcFeMIBFullCompliance MODULE-
STATUS
"The full compliance statement for SNMP
which implement the FIBRE-CHANNEL-FE-MIB."
MODULE -- this
MANDATORY-GROUPS { fcFeConfigGroup, fcFeStatusGroup
fcFeErrorGroup, fcFeCapabilitiesGroup }
GROUP fcFeClass1
"This group is mandatory for all fibre channel
elements which support class 1 frames."
GROUP fcFeClass2
"This group is mandatory for all fibre channel
elements which support class 2 frames."
GROUP fcFeClass3
"This group is mandatory for all fibre channel
elements which support class 3 frames."
OBJECT
MIN-ACCESS read-
"Write access is not required."
OBJECT
MIN-ACCESS read-
"Write access is not required."
OBJECT
MIN-ACCESS read-
"Write access is not required."
OBJECT
MIN-ACCESS read-
"Write access is not required."
OBJECT
MIN-ACCESS read-
Teow Standards Track [Page 40]
RFC 2837 FC Fabric Element MIB May 2000
"Write access is not required."
OBJECT
MIN-ACCESS read-
"Write access is not required."
OBJECT
MIN-ACCESS read-
"Write access is not required."
::= { fcFeMIBCompliances 2 }
-- units of
fcFeConfigGroup OBJECT-
OBJECTS { fcFeFabricName, fcFeElementName, fcFeModuleCapacity
fcFeModuleDescr, fcFeModuleObjectID
fcFeModuleOperStatus, fcFeModuleLastChange
fcFeModuleFxPortCapacity, fcFeModuleName
fcFxPortName, fcFxPortFcphVersionHigh
fcFxPortFcphVersionLow, fcFxPortBbCredit
fcFxPortRxBufSize, fcFxPortRatov, fcFxPortEdtov
fcFxPortCosSupported, fcFxPortIntermixSupported
fcFxPortStackedConnMode, fcFxPortClass2SeqDeliv
fcFxPortClass3SeqDeliv, fcFxPortHoldTime }
STATUS
"A collection of objects providing the configuration and
parameters of the Fabric Element, the modules, and FxPorts."
::= { fcFeMIBGroups 1 }
fcFeStatusGroup OBJECT-
OBJECTS { fcFxPortID, fcFxPortBbCreditAvailable
fcFxPortOperMode, fcFxPortAdminMode
fcFxPortPhysAdminStatus, fcFxPortPhysOperStatus
fcFxPortPhysLastChange, fcFxPortPhysRttov
fcFxPortFcphVersionAgreed, fcFxPortNxPortBbCredit
fcFxPortNxPortRxDataFieldSize, fcFxPortCosSuppAgreed
fcFxPortIntermixSuppAgreed
fcFxPortStackedConnModeAgreed
fcFxPortClass2SeqDelivAgreed
fcFxPortClass3SeqDelivAgreed
fcFxPortNxPortName, fcFxPortConnectedNxPort
fcFxPortBbCreditModel }
STATUS
Teow Standards Track [Page 41]
RFC 2837 FC Fabric Element MIB May 2000
"A collection of objects providing the operational status
established service parameters for the Fabric Element and
attached NxPorts."
::= { fcFeMIBGroups 2 }
fcFeErrorGroup OBJECT-
OBJECTS { fcFxPortLinkFailures, fcFxPortSyncLosses
fcFxPortSigLosses, fcFxPortPrimSeqProtoErrors
fcFxPortInvalidTxWords, fcFxPortInvalidCrcs
fcFxPortDelimiterErrors, fcFxPortAddressIdErrors
fcFxPortLinkResetIns, fcFxPortLinkResetOuts
fcFxPortOlsIns, fcFxPortOlsOuts }
STATUS
"A collection of objects providing various
statistics detected by the FxPorts."
::= { fcFeMIBGroups 3 }
fcFeClass1AccountingGroup OBJECT-
OBJECTS { fcFxPortC1InFrames, fcFxPortC1OutFrames
fcFxPortC1InOctets, fcFxPortC1OutOctets
fcFxPortC1Discards, fcFxPortC1FbsyFrames
fcFxPortC1FrjtFrames, fcFxPortC1InConnections
fcFxPortC1OutConnections, fcFxPortC1
}
STATUS
"A collection of objects providing various class 1
performance statistics detected by the FxPorts."
::= { fcFeMIBGroups 4 }
fcFeClass2AccountingGroup OBJECT-
OBJECTS { fcFxPortC2InFrames, fcFxPortC2OutFrames
fcFxPortC2InOctets, fcFxPortC2OutOctets
fcFxPortC2Discards, fcFxPortC2FbsyFrames
fcFxPortC2
}
STATUS
"A collection of objects providing various class 2
performance statistics detected by the FxPorts."
::= { fcFeMIBGroups 5 }
fcFeClass3AccountingGroup OBJECT-
OBJECTS { fcFxPortC3InFrames, fcFxPortC3OutFrames
fcFxPortC3InOctets, fcFxPortC3OutOctets
fcFxPortC3
}
Teow Standards Track [Page 42]
RFC 2837 FC Fabric Element MIB May 2000
STATUS
"A collection of objects providing various class 3
performance statistics detected by the FxPorts."
::= { fcFeMIBGroups 6 }
fcFeCapabilitiesGroup OBJECT-
OBJECTS { fcFxPortCapFcphVersionHigh, fcFxPortCapFcphVersionLow
fcFxPortCapBbCreditMax, fcFxPortCapBbCreditMin
fcFxPortCapRxDataFieldSizeMax
fcFxPortCapRxDataFieldSizeMin
fcFxPortCapCos, fcFxPortCapIntermix
fcFxPortCapStackedConnMode, fcFxPortCapClass2SeqDeliv
fcFxPortCapClass3SeqDeliv, fcFxPortCapHoldTimeMax
}
STATUS
"A collection of objects providing the
capability of each FxPort within the Fabric Element."
::= { fcFeMIBGroups 7 }
-- End of Object
4. Security
There are a number of management objects defined in this MIB
have a MAX-ACCESS clause of read-write. Such objects may
considered sensitive or vulnerable in some network environments.
support for SET operations in a non-secure environment without
protection can have a negative effect on network operations
SNMPv1 by itself is not a secure environment. Even if the
itself is secure (for example by using IPSec), even then, there is
control as to who on the secure network is allowed to access
GET/SET (read/change/create/delete) the objects in this MIB
It is recommended that the implementers consider the
features as provided by the SNMPv3 framework. Specifically, the
of the User-based Security Model RFC 2574 [12] and the View-
Access Control Model RFC 2575 [15] is recommended
Teow Standards Track [Page 43]
RFC 2837 FC Fabric Element MIB May 2000
It is then a customer/user responsibility to ensure that the
entity giving access to an instance of this MIB, is
configured to give access to the objects only to those
(users) that have legitimate rights to indeed GET or
(change/delete) them
5. Intellectual
The IETF takes no position regarding the validity or scope of
intellectual property or other rights that might be claimed
pertain to the implementation or use of the technology described
this document or the extent to which any license under such
might or might not be available; neither does it represent that
has made any effort to identify any such rights. Information on
IETF's procedures with respect to rights in standards-track
standards-related documentation can be found in BCP-11. Copies
claims of rights made available for publication and any assurances
licenses to be made available, or the result of an attempt made
obtain a general license or permission for the use of
proprietary rights by implementors or users of this specification
be obtained from the IETF Secretariat
The IETF invites any interested party to bring to its attention
copyrights, patents or patent applications, or other
rights which may cover technology that may be required to
this standard. Please address the information to the IETF
Director
6.
The editors would like to thank the following individuals for
assistance and constructive comments
Juergen Schoenwaelder, Technical University
Vincent Guan, Brocade Gavin Bowlby,
Bent Stoevhase, Brocade Jeff Meyer,
John Y. Chu,
Yakov Rekhter, Cisco Martin Sachs,
Dan Eisenhauer, IBM Beth Vanderbeck,
Carl Zeitler, Compaq Paul Griffiths,
KC Chennappan, IBM Jessie Haug,
Bob Cornelius, ANCOR Lansing Sloan,
Paul Rupert, LLNL Rich Taborak,
Steve Wilson, Brocade Jerry Rouse,
Dal Allan, ENDL Hubert Huot,
Venkat Rao, HP Amir Artsi, RADWAY International Ltd
Teow Standards Track [Page 44]
RFC 2837 FC Fabric Element MIB May 2000
7.
7.1. IETF
[1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture
Describing SNMP Management Frameworks", RFC 2571, April 1999.
[2] Rose, M. and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based Internets", STD 16,
1155, May 1990.
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991.
[4] Rose, M., "A Convention for Defining Traps for use with
SNMP", RFC 1215, March 1991.
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S. Waldbusser, "Structure of Management
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
RFC 2579, April 1999.
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S. Waldbusser, "Conformance Statements for SMIv2",
58, RFC 2580, April 1999.
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "
Network Management Protocol", STD 15, RFC 1157, May 1990.
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser
"Introduction to Community-based SNMPv2", RFC 1901,
1996.
[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "
Mappings for Version 2 of the Simple Network Management
(SNMPv2)", RFC 1906, January 1996.
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "
Processing and Dispatching for the Simple Network
Protocol (SNMP)", RFC 2572, April 1999.
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM
for version 3 of the Simple Network Management
(SNMPv3)", RFC 2574, April 1999.
Teow Standards Track [Page 45]
RFC 2837 FC Fabric Element MIB May 2000
[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "
Operations for Version 2 of the Simple Network
Protocol (SNMPv2)", RFC 1905, January 1996.
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications",
2573, April 1999.
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Control Model (VACM) for the Simple Network Management
(SNMP)", RFC 2575, April 1999.
[16] Case, J., Mundy, R., Partain, D. and B. Stewart, "
to Version 3 of the Internet-standard Network
Framework", RFC 2570, April 1999.
7.2. Approved ANSI/NCITS
[17] Fibre Channel Physical and Signaling Interface (FC-PH),
National Standard for Information Systems X3.230:1994,
and Business Equipment Manufacturers Association, Washington
DC
[18] Fibre Channel Fabric Generic (FC-FG), American National
for Information Systems X3.289:1996, Computer and
Equipment Manufacturers Association, Washington, DC
[19] Fibre Channel Generic Services (FC-GS), American
Standard for Information Systems X3.288:1996, Computer
Business Equipment Manufacturers Association, Washington, DC
[20] Fibre Channel Arbitrated Loop (FC-AL), American
Standard for Information Systems X3.272:1996, Computer
Business Equipment Manufacturers Association, Washington, DC
[21] Fibre Channel Physical and Signaling Interface-2 (FC-PH-2),
American National Standard for Information Systems, X3.297:1997,
Computer and Business Equipment Manufacturers Association
Washington, DC
[22] Fibre Channel Physical and Signaling