idnits 2.17.1 draft-desanti-fc-name-server-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 3667, Section 5.1 on line 16. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 36), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 36. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** The document seems to lack an RFC 3978 Section 5.5 (updated by RFC 4748) Disclaimer -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack an RFC 3979 Section 5, para. 1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ( - It does however have an RFC 2026 Section 10.4(A) Disclaimer.) ** The document seems to lack an RFC 3979 Section 5, para. 2 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 3 IPR Disclosure Invitation -- however, there's a paragraph with a matching beginning. Boilerplate error? ( - It does however have an RFC 2026 Section 10.4(B) IPR Disclosure Invitation.) ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == 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 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.) ** 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 248: '...erver. The SNMP agent MUST report the...' RFC 2119 keyword, line 1384: '...It is RECOMMENDED that implementors co...' RFC 2119 keyword, line 1389: '...ns prior to SNMPv3 is NOT RECOMMENDED....' RFC 2119 keyword, line 1390: '...Instead, it is RECOMMENDED to deploy S...' 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 (17 July 2004) is 7222 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2741' is mentioned on line 180, but not defined -- 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-ips-fcmgmt-mib-nn - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'FC-MGMT' -- No information found for draft-desanti-fc-fabric-addr-mgr-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: 13 errors (**), 0 flaws (~~), 3 warnings (==), 12 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 17 July 2004 8 Fibre-Channel Name Server MIB 9 draft-desanti-fc-name-server-02.txt 11 Status of this Memo 13 By submitting this Internet-Draft, I certify that any applicable 14 patent or other IPR claims of which I am aware have been disclosed, 15 and any of which I become aware will be disclosed, in accordance with 16 RFC 3668. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet- Drafts as reference 26 material or to cite them other than as "work in progress". 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 Copyright Notice 36 Copyright (C) The Internet Society (2004). All Rights Reserved. 38 Abstract 40 This memo defines a portion of the Management Information Base (MIB) 41 for use with network management protocols in the Internet community. 42 In particular, it describes managed objects for information related 43 to the Fibre Channel network's Name Server function. At present, 44 this memo is a work item of T11.5 (http://www.t11.org). The plan is 45 that it will later become a work item of IETF's IMSS working group. 47 Table of Contents 49 1 Introduction ................................................. 3 50 2 The Internet-Standard Management Framework ................... 3 51 3 Short Overview of Fibre Channel .............................. 3 52 4 Relationship to Other MIBs ................................... 4 53 5 MIB Overview ................................................. 5 54 5.1 Fibre Channel management instance .......................... 5 55 5.2 Name Server Index .......................................... 5 56 5.3 Fabric Index ............................................... 6 57 5.4 The MIB Groups ............................................. 6 58 5.4.1 The t11NsDBGroup group ................................... 6 59 5.4.2 The t11NsStatsGroup group ................................ 6 60 5.4.3 The t11NsNotifyControlGroup group ........................ 6 61 5.4.4 The t11NsNotifyGroup group ............................... 6 62 5.5 The Actual Values of Objects ............................... 6 63 6 The T11-FC-NAME-SERVER-MIB Module ............................ 7 64 7 Intellectual Property ........................................ 29 65 8 Acknowledgements ............................................. 30 66 9 Normative References ......................................... 30 67 10 Informative References ...................................... 31 68 11 Security Considerations ..................................... 31 69 12 Authors' Addresses .......................................... 33 70 13 Full Copyright Statement .................................... 34 72 1. Introduction 74 This memo defines a portion of the Management Information Base (MIB) 75 for use with network management protocols in the Internet community. 76 In particular, it describes managed objects for information related 77 to the Fibre Channel network's Name Server function. 79 2. The Internet-Standard Management Framework 81 For a detailed overview of the documents that describe the current 82 Internet-Standard Management Framework, please refer to section 7 of 83 RFC 3410 [RFC3410]. 85 Managed objects are accessed via a virtual information store, termed 86 the Management Information Base or MIB. MIB objects are generally 87 accessed through the Simple Network Management Protocol (SNMP). 88 Objects in the MIB are defined using the mechanisms defined in the 89 Structure of Management Information (SMI). This memo specifies a MIB 90 module that is compliant to the SMIv2, which is described in STD 58, 91 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 92 [RFC2580]. 94 3. Short Overview of Fibre Channel 96 The Fibre Channel (FC) is logically a bidirectional point-to-point 97 serial data channel, structured for high performance. Fibre Channel 98 provides a general transport vehicle for higher level protocols such 99 as Small Computer System Interface (SCSI) command sets, the High- 100 Performance Parallel Interface (HIPPI) data framing, IP (Internet 101 Protocol), IEEE 802.2, and others. 103 Physically, Fibre Channel is an interconnection of multiple 104 communication points, called N_Ports, interconnected either by a 105 switching network, called a Fabric, or by a point-to-point link. A 106 Fibre Channel "node" consists of one or more N_Ports. A Fabric may 107 consist of multiple Interconnect Elements, some of which are 108 switches. An N_Port connects to the Fabric via a port on a switch 109 called an F_Port. When multiple FC nodes are connected to a single 110 port on a switch via an "Arbitrated Loop" topology, the switch port 111 is called an FL_Port, and the nodes' ports are called NL_Ports. The 112 term Nx_Port is used to refer to either an N_Port or an NL_Port. The 113 term Fx_Port is used to refer to either an F_Port or an FL_Port. A 114 switch port, which is interconnected to another switch port via an 115 Inter-Switch Link (ISL), is called an E_Port. A B_Port connects a 116 bridge device with an E_Port on a switch; a B_Port provides a subset 117 of E_Port functionality. 119 Many Fibre Channel components, including the fabric, each node, and 120 most ports, have globally-unique names. These globally-unique names 121 are typically formatted as World Wide Names (WWNs). More information 122 on WWNs can be found in [FC-FS]. WWNs are expected to be persistent 123 across agent and unit resets. 125 Fibre Channel frames contain 24-bit address identifiers which 126 identify the frame's source and destination ports. Each FC port has 127 both an address identifier and a WWN. When a fabric is in use, the 128 FC address identifiers are dynamic and are assigned by a switch. 129 Each octet of a 24-bit address represents a level in an address 130 hierarchy, with a Domain_ID being the highest level of the hierarchy. 132 The Fibre Channel Name Server provides a way for N_Ports and NL_Ports 133 to register and discover Fibre Channel attributes. Such attributes 134 include names, addresses, types, features, etc. at various protocol 135 layers, including upper layer protocols specific to Fibre Channel 136 (which are sometimes called "FC-4s"). Communication with the Name 137 Server is via Fibre Channel's CT (Common Transport for Generic 138 Services) using "Information Units" (called CT_IU's) as either 139 requests, responses or unsolicited. 141 Registrations may be performed by a third party. However, the Name 142 Server may refuse such third party registration for unspecified 143 reasons . Once registered, the attributes are made available to 144 requestors. 146 The Fibre Channel Name Server is defined in the FC-GS specification, 147 The latest specification is [FC-GS-4]; the previous version was [FC- 148 GS-3]. 150 4. Relationship to Other MIBs 152 The first standardized MIB for Fibre Channel [RFC2837] was focussed 153 on Fibre Channel switches. It is being replaced by the more generic 154 Fibre Channel Management MIB [FC-MGMT] which defines basic 155 information for Fibre Channel hosts and switches, including 156 extensions to the standard IF-MIB for Fibre Channel interfaces. 158 This MIB extends beyond [FC-MGMT] to cover the functionality, in 159 Fibre Channel switches, of providing Fibre Channel's Name Server 160 function. 162 This MIB also imports some common Textual Conventions from T11-TC- 163 MIB, defined in [FC-FAM-MIB]. 165 5. MIB Overview 167 This MIB module provides the means for monitoring the operation of, 168 and configuring some parameters of, one or more instances of Fibre 169 Channel Name Server functionality. (Note that there are no 170 definitions in this MIB module of "managed actions" which can be 171 invoked via SNMP.) 173 5.1. Fibre Channel management instance 175 A Fibre Channel management instance is defined in [FC-MGMT] as a 176 separable managed instance of Fibre Channel functionality. Fibre 177 Channel functionality may be grouped into Fibre Channel management 178 instances in whatever way is most convenient for the 179 implementation(s). For example, one such grouping accommodates a 180 single SNMP agent having multiple AgentX [RFC2741] sub-agents, with 181 each sub-agent implementing a different Fibre Channel management 182 instance. 184 The object, fcmInstanceIndex, is IMPORTed from the FC-MGMT-MIB 185 [FC-MGMT] as the index value to uniquely identify each Fibre Channel 186 management instance within the same SNMP context ([RFC3411] section 187 3.3.1). 189 5.2. Name Server Index 191 As well as allowing for multiple Fibre Channel management instances, 192 this MIB also allows for multiple instances of the Name Server 193 functionality within each Fibre Channel management instance. 194 Further, some of the Name Server instances managed by the same Fibre 195 Channel management instance, can operate local to a particular Fibre 196 Channel switch and some can operate independent of any particular 197 switch. 199 Therefore, all objects in this MIB are in tables which are INDEX-ed 200 by at least fcmInstanceIndex and t11NsIndex, where the latter is an 201 index value which uniquely identifies a Name Server instance within a 202 Fibre Channel management instance. 204 5.3. Fabric Index 206 The current standard for an interconnecting Fabric consisting of 207 multiple Fabric Switch elements is [FC-SW-3], which describes the 208 operation of a single Fabric in a physical infrastructure. It is 209 possible that future standards will define how multiple Fabrics could 210 operate within one (or more) physical infrastructures. In such a 211 scenario, each Fabric would, of course, have its own management 212 instrumentation. Therefore, to *allow* for this future possibility, 213 this MIB defines all Fabric-related information in tables which are 214 INDEX-ed by an arbitrary integer, named a "Fabric Index". In a 215 Fabric which is conformant to [FC-SW-3], the value of this Fabric 216 Index will always be 1. 218 5.4. The MIB Groups 220 This section describes the four MIB groups contained in the MIB. 222 5.4.1. The t11NsDBGroup group 224 This group contains information about the operation of the Name 225 Server function, including an indication of whether each Name Server 226 instance operates local to a particular Fibre Channel switch, or 227 independently of any Fibre Channel switch. It also contains the 228 information currently registered with the Name Server. 230 5.4.2. The t11NsStatsGroup group 232 This group contains Name Server statistics. 234 5.4.3. The t11NsNotifyControlGroup group 236 This group contains those notification control and notification 237 information objects which are required for monitoring Name Server 238 registrations/de-registrations. 240 5.4.4. The t11NsNotifyGroup group 242 This group contains notifications which provide for the monitoring of 243 Name Server registrations/de-registrations. 245 5.5. The Actual Values of Objects 247 The objects defined in the t11NsRegTable represent the values 248 registered with the Name Server. The SNMP agent MUST report the 249 actual values, even if they are incorrectly formatted. This is the 250 reason why, for example, the two objects which represent IP- 251 addresses, t11NsNodeIpAddress and t11NsPortIpAddress, have the SYNTAX 252 of OCTET STRING, so that they are able to represent invalid values 253 (which could not be represented using InetAddressType and 254 InetAddress). 256 Similarly, each pair of t11NsRejectReasonCode and 257 t11NsRejReasonCodeExp objects holds the values of the actual reject 258 code and explanation which was present in the generated Reject 259 message (the "Reject CT_IU"), irrespective of whether such a reject 260 code and explanation were appropriate or not. 262 6. The T11-FC-NAME-SERVER-MIB Module 264 T11-FC-NAME-SERVER-MIB DEFINITIONS ::= BEGIN 266 -- The MIB for management of the Fibre Channel functionality which 267 -- implements the Name Server function. 269 IMPORTS 270 MODULE-IDENTITY,OBJECT-TYPE, NOTIFICATION-TYPE, Unsigned32, 271 Counter32,Integer32 FROM SNMPv2-SMI -- [RFC2578] 272 MODULE-COMPLIANCE, OBJECT-GROUP, 273 NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580] 274 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 275 TruthValue, TEXTUAL-CONVENTION, 276 TimeStamp FROM SNMPv2-TC -- [RFC2579] 277 fcmInstanceIndex, FcPortType, FcAddressIdOrZero, FcClasses, 278 FcNameIdOrZero FROM FC-MGMT-MIB -- [FC-MGMT] 279 FabricIndex FROM T11-TC-MIB; -- [FC-FAM-MIB] 281 t11NameServerMIB MODULE-IDENTITY 282 LAST-UPDATED "200407170000Z" 283 ORGANIZATION "T11" 284 CONTACT-INFO 285 " Claudio DeSanti 286 Cisco Systems, Inc. 287 170 West Tasman Drive 288 San Jose, CA 95134 USA 289 Phone: +1 408 853-9172 290 EMail: cds@cisco.com 291 Keith McCloghrie 292 Cisco Systems, Inc. 293 170 West Tasman Drive 294 San Jose, CA USA 95134 295 Phone: +1 408-526-5260 296 EMail: kzm@cisco.com" 297 DESCRIPTION 298 "The MIB module for the management of the functionality, 299 which realizes the FC-GS-4 requirements for Name 300 Server(NS)." 301 REVISION "200407170000Z" 302 DESCRIPTION 303 "Initial version of this MIB module." 304 ::= { tbd } 306 t11NsMIBObjects OBJECT IDENTIFIER ::= { t11NameServerMIB 1 } 307 t11NsMIBConformance OBJECT IDENTIFIER ::= { t11NameServerMIB 2 } 308 t11NsStatus OBJECT IDENTIFIER ::= { t11NsMIBObjects 1 } 309 t11NsStatistics OBJECT IDENTIFIER ::= { t11NsMIBObjects 2 } 310 t11NsNotifications OBJECT IDENTIFIER ::= { t11NsMIBObjects 0 } 312 -- Textual Conventions 314 T11NsGs4RejectReasonCode ::= TEXTUAL-CONVENTION 315 STATUS current 316 DESCRIPTION 317 "The FC-GS-4 reject reason code for a request. 319 none(1) - no error. 320 invalidCmdCode(2) - request contained an invalid 321 command code. 322 invalidVerLevel(3) - request containeds an invalid 323 version number. 324 logicalError(4) - there was a logical error. 325 invalidIUSize(5) - the CT_IU (Information Unit) size 326 was invalid. 327 logicalBusy(6) - the module is busy. 328 protocolError(7) - there was a protocol error. 329 unableToPerformCmdReq(8) - the command specified 330 in the req could not be 331 executed. The details 332 of exactly what failed 333 will be in the 334 corresponding reason 335 code explanation. 336 cmdNotSupported(9) - the command is not 337 supported. 338 serverNotAvailable(10) - the identified server was 339 not available. 340 couldNotEstabSession(11) - a server session (i.e., 341 using SSE) could not be 342 established. 343 vendorError(12) - vendor-specific error." 344 REFERENCE 345 "ANSI INCITS 387-2004, Fibre Channel - Generic 346 Services-4 (FC-GS-4), section 4.4.3." 347 SYNTAX INTEGER { 348 none(1), 349 invalidCmdCode(2), 350 invalidVerLevel(3), 351 logicalError(4), 352 invalidIUSize(5), 353 logicalBusy(6), 354 protocolError(7), 355 unableToPerformCmdReq(8), 356 cmdNotSupported(9), 357 serverNotAvailable(10), 358 couldNotEstabSession(11), 359 vendorError(12) 360 } 362 T11NsRejReasonCodeExpl ::= TEXTUAL-CONVENTION 363 STATUS current 364 DESCRIPTION 365 "The reject reason code explanation: 367 noAdditionalExplanation(1) - no additional 368 explanation. 369 portIdentifierNotRegistered(2) - Port Identifier not 370 registered. 371 portNameNotRegistered(3) - Port Name not registered. 372 nodeNameNotRegistered(4) - Node Name not registered. 373 classOfServiceNotRegistered(5) - Class of Service 374 not registered. 375 nodeIpAddressNotRegistered(6) - 'IP Address (Node)' 376 value not registered. 377 ipaNotRegistered(7) - Initial Process Associator (IPA) 378 not registered. 379 fc4TypeNotRegistered(8) - FC-4 TYPEs not registered. 381 symbolicPortNameNotRegistered(9) - Symbolic Port Name 382 not registered. 383 symbolicNodeNameNotRegistered(10) - Symbolic Node Name 384 not registered. 385 portTypeNotRegistered(11) - 'Port Type' not registered. 386 portIpAddressNotRegistered(12) - 'IP Address (Port)' 387 value not registered. 388 fabricPortNameNotRegistered(13) - Fabric Port Name not 389 registered. 390 hardAddressNotRegistered(14) - 'Hard Address' not 391 registered 392 fc4DescriptorNotRegistered(15) - FC-4 Descriptor not 393 registered. 394 fc4FeaturesNotRegistered(16) - FC-4 Features not 395 registered. 396 accessDenied(17) - Access denied. 397 unacceptablePortIdentifier(18) - Unacceptable 398 Port Identifier 399 databaseEmpty(19) - Database is empty. 400 noObjectRegInSpecifiedScope(20) - no object has been 401 registered in the 402 specified scope. 403 domainIdNotPresent(21) - Domain ID not present 404 portIdNotPresent(22) - Port number not present 405 noDeviceAttached(23) - No device attached. 406 authorizationException(24) - Authorization Exception 407 authenticationException(25) - Authentication Exception 408 databaseFull(26) - Data base full." 409 REFERENCE 410 "ANSI INCITS 387-2004, Fibre Channel - Generic 411 Services-4 (FC-GS-4), sections 4.4.4 and 5.2.4" 412 SYNTAX INTEGER { 413 noAdditionalExplanation(1), 414 portIdentifierNotRegistered(2), 415 portNameNotRegistered(3), 416 nodeNameNotRegistered(4), 417 classOfServiceNotRegistered(5), 418 nodeIpAddressNotRegistered(6), 419 ipaNotRegistered(7), 420 fc4TypeNotRegistered(8), 421 symbolicPortNameNotRegistered(9), 422 symbolicNodeNameNotRegistered(10), 423 portTypeNotRegistered(11), 424 portIpAddressNotRegistered(12), 425 fabricPortNameNotRegistered(13), 426 hardAddressNotRegistered(14), 427 fc4DescriptorNotRegistered(15), 428 fc4FeaturesNotRegistered(16), 429 accessDenied(17), 430 unacceptablePortIdentifier(18), 431 databaseEmpty(19), 432 noObjectRegInSpecifiedScope(20), 433 domainIdNotPresent(21), 434 portIdNotPresent(22), 435 noDeviceAttached(23), 436 authorizationException(24), 437 authenticationException(25), 438 databaseFull(26) 439 } 441 -- 442 -- Information about a Name Server instance 443 -- 445 t11NsTable OBJECT-TYPE 446 SYNTAX SEQUENCE OF T11NsEntry 447 MAX-ACCESS not-accessible 448 STATUS current 449 DESCRIPTION 450 "This table contains one entry for each instance of 451 Name Server functionality within each Fibre Channel 452 managed instance." 453 ::= { t11NsStatus 1 } 455 t11NsEntry OBJECT-TYPE 456 SYNTAX T11NsEntry 457 MAX-ACCESS not-accessible 458 STATUS current 459 DESCRIPTION 460 "An entry in the t11NsTable. This contains information 461 about one Name Server instance within the Fibre Channel 462 management instance identified by fcmInstanceIndex." 463 INDEX { fcmInstanceIndex, t11NsIndex } 464 ::= { t11NsTable 1 } 466 T11NsEntry ::= SEQUENCE { 467 t11NsIndex Unsigned32, 468 t11NsSwitchIndex Unsigned32, 469 t11NsTableLastChange TimeStamp, 470 t11NsNumRows Integer32, 471 t11NsTotalRejects Counter32, 472 t11NsRejReqNotifyEnable TruthValue 473 } 475 t11NsIndex OBJECT-TYPE 476 SYNTAX Unsigned32 (1..4294967295) 477 MAX-ACCESS not-accessible 478 STATUS current 479 DESCRIPTION 480 "An arbitrary integer value which uniquely identifies 481 this Name Server instance amongst all others within the 482 same Fibre Channel management instance. 484 It is mandatory to keep this value constant between 485 restarts of the agent, and to make every possible 486 effort to keep it constant across restarts." 487 ::= { t11NsEntry 1 } 489 t11NsSwitchIndex OBJECT-TYPE 490 SYNTAX Unsigned32 (0..4294967295) 491 MAX-ACCESS read-only 492 STATUS current 493 DESCRIPTION 494 "The value of this object is zero when this Name 495 Server instance does not operate local to a Fibre 496 Channel switch; otherwise, it is non-zero and 497 identifies the local switch. 499 The switch identified by a non-zero value of this 500 object is the same switch as is identified by the 501 same value of fcmSwitchIndex." 502 REFERENCE 503 "fcmSwitchIndex is defined in the FC-MGMT-MIB module" 504 ::= { t11NsEntry 2 } 506 t11NsTableLastChange OBJECT-TYPE 507 SYNTAX TimeStamp 508 MAX-ACCESS read-only 509 STATUS current 510 DESCRIPTION 511 "The value of sysUpTime at the time of the last update 512 to any entry in the t11NsRegTable with the same values 513 of fcmInstanceIndex and t11NsIndex. This includes 514 creation of an entry, deletion of an entry, or 515 modification of an existing entry. If no such update 516 has taken place since the last re-initialization of the 517 local network management subsystem, then this object 518 contains a zero value." 519 ::= { t11NsEntry 3 } 521 t11NsNumRows OBJECT-TYPE 522 SYNTAX Integer32 (0..2147483647) 523 MAX-ACCESS read-only 524 STATUS current 525 DESCRIPTION 526 "The number of Nx_Ports currently registered with 527 this Name Server instance, i.e., the number of rows 528 in the t11NsRegTable with the same values of 529 fcmInstanceIndex and t11NsIndex." 530 ::= { t11NsEntry 4 } 532 t11NsTotalRejects OBJECT-TYPE 533 SYNTAX Counter32 534 MAX-ACCESS read-only 535 STATUS current 536 DESCRIPTION 537 "The total number of (CT_IU) Requests for Name Server 538 functions which were rejected by this Name Server 539 instance, across all Fabrics it serves." 540 ::= { t11NsEntry 5 } 542 t11NsRejReqNotifyEnable OBJECT-TYPE 543 SYNTAX TruthValue 544 MAX-ACCESS read-write 545 STATUS current 546 DESCRIPTION 547 "This object indicates whether this Name Server 548 instance generates 't11NsRejectRegNotify' 549 notifications. 551 If value of this object is 'true', then the 552 notification is generated when a request is rejected. 553 If it is 'false', the notification is not generated." 554 DEFVAL { false } 555 ::= { t11NsEntry 6 } 557 -- 558 -- Registered Port Information 559 -- 560 t11NsRegTable OBJECT-TYPE 561 SYNTAX SEQUENCE OF T11NsRegEntry 562 MAX-ACCESS not-accessible 563 STATUS current 564 DESCRIPTION 565 "This table contains entries for all Nx_Ports registered 566 with all Name Server instances on all Fabrics on which 567 they operate." 568 ::= { t11NsStatus 2 } 570 t11NsRegEntry OBJECT-TYPE 571 SYNTAX T11NsRegEntry 572 MAX-ACCESS not-accessible 573 STATUS current 574 DESCRIPTION 575 "An entry in the t11NsRegTable, containing information 576 about an Nx_Port represented by t11NsRegPortIdentifier 577 which is registered with a Name Server instance 578 (identified by t11NsIndex) within the Fibre Channel 579 management instance (identified by fcmInstanceIndex) 580 on the Fabric (identified by t11NsRegFabricIndex)." 581 INDEX { fcmInstanceIndex, t11NsIndex, 582 t11NsRegFabricIndex, t11NsRegPortIdentifier } 583 ::= { t11NsRegTable 1 } 585 T11NsRegEntry ::= SEQUENCE { 586 t11NsRegFabricIndex FabricIndex, 587 t11NsRegPortIdentifier FcAddressIdOrZero, 588 t11NsRegPortName FcNameIdOrZero, 589 t11NsRegNodeName FcNameIdOrZero, 590 t11NsRegClassOfSvc FcClasses, 591 t11NsRegNodeIpAddress OCTET STRING, 592 t11NsRegProcAssoc OCTET STRING, 593 t11NsRegFc4Type OCTET STRING, 594 t11NsRegPortType FcPortType, 595 t11NsRegPortIpAddress OCTET STRING, 596 t11NsRegFabricPortName FcNameIdOrZero, 597 t11NsRegHardAddress FcAddressIdOrZero, 598 t11NsRegSymbolicPortName SnmpAdminString, 599 t11NsRegSymbolicNodeName SnmpAdminString, 600 t11NsRegFc4Features OCTET STRING 601 } 603 t11NsRegFabricIndex OBJECT-TYPE 604 SYNTAX FabricIndex 605 MAX-ACCESS not-accessible 606 STATUS current 607 DESCRIPTION 608 "A unique index value which uniquely identifies a 609 particular Fabric. 611 In a Fabric conformant to SW-3, only a single Fabric can 612 operate within a single physical infrastructure, and thus, 613 the value of this Fabric Index will always be 1. 615 However, it is possible that future standards will define 616 how multiple Fabrics, each with its own management 617 instrumentation, could operate within one (or more) physical 618 infrastructures. To allow for this future possibility, this 619 index value is used to uniquely identify a particular 620 Fabric within a physical infrastructure." 621 ::= { t11NsRegEntry 1 } 623 t11NsRegPortIdentifier OBJECT-TYPE 624 SYNTAX FcAddressIdOrZero 625 MAX-ACCESS not-accessible 626 STATUS current 627 DESCRIPTION 628 "The Fibre Channel Address Identifier of this Nx_Port. 629 If no Port Identifier has been registered, then the 630 value of this object is the zero-length string." 631 ::= { t11NsRegEntry 2 } 633 t11NsRegPortName OBJECT-TYPE 634 SYNTAX FcNameIdOrZero 635 MAX-ACCESS read-only 636 STATUS current 637 DESCRIPTION 638 "The Port_Name (WWN) of this Nx_Port. 639 If this object has not been registered, then its value 640 is the zero-length string." 641 DEFVAL {''H} 642 ::= { t11NsRegEntry 3 } 644 t11NsRegNodeName OBJECT-TYPE 645 SYNTAX FcNameIdOrZero 646 MAX-ACCESS read-only 647 STATUS current 648 DESCRIPTION 649 "The Node_Name (WWN) of this Nx_Port. 651 If this object has not been registered, then its value 652 is the zero-length string." 653 DEFVAL {''H} 654 ::= { t11NsRegEntry 4 } 656 t11NsRegClassOfSvc OBJECT-TYPE 657 SYNTAX FcClasses 658 MAX-ACCESS read-only 659 STATUS current 660 DESCRIPTION 661 "The class of service indicator. This object is a 662 array of bits that contain a bit map of the classes of 663 service supported by the associated port. If a bit in 664 this object is 1, it indicates that the class of 665 service is supported by the associated port. When a 666 bit is set to 0, it indicates that no class of service 667 is supported by this Nx_Port. 669 If this object has not been not registered for a port, 670 then that the instance for that port is not instantiated." 671 ::= { t11NsRegEntry 5 } 673 t11NsRegNodeIpAddress OBJECT-TYPE 674 SYNTAX OCTET STRING (SIZE (0 | 16)) 675 MAX-ACCESS read-only 676 STATUS current 677 DESCRIPTION 678 "The IP address of the node of this Nx_Port, either as a 679 32-bit IPv4 address or a 128-bit IPv6 address. For the 680 former, the leftmost 96 bits (12 bytes) should contain 681 x'00 00 00 00 00 00 00 00 00 00 FF FF', and the IPv4 682 address should be present in the rightmost 32 bits. 684 Note that the value of this object is the IP address value 685 that is received in the FC-GS-4 message Register IP address 686 (Node) RIP_NN. It is not validated against any IP address 687 format. 689 If no 'IP address (Node)' has been registered, then the 690 value of this object is the zero-length string." 691 REFERENCE 692 "ANSI INCITS 387-2004, Fibre Channel - Generic 693 Services-3 (FC-GS-4)" 694 DEFVAL { ''H } 695 ::= { t11NsRegEntry 6 } 697 t11NsRegProcAssoc OBJECT-TYPE 698 SYNTAX OCTET STRING (SIZE (0 | 8)) 699 MAX-ACCESS read-only 700 STATUS current 701 DESCRIPTION 702 "The Fibre Channel Initial Process Associator (IPA). 704 If no 'Initial Process Associator' has been registered, 705 then the value of this object is the zero-length string." 706 REFERENCE 707 "ANSI INCITS 387-2004, Fibre Channel - Generic 708 Services-3 (FC-GS-4)" 709 DEFVAL { ''H } 710 ::= { t11NsRegEntry 7 } 712 t11NsRegFc4Type OBJECT-TYPE 713 SYNTAX OCTET STRING (SIZE (0 | 32)) 714 MAX-ACCESS read-only 715 STATUS current 716 DESCRIPTION 717 "The FC-4 protocol types supported by this Nx_Port. 718 This is an array of 256-bits. Each bit in the array 719 corresponds to a Type value as defined by the fibre 720 channel standards and contained in the Type field of 721 the frame header. 723 If no 'FC-4 TYPEs' has been registered, then the value 724 of this object is the zero-length string." 725 REFERENCE 726 "ANSI INCITS 387-2004, Fibre Channel - Generic 727 Services-3 (FC-GS-4)" 728 DEFVAL { ''H } 729 ::= { t11NsRegEntry 8 } 731 t11NsRegPortType OBJECT-TYPE 732 SYNTAX FcPortType 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "The port type of this port. 738 If no 'Port Type' has been registered, then the value 739 of this object is unidentified, and represented by 740 the value: 'unknown'." 741 DEFVAL { 1 } -- 'unknown', see [FC-MGMT] 742 ::= { t11NsRegEntry 9 } 744 t11NsRegPortIpAddress OBJECT-TYPE 745 SYNTAX OCTET STRING (SIZE (0 | 16)) 746 MAX-ACCESS read-only 747 STATUS current 748 DESCRIPTION 749 "The value which Fibre Channel calls an 'IP Address (Port)' 750 which represents the IP address of the associated port. 751 The value is either in 32-bit IPv4 format or 128-bit IPv6 752 format. When this object contains a IPv4 address, the 753 leftmost 96 bits (12 bytes) should contain x'00 00 00 00 00 754 00 00 00 00 00 FF FF'. The IPv4 address should be present in 755 the rightmost 32 bits. 757 Note that the value of this object is the IP address value 758 that is received in the FC-GS-4 message Register IP address 759 (Port) RIPP_ID. It is not validated against any IP address 760 format. 762 If no 'IP address (Port)' has been registered, then the 763 value of this object is the zero-length string." 764 REFERENCE 765 "ANSI INCITS 387-2004, Fibre Channel - Generic 766 Services-3, (FC-GS-4)" 767 DEFVAL {''H} 768 ::= { t11NsRegEntry 10 } 770 t11NsRegFabricPortName OBJECT-TYPE 771 SYNTAX FcNameIdOrZero 772 MAX-ACCESS read-only 773 STATUS current 774 DESCRIPTION 775 "The Fabric Port Name (WWN) of the Fx_Port to which 776 this Nx_Port is attached. 778 If no 'Fabric Port Name' has been registered, then the 779 value of this object is the zero-length string." 780 DEFVAL {''H} 781 ::= { t11NsRegEntry 11 } 783 t11NsRegHardAddress OBJECT-TYPE 784 SYNTAX FcAddressIdOrZero 785 MAX-ACCESS read-only 786 STATUS current 787 DESCRIPTION 788 "The format of this object is identical to the format 789 of Hard Address defined in the Discover Address (ADISC) 790 Extended Link Service (FC-FS). 791 Hard Address is the 24-bit NL_Port identifier which 792 consists of 793 - the 8-bit Domain_ID in the most significant byte 794 - the 8-bit Area Id in the next most significant 795 byte 796 - the 8-bit AL-PA(Arbitrated Loop Physical Address) 797 which an NL_Port attempts acquire during FC-AL 798 initialization in the least significant byte. 800 If the port is not an NL_Port, or if it is an NL_Port 801 but does not have a hard address, then all bits are 802 reported as zeros. 804 If no 'Hard Address' has been registered, then the 805 value of this object is the zero-length string." 806 DEFVAL {''H} 807 ::= { t11NsRegEntry 12 } 809 t11NsRegSymbolicPortName OBJECT-TYPE 810 SYNTAX SnmpAdminString (SIZE (0..255)) 811 MAX-ACCESS read-only 812 STATUS current 813 DESCRIPTION 814 "The user-defined name of this port. 816 If no 'Symbolic Port Name' has been registered, then 817 the value of this object is the zero length string." 818 DEFVAL {''H} 819 ::= { t11NsRegEntry 13 } 821 t11NsRegSymbolicNodeName OBJECT-TYPE 822 SYNTAX SnmpAdminString (SIZE (0..255)) 823 MAX-ACCESS read-only 824 STATUS current 825 DESCRIPTION 826 "The user-defined name of the node of this port. 828 If no 'Symbolic Node Name' has been registered, then 829 the value of this object is the zero length string." 830 DEFVAL {''H} 831 ::= { t11NsRegEntry 14 } 833 t11NsRegFc4Features OBJECT-TYPE 834 SYNTAX OCTET STRING (SIZE (0 | 32)) 835 MAX-ACCESS read-only 836 STATUS current 837 DESCRIPTION 838 "The FC-4 Features associated with this port and the 839 FC-4 Type. Refer to FC-GS-4 specification for the 840 format of this object. 841 This object is an array of 4-bit values, one for each 842 TYPE code value. 843 The 5 most significant bits of the TYPE field will be 844 used to identify the word for the FC-4 Features object. 845 - Word 0 contains information related to TYPE 846 code '00' through '07'; 847 - Word 1 contains information related to TYPE 848 code '08' through 0F'; 849 - and so forth to Word 31 that contains 850 information related to TYPE code 'F8' 851 through 'FF'. 852 The 3 least significant bits of the TYPE field will be 853 used to identify the position within the word for the 854 4-bit FC-4 Features value. 856 If no 'FC-4 Features' has been registered, then 857 the value of this object is the zero length string." 858 REFERENCE 859 "ANSI INCITS 387-2004, Fibre Channel - Generic 860 Services-3 (FC-GS-4)" 861 DEFVAL {''H} 862 ::= { t11NsRegEntry 15 } 864 -- 865 -- Registered FC-4 Descriptors 866 -- 868 t11NsRegFc4DescriptorTable OBJECT-TYPE 869 SYNTAX SEQUENCE OF T11NsRegFc4DescriptorEntry 870 MAX-ACCESS not-accessible 871 STATUS current 872 DESCRIPTION 873 "This table contains entries for all FC-4 Descriptors 874 registered with Name Server instances on 875 all Fabrics on which they operate." 876 ::= { t11NsStatus 3 } 878 t11NsRegFc4DescriptorEntry OBJECT-TYPE 879 SYNTAX T11NsRegFc4DescriptorEntry 880 MAX-ACCESS not-accessible 881 STATUS current 882 DESCRIPTION 883 "An entry in the t11NsRegFc4DescriptorTable, 884 containing information about a FC-4 Descriptor 885 which is associated with a particular FC-4 Type 886 value. The particular FC-4 Descriptor was 887 registered by an Nx_Port (identified by 888 t11NsRegPortIdentifier) with a Name Server instance 889 (identified by t11NsIndex) within the Fibre Channel 890 management instance (identified by fcmInstanceIndex) 891 on the Fabric (identified by t11NsRegFabricIndex). 893 If no FC-4 Descriptors have been registered 894 for a particular port, then there will be no 895 entries in this table for that port." 896 INDEX { fcmInstanceIndex, t11NsIndex, 897 t11NsRegFabricIndex, t11NsRegPortIdentifier, 898 t11NsRegFc4TypeValue } 899 ::= { t11NsRegFc4DescriptorTable 1 } 901 T11NsRegFc4DescriptorEntry ::= SEQUENCE { 902 t11NsRegFc4TypeValue Unsigned32, 903 t11NsRegFc4Descriptor OCTET STRING 904 } 906 t11NsRegFc4TypeValue OBJECT-TYPE 907 SYNTAX Unsigned32 908 MAX-ACCESS not-accessible 909 STATUS current 910 DESCRIPTION 911 "An integer value which identifies an FC-4 Type value 912 for which an FC-4 Descriptor has been registered. 914 An instance of this object contains the 'Type value' 915 to which one of the 256 bits in a t11NsRegFc4Type value 916 corresponds." 917 ::= { t11NsRegFc4DescriptorEntry 1 } 919 t11NsRegFc4Descriptor OBJECT-TYPE 920 SYNTAX OCTET STRING (SIZE (0..255)) 921 MAX-ACCESS read-only 922 STATUS current 923 DESCRIPTION 924 "The FC-4 Descriptor value which has been registered 925 for the particular port on the particular fabric, and 926 for the FC-4 Type represented by the corresponding 927 value of t11NsRegFc4TypeIndex. 929 The format of an FC-4 Descriptor is dependent on the 930 corresponding FC-4 Type value." 931 REFERENCE 932 "ANSI INCITS 387-2004, Fibre Channel - Generic 933 Services-3 (FC-GS-4), section 5.2.5.42" 934 ::= { t11NsRegFc4DescriptorEntry 2 } 936 -- 937 -- Name Server per-Fabric Statistics 938 -- 940 t11NsStatsTable OBJECT-TYPE 941 SYNTAX SEQUENCE OF T11NsStatsEntry 942 MAX-ACCESS not-accessible 943 STATUS current 944 DESCRIPTION 945 "This table contains per-Fabric state and statistics 946 maintained by Name Server instances." 947 ::= { t11NsStatistics 1 } 949 t11NsStatsEntry OBJECT-TYPE 950 SYNTAX T11NsStatsEntry 951 MAX-ACCESS not-accessible 952 STATUS current 953 DESCRIPTION 954 "An entry in this table, containing state and stats 955 for a Name Server instance (identified by t11NsIndex) 956 within the Fibre Channel management instance 957 (identified by fcmInstanceIndex) on the Fabric 958 (identified by t11NsRegFabricIndex)." 959 INDEX { fcmInstanceIndex, t11NsIndex, t11NsRegFabricIndex } 960 ::= { t11NsStatsTable 1 } 962 T11NsStatsEntry ::= SEQUENCE { 963 t11NsInGetReqs Counter32, 964 t11NsOutGetReqs Counter32, 965 t11NsInRegReqs Counter32, 966 t11NsInDeRegReqs Counter32, 967 t11NsInRscns Counter32, 968 t11NsOutRscns Counter32, 969 t11NsRejects Counter32, 970 t11NsDatabaseFull TruthValue 971 } 973 t11NsInGetReqs OBJECT-TYPE 974 SYNTAX Counter32 975 MAX-ACCESS read-only 976 STATUS current 977 DESCRIPTION 978 "The total number of (CT_IU) Get Requests 979 received by the Name Server instance on this 980 Fabric." 981 ::= { t11NsStatsEntry 1 } 983 t11NsOutGetReqs OBJECT-TYPE 984 SYNTAX Counter32 985 MAX-ACCESS read-only 986 STATUS current 987 DESCRIPTION 988 "The total number of (CT_IU) Get Requests sent by 989 the Name Server instance on this Fabric." 990 ::= { t11NsStatsEntry 2 } 992 t11NsInRegReqs OBJECT-TYPE 993 SYNTAX Counter32 994 MAX-ACCESS read-only 995 STATUS current 996 DESCRIPTION 997 "The total number of (CT_IU) Registration Requests 998 received by the Name Server instance on this Fabric." 999 ::= { t11NsStatsEntry 3 } 1001 t11NsInDeRegReqs OBJECT-TYPE 1002 SYNTAX Counter32 1003 MAX-ACCESS read-only 1004 STATUS current 1005 DESCRIPTION 1006 "The total number of (CT_IU) De-registration Requests 1007 received by the Name Server instance on this Fabric." 1008 ::= { t11NsStatsEntry 4 } 1010 t11NsInRscns OBJECT-TYPE 1011 SYNTAX Counter32 1012 MAX-ACCESS read-only 1013 STATUS current 1014 DESCRIPTION 1015 "The total number of RSCNs, indicating Name 1016 Server-related changes, received by the Name Server 1017 instance on this Fabric." 1018 ::= { t11NsStatsEntry 5 } 1020 t11NsOutRscns OBJECT-TYPE 1021 SYNTAX Counter32 1022 MAX-ACCESS read-only 1023 STATUS current 1024 DESCRIPTION 1025 "The total number of RSCNs, indicating Name 1026 Server-related changes, sent by the Name Server 1027 instance on this Fabric." 1028 ::= { t11NsStatsEntry 6 } 1030 t11NsRejects OBJECT-TYPE 1031 SYNTAX Counter32 1032 MAX-ACCESS read-only 1033 STATUS current 1034 DESCRIPTION 1035 "The total number of CT_IU Requests for Name 1036 Server functions which were rejected by the Name 1037 Server instance on this Fabric." 1038 ::= { t11NsStatsEntry 7 } 1040 t11NsDatabaseFull OBJECT-TYPE 1041 SYNTAX TruthValue 1042 MAX-ACCESS read-only 1043 STATUS current 1044 DESCRIPTION 1045 "An indication of whether the Name Server instance's 1046 database is full. This object is set to 'true' only 1047 if the Name Server is unable to allocate space for a 1048 new entry for the corresponding Fabric, and set to 1049 'false' whenever an existing entry is deleted for the 1050 corresponding Fabric." 1051 ::= { t11NsStatsEntry 8 } 1053 -- 1054 -- Reject information objects 1055 -- 1056 t11NsRejectTable OBJECT-TYPE 1057 SYNTAX SEQUENCE OF T11NsRejectEntry 1058 MAX-ACCESS not-accessible 1059 STATUS current 1060 DESCRIPTION 1061 "This table contains information about the most recent 1062 Name Server Registration request failures for various 1063 ports on various fabrics. 1065 If no information is available about the most recent 1066 rejection of a registration request on a particular port 1067 on a particular fabric, then there will no entry in this 1068 table for that port and fabric. 1070 When a t11NsRejectRegNotify notification is sent for 1071 such a registration request failure, the values of the 1072 objects in the relevant entry of this table are updated 1073 immediately prior to generating the notification." 1074 ::= { t11NsStatus 4 } 1076 t11NsRejectEntry OBJECT-TYPE 1077 SYNTAX T11NsRejectEntry 1078 MAX-ACCESS not-accessible 1079 STATUS current 1080 DESCRIPTION 1081 "An entry in the t11NsRejectTable containing information 1082 about the most recent Registration request rejected by 1083 a Name Server instance (identified by t11NsIndex) 1084 within the Fibre Channel management instance (identified 1085 by fcmInstanceIndex) for a particular port (identified by 1086 t11NsRegPortIdentifier) on a particular fabric (identified by 1087 t11NsRegFabricIndex)." 1088 INDEX { fcmInstanceIndex, t11NsIndex, 1089 t11NsRegFabricIndex, t11NsRegPortIdentifier } 1090 ::= { t11NsRejectTable 1 } 1092 T11NsRejectEntry ::= SEQUENCE { 1093 t11NsRejectCtCommandString OCTET STRING, 1094 t11NsRejectReasonCode T11NsGs4RejectReasonCode, 1095 t11NsRejReasonCodeExp T11NsRejReasonCodeExpl 1096 } 1098 t11NsRejectCtCommandString OBJECT-TYPE 1099 SYNTAX OCTET STRING (SIZE (0..255)) 1100 MAX-ACCESS read-only 1101 STATUS current 1102 DESCRIPTION 1103 "The binary content of the Registration Request, 1104 formatted as an octet string (in network byte 1105 order) containing the CT_IU, as described in 1106 Table 2 of [FC-GS-4] (including the preamble), 1107 which was most recently rejected by the 1108 Name Server instance for the particular port 1109 on the particular fabric. 1111 This object contains the zero-length string 1112 if and when the CT-IU's content is unavailable. 1114 When the length of this object is 255 octets, it 1115 contains the first 255 octets of the CT-IU." 1116 ::= { t11NsRejectEntry 1 } 1118 t11NsRejectReasonCode OBJECT-TYPE 1119 SYNTAX T11NsGs4RejectReasonCode 1120 MAX-ACCESS read-only 1121 STATUS current 1122 DESCRIPTION 1123 "A registration reject reason code. This object 1124 contains the reason code of the most recent Name 1125 Server Registration request failure for the 1126 particular port on the particular fabric." 1127 ::= { t11NsRejectEntry 2 } 1129 t11NsRejReasonCodeExp OBJECT-TYPE 1130 SYNTAX T11NsRejReasonCodeExpl 1131 MAX-ACCESS read-only 1132 STATUS current 1133 DESCRIPTION 1134 "A registration reject reason code explanation. This 1135 object contains the reason code explanation of the most 1136 recent Name Server Registration request failure for the 1137 particular port on the particular fabric." 1138 ::= { t11NsRejectEntry 3 } 1140 -- 1141 -- Notifications 1142 -- 1144 t11NsRejectRegNotify NOTIFICATION-TYPE 1145 OBJECTS { t11NsRegPortName, t11NsRejectCtCommandString, 1146 t11NsRejectReasonCode, t11NsRejReasonCodeExp } 1147 STATUS current 1148 DESCRIPTION 1149 "This notification is generated by a Name Server 1150 instance (if its t11NsRejReqNotifyEnable is 'true') 1151 whenever it rejects a registration request on a 1152 particular fabric for a particular Nx_Port. 1153 The value of t11NsRejectCtCommandString indicates 1154 the rejected request, and the values of 1155 t11NsRejectReasonCode and t11NsRejReasonCodeExp 1156 indicate the reason for the rejection. 1158 The value of t11NsRegPortName represents the Port Name 1159 if it is able to be extracted out of the registration 1160 request, or otherwise the value as currently registered 1161 on the port." 1162 ::= { t11NsNotifications 1 } 1164 -- 1165 -- Conformance 1166 -- 1168 t11NsMIBCompliances OBJECT IDENTIFIER ::= {t11NsMIBConformance 1} 1169 t11NsMIBGroups OBJECT IDENTIFIER ::= {t11NsMIBConformance 2} 1171 t11NsMIBCompliance MODULE-COMPLIANCE 1172 STATUS current 1173 DESCRIPTION 1174 "The compliance statement for entities which 1175 implement the Fibre Channel Name Server." 1176 MODULE MANDATORY-GROUPS {t11NsDBGroup, 1177 t11NsStatsGroup, 1178 t11NsNotifyControlGroup, 1179 t11NsNotifyGroup} 1181 OBJECT t11NsRejReqNotifyEnable 1182 MIN-ACCESS read-only 1183 DESCRIPTION 1184 "Write access is not required." 1186 ::= { t11NsMIBCompliances 1 } 1188 -- Units of conformance 1189 t11NsDBGroup OBJECT-GROUP 1190 OBJECTS { t11NsSwitchIndex, 1191 t11NsTableLastChange, 1192 t11NsNumRows, 1193 t11NsRegPortName, 1194 t11NsRegNodeName, 1195 t11NsRegClassOfSvc, 1196 t11NsRegNodeIpAddress, 1197 t11NsRegProcAssoc, 1198 t11NsRegFc4Type, 1199 t11NsRegPortType, 1200 t11NsRegPortIpAddress, 1201 t11NsRegFabricPortName, 1202 t11NsRegHardAddress, 1203 t11NsRegSymbolicPortName, 1204 t11NsRegSymbolicNodeName, 1205 t11NsRegFc4Features, 1206 t11NsRegFc4Descriptor } 1207 STATUS current 1208 DESCRIPTION 1209 "A collection of objects for monitoring the information 1210 registered with the Name Server." 1211 ::= { t11NsMIBGroups 1 } 1213 t11NsStatsGroup OBJECT-GROUP 1214 OBJECTS { t11NsTotalRejects, 1215 t11NsInGetReqs, 1216 t11NsOutGetReqs, 1217 t11NsInRegReqs, 1218 t11NsInDeRegReqs, 1219 t11NsInRscns, 1220 t11NsOutRscns, 1221 t11NsRejects, 1222 t11NsDatabaseFull} 1223 STATUS current 1224 DESCRIPTION 1225 "A collection of objects for displaying Name 1226 Server statistics and state." 1227 ::= { t11NsMIBGroups 2 } 1229 t11NsNotifyControlGroup OBJECT-GROUP 1230 OBJECTS { t11NsRejectCtCommandString, 1231 t11NsRejectReasonCode, 1232 t11NsRejReasonCodeExp, 1233 t11NsRejReqNotifyEnable } 1235 STATUS current 1236 DESCRIPTION 1237 "A collection of notification control and 1238 notification information objects for monitoring 1239 Name Server registrations/de-registrations." 1240 ::= { t11NsMIBGroups 3 } 1242 t11NsNotifyGroup NOTIFICATION-GROUP 1243 NOTIFICATIONS {t11NsRejectRegNotify } 1244 STATUS current 1245 DESCRIPTION 1246 "A collection of notifications for monitoring 1247 Name Server registrations/de-registrations." 1248 ::= { t11NsMIBGroups 4 } 1250 END 1252 7. Intellectual Property 1254 The IETF takes no position regarding the validity or scope of any 1255 intellectual property or other rights that might be claimed to 1256 pertain to the implementation or use of the technology described in 1257 this document or the extent to which any license under such rights 1258 might or might not be available; neither does it represent that it 1259 has made any effort to identify any such rights. Information on the 1260 IETF's procedures with respect to rights in standards-track and 1261 standards-related documentation can be found in BCP-11. Copies of 1262 claims of rights made available for publication and any assurances of 1263 licenses to be made available, or the result of an attempt made to 1264 obtain a general license or permission for the use of such 1265 proprietary rights by implementors or users of this specification can 1266 be obtained from the IETF Secretariat. 1268 The IETF invites any interested party to bring to its attention any 1269 copyrights, patents or patent applications, or other proprietary 1270 rights which may cover technology that may be required to practice 1271 this standard. Please address the information to the IETF Executive 1272 Director. 1274 8. Acknowledgements 1276 This document is currently a work item of the INCITS Task Group 1277 T11.5. We wish to acknowledge the many contributions and comments 1278 from the INCITS Technical Committee T11, including the following: 1279 T11 Chair: Robert Snively, Brocade 1280 T11 Vice Chair: Claudio Desanti, Cisco Systems 1281 T11.5 Chair: Roger Cummings, VERITAS 1282 T11.5 members, especially: 1283 Ken Hirata, Emulex 1284 Scott Kipp, McData 1285 Michael O'Donnell, McData 1286 Elizabeth G. Rodriguez, Dot Hill 1287 Steven L. Wilson, Brocade 1289 9. Normative References 1291 [RFC2578] 1292 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1293 and S. Waldbusser, "Structure of Management Information Version 2 1294 (SMIv2)", STD 58, RFC 2578, April 1999. 1296 [RFC2579] 1297 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1298 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 1299 2579, April 1999. 1301 [RFC2580] 1302 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1303 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 1304 2580, April 1999. 1306 [RFC3411] 1307 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1308 Describing Simple Network Management Protocol (SNMP) Management 1309 Frameworks", STD 58, RFC 3411, December 2002. 1311 [FC-FS] 1312 "Fibre Channel - Framing and Signaling (FC-FS)" ANSI INCITS 1313 373-2003, April 2003. 1315 [FC-GS-3] 1316 "Fibre Channel - Generic Services - 3 (FC-GS-3)", ANSI INCITS 1317 348-2000, November 2000. 1319 [FC-GS-4] 1320 "Fibre Channel - Generic Services - 4 (FC-GS-4)", ANSI INCITS 1321 387-2004, T11/Project 1505-D/Rev 7.91 Febrauary 2004. 1323 [FC-SW-3] 1324 "Fibre Channel - Switch Fabric - 3 (FC-SW-3)", ANSI NCITS xxx-xxxx, 1325 T11/Project 1508-D/Rev 6.6, December 2003. 1327 [FC-MGMT] 1328 K. McCloghrie, "Fibre Channel Management MIB", Internet-Draft 1329 (draft-ietf-ips-fcmgmt-mib-nn.txt), work-in-progress. 1331 [FC-FAM-MIB] 1332 DeSanti, C., Gaonkar, V., McCloghrie, K., and S. Gai, "Fibre- 1333 Channel Fabric Address Manager MIB", Internet-Draft (draft-desanti- 1334 fc-fabric-addr-mgr-nn.txt), work-in-progress. 1336 10. Informative References 1338 [RFC2837] 1339 Teow, K., "Definitions of Managed Objects for the Fabric Element in 1340 Fibre Channel Standard", RFC 2837, May 2000. 1342 [RFC3410] 1343 Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and 1344 Applicability Statements for Internet- Standard Management 1345 Framework", RFC 3410, December 2002. 1347 11. Security Considerations 1349 There is one management object defined in this MIB module with a MAX- 1350 ACCESS clause of read-write and/or read-create. Such objects may be 1351 considered sensitive or vulnerable in some network environments. The 1352 support for SET operations in a non-secure environment without proper 1353 protection can have a negative effect on network operations. This 1354 object and its sensitivity/vulnerability is: 1356 t11NsRejReqNotifyEnable -- the ability to enable/disable 1357 notifications. 1359 Such objects may be considered sensitive or vulnerable in some network 1360 environments. For example, the ability to change network topology or 1361 network speed may afford an attacker the ability to obtain better 1362 performance at the expense of other network users. The support for SET 1363 operations in a non-secure environment without proper protection can 1364 have a negative effect on network operations. 1366 Some of the readable objects in this MIB module (i.e., objects with a 1367 MAX-ACCESS other than not-accessible) may be considered sensitive or 1368 vulnerable in some network environments. It is thus important to 1369 control even GET and/or NOTIFY access to these objects and possibly to 1370 even encrypt the values of these objects when sending them over the 1371 network via SNMP. These are the tables and objects and their 1372 sensitivity/vulnerability: 1374 t11NsRegTable -- contains information about registered Nx_Ports. 1376 t11NsStatsTable -- contains statistics and state information about 1377 the Name Server. 1379 SNMP versions prior to SNMPv3 did not include adequate security. Even 1380 if the network itself is secure (for example by using IPSec), even then, 1381 there is no control as to who on the secure network is allowed to access 1382 and GET/SET (read/change/create/delete) the objects in this MIB module. 1384 It is RECOMMENDED that implementors consider the security features as 1385 provided by the SNMPv3 framework (see [RFC3410], section 8), including 1386 full support for the SNMPv3 cryptographic mechanisms (for authentication 1387 and privacy). 1389 Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. 1390 Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic 1391 security. It is then a customer/operator responsibility to ensure that 1392 the SNMP entity giving access to an instance of this MIB module is 1393 properly configured to give access to the objects only to those 1394 principals (users) that have legitimate rights to indeed GET or SET 1395 (change/create/delete) them. 1397 12. Authors' Addresses 1399 Claudio DeSanti 1400 Cisco Systems, Inc. 1401 170 West Tasman Drive 1402 San Jose, CA 95134 USA 1403 Phone: +1 408 853-9172 1404 EMail: cds@cisco.com 1406 Vinay Gaonkar 1407 Cisco Systems, Inc. 1408 170 West Tasman Drive 1409 San Jose, CA 95134 USA 1410 Phone: +1 408 527-8576 1411 EMail: vgaonkar@cisco.com 1413 H.K. Vivek 1414 Cisco Systems, Inc. 1415 71 Millers Rd 1416 Bangalore, India 1417 Phone: +91 80 2289933x5117 1418 EMail: hvivek@cisco.com 1420 Keith McCloghrie 1421 Cisco Systems, Inc. 1422 170 West Tasman Drive 1423 San Jose, CA USA 95134 1424 Phone: +1 408-526-5260 1425 Email: kzm@cisco.com 1427 Silvano Gai 1428 Cisco Systems, Inc. 1429 170 West Tasman Drive 1430 San Jose, CA USA 95134 1431 Phone: +1 408-526-7269 1432 Email: sgai@cisco.com 1434 13. Full Copyright Statement 1436 Copyright (C) The Internet Society (2004). All Rights Reserved. 1438 This document and translations of it may be copied and furnished to 1439 others, and derivative works that comment on or otherwise explain it or 1440 assist in its implementation may be prepared, copied, published and 1441 distributed, in whole or in part, without restriction of any kind, 1442 provided that the above copyright notice and this paragraph are included 1443 on all such copies and derivative works. However, this document itself 1444 may not be modified in any way, such as by removing the copyright notice 1445 or references to the Internet Society or other Internet organizations, 1446 except as needed for the purpose of developing Internet standards in 1447 which case the procedures for copyrights defined in the Internet 1448 Standards process must be followed, or as required to translate it into 1449 languages other than English. 1451 The limited permissions granted above are perpetual and will not be 1452 revoked by the Internet Society or its successors or assigns. 1454 This document and the information contained herein is provided on an "AS 1455 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1456 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1457 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1458 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1459 FITNESS FOR A PARTICULAR PURPOSE.