< draft-ietf-imss-fc-rtm-mib-03.txt   draft-ietf-imss-fc-rtm-mib-04.txt >
Internet Draft C. DeSanti Internet Draft C. DeSanti
K. McCloghrie K. McCloghrie
Cisco Systems Cisco Systems
S. Kode S. Kode
Consultant Consultant
S. Gai S. Gai
10 March 2006 28 April 2006
Fibre-Channel Routing Information MIB Fibre-Channel Routing Information MIB
draft-ietf-imss-fc-rtm-mib-03.txt draft-ietf-imss-fc-rtm-mib-04.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 2, line 10 skipping to change at page 2, line 10
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for information related In particular, it describes managed objects for information related
to routing within a Fibre Channel fabric which is independent of the to routing within a Fibre Channel fabric which is independent of the
usage of a particular routing protocol. usage of a particular routing protocol.
Table of Contents Table of Contents
1 Introduction ................................................. 3 1 Introduction ................................................. 3
2 The Internet-Standard Management Framework ................... 3 2 The Internet-Standard Management Framework ................... 3
3 Short Overview of Fibre Channel .............................. 3 3 Short Overview of Fibre Channel .............................. 3
4 Relationship to Other MIBs ................................... 4 4 Relationship to Other MIBs ................................... 5
5 MIB Overview ................................................. 5 5 MIB Overview ................................................. 5
5.1 Fibre Channel management instance .......................... 5 5.1 Fibre Channel management instance .......................... 5
5.2 Switch Index ............................................... 5 5.2 Switch Index ............................................... 6
5.3 Fabric Index ............................................... 5 5.3 Fabric Index ............................................... 6
5.4 The t11FcRouteGroup Group .................................. 6 5.4 The t11FcRouteGroup Group .................................. 6
5.5 The t11FcRouteTable's INDEX ................................ 6 5.5 The t11FcRouteTable's INDEX ................................ 6
6 The T11-FC-ROUTE-MIB Module .................................. 7 6 The T11-FC-ROUTE-MIB Module .................................. 7
7 Intellectual Property ........................................ 17 7 Intellectual Property ........................................ 17
8 Acknowledgements ............................................. 17 8 Acknowledgements ............................................. 18
9 Normative References ......................................... 18 9 Normative References ......................................... 18
10 Informative References ...................................... 19 10 Informative References ...................................... 19
11 IANA Considerations ......................................... 19 11 IANA Considerations ......................................... 20
12 Security Considerations ..................................... 20 12 Security Considerations ..................................... 20
13 Authors' Addresses .......................................... 21 13 Authors' Addresses .......................................... 21
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for information related In particular, it describes managed objects for information related
to the Fibre Channel network's Routing Table for routing within a to the Fibre Channel network's Routing Table for routing within a
Fabric. Managed objects specific to particular routing protocols, Fabric. Managed objects specific to particular routing protocols,
such as FSPF, are not specified in this MIB module. such as the Fabric Shortest Path First (FSPF) protocol [FC-SW-4], are
not specified in this MIB module.
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 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 4, line 31 skipping to change at page 4, line 32
The routing of frames within the Fabric is normally based on the The routing of frames within the Fabric is normally based on the
standard routing protocol, called the Fabric Shortest Path First standard routing protocol, called the Fabric Shortest Path First
(FSPF) protocol. The operation of FSPF (or any other routing (FSPF) protocol. The operation of FSPF (or any other routing
protocol) allows a switch to generate and maintain its own routing protocol) allows a switch to generate and maintain its own routing
table of how to forward frames it receives, i.e., a table in which to table of how to forward frames it receives, i.e., a table in which to
lookup the destination address of a received frame in order to lookup the destination address of a received frame in order to
determine the best link by which to forward that frame towards its determine the best link by which to forward that frame towards its
destination. destination.
The latest standard for an interconnecting Fabric containing multiple
Fabric Switch elements is [FC-SW-4] (which replaces the previous
revision [FC-SW-3]). [FC-SW-4] carries forward the existing
specification for the operation of a single Fabric in a physical
infrastructure, augmenting it with the definition of Virtual Fabrics
and with the specification of how multiple Virtual Fabrics can
operate within one (or more) physical infrastructures. The use of
Virtual Fabrics provides for each frame to be tagged in its header to
indicate which one of several Virtual Fabrics that frame is being
transmitted on. All frames entering a particular "Core Switch"
[FC-SW-4] (i.e., a physical switch) on the same Virtual Fabric are
processed by the same "Virtual Switch" within that Core switch.
4. Relationship to Other MIBs 4. Relationship to Other MIBs
The first standardized MIB for Fibre Channel [RFC2837] was focussed The first standardized MIB for Fibre Channel [RFC2837] was focussed
on Fibre Channel switches. It is being replaced by the more generic on Fibre Channel switches. It is being replaced by the more generic
Fibre Channel Management MIB [FC-MGMT] which defines basic Fibre Channel Management MIB [FC-MGMT] which defines basic
information for Fibre Channel hosts and switches, including information for Fibre Channel hosts and switches, including
extensions to the standard IF-MIB [RFC2863] for Fibre Channel extensions to the standard IF-MIB [RFC2863] for Fibre Channel
interfaces. interfaces.
This MIB extends beyond [FC-MGMT] to cover the routing of traffic This MIB extends beyond [FC-MGMT] to cover the routing of traffic
skipping to change at page 5, line 43 skipping to change at page 6, line 17
The FC-MGMT-MIB [FC-MGMT] defines the fcmSwitchTable as a table of The FC-MGMT-MIB [FC-MGMT] defines the fcmSwitchTable as a table of
information about Fibre Channel switches which are managed by Fibre information about Fibre Channel switches which are managed by Fibre
Channel management instances. Each Fibre Channel management instance Channel management instances. Each Fibre Channel management instance
can manage one or more Fibre Channel switches. The Switch Index, can manage one or more Fibre Channel switches. The Switch Index,
fcmSwitchIndex, is IMPORTed from the FC-MGMT-MIB as the index value fcmSwitchIndex, is IMPORTed from the FC-MGMT-MIB as the index value
to uniquely identify a Fibre Channel switch amongst those (one or to uniquely identify a Fibre Channel switch amongst those (one or
more) managed by the same Fibre Channel management instance. more) managed by the same Fibre Channel management instance.
5.3. Fabric Index 5.3. Fabric Index
The latest standard for an interconnecting Fabric containing multiple Whether operating on a physical Fabric (i.e., without Virtual
Fabric Switch elements is [FC-SW-4] (which replaces the previous Fabrics) or within a Virtual Fabric, the operation of FSPF within a
revision [FC-SW-3]). [FC-SW-4] specifies the operation of both a Fabric is identical. Therefore, this MIB defines all Fabric-related
single Fabric in a physical infrastructure, as well as the support of information in tables which are INDEX-ed by an arbitrary integer,
multiple Virtual Fabrics operating within one (or more) physical named a "Fabric Index", the syntax of which is IMPORTed from the
infrastructures. Whether operating on a physical Fabric (i.e., T11-TC-MIB. When a device is connected to a single physical Fabric,
without Virtual Fabrics) or within a Virtual Fabric, the operation of without use of any virtual Fabrics, the value of this Fabric Index
FSPF within a Fabric is identical. Therefore, this MIB defines all will always be 1. In an environment of multiple virtual and/or
Fabric-related information in tables which are INDEX-ed by an physical Fabrics, this index provides a means to distinguish one
arbitrary integer, named a "Fabric Index", the syntax of which is Fabric from another.
IMPORTed from the T11-TC-MIB. When a device is connected to a single
physical Fabric, without use of any virtual Fabrics, the value of
this Fabric Index will always be 1. In an environment of multiple
virtual and/or physical Fabrics, this index provides a means to
distinguish one Fabric from another.
It is quite possible, and may even be likely, that a Fibre Channel It is quite possible, and may even be likely, that a Fibre Channel
switch will have ports connected to multiple virtual and/or physical switch will have ports connected to multiple virtual and/or physical
Fabrics. Thus, in order to simplify a management protocol query Fabrics. Thus, in order to simplify a management protocol query
concerning all the Fabrics to which a single switch is connected, concerning all the Fabrics to which a single switch is connected,
fcmSwitchIndex will be listed before t11FcRouteFabricIndex when they fcmSwitchIndex will be listed before t11FcRouteFabricIndex when they
both appear in the same INDEX clause. both appear in the same INDEX clause.
5.4. The t11FcRouteGroup Group 5.4. The t11FcRouteGroup Group
skipping to change at page 6, line 39 skipping to change at page 7, line 7
It is normally valuable for a MIB table which contains routes to be It is normally valuable for a MIB table which contains routes to be
ordered such that a management application is able to query the table ordered such that a management application is able to query the table
based on some attribute, without having to read every row in the MIB based on some attribute, without having to read every row in the MIB
table. This requires the rows in the table be ordered according to table. This requires the rows in the table be ordered according to
such attributes, and thus, that those attributes be represented by such attributes, and thus, that those attributes be represented by
objects included in the table's INDEX clause. Examples of this can objects included in the table's INDEX clause. Examples of this can
be seen in the ipCidrRouteTable [RFC2096], and more recently, the be seen in the ipCidrRouteTable [RFC2096], and more recently, the
inetCidrRouteTable in [RFC2096bis]. inetCidrRouteTable in [RFC2096bis].
Providing the same useful feature in the MIB in this document, While this useful feature results in an unusually large number (ten)
results in having an unusually large number (ten) of objects in the of objects in the t11FcRouteTable's INDEX clause, all ten are either
t11FcRouteTable's INDEX clause. However, all ten are either integers integers or strings of length 3 (or zero) octets, so the resulting
or strings of length 0 or 3 octets. Thus, the aggregate number of OIDs are not unusually large. [Specifically, the aggregate number of
sub-identifiers to be appended to an OBJECT-TYPE's OID when naming an sub-identifiers to be appended to an OBJECT-TYPE's OID, when naming
instance of an object in this table, is at most 22 sub-identifiers, an instance of an object in the t11FcRouteTable, is at most 22 sub-
i.e., less than the *minimum* number to be appended for the identifiers, i.e., less than the *minimum* number to be appended for
inetCidrRouteTable table. In other words, while ten is an unusually the inetCidrRouteTable table.]
large number of objects in an INDEX clause, the resultant OIDs are
not unusually large.
6. The T11-FC-ROUTE-MIB Module 6. The T11-FC-ROUTE-MIB Module
T11-FC-ROUTE-MIB DEFINITIONS ::= BEGIN T11-FC-ROUTE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Unsigned32, mib-2 FROM SNMPv2-SMI -- [RFC2578] Unsigned32, mib-2 FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
RowStatus, TimeStamp, RowStatus, TimeStamp,
 End of changes. 11 change blocks. 
34 lines changed or deleted 40 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/