idnits 2.17.1 draft-ietf-imss-fc-virtual-fabrics-mib-00.txt: -(697): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(701): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(705): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 771. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 740. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 747. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 753. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == There are 11 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 10 instances of too long lines in the document, the longest one being 2 characters in excess of 72. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 654: '... It is RECOMMENDED that implementers...' RFC 2119 keyword, line 660: '... RECOMMENDED. Instead, it is RECOMM...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 21, 2005) is 6789 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC3410' is mentioned on line 655, but not defined == Missing Reference: 'FC-MGMT' is mentioned on line 218, but not defined == Missing Reference: 'RFC2741' is mentioned on line 190, but not defined == Missing Reference: 'RFC3411' is mentioned on line 196, but not defined == Unused Reference: 'FCMGMT-MIB' is defined on line 669, but no explicit reference was found in the text == Unused Reference: 'FC-SW-3' is defined on line 696, but no explicit reference was found in the text == Unused Reference: 'FC-SW-4' is defined on line 704, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'FCMGMT-MIB' -- No information found for draft-desanti-fc-fabric-addr-mgr-mib-0x - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'FC-FAM-MIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-SW-3' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-FS' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-SW-4' Summary: 6 errors (**), 0 flaws (~~), 10 warnings (==), 13 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET DRAFT Scott Kipp 3 G D Ramkumar 4 McDATA Corporation 6 Keith McCloghrie 7 Cisco Systems 8 September 21, 2005 10 The Virtual Fabrics MIB 11 draft-ietf-imss-fc-virtual-fabrics-mib-00.txt 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. Internet-Drafts are draft documents valid for a maximum of 24 six months and may be updated, replaced, or made obsolete by other 25 documents at any time. It is inappropriate to use Internet- Drafts 26 as reference material or to cite them other than as "work in 27 progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 Abstract 37 This memo defines a portion of the Management Information Base (MIB) 38 for use with network management protocols in the Internet community. 39 In particular, it describes managed objects for information related 40 to the Fibre Channel network's Virtual Fabrics function. 42 Table of Contents 44 Status of this Memo.................................................1 45 Abstract............................................................1 46 1. Introduction...................................................3 47 2. The Internet-Standard Management Framework.....................3 48 3. Short Overview of Fibre Channel................................3 49 4. Relationship to Other MIBs.....................................4 50 5. MIB Overview...................................................5 51 6. IANA Considerations............................................6 52 7. Definition.....................................................7 53 8. Security Considerations.......................................16 54 9. Normative References..........................................17 55 10. Author's Addresses............................................19 56 12. Intellectual Property.........................................19 57 13. Full Copyright Statement......................................19 58 14. Disclaimer of Validity........................................20 59 15. Acknowledgement...............................................20 60 16. Expiration Notice.............................................20 61 1. Introduction 63 This memo defines a portion of the Management Information Base (MIB) 64 for use with network management protocols in the Internet community. 65 In particular, it describes managed objects for information related 66 to the Fibre Channel network's Virtual Fabric function. 68 2. The Internet-Standard Management Framework 70 For a detailed overview of the documents that describe the current 71 Internet-Standard Management Framework, please refer to section 7 of 72 RFC 3410 [RFC3410]. Managed objects are accessed via a virtual 73 information store, termed the Management Information Base or MIB. 74 MIB objects are generally accessed through the Simple Network 75 Management Protocol (SNMP). 77 Objects in the MIB are defined using the mechanisms defined in the 78 Structure of Management Information (SMI). This memo specifies a MIB 79 module that is compliant to the SMIv2, which is described in STD 58, 80 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 81 [RFC2580]. 83 3. Short Overview of Fibre Channel 85 The Fibre Channel (FC) is logically a bidirectional point-to-point 86 serial data channel, structured for high performance. Fibre Channel 87 provides a general transport vehicle for higher level protocols such 88 as Small Computer System Interface (SCSI) command sets, the High- 89 Performance Parallel Interface (HIPPI) data framing, IP (Internet 90 Protocol), IEEE 802.2, and others. 92 Physically, Fibre Channel is an interconnection of multiple 93 communication points, called N_Ports, interconnected either by a 94 switching network, called a Fabric, or by a point-to-point link. A 95 Fibre Channel "node" consists of one or more N_Ports. A Fabric may 96 consist of multiple Interconnect Elements, some of which are 97 switches. An N_Port connects to the Fabric via a port on a switch 98 called an F_Port. When multiple FC nodes are connected to a single 99 port on a switch via an "Arbitrated Loop" topology, the switch port 100 is called an FL_Port, and the nodes' ports are called NL_Ports. The 101 term Nx_Port is used to refer to either an N_Port or an NL_Port. The 102 term Fx_Port is used to refer to either an F_Port or an FL_Port. A 103 switch port, which is interconnected to another switch port via an 104 Inter-Switch Link (ISL), is called an E_Port. A B_Port connects a 105 bridge device with an E_Port on a switch; a B_Port provides a subset 106 of E_Port functionality. 108 Many Fibre Channel components, including the Fabric, each node, and 109 most ports, have globally-unique names. These globally-unique names 110 are typically formatted as World Wide Names (WWNs). More information 111 on WWNs can be found in [FC-FS]. WWNs are expected to be persistent 112 across agent and unit resets. 114 Fibre Channel frames contain 24-bit address identifiers which 115 identify the frame's source and destination ports. Each FC port has 116 both an address identifier and a WWN. When a Fabric is in use, the 117 FC address identifiers are dynamic and are assigned by a switch. 118 Each octet of a 24-bit address represents a level in an address 119 hierarchy, with a Domain_ID being the highest level of the 120 hierarchy. 122 Virtual Fabrics allow a single physical Fabric to be divided into 123 multiple logical Fabrics. Each Virtual Fabric may be managed 124 independently like traditional Fabrics. Virtual Fabrics are 125 designed to achieve a better utilization of a physical 126 infrastructure and to isolate events in one Virtual Fabric from 127 affecting other Fabrics. When one Core Switch provides switching 128 functions for multiple Virtual Fabrics, that Core Switch is modeled 129 as containing multiple Virtual Switches, one for each Virtual 130 Fabric. 132 Each Virtual Fabric is identified by a 12-bit Virtual Fabric ID 133 (VF_ID). When frames from multiple Virtual Fabrics are transmitted 134 over a physical link, the VF_ID carried in a frame�s Virtual Fabric 135 Tagging Header (VFT_Header) identifies which Virtual Fabric the 136 frame belongs to. The use of VFT_Headers is enabled through an 137 initial negotiation exchange between the two connected ports. 139 4. Relationship to Other MIBs 141 This MIB extends beyond [FC-MGMT] to cover the functionality, in 142 Fibre Channel switches, of providing Fibre Channel's Virtual 143 Fabrics function. 145 5. MIB Overview 147 This MIB module provides the means for monitoring the operation of, 148 and configuring some parameters of, one or more instances of Fibre 149 Channel Virtual Fabric functionality. (Note that there are no 150 definitions in this MIB module of "managed actions" which can be 151 invoked via SNMP.) 153 5.1 Fibre Channel management instance 155 A Fibre Channel management instance is defined in [FC-MGMT] as a 156 separable managed instance of Fibre Channel functionality. Fibre 157 Channel functionality may be grouped into Fibre Channel management 158 instances in whatever way is most convenient for the 159 implementation(s). For example, one such grouping accommodates a 160 single SNMP agent having multiple AgentX [RFC2741] sub-agents, with 161 each sub-agent implementing a different Fibre Channel management 162 instance. 164 The object, fcmInstanceIndex, is IMPORTed from the FC-MGMT-MIB [FC- 165 MGMT] as the index value to uniquely identify each Fibre Channel 166 management instance within the same SNMP context ([RFC3411] section 167 3.3.1). The t11vfVirtualSwitchTable augments the fcmSwitchTable, and 168 the primary index variable of the fcmSwitchTable is 169 fcmInstanceIndex. 171 5.2 Representing Core and Virtual Switches 173 In the presence of Virtual Switches, fcmSwitchTable in the FC-MGMT- 174 MIB contains a row for each Virtual Switch. fcmSwitchTable, 175 t11vfCoreSwitchTable and t11vfVirtualSwitchTable are complementary. 176 The t11vfCoreSwitchTable and t11vfVirtualSwitchTable contain 177 information that helps the management client determine which 178 Switches are Virtual Switches and how each relates to a Core Switch. 179 A Virtual Switch must reside in a single Core Switch and a Core 180 Switch is defined as a set of entities with the same Core 181 Switch_Name. 183 5.3 Fibre Channel management instance 185 A Fibre Channel management instance is defined in [FC-MGMT] as a 186 separable managed instance of Fibre Channel functionality. Fibre 187 Channel functionality may be grouped into Fibre Channel management 188 instances in whatever way is most convenient for the 189 implementation(s). For example, one such grouping accommodates a 190 single SNMP agent having multiple AgentX [RFC2741] sub-agents, with 191 each sub-agent implementing a different Fibre Channel management 192 instance. 194 The object, fcmInstanceIndex, is IMPORTed from the FC-MGMT-MIB [FC- 195 MGMT] as the index value to uniquely identify each Fibre Channel 196 management instance within the same SNMP context ([RFC3411] section 197 3.3.1). 199 6. IANA Considerations 201 IANA is requested to make the OID assignment for the MIB module 202 under the appropriate subtree. 204 7. Definition 206 T11-IETF-IMSS-FC-VIRTUAL-FABRIC-MIB DEFINITIONS ::= BEGIN 208 IMPORTS 209 MODULE-IDENTITY, OBJECT-TYPE, 210 Unsigned32, mib-2 211 FROM SNMPv2-SMI -- [RFC2578] 212 MODULE-COMPLIANCE, OBJECT-GROUP 213 FROM SNMPv2-CONF -- [RFC2580] 214 RowStatus FROM SNMPv2-TC -- [RFC2579] 215 InterfaceIndex FROM IF-MIB -- [RFC2863] 216 fcmInstanceIndex, FcNameIdOrZero, 217 fcmPortEntry, fcmSwitchEntry 218 FROM FC-MGMT-MIB -- [FC-MGMT] 219 T11FabricIndex FROM T11-TC-MIB; -- [FC-FAM-MIB] 221 t11FcVirtualFabricMIB MODULE-IDENTITY 222 LAST-UPDATED "200509210000Z" 223 ORGANIZATION "IETF IMSS (Internet and Management Support 224 for Storage)Working Group" 225 CONTACT-INFO 226 " 227 Scott Kipp 228 McDATA Corporation 229 Tel: +1 720 558-3452 230 E-mail: scott.kipp@mcdata.com 231 Postal: 4 McDATA Parkway 232 Broomfield, CO USA 80021 234 G D Ramkumar 235 McDATA Corporation 236 Tel: +1 408 567-5614 237 E-mail: g.ramkumar@mcdata.com 238 Postal: 4555 Great American Parkway 239 Santa Clara, CA USA 95054 241 Keith McCloghrie 242 Cisco Systems, Inc. 243 Tel: +1 408 526-5260 244 E-mail: kzm@cisco.com 245 Postal: 170 West Tasman Drive 246 San Jose, CA USA 95134 247 " 248 DESCRIPTION 249 "This module defines management information specific to 250 Fibre Channel Virtual Fabrics. A Virtual Fabric is a 251 Fabric composed of partitions of switches, links and N_Ports 252 with a single Fabric management domain, Fabric Services 253 and independence from other Virtual Fabrics. 255 Copyright (C) The Internet Society (2005). This version of 256 this MIB module is part of RFC yyyy; see the RFC itself for 257 full legal notices." 258 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 259 REVISION "200509210000Z" 260 DESCRIPTION 261 "Initial version of this MIB module." 262 ::= { mib-2 nnn } -- IANA, please enter the value you assign here 264 t11vfObjects OBJECT IDENTIFIER ::= { t11FcVirtualFabricMIB 1 } 265 t11vfConformance OBJECT IDENTIFIER ::= { t11FcVirtualFabricMIB 2 } 267 --******************************** 268 -- MIB object definitions 269 -- 271 t11vfCoreSwitchTable OBJECT-TYPE 272 SYNTAX SEQUENCE OF T11vfCoreSwitchEntry 273 MAX-ACCESS not-accessible 274 STATUS current 275 DESCRIPTION 276 "A table of core switches supported by the current 277 management entity." 278 ::= { t11vfObjects 1 } 280 t11vfCoreSwitchEntry OBJECT-TYPE 281 SYNTAX T11vfCoreSwitchEntry 282 MAX-ACCESS not-accessible 283 STATUS current 284 DESCRIPTION 285 "Each entry represents one core switch." 286 INDEX { fcmInstanceIndex, t11vfCoreSwitchSwitchName } 287 ::= { t11vfCoreSwitchTable 1} 289 T11vfCoreSwitchEntry ::= 290 SEQUENCE { 291 t11vfCoreSwitchSwitchName FcNameIdOrZero, 292 t11vfCoreSwitchMaxSupported Unsigned32 293 } 295 t11vfCoreSwitchSwitchName OBJECT-TYPE 296 SYNTAX FcNameIdOrZero 297 MAX-ACCESS not-accessible 298 STATUS current 299 DESCRIPTION 300 "The Core Switch_Name (WWN) of this Core Switch. A 301 zero-length string for this field is not allowed. " 302 ::= { t11vfCoreSwitchEntry 1 } 304 t11vfCoreSwitchMaxSupported OBJECT-TYPE 305 SYNTAX Unsigned32 306 MAX-ACCESS read-write 307 STATUS current 308 DESCRIPTION 309 " In switches that do not support Virtual Fabrics, 310 this object has the value of 1. If Virtual Fabrics 311 are supported, this object is the maximum number of 312 Virtual Fabrics supported by the Core Switch. For 313 the purpose of this count, the Control VF_ID is 314 ignored." 315 ::= { t11vfCoreSwitchEntry 2 } 317 -- Virtual Switch table 319 t11vfVirtualSwitchTable OBJECT-TYPE 320 SYNTAX SEQUENCE OF T11vfVirtualSwitchEntry 321 MAX-ACCESS not-accessible 322 STATUS current 323 DESCRIPTION 324 "A table of Virtual Switches. When one Core Switch 325 provides switching functions for multiple Virtual Fabrics, 326 that Core Switch is modeled as containing multiple 327 Virtual Switches, one for each Virtual Fabric. This table 328 contains one row for every Virtual Switch on every Core 329 Switch. This table augments the basic switch information in 330 the fcmSwitchTable Table in the FCMGMT-MIB." 331 REFERENCE 332 "fcmSwitchTable is defined in the FCMGMT-MIB module." 333 ::= { t11vfObjects 2 } 335 t11vfVirtualSwitchEntry OBJECT-TYPE 336 SYNTAX T11vfVirtualSwitchEntry 337 MAX-ACCESS not-accessible 338 STATUS current 340 DESCRIPTION 341 "An entry of the Virtual Switch table. Each row is for a 342 Virtual Switch." 343 REFERENCE 344 "fcmSwitchEntry is defined in the FCMGMT-MIB module." 345 AUGMENTS { fcmSwitchEntry } 346 ::= { t11vfVirtualSwitchTable 1} 348 T11vfVirtualSwitchEntry ::= 349 SEQUENCE { 350 t11vfVirtualSwitchVfId T11FabricIndex, 351 t11vfVirtualSwitchCoreSwitchName FcNameIdOrZero, 352 t11vfVirtualSwitchRowStatus RowStatus 353 } 355 t11vfVirtualSwitchVfId OBJECT-TYPE 356 SYNTAX T11FabricIndex 357 MAX-ACCESS read-create 358 STATUS current 359 DESCRIPTION 360 "The VF_ID of the Virtual Fabric for which this virtual 361 switch performs its switching function. The Control 362 VF_ID is implicitly enabled and is not set. 363 Communication with the Control VF_ID is required. " 364 REFERENCE 365 "FC-SW-4, REV 7.5, section 12.2" 366 ::= { t11vfVirtualSwitchEntry 1 } 368 t11vfVirtualSwitchCoreSwitchName OBJECT-TYPE 369 SYNTAX FcNameIdOrZero 370 MAX-ACCESS read-only 371 STATUS current 372 DESCRIPTION 373 "The Core Switch_Name (WWN) of the Core Switch that 374 contains this Virtual Switch." 375 REFERENCE 376 "FC-SW-4, REV 7.5, section 12.2." 377 ::= { t11vfVirtualSwitchEntry 2 } 379 t11vfVirtualSwitchRowStatus OBJECT-TYPE 380 SYNTAX RowStatus 381 MAX-ACCESS read-create 382 STATUS current 383 DESCRIPTION 384 "The status of this row." 385 ::= { t11vfVirtualSwitchEntry 3 } 387 -- Port table 389 t11vfPortTable OBJECT-TYPE 390 SYNTAX SEQUENCE OF T11vfPortEntry 391 MAX-ACCESS not-accessible 392 STATUS current 393 DESCRIPTION 394 "A table of Port attributes related to Virtual Fabrics." 395 ::= { t11vfObjects 3 } 397 t11vfPortEntry OBJECT-TYPE 398 SYNTAX T11vfPortEntry 399 MAX-ACCESS not-accessible 400 STATUS current 401 DESCRIPTION 402 "Each entry represents a physical Port on a switch." 403 REFERENCE 404 "fcmPortEntry is defined in the FCMGMT-MIB module." 405 AUGMENTS { fcmPortEntry } 406 ::= { t11vfPortTable 1} 408 T11vfPortEntry ::= 409 SEQUENCE { 410 t11vfPortVfId T11FabricIndex, 411 t11vfPortTaggingAdminStatus INTEGER 412 t11vfPortTaggingOperStatus INTEGER 413 } 415 t11vfPortVfId OBJECT-TYPE 416 SYNTAX T11FabricIndex 417 MAX-ACCESS read-write 418 STATUS current 419 DESCRIPTION 420 "The Port VF_ID assigned to this Port. The Port VF_ID is the 421 default Virtual Fabric that is assigned to untagged frames 422 arriving at this Port. The Control VF_ID is implicitly 423 enabled and is not set. Communication with the Control 424 VF_ID is required. " 426 REFERENCE 427 "FC-SW-4, REV 7.5, section 12.1" 428 ::= { t11vfPortEntry 1 } 429 DEFVAL {1} 431 t11vfPortTaggingAdminStatus OBJECT-TYPE 432 SYNTAX INTEGER { 433 off(1), 434 on(2), 435 auto(3) 436 } 437 MAX-ACCESS read-write 438 STATUS current 439 DESCRIPTION 440 "This object is used to configure the administrative status 441 of Virtual Fabric tagging on this Port. 443 SET operation Description 444 -------------- ------------------------------------------- 445 off(1) To disable Virtual Fabric tagging on this 446 Port. 448 on(2) To enable Virtual Fabric tagging on this 449 Port if the attached Port doesn't 450 prohibit it. 452 auto(3) To enable Virtual Fabric tagging if the 453 peer requests it. " 454 REFERENCE 455 " FC-SW-4, REV 7.5, section 12.4" 456 ::= { t11vfPortEntry 2 } 458 t11vfPortTaggingOperStatus OBJECT-TYPE 459 SYNTAX INTEGER { 460 off(1), 461 on(2), 462 } 463 MAX-ACCESS read-only 464 STATUS current 465 DESCRIPTION 466 "This object is used to report the operational status of 467 Virtual Fabric tagging on this Port. 469 SET operation Description 470 -------------- ------------------------------------------- 471 off(1) Virtual Fabric tagging is disabled on this 472 Port. 474 on(2) Virtual Fabric tagging is enabled on this 475 Port. 477 REFERENCE 478 " FC-SW-4, REV 7.5, section 12.4" 479 ::= { t11vfPortEntry 3 } 481 -- Locally Enabled Table 483 t11vfLocallyEnabledTable OBJECT-TYPE 484 SYNTAX SEQUENCE OF T11vfLocallyEnabledEntry 485 MAX-ACCESS not-accessible 486 STATUS current 487 DESCRIPTION 488 "A table for assigning and reporting operational status of 489 Locally-enabled Virtual Fabric IDs to Ports. The set of 490 Virtual Fabrics operational on the Port is the bit-wise 491 �AND� of the set of Locally-enabled VF_IDs of this Port 492 and the Locally-enabled VF_IDs of the attached Port." 493 ::= { t11vfObjects 4 } 495 t11vfLocallyEnabledEntry OBJECT-TYPE 496 SYNTAX T11vfLocallyEnabledEntry 497 MAX-ACCESS not-accessible 498 STATUS current 499 DESCRIPTION 500 "An entry for each Locally-enabled VF_ID on 501 each Port." 502 REFERENCE 503 " FC-SW-4, REV 7.5, section 12.4" 504 INDEX { t11vfLocallyEnabledPortIfIndex, t11vfLocallyEnabledVfId } 506 ::= { t11vfLocallyEnabledTable 1} 508 T11vfLocallyEnabledEntry ::= 509 SEQUENCE { 510 t11vfLocallyEnabledPortIfIndex InterfaceIndex, 511 t11vfLocallyEnabledVfId T11FabricIndex, 512 t11vfLocallyEnabledOperStatus Integer, 513 t11vfLocallyEnabledRowStatus RowStatus 514 } 516 t11vfLocallyEnabledPortIfIndex OBJECT-TYPE 517 SYNTAX InterfaceIndex 518 MAX-ACCESS not-accessible 519 STATUS current 520 DESCRIPTION 521 "The value of the ifIndex which identifies the Port." 522 ::= { t11vfLocallyEnabledEntry 1 } 524 t11vfLocallyEnabledVfId OBJECT-TYPE 525 SYNTAX T11FabricIndex 526 MAX-ACCESS not-accessible 527 STATUS current 528 DESCRIPTION 529 "A Locally-Enabled VF_ID on this Port." 530 ::= { t11vfLocallyEnabledEntry 2 } 532 t11vfLocallyEnabledOperStatus OBJECT-TYPE 533 SYNTAX INTEGER { 534 off(1), 535 on(2), 536 } 537 MAX-ACCESS read-only 538 STATUS current 539 DESCRIPTION 540 "This object is used to report the operational status of 541 Virtual Fabric tagging on this Port. 543 SET operation Description 544 -------------- ------------------------------------------- 545 off(1) Virtual Fabric tagging is disabled on this 546 Port. 548 on(2) Virtual Fabric tagging is enabled on this 549 Port. 551 REFERENCE 552 " FC-SW-4, REV 7.3, section 12.4" 553 ::= { t11vfPortEntry 3 } 555 t11vfLocallyEnabledRowStatus OBJECT-TYPE 556 SYNTAX RowStatus 557 MAX-ACCESS read-create 558 STATUS current 559 DESCRIPTION 560 "The status of this conceptual row." 561 ::= { t11vfLocallyEnabledEntry 4 } 563 --******************************** 564 -- Conformance Section 565 -- 567 t11vfMIBCompliances OBJECT IDENTIFIER ::= { t11vfConformance 1 } 568 t11vfMIBGroups OBJECT IDENTIFIER ::= { t11vfConformance 2 } 570 t11vfMIBCompliance MODULE-COMPLIANCE 571 STATUS current 572 DESCRIPTION 573 "Describes the requirements for compliance to the 574 Fibre Channel Virtual Fabric MIB." 575 MODULE -- this module 576 MANDATORY-GROUPS { t11vfGeneralGroup } 578 OBJECT t11vfCoreSwitchMaxSupported 579 MIN-ACCESS read-only 580 DESCRIPTION 581 "Write access is not required." 583 OBJECT t11vfPortVfId 584 MIN-ACCESS read-only 585 DESCRIPTION 586 "Write access is not required." 588 OBJECT t11vfPortTaggingAdminStatus 589 MIN-ACCESS read-only 590 DESCRIPTION 591 "Write access is not required." 593 OBJECT t11vfVirtualSwitchVfId 594 MIN-ACCESS read-only 595 DESCRIPTION 596 "Write access is not required." 598 OBJECT t11vfVirtualSwitchRowStatus 599 MIN-ACCESS read-only 600 DESCRIPTION 601 "Write access is not required." 603 OBJECT t11vfLocallyEnabledVfId 604 MIN-ACCESS read-only 605 DESCRIPTION 606 "Write access is not required." 608 OBJECT t11vfLocallyEnabledRowStatus 609 MIN-ACCESS read-only 610 DESCRIPTION 611 "Write access is not required." 613 ::= { t11vfMIBCompliances 1 } 615 -- Units of conformance 617 t11vfGeneralGroup OBJECT-GROUP 618 OBJECTS { t11vfCoreSwitchMaxSupported, 619 t11vfVirtualSwitchVfId, 620 t11vfVirtualSwitchCoreSwitchName, 621 t11vfVirtualSwitchRowStatus, 622 t11vfPortVfId, 623 t11vfPortTaggingStatus, 624 t11vfLocallyEnabledVfId, 625 t11vfLocallyEnabledRowStatus 626 } 627 STATUS current 628 DESCRIPTION 629 "A collection of objects for monitoring and 630 configuring Virtual Fabrics in a Fibre Channel switch." 631 ::= { t11vfMIBGroups 1 } 633 END 635 8. Security Considerations 637 There are a number of management objects defined in this MIB module 638 with a MAX-ACCESS clause of read-write and/or read-create. Such 639 objects may be considered sensitive or vulnerable in some network 640 environments. The support for SET operations in a non-secure 641 environment without proper protection can have a negative effect on 642 network operations. These are the tables and objects and their 643 sensitivity/vulnerability: 645 t11vfCoreSwitchMaxSupported, t11vfVirtualSwitchVfId, t11vfPortVfId, 646 t11vfPortTaggingStatus, t11vfLocallyEnabledVfId 648 SNMP versions prior to SNMPv3 did not include adequate security. 649 Even if the network itself is secure (for example by using IPSec), 650 even then, there is no control as to who on the secure network is 651 allowed to access and GET/SET (read/change/create/delete) the 652 objects in this MIB module. 654 It is RECOMMENDED that implementers consider the security features 655 as provided by the SNMPv3 framework (see [RFC3410], section 8), 656 including full support for the SNMPv3 cryptographic mechanisms (for 657 authentication and privacy). 659 Further, deployment of SNMP versions prior to SNMPv3 is NOT 660 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 661 enable cryptographic security. It is then a customer/operator 662 responsibility to ensure that the SNMP entity giving access to an 663 instance of this MIB module is properly configured to give access to 664 the objects only to those principals (users) that have legitimate 665 rights to indeed GET or SET (change/create/delete) them. 667 9. Normative References 669 [FCMGMT-MIB] McCloghrie, K., "Fibre Channel Management MIB", 670 Working draft, January 2005 672 [RFC2578] 673 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 674 Rose, M. and S. Waldbusser, "Structure of Management 675 Information Version 2 (SMIv2)��, RFC 2578, April 1999. 677 [RFC2579] 678 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 679 Rose, M. and S. Waldbusser, "Textual Conventions for 680 SMIv2��, STD 58, RFC 2579, April 1999. 682 [RFC2580] 683 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 684 Rose, M. and S. Waldbusser, "Conformance Statements for 685 SMIv2��, RFC 2580, April 1999. 687 [RFC2863] 688 McCloghrie and K., Kastenholz, F., "The Interface Group 689 MIB��, RFC 2863, June 2000. 691 [FC-FAM-MIB] 692 Desanti, C., Gaonkar, V., McCloghrie, K., Gai, S., "Fibre 693 Channel Fabric Address Manager MIB��, draft-desanti-fc- 694 fabric-addr-mgr-mib-0x.txt, April 2005. 696 [FC-SW-3] 697 ��Fibre Channel Switch Fabric 3 (FC-SW-3)��, ANSI NCITS 384- 698 2004, T11/Project 1508-D/Rev 6.6, December 2003. 700 [FC-FS] 701 ��Fibre Channel Framing and Signaling (FC-FS)��, ANSI NCITS 702 373-2003, April 2003. 704 [FC-SW-4] 705 ��Fibre Channel Switch Fabric 4 (FC-SW-4)��, ANSI NCITS xxx- 706 200x, T11/Project 1674-D/Rev 7.3, March 2005. 708 10. Author's Addresses 710 Scott Kipp, 711 McDATA Corporation 712 4 McDATA Parkway 713 Broomfield, CO 80021 714 Phone: (720) 558-3452 715 Email: scott.kipp@mcdata.com 717 G D Ramkumar 718 McDATA Corporation 719 4555 Great American Parkway 720 Santa Clara, CA 95054 721 Phone: (408) 567-5614 722 Email: g.ramkumar@mcdata.com 724 Keith McCloghrie 725 Cisco Systems 726 170 West Tasman Drive 727 San Jose, CA USA 95134 728 Phone : +1 408-526-5260 729 Email : kzm@cisco.com 731 11. Intellectual Property 733 The IETF takes no position regarding the validity or scope of any 734 Intellectual Property Rights or other rights that might be claimed to 735 pertain to the implementation or use of the technology described in 736 this document or the extent to which any license under such rights 737 might or might not be available; nor does it represent that it has made 738 any independent effort to identify any such rights. Information on the 739 procedures with respect to rights in RFC documents can be found in BCP 740 78 and BCP 79. 742 Copies of IPR disclosures made to the IETF Secretariat and any 743 assurances of licenses to be made available, or the result of an 744 attempt made to obtain a general license or permission for the use of 745 such proprietary rights by implementers or users of this specification 746 can be obtained from the IETF on-line IPR repository at 747 http://www.ietf.org/ipr. 749 The IETF invites any interested party to bring to its attention any 750 copyrights, patents or patent applications, or other proprietary rights 751 that may cover technology that may be required to implement this 752 standard. Please address the information to the IETF at ietf- 753 ipr@ietf.org. 755 12. Full Copyright Statement 757 Copyright (C) The Internet Society 2005. 759 This document is subject to the rights, licenses and restrictions 760 contained in BCP 78, and except as set forth therein, the authors 761 retain all their rights. 763 13. Disclaimer of Validity 765 This document and the information contained herein are provided on an 766 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 767 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 768 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 769 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 770 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 771 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 773 Internet-Drafts are working documents of the Internet Engineering Task 774 Force (IETF), its areas, and its working groups. Note that other groups 775 may also distribute working documents as Internet-Drafts. 777 Internet-Drafts are draft documents valid for a maximum of six months 778 and may be upated, replaced, or obsoleted by other documents at any 779 time. It is inappropriate to use Internet-Drafts as reference material 780 or to cite them other than a ��work in progress.�� 782 The list of current Internet-Drafts can be accessed at 783 http://www.ietf.org/1id-abstracts.html 785 The list of Internet-Draft Shadow Directories can be accessed at 786 http://www.ietf.org/shadow.html 788 14. Acknowledgement 790 Funding for the RFC Editor function is currently provided by the 791 Internet Society. 793 15. Expiration Notice 795 This Internet-Draft expires in March 2006.