idnits 2.17.1 draft-ietf-imss-fc-nsm-mib-05.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 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1618. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1629. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1636. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1642. ** The document seems to lack an RFC 3978 Section 5.4 (updated by RFC 4748) Copyright Line. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** 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 Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 282: '...erver. The SNMP agent MUST report the...' RFC 2119 keyword, line 1556: '... It is RECOMMENDED that implementors...' RFC 2119 keyword, line 1562: '... RECOMMENDED. Instead, it is RECOMM...' Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (20 December 2005) is 6702 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-FS' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-GS-3' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-GS-4' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-SW-3' -- No information found for draft-ietf-imss-fc-fam-mib-nn - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'FC-FAM-MIB' -- Obsolete informational reference (is this intentional?): RFC 2837 (Obsoleted by RFC 4044) Summary: 5 errors (**), 0 flaws (~~), 1 warning (==), 14 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft C. DeSanti 2 V. Gaonkar 3 H.K. Vivek 4 K. McCloghrie 5 S. Gai 6 Cisco Systems 7 20 December 2005 8 Fibre-Channel Name Server MIB 9 draft-ietf-imss-fc-nsm-mib-05.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that other 20 groups may also distribute working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/1id-abstracts.html 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Copyright Notice 35 Copyright(C) The Internet Society (2005). All Rights Reserved. 37 Abstract 39 This memo defines a portion of the Management Information Base (MIB) 40 for use with network management protocols in the Internet community. 41 In particular, it describes managed objects for information related 42 to the Name Server function of a Fibre Channel network. The Fibre 43 Channel Name Server provides a means for Fibre Channel ports to 44 register and discover Fibre Channel names and attributes. 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 ................................... 5 52 5 MIB Overview ................................................. 5 53 5.1 Fibre Channel management instance .......................... 5 54 5.2 Name Server Information Subset ............................. 5 55 5.3 Fabric Index ............................................... 6 56 5.4 The MIB Groups ............................................. 6 57 5.4.1 The t11NsDBGroup group ................................... 6 58 5.4.2 Three Statistics groups .................................. 7 59 5.4.3 The t11NsNotifyGroup group ............................... 7 60 5.4.4 The t11NsNotifyControlGroup group ........................ 7 61 5.5 The Actual Values of Objects ............................... 7 62 6 The T11-FC-NAME-SERVER-MIB Module ............................ 8 63 7 Acknowledgements ............................................. 33 64 8 Normative References ......................................... 33 65 9 Informative References ....................................... 34 66 10 IANA Considerations ......................................... 35 67 11 Security Considerations ..................................... 35 68 12 Authors' Addresses .......................................... 36 70 1. Introduction 72 This memo defines a portion of the Management Information Base (MIB) 73 for use with network management protocols in the Internet community. 74 In particular, it describes managed objects for information related 75 to the Fibre Channel network's Name Server function, which provides a 76 means for Fibre Channel ports to register and discover Fibre Channel 77 attributes. Such attributes include names, addresses, types, 78 features, etc. at various protocol layers. 80 2. The Internet-Standard Management Framework 82 For a detailed overview of the documents that describe the current 83 Internet-Standard Management Framework, please refer to section 7 of 84 RFC 3410 [RFC3410]. 86 Managed objects are accessed via a virtual information store, termed 87 the Management Information Base or MIB. MIB objects are generally 88 accessed through the Simple Network Management Protocol (SNMP). 89 Objects in the MIB are defined using the mechanisms defined in the 90 Structure of Management Information (SMI). This memo specifies a MIB 91 module that is compliant to the SMIv2, which is described in STD 58, 92 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 93 [RFC2580]. 95 3. Short Overview of Fibre Channel 97 The Fibre Channel (FC) is logically a bidirectional point-to-point 98 serial data channel, structured for high performance. Fibre Channel 99 provides a general transport vehicle for higher level protocols such 100 as Small Computer System Interface (SCSI) command sets, the High- 101 Performance Parallel Interface (HIPPI) data framing, IP (Internet 102 Protocol), IEEE 802.2, and others. 104 Physically, Fibre Channel is an interconnection of multiple 105 communication points, called N_Ports, interconnected either by a 106 switching network, called a Fabric, or by a point-to-point link. A 107 Fibre Channel "node" consists of one or more N_Ports. A Fabric may 108 consist of multiple Interconnect Elements, some of which are 109 switches. An N_Port connects to the Fabric via a port on a switch 110 called an F_Port. When multiple FC nodes are connected to a single 111 port on a switch via an "Arbitrated Loop" topology, the switch port 112 is called an FL_Port, and the nodes' ports are called NL_Ports. The 113 term Nx_Port is used to refer to either an N_Port or an NL_Port. The 114 term Fx_Port is used to refer to either an F_Port or an FL_Port. A 115 switch port, which is interconnected to another switch port via an 116 Inter-Switch Link (ISL), is called an E_Port. A B_Port connects a 117 bridge device with an E_Port on a switch; a B_Port provides a subset 118 of E_Port functionality. 120 Many Fibre Channel components, including the fabric, each node, and 121 most ports, have globally-unique names. These globally-unique names 122 are typically formatted as World Wide Names (WWNs). More information 123 on WWNs can be found in [FC-FS]. WWNs are expected to be persistent 124 across agent and unit resets. 126 Fibre Channel frames contain 24-bit address identifiers which 127 identify the frame's source and destination ports. Each FC port has 128 both an address identifier and a WWN. When a fabric is in use, the 129 FC address identifiers are dynamic and are assigned by a switch. 130 Each octet of a 24-bit address represents a level in an address 131 hierarchy, with a Domain_ID being the highest level of the hierarchy. 133 The Fibre Channel Name Server provides a way for N_Ports and NL_Ports 134 to register and discover Fibre Channel attributes. Such attributes 135 include names, addresses, types, features, etc. at various protocol 136 layers, including upper layer protocols specific to Fibre Channel 137 (which are sometimes called "FC-4s"). Communication with the Name 138 Server is via Fibre Channel's CT (Common Transport for Generic 139 Services) using "Information Units" (called CT_IU's) as either 140 requests, responses or unsolicited. 142 Registrations may be performed by a third party. However, the Name 143 Server may refuse such third party registration for unspecified 144 reasons. Once registered, the attributes are made available to 145 requestors. 147 Requestors could learn about new registrations via periodic polling 148 of the Name Server, but such polling would generate a considerable 149 overhead. To avoid this overhead, the Registered State Change 150 Notification (RSCN) mechanism defined in FC-FS [FC-FS] allows an 151 Nx_Port to register to receive a RSCN whenever an event occurs that 152 may affect the state of other Nx_Port(s), including changes in the 153 information registered with the Name Server. 155 The Fibre Channel Name Server is defined in the FC-GS specification, 156 The latest specification is [FC-GS-4]; the previous version was [FC- 157 GS-3]. 159 4. Relationship to Other MIBs 161 The first standardized MIB for Fibre Channel [RFC2837] was focussed 162 on Fibre Channel switches. It is being replaced by the more generic 163 Fibre Channel Management MIB [FC-MGMT] which defines basic 164 information for Fibre Channel hosts and switches, including 165 extensions to the standard IF-MIB [IF-MIB] for Fibre Channel 166 interfaces. 168 This MIB extends beyond [FC-MGMT] to cover the functionality, in 169 Fibre Channel switches, of providing Fibre Channel's Name Server 170 function. 172 This MIB also imports some common Textual Conventions from T11-TC- 173 MIB, defined in [FC-FAM-MIB]. 175 5. MIB Overview 177 This MIB module provides the means for monitoring the operation of, 178 and configuring some parameters of, one or more instances of Fibre 179 Channel Name Server functionality. (Note that there are no 180 definitions in this MIB module of "managed actions" which can be 181 invoked via SNMP.) 183 5.1. 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 195 [FC-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 5.2. Name Server Information Subset 201 In addition to allowing for multiple Fibre Channel management 202 instances, this MIB is based on the notion that the information 203 registered with the Name Server is available as one or more subsets. 204 The MIB allows the different subsets to be accessed either: 206 - via different SNMP agents/contexts, 207 - via different Fibre Channel management instances within the 208 same SNMP agent/context, and/or 209 - via the same Fibre Channel management instance within the 210 same SNMP agent/context. 212 The union of these subsets (across all agents/contexts in the 213 network) represents the total set of information registered with the 214 Name Server. Note that the intersection of the subsets is often non- 215 empty, and the use of the term "subset" does not preclude any subset 216 from containing the complete set of Name Server information. Each of 217 these subsets is identified using an index value called a Name Server 218 Information Subset Index. 220 Thus, all objects in this MIB are in tables which are INDEX-ed by at 221 least fcmInstanceIndex and t11NsInfoSubsetIndex, where the latter 222 contains a Name Server Information Subset Index value. 224 5.3. Fabric Index 226 The current standard for an interconnecting Fabric consisting of 227 multiple Fabric Switch elements is [FC-SW-3], which describes the 228 operation of a single Fabric in a physical infrastructure. It is 229 possible that future standards will define how multiple Fabrics could 230 operate within one (or more) physical infrastructures. In such a 231 scenario, each Fabric would, of course, have its own management 232 instrumentation. Therefore, to *allow* for this future possibility, 233 this MIB defines all Fabric-related information in tables which are 234 INDEX-ed by an arbitrary integer, named a "Fabric Index". In a 235 Fabric which is conformant to [FC-SW-3], the value of this Fabric 236 Index will always be 1. 238 5.4. The MIB Groups 240 This section describes the six MIB groups contained in the MIB. 242 5.4.1. The t11NsDBGroup group 244 This group contains information about the operation of the Name 245 Server function acting upon a Name Server Information Subset, 246 including an indication of whether such operation is performed local 247 to a particular Fibre Channel switch, or independently of a Fibre 248 Channel switch. It also contains the information currently 249 registered in a particular Name Server Information Subset. 251 5.4.2. Three Statistics groups 253 There are three groups of Name Server statistics objects: 255 t11NsRequestStatsGroup -- stats about requests, 256 t11NsRscnStatsGroup -- stats about (Name Server) RSCNs, 257 t11NsRejectStatsGroup -- stats about rejects, 259 Each of these groups is conditionally mandatory; specifically, each 260 group contains objects for particular statistics such that 261 implementation of the group is mandatory only for an implementation 262 which counts/captures the group's particular statistics. 264 The intent here is not to force implementations to capture these 265 statistics, but rather to have all implementations which do capture 266 them, provide access to them via the same MIB objects. 268 5.4.3. The t11NsNotifyGroup group 270 This group contains a set of notifications which provide for 271 monitoring the rejections of Name Server registration requests. 273 5.4.4. The t11NsNotifyControlGroup group 275 This group contains objects for controlling the generation of, and 276 for information to be included in, the notifications defined in the 277 t11NsNotifyGroup group. 279 5.5. The Actual Values of Objects 281 The objects defined in the t11NsRegTable represent the values 282 registered with the Name Server. The SNMP agent MUST report the 283 actual values, even if they are incorrectly formatted. This is the 284 reason why, for example, the two objects which represent IP- 285 addresses, t11NsNodeIpAddress and t11NsPortIpAddress, have the SYNTAX 286 of OCTET STRING, so that they are able to represent invalid values 287 (which could not be represented using InetAddressType and 288 InetAddress). 290 Similarly, each set of (t11NsRejectReasonCode, t11NsRejReasonCodeExp, 291 t11NsRejReasonVendorCode) objects must hold the values of the actual 292 reject, explanation and vendor-specific codes which were present in 293 the generated Reject message (the "Reject CT_IU"), irrespective of 294 whether such code values were appropriate or not. 296 6. The T11-FC-NAME-SERVER-MIB Module 298 T11-FC-NAME-SERVER-MIB DEFINITIONS ::= BEGIN 300 -- The MIB for management of the Fibre Channel functionality which 301 -- implements the Name Server function. 303 IMPORTS 304 MODULE-IDENTITY,OBJECT-TYPE, 305 NOTIFICATION-TYPE, Unsigned32, 306 Counter32, Integer32, mib-2 FROM SNMPv2-SMI -- [RFC2578] 307 MODULE-COMPLIANCE, OBJECT-GROUP, 308 NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580] 309 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 310 TruthValue, TEXTUAL-CONVENTION, 311 TimeStamp FROM SNMPv2-TC -- [RFC2579] 312 fcmInstanceIndex, FcPortType, 313 FcAddressIdOrZero, FcClasses, 314 FcNameIdOrZero FROM FC-MGMT-MIB -- [FC-MGMT] 315 T11FabricIndex FROM T11-TC-MIB -- [FC-FAM-MIB] 316 t11FamLocalSwitchWwn 317 FROM T11-FC-FABRIC-ADDR-MGR-MIB; -- [FC-FAM-MIB] 319 t11FcNameServerMIB MODULE-IDENTITY 320 LAST-UPDATED "200512200000Z" 321 ORGANIZATION "T11" 322 CONTACT-INFO 323 " Claudio DeSanti 324 Cisco Systems, Inc. 325 170 West Tasman Drive 326 San Jose, CA 95134 USA 327 Phone: +1 408 853-9172 328 EMail: cds@cisco.com 330 Keith McCloghrie 331 Cisco Systems, Inc. 332 170 West Tasman Drive 333 San Jose, CA USA 95134 334 Phone: +1 408-526-5260 335 EMail: kzm@cisco.com" 337 DESCRIPTION 338 "The MIB module for the management of the functionality, 339 which realizes the FC-GS-4 requirements for Name 340 Server(NS). 342 Copyright (C) The Internet Society (2005). This version of 343 this MIB module is part of RFC yyyy; see the RFC itself for 344 full legal notices." 345 -- RFC Editor: replace yyyy with actual RFC number & remove this note 346 REVISION "200512120000Z" 347 DESCRIPTION 348 "Initial version of this MIB module, published as RFCyyyy." 349 -- RFC-Editor, replace yyyy with actual RFC number & remove this note 350 ::= { mib-2 XXX } -- to be assigned by IANA 351 -- RFC Editor: replace XXX with IANA-assigned number & remove this note 353 t11NsNotifications OBJECT IDENTIFIER ::= { t11FcNameServerMIB 0 } 354 t11NsMIBObjects OBJECT IDENTIFIER ::= { t11FcNameServerMIB 1 } 355 t11NsMIBConformance OBJECT IDENTIFIER ::= { t11FcNameServerMIB 2 } 356 t11NsStatus OBJECT IDENTIFIER ::= { t11NsMIBObjects 1 } 357 t11NsStatistics OBJECT IDENTIFIER ::= { t11NsMIBObjects 2 } 359 -- Textual Conventions 361 T11NsGs4RejectReasonCode ::= TEXTUAL-CONVENTION 362 STATUS current 363 DESCRIPTION 364 "The FC-GS-4 reject reason code for a request. 366 none(1) 367 - no error. 368 invalidCmdCode(2) 369 - request contained an invalid command code. 370 invalidVerLevel(3) 371 - request contained an invalid version number. 372 logicalError(4) 373 - there was a logical error. 374 invalidIUSize(5) 375 - the CT_IU (Information Unit) size was invalid. 376 logicalBusy(6) 377 - the module is busy. 378 protocolError(7) 379 - there was a protocol error. 380 unableToPerformCmdReq(8) 381 - the command specified in the req could not be 382 executed. The details of exactly what failed 383 will be in the corresponding reason code 384 explanation. 385 cmdNotSupported(9) 386 - the command is not supported. 387 serverNotAvailable(10) 388 - the identified server was not available. 389 couldNotEstabSession(11) 390 - a server session (i.e., using SSE) could not be 391 established. 392 vendorError(12) 393 - a vendor-specific error." 394 REFERENCE 395 "ANSI INCITS 387-2004, Fibre Channel - Generic 396 Services-4 (FC-GS-4), section 4.4.3." 397 SYNTAX INTEGER { 398 none(1), 399 invalidCmdCode(2), 400 invalidVerLevel(3), 401 logicalError(4), 402 invalidIUSize(5), 403 logicalBusy(6), 404 protocolError(7), 405 unableToPerformCmdReq(8), 406 cmdNotSupported(9), 407 serverNotAvailable(10), 408 couldNotEstabSession(11), 409 vendorError(12) 410 } 412 T11NsRejReasonCodeExpl ::= TEXTUAL-CONVENTION 413 STATUS current 414 DESCRIPTION 415 "The reject reason code explanation: 417 noAdditionalExplanation(1) 418 - no additional explanation. 419 portIdentifierNotRegistered(2) 420 - Port Identifier not registered. 421 portNameNotRegistered(3) 422 - Port Name not registered. 423 nodeNameNotRegistered(4) 424 - Node Name not registered. 425 classOfServiceNotRegistered(5) 426 - Class of Service not registered. 428 nodeIpAddressNotRegistered(6) 429 - 'IP Address (Node)' value not registered. 430 ipaNotRegistered(7) 431 - Initial Process Associator (IPA) not registered. 432 fc4TypeNotRegistered(8) 433 - FC-4 TYPEs not registered. 434 symbolicPortNameNotRegistered(9) 435 - Symbolic Port Name not registered. 436 symbolicNodeNameNotRegistered(10) 437 - Symbolic Node Name not registered. 438 portTypeNotRegistered(11) 439 - 'Port Type' not registered. 440 portIpAddressNotRegistered(12) 441 - 'IP Address (Port)' value not registered. 442 fabricPortNameNotRegistered(13) 443 - Fabric Port Name not registered. 444 hardAddressNotRegistered(14) 445 - 'Hard Address' not registered 446 fc4DescriptorNotRegistered(15) 447 - FC-4 Descriptor not registered. 448 fc4FeaturesNotRegistered(16) 449 - FC-4 Features not registered. 450 accessDenied(17) 451 - Access denied. 452 unacceptablePortIdentifier(18) 453 - Unacceptable Port Identifier 454 databaseEmpty(19) 455 - Database is empty. 456 noObjectRegInSpecifiedScope(20) 457 - no object has been registered in the specified 458 scope. 459 domainIdNotPresent(21) 460 - Domain ID not present 461 portIdNotPresent(22) 462 - Port number not present 463 noDeviceAttached(23) 464 - No device attached. 465 authorizationException(24) 466 - Authorization Exception 467 authenticationException(25) 468 - Authentication Exception 469 databaseFull(26) 470 - Data base full." 471 REFERENCE 472 "ANSI INCITS 387-2004, Fibre Channel - Generic 473 Services-4 (FC-GS-4), sections 4.4.4 and 5.2.4" 474 SYNTAX INTEGER { 475 noAdditionalExplanation(1), 476 portIdentifierNotRegistered(2), 477 portNameNotRegistered(3), 478 nodeNameNotRegistered(4), 479 classOfServiceNotRegistered(5), 480 nodeIpAddressNotRegistered(6), 481 ipaNotRegistered(7), 482 fc4TypeNotRegistered(8), 483 symbolicPortNameNotRegistered(9), 484 symbolicNodeNameNotRegistered(10), 485 portTypeNotRegistered(11), 486 portIpAddressNotRegistered(12), 487 fabricPortNameNotRegistered(13), 488 hardAddressNotRegistered(14), 489 fc4DescriptorNotRegistered(15), 490 fc4FeaturesNotRegistered(16), 491 accessDenied(17), 492 unacceptablePortIdentifier(18), 493 databaseEmpty(19), 494 noObjectRegInSpecifiedScope(20), 495 domainIdNotPresent(21), 496 portIdNotPresent(22), 497 noDeviceAttached(23), 498 authorizationException(24), 499 authenticationException(25), 500 databaseFull(26) 501 } 503 -- 504 -- Information about a Name Server Information Subset 505 -- 507 t11NsInfoSubsetTable OBJECT-TYPE 508 SYNTAX SEQUENCE OF T11NsInfoSubsetEntry 509 MAX-ACCESS not-accessible 510 STATUS current 511 DESCRIPTION 512 "This table contains one entry for each Name Server 513 Information Subset within each Fibre Channel 514 managed instance." 515 ::= { t11NsStatus 1 } 517 t11NsInfoSubsetEntry OBJECT-TYPE 518 SYNTAX T11NsInfoSubsetEntry 519 MAX-ACCESS not-accessible 520 STATUS current 521 DESCRIPTION 522 "This entry contains information about operations 523 on a particular Name Server Information Subset 524 within the Fibre Channel management instance 525 identified by fcmInstanceIndex." 526 INDEX { fcmInstanceIndex, t11NsInfoSubsetIndex } 527 ::= { t11NsInfoSubsetTable 1 } 529 T11NsInfoSubsetEntry ::= SEQUENCE { 530 t11NsInfoSubsetIndex Unsigned32, 531 t11NsInfoSubsetSwitchIndex Unsigned32, 532 t11NsInfoSubsetTableLastChange TimeStamp, 533 t11NsInfoSubsetNumRows Integer32, 534 t11NsInfoSubsetTotalRejects Counter32, 535 t11NsInfoSubsetRejReqNotfyEnable TruthValue 536 } 538 t11NsInfoSubsetIndex OBJECT-TYPE 539 SYNTAX Unsigned32 (1..4294967295) 540 MAX-ACCESS not-accessible 541 STATUS current 542 DESCRIPTION 543 "An arbitrary integer value which uniquely identifies 544 this Name Server Information Subset amongst all others 545 within the same Fibre Channel management instance. 547 It is mandatory to keep this value constant between 548 restarts of the agent, and to make every possible 549 effort to keep it constant across such restarts." 550 ::= { t11NsInfoSubsetEntry 1 } 552 t11NsInfoSubsetSwitchIndex OBJECT-TYPE 553 SYNTAX Unsigned32 (0..4294967295) 554 MAX-ACCESS read-only 555 STATUS current 556 DESCRIPTION 557 "The value of this object is zero when operations 558 upon this Name Server Information Subset do not occur 559 at a local Fibre Channel switch; otherwise, it is 560 non-zero and identifies the local switch. 562 The switch identified by a non-zero value of this 563 object is the same switch as is identified by the 564 same value of fcmSwitchIndex." 565 REFERENCE 566 "fcmSwitchIndex is defined in the FC-MGMT-MIB module" 567 ::= { t11NsInfoSubsetEntry 2 } 569 t11NsInfoSubsetTableLastChange OBJECT-TYPE 570 SYNTAX TimeStamp 571 MAX-ACCESS read-only 572 STATUS current 573 DESCRIPTION 574 "The value of sysUpTime at the time of the last update 575 to any entry in the t11NsRegTable with the same values 576 of fcmInstanceIndex and t11NsInfoSubsetIndex. This 577 includes creation of an entry, deletion of an entry, or 578 modification of an existing entry. If no such update 579 has taken place since the last re-initialization of the 580 local network management subsystem, then this object 581 contains a zero value." 582 ::= { t11NsInfoSubsetEntry 3 } 584 t11NsInfoSubsetNumRows OBJECT-TYPE 585 SYNTAX Integer32 (0..2147483647) 586 MAX-ACCESS read-only 587 STATUS current 588 DESCRIPTION 589 "The number of Nx_Ports currently registered in this 590 Name Server Information Subset, i.e., the number of 591 rows in the t11NsRegTable with the same values of 592 fcmInstanceIndex and t11NsInfoSubsetIndex." 593 ::= { t11NsInfoSubsetEntry 4 } 595 t11NsInfoSubsetTotalRejects OBJECT-TYPE 596 SYNTAX Counter32 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION 600 "The total number of (CT_IU) Requests for Name Server 601 functions which were rejected for inclusion in this 602 Name Server Information Subset, across all Fabrics 603 for which it contains information. 605 This counter has no discontinuities other than those 606 which all Counter32's have when sysUpTime=0." 607 ::= { t11NsInfoSubsetEntry 5 } 609 t11NsInfoSubsetRejReqNotfyEnable OBJECT-TYPE 610 SYNTAX TruthValue 611 MAX-ACCESS read-write 612 STATUS current 613 DESCRIPTION 614 "This object indicates whether 't11NsRejectRegNotify' 615 notifications are generated by rejections of requests 616 to register information in this Name Server Information 617 Subset. 619 If value of this object is 'true', then the 620 notification is generated when a request is rejected. 621 If it is 'false', the notification is not generated. 623 The persistence of values of this object across an 624 agent reboot is implementation-dependent." 625 DEFVAL { false } 626 ::= { t11NsInfoSubsetEntry 6 } 628 -- 629 -- Registered Port Information 630 -- 632 t11NsRegTable OBJECT-TYPE 633 SYNTAX SEQUENCE OF T11NsRegEntry 634 MAX-ACCESS not-accessible 635 STATUS current 636 DESCRIPTION 637 "This table contains entries for all Nx_Ports registered 638 in the identified Name Server Information Subsets across 639 all Fabrics for which such Subsets contain information." 640 ::= { t11NsStatus 2 } 642 t11NsRegEntry OBJECT-TYPE 643 SYNTAX T11NsRegEntry 644 MAX-ACCESS not-accessible 645 STATUS current 646 DESCRIPTION 647 "An entry containing information about an Nx_Port 648 represented by t11NsRegPortIdentifier which is registered 649 with a Name Server Information Subset (identified by 650 t11NsInfoSubsetIndex) within the Fibre Channel management 651 instance (identified by fcmInstanceIndex) on the Fabric 652 (identified by t11NsRegFabricIndex)." 653 INDEX { fcmInstanceIndex, t11NsInfoSubsetIndex, 654 t11NsRegFabricIndex, t11NsRegPortIdentifier } 655 ::= { t11NsRegTable 1 } 657 T11NsRegEntry ::= SEQUENCE { 658 t11NsRegFabricIndex T11FabricIndex, 659 t11NsRegPortIdentifier FcAddressIdOrZero, 660 t11NsRegPortName FcNameIdOrZero, 661 t11NsRegNodeName FcNameIdOrZero, 662 t11NsRegClassOfSvc FcClasses, 663 t11NsRegNodeIpAddress OCTET STRING, 664 t11NsRegProcAssoc OCTET STRING, 665 t11NsRegFc4Type OCTET STRING, 666 t11NsRegPortType FcPortType, 667 t11NsRegPortIpAddress OCTET STRING, 668 t11NsRegFabricPortName FcNameIdOrZero, 669 t11NsRegHardAddress FcAddressIdOrZero, 670 t11NsRegSymbolicPortName SnmpAdminString, 671 t11NsRegSymbolicNodeName SnmpAdminString, 672 t11NsRegFc4Features OCTET STRING 673 } 675 t11NsRegFabricIndex OBJECT-TYPE 676 SYNTAX T11FabricIndex 677 MAX-ACCESS not-accessible 678 STATUS current 679 DESCRIPTION 680 "A unique index value which uniquely identifies a 681 particular Fabric. 683 In a Fabric conformant to SW-3, only a single Fabric can 684 operate within a single physical infrastructure, and thus, 685 the value of this Fabric Index will always be 1. 687 However, it is possible that future standards will define 688 how multiple Fabrics, each with its own management 689 instrumentation, could operate within one (or more) physical 690 infrastructures. To allow for this future possibility, this 691 index value is used to uniquely identify a particular 692 Fabric within a physical infrastructure." 693 ::= { t11NsRegEntry 1 } 695 t11NsRegPortIdentifier OBJECT-TYPE 696 SYNTAX FcAddressIdOrZero 697 MAX-ACCESS not-accessible 698 STATUS current 699 DESCRIPTION 700 "The Fibre Channel Address Identifier of this Nx_Port. 701 If no Port Identifier has been registered, then the 702 value of this object is the zero-length string." 703 ::= { t11NsRegEntry 2 } 705 t11NsRegPortName OBJECT-TYPE 706 SYNTAX FcNameIdOrZero 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "The Port_Name (WWN) of this Nx_Port. 711 If this object has not been registered, then its value 712 is the zero-length string." 713 DEFVAL {''H} 714 ::= { t11NsRegEntry 3 } 716 t11NsRegNodeName OBJECT-TYPE 717 SYNTAX FcNameIdOrZero 718 MAX-ACCESS read-only 719 STATUS current 720 DESCRIPTION 721 "The Node_Name (WWN) of this Nx_Port. 722 If this object has not been registered, then its value 723 is the zero-length string." 724 DEFVAL {''H} 725 ::= { t11NsRegEntry 4 } 727 t11NsRegClassOfSvc OBJECT-TYPE 728 SYNTAX FcClasses 729 MAX-ACCESS read-only 730 STATUS current 731 DESCRIPTION 732 "The class of service indicator. This object is a 733 array of bits that contain a bit map of the classes of 734 service supported by the associated port. If a bit in 735 this object is 1, it indicates that the class of 736 service is supported by the associated port. When a 737 bit is set to 0, it indicates that no class of service 738 is supported by this Nx_Port. 740 If this object has not been not registered for a port, 741 then the instance for that port is not instantiated." 742 ::= { t11NsRegEntry 5 } 744 t11NsRegNodeIpAddress OBJECT-TYPE 745 SYNTAX OCTET STRING (SIZE (0 | 16)) 746 MAX-ACCESS read-only 747 STATUS current 748 DESCRIPTION 749 "The IP address of the node of this Nx_Port, in 750 network-byte order, either as a 32-bit IPv4 address or 751 a 128-bit IPv6 address. For the former, the leftmost 96 bits 752 (12 bytes) should contain x'00 00 00 00 00 00 00 00 00 00 FF 753 FF', and the IPv4 address should be present in the rightmost 754 32 bits. 756 Note that the value of this object is the IP address value 757 that is received in the FC-GS-4 message Register IP address 758 (Node) RIP_NN. It is not validated against any IP address 759 format. 761 If no 'IP address (Node)' has been registered, then the 762 value of this object is the zero-length string." 763 REFERENCE 764 "ANSI INCITS 387-2004, Fibre Channel - Generic 765 Services-4 (FC-GS-4)" 766 DEFVAL { ''H } 767 ::= { t11NsRegEntry 6 } 769 t11NsRegProcAssoc OBJECT-TYPE 770 SYNTAX OCTET STRING (SIZE (0 | 8)) 771 MAX-ACCESS read-only 772 STATUS current 773 DESCRIPTION 774 "The Fibre Channel Initial Process Associator (IPA). 776 If no 'Initial Process Associator' has been registered, 777 then the value of this object is the zero-length string." 778 REFERENCE 779 "ANSI INCITS 387-2004, Fibre Channel - Generic 780 Services-4 (FC-GS-4)" 781 DEFVAL { ''H } 782 ::= { t11NsRegEntry 7 } 784 t11NsRegFc4Type OBJECT-TYPE 785 SYNTAX OCTET STRING (SIZE (0 | 32)) 786 MAX-ACCESS read-only 787 STATUS current 788 DESCRIPTION 789 "The FC-4 protocol types supported by this Nx_Port. 790 This is an array of 256-bits. Each bit in the array 791 corresponds to a Type value as defined by Fibre Channel 792 standards and contained in the Type field of the frame 793 header. The order of the bits in the 256-bit (32-byte) 794 value is the same as defined in FC-GS-4, section 5.2.3.8 795 and represented in network-byte order. 797 If no 'FC-4 TYPEs' has been registered, then the 798 value of this object is the zero-length string." 799 REFERENCE 800 "ANSI INCITS 387-2004, Fibre Channel - Generic 801 Services-4 (FC-GS-4), section 5.2.3.8." 802 DEFVAL { ''H } 803 ::= { t11NsRegEntry 8 } 805 t11NsRegPortType OBJECT-TYPE 806 SYNTAX FcPortType 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "The port type of this port. 812 If no 'Port Type' has been registered, then the value 813 of this object is unidentified, and represented by 814 the value: 'unknown'." 815 DEFVAL { 1 } -- 'unknown', see [FC-MGMT] 816 ::= { t11NsRegEntry 9 } 818 t11NsRegPortIpAddress OBJECT-TYPE 819 SYNTAX OCTET STRING (SIZE (0 | 16)) 820 MAX-ACCESS read-only 821 STATUS current 822 DESCRIPTION 823 "The value which Fibre Channel calls an 'IP Address (Port)' 824 which represents the IP address of the associated port. 825 The value is either in 32-bit IPv4 format or 128-bit IPv6 826 format, in network-byte order. When this object contains a 827 IPv4 address, the leftmost 96 bits (12 bytes) should contain 828 x'00 00 00 00 00 00 00 00 00 00 FF FF'. The IPv4 address 829 should be present in the rightmost 32 bits. 831 Note that the value of this object is the IP address value 832 that is received in the FC-GS-4 message Register IP address 833 (Port) RIPP_ID. It is not validated against any IP address 834 format. 836 If no 'IP address (Port)' has been registered, then the 837 value of this object is the zero-length string." 838 REFERENCE 839 "ANSI INCITS 387-2004, Fibre Channel - Generic 840 Services-4, (FC-GS-4)" 841 DEFVAL {''H} 842 ::= { t11NsRegEntry 10 } 844 t11NsRegFabricPortName OBJECT-TYPE 845 SYNTAX FcNameIdOrZero 846 MAX-ACCESS read-only 847 STATUS current 848 DESCRIPTION 849 "The Fabric Port Name (WWN) of the Fx_Port to which 850 this Nx_Port is attached. 852 If no 'Fabric Port Name' has been registered, then the 853 value of this object is the zero-length string." 854 DEFVAL {''H} 855 ::= { t11NsRegEntry 11 } 857 t11NsRegHardAddress OBJECT-TYPE 858 SYNTAX FcAddressIdOrZero 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION 862 "The format of this object is identical to the format 863 of Hard Address defined in the Discover Address (ADISC) 864 Extended Link Service (FC-FS). 865 Hard Address is the 24-bit NL_Port identifier which 866 consists of 867 - the 8-bit Domain_ID in the most significant byte 868 - the 8-bit Area Id in the next most significant 869 byte 870 - the 8-bit AL-PA(Arbitrated Loop Physical Address) 871 which an NL_Port attempts acquire during FC-AL 872 initialization in the least significant byte. 874 If the port is not an NL_Port, or if it is an NL_Port 875 but does not have a hard address, then all bits are 876 reported as zeros. 878 If no 'Hard Address' has been registered, then the 879 value of this object is the zero-length string." 880 DEFVAL {''H} 881 ::= { t11NsRegEntry 12 } 883 t11NsRegSymbolicPortName OBJECT-TYPE 884 SYNTAX SnmpAdminString (SIZE (0..255)) 885 MAX-ACCESS read-only 886 STATUS current 887 DESCRIPTION 888 "The user-defined name of this port. 890 If no 'Symbolic Port Name' has been registered, then 891 the value of this object is the zero length string." 892 DEFVAL {''H} 893 ::= { t11NsRegEntry 13 } 895 t11NsRegSymbolicNodeName OBJECT-TYPE 896 SYNTAX SnmpAdminString (SIZE (0..255)) 897 MAX-ACCESS read-only 898 STATUS current 899 DESCRIPTION 900 "The user-defined name of the node of this port. 902 If no 'Symbolic Node Name' has been registered, then 903 the value of this object is the zero length string." 904 DEFVAL {''H} 905 ::= { t11NsRegEntry 14 } 907 t11NsRegFc4Features OBJECT-TYPE 908 SYNTAX OCTET STRING (SIZE (0 | 128)) 909 MAX-ACCESS read-only 910 STATUS current 911 DESCRIPTION 912 "The FC-4 Features associated with FC-4 Types on this 913 port encoded as a 128-byte value in network-byte order, 914 or, the zero-length string if no 'FC-4 Features' have been 915 registered. 917 Section 5.2.3.15 of the FC-GS-4 is the authoritative 918 definition of the format of the 128-byte value, 919 i.e., if different, FC-GS-4 takes precedence over the 920 following description: 922 The 128-byte value is an array of 4-bit values, one for 923 each FC-4 TYPE value, positioned as follows: the 5 most 924 significant bits of a TYPE value identify where it appears 925 within the 128-byte value, specifically, within which word: 926 - Word 0 (of the 128-byte value) contains information 927 related to TYPEs '00' through '07'; 928 - Word 1 contains information related to TYPEs 929 '08' through 0F'; 930 - and so forth ... up to Word 31 that contains 931 information related to TYPEs 'F8' through 'FF'. 932 The least significant of the eight 4-bit values in each 933 Word represents an FC-4 Type with 000 as its 3 least 934 significant bits, and most significant 4-bit value in 935 each Word represents an FC-4 Type with 111 as its 3 least 936 significant bits." 937 REFERENCE 938 "ANSI INCITS 387-2004, Fibre Channel - Generic 939 Services-4 (FC-GS-4), section 5.2.3.15." 940 DEFVAL {''H} 941 ::= { t11NsRegEntry 15 } 943 -- 944 -- Registered FC-4 Descriptors 945 -- 947 t11NsRegFc4DescriptorTable OBJECT-TYPE 948 SYNTAX SEQUENCE OF T11NsRegFc4DescriptorEntry 949 MAX-ACCESS not-accessible 950 STATUS current 951 DESCRIPTION 952 "This table contains entries for all FC-4 Descriptors 953 registered in the identified Name Server Information 954 Subsets across all Fabrics for which such Subsets 955 contain information." 956 ::= { t11NsStatus 3 } 958 t11NsRegFc4DescriptorEntry OBJECT-TYPE 959 SYNTAX T11NsRegFc4DescriptorEntry 960 MAX-ACCESS not-accessible 961 STATUS current 962 DESCRIPTION 963 "An entry in the t11NsRegFc4DescriptorTable, 964 containing information about a FC-4 Descriptor 965 which is associated with a particular FC-4 Type 966 value. The particular FC-4 Descriptor was 967 registered by an Nx_Port (identified by 968 t11NsRegPortIdentifier) in a Name Server Information 969 Subset (identified by t11NsInfoSubsetIndex) within 970 the Fibre Channel management instance (identified by 971 fcmInstanceIndex) on the Fabric (identified by 972 t11NsRegFabricIndex). 974 If no FC-4 Descriptors have been registered 975 for a particular port, then there will be no 976 entries in this table for that port." 977 INDEX { fcmInstanceIndex, t11NsInfoSubsetIndex, 978 t11NsRegFabricIndex, t11NsRegPortIdentifier, 979 t11NsRegFc4TypeValue } 980 ::= { t11NsRegFc4DescriptorTable 1 } 982 T11NsRegFc4DescriptorEntry ::= SEQUENCE { 983 t11NsRegFc4TypeValue Unsigned32, 984 t11NsRegFc4Descriptor OCTET STRING 985 } 987 t11NsRegFc4TypeValue OBJECT-TYPE 988 SYNTAX Unsigned32 (0..255) 989 MAX-ACCESS not-accessible 990 STATUS current 991 DESCRIPTION 992 "An integer value which identifies an FC-4 TYPE value 993 (representing a particular protocol type, as specified 994 in FC-FS) for which an FC-4 Descriptor has been 995 registered. 997 An instance of this object contains a 'Type value' 998 which corresponds to a '1' bit in the value of the 999 t11NsRegFc4Type registered for the same port; 1000 this correspondence is as specified in FC-GS-4." 1001 REFERENCE 1002 "ANSI INCITS 387-2004, Fibre Channel - Generic 1003 Services-4 (FC-GS-4), section 5.2.3.8, and 1004 ANSI INCITS 373-2003, Fibre Channel - Framing and 1005 Signaling (FC-FS), section 9.6, Table 29." 1006 ::= { t11NsRegFc4DescriptorEntry 1 } 1008 t11NsRegFc4Descriptor OBJECT-TYPE 1009 SYNTAX OCTET STRING (SIZE (0..255)) 1010 MAX-ACCESS read-only 1011 STATUS current 1012 DESCRIPTION 1013 "The FC-4 Descriptor value which has been registered 1014 for the particular port on the particular fabric, and 1015 for the FC-4 Type represented by the corresponding 1016 value of t11NsRegFc4TypeIndex. 1018 The format of an FC-4 Descriptor is dependent on the 1019 corresponding FC-4 Type value, but is represented in 1020 network-byte order." 1021 REFERENCE 1022 "ANSI INCITS 387-2004, Fibre Channel - Generic 1023 Services-4 (FC-GS-4), section 5.2.5.42" 1024 ::= { t11NsRegFc4DescriptorEntry 2 } 1026 -- 1027 -- Name Server per-Fabric Statistics 1028 -- 1030 t11NsStatsTable OBJECT-TYPE 1031 SYNTAX SEQUENCE OF T11NsStatsEntry 1032 MAX-ACCESS not-accessible 1033 STATUS current 1034 DESCRIPTION 1035 "This table contains per-Fabric state and statistics 1036 for operations upon the identified Name Server 1037 Information Subsets." 1038 ::= { t11NsStatistics 1 } 1040 t11NsStatsEntry OBJECT-TYPE 1041 SYNTAX T11NsStatsEntry 1042 MAX-ACCESS not-accessible 1043 STATUS current 1044 DESCRIPTION 1045 "An entry in this table contains state and statistics 1046 for operations upon a Name Server Information Subset 1047 (identified by t11NsInfoSubsetIndex) within the Fibre 1048 Channel management instance (identified by 1049 fcmInstanceIndex) on the Fabric (identified by 1050 t11NsRegFabricIndex)." 1051 INDEX { fcmInstanceIndex, t11NsInfoSubsetIndex, 1052 t11NsRegFabricIndex } 1053 ::= { t11NsStatsTable 1 } 1055 T11NsStatsEntry ::= SEQUENCE { 1056 t11NsInGetReqs Counter32, 1057 t11NsOutGetReqs Counter32, 1058 t11NsInRegReqs Counter32, 1059 t11NsInDeRegReqs Counter32, 1060 t11NsInRscns Counter32, 1061 t11NsOutRscns Counter32, 1062 t11NsRejects Counter32, 1063 t11NsDatabaseFull TruthValue 1064 } 1066 t11NsInGetReqs OBJECT-TYPE 1067 SYNTAX Counter32 1068 MAX-ACCESS read-only 1069 STATUS current 1070 DESCRIPTION 1071 "The total number of (CT_IU) Get Requests 1072 received requesting information from this Name 1073 Server Information Subset on this Fabric. 1075 This counter has no discontinuities other than those 1076 which all Counter32's have when sysUpTime=0." 1077 ::= { t11NsStatsEntry 1 } 1079 t11NsOutGetReqs OBJECT-TYPE 1080 SYNTAX Counter32 1081 MAX-ACCESS read-only 1082 STATUS current 1083 DESCRIPTION 1084 "The total number of (CT_IU) Get Requests sent in 1085 order to obtain information needed in this Name Server 1086 Information Subset on this Fabric. 1088 This counter has no discontinuities other than those 1089 which all Counter32's have when sysUpTime=0." 1090 ::= { t11NsStatsEntry 2 } 1092 t11NsInRegReqs OBJECT-TYPE 1093 SYNTAX Counter32 1094 MAX-ACCESS read-only 1095 STATUS current 1096 DESCRIPTION 1097 "The total number of (CT_IU) Registration Requests 1098 received to register information in the Name Server 1099 Information Subset on this Fabric. 1101 This counter has no discontinuities other than those 1102 which all Counter32's have when sysUpTime=0." 1103 ::= { t11NsStatsEntry 3 } 1105 t11NsInDeRegReqs OBJECT-TYPE 1106 SYNTAX Counter32 1107 MAX-ACCESS read-only 1108 STATUS current 1109 DESCRIPTION 1110 "The total number of (CT_IU) De-registration Requests 1111 received to de-register information from this Name Server 1112 Information Subset on this Fabric. 1114 This counter has no discontinuities other than those 1115 which all Counter32's have when sysUpTime=0." 1116 ::= { t11NsStatsEntry 4 } 1118 t11NsInRscns OBJECT-TYPE 1119 SYNTAX Counter32 1120 MAX-ACCESS read-only 1121 STATUS current 1122 DESCRIPTION 1123 "The total number of received RSCNs, indicating 1124 Name Server-related changes relating to this Name 1125 Server Information Subset on this Fabric. 1127 This counter has no discontinuities other than those 1128 which all Counter32's have when sysUpTime=0." 1129 ::= { t11NsStatsEntry 5 } 1131 t11NsOutRscns OBJECT-TYPE 1132 SYNTAX Counter32 1133 MAX-ACCESS read-only 1134 STATUS current 1135 DESCRIPTION 1136 "The total number of transmitted RSCNs, indicating 1137 Name Server-related changes relating to this Name 1138 Server Information Subset on this Fabric. 1140 This counter has no discontinuities other than those 1141 which all Counter32's have when sysUpTime=0." 1142 ::= { t11NsStatsEntry 6 } 1144 t11NsRejects OBJECT-TYPE 1145 SYNTAX Counter32 1146 MAX-ACCESS read-only 1147 STATUS current 1148 DESCRIPTION 1149 "The total number of CT_IU Requests for Name 1150 Server functions on this Name Server Information 1151 Subset on this Fabric, which were rejected. 1153 This counter has no discontinuities other than those 1154 which all Counter32's have when sysUpTime=0." 1155 ::= { t11NsStatsEntry 7 } 1157 t11NsDatabaseFull OBJECT-TYPE 1158 SYNTAX TruthValue 1159 MAX-ACCESS read-only 1160 STATUS current 1161 DESCRIPTION 1162 "An indication of whether the database containing this 1163 Name Server Information Subset is full. This object is 1164 set to 'true' only if the Name Server is unable to allocate 1165 space for a new entry for the corresponding Fabric, and set 1166 to 'false' whenever an existing entry is deleted for the 1167 corresponding Fabric." 1168 ::= { t11NsStatsEntry 8 } 1170 -- 1171 -- Reject information objects 1172 -- 1174 t11NsRejectTable OBJECT-TYPE 1175 SYNTAX SEQUENCE OF T11NsRejectEntry 1176 MAX-ACCESS not-accessible 1177 STATUS current 1178 DESCRIPTION 1179 "This table contains information about the most recent 1180 Name Server Registration request failures for various 1181 ports on various fabrics. 1183 If no information is available about the most recent 1184 rejection of a registration request on a particular port 1185 on a particular fabric, then there will no entry in this 1186 table for that port and fabric. 1188 When a t11NsRejectRegNotify notification is sent for 1189 such a registration request failure, the values of the 1190 objects in the relevant entry of this table are updated 1191 immediately prior to generating the notification." 1192 ::= { t11NsStatus 4 } 1194 t11NsRejectEntry OBJECT-TYPE 1195 SYNTAX T11NsRejectEntry 1196 MAX-ACCESS not-accessible 1197 STATUS current 1198 DESCRIPTION 1199 "An entry containing information about the most recent 1200 rejection of a request to register information in the Name 1201 Server Information Subset (identified by 1202 t11NsInfoSubsetIndex) within the Fibre Channel management 1203 instance (identified by fcmInstanceIndex) for a particular 1204 port (identified by t11NsRegPortIdentifier) on a particular 1205 fabric (identified by t11NsRegFabricIndex)." 1206 INDEX { fcmInstanceIndex, t11NsInfoSubsetIndex, 1207 t11NsRegFabricIndex, t11NsRegPortIdentifier } 1208 ::= { t11NsRejectTable 1 } 1210 T11NsRejectEntry ::= SEQUENCE { 1211 t11NsRejectCtCommandString OCTET STRING, 1212 t11NsRejectReasonCode T11NsGs4RejectReasonCode, 1213 t11NsRejReasonCodeExp T11NsRejReasonCodeExpl, 1214 t11NsRejReasonVendorCode OCTET STRING 1215 } 1217 t11NsRejectCtCommandString OBJECT-TYPE 1218 SYNTAX OCTET STRING (SIZE (0..255)) 1219 MAX-ACCESS read-only 1220 STATUS current 1221 DESCRIPTION 1222 "The binary content of the Registration Request, 1223 formatted as an octet string (in network byte 1224 order) containing the CT_IU, as described in 1225 Table 2 of [FC-GS-4] (including the preamble), 1226 which was most recently rejected for the particular 1227 Name Server Information Subset on the particular port 1228 on the particular fabric. 1230 This object contains the zero-length string 1231 if and when the CT-IU's content is unavailable. 1233 When the length of this object is 255 octets, it 1234 contains the first 255 octets of the CT-IU (in 1235 network-byte order)." 1237 ::= { t11NsRejectEntry 1 } 1239 t11NsRejectReasonCode OBJECT-TYPE 1240 SYNTAX T11NsGs4RejectReasonCode 1241 MAX-ACCESS read-only 1242 STATUS current 1243 DESCRIPTION 1244 "A registration reject reason code. This object 1245 contains the reason code of the most recent Name 1246 Server Registration request failure for the 1247 particular port on the particular fabric." 1248 ::= { t11NsRejectEntry 2 } 1250 t11NsRejReasonCodeExp OBJECT-TYPE 1251 SYNTAX T11NsRejReasonCodeExpl 1252 MAX-ACCESS read-only 1253 STATUS current 1254 DESCRIPTION 1255 "A registration reject reason code explanation. This 1256 object contains the reason code explanation of the most 1257 recent Name Server Registration request failure for the 1258 particular port on the particular fabric." 1259 ::= { t11NsRejectEntry 3 } 1261 t11NsRejReasonVendorCode OBJECT-TYPE 1262 SYNTAX OCTET STRING (SIZE(1)) 1263 MAX-ACCESS read-only 1264 STATUS current 1265 DESCRIPTION 1266 "A registration reject vendor-specific code. This 1267 object contains the vendor-specific code of the most 1268 recent Name Server Registration request failure for the 1269 particular port on the particular fabric." 1270 ::= { t11NsRejectEntry 4 } 1272 -- 1273 -- Notifications 1274 -- 1276 t11NsRejectRegNotify NOTIFICATION-TYPE 1277 OBJECTS { t11FamLocalSwitchWwn, 1278 t11NsRegPortName, t11NsRejectCtCommandString, 1279 t11NsRejectReasonCode, t11NsRejReasonCodeExp, 1280 t11NsRejReasonVendorCode } 1282 STATUS current 1283 DESCRIPTION 1284 "This notification is generated whenever a request to 1285 register information in a Name Server Information 1286 Subset (for which the corresponding instance of 1287 t11NsInfoSubsetRejReqNotfyEnable is 'true') is 1288 rejected on a particular fabric for a particular Nx_Port. 1290 The value of t11FamLocalSwitchWwn indicates the 1291 WWN of the switch which received the request. 1292 (If the WWN is unavailable, the value is set to 1293 the zero-length string.) 1295 The value of t11NsRejectCtCommandString indicates 1296 the rejected request, and the values of 1297 t11NsRejectReasonCode, t11NsRejReasonCodeExp and 1298 t11NsRejReasonVendorCode indicate the reason for 1299 the rejection. 1301 The value of t11NsRegPortName represents the Port Name 1302 if it is able to be extracted out of the registration 1303 request, or otherwise the value as currently registered 1304 on the port." 1305 ::= { t11NsNotifications 1 } 1307 -- 1308 -- Conformance 1309 -- 1311 t11NsMIBCompliances OBJECT IDENTIFIER ::= {t11NsMIBConformance 1} 1312 t11NsMIBGroups OBJECT IDENTIFIER ::= {t11NsMIBConformance 2} 1314 t11NsMIBCompliance MODULE-COMPLIANCE 1315 STATUS current 1316 DESCRIPTION 1317 "The compliance statement for entities which 1318 implement the Fibre Channel Name Server." 1319 MODULE MANDATORY-GROUPS {t11NsDBGroup, 1320 t11NsNotifyControlGroup, 1321 t11NsNotifyGroup} 1323 OBJECT t11NsInfoSubsetRejReqNotfyEnable 1324 MIN-ACCESS read-only 1325 DESCRIPTION 1326 "Write access is not required." 1328 GROUP t11NsRequestStatsGroup 1329 DESCRIPTION 1330 "This group is mandatory only for an implementation 1331 which captures statistics related to Name Server 1332 requests." 1334 GROUP t11NsRscnStatsGroup 1335 DESCRIPTION 1336 "This group is mandatory only for an implementation 1337 which captures statistics related to Name 1338 Server-related RSCNs." 1340 GROUP t11NsRejectStatsGroup 1341 DESCRIPTION 1342 "This group is mandatory only for an implementation 1343 which captures statistics related to Name Server 1344 rejects." 1346 ::= { t11NsMIBCompliances 1 } 1348 -- Units of conformance 1350 t11NsDBGroup OBJECT-GROUP 1351 OBJECTS { t11NsInfoSubsetSwitchIndex, 1352 t11NsInfoSubsetTableLastChange, 1353 t11NsInfoSubsetNumRows, 1354 t11NsRegPortName, 1355 t11NsRegNodeName, 1356 t11NsRegClassOfSvc, 1357 t11NsRegNodeIpAddress, 1358 t11NsRegProcAssoc, 1359 t11NsRegFc4Type, 1360 t11NsRegPortType, 1361 t11NsRegPortIpAddress, 1362 t11NsRegFabricPortName, 1363 t11NsRegHardAddress, 1364 t11NsRegSymbolicPortName, 1365 t11NsRegSymbolicNodeName, 1366 t11NsRegFc4Features, 1367 t11NsRegFc4Descriptor } 1368 STATUS current 1369 DESCRIPTION 1370 "A collection of objects for monitoring the information 1371 registered in a Name Server Information Subset." 1372 ::= { t11NsMIBGroups 1 } 1374 t11NsRequestStatsGroup OBJECT-GROUP 1375 OBJECTS { t11NsInGetReqs, 1376 t11NsOutGetReqs, 1377 t11NsInRegReqs, 1378 t11NsInDeRegReqs, 1379 t11NsDatabaseFull} 1380 STATUS current 1381 DESCRIPTION 1382 "A collection of objects for displaying Name 1383 Server statistics and state for Name Server requests." 1384 ::= { t11NsMIBGroups 2 } 1386 t11NsRscnStatsGroup OBJECT-GROUP 1387 OBJECTS { t11NsInRscns, 1388 t11NsOutRscns } 1389 STATUS current 1390 DESCRIPTION 1391 "A collection of objects for displaying Name 1392 Server statistics for Name Server-related RSCNs." 1393 ::= { t11NsMIBGroups 3 } 1395 t11NsRejectStatsGroup OBJECT-GROUP 1396 OBJECTS { t11NsInfoSubsetTotalRejects, 1397 t11NsRejects } 1398 STATUS current 1399 DESCRIPTION 1400 "A collection of objects for displaying Name 1401 Server statistics for rejects." 1402 ::= { t11NsMIBGroups 4 } 1404 t11NsNotifyControlGroup OBJECT-GROUP 1405 OBJECTS { t11NsRejectCtCommandString, 1406 t11NsRejectReasonCode, 1407 t11NsRejReasonCodeExp, 1408 t11NsRejReasonVendorCode, 1409 t11NsInfoSubsetRejReqNotfyEnable } 1410 STATUS current 1411 DESCRIPTION 1412 "A collection of notification control and 1413 notification information objects for monitoring 1414 rejections of Name Server registrations." 1415 ::= { t11NsMIBGroups 5 } 1417 t11NsNotifyGroup NOTIFICATION-GROUP 1418 NOTIFICATIONS {t11NsRejectRegNotify } 1419 STATUS current 1420 DESCRIPTION 1421 "A collection of notifications for monitoring 1422 rejections of Name Server registrations." 1423 ::= { t11NsMIBGroups 6 } 1425 END 1427 7. Acknowledgements 1429 This document began life as a work item of the INCITS Task Group 1430 T11.5. We wish to acknowledge the many contributions and comments 1431 from the INCITS Technical Committee T11, including the following: 1433 T11 Chair: Robert Snively, Brocade 1434 T11 Vice Chair: Claudio Desanti, Cisco Systems 1435 T11.5 Chair: Roger Cummings, Symantec 1436 T11.5 members, especially: 1437 Ken Hirata, Emulex 1438 Scott Kipp, McData 1439 Michael O'Donnell, McData 1440 Elizabeth G. Rodriguez, Dot Hill 1441 Steven L. Wilson, Brocade 1442 Bob Nixon, Emulex 1444 Thanks also to Orly Nicklass of RAD Data Communications, Bert 1445 Wijnen of Lucent, and those members of the IMSS WG who provided 1446 review comments. 1448 8. Normative References 1450 [RFC2578] 1451 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1452 and S. Waldbusser, "Structure of Management Information Version 2 1453 (SMIv2)", STD 58, RFC 2578, April 1999. 1455 [RFC2579] 1456 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1457 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 1458 2579, April 1999. 1460 [RFC2580] 1461 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1462 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 1463 2580, April 1999. 1465 [RFC3411] 1466 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1467 Describing Simple Network Management Protocol (SNMP) Management 1468 Frameworks", STD 58, RFC 3411, December 2002. 1470 [FC-FS] 1471 "Fibre Channel - Framing and Signaling (FC-FS)" ANSI INCITS 1472 373-2003, April 2003. 1474 [FC-GS-3] 1475 "Fibre Channel - Generic Services - 3 (FC-GS-3)", ANSI INCITS 1476 348-2000, November 2000. 1478 [FC-GS-4] 1479 "Fibre Channel - Generic Services - 4 (FC-GS-4)", ANSI INCITS 1480 387-2004, T11/Project 1505-D/Rev 7.91 Febrauary 2004. 1482 [FC-SW-3] 1483 "Fibre Channel - Switch Fabric - 3 (FC-SW-3)", ANSI INCITS 1484 384-2004, June 2004. 1486 [FC-MGMT] 1487 K. McCloghrie, "Fibre Channel Management MIB", RFC 4044, May 2005. 1489 [FC-FAM-MIB] 1490 DeSanti, C., Gaonkar, V., McCloghrie, K., and S. Gai, "Fibre- 1491 Channel Fabric Address Manager MIB", Internet-Draft (draft-ietf- 1492 imss-fc-fam-mib-nn.txt), work-in-progress. 1494 9. Informative References 1496 [RFC2741] 1497 Daniele, M., Wijnen, B., Ellison, M., and D. Francisco, "Agent 1498 Extensibility (AgentX) Protocol Version 1", RFC 2741, January 2000. 1500 [RFC2837] 1501 Teow, K., "Definitions of Managed Objects for the Fabric Element in 1502 Fibre Channel Standard", RFC 2837, May 2000. 1504 [RFC3410] 1505 Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and 1506 Applicability Statements for Internet- Standard Management 1507 Framework", RFC 3410, December 2002. 1509 [IF-MIB] 1510 McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB", RFC 1511 2863, June 2000. 1513 10. IANA Considerations 1515 IANA is requested to make a MIB OID assignment to the T11-FC-NAME- 1516 SERVER-MIB module under the appropriate subtree. 1518 11. Security Considerations 1520 There is one management object defined in this MIB module with a MAX- 1521 ACCESS clause of read-write and/or read-create. Such objects may be 1522 considered sensitive or vulnerable in some network environments. The 1523 support for SET operations in a non-secure environment without proper 1524 protection can have a negative effect on network operations. This 1525 object and its sensitivity/vulnerability is: 1527 t11NsInfoSubsetRejReqNotfyEnable -- the ability to enable/disable 1528 notifications. 1530 Such objects may be considered sensitive or vulnerable in some 1531 network environments. For example, the ability to change network 1532 topology or network speed may afford an attacker the ability to 1533 obtain better performance at the expense of other network users. The 1534 support for SET operations in a non-secure environment without proper 1535 protection can have a negative effect on network operations. 1537 Some of the readable objects in this MIB module (i.e., objects with a 1538 MAX-ACCESS other than not-accessible) may be considered sensitive or 1539 vulnerable in some network environments. It is thus important to 1540 control even GET and/or NOTIFY access to these objects and possibly 1541 to even encrypt the values of these objects when sending them over 1542 the network via SNMP. These are the tables and objects and their 1543 sensitivity/vulnerability: 1545 t11NsRegTable -- contains information about registered Nx_Ports. 1547 t11NsStatsTable -- contains statistics and state information about 1548 the Name Server. 1550 SNMP versions prior to SNMPv3 did not include adequate security. 1551 Even if the network itself is secure (for example by using IPSec), 1552 even then, there is no control as to who on the secure network is 1553 allowed to access and GET/SET (read/change/create/delete) the objects 1554 in this MIB module. 1556 It is RECOMMENDED that implementors consider the security features as 1557 provided by the SNMPv3 framework (see [RFC3410], section 8), 1558 including full support for the SNMPv3 cryptographic mechanisms (for 1559 authentication and privacy). 1561 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1562 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1563 enable cryptographic security. It is then a customer/operator 1564 responsibility to ensure that the SNMP entity giving access to an 1565 instance of this MIB module is properly configured to give access to 1566 the objects only to those principals (users) that have legitimate 1567 rights to indeed GET or SET (change/create/delete) them. 1569 12. Authors' Addresses 1571 Claudio DeSanti 1572 Cisco Systems, Inc. 1573 170 West Tasman Drive 1574 San Jose, CA 95134 USA 1575 Phone: +1 408 853-9172 1576 EMail: cds@cisco.com 1578 Vinay Gaonkar 1579 Cisco Systems, Inc. 1580 170 West Tasman Drive 1581 San Jose, CA 95134 USA 1582 Phone: +1 408 527-8576 1583 EMail: vgaonkar@cisco.com 1585 H.K. Vivek 1586 Cisco Systems, Inc. 1587 71 Millers Rd 1588 Bangalore, India 1589 Phone: +91 80 2289933x5117 1590 EMail: hvivek@cisco.com 1592 Keith McCloghrie 1593 Cisco Systems, Inc. 1594 170 West Tasman Drive 1595 San Jose, CA USA 95134 1596 Phone: +1 408-526-5260 1597 Email: kzm@cisco.com 1599 Silvano Gai 1600 Cisco Systems, Inc. 1601 170 West Tasman Drive 1602 San Jose, CA USA 95134 1603 Phone: +1 408-526-7269 1604 Email: sgai@cisco.com 1606 Full Copyright Statement 1608 Copyright (C) The Internet Society (2005). This document is subject 1609 to the rights, licenses and restrictions contained in BCP 78, and 1610 except as set forth therein, the authors retain all their rights. 1612 This document and the information contained herein are provided on an 1613 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1614 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1615 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1616 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1617 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1618 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1620 Disclaimer of validity 1622 The IETF takes no position regarding the validity or scope of any 1623 Intellectual Property Rights or other rights that might be claimed to 1624 pertain to the implementation or use of the technology described in 1625 this document or the extent to which any license under such rights 1626 might or might not be available; nor does it represent that it has 1627 made any independent effort to identify any such rights. Information 1628 on the procedures with respect to rights in RFC documents can be 1629 found in BCP 78 and BCP 79. 1631 Copies of IPR disclosures made to the IETF Secretariat and any 1632 assurances of licenses to be made available, or the result of an 1633 attempt made to obtain a general license or permission for the use of 1634 such proprietary rights by implementers or users of this 1635 specification can be obtained from the IETF on-line IPR repository at 1636 http://www.ietf.org/ipr. 1638 The IETF invites any interested party to bring to its attention any 1639 copyrights, patents or patent applications, or other proprietary 1640 rights that may cover technology that may be required to implement 1641 this standard. Please address the information to the IETF at 1642 ietf-ipr@ietf.org. 1644 Acknowledgment 1646 Funding for the RFC Editor function is currently provided by the 1647 Internet Society.