idnits 2.17.1 draft-ietf-imss-fc-vf-mib-02.txt: 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 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 941. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 908. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 916. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 922. ** 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: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 10 longer pages, the longest (page 16) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 7. Security Considerations' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) (A line matching the expected section header was found, but with an unexpected indentation: ' 8. IANA Considerations' ) ** The document seems to lack an Authors' Addresses Section. ** There are 2 instances of too long lines in the document, the longest one being 2 characters in excess of 72. ** There are 2 instances of lines with control characters in the document. ** 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 787: '... It is RECOMMENDED that implementers...' RFC 2119 keyword, line 793: '... 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 (April 27, 2006) is 6567 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) ** Downref: Normative reference to an Experimental RFC: RFC 4389 (ref. 'FC-FAM-MIB') -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-FS' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-SW-4' Summary: 10 errors (**), 0 flaws (~~), 3 warnings (==), 9 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 April 27, 2006 10 The Virtual Fabrics MIB 11 draft-ietf-imss-fc-vf-mib-02.txt 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents 16 that any applicable patent or other IPR claims of which he or 17 she is aware have been or will be disclosed, and any of which 18 he or she becomes aware will be disclosed, in accordance with 19 Section 6 of BCP 79. 21 Internet-Drafts are working documents of the Internet 22 Engineering 24 Task Force (IETF), its areas, and its working groups. Note 25 that other groups may also distribute working documents as 26 Internet-Drafts. Internet-Drafts are draft documents valid 27 for a maximum of six months and may be updated, replaced, or 28 made obsolete by other documents at any time. It is 29 inappropriate to use Internet- Drafts as reference material 30 or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt 35 The list of Internet-Draft Shadow Directories can be accessed 36 at http://www.ietf.org/shadow.html. 38 Abstract 40 This memo defines a portion of the Management Information 41 Base (MIB) for use with network management protocols in the 42 Internet community. In particular, it describes managed 43 objects for information related to the Fibre Channel 44 network's Virtual Fabrics function. 46 Table of Contents 48 1. Introduction.....................................................3 49 2. The Internet-Standard Management Framework.......................3 50 3. Short Overview of Fibre Channel..................................3 51 4. Relationship to Other MIBs.......................................4 52 5. MIB Overview.....................................................5 53 5.1 Fibre Channel management instance...............................5 54 5.2 Representing Core and Virtual Switches..........................5 55 6. The T11-FC-IRTUAL-FABRIC-MIB Module..............................7 56 7. Security Considerations.........................................17 57 8. IANA Considerations.............................................18 58 9. Acknowledgements................................................18 59 10. Normative References...........................................19 60 11. Informative References.........................................19 61 12. Author's Addresses.............................................21 62 13. Intellectual Property..........................................22 63 1. Introduction 65 This memo defines a portion of the Management Information 66 Base (MIB) for use with network management protocols in the 67 Internet community. In particular, it describes managed 68 objects for information related to the Fibre Channel 69 network's Virtual Fabric function. 71 2. The Internet-Standard Management Framework 73 For a detailed overview of the documents that describe the 74 current Internet-Standard Management Framework, please refer 75 to section 7 of RFC 3410 [RFC3410]. Managed objects are 76 accessed via a virtual information store, termed the 77 Management Information Base or MIB. MIB objects are generally 78 accessed through the Simple Network Management Protocol 79 (SNMP). 81 Objects in the MIB are defined using the mechanisms defined 82 in the Structure of Management Information (SMI). This memo 83 specifies a MIB module that is compliant to the SMIv2, which 84 is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 85 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 87 3. Short Overview of Fibre Channel 89 The Fibre Channel (FC) is logically a bidirectional point-to- 90 point serial data channel, structured for high performance. 91 Fibre Channel provides a general transport vehicle for higher 92 level protocols such as Small Computer System Interface 93 (SCSI) command sets, the High-Performance Parallel Interface 94 (HIPPI) data framing, IP (Internet Protocol), IEEE 802.2, and 95 others. 97 Physically, Fibre Channel is an interconnection of multiple 98 communication points, called N_Ports, interconnected either 99 by a switching network, called a Fabric, or by a point-to- 100 point link. A Fibre Channel "node" consists of one or more 101 N_Ports. A Fabric may consist of multiple Interconnect 102 Elements, some of which are switches. An N_Port connects to 103 the Fabric via a port on a switch called an F_Port. When 104 multiple FC nodes are connected to a single port on a switch 105 via an "Arbitrated Loop" topology, the switch port is called 106 an FL_Port, and the nodes' ports are called NL_Ports. The 107 term Nx_Port is used to refer to either an N_Port or an 108 NL_Port. The term Fx_Port is used to refer to either an 109 F_Port or an FL_Port. A switch port, which is interconnected 110 to another switch port via an Inter-Switch Link (ISL), is 111 called an E_Port. A B_Port connects a bridge device with an 112 E_Port on a switch; a B_Port provides a subset of E_Port 113 functionality. 115 Many Fibre Channel components, including the Fabric, each 116 node, and most ports, have globally-unique names. These 117 globally-unique names are typically formatted as World Wide 118 Names (WWNs). More information on WWNs can be found in [FC- 119 FS]. WWNs are expected to be persistent across agent and unit 120 resets. 122 Fibre Channel frames contain 24-bit address identifiers which 123 identify the frame's source and destination ports. Each FC 124 port has both an address identifier and a WWN. When a Fabric 125 is in use, the FC address identifiers are dynamic and are 126 assigned by a switch. Each octet of a 24-bit address 127 represents a level in an address hierarchy, with a Domain_ID 128 being the highest level of the hierarchy. 130 Virtual Fabrics allow a single physical Fabric to be divided 131 into multiple logical Fabrics. Each Virtual Fabric may be 132 managed independently like traditional Fabrics. Virtual 133 Fabrics are designed to achieve a better utilization of a 134 physical infrastructure and to isolate events in one Virtual 135 Fabric from affecting other Fabrics. When one Core Switch 136 provides switching functions for multiple Virtual Fabrics, 137 that Core Switch is modeled as containing multiple Virtual 138 Switches, one for each Virtual Fabric. 140 Each Virtual Fabric is identified by a 12-bit Virtual Fabric 141 ID (VF_ID). When frames from multiple Virtual Fabrics are 142 transmitted over a physical link, the VF_ID carried in a 143 frame's Virtual Fabric Tagging Header (VFT_Header) identifies 144 which Virtual Fabric the frame belongs to. The use of 145 VFT_Headers is enabled through an initial negotiation 146 exchange between the two connected ports. 148 4. Relationship to Other MIBs 150 This MIB extends beyond [RFC4044] to cover the functionality, 151 in Fibre Channel switches, of providing Fibre Channel's 152 Virtual 154 Fabrics function. 156 5. MIB Overview 158 This MIB module provides the means for monitoring the 159 operation of, and configuring some parameters of, one or more 160 instances of Fibre Channel Virtual Fabric functionality. 161 (Note that there are no definitions in this MIB module of 162 "managed actions" which can be invoked via SNMP.) 164 The following MIB module has IMPORTS from [RFC2578], 165 [RFC2579], [RFC2580], [RFC2863], [RFC4044] and [FC-FAM-MIB]. 166 In REFERENCE clauses, it refers to [FC-SW-4]. 168 5.1 Fibre Channel management instance 170 A Fibre Channel management instance is defined in [RFC4044] 171 as a separable managed instance of Fibre Channel 172 functionality. Fibre Channel functionality may be grouped 173 into Fibre Channel management instances in whatever way is 174 most convenient for the implementation(s). For example, one 175 such grouping accommodates a single SNMP agent having 176 multiple AgentX [RFC2741] sub-agents, with each sub-agent 177 implementing a different Fibre Channel management instance. 179 The object, fcmInstanceIndex, is IMPORTed from the FC-MGMT- 180 MIB [RFC4044] as the index value to uniquely identify each 181 Fibre Channel management instance within the same SNMP 182 context ([RFC3411] section 3.3.1). The 183 t11vfVirtualSwitchTable augments the fcmSwitchTable, and the 184 primary index variable of the fcmSwitchTable is 185 fcmInstanceIndex. 187 5.2 Representing Core and Virtual Switches 189 In the presence of Virtual Switches, fcmSwitchTable in 190 RFC4044 contains a row for each Virtual Switch. 191 fcmSwitchTable, t11vfCoreSwitchTable and 192 t11vfVirtualSwitchTable are complementary. The 193 t11vfCoreSwitchTable and t11vfVirtualSwitchTable contain 194 information that helps the management client determine which 195 Switches are Virtual Switches and how each relates to a Core 196 Switch. A Virtual Switch must reside in a single Core Switch 197 and a Core Switch is defined as a set of entities with the 198 same Core Switch_Name. 200 RFC 4044 was defined before Virtual Switches were standard 201 and represented only physical Switches, so the RFC 4044 202 tables were not defined as read-create. With the advent of 203 Virtual Switches, Virtual Switches can now be created by 204 administrators and read-create tables are required. The 205 StorageType of RFC 4044 tables were not defined and 206 StorageTypes used in this MIB should also apply to the 207 RFC4044 tables that this MIB augments. 209 6. The T11-FC-IRTUAL-FABRIC-MIB Module 211 T11-FC-VIRTUAL-FABRIC-MIB DEFINITIONS ::= BEGIN 213 IMPORTS 214 MODULE-IDENTITY, OBJECT-TYPE, 215 Unsigned32, mib-2 216 FROM SNMPv2-SMI -- [RFC2578] 217 MODULE-COMPLIANCE, OBJECT-GROUP 218 FROM SNMPv2-CONF -- [RFC2580] 219 RowStatus, StorageType FROM SNMPv2-TC -- [RFC2579] 220 InterfaceIndex FROM IF-MIB -- [RFC2863] 221 fcmInstanceIndex, FcNameIdOrZero, 222 fcmPortEntry, fcmSwitchEntry 223 FROM FC-MGMT-MIB -- [RFC4044] 224 T11FabricIndex FROM T11-TC-MIB; -- [FC-FAM-MIB] 226 t11FcVirtualFabricMIB MODULE-IDENTITY 227 LAST-UPDATED "200604270000Z" 228 ORGANIZATION "IETF IMSS (Internet and Management Support 229 for Storage)Working Group" 230 CONTACT-INFO 231 " 232 Scott Kipp 233 McDATA Corporation 234 Tel: +1 720 558-3452 235 E-mail: scott.kipp@mcdata.com 236 Postal: 4 McDATA Parkway 237 Broomfield, CO USA 80021 239 G D Ramkumar 240 McDATA Corporation 241 Tel: +1 408 567-5614 242 E-mail: gramkumar@stanfordalumni.org 243 Postal: 4555 Great American Parkway 244 Santa Clara, CA USA 95054 246 Keith McCloghrie 247 Cisco Systems, Inc. 248 Tel: +1 408 526-5260 249 E-mail: kzm@cisco.com 250 Postal: 170 West Tasman Drive 251 San Jose, CA USA 95134 252 " 254 DESCRIPTION 255 "This module defines management information specific to 256 Fibre Channel Virtual Fabrics. A Virtual Fabric is a 257 Fabric composed of partitions of switches, links and 258 N_Ports with a single Fabric management domain, Fabric 259 Services and independence from other Virtual Fabrics. 261 Copyright (C) The Internet Society (2006). This version of 262 this MIB module is part of RFC yyyy; see the RFC itself for 263 full legal notices." 264 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 265 REVISION "200604270000Z" 266 DESCRIPTION 267 "Initial version of this MIB module, published as RFCyyyy." 268 -- RFC-Editor, replace yyyy with actual RFC number & remove this note 269 ::= { mib-2 nnn } -- to be assigned by IANA 270 -- RFC Editor: replace nnn with IANA-assigned number & remove this note 272 t11vfObjects OBJECT IDENTIFIER ::= { t11FcVirtualFabricMIB 1 } 273 t11vfConformance OBJECT IDENTIFIER ::= { t11FcVirtualFabricMIB 2 } 275 --******************************** 276 -- MIB object definitions 277 -- 279 t11vfCoreSwitchTable OBJECT-TYPE 280 SYNTAX SEQUENCE OF T11vfCoreSwitchEntry 281 MAX-ACCESS not-accessible 282 STATUS current 283 DESCRIPTION 284 "A table of core switches supported by the current 285 management entity." 286 ::= { t11vfObjects 1 } 288 t11vfCoreSwitchEntry OBJECT-TYPE 289 SYNTAX T11vfCoreSwitchEntry 290 MAX-ACCESS not-accessible 291 STATUS current 292 DESCRIPTION 293 "Each entry represents one core switch." 294 INDEX { fcmInstanceIndex, t11vfCoreSwitchSwitchName } 295 ::= { t11vfCoreSwitchTable 1} 297 T11vfCoreSwitchEntry ::= 298 SEQUENCE { 299 t11vfCoreSwitchSwitchName FcNameIdOrZero, 300 t11vfCoreSwitchMaxSupported Unsigned32, 301 t11vfCoreSwitchStorageType StorageType 302 } 304 t11vfCoreSwitchSwitchName OBJECT-TYPE 305 SYNTAX FcNameIdOrZero (SIZE(8 | 16)) 306 MAX-ACCESS not-accessible 307 STATUS current 308 DESCRIPTION 309 "The Core Switch_Name (WWN) of this Core Switch. " 311 ::= { t11vfCoreSwitchEntry 1 } 313 t11vfCoreSwitchMaxSupported OBJECT-TYPE 314 SYNTAX Unsigned32 (1..4095) 315 MAX-ACCESS read-write 316 STATUS current 317 DESCRIPTION 318 " In switches that do not support Virtual Fabrics, 319 this object has the value of 1. If Virtual Fabrics 320 are supported, this object is the maximum number of 321 Virtual Fabrics supported by the Core Switch. For 322 the purpose of this count, the Control VF_ID is 323 ignored." 324 ::= { t11vfCoreSwitchEntry 2 } 326 t11vfCoreSwitchStorageType OBJECT-TYPE 327 SYNTAX StorageType 328 MAX-ACCESS read-write 329 STATUS current 330 DESCRIPTION 331 "The storage type for this conceptual row. 332 Conceptual rows having the value 'permanent' need not 333 allow write-access to any columnar objects in the row." 334 DEFVAL { nonVolatile } 335 ::= { t11vfCoreSwitchEntry 3 } 337 -- Virtual Switch table 339 t11vfVirtualSwitchTable OBJECT-TYPE 340 SYNTAX SEQUENCE OF T11vfVirtualSwitchEntry 341 MAX-ACCESS not-accessible 342 STATUS current 343 DESCRIPTION 344 "A table of Virtual Switches. When one Core Switch 345 provides switching functions for multiple Virtual Fabrics, 346 that Core Switch is modeled as containing multiple 347 Virtual Switches, one for each Virtual Fabric. This table 348 contains one row for every Virtual Switch on every Core 349 Switch. This table augments the basic switch information in 350 the fcmSwitchTable Table in the FC-MGMT-MIB." 351 REFERENCE 352 "fcmSwitchTable is defined in the FC-MGMT-MIB [RFC4044]." 353 ::= { t11vfObjects 2 } 355 t11vfVirtualSwitchEntry OBJECT-TYPE 356 SYNTAX T11vfVirtualSwitchEntry 357 MAX-ACCESS not-accessible 358 STATUS current 360 DESCRIPTION 361 "An entry of the Virtual Switch table. Each row is for a 362 Virtual Switch. 364 This table augments the fcmSwitchTable, i.e., every entry 365 in this table has a one-to-one correspondence with an 366 entry in the fcmSwitchTable. At the time when the 367 fcmSwitchTable was defined, it applied to physical 368 switches. With the definition and usage of virtual 369 switches, fcmSwitchTable now applies to virtual switches 370 which (unlike physical fabrics) are create-able via SNMP. 371 So, this entry contains a RowStatus object (to allow the 372 creation of a virtual switch), as well as a StorageType 373 object. Obviously, if a row is created/deleted in this 374 table, the corresponding row in the fcmSwitchTable will 375 be created/deleted." 376 REFERENCE 377 "fcmSwitchEntry is defined in the FC-MGMT-MIB module 378 [RFC4044]." 379 AUGMENTS { fcmSwitchEntry } 380 ::= { t11vfVirtualSwitchTable 1} 382 T11vfVirtualSwitchEntry ::= 383 SEQUENCE { 384 t11vfVirtualSwitchVfId T11FabricIndex, 385 t11vfVirtualSwitchCoreSwitchName FcNameIdOrZero, 386 t11vfVirtualSwitchRowStatus RowStatus, 387 t11vfVirtualSwitchStorageType StorageType 388 } 390 t11vfVirtualSwitchVfId OBJECT-TYPE 391 SYNTAX T11FabricIndex 392 MAX-ACCESS read-create 393 STATUS current 394 DESCRIPTION 395 "The VF_ID of the Virtual Fabric for which this virtual 396 switch performs its switching function. The Control 397 VF_ID is implicitly enabled and is not set. 398 Communication with the Control VF_ID is required. " 399 REFERENCE 400 "FC-SW-4, REV 7.5, section 12.2" 401 ::= { t11vfVirtualSwitchEntry 1 } 403 t11vfVirtualSwitchCoreSwitchName OBJECT-TYPE 404 SYNTAX FcNameIdOrZero (SIZE(8 | 16)) 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION 408 "The Core Switch_Name (WWN) of the Core Switch that 409 contains this Virtual Switch." 410 REFERENCE 411 "FC-SW-4, REV 7.5, section 12.2." 412 ::= { t11vfVirtualSwitchEntry 2 } 414 t11vfVirtualSwitchRowStatus OBJECT-TYPE 415 SYNTAX RowStatus 416 MAX-ACCESS read-create 417 STATUS current 418 DESCRIPTION 419 "The status of this row." 420 ::= { t11vfVirtualSwitchEntry 3 } 422 t11vfVirtualSwitchStorageType OBJECT-TYPE 423 SYNTAX StorageType 424 MAX-ACCESS read-create 425 STATUS current 426 DESCRIPTION 427 "The storage type for this conceptual row. 428 Conceptual rows having the value 'permanent' need not 429 allow write-access to any columnar objects in the row." 430 DEFVAL { nonVolatile } 431 ::= { t11vfVirtualSwitchEntry 4 } 433 -- Port table 435 t11vfPortTable OBJECT-TYPE 436 SYNTAX SEQUENCE OF T11vfPortEntry 437 MAX-ACCESS not-accessible 438 STATUS current 439 DESCRIPTION 440 "A table of Port attributes related to Virtual Fabrics." 441 ::= { t11vfObjects 3 } 443 t11vfPortEntry OBJECT-TYPE 444 SYNTAX T11vfPortEntry 445 MAX-ACCESS not-accessible 446 STATUS current 447 DESCRIPTION 448 "Each entry represents a physical Port on a switch. 449 Switches that support Virtual Fabrics would add 450 these four additional columns to the fcmPortEntry 451 row." 452 REFERENCE 453 "fcmPortEntry is defined in the FC-MGMT-MIB module. " 454 AUGMENTS { fcmPortEntry } 455 ::= { t11vfPortTable 1} 457 T11vfPortEntry ::= 458 SEQUENCE { 459 t11vfPortVfId T11FabricIndex, 460 t11vfPortTaggingAdminStatus INTEGER, 461 t11vfPortTaggingOperStatus INTEGER, 462 t11vfPortStorageType StorageType 463 } 465 t11vfPortVfId OBJECT-TYPE 466 SYNTAX T11FabricIndex 467 MAX-ACCESS read-write 468 STATUS current 469 DESCRIPTION 470 "The Port VF_ID assigned to this Port. The Port VF_ID is the 471 default Virtual Fabric that is assigned to untagged frames 472 arriving at this Port. The Control VF_ID is implicitly 473 enabled and is not set. Communication with the Control 474 VF_ID is required. " 475 REFERENCE 476 "FC-SW-4, REV 7.5, section 12.1" 477 DEFVAL {1} 478 ::= { t11vfPortEntry 1 } 480 t11vfPortTaggingAdminStatus OBJECT-TYPE 481 SYNTAX INTEGER { 482 off(1), 483 on(2), 484 auto(3) 485 } 486 MAX-ACCESS read-write 487 STATUS current 488 DESCRIPTION 489 "This object is used to configure the administrative status 490 of Virtual Fabric tagging on this Port. 492 SET operation Description 493 -------------- ------------------------------------------- 494 off(1) To disable Virtual Fabric tagging on this 495 Port. 497 on(2) To enable Virtual Fabric tagging on this 498 Port if the attached Port doesn't 499 prohibit it. 501 auto(3) To enable Virtual Fabric tagging if the 502 peer requests it. " 503 REFERENCE 504 " FC-SW-4, REV 7.5, section 12.4" 505 ::= { t11vfPortEntry 2 } 507 t11vfPortTaggingOperStatus OBJECT-TYPE 508 SYNTAX INTEGER { 509 off(1), 510 on(2) 511 } 512 MAX-ACCESS read-only 513 STATUS current 514 DESCRIPTION 515 "This object is used to report the operational status of 516 Virtual Fabric tagging on this Port. 518 SET operation Description 519 -------------- ------------------------------------------- 520 off(1) Virtual Fabric tagging is disabled on this 521 Port. 523 on(2) Virtual Fabric tagging is enabled on this 524 Port. " 526 REFERENCE 527 " FC-SW-4, REV 7.5, section 12.4" 528 ::= { t11vfPortEntry 3 } 530 t11vfPortStorageType OBJECT-TYPE 531 SYNTAX StorageType 532 MAX-ACCESS read-write 533 STATUS current 534 DESCRIPTION 535 "The storage type for this conceptual row, and for the 536 corresponding row in the augmented fcmPortTable. 538 Conceptual rows having the value 'permanent' need not 539 allow write-access to any columnar objects in the row." 540 DEFVAL { nonVolatile } 541 ::= { t11vfPortEntry 4 } 543 -- Locally Enabled Table 545 t11vfLocallyEnabledTable OBJECT-TYPE 546 SYNTAX SEQUENCE OF T11vfLocallyEnabledEntry 547 MAX-ACCESS not-accessible 548 STATUS current 549 DESCRIPTION 550 "A table for assigning and reporting operational status of 551 Locally-enabled Virtual Fabric IDs to Ports. The set of 552 Virtual Fabrics operational on the Port is the bit-wise 553 'AND' of the set of Locally-enabled VF_IDs of this Port 554 and the Locally-enabled VF_IDs of the attached Port." 555 ::= { t11vfObjects 4 } 557 t11vfLocallyEnabledEntry OBJECT-TYPE 558 SYNTAX T11vfLocallyEnabledEntry 559 MAX-ACCESS not-accessible 560 STATUS current 561 DESCRIPTION 562 "An entry for each Locally-enabled VF_ID on 563 each Port." 565 REFERENCE 566 " FC-SW-4, REV 7.5, section 12.4" 567 INDEX { t11vfLocallyEnabledPortIfIndex, t11vfLocallyEnabledVfId } 569 ::= { t11vfLocallyEnabledTable 1} 571 T11vfLocallyEnabledEntry ::= 572 SEQUENCE { 573 t11vfLocallyEnabledPortIfIndex InterfaceIndex, 574 t11vfLocallyEnabledVfId T11FabricIndex, 575 t11vfLocallyEnabledOperStatus INTEGER, 576 t11vfLocallyEnabledRowStatus RowStatus, 577 t11vfLocallyEnabledStorageType StorageType 578 } 580 t11vfLocallyEnabledPortIfIndex OBJECT-TYPE 581 SYNTAX InterfaceIndex 582 MAX-ACCESS not-accessible 583 STATUS current 584 DESCRIPTION 585 "The value of the ifIndex which identifies the Port." 586 ::= { t11vfLocallyEnabledEntry 1 } 588 t11vfLocallyEnabledVfId OBJECT-TYPE 589 SYNTAX T11FabricIndex 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 "A Locally-Enabled VF_ID on this Port." 594 ::= { t11vfLocallyEnabledEntry 2 } 596 t11vfLocallyEnabledOperStatus OBJECT-TYPE 597 SYNTAX INTEGER { 598 off(1), 599 on(2) 600 } 601 MAX-ACCESS read-only 602 STATUS current 603 DESCRIPTION 604 "This object is used to report the operational status of 605 Virtual Fabric tagging on this Port. 607 SET operation Description 608 -------------- ------------------------------------------- 609 off(1) Virtual Fabric tagging is disabled on this 610 Port. 612 on(2) Virtual Fabric tagging is enabled on this 613 Port. " 615 REFERENCE 616 " FC-SW-4, REV 7.3, section 12.4" 617 ::= { t11vfLocallyEnabledEntry 3 } 619 t11vfLocallyEnabledRowStatus OBJECT-TYPE 620 SYNTAX RowStatus 621 MAX-ACCESS read-create 622 STATUS current 623 DESCRIPTION 624 "The status of this conceptual row. 626 When a row in this table is in 'active(1)' state, 627 no object in that row can be modified except 628 t11vfLocallyEnabledRowStatus and 629 t11vfLocallyEnabledStorageType." 630 ::= { t11vfLocallyEnabledEntry 4 } 632 t11vfLocallyEnabledStorageType OBJECT-TYPE 633 SYNTAX StorageType 634 MAX-ACCESS read-create 635 STATUS current 636 DESCRIPTION 637 "The storage type for this conceptual row. 638 Conceptual rows having the value 'permanent' need not 639 allow write-access to any columnar objects in the row." 640 DEFVAL { nonVolatile } 641 ::= { t11vfLocallyEnabledEntry 5 } 643 --******************************** 644 -- Conformance Section 645 -- 647 t11vfMIBCompliances OBJECT IDENTIFIER ::= { t11vfConformance 1 } 648 t11vfMIBGroups OBJECT IDENTIFIER ::= { t11vfConformance 2 } 650 t11vfMIBCompliance MODULE-COMPLIANCE 651 STATUS current 652 DESCRIPTION 653 "Describes the requirements for compliance to the 654 Fibre Channel Virtual Fabric MIB." 655 MODULE -- this module 656 MANDATORY-GROUPS { t11vfGeneralGroup } 658 OBJECT t11vfCoreSwitchMaxSupported 659 MIN-ACCESS read-only 660 DESCRIPTION 661 "Write access is not required." 663 OBJECT t11vfCoreSwitchStorageType 664 MIN-ACCESS read-only 665 DESCRIPTION 666 "Write access is not required." 668 OBJECT t11vfVirtualSwitchVfId 669 MIN-ACCESS read-only 670 DESCRIPTION 671 "Write access is not required." 673 OBJECT t11vfVirtualSwitchRowStatus 674 SYNTAX RowStatus { active(1) } 675 MIN-ACCESS read-only 676 DESCRIPTION 677 "Write access is not required." 679 OBJECT t11vfVirtualSwitchStorageType 680 MIN-ACCESS read-only 681 DESCRIPTION 682 "Write access is not required." 684 OBJECT t11vfPortVfId 685 MIN-ACCESS read-only 686 DESCRIPTION 687 "Write access is not required." 689 OBJECT t11vfPortTaggingAdminStatus 690 MIN-ACCESS read-only 691 DESCRIPTION 692 "Write access is not required." 694 OBJECT t11vfPortStorageType 695 MIN-ACCESS read-only 696 DESCRIPTION 697 "Write access is not required." 699 OBJECT t11vfLocallyEnabledRowStatus 700 SYNTAX RowStatus { active(1) } 701 MIN-ACCESS read-only 702 DESCRIPTION 703 "Write access is not required." 705 OBJECT t11vfLocallyEnabledStorageType 706 MIN-ACCESS read-only 707 DESCRIPTION 708 "Write access is not required." 710 ::= { t11vfMIBCompliances 1 } 712 -- Units of conformance 714 t11vfGeneralGroup OBJECT-GROUP 715 OBJECTS { t11vfCoreSwitchMaxSupported, 716 t11vfVirtualSwitchVfId, 717 t11vfVirtualSwitchCoreSwitchName, 718 t11vfVirtualSwitchRowStatus, 719 t11vfPortVfId, 720 t11vfPortTaggingAdminStatus, 721 t11vfLocallyEnabledOperStatus, 722 t11vfPortTaggingOperStatus, 723 t11vfLocallyEnabledRowStatus, 724 t11vfCoreSwitchStorageType, 725 t11vfVirtualSwitchStorageType, 726 t11vfPortStorageType, 727 t11vfLocallyEnabledStorageType 729 } 730 STATUS current 731 DESCRIPTION 732 "A collection of objects for monitoring and 733 configuring Virtual Fabrics in a Fibre Channel switch." 734 ::= { t11vfMIBGroups 1 } 736 END 738 7. Security Considerations 740 There are a number of management objects defined in this MIB 741 module with a MAX-ACCESS clause of read-write and/or read- 742 create. Such objects may be considered sensitive or 743 vulnerable in some network environments. The support for SET 744 operations in a non-secure environment without proper 745 protection can have a negative effect on network operations. 746 These are the tables and objects and their 747 sensitivity/vulnerability: 749 t11vfCoreSwitchMaxSupported, t11vfVirtualSwitchVfId, 751 t11vfCoreSwitchStorageType, t11vfVirtualSwitchStorageType 752 and t11vfVirtualSwitchRowStatus 754 - the ability to change the configuration of Virtual 755 Fabrics on a particular switch. 757 t11vfPortTaggingAdminStatus, t11vfLocallyEnabledRowStatus, 758 t11vfPortVfId, t11vfPortStorageType and 759 t11vfLocallyEnabledStorageType 761 - the ability to change the configuration of Virtual 762 Fabrics 763 on a port of a particular switch. 765 Some of the readable objects in this MIB module (i.e., 766 objects with a MAX-ACCESS other than not-accessible) may be 767 considered sensitive or vulnerable in some network 768 environments. It is thus important to control even GET 769 and/or NOTIFY access to these objects and possibly to even 770 encrypt the values of these objects when sending them over 771 the network via SNMP. These are the tables and objects and 772 their sensitivity/vulnerability: 774 t11vfVirtualSwitchCoreSwitchName, t11vfPortTaggingOperStatus, 775 t11vfLocallyEnabledOperStatus, 777 - the ability to discover configuration of Virtual 778 Fabrics on 779 a virtual switch or a port. 781 SNMP versions prior to SNMPv3 did not include adequate 782 security. Even if the network itself is secure (for example 783 by using IPSec), even then, there is no control as to who on 784 the secure network is allowed to access and GET/SET 785 (read/change/create/delete) the objects in this MIB module. 787 It is RECOMMENDED that implementers consider the security 788 features as provided by the SNMPv3 framework (see [RFC3410], 789 section 8), including full support for the SNMPv3 790 cryptographic mechanisms (for authentication and privacy). 792 Further, deployment of SNMP versions prior to SNMPv3 is NOT 793 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and 794 to enable cryptographic security. It is then a 795 customer/operator responsibility to ensure that the SNMP 796 entity giving access to an instance of this MIB module is 797 properly configured to give access to the objects only to 798 those principals (users) that have legitimate rights to 799 indeed GET or SET (change/create/delete) them. 801 8. IANA Considerations 803 IANA is requested to make the OID assignment for the MIB 804 module under the appropriate subtree. 806 9. Acknowledgements 808 This document was developed by the INCITS Task Group T11.5. 809 We wish to acknowledge the contributions and comments from 810 the INCITS Technical Committee T11 and the IMSS WG, including 811 the following: 813 T11 Chair: Robert Snively, Brocade 814 T11 Vice Chair: Claudio Desanti, Cisco Systems 815 T11.5 Chair: Roger Cummings, Symantec 816 IMSS WG Chair: David Black 817 Bert Wijnen 819 10. Normative References 821 [RFC4044] 822 McCloghrie, K., "Fibre Channel Management MIB", RFC 4044, 823 May 2005 825 [RFC2578] 826 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 827 Rose, M. and S. Waldbusser, "Structure of Management 828 Information Version 2 (SMIv2)", RFC 2578, April 1999. 830 [RFC2579] 831 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 832 Rose, M. and S. Waldbusser, "Textual Conventions for 833 SMIv2", STD 58, RFC 2579, April 1999. 835 [RFC2580] 836 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 837 Rose, M. and S. Waldbusser, "Conformance Statements for 838 SMIv2", RFC 2580, April 1999. 840 [RFC2863] 841 McCloghrie and K., Kastenholz, F., "The Interface Group 842 MIB", RFC 2863, June 2000. 844 [FC-FAM-MIB] 845 Desanti, C., Gaonkar, V., McCloghrie, K., Gai, S., "Fibre 846 Channel Fabric Address Manager MIB", RFC 4389, March 2006. 848 [FC-FS] 849 "Fibre Channel Framing and Signaling (FC-FS)", ANSI INCITS 850 373-2003, http://www.t11.org/t11/stat.nsf/upnum/1331-d, 851 April 2003. 853 [FC-SW-4] 854 "Fibre Channel Switch Fabric 4 (FC-SW-4)", ANSI INCITS 418- 855 2006, http://www.t11.org/t11/stat.nsf/upnum/1674-d, 2006. 857 11. Informative References 859 [RFC3410] 860 Case, J., Mundy, R., Partain, D. and B. Stewart, 861 "Introduction and Applicability Statements for Internet- 862 Standard Management Framework", RFC 3410, December 2002. 864 [RFC2741] 865 Daniele, M., Wijnen, B., Ellison, M., and D. Francisco, 866 "Agent Extensibility (AgentX) Protocol Version 1", RFC 867 2741, January 2000. 869 [RFC3411] 870 Harrington, D., Presuhn, R., and B. Wijnen, "An 871 Architecture for Describing Simple Network Management 872 Protocol (SNMP) Management Frameworks", STD 58, RFC 3411, 873 December 2002. 875 12. Author's Addresses 877 Scott Kipp, 878 McDATA Corporation 879 4 McDATA Parkway 880 Broomfield, CO 80021 881 Phone: (720) 558-3452 882 Email: scott.kipp@mcdata.com 884 G D Ramkumar 885 McDATA Corporation 886 4555 Great American Parkway 887 Santa Clara, CA 95054 888 Phone: (408) 567-5614 889 Email: gramkumar@stanfordalumni.org 891 Keith McCloghrie 892 Cisco Systems 893 170 West Tasman Drive 894 San Jose, CA USA 95134 895 Phone : +1 408-526-5260 896 Email : kzm@cisco.com 898 13. Intellectual Property 900 The IETF takes no position regarding the validity or scope of 901 any Intellectual Property Rights or other rights that might 902 be claimed to pertain to the implementation or use of the 903 technology described in this document or the extent to which 904 any license under such rights might or might not be 905 available; nor does it represent that it has made any 906 independent effort to identify any such rights. Information 907 on the procedures with respect to rights in RFC documents can 908 be found in BCP 78 and BCP 79. 910 Copies of IPR disclosures made to the IETF Secretariat and 911 any assurances of licenses to be made available, or the 912 result of an attempt made to obtain a general license or 913 permission for the use of such proprietary rights by 914 implementers or users of this specification can be obtained 915 from the IETF on-line IPR repository at 916 http://www.ietf.org/ipr. 918 The IETF invites any interested party to bring to its 919 attention any copyrights, patents or patent applications, or 920 other proprietary rights that may cover technology that may 921 be required to implement this standard. Please address the 922 information to the IETF at ietf-ipr@ietf.org. 924 Full Copyright Statement 926 Copyright (C) The Internet Society 2006. 928 This document is subject to the rights, licenses and 929 restrictions contained in BCP 78, and except as set forth 930 therein, the authors retain all their rights. 932 Disclaimer of Validity 934 This document and the information contained herein are 935 provided on an "AS IS" basis and THE CONTRIBUTOR, THE 936 ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), 937 THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 938 DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 939 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 940 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES 941 OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 943 Internet-Drafts are working documents of the Internet 944 Engineering Task Force (IETF), its areas, and its working 945 groups. Note that other groups may also distribute working 946 documents as Internet-Drafts. 948 Internet-Drafts are draft documents valid for a maximum of 949 six months and may be updated, replaced, or obsoleted by 950 other documents at any time. It is inappropriate to use 951 Internet-Drafts as reference material or to cite them other 952 than as "work in progress." 954 The list of current Internet-Drafts can be accessed at 955 http://www.ietf.org/1id-abstracts.html 957 The list of Internet-Draft Shadow Directories can be accessed 958 at 959 http://www.ietf.org/shadow.html 961 Acknowledgement 963 Funding for the RFC Editor function is currently provided by 964 the Internet Society. 966 Expiration Notice 968 This Internet-Draft expires in September 2006.