idnits 2.17.1 draft-ietf-imss-fc-rscn-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1344. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1355. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1362. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1368. ** 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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (10 November 2006) is 6378 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-SW-4' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-FS' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-LS' -- Obsolete informational reference (is this intentional?): RFC 2837 (Obsoleted by RFC 4044) Summary: 4 errors (**), 0 flaws (~~), 2 warnings (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft C. DeSanti 2 H.K. Vivek 3 K. McCloghrie 4 Cisco Systems 5 S. Gai 6 10 November 2006 8 Fibre Channel Registered State Change Notification (RSCN) MIB 9 draft-ietf-imss-fc-rscn-mib-02.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 (2006). 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 management of Fibre Channel's Registered State Change 43 Notifications (RSCNs). 45 Table of Contents 47 1 Introduction ................................................. 3 48 1.1 Change Log ................................................. 3 49 2 The Internet-Standard Management Framework ................... 5 50 3 Short Overview of Fibre Channel .............................. 6 51 4 Relationship to Other MIBs ................................... 7 52 5 MIB Overview ................................................. 8 53 5.1 Fibre Channel management instance .......................... 8 54 5.2 Switch Index ............................................... 8 55 5.3 Fabric Index ............................................... 8 56 5.4 The t11FcRscnRegistrationGroup group ....................... 9 57 5.5 The t11FcRscnNotifyGroup group ............................. 9 58 5.6 The t11FcRscnNotifyControlGroup group ...................... 9 59 5.7 The t11FcRscnStatsGroup group .............................. 10 60 6 Definitions .................................................. 11 61 6.1 The T11-FC-RSCN-MIB Module ................................. 11 62 7 Acknowledgements ............................................. 28 63 8 Normative References ......................................... 28 64 9 Informative References ....................................... 29 65 10 IANA Considerations ......................................... 30 66 11 Security Considerations ..................................... 30 67 12 Authors' Addresses .......................................... 31 69 1. Introduction 71 This memo defines a portion of the Management Information Base (MIB) 72 for use with network management protocols in the Internet community. 73 In particular, it describes managed objects for information related 74 to Registered State Change Notifications (RSCNs) [FC-LS] in a Fibre 75 Channel network, including which Nx_Ports are registered to receive 76 which types of RSCNs, the control and generation of SNMP 77 notifications on registration failures, and RSCN-related statistics. 79 This memo was previously approved by T11.5 (http://www.t11.org); it 80 is currently a work item of the IETF's IMSS working group. 82 This memo includes boilerplate which uses only one of the following 83 terms, but is nevertheless required to mention all of the keywords in 84 the following statement: 86 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 87 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" 88 in this document are to be interpreted as described in BCP 14, RFC 89 2119 [RFC2119]. 91 1.1. Change Log 93 This section to be deleted before publication as an RFC. 95 1.1.1. Initial version 97 The initial version was submitted to T11.5 as T11/05-787v0 on 18 98 November 2005. 100 1.1.2. 6 December 2005 version 102 The following changes were made for the version was submitted to 103 T11.5 as T11/05-787v1 and the IETF as: 104 draft-kzm-imss-fc-rscn-mib-01.txt. 106 - added many clarifications, fixed typos, and finished previously- 107 incomplete sections. 109 - fixed compile errors in the MIB module. 111 1.1.3. 17 December 2005 version 113 The following changes were made for the version was submitted to 114 T11.5 as T11/05-787v2 and the IETF as: 115 draft-kzm-imss-fc-rscn-mib-02.txt. 117 - Replaced the one (aggregated) object t11FcRscnRejectedReasonCode by 118 the three separate objects for Reject Reason Code, Reason Code 119 Explanation and Reason Vendor Specific Code. 121 - Changed the reference for definitions of RSCN and SCR to be FC-LS 122 (instead of FC-FS). 124 - Added URLs for T11 specifications in the Reference section. 126 1.1.4. 5 March 2006 version 128 The following changes were made for the version was submitted to 129 T11.5 as T11/06-198v0 and the IETF as: 130 draft-kzm-imss-fc-rscn-mib-03.txt. 132 - Explained the term "SW_RSCN" on the first usage of the phrase "an 133 SW_ILS with a SW_RSCN payload", and replaced all subsequent uses of 134 the phrase by SW_RSCN. 136 - Changed "Rx" to "In" and "Tx" to "Out" in the descriptors of 137 Counter32's, e.g., changed t11FcRscnRxRscns to t11FcRscnInRscns. 139 - Added ten counters for the number of sent/received RSCNs for the 140 individual 'Event Qualifier' values defined in [FC-LS]. 142 - Many editorial changes. 144 1.1.5. 14 August 2006 version 146 The following changes were made for the version was submitted to the 147 IETF as: draft-ietf-imss-fc-rscn-mib-00.txt. 149 - Changes to indicate the adoption of this memo as a work item of the 150 IMSS Working Group. 152 - Added explicit statement to all Counter32's that they have no 153 discontinuities other than those that all Counter32s have when 154 sysUpTime=0. 156 - Updated references to FC-SW-4 to point at "ANSI INCITS 418-2006". 158 1.1.6. 16 October 2006 version 160 The following changes were made for the version was submitted to the 161 IETF as: draft-ietf-imss-fc-rscn-mib-01.txt. 163 - Fixed missing comma in T11FcRscnStatsEntry's SEQUENCE. 165 - Minor editorial changes in the references to an SNMP context. 167 - A clarification was added to the Security Considerations section. 169 - Text was added to explain why flow-control is not needed for the 170 notifications in this MIB module. 172 1.1.7. 10 November 2006 version 174 The following changes were made for the version was submitted to the 175 IETF as: draft-ietf-imss-fc-rscn-mib-02.txt. 177 - References to [FC-LS] were updated to refer to Revision 1.61 of 3 178 November 2006. (The use of "xxx-200n" remains, with an RFC- 179 Editor's Note that it needs to be updated before RFC publication.) 181 2. The Internet-Standard Management Framework 183 For a detailed overview of the documents that describe the current 184 Internet-Standard Management Framework, please refer to section 7 of 185 RFC 3410 [RFC3410]. 187 Managed objects are accessed via a virtual information store, termed 188 the Management Information Base or MIB. MIB objects are generally 189 accessed through the Simple Network Management Protocol (SNMP). 190 Objects in the MIB are defined using the mechanisms defined in the 191 Structure of Management Information (SMI). This memo specifies a MIB 192 module that is compliant to the SMIv2, which is described in STD 58, 193 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 194 [RFC2580]. 196 3. Short Overview of Fibre Channel 198 The Fibre Channel (FC) is logically a bidirectional point-to-point 199 serial data channel, structured for high performance. Fibre Channel 200 provides a general transport vehicle for higher level protocols such 201 as Small Computer System Interface (SCSI) command sets, the High- 202 Performance Parallel Interface (HIPPI) data framing, IP (Internet 203 Protocol), IEEE 802.2, and others. 205 Physically, Fibre Channel is an interconnection of multiple 206 communication points, called N_Ports, interconnected either by a 207 switching network, called a Fabric, or by a point-to-point link. A 208 Fibre Channel "node" consists of one or more N_Ports. A Fabric may 209 consist of multiple Interconnect Elements, some of which are 210 switches. An N_Port connects to the Fabric via a port on a switch 211 called an F_Port. When multiple FC nodes are connected to a single 212 port on a switch via an "Arbitrated Loop" topology, the switch port 213 is called an FL_Port, and the nodes' ports are called NL_Ports. The 214 term Nx_Port is used to refer to either an N_Port or an NL_Port. The 215 term Fx_Port is used to refer to either an F_Port or an FL_Port. A 216 switch port, which is interconnected to another switch port via an 217 Inter Element Link (IEL), is called an E_Port. A B_Port connects a 218 bridge device with an E_Port on a switch; a B_Port provides a subset 219 of E_Port functionality. 221 Many Fibre Channel components, including the fabric, each node, and 222 most ports, have globally-unique names. These globally-unique names 223 are typically formatted as World Wide Names (WWNs). More information 224 on WWNs can be found in [FC-FS]. WWNs are expected to be persistent 225 across agent and unit resets. 227 Fibre Channel frames contain 24-bit address identifiers which 228 identify the frame's source and destination ports. Each FC port has 229 both an address identifier and a WWN. When a fabric is in use, the 230 FC address identifiers are dynamically assigned by a switch. Each 231 octet of a 24-bit address represents a level in an address hierarchy, 232 with a Domain_ID being the highest level of the hierarchy. 234 Registered State Change Notifications (RSCNs) are defined in [FC-LS] 235 as a means to provide Nx_Ports which have registered to receive such 236 notifications, with a timely indication of changes in the state of 237 nodes attached to the fabric. Specifically, an Nx_Port may choose to 238 register, using an State Change Registration (SCR) request [FC-LS] to 239 receive RSCNs. A Nx_Port which has registered will receive an RSCN 240 when an event occurs which may affect the registered port's state. 242 For example, an Nx_Port can use RSCNs as the means by which it is 243 informed of the failures of other nodes, of new devices coming 244 online, or even of more network-accessible storage becoming 245 available. The payload of the RSCN indicates the type of change and 246 includes the address of the changed port. RSCNs are often generated 247 by the fabric, but an Nx_Port can also generate (and send to the 248 fabric) an RSCN if and when it detects an event not visible to the 249 fabric. The sender of an RSCN may coalesce several events into a 250 single RSCN message. Each RSCN is a "request" which is acknowledged 251 by the receiver with an accept or reject. 253 An RSCN is received by an Nx_Port from the Fabric as an Extended Link 254 Service (ELS) request [FC-LS]. The Fabric distributes RSCNs between 255 Switches using an SW_ILS frame with an Inter-Switch RSCN payload, 256 also known as an SW_RSCN [FC-SW-4]. So, when a Switch has directly 257 attached Nx_Ports which have registered to receive RSCNs, it converts 258 received SW_RSCNs (i.e., SW_ILS frames containing SW_RSCN payloads) 259 into ELS requests containing the corresponding RSCN which it sends to 260 each such Nx_Port. 262 The latest standard for an interconnecting Fabric containing multiple 263 Fabric Switch elements is [FC-SW-4]. [FC-SW-4] carries forward the 264 earlier specification for the operation of a single Fabric in a 265 physical infrastructure, and augments it with the definition of 266 Virtual Fabrics and with the specification of how multiple Virtual 267 Fabrics can operate within one (or more) physical infrastructures. 268 The use of Virtual Fabrics provides for each frame to be tagged in 269 its header to indicate which one of several Virtual Fabrics that 270 frame is being transmitted on. All frames entering a particular 271 "Core Switch" [FC-SW-4] (i.e., a physical switch) on the same Virtual 272 Fabric are processed by the same "Virtual Switch" within that Core 273 switch. 275 4. Relationship to Other MIBs 277 The first standardized MIB for Fibre Channel [RFC2837] was focused on 278 Fibre Channel switches. It was replaced by the more generic Fibre 279 Channel Management MIB [RFC4044] which defines basic information for 280 Fibre Channel hosts and switches, including extensions to the 281 standard IF-MIB [IF-MIB] for Fibre Channel interfaces. [RFC4044] 282 includes the specification of how the generic objects defined in [IF- 283 MIB] apply to Fibre Channel interfaces. 285 This MIB imports some common Textual Conventions defined in the 286 T11-TC-MIB [RFC4439] and in the T11-FC-NAME-SERVER-MIB [RFC4438]. 288 5. MIB Overview 290 This section explains the use of a Fibre Channel management instance, 291 a Switch Index, and a Fabric Index. It also describes the four MIB 292 groups contained in the MIB. 294 5.1. Fibre Channel management instance 296 A Fibre Channel management instance is defined in [RFC4044] as a 297 separable managed instance of Fibre Channel functionality. Fibre 298 Channel functionality may be grouped into Fibre Channel management 299 instances in whatever way is most convenient for the 300 implementation(s). For example, one such grouping accommodates a 301 single SNMP agent having multiple AgentX [RFC2741] sub-agents, with 302 each sub-agent implementing a different Fibre Channel management 303 instance. 305 The object, fcmInstanceIndex, is IMPORTed from the FC-MGMT-MIB 306 [RFC4044] as the index value to uniquely identify each Fibre Channel 307 management instance, for example within the same SNMP context 308 ([RFC3411] section 3.3.1). 310 5.2. Switch Index 312 The FC-MGMT-MIB [RFC4044] defines the fcmSwitchTable as a table of 313 information about Fibre Channel switches which are managed by Fibre 314 Channel management instances. Each Fibre Channel management instance 315 can manage one or more Fibre Channel switches. The Switch Index, 316 fcmSwitchIndex, is IMPORTed from the FC-MGMT-MIB as the index value 317 to uniquely identify a Fibre Channel switch amongst those (one or 318 more) managed by the same Fibre Channel management instance. 320 5.3. Fabric Index 322 Whether operating on a physical Fabric (i.e., without Virtual 323 Fabrics) or within a Virtual Fabric, the manner of operation of RSCNs 324 within a/each Fabric is identical. Therefore, this MIB defines all 325 Fabric-related information in tables which are INDEX-ed by an 326 arbitrary integer, named a "Fabric Index", the syntax of which is 327 IMPORTed from the T11-TC-MIB [RFC4439]. When a device is connected 328 to a single physical Fabric, without use of any virtual Fabrics, the 329 value of this Fabric Index will always be 1. In an environment of 330 multiple virtual and/or physical Fabrics, this index provides a means 331 to distinguish one Fabric from another. 333 It is quite possible, and may even be likely, that a Fibre Channel 334 switch will have ports connected to multiple virtual and/or physical 335 Fabrics. Thus, in order to simplify a management protocol query 336 concerning all the Fabrics to which a single switch is connected, 337 fcmSwitchIndex will be listed before t11FcRscnFabricIndex when they 338 both appear in the same INDEX clause. 340 5.4. The t11FcRscnRegistrationGroup group 342 This group contains information about the Nx_Ports which have 343 registered to receive RSCNs. 345 5.5. The t11FcRscnNotifyGroup group 347 This group contains two notifications: one generated by when a switch 348 rejects a SCR or RSCN; the other when a switch rejects a SW_RSCN. 350 5.5.1. Flow-Control for Notifications 352 When defining SNMP notifications for events which occur in the data- 353 plane, the maximum frequency of their generation needs to be 354 considered. Unless there is some limiting factor, such notifications 355 need to be flow-controlled in some way, e.g., defined such that after 356 some maximum number within a specified time interval have occurred, 357 further notifications are suppressed for some subsequent time 358 interval. However, as and when such a suppression occurs, the NMS 359 which didn't receive the notifications (because they were suppressed) 360 needs to be able to obtain an indication of how many were suppressed. 361 Therefore, an additional Counter32 object needs to be defined, and/or 362 a new type of notification needs to be defined for use at the end of 363 the interval. While this is extra complexity, it is necessary for 364 notifications which need to be flow-controlled. 366 In contrast, for notifications such as both the ones defined in this 367 MIB module, which are generated due to control plane events (and are 368 not able to start a chain-reaction), the extra complexity of flow- 369 controlling these types of notifications is not warranted. 371 5.6. The t11FcRscnNotifyControlGroup group 373 This group contains one object for each notification in the 374 t11FcRscnNotifyGroup group to enable/disable that notification, as 375 well as three objects which record information about the latest 376 rejection of an SCR, RSCN or SW_RSCN, specifically, the content (if 377 available) of the rejected request, the source of the rejected 378 request, and the reason for the rejection. 380 5.7. The t11FcRscnStatsGroup group 382 This group contains RSCN-related statistics. Two levels of 383 statistics are included: 385 1) counters at the message-type level, for: 386 - the number of SCRs received/rejected, 387 - the number of RSCNs sent/received/rejected, 388 - the number of SW_RSCNs sent/received/rejected. 390 2) counters for each different category of sent/received RSCNs, 391 where different categories are indicated by different values of 392 the 'Event Qualifier' contained in an RSCN message. Note that 393 if and when several RSCN events are coalesced into a single RSCN 394 message, then that message may be counted in more than one of 395 these counters. No counters are defined in this MIB for the 396 'Event Qualifier' value of '0001'b (meaning "Changed Name Server 397 Object") because these types of RSCNs are counted by the 398 t11NsInRscns and t11NsOutRscns objects already defined in 399 [RFC4438]. 401 6. Definitions 403 6.1. The T11-FC-RSCN-MIB Module 405 T11-FC-RSCN-MIB DEFINITIONS ::= BEGIN 407 -- The Fibre Channel RSCN MIB 408 -- 409 -- for the monitoring of registrations by Nx_Ports to receive 410 -- Registered State Change Notifications (RSCNs), and the 411 -- monitoring of RSCN usage. 412 -- 414 IMPORTS 415 MODULE-IDENTITY, OBJECT-TYPE, 416 NOTIFICATION-TYPE, 417 Counter32, mib-2 FROM SNMPv2-SMI -- [RFC2578] 418 MODULE-COMPLIANCE, OBJECT-GROUP, 419 NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580] 420 TruthValue FROM SNMPv2-TC -- [RFC2579] 421 fcmInstanceIndex, fcmSwitchIndex, 422 FcNameIdOrZero, FcAddressIdOrZero FROM FC-MGMT-MIB -- [RFC4044] 423 T11NsGs4RejectReasonCode FROM T11-FC-NAME-SERVER-MIB -- [RFC4438] 424 T11FabricIndex FROM T11-TC-MIB; -- [RFC4439] 426 t11FcRscnMIB MODULE-IDENTITY 427 LAST-UPDATED "200609040000Z" 428 ORGANIZATION "T11 " 429 CONTACT-INFO 430 " Claudio DeSanti 431 Cisco Systems, Inc. 432 170 West Tasman Drive 433 San Jose, CA 95134 USA 434 Phone: +1 408 853-9172 435 EMail: cds@cisco.com 437 Keith McCloghrie 438 Cisco Systems, Inc. 439 170 West Tasman Drive 440 San Jose, CA USA 95134 441 Phone: +1 408-526-5260 442 Email: kzm@cisco.com" 444 DESCRIPTION 445 "The MIB module for the management of registrations 446 by Nx_Ports to receive RSCNs (Registered State Change 447 Notifications) on a Fibre Channel network, as defined 448 in FC-LS, and for the monitoring of RSCNs sent/received 449 or rejected in a Fibre Channel network. 451 Copyright (C) The Internet Society (2006). This version of 452 this MIB module is part of RFC yyyy; see the RFC itself for 453 full legal notices." 454 -- RFC Editor: replace yyyy with actual RFC number & remove this note 455 REVISION "200609040000Z" 456 DESCRIPTION 457 "Initial version of this MIB module, published as RFCyyyy." 458 -- RFC-Editor, replace yyyy with actual RFC number & remove this note 459 ::= { mib-2 nnn } -- to be assigned by IANA 460 -- RFC Editor: replace nnn with IANA-assigned number & remove this note 462 t11FcRscnNotifications OBJECT IDENTIFIER ::= { t11FcRscnMIB 0 } 463 t11FcRscnObjects OBJECT IDENTIFIER ::= { t11FcRscnMIB 1 } 464 t11FcRscnConformance OBJECT IDENTIFIER ::= { t11FcRscnMIB 2 } 465 t11FcRscnRegistrations OBJECT IDENTIFIER ::= { t11FcRscnObjects 1 } 466 t11FcRscnStats OBJECT IDENTIFIER ::= { t11FcRscnObjects 2 } 467 t11FcRscnInformation OBJECT IDENTIFIER ::= { t11FcRscnObjects 3 } 469 -- State Change Registration Table 471 t11FcRscnRegTable OBJECT-TYPE 472 SYNTAX SEQUENCE OF T11FcRscnRegEntry 473 MAX-ACCESS not-accessible 474 STATUS current 475 DESCRIPTION 476 "A table of Nx_Ports that have registered to receive 477 RSCNs on all fabrics configured on one or more Fibre 478 Channel switches." 479 ::= { t11FcRscnRegistrations 1 } 481 t11FcRscnRegEntry OBJECT-TYPE 482 SYNTAX T11FcRscnRegEntry 483 MAX-ACCESS not-accessible 484 STATUS current 485 DESCRIPTION 486 "An entry containing information about one Nx_Port which 487 has registered with a particular switch (identified by 488 values of fcmInstanceIndex and fcmSwitchIndex) for a 489 particular Fabric (identified by a t11FcRscnFabricIndex 490 value)." 491 INDEX { fcmInstanceIndex, fcmSwitchIndex, t11FcRscnFabricIndex, 492 t11FcRscnRegFcId } 493 ::= { t11FcRscnRegTable 1 } 495 T11FcRscnRegEntry ::= SEQUENCE { 496 t11FcRscnFabricIndex T11FabricIndex, 497 t11FcRscnRegFcId FcAddressIdOrZero, 498 t11FcRscnRegType BITS 499 } 501 t11FcRscnFabricIndex OBJECT-TYPE 502 SYNTAX T11FabricIndex 503 MAX-ACCESS not-accessible 504 STATUS current 505 DESCRIPTION 506 "An index value which uniquely identifies a particular 507 Fabric. 509 In a Fabric conformant to FC-SW-4, multiple Virtual Fabrics 510 can operate within one (or more) physical infrastructures. 511 In such a case, this index value is used to uniquely 512 identify a particular Fabric within a physical 513 infrastructure. 515 In a Fabric which has (can have) only a single Fabric 516 operating within the physical infrastructure, the 517 value of this Fabric Index will always be 1." 518 REFERENCE 519 "ANSI INCITS 418-2006, Fibre Channel - Switch Fabric - 4 520 (FC-SW-4), 2006." 521 ::= { t11FcRscnRegEntry 1 } 523 t11FcRscnRegFcId OBJECT-TYPE 524 SYNTAX FcAddressIdOrZero (SIZE (3)) 525 MAX-ACCESS not-accessible 526 STATUS current 527 DESCRIPTION 528 "The Fibre Channel Address Identifier (FC_ID) of the 529 registering Nx_Port." 530 ::= { t11FcRscnRegEntry 2 } 532 t11FcRscnRegType OBJECT-TYPE 533 SYNTAX BITS { 534 fromFabricController(0), 535 fromNxPort(1) 536 } 537 MAX-ACCESS read-only 538 STATUS current 539 DESCRIPTION 540 "This object indicates the type of registration 541 desired by the registering Nx_Port, one bit per type: 543 'fromFabricController' -- RSCNs generated for events 544 detected by the Fabric Controller. 546 'fromNxPorts' -- RSCNs generated for events 547 detected by the affected Nx_Port." 548 REFERENCE 549 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 550 (FC-LS), Rev 1.61, table 40, November 2006." 551 ::= { t11FcRscnRegEntry 3 } 553 -- Statistics 555 t11FcRscnStatsTable OBJECT-TYPE 556 SYNTAX SEQUENCE OF T11FcRscnStatsEntry 557 MAX-ACCESS not-accessible 558 STATUS current 559 DESCRIPTION 560 "The RSCN-related statistics on all fabrics configured 561 on one or more Fibre Channel switches. 563 Two levels of statistics are included: 565 1) counters at the message-type level, for: 566 - the number of SCRs received/rejected, 567 - the number of RSCNs sent/received/rejected, 568 - the number of SW_RSCNs sent/received/rejected. 570 2) counters of sent/received RSCNs per 'Event 571 Qualifier' value. Note that if and when several 572 RSCN events are coalesced into a single RSCN 573 message, then that message may be counted in 574 more than one of these counters." 575 ::= { t11FcRscnStats 1 } 577 t11FcRscnStatsEntry OBJECT-TYPE 578 SYNTAX T11FcRscnStatsEntry 579 MAX-ACCESS not-accessible 580 STATUS current 581 DESCRIPTION 582 "An entry containing statistics for a particular Fabric 583 (identified by a t11FcRscnFabricIndex value) on a particular 584 switch (identified by values of fcmInstanceIndex and 585 fcmSwitchIndex)." 586 INDEX { fcmInstanceIndex, fcmSwitchIndex, t11FcRscnFabricIndex } 587 ::= { t11FcRscnStatsTable 1 } 589 T11FcRscnStatsEntry ::= SEQUENCE { 590 t11FcRscnInScrs Counter32, 591 t11FcRscnInRscns Counter32, 592 t11FcRscnOutRscns Counter32, 593 t11FcRscnInSwRscns Counter32, 594 t11FcRscnOutSwRscns Counter32, 595 t11FcRscnScrRejects Counter32, 596 t11FcRscnRscnRejects Counter32, 597 t11FcRscnSwRscnRejects Counter32, 598 t11FcRscnInUnspecifiedRscns Counter32, 599 t11FcRscnOutUnspecifiedRscns Counter32, 600 t11FcRscnInChangedAttribRscns Counter32, 601 t11FcRscnOutChangedAttribRscns Counter32, 602 t11FcRscnInChangedServiceRscns Counter32, 603 t11FcRscnOutChangedServiceRscns Counter32, 604 t11FcRscnInChangedSwitchRscns Counter32, 605 t11FcRscnOutChangedSwitchRscns Counter32, 606 t11FcRscnInRemovedRscns Counter32, 607 t11FcRscnOutRemovedRscns Counter32 608 } 610 t11FcRscnInScrs OBJECT-TYPE 611 SYNTAX Counter32 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "The number of SCRs received from Nx_Ports 616 by this switch on this fabric. 618 This counter has no discontinuities other than 619 those that all Counter32s have when sysUpTime=0." 620 ::= { t11FcRscnStatsEntry 1 } 622 t11FcRscnInRscns OBJECT-TYPE 623 SYNTAX Counter32 624 MAX-ACCESS read-only 625 STATUS current 626 DESCRIPTION 627 "The number of RSCNs received from Nx_Ports 628 by this switch on this fabric. 630 This counter has no discontinuities other than 631 those that all Counter32s have when sysUpTime=0." 632 ::= { t11FcRscnStatsEntry 2 } 634 t11FcRscnOutRscns OBJECT-TYPE 635 SYNTAX Counter32 636 MAX-ACCESS read-only 637 STATUS current 638 DESCRIPTION 639 "The number of RSCNs transmitted to Nx_Ports 640 by this switch on this fabric. 642 This counter has no discontinuities other than 643 those that all Counter32s have when sysUpTime=0." 644 ::= { t11FcRscnStatsEntry 3 } 646 t11FcRscnInSwRscns OBJECT-TYPE 647 SYNTAX Counter32 648 MAX-ACCESS read-only 649 STATUS current 650 DESCRIPTION 651 "The number of SW_RSCNs received by this switch from 652 other switches on this fabric. 654 This counter has no discontinuities other than 655 those that all Counter32s have when sysUpTime=0." 656 ::= { t11FcRscnStatsEntry 4 } 658 t11FcRscnOutSwRscns OBJECT-TYPE 659 SYNTAX Counter32 660 MAX-ACCESS read-only 661 STATUS current 662 DESCRIPTION 663 "The number of SW_RSCNs transmitted by this switch 664 from other switches on this fabric. 666 This counter has no discontinuities other than 667 those that all Counter32s have when sysUpTime=0." 668 ::= { t11FcRscnStatsEntry 5 } 670 t11FcRscnScrRejects OBJECT-TYPE 671 SYNTAX Counter32 672 MAX-ACCESS read-only 673 STATUS current 674 DESCRIPTION 675 "The number of SCRs rejected by this switch on 676 this fabric. 678 This counter has no discontinuities other than 679 those that all Counter32s have when sysUpTime=0." 680 ::= { t11FcRscnStatsEntry 6 } 682 t11FcRscnRscnRejects OBJECT-TYPE 683 SYNTAX Counter32 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "The number of RSCNs rejected by this switch on this 688 fabric. 690 This counter has no discontinuities other than 691 those that all Counter32s have when sysUpTime=0." 692 ::= { t11FcRscnStatsEntry 7 } 694 t11FcRscnSwRscnRejects OBJECT-TYPE 695 SYNTAX Counter32 696 MAX-ACCESS read-only 697 STATUS current 698 DESCRIPTION 699 "The number of SW_RSCN rejected by this switch on this 700 fabric. 702 This counter has no discontinuities other than 703 those that all Counter32s have when sysUpTime=0." 704 ::= { t11FcRscnStatsEntry 8 } 706 t11FcRscnInUnspecifiedRscns OBJECT-TYPE 707 SYNTAX Counter32 708 MAX-ACCESS read-only 709 STATUS current 710 DESCRIPTION 711 "The number of Registered State Change Notifications 712 (RSCNs) received by this switch on this fabric which 713 contained an RSCN Event Qualifier value of '0000'b 714 meaning 'Event is not specified'. 716 This counter has no discontinuities other than 717 those that all Counter32s have when sysUpTime=0." 718 REFERENCE 719 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 720 (FC-LS), Rev 1.61, table 36, November 2006." 721 ::= { t11FcRscnStatsEntry 9 } 723 t11FcRscnOutUnspecifiedRscns OBJECT-TYPE 724 SYNTAX Counter32 725 MAX-ACCESS read-only 726 STATUS current 727 DESCRIPTION 728 "The number of Registered State Change Notifications 729 (RSCNs) sent by this switch on this fabric which 730 contained an RSCN Event Qualifier value of '0000'b 731 meaning 'Event is not specified'. 733 This counter has no discontinuities other than 734 those that all Counter32s have when sysUpTime=0." 735 REFERENCE 736 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 737 (FC-LS), Rev 1.61, table 36, November 2006." 738 ::= { t11FcRscnStatsEntry 10 } 740 t11FcRscnInChangedAttribRscns OBJECT-TYPE 741 SYNTAX Counter32 742 MAX-ACCESS read-only 743 STATUS current 744 DESCRIPTION 745 "The number of Registered State Change Notifications 746 (RSCNs) received by this switch on this fabric which 747 contained an RSCN Event Qualifier value of '0002'b 748 meaning 'Changed Port Attribute'. 750 This counter has no discontinuities other than 751 those that all Counter32s have when sysUpTime=0." 752 REFERENCE 753 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 754 (FC-LS), Rev 1.61, table 36, November 2006." 755 ::= { t11FcRscnStatsEntry 11 } 757 t11FcRscnOutChangedAttribRscns OBJECT-TYPE 758 SYNTAX Counter32 759 MAX-ACCESS read-only 760 STATUS current 761 DESCRIPTION 762 "The number of Registered State Change Notifications 763 (RSCNs) sent by this switch on this fabric which 764 contained an RSCN Event Qualifier value of '0002'b 765 meaning 'Changed Port Attribute'. 767 This counter has no discontinuities other than 768 those that all Counter32s have when sysUpTime=0." 769 REFERENCE 770 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 771 (FC-LS), Rev 1.61, table 36, November 2006." 772 ::= { t11FcRscnStatsEntry 12 } 774 t11FcRscnInChangedServiceRscns OBJECT-TYPE 775 SYNTAX Counter32 776 MAX-ACCESS read-only 777 STATUS current 778 DESCRIPTION 779 "The number of Registered State Change Notifications 780 (RSCNs) received by this switch on this fabric which 781 contained an RSCN Event Qualifier value of '0003'b 782 meaning 'Changed Service Object'. 784 This counter has no discontinuities other than 785 those that all Counter32s have when sysUpTime=0." 786 REFERENCE 787 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 788 (FC-LS), Rev 1.61, table 36, November 2006." 789 ::= { t11FcRscnStatsEntry 13 } 791 t11FcRscnOutChangedServiceRscns OBJECT-TYPE 792 SYNTAX Counter32 793 MAX-ACCESS read-only 794 STATUS current 795 DESCRIPTION 796 "The number of Registered State Change Notifications 797 (RSCNs) sent by this switch on this fabric which 798 contained an RSCN Event Qualifier value of '0003'b 799 meaning 'Changed Service Object'. 801 This counter has no discontinuities other than 802 those that all Counter32s have when sysUpTime=0." 803 REFERENCE 804 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 805 (FC-LS), Rev 1.61, table 36, November 2006." 806 ::= { t11FcRscnStatsEntry 14 } 808 t11FcRscnInChangedSwitchRscns OBJECT-TYPE 809 SYNTAX Counter32 810 MAX-ACCESS read-only 811 STATUS current 812 DESCRIPTION 813 "The number of Registered State Change Notifications 814 (RSCNs) received by this switch on this fabric which 815 contained an RSCN Event Qualifier value of '0004'b 816 meaning 'Changed Switch Configuration'. 818 This counter has no discontinuities other than 819 those that all Counter32s have when sysUpTime=0." 820 REFERENCE 821 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 822 (FC-LS), Rev 1.61, table 36, November 2006." 823 ::= { t11FcRscnStatsEntry 15 } 825 t11FcRscnOutChangedSwitchRscns OBJECT-TYPE 826 SYNTAX Counter32 827 MAX-ACCESS read-only 828 STATUS current 829 DESCRIPTION 830 "The number of Registered State Change Notifications 831 (RSCNs) sent by this switch on this fabric which 832 contained an RSCN Event Qualifier value of '0004'b 833 meaning 'Changed Switch Configuration'. 835 This counter has no discontinuities other than 836 those that all Counter32s have when sysUpTime=0." 837 REFERENCE 838 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 839 (FC-LS), Rev 1.61, table 36, November 2006." 840 ::= { t11FcRscnStatsEntry 16 } 842 t11FcRscnInRemovedRscns OBJECT-TYPE 843 SYNTAX Counter32 844 MAX-ACCESS read-only 845 STATUS current 846 DESCRIPTION 847 "The number of Registered State Change Notifications 848 (RSCNs) received by this switch on this fabric which 849 contained an RSCN Event Qualifier value of '0005'b 850 meaning 'Removed Object'. 852 This counter has no discontinuities other than 853 those that all Counter32s have when sysUpTime=0." 854 REFERENCE 855 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 856 (FC-LS), Rev 1.61, table 36, November 2006." 857 ::= { t11FcRscnStatsEntry 17 } 859 t11FcRscnOutRemovedRscns OBJECT-TYPE 860 SYNTAX Counter32 861 MAX-ACCESS read-only 862 STATUS current 863 DESCRIPTION 864 "The number of Registered State Change Notifications 865 (RSCNs) sent by this switch on this fabric which 866 contained an RSCN Event Qualifier value of '0005'b 867 meaning 'Removed Object'. 869 This counter has no discontinuities other than 870 those that all Counter32s have when sysUpTime=0." 871 REFERENCE 872 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 873 (FC-LS), Rev 1.61, table 36, November 2006." 874 ::= { t11FcRscnStatsEntry 18 } 876 -- 877 -- Notification Control Table 878 -- 879 t11FcRscnNotifyControlTable OBJECT-TYPE 880 SYNTAX SEQUENCE OF T11FcRscnNotifyControlEntry 881 MAX-ACCESS not-accessible 882 STATUS current 883 DESCRIPTION 884 "A table of control information for notifications 885 generated due to the rejection of an SCR or RSCN." 886 ::= { t11FcRscnInformation 1 } 888 t11FcRscnNotifyControlEntry OBJECT-TYPE 889 SYNTAX T11FcRscnNotifyControlEntry 890 MAX-ACCESS not-accessible 891 STATUS current 892 DESCRIPTION 893 "Each entry contains notification control information 894 concerning the rejection of RSCN/SCRs for a particular 895 fabric (identified by the value of t11FcRscnFabricIndex) 896 by a particular switch (identified by values of 897 fcmInstanceIndex and fcmSwitchIndex)." 898 INDEX { fcmInstanceIndex, fcmSwitchIndex, t11FcRscnFabricIndex } 899 ::= { t11FcRscnNotifyControlTable 1 } 901 T11FcRscnNotifyControlEntry ::= SEQUENCE { 902 t11FcRscnIlsRejectNotifyEnable TruthValue, 903 t11FcRscnElsRejectNotifyEnable TruthValue, 904 t11FcRscnRejectedRequestString OCTET STRING, 905 t11FcRscnRejectedRequestSource FcNameIdOrZero, 906 t11FcRscnRejectReasonCode T11NsGs4RejectReasonCode, 907 t11FcRscnRejectReasonCodeExp OCTET STRING, 908 t11FcRscnRejectReasonVendorCode OCTET STRING 909 } 911 t11FcRscnIlsRejectNotifyEnable OBJECT-TYPE 912 SYNTAX TruthValue 913 MAX-ACCESS read-write 914 STATUS current 915 DESCRIPTION 916 "This object specifies if a t11FcRscnIlsRejectReqNotify 917 notification should be generated when this switch 918 rejects an SW_RSCN on this fabric. 920 Values written to this object should be retained 921 over agent reboots." 922 DEFVAL { false } 923 ::= { t11FcRscnNotifyControlEntry 1 } 925 t11FcRscnElsRejectNotifyEnable OBJECT-TYPE 926 SYNTAX TruthValue 927 MAX-ACCESS read-write 928 STATUS current 929 DESCRIPTION 930 "This object specifies if a t11FcRscnElsRejectReqNotify 931 notification should be generated when this switch 932 rejects an RSCN or SCR on this fabric. 934 Values written to this object should be retained 935 over agent reboots." 937 DEFVAL { false } 938 ::= { t11FcRscnNotifyControlEntry 2 } 940 t11FcRscnRejectedRequestString OBJECT-TYPE 941 SYNTAX OCTET STRING (SIZE (0..255)) 942 MAX-ACCESS read-only 943 STATUS current 944 DESCRIPTION 945 "The binary content of the RSCN or SCR or SW_RSCN which 946 was most recently rejected by this switch on this fabric. 947 The value is formatted as an octet string (in network 948 byte order) as described in the relevant Fibre Channel 949 standard, containing the payload (which is typically a 950 list of affected ports and error codes) of the rejected 951 RSCN or SCR as described in FC-LS, or the rejected 952 SW_RSCN as described in FC-SW-4. 954 This object contains the zero-length string if and when 955 the RSCN/SCR/SW_RSCN payload is unavailable. When the 956 length of this object is 255 octets, it contains the 957 first 255 octets of the payload (in network-byte order)." 958 REFERENCE 959 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 960 (FC-LS), Rev 1.61, tables 34 & 39, November 2006. 962 ANSI INCITS 418-2006, Fibre Channel - Switch Fabric - 4 963 (FC-SW-4), 2006, table 45." 964 ::= { t11FcRscnNotifyControlEntry 3 } 966 t11FcRscnRejectedRequestSource OBJECT-TYPE 967 SYNTAX FcNameIdOrZero 968 MAX-ACCESS read-only 969 STATUS current 970 DESCRIPTION 971 "The WWN which was the source of the RSCN, SCR or 972 SW_RSCN which was most recently rejected by this switch 973 on this fabric." 974 ::= { t11FcRscnNotifyControlEntry 4 } 976 t11FcRscnRejectReasonCode OBJECT-TYPE 977 SYNTAX T11NsGs4RejectReasonCode 978 MAX-ACCESS read-only 979 STATUS current 980 DESCRIPTION 981 "This object contains the Reason Code of the most recent 982 rejection by this switch of an RSCN, SCR or SW_RSCN on 983 this fabric." 984 REFERENCE 985 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 986 (FC-LS), Rev 1.61, table 146, November 2006. 988 ANSI INCITS 418-2006, Fibre Channel - Switch Fabric - 4 989 (FC-SW-4), 2006, table 5." 990 ::= { t11FcRscnNotifyControlEntry 5 } 992 t11FcRscnRejectReasonCodeExp OBJECT-TYPE 993 SYNTAX OCTET STRING (SIZE(1)) 994 MAX-ACCESS read-only 995 STATUS current 996 DESCRIPTION 997 "This object contains the Reason Code Explanation 998 of the most recent rejection by this switch of an 999 RSCN, SCR or SW_RSCN on this fabric." 1000 REFERENCE 1001 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 1002 (FC-LS), Rev 1.61, table 147, November 2006. 1004 ANSI INCITS 418-2006, Fibre Channel - Switch Fabric - 4 1005 (FC-SW-4), 2006, table 6." 1006 ::= { t11FcRscnNotifyControlEntry 6 } 1008 t11FcRscnRejectReasonVendorCode OBJECT-TYPE 1009 SYNTAX OCTET STRING (SIZE(1)) 1010 MAX-ACCESS read-only 1011 STATUS current 1012 DESCRIPTION 1013 "This object contains the Reason Vendor Specific 1014 Code of the most recent rejection by this switch 1015 of an RSCN, SCR or SW_RSCN on this fabric." 1016 REFERENCE 1017 "ANSI INCITS xxx-200n, Fibre Channel - Link Services 1018 (FC-LS), Rev 1.61, table 148, November 2006. 1020 ANSI INCITS 418-2006, Fibre Channel - Switch Fabric - 4 1021 (FC-SW-4), 2006, section 6.1.3." 1022 ::= { t11FcRscnNotifyControlEntry 7 } 1024 -- Notifications 1025 t11FcRscnElsRejectReqNotify NOTIFICATION-TYPE 1026 OBJECTS { t11FcRscnRejectedRequestString, 1027 t11FcRscnRejectedRequestSource, 1028 t11FcRscnRejectReasonCode, 1029 t11FcRscnRejectReasonCodeExp, 1030 t11FcRscnRejectReasonVendorCode } 1031 STATUS current 1032 DESCRIPTION 1033 "This notification is generated when a switch rejects 1034 an SCR or RSCN. 1036 The value of t11FcRscnRejectedRequestString indicates the 1037 binary content of the rejected request if available, or 1038 the zero-length string otherwise. The source of the 1039 rejected request is given by t11FcRscnRejectedRequestSource, 1040 and the reason for rejection is given by the values of 1041 t11FcRscnRejectReasonCode, t11FcRscnRejectReasonCodeExp 1042 and t11FcRscnRejectReasonVendorCode." 1043 ::= { t11FcRscnNotifications 1 } 1045 t11FcRscnIlsRejectReqNotify NOTIFICATION-TYPE 1046 OBJECTS { t11FcRscnRejectedRequestString, 1047 t11FcRscnRejectedRequestSource, 1048 t11FcRscnRejectReasonCode, 1049 t11FcRscnRejectReasonCodeExp, 1050 t11FcRscnRejectReasonVendorCode } 1051 STATUS current 1052 DESCRIPTION 1053 "This notification is generated when a switch rejects 1054 an SW_RSCN. 1056 The value of t11FcRscnRejectedRequestString indicates the 1057 binary content of the rejected request if available, or 1058 the zero-length string otherwise. The source of the 1059 rejected request is given by t11FcRscnRejectedRequestSource, 1060 and the reason for rejection is given by the values of 1061 t11FcRscnRejectReasonCode, t11FcRscnRejectReasonCodeExp 1062 and t11FcRscnRejectReasonVendorCode." 1063 ::= { t11FcRscnNotifications 2 } 1065 -- Conformance 1066 t11FcRscnCompliances OBJECT IDENTIFIER ::= { t11FcRscnConformance 1 } 1067 t11FcRscnGroups OBJECT IDENTIFIER ::= { t11FcRscnConformance 2 } 1069 t11FcRscnCompliance MODULE-COMPLIANCE 1070 STATUS current 1071 DESCRIPTION 1072 "The compliance statement for entities which implement 1073 this MIB." 1074 MODULE 1075 MANDATORY-GROUPS { t11FcRscnRegistrationGroup, 1076 t11FcRscnNotifyControlGroup, 1077 t11FcRscnNotifyGroup } 1079 GROUP t11FcRscnStatsGroup 1080 DESCRIPTION 1081 "These counters, containing RSCN-related statistics, are 1082 mandatory only for those systems which count such events." 1084 OBJECT t11FcRscnIlsRejectNotifyEnable 1085 MIN-ACCESS read-only 1086 DESCRIPTION 1087 "Write access is not required." 1089 OBJECT t11FcRscnElsRejectNotifyEnable 1090 MIN-ACCESS read-only 1091 DESCRIPTION 1092 "Write access is not required." 1094 ::= { t11FcRscnCompliances 1 } 1096 -- Units of conformance 1098 t11FcRscnRegistrationGroup OBJECT-GROUP 1099 OBJECTS { t11FcRscnRegType } 1100 STATUS current 1101 DESCRIPTION 1102 "A collection of objects for monitoring RSCN 1103 registrations." 1104 ::= { t11FcRscnGroups 1 } 1106 t11FcRscnStatsGroup OBJECT-GROUP 1107 OBJECTS { t11FcRscnInScrs, 1108 t11FcRscnInRscns, 1109 t11FcRscnOutRscns, 1110 t11FcRscnInSwRscns, 1111 t11FcRscnOutSwRscns, 1112 t11FcRscnScrRejects, 1113 t11FcRscnRscnRejects, 1114 t11FcRscnSwRscnRejects, 1115 t11FcRscnInUnspecifiedRscns, 1116 t11FcRscnOutUnspecifiedRscns, 1117 t11FcRscnInChangedAttribRscns, 1118 t11FcRscnOutChangedAttribRscns, 1119 t11FcRscnInChangedServiceRscns, 1120 t11FcRscnOutChangedServiceRscns, 1121 t11FcRscnInChangedSwitchRscns, 1122 t11FcRscnOutChangedSwitchRscns, 1123 t11FcRscnInRemovedRscns, 1124 t11FcRscnOutRemovedRscns 1125 } 1126 STATUS current 1127 DESCRIPTION 1128 "A collection of objects for collecting RSCN-related 1129 statistics." 1130 ::= { t11FcRscnGroups 2 } 1132 t11FcRscnNotifyControlGroup OBJECT-GROUP 1133 OBJECTS { t11FcRscnIlsRejectNotifyEnable, 1134 t11FcRscnElsRejectNotifyEnable, 1135 t11FcRscnRejectedRequestString, 1136 t11FcRscnRejectedRequestSource, 1137 t11FcRscnRejectReasonCode, 1138 t11FcRscnRejectReasonCodeExp, 1139 t11FcRscnRejectReasonVendorCode 1140 } 1141 STATUS current 1142 DESCRIPTION 1143 "A collection of notification control and 1144 notification information objects." 1145 ::= { t11FcRscnGroups 3 } 1147 t11FcRscnNotifyGroup NOTIFICATION-GROUP 1148 NOTIFICATIONS { t11FcRscnIlsRejectReqNotify, 1149 t11FcRscnElsRejectReqNotify 1150 } 1151 STATUS current 1152 DESCRIPTION 1153 "A collection of notifications for monitoring 1154 ILS and ELS rejections by the RSCN module." 1155 ::= { t11FcRscnGroups 4 } 1157 END 1158 7. Acknowledgements 1160 This document was originally developed and approved by the INCITS 1161 Task Group T11.5 (http://www.t11.org) as the SM-RSCNM project. We 1162 wish to acknowledge the many contributions and comments from the 1163 INCITS Technical Committee T11, including the following: 1165 T11 Chair: Robert Snively, Brocade 1166 T11 Vice Chair: Claudio DeSanti, Cisco Systems 1167 T11.5 Chair: Roger Cummings, Symantec 1168 T11.5 Vice Chair: Scott Kipp, McData 1169 and T11.5 members. 1171 The document was subsequently a work item of the IETF's IMSS Working 1172 Group, chaired by David Black (EMC Corporation). We thank Bert 1173 Wijnen (Lucent Technologies) for his thorough review of the document. 1174 We also wish to acknowledge Dan Romascanu (Avaya), the IETF Area 1175 Director, for his comments and assistance. 1177 8. Normative References 1179 [RFC2578] 1180 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1181 and S. Waldbusser, "Structure of Management Information Version 2 1182 (SMIv2)", STD 58, RFC 2578, April 1999. 1184 [RFC2579] 1185 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1186 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 1187 2579, April 1999. 1189 [RFC2580] 1190 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 1191 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 1192 2580, April 1999. 1194 [RFC3411] 1195 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1196 Describing Simple Network Management Protocol (SNMP) Management 1197 Frameworks", STD 58, RFC 3411, December 2002. 1199 [IF-MIB] 1200 McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB", RFC 1201 2863, June 2000. 1203 [RFC4044] 1204 K. McCloghrie, "Fibre Channel Management MIB", RFC 4044, May 2005. 1206 [RFC4438] 1207 DeSanti, C., Gaonkar, V., Vivek, H.K., McCloghrie, K., and S. Gai, 1208 "Fibre-Channel Name Server MIB", RFC 4438, March 2006. 1210 [RFC4439] 1211 DeSanti, C., Gaonkar, V., McCloghrie, K., and S. Gai, "Fibre- 1212 Channel Fabric Address Manager MIB", RFC 4439, March 2006. 1214 [FC-SW-4] 1215 "Fibre Channel - Switch Fabric - 4 (FC-SW-4)", ANSI INCITS 1216 418-2006, http://www.t11.org/t11/stat.nsf/upnum/1674-d, 2006. 1218 [FC-FS] 1219 "Fibre Channel - Framing and Signaling (FC-FS)", ANSI INCITS 1220 373-2003, http://www.t11.org/t11/stat.nsf/upnum/1331-d, April 2003. 1222 [FC-LS] 1223 "Fibre Channel - Link Services (FC-LS)", ANSI INCITS xxx-200n, Rev 1224 1.61, http://www.t11.org/t11/stat.nsf/upnum/1620-d, November 2006. 1226 -- RFC-Editor: the "xxx-200n" above (and in earlier REFERENCE clauses) 1227 -- needs to be replaced with the document's number, which is expected 1228 -- to be assigned in the coming months. 1230 [RFC2119] 1231 Bradner, S., "Key words for use in RFCs to Indicate Requirement 1232 Levels", BCP 14, RFC 2119, March 1997. 1234 9. Informative References 1236 [RFC2741] 1237 Daniele, M., Wijnen, B., Ellison, M., and D. Francisco, "Agent 1238 Extensibility (AgentX) Protocol Version 1", RFC 2741, January 2000. 1240 [RFC2837] 1241 Teow, K., "Definitions of Managed Objects for the Fabric Element in 1242 Fibre Channel Standard", RFC 2837, May 2000. 1244 [RFC3410] 1245 Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and 1246 Applicability Statements for Internet-Standard Management 1247 Framework", RFC 3410, December 2002. 1249 10. IANA Considerations 1251 IANA is requested to make a MIB OID assignment for the 1252 T11-FC-RSCN-MIB module, under the appropriate subtree. 1254 11. Security Considerations 1256 There are a number of management objects defined in this MIB module 1257 with a MAX-ACCESS clause of read-write and/or read-create. Such 1258 objects may be considered sensitive or vulnerable in some network 1259 environments. The support for SET operations in a non-secure 1260 environment without proper protection can have a negative effect on 1261 network operations. These objects and their 1262 sensitivity/vulnerability are: 1264 t11FcRscnIlsRejectNotifyEnable 1265 t11FcRscnElsRejectNotifyEnable 1266 -- ability to enable/disable a notification; these object, if 1267 misconfigured, would either generate unwanted notifications 1268 or suppress wanted notifications. 1270 Some of the readable objects in this MIB module (i.e., objects with a 1271 MAX-ACCESS other than not-accessible) may also be considered 1272 sensitive or vulnerable in some network environments. It is thus 1273 important to control even GET and/or NOTIFY access to these objects 1274 and possibly to even encrypt the values of these objects when sending 1275 them over the network via SNMP. These are the tables and objects and 1276 their sensitivity/vulnerability: 1278 t11FcRscnRegTable -- contains a list of Nx_Ports which are 1279 currently registered to received RSCNs. 1281 t11FcRscnStatsTable -- contains RSCN-related statistics. 1283 t11FcRscnNotifyControlTable -- contains control and logging 1284 information for notifications which are concerned with the 1285 rejection of RSCN-related requests. 1287 SNMP versions prior to SNMPv3 did not include adequate security. 1288 Even if the network itself is secure (for example by using IPsec), 1289 even then, there is no control as to who on the secure network is 1290 allowed to access and GET/SET (read/change/create/delete) the objects 1291 in this MIB module. 1293 It is RECOMMENDED that implementors consider the security features as 1294 provided by the SNMPv3 framework (see [RFC3410], section 8), 1295 including full support for the SNMPv3 cryptographic mechanisms (for 1296 authentication and privacy). 1298 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1299 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1300 enable cryptographic security. It is then a customer/operator 1301 responsibility to ensure that the SNMP entity giving access to an 1302 instance of this MIB module is properly configured to give access to 1303 the objects only to those principals (users) that have legitimate 1304 rights to indeed GET or SET (change/create/delete) them. 1306 12. Authors' Addresses 1308 Claudio DeSanti 1309 Cisco Systems, Inc. 1310 170 West Tasman Drive 1311 San Jose, CA 95134 USA 1312 Phone: +1 408 853-9172 1313 EMail: cds@cisco.com 1315 H.K. Vivek 1316 Cisco Systems, Inc. 1317 71 Millers Rd 1318 Bangalore, India 1319 Phone: +91 80 2289933x5117 1320 EMail: hvivek@cisco.com 1322 Keith McCloghrie 1323 Cisco Systems, Inc. 1324 170 West Tasman Drive 1325 San Jose, CA USA 95134 1326 Phone: +1 408-526-5260 1327 Email: kzm@cisco.com 1329 Silvano Gai 1330 Retired 1332 Full Copyright Statement 1334 Copyright (C) The Internet Society (2006). This document is subject 1335 to the rights, licenses and restrictions contained in BCP 78, and 1336 except as set forth therein, the authors retain all their rights. 1338 This document and the information contained herein are provided on an 1339 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1340 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1341 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1342 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1343 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1344 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1346 Disclaimer of validity 1348 The IETF takes no position regarding the validity or scope of any 1349 Intellectual Property Rights or other rights that might be claimed to 1350 pertain to the implementation or use of the technology described in 1351 this document or the extent to which any license under such rights 1352 might or might not be available; nor does it represent that it has 1353 made any independent effort to identify any such rights. Information 1354 on the procedures with respect to rights in RFC documents can be 1355 found in BCP 78 and BCP 79. 1357 Copies of IPR disclosures made to the IETF Secretariat and any 1358 assurances of licenses to be made available, or the result of an 1359 attempt made to obtain a general license or permission for the use of 1360 such proprietary rights by implementers or users of this 1361 specification can be obtained from the IETF on-line IPR repository at 1362 http://www.ietf.org/ipr. 1364 The IETF invites any interested party to bring to its attention any 1365 copyrights, patents or patent applications, or other proprietary 1366 rights that may cover technology that may be required to implement 1367 this standard. Please address the information to the IETF at 1368 ietf-ipr@ietf.org. 1370 Acknowledgment 1372 Funding for the RFC Editor function is currently provided by the 1373 Internet Society.