draft-ietf-imss-fc-vf-mib-00.txt   draft-ietf-imss-fc-vf-mib-01.txt 
INTERNET DRAFT Scott Kipp INTERNET DRAFT Scott Kipp
G D Ramkumar G D Ramkumar
McDATA Corporation McDATA Corporation
Keith McCloghrie Keith McCloghrie
Cisco Systems Cisco Systems
November 8, 2005 January 23, 2006
The Virtual Fabrics MIB The Virtual Fabrics MIB
draft-ietf-imss-fc-vf-mib-00.txt draft-ietf-imss-fc-vf-mib-01.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
applicable patent or other IPR claims of which he or she is aware that any applicable patent or other IPR claims of which he or
have been or will be disclosed, and any of which he or she becomes she is aware have been or will be disclosed, and any of which
aware will be disclosed, in accordance with Section 6 of BCP 79. he or she becomes 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
Task Force (IETF), its areas, and its working groups. Note that Engineering
other groups may also distribute working documents as Internet-
Drafts. Internet-Drafts are draft documents valid for a maximum of Task Force (IETF), its areas, and its working groups. Note
six months and may be updated, replaced, or made obsolete by other that other groups may also distribute working documents as
documents at any time. It is inappropriate to use Internet- Drafts Internet-Drafts. Internet-Drafts are draft documents valid
as reference material or to cite them other than as "work in for a maximum of six months and may be updated, replaced, or
progress." made obsolete by other documents at any time. It is
inappropriate to use Internet- Drafts as reference material
or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at 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
http://www.ietf.org/shadow.html. at http://www.ietf.org/shadow.html.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information
for use with network management protocols in the Internet community. Base (MIB) for use with network management protocols in the
In particular, it describes managed objects for information related Internet community. In particular, it describes managed
to the Fibre Channel network's Virtual Fabrics function. objects for information related to the Fibre Channel
network's Virtual Fabrics function.
draft-ietf-imss-fc-vf-mib-00.txt draft-ietf-imss-fc-vf-mib-01.txt
Table of Contents Table of Contents
Status of this Memo.................................................1 1. Introduction.....................................................3
Abstract............................................................1 2. The Internet-Standard Management Framework.......................3
1. Introduction...................................................3 3. Short Overview of Fibre Channel..................................3
2. The Internet-Standard Management Framework.....................3 4. Relationship to Other MIBs.......................................4
3. Short Overview of Fibre Channel................................3 5. MIB Overview.....................................................5
4. Relationship to Other MIBs.....................................4 5.1 Fibre Channel management instance................................5
5. MIB Overview...................................................5 5.2 Representing Core and Virtual Switches...........................5
6. IANA Considerations............................................6 6. IANA Considerations..............................................5
7. Definition.....................................................7 7. The T11-FC-IRTUAL-FABRIC-MIB Module..............................6
8. Security Considerations.......................................18 8. Security Considerations.........................................16
9. Normative References..........................................19 9. Acknowledgements................................................17
10. Author's Addresses............................................21 10. Normative References............................................17
12. Intellectual Property.........................................21 11. Informative References..........................................18
13. Full Copyright Statement......................................21 12. Author's Addresses..............................................19
14. Disclaimer of Validity........................................22 13. Intellectual Property...........................................19
15. Acknowledgement...............................................22 draft-ietf-imss-fc-vf-mib-01.txt
16. Expiration Notice.............................................22
draft-ietf-imss-fc-vf-mib-00.txt
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information
for use with network management protocols in the Internet community. Base (MIB) for use with network management protocols in the
In particular, it describes managed objects for information related Internet community. In particular, it describes managed
to the Fibre Channel network's Virtual Fabric function. objects for information related to the Fibre Channel
network's Virtual Fabric function.
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
Internet-Standard Management Framework, please refer to section 7 of current Internet-Standard Management Framework, please refer
RFC 3410 [RFC3410]. Managed objects are accessed via a virtual to section 7 of RFC 3410 [RFC3410]. Managed objects are
information store, termed the Management Information Base or MIB. accessed via a virtual information store, termed the
MIB objects are generally accessed through the Simple Network Management Information Base or MIB. MIB objects are generally
Management Protocol (SNMP). accessed through the Simple Network Management Protocol
(SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined
Structure of Management Information (SMI). This memo specifies a MIB in the Structure of Management Information (SMI). This memo
module that is compliant to the SMIv2, which is described in STD 58, specifies a MIB module that is compliant to the SMIv2, which
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579
[RFC2580]. [RFC2579] and STD 58, RFC 2580 [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-
serial data channel, structured for high performance. Fibre Channel point serial data channel, structured for high performance.
provides a general transport vehicle for higher level protocols such Fibre Channel provides a general transport vehicle for higher
as Small Computer System Interface (SCSI) command sets, the High- level protocols such as Small Computer System Interface
Performance Parallel Interface (HIPPI) data framing, IP (Internet (SCSI) command sets, the High-Performance Parallel Interface
Protocol), IEEE 802.2, and others. (HIPPI) data framing, IP (Internet Protocol), IEEE 802.2, and
others.
Physically, Fibre Channel is an interconnection of multiple Physically, Fibre Channel is an interconnection of multiple
communication points, called N_Ports, interconnected either by a communication points, called N_Ports, interconnected either
switching network, called a Fabric, or by a point-to-point link. A by a switching network, called a Fabric, or by a point-to-
Fibre Channel "node" consists of one or more N_Ports. A Fabric may point link. A Fibre Channel "node" consists of one or more
consist of multiple Interconnect Elements, some of which are N_Ports. A Fabric may consist of multiple Interconnect
switches. An N_Port connects to the Fabric via a port on a switch Elements, some of which are switches. An N_Port connects to
called an F_Port. When multiple FC nodes are connected to a single the Fabric via a port on a switch called an F_Port. When
port on a switch via an "Arbitrated Loop" topology, the switch port multiple FC nodes are connected to a single port on a switch
is called an FL_Port, and the nodes' ports are called NL_Ports. The via an "Arbitrated Loop" topology, the switch port is called
draft-ietf-imss-fc-vf-mib-00.txt an FL_Port, and the nodes' ports are called NL_Ports. The
term Nx_Port is used to refer to either an N_Port or an NL_Port. The term Nx_Port is used to refer to either an N_Port or an
term Fx_Port is used to refer to either an F_Port or an FL_Port. A NL_Port. The term Fx_Port is used to refer to either an
switch port, which is interconnected to another switch port via an draft-ietf-imss-fc-vf-mib-01.txt
Inter-Switch Link (ISL), is called an E_Port. A B_Port connects a F_Port or an FL_Port. A switch port, which is interconnected
bridge device with an E_Port on a switch; a B_Port provides a subset to another switch port via an Inter-Switch Link (ISL), is
of E_Port functionality. called an E_Port. A B_Port connects a bridge device with an
E_Port on a switch; a B_Port provides a subset of E_Port
functionality.
Many Fibre Channel components, including the Fabric, each node, and Many Fibre Channel components, including the Fabric, each
most ports, have globally-unique names. These globally-unique names node, and most ports, have globally-unique names. These
are typically formatted as World Wide Names (WWNs). More information globally-unique names are typically formatted as World Wide
on WWNs can be found in [FC-FS]. WWNs are expected to be persistent Names (WWNs). More information on WWNs can be found in [FC-
across agent and unit resets. FS]. WWNs are expected to be persistent across agent and unit
resets.
Fibre Channel frames contain 24-bit address identifiers which Fibre Channel frames contain 24-bit address identifiers which
identify the frame's source and destination ports. Each FC port has identify the frame's source and destination ports. Each FC
both an address identifier and a WWN. When a Fabric is in use, the port has both an address identifier and a WWN. When a Fabric
FC address identifiers are dynamic and are assigned by a switch. is in use, the FC address identifiers are dynamic and are
Each octet of a 24-bit address represents a level in an address assigned by a switch. Each octet of a 24-bit address
hierarchy, with a Domain_ID being the highest level of the represents a level in an address hierarchy, with a Domain_ID
hierarchy. being the highest level of the hierarchy.
Virtual Fabrics allow a single physical Fabric to be divided into Virtual Fabrics allow a single physical Fabric to be divided
multiple logical Fabrics. Each Virtual Fabric may be managed into multiple logical Fabrics. Each Virtual Fabric may be
independently like traditional Fabrics. Virtual Fabrics are managed independently like traditional Fabrics. Virtual
designed to achieve a better utilization of a physical Fabrics are designed to achieve a better utilization of a
infrastructure and to isolate events in one Virtual Fabric from physical infrastructure and to isolate events in one Virtual
affecting other Fabrics. When one Core Switch provides switching Fabric from affecting other Fabrics. When one Core Switch
functions for multiple Virtual Fabrics, that Core Switch is modeled provides switching functions for multiple Virtual Fabrics,
as containing multiple Virtual Switches, one for each Virtual that Core Switch is modeled as containing multiple Virtual
Fabric. Switches, one for each Virtual Fabric.
Each Virtual Fabric is identified by a 12-bit Virtual Fabric ID Each Virtual Fabric is identified by a 12-bit Virtual Fabric
(VF_ID). When frames from multiple Virtual Fabrics are transmitted ID (VF_ID). When frames from multiple Virtual Fabrics are
over a physical link, the VF_ID carried in a frame's Virtual Fabric transmitted over a physical link, the VF_ID carried in a
Tagging Header (VFT_Header) identifies which Virtual Fabric the frame's Virtual Fabric Tagging Header (VFT_Header) identifies
frame belongs to. The use of VFT_Headers is enabled through an which Virtual Fabric the frame belongs to. The use of
initial negotiation exchange between the two connected ports. VFT_Headers is enabled through an initial negotiation
exchange between the two connected ports.
4. Relationship to Other MIBs 4. Relationship to Other MIBs
This MIB extends beyond [FC-MGMT-MIB] to cover the functionality, in This MIB extends beyond [RFC4044] to cover the functionality,
Fibre Channel switches, of providing Fibre Channel's Virtual in Fibre Channel switches, of providing Fibre Channel's
draft-ietf-imss-fc-vf-mib-00.txt Virtual
Fabrics function. Fabrics function.
draft-ietf-imss-fc-vf-mib-01.txt
5. MIB Overview 5. MIB Overview
This MIB module provides the means for monitoring the operation of, This MIB module provides the means for monitoring the
and configuring some parameters of, one or more instances of Fibre operation of, and configuring some parameters of, one or more
Channel Virtual Fabric functionality. (Note that there are no instances of Fibre Channel Virtual Fabric functionality.
definitions in this MIB module of "managed actions" which can be (Note that there are no definitions in this MIB module of
invoked via SNMP.) "managed actions" which can be invoked via SNMP.)
The following MIB module has IMPORTS from [RFC2578], [RFC2579], The following MIB module has IMPORTS from [RFC2578],
[RFC2580], [RFC2863], [FC-MGMT-MIB] and [FC-FAM-MIB]. [RFC2579], [RFC2580], [RFC2863], [RFC4044] and [FC-FAM-MIB].
In REFERENCE clauses, it refers to [FC-SW-4]. In REFERENCE clauses, it refers to [FC-SW-4].
5.1 Fibre Channel management instance 5.1 Fibre Channel management instance
A Fibre Channel management instance is defined in [FC-MGMT-MIB] as a A Fibre Channel management instance is defined in [RFC4044]
separable managed instance of Fibre Channel functionality. Fibre as a separable managed instance of Fibre Channel
Channel functionality may be grouped into Fibre Channel management functionality. Fibre Channel functionality may be grouped
instances in whatever way is most convenient for the into Fibre Channel management instances in whatever way is
implementation(s). For example, one such grouping accommodates a most convenient for the implementation(s). For example, one
single SNMP agent having multiple AgentX [RFC2741] sub-agents, with such grouping accommodates a single SNMP agent having
each sub-agent implementing a different Fibre Channel management multiple AgentX [RFC2741] sub-agents, with each sub-agent
instance. implementing a different Fibre Channel management instance.
The object, fcmInstanceIndex, is IMPORTed from the [FC-MGMT-MIB] as The object, fcmInstanceIndex, is IMPORTed from the FC-MGMT-
the index value to uniquely identify each Fibre Channel management MIB [RFC4044] as the index value to uniquely identify each
instance within the same SNMP context ([RFC3411] section 3.3.1). The Fibre Channel management instance within the same SNMP
t11vfVirtualSwitchTable augments the fcmSwitchTable, and the primary context ([RFC3411] section 3.3.1). The
index variable of the fcmSwitchTable is fcmInstanceIndex. t11vfVirtualSwitchTable augments the fcmSwitchTable, and the
primary index variable of the fcmSwitchTable is
fcmInstanceIndex.
5.2 Representing Core and Virtual Switches 5.2 Representing Core and Virtual Switches
In the presence of Virtual Switches, fcmSwitchTable in the FC-MGMT- In the presence of Virtual Switches, fcmSwitchTable in
MIB contains a row for each Virtual Switch. fcmSwitchTable, RFC4044 contains a row for each Virtual Switch.
t11vfCoreSwitchTable and t11vfVirtualSwitchTable are complementary. fcmSwitchTable, t11vfCoreSwitchTable and
The t11vfCoreSwitchTable and t11vfVirtualSwitchTable contain t11vfVirtualSwitchTable are complementary. The
t11vfCoreSwitchTable and t11vfVirtualSwitchTable contain
information that helps the management client determine which information that helps the management client determine which
Switches are Virtual Switches and how each relates to a Core Switch. Switches are Virtual Switches and how each relates to a Core
A Virtual Switch must reside in a single Core Switch and a Core Switch. A Virtual Switch must reside in a single Core Switch
Switch is defined as a set of entities with the same Core and a Core Switch is defined as a set of entities with the
Switch_Name. same Core Switch_Name.
draft-ietf-imss-fc-vf-mib-00.txt
6. IANA Considerations 6. IANA Considerations
IANA is requested to make the OID assignment for the MIB module IANA is requested to make the OID assignment for the MIB
under the appropriate subtree. module under the appropriate subtree.
draft-ietf-imss-fc-vf-mib-00.txt draft-ietf-imss-fc-vf-mib-01.txt
7. Definition 7. The T11-FC-IRTUAL-FABRIC-MIB Module
T11-FC-VIRTUAL-FABRIC-MIB DEFINITIONS ::= BEGIN T11-FC-VIRTUAL-FABRIC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Unsigned32, mib-2 Unsigned32, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
RowStatus, StorageType FROM SNMPv2-TC -- [RFC2579] RowStatus, StorageType FROM SNMPv2-TC -- [RFC2579]
InterfaceIndex FROM IF-MIB -- [RFC2863] InterfaceIndex FROM IF-MIB -- [RFC2863]
fcmInstanceIndex, FcNameIdOrZero, fcmInstanceIndex, FcNameIdOrZero,
fcmPortEntry, fcmSwitchEntry fcmPortEntry, fcmSwitchEntry
FROM FC-MGMT-MIB -- [FC-MGMT-MIB] FROM FC-MGMT-MIB -- [RFC4044]
T11FabricIndex FROM T11-TC-MIB; -- [FC-FAM-MIB] T11FabricIndex FROM T11-TC-MIB; -- [FC-FAM-MIB]
t11FcVirtualFabricMIB MODULE-IDENTITY t11FcVirtualFabricMIB MODULE-IDENTITY
LAST-UPDATED "200511080000Z" LAST-UPDATED "200601230000Z"
ORGANIZATION "IETF IMSS (Internet and Management Support ORGANIZATION "IETF IMSS (Internet and Management Support
for Storage)Working Group" for Storage)Working Group"
CONTACT-INFO CONTACT-INFO
" "
Scott Kipp Scott Kipp
McDATA Corporation McDATA Corporation
Tel: +1 720 558-3452 Tel: +1 720 558-3452
E-mail: scott.kipp@mcdata.com E-mail: scott.kipp@mcdata.com
Postal: 4 McDATA Parkway Postal: 4 McDATA Parkway
Broomfield, CO USA 80021 Broomfield, CO USA 80021
skipping to change at page 8, line 4 skipping to change at page 6, line 51
Postal: 4555 Great American Parkway Postal: 4555 Great American Parkway
Santa Clara, CA USA 95054 Santa Clara, CA USA 95054
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
" "
draft-ietf-imss-fc-vf-mib-00.txt
DESCRIPTION DESCRIPTION
"This module defines management information specific to "This module defines management information specific to
Fibre Channel Virtual Fabrics. A Virtual Fabric is a Fibre Channel Virtual Fabrics. A Virtual Fabric is a
Fabric composed of partitions of switches, links and Fabric composed of partitions of switches, links and
N_Ports with a single Fabric management domain, Fabric N_Ports with a single Fabric management domain, Fabric
Services and independence from other Virtual Fabrics. Services and independence from other Virtual Fabrics.
Copyright (C) The Internet Society (2005). This version of draft-ietf-imss-fc-vf-mib-01.txt
Copyright (C) The Internet Society (2006). This version of
this MIB module is part of RFC yyyy; see the RFC itself for this MIB module is part of RFC yyyy; see the RFC itself for
full legal notices." full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200511080000Z" REVISION "200601230000Z"
DESCRIPTION DESCRIPTION
"Initial version of this MIB module, published as RFCxxxx." "Initial version of this MIB module, published as RFCxxxx."
-- RFC-Editor, replace yyyy with actual RFC number & remove this note -- RFC-Editor, replace yyyy with actual RFC number & remove this note
::= { mib-2 nnn } -- to be assigned by IANA ::= { mib-2 nnn } -- to be assigned by IANA
-- RFC Editor: replace nnn with IANA-assigned number & remove this note -- RFC Editor: replace nnn with IANA-assigned number & remove this note
t11vfObjects OBJECT IDENTIFIER ::= { t11FcVirtualFabricMIB 1 } t11vfObjects OBJECT IDENTIFIER ::= { t11FcVirtualFabricMIB 1 }
t11vfConformance OBJECT IDENTIFIER ::= { t11FcVirtualFabricMIB 2 } t11vfConformance OBJECT IDENTIFIER ::= { t11FcVirtualFabricMIB 2 }
--******************************** --********************************
skipping to change at page 9, line 4 skipping to change at page 7, line 43
t11vfCoreSwitchEntry OBJECT-TYPE t11vfCoreSwitchEntry OBJECT-TYPE
SYNTAX T11vfCoreSwitchEntry SYNTAX T11vfCoreSwitchEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry represents one core switch." "Each entry represents one core switch."
INDEX { fcmInstanceIndex, t11vfCoreSwitchSwitchName } INDEX { fcmInstanceIndex, t11vfCoreSwitchSwitchName }
::= { t11vfCoreSwitchTable 1} ::= { t11vfCoreSwitchTable 1}
T11vfCoreSwitchEntry ::= T11vfCoreSwitchEntry ::=
draft-ietf-imss-fc-vf-mib-00.txt
SEQUENCE { SEQUENCE {
t11vfCoreSwitchSwitchName FcNameIdOrZero, t11vfCoreSwitchSwitchName FcNameIdOrZero,
t11vfCoreSwitchMaxSupported Unsigned32, t11vfCoreSwitchMaxSupported Unsigned32,
t11vfCoreSwitchStorageType StorageType t11vfCoreSwitchStorageType StorageType
} }
t11vfCoreSwitchSwitchName OBJECT-TYPE t11vfCoreSwitchSwitchName OBJECT-TYPE
SYNTAX FcNameIdOrZero SYNTAX FcNameIdOrZero
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Core Switch_Name (WWN) of this Core Switch. A "The Core Switch_Name (WWN) of this Core Switch. A
draft-ietf-imss-fc-vf-mib-01.txt
zero-length string for this field is not allowed. " zero-length string for this field is not allowed. "
::= { t11vfCoreSwitchEntry 1 } ::= { t11vfCoreSwitchEntry 1 }
t11vfCoreSwitchMaxSupported OBJECT-TYPE t11vfCoreSwitchMaxSupported OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" In switches that do not support Virtual Fabrics, " In switches that do not support Virtual Fabrics,
this object has the value of 1. If Virtual Fabrics this object has the value of 1. If Virtual Fabrics
skipping to change at page 10, line 4 skipping to change at page 8, line 38
allow write-access to any columnar objects in the row." allow write-access to any columnar objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { t11vfCoreSwitchEntry 3 } ::= { t11vfCoreSwitchEntry 3 }
-- Virtual Switch table -- Virtual Switch table
t11vfVirtualSwitchTable OBJECT-TYPE t11vfVirtualSwitchTable OBJECT-TYPE
SYNTAX SEQUENCE OF T11vfVirtualSwitchEntry SYNTAX SEQUENCE OF T11vfVirtualSwitchEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
draft-ietf-imss-fc-vf-mib-00.txt
DESCRIPTION DESCRIPTION
"A table of Virtual Switches. When one Core Switch "A table of Virtual Switches. When one Core Switch
provides switching functions for multiple Virtual Fabrics, provides switching functions for multiple Virtual Fabrics,
that Core Switch is modeled as containing multiple that Core Switch is modeled as containing multiple
Virtual Switches, one for each Virtual Fabric. This table Virtual Switches, one for each Virtual Fabric. This table
contains one row for every Virtual Switch on every Core contains one row for every Virtual Switch on every Core
Switch. This table augments the basic switch information in Switch. This table augments the basic switch information in
the fcmSwitchTable Table in the FCMGMT-MIB." the fcmSwitchTable Table in the FC-MGMT-MIB."
REFERENCE REFERENCE
"fcmSwitchTable is defined in the FCMGMT-MIB module." "fcmSwitchTable is defined in the FC-MGMT-MIB [RFC4044]."
::= { t11vfObjects 2 } ::= { t11vfObjects 2 }
t11vfVirtualSwitchEntry OBJECT-TYPE t11vfVirtualSwitchEntry OBJECT-TYPE
SYNTAX T11vfVirtualSwitchEntry SYNTAX T11vfVirtualSwitchEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
draft-ietf-imss-fc-vf-mib-01.txt
"An entry of the Virtual Switch table. Each row is for a "An entry of the Virtual Switch table. Each row is for a
Virtual Switch." Virtual Switch."
REFERENCE REFERENCE
"fcmSwitchEntry is defined in the FCMGMT-MIB module." "fcmSwitchEntry is defined in the FC-MGMT-MIB module
[RFC4044]."
AUGMENTS { fcmSwitchEntry } AUGMENTS { fcmSwitchEntry }
::= { t11vfVirtualSwitchTable 1} ::= { t11vfVirtualSwitchTable 1}
T11vfVirtualSwitchEntry ::= T11vfVirtualSwitchEntry ::=
SEQUENCE { SEQUENCE {
t11vfVirtualSwitchVfId T11FabricIndex, t11vfVirtualSwitchVfId T11FabricIndex,
t11vfVirtualSwitchCoreSwitchName FcNameIdOrZero, t11vfVirtualSwitchCoreSwitchName FcNameIdOrZero,
t11vfVirtualSwitchRowStatus RowStatus, t11vfVirtualSwitchRowStatus RowStatus,
t11vfVirtualSwitchStorageType StorageType t11vfVirtualSwitchStorageType StorageType
} }
skipping to change at page 11, line 4 skipping to change at page 9, line 33
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VF_ID of the Virtual Fabric for which this virtual "The VF_ID of the Virtual Fabric for which this virtual
switch performs its switching function. The Control switch performs its switching function. The Control
VF_ID is implicitly enabled and is not set. VF_ID is implicitly enabled and is not set.
Communication with the Control VF_ID is required. " Communication with the Control VF_ID is required. "
REFERENCE REFERENCE
"FC-SW-4, REV 7.5, section 12.2" "FC-SW-4, REV 7.5, section 12.2"
::= { t11vfVirtualSwitchEntry 1 } ::= { t11vfVirtualSwitchEntry 1 }
draft-ietf-imss-fc-vf-mib-00.txt
t11vfVirtualSwitchCoreSwitchName OBJECT-TYPE t11vfVirtualSwitchCoreSwitchName OBJECT-TYPE
SYNTAX FcNameIdOrZero SYNTAX FcNameIdOrZero
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Core Switch_Name (WWN) of the Core Switch that "The Core Switch_Name (WWN) of the Core Switch that
contains this Virtual Switch." contains this Virtual Switch."
REFERENCE REFERENCE
"FC-SW-4, REV 7.5, section 12.2." "FC-SW-4, REV 7.5, section 12.2."
::= { t11vfVirtualSwitchEntry 2 } ::= { t11vfVirtualSwitchEntry 2 }
skipping to change at page 11, line 27 skipping to change at page 10, line 4
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row." "The status of this row."
::= { t11vfVirtualSwitchEntry 3 } ::= { t11vfVirtualSwitchEntry 3 }
t11vfVirtualSwitchStorageType OBJECT-TYPE t11vfVirtualSwitchStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
draft-ietf-imss-fc-vf-mib-01.txt
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. "The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row." allow write-access to any columnar objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { t11vfVirtualSwitchEntry 4 } ::= { t11vfVirtualSwitchEntry 4 }
-- Port table -- Port table
skipping to change at page 12, line 4 skipping to change at page 10, line 27
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of Port attributes related to Virtual Fabrics." "A table of Port attributes related to Virtual Fabrics."
::= { t11vfObjects 3 } ::= { t11vfObjects 3 }
t11vfPortEntry OBJECT-TYPE t11vfPortEntry OBJECT-TYPE
SYNTAX T11vfPortEntry SYNTAX T11vfPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
draft-ietf-imss-fc-vf-mib-00.txt
DESCRIPTION DESCRIPTION
"Each entry represents a physical Port on a switch." "Each entry represents a physical Port on a switch."
REFERENCE REFERENCE
"fcmPortEntry is defined in the FCMGMT-MIB module." "fcmPortEntry is defined in the FC-MGMT-MIB module."
AUGMENTS { fcmPortEntry } AUGMENTS { fcmPortEntry }
::= { t11vfPortTable 1} ::= { t11vfPortTable 1}
T11vfPortEntry ::= T11vfPortEntry ::=
SEQUENCE { SEQUENCE {
t11vfPortVfId T11FabricIndex, t11vfPortVfId T11FabricIndex,
t11vfPortTaggingAdminStatus INTEGER, t11vfPortTaggingAdminStatus INTEGER,
t11vfPortTaggingOperStatus INTEGER, t11vfPortTaggingOperStatus INTEGER,
t11vfPortStorageType StorageType t11vfPortStorageType StorageType
} }
skipping to change at page 12, line 34 skipping to change at page 11, line 4
DESCRIPTION DESCRIPTION
"The Port VF_ID assigned to this Port. The Port VF_ID is the "The Port VF_ID assigned to this Port. The Port VF_ID is the
default Virtual Fabric that is assigned to untagged frames default Virtual Fabric that is assigned to untagged frames
arriving at this Port. The Control VF_ID is implicitly arriving at this Port. The Control VF_ID is implicitly
enabled and is not set. Communication with the Control enabled and is not set. Communication with the Control
VF_ID is required. " VF_ID is required. "
REFERENCE REFERENCE
"FC-SW-4, REV 7.5, section 12.1" "FC-SW-4, REV 7.5, section 12.1"
DEFVAL {1} DEFVAL {1}
::= { t11vfPortEntry 1 } ::= { t11vfPortEntry 1 }
draft-ietf-imss-fc-vf-mib-01.txt
t11vfPortTaggingAdminStatus OBJECT-TYPE t11vfPortTaggingAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
off(1), off(1),
on(2), on(2),
auto(3) auto(3)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is used to configure the administrative status "This object is used to configure the administrative status
of Virtual Fabric tagging on this Port. of Virtual Fabric tagging on this Port.
SET operation Description SET operation Description
-------------- ------------------------------------------- -------------- -------------------------------------------
off(1) To disable Virtual Fabric tagging on this off(1) To disable Virtual Fabric tagging on this
draft-ietf-imss-fc-vf-mib-00.txt
Port. Port.
on(2) To enable Virtual Fabric tagging on this on(2) To enable Virtual Fabric tagging on this
Port if the attached Port doesn't Port if the attached Port doesn't
prohibit it. prohibit it.
auto(3) To enable Virtual Fabric tagging if the auto(3) To enable Virtual Fabric tagging if the
peer requests it. " peer requests it. "
REFERENCE REFERENCE
" FC-SW-4, REV 7.5, section 12.4" " FC-SW-4, REV 7.5, section 12.4"
skipping to change at page 13, line 39 skipping to change at page 12, line 4
-------------- ------------------------------------------- -------------- -------------------------------------------
off(1) Virtual Fabric tagging is disabled on this off(1) Virtual Fabric tagging is disabled on this
Port. Port.
on(2) Virtual Fabric tagging is enabled on this on(2) Virtual Fabric tagging is enabled on this
Port. " Port. "
REFERENCE REFERENCE
" FC-SW-4, REV 7.5, section 12.4" " FC-SW-4, REV 7.5, section 12.4"
::= { t11vfPortEntry 3 } ::= { t11vfPortEntry 3 }
draft-ietf-imss-fc-vf-mib-01.txt
t11vfPortStorageType OBJECT-TYPE t11vfPortStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. "The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row." allow write-access to any columnar objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { t11vfPortEntry 4 } ::= { t11vfPortEntry 4 }
draft-ietf-imss-fc-vf-mib-00.txt
-- Locally Enabled Table -- Locally Enabled Table
t11vfLocallyEnabledTable OBJECT-TYPE t11vfLocallyEnabledTable OBJECT-TYPE
SYNTAX SEQUENCE OF T11vfLocallyEnabledEntry SYNTAX SEQUENCE OF T11vfLocallyEnabledEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table for assigning and reporting operational status of "A table for assigning and reporting operational status of
Locally-enabled Virtual Fabric IDs to Ports. The set of Locally-enabled Virtual Fabric IDs to Ports. The set of
Virtual Fabrics operational on the Port is the bit-wise Virtual Fabrics operational on the Port is the bit-wise
skipping to change at page 14, line 43 skipping to change at page 13, line 4
SEQUENCE { SEQUENCE {
t11vfLocallyEnabledPortIfIndex InterfaceIndex, t11vfLocallyEnabledPortIfIndex InterfaceIndex,
t11vfLocallyEnabledVfId T11FabricIndex, t11vfLocallyEnabledVfId T11FabricIndex,
t11vfLocallyEnabledOperStatus INTEGER, t11vfLocallyEnabledOperStatus INTEGER,
t11vfLocallyEnabledRowStatus RowStatus, t11vfLocallyEnabledRowStatus RowStatus,
t11vfLocallyEnabledStorageType StorageType t11vfLocallyEnabledStorageType StorageType
} }
t11vfLocallyEnabledPortIfIndex OBJECT-TYPE t11vfLocallyEnabledPortIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
draft-ietf-imss-fc-vf-mib-01.txt
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the ifIndex which identifies the Port." "The value of the ifIndex which identifies the Port."
draft-ietf-imss-fc-vf-mib-00.txt
::= { t11vfLocallyEnabledEntry 1 } ::= { t11vfLocallyEnabledEntry 1 }
t11vfLocallyEnabledVfId OBJECT-TYPE t11vfLocallyEnabledVfId OBJECT-TYPE
SYNTAX T11FabricIndex SYNTAX T11FabricIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A Locally-Enabled VF_ID on this Port." "A Locally-Enabled VF_ID on this Port."
::= { t11vfLocallyEnabledEntry 2 } ::= { t11vfLocallyEnabledEntry 2 }
skipping to change at page 16, line 4 skipping to change at page 13, line 53
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this conceptual row." "The status of this conceptual row."
::= { t11vfLocallyEnabledEntry 4 } ::= { t11vfLocallyEnabledEntry 4 }
t11vfLocallyEnabledStorageType OBJECT-TYPE t11vfLocallyEnabledStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
draft-ietf-imss-fc-vf-mib-00.txt
STATUS current STATUS current
DESCRIPTION DESCRIPTION
draft-ietf-imss-fc-vf-mib-01.txt
"The storage type for this conceptual row. "The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row." allow write-access to any columnar objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { t11vfLocallyEnabledEntry 5 } ::= { t11vfLocallyEnabledEntry 5 }
--******************************** --********************************
-- Conformance Section -- Conformance Section
-- --
skipping to change at page 17, line 4 skipping to change at page 14, line 47
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT t11vfVirtualSwitchRowStatus OBJECT t11vfVirtualSwitchRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT t11vfVirtualSwitchStorageType OBJECT t11vfVirtualSwitchStorageType
draft-ietf-imss-fc-vf-mib-00.txt
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT t11vfPortVfId OBJECT t11vfPortVfId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
draft-ietf-imss-fc-vf-mib-01.txt
OBJECT t11vfPortTaggingAdminStatus OBJECT t11vfPortTaggingAdminStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT t11vfPortStorageType OBJECT t11vfPortStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 18, line 4 skipping to change at page 15, line 41
t11vfVirtualSwitchVfId, t11vfVirtualSwitchVfId,
t11vfVirtualSwitchCoreSwitchName, t11vfVirtualSwitchCoreSwitchName,
t11vfVirtualSwitchRowStatus, t11vfVirtualSwitchRowStatus,
t11vfPortVfId, t11vfPortVfId,
t11vfPortTaggingAdminStatus, t11vfPortTaggingAdminStatus,
t11vfLocallyEnabledOperStatus, t11vfLocallyEnabledOperStatus,
t11vfPortTaggingOperStatus, t11vfPortTaggingOperStatus,
t11vfLocallyEnabledRowStatus, t11vfLocallyEnabledRowStatus,
t11vfCoreSwitchStorageType, t11vfCoreSwitchStorageType,
t11vfVirtualSwitchStorageType, t11vfVirtualSwitchStorageType,
draft-ietf-imss-fc-vf-mib-00.txt
t11vfPortStorageType, t11vfPortStorageType,
t11vfLocallyEnabledStorageType t11vfLocallyEnabledStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects for monitoring and "A collection of objects for monitoring and
configuring Virtual Fabrics in a Fibre Channel switch." configuring Virtual Fabrics in a Fibre Channel switch."
::= { t11vfMIBGroups 1 } ::= { t11vfMIBGroups 1 }
END END
draft-ietf-imss-fc-vf-mib-01.txt
8. Security Considerations 8. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB
with a MAX-ACCESS clause of read-write and/or read-create. Such module with a MAX-ACCESS clause of read-write and/or read-
objects may be considered sensitive or vulnerable in some network create. Such objects may be considered sensitive or
environments. The support for SET operations in a non-secure vulnerable in some network environments. The support for SET
environment without proper protection can have a negative effect on operations in a non-secure environment without proper
network operations. These are the tables and objects and their protection can have a negative effect on network operations.
These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
t11vfCoreSwitchMaxSupported, t11vfVirtualSwitchVfId, t11vfCoreSwitchMaxSupported, t11vfVirtualSwitchVfId,
t11vfCoreSwitchStorageType, t11vfVirtualSwitchStorageType t11vfCoreSwitchStorageType, t11vfVirtualSwitchStorageType
and t11vfVirtualSwitchRowStatus and t11vfVirtualSwitchRowStatus
- the ability to change the configuration of Virtual - the ability to change the configuration of Virtual
Fabrics on a particular switch. Fabrics on a particular switch.
t11vfPortTaggingAdminStatus, t11vfLocallyEnabledRowStatus, t11vfPortTaggingAdminStatus, t11vfLocallyEnabledRowStatus,
t11vfPortVfId, t11vfPortStorageType and t11vfPortVfId, t11vfPortStorageType and
t11vfLocallyEnabledStorageType t11vfLocallyEnabledStorageType
- the ability to change the configuration of Virtual Fabrics - the ability to change the configuration of Virtual
Fabrics
on a port of a particular switch. on a port of a particular switch.
Some of the readable objects in this MIB module (i.e., objects with Some of the readable objects in this MIB module (i.e.,
a MAX-ACCESS other than not-accessible) may be considered sensitive objects with a MAX-ACCESS other than not-accessible) may be
or vulnerable in some network environments. It is thus important to considered sensitive or vulnerable in some network
control even GET and/or NOTIFY access to these objects and possibly environments. It is thus important to control even GET
to even encrypt the values of these objects when sending them over and/or NOTIFY access to these objects and possibly to even
draft-ietf-imss-fc-vf-mib-00.txt encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and
sensitivity/vulnerability: their sensitivity/vulnerability:
t11vfVirtualSwitchCoreSwitchName, t11vfPortTaggingOperStatus, t11vfVirtualSwitchCoreSwitchName, t11vfPortTaggingOperStatus,
t11vfLocallyEnabledOperStatus, t11vfLocallyEnabledOperStatus,
- the ability to discover configuration of Virtual Fabrics on - the ability to discover configuration of Virtual
Fabrics on
a virtual switch or a port. a virtual switch or a port.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate
Even if the network itself is secure (for example by using IPSec), security. Even if the network itself is secure (for example
even then, there is no control as to who on the secure network is by using IPSec), even then, there is no control as to who on
allowed to access and GET/SET (read/change/create/delete) the the secure network is allowed to access and GET/SET
objects in this MIB module. (read/change/create/delete) the objects in this MIB module.
It is RECOMMENDED that implementers consider the security features draft-ietf-imss-fc-vf-mib-01.txt
as provided by the SNMPv3 framework (see [RFC3410], section 8), It is RECOMMENDED that implementers consider the security
including full support for the SNMPv3 cryptographic mechanisms (for features as provided by the SNMPv3 framework (see [RFC3410],
authentication and privacy). section 8), including full support for the SNMPv3
cryptographic mechanisms (for authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and
enable cryptographic security. It is then a customer/operator to enable cryptographic security. It is then a
responsibility to ensure that the SNMP entity giving access to an customer/operator responsibility to ensure that the SNMP
instance of this MIB module is properly configured to give access to entity giving access to an instance of this MIB module is
the objects only to those principals (users) that have legitimate properly configured to give access to the objects only to
rights to indeed GET or SET (change/create/delete) them. those principals (users) that have legitimate rights to
indeed GET or SET (change/create/delete) them.
9. Normative References 9. Acknowledgements
[FCMGMT-MIB] McCloghrie, K., "Fibre Channel Management MIB", RFC This document is a work item of the INCITS Task Group T11.5.
4044, May 2005 We wish to acknowledge the contributions and comments from
the INCITS Technical Committee T11 and the IMSS WG, including
the following:
T11 Chair: Robert Snively, Brocade
T11 Vice Chair: Claudio Desanti, Cisco Systems
T11.5 Chair: Roger Cummings, Symantec
IMSS WG Chair: David Black
10. Normative References
[RFC4044]
McCloghrie, K., "Fibre Channel Management MIB", RFC 4044,
May 2005
[RFC2578] [RFC2578]
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", RFC 2578, April 1999. Information Version 2 (SMIv2)", RFC 2578, April 1999.
[RFC2579] [RFC2579]
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
draft-ietf-imss-fc-vf-mib-00.txt
Rose, M. and S. Waldbusser, "Textual Conventions for Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] [RFC2580]
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for Rose, M. and S. Waldbusser, "Conformance Statements for
draft-ietf-imss-fc-vf-mib-01.txt
SMIv2", RFC 2580, April 1999. SMIv2", RFC 2580, April 1999.
[RFC2863] [RFC2863]
McCloghrie and K., Kastenholz, F., "The Interface Group McCloghrie and K., Kastenholz, F., "The Interface Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[FC-FAM-MIB] [FC-FAM-MIB]
Desanti, C., Gaonkar, V., McCloghrie, K., Gai, S., "Fibre Desanti, C., Gaonkar, V., McCloghrie, K., Gai, S., "Fibre
Channel Fabric Address Manager MIB", draft-desanti-fc- Channel Fabric Address Manager MIB", draft-desanti-fc-
fabric-addr-mgr-mib-0x.txt, April 2005. fabric-addr-mgr-mib-0x.txt, April 2005.
[FC-FS] [FC-FS]
"Fibre Channel Framing and Signaling (FC-FS)", ANSI NCITS "Fibre Channel Framing and Signaling (FC-FS)", ANSI NCITS
373-2003, April 2003. 373-2003, April 2003.
[FC-SW-4] [FC-SW-4]
"Fibre Channel Switch Fabric 4 (FC-SW-4)", ANSI NCITS xxx- "Fibre Channel Switch Fabric 4 (FC-SW-4)", ANSI NCITS xxx-
200x, T11/Project 1674-D/Rev 7.3, March 2005. 200x, T11/Project 1674-D/Rev 7.3, March 2005.
10. Author's Addresses 11. Informative References
[RFC3410]
Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[RFC2741]
Daniele, M., Wijnen, B., Ellison, M., and D. Francisco,
"Agent Extensibility (AgentX) Protocol Version 1", RFC
2741, January 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.
draft-ietf-imss-fc-vf-mib-01.txt
12. Author's Addresses
Scott Kipp, Scott Kipp,
McDATA Corporation McDATA Corporation
4 McDATA Parkway 4 McDATA Parkway
Broomfield, CO 80021 Broomfield, CO 80021
Phone: (720) 558-3452 Phone: (720) 558-3452
Email: scott.kipp@mcdata.com Email: scott.kipp@mcdata.com
G D Ramkumar G D Ramkumar
McDATA Corporation McDATA Corporation
skipping to change at page 21, line 28 skipping to change at page 19, line 29
Phone: (408) 567-5614 Phone: (408) 567-5614
Email: g.ramkumar@mcdata.com Email: g.ramkumar@mcdata.com
Keith McCloghrie Keith McCloghrie
Cisco Systems Cisco Systems
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
11. Intellectual Property 13. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of
Intellectual Property Rights or other rights that might be claimed to any Intellectual Property Rights or other rights that might
pertain to the implementation or use of the technology described in be claimed to pertain to the implementation or use of the
this document or the extent to which any license under such rights technology described in this document or the extent to which
might or might not be available; nor does it represent that it has made any license under such rights might or might not be
any independent effort to identify any such rights. Information on the available; nor does it represent that it has made any
procedures with respect to rights in RFC documents can be found in BCP independent effort to identify any such rights. Information
78 and BCP 79. on the procedures with respect to rights in RFC documents can
be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and
assurances of licenses to be made available, or the result of an any assurances of licenses to be made available, or the
attempt made to obtain a general license or permission for the use of result of an attempt made to obtain a general license or
such proprietary rights by implementers or users of this specification permission for the use of such proprietary rights by
can be obtained from the IETF on-line IPR repository at implementers or users of this specification can be obtained
from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its
copyrights, patents or patent applications, or other proprietary rights attention any copyrights, patents or patent applications, or
that may cover technology that may be required to implement this other proprietary rights that may cover technology that may
standard. Please address the information to the IETF at ietf- draft-ietf-imss-fc-vf-mib-01.txt
ipr@ietf.org. be required to implement this standard. Please address the
information to the IETF at ietf-ipr@ietf.org.
12. Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society 2005. Copyright (C) The Internet Society 2006.
draft-ietf-imss-fc-vf-mib-00.txt This document is subject to the rights, licenses and
This document is subject to the rights, licenses and restrictions restrictions contained in BCP 78, and except as set forth
contained in BCP 78, and except as set forth therein, the authors therein, the authors retain all their rights.
retain all their rights.
13. Disclaimer of Validity Disclaimer of Validity
This document and the information contained herein are provided on an This document and the information contained herein are
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS provided on an "AS IS" basis and THE CONTRIBUTOR, THE
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY),
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet
Task Force (IETF), its areas, and its working groups. Note that Engineering
other groups may also distribute working documents as Internet- Task Force (IETF), its areas, and its working groups. Note
that
other groups may also distribute working documents as
Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of
and may be updated, replaced, or obsoleted by other documents at any six months and may be updated, replaced, or obsoleted by
time. It is inappropriate to use Internet-Drafts as reference other documents at any time. It is inappropriate to use
Internet-Drafts as reference
material or to cite them other than as "work in progress." material 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/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
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
14. Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by
Internet Society. the Internet Society.
15. Expiration Notice draft-ietf-imss-fc-vf-mib-01.txt
Expiration Notice
This Internet-Draft expires in May 2006. This Internet-Draft expires in July 2006.
 End of changes. 85 change blocks. 
240 lines changed or deleted 298 lines changed or added

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