idnits 2.17.1 draft-ietf-imss-fc-zs-mib-03.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 15. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 4074. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 4085. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 4092. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 4098. ** 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. 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 : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. 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 (24 January 2007) is 6299 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-GS-5' -- Possible downref: Non-RFC (?) normative reference: ref. 'FC-GS-4' -- 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. 'APPL-ID' Summary: 3 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 H.K. Vivek 3 K. McCloghrie 4 Cisco Systems 5 S. Gai 6 24 January 2007 7 Fibre-Channel Zone Server MIB 8 draft-ietf-imss-fc-zs-mib-03.txt 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 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.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Abstract 35 This memo defines a portion of the Management Information Base (MIB) 36 for use with network management protocols in the Internet community. 37 In particular, it describes managed objects for information related 38 to a Fibre Channel Zone Server. 40 Table of Contents 42 1 Introduction ................................................. 3 43 1.1 Change Log ................................................. 3 44 2 The Internet-Standard Management Framework ................... 7 45 3 Overview of Fibre Channel .................................... 7 46 3.1 General Overview ........................................... 8 47 3.2 Zoning ..................................................... 8 48 3.3 Zoning Configuration and Management ........................ 9 49 4 Relationship to Other MIBs ................................... 12 50 5 MIB Overview ................................................. 12 51 5.1 Fibre Channel management instance .......................... 12 52 5.2 Switch Index ............................................... 13 53 5.3 Fabric Index ............................................... 13 54 5.4 Locking the Fabric ......................................... 13 55 5.5 Basic and Enhanced Modes ................................... 14 56 5.6 Persistent Storage ......................................... 15 57 5.7 The Active Zone Set and the Zone Set Database .............. 15 58 5.8 Conformance Groups ......................................... 16 59 6 The T11-FC-FABRIC-LOCK-MIB Module ............................ 18 60 7 The T11-FC-ZONE-SERVER-MIB Module ............................ 29 61 8 Acknowledgements ............................................. 88 62 9 Normative References ......................................... 88 63 10 Informative References ...................................... 90 64 11 IANA Considerations ......................................... 90 65 12 Security Considerations ..................................... 90 66 13 Authors' Addresses .......................................... 92 68 1. Introduction 70 This memo defines a portion of the Management Information Base (MIB) 71 for use with network management protocols in the Internet community. 72 In particular, it describes managed objects for information related 73 to a Fibre Channel network's Zone Server. 75 This memo was previously approved by T11.5 (http://www.t11.org); it 76 is currently a work item of the IETF's IMSS working group. 78 This memo includes boilerplate which uses only one of the following 79 terms, but is nevertheless required to mention all of the keywords in 80 the following statement: 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 83 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" 84 in this document are to be interpreted as described in BCP 14, RFC 85 2119 [RFC2119]. 87 1.1. Change Log 89 This section to be deleted before publication as an RFC. 91 1.1.1. Initial version 93 The initial version was submitted to T11.5 as T11/05-505v0 on 25 July 94 2005. 96 1.1.2. Changes made in 19 January version 98 The following changes were made for the version dated 19 January 99 2006, which was submitted to T11.5 as: T11/06-047v0. 101 - The MIB module for GS Server Sessions (T11-GS-SESSIONS-MIB) was 102 changed to be the MIB module for Fibre Channel Fabric locks 103 (T11-FC-FABRIC-LOCK-MIB). The t11GssSessionTable table was changed 104 to be the t11FLockTable table, and the INDEX-ing changed to include 105 GS_Type and GS_SubType values. 107 - Three reason code objects were added to the t11FLockTable to hold 108 the reason code, the reason code explanation, and the reason vendor 109 code if and when a lock request is rejected by an SW_RJT. 111 - The ability to commit Zone changes (which was in 112 t11GssSessionTable) was not included in the t11FLockTable. 113 Instead, it was added as a new object, t11ZsServerCommit, in the 114 T11-FC-ZONE-SERVER-MIB. 116 - The descriptions of t11ZsTxChangeRequests, t11ZsRxChangeAccepts, 117 t11ZsRxChangeRequests & t11ZsTxChangeAccepts were clarified to 118 indicate they include Enhanced Commit Service requests/responses, 119 and that they include requests/responses in both Basic & Enhanced 120 modes. 122 - t11ZsServerDistributeFailReason was replaced by three objects 123 t11ZsServerReasonCode, t11ZsServerReasonCodeExp and 124 t11ZsServerReasonVendorCode to contain the individual codes 125 separately. 127 - t11ZsRejectReasonVendorCode was added in the 128 t11ZsNotifyControlTable and as an additional object in the 129 t11ZsRequestRejectNotify notification. 131 - t11ZsRxGS5Requests and t11ZsTxGS5Rejects were renamed to 132 t11ZsRxZsRequests and t11ZsTxZsRejects, their descriptions updated 133 to be described as Zone Server requests/responses (rather than GS-5 134 requests/responses). 136 1.1.3. Changes made in 5 March version 138 The following changes were made for the version which was submitted 139 to T11.5 as: T11/06-047v1, and to the IETF as: 140 draft-kzm-imss-fc-zs-mib-03.txt. 142 - Updated the DESCRIPTION of the t11FLockTable to mention locks via 143 ACAs and locks via EACAs. 145 - Defined the t11FLockApplicationID to be used in the INDEX clause of 146 the t11FLockTable, replacing t11FLockGsType and t11FLockGsSubType 147 (which get deleted). 149 - Changed the 'gsClient' label of the t11FLockInitiatorType object to 150 'ssb' so as to accommodate FC-SP clients as well as GS-5 clients. 152 - Changed "Rx" to "In" and "Tx" to "Out" in the descriptors of 153 Counter32's, e.g., changed t11ZsRxZsRequests to t11ZsInZsRequests. 155 - Many editorial changes. 157 1.1.4. 14 August 2006 version 159 The following changes were made for the version was submitted to the 160 IETF as: draft-ietf-imss-fc-zs-mib-00.txt. 162 - Updated to use the assignment of 'D0'h (208 decimal) as the 163 (pseudo) Application ID value as and when a Fabric is locked via an 164 ACA request. This value is used to distinguish such a lock in the 165 t11FLockTable from those established via EACA requests (which are 166 defined to have an explicit Application ID). 168 - Changes to indicate the adoption of this memo as a work item of the 169 IMSS Working Group. 171 - Added explicit statement to all Counter32's that they have no 172 discontinuities other than those that all Counter32s have when 173 sysUpTime=0. 175 - Updated references to FC-SW-4 to point at "ANSI INCITS 418-2006". 177 1.1.5. 16 October 2006 version 179 The following changes were made for the version was submitted to the 180 IETF as: draft-ietf-imss-fc-zs-mib-01.txt. 182 - Updated the value of the (pseudo) Application_ID assigned to this 183 MIB module, for use when a Fabric is locked via an ACA request, to 184 be x'FF' (255). Added a paragraph in the Overview section 185 explaining the use of this pseudo Application_ID value and 186 including a reference to the T11-approved letter documenting the 187 assignment. 189 - Moved Copyright from one DESCRIPTION to another DESCRIPTION. 191 - Changed "IPSec" to "IPsec'. 193 - In T11ZoningName, change "letter" to "ASCII letter". 195 - Omitted "Short" from Section 3's title. Divided section 3 up into 196 several sub-sections with appropriate titles. Added a couple of 197 paragraphs to the explanation of what a zone does and how it's 198 enforced. 200 - Added a DISPLAY-HINT for T11ZsZoneMemberType. 202 - Added a section on why the notifications don't need to be flow- 203 controlled. 205 - Changed the value of t11FLockInitiator, which corresponds to 206 t11FLockInitiatorType's value of 'snmp', to be an SNMP 207 securityName. 209 - Added two new objects: t11FLockInitiatorIpAddrType and 210 t11FLockInitiatorIpAddr to hold the IP address, if applicable and 211 known, of the initiator. 213 - Expanded the DESCRIPTION of t11FLockTable to better explain when 214 rows in this table exist, and that they are not retained over 215 restarts. 217 - Changed 'rejected' to be 'rejectFailure' in 218 t11FLockRejectReasonCode, t11FLockRejectReasonCodeExp and 219 t11FLockRejectReasonVendorCode. 221 - Changed the syntax of t11FLockRejectReasonCodeExp and 222 t11FLockRejectReasonVendorCode to allow a zero-length string. 224 - Changed the descriptors for two objects: t11ZsActiveBroadcast to 225 t11ZsActiveZoneBroadcastZoning, and t11ZsActiveHardZoning to 226 t11ZsActiveZoneHardZoning. 228 - Added text to the DESCRIPTIONs of the t11ZsSetZoneTable, 229 t11ZsZoneMemberTable and t11ZsAttribBlockTable explaining their 230 fate-sharing relationships with other tables. 232 - Fixed several typos. 234 1.1.6. 8 January 2007 version 236 The following changes were made for the version was submitted to the 237 IETF as: draft-ietf-imss-fc-zs-mib-02.txt. 239 - Inserted references to FC-SW-5 to replace the "TBD" for the 240 reference to the assignment of an Application_ID value for the 241 benefit of this MIB module. 243 - fixed typos. 245 - added IETF IMSS WG to the ORGANIZATION clause. 247 - Changed year in copyright dates to 2007. 249 - Included a reference to RFC 3584. 251 - Updated the SIZE clause of t11ZsActiveAttribValue. 253 - Included a statement in t11ZsNotifyControlEntry on the persistency 254 of read-write data in rows of the t11ZsNotifyControlTable. 256 - Removed the statement specifying the meaning of non-instantiated 257 instances of t11FLockInitiatorIpAddrType & t11FLockInitiatorIpAddr, 258 and clarified the meaning of "request" in the DESCRIPTION of 259 t11FLockInitiatorIpAddr. 261 1.1.7. 24 January 2007 version 263 The following changes were made for the version was submitted to the 264 IETF as: draft-ietf-imss-fc-zs-mib-03.txt. 266 - Removed all references to the incomplete FC-SW-5 specification so 267 that this document can proceed without delay. 269 2. The Internet-Standard Management Framework 271 For a detailed overview of the documents that describe the current 272 Internet-Standard Management Framework, please refer to section 7 of 273 RFC 3410 [RFC3410]. 275 Managed objects are accessed via a virtual information store, termed 276 the Management Information Base or MIB. MIB objects are generally 277 accessed through the Simple Network Management Protocol (SNMP). 278 Objects in the MIB are defined using the mechanisms defined in the 279 Structure of Management Information (SMI). This memo specifies a MIB 280 module that is compliant to the SMIv2, which is described in STD 58, 281 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 282 [RFC2580]. 284 3. Overview of Fibre Channel 285 3.1. General Overview 287 The Fibre Channel (FC) is logically a bidirectional point-to-point 288 serial data channel, structured for high performance. Fibre Channel 289 provides a general transport vehicle for higher level protocols such 290 as Small Computer System Interface (SCSI) command sets, the High- 291 Performance Parallel Interface (HIPPI) data framing, IP (Internet 292 Protocol), IEEE 802.2, and others. 294 Physically, Fibre Channel is an interconnection of multiple 295 communication points, called N_Ports, interconnected either by a 296 switching network, called a fabric, or by a point-to-point link. A 297 Fibre Channel "node" consists of one or more N_Ports. A fabric may 298 consist of multiple Interconnect Elements, some of which are 299 switches. An N_Port connects to the fabric via a port on a switch 300 called an F_Port. When multiple FC nodes are connected to a single 301 port on a switch via an "Arbitrated Loop" topology, the switch port 302 is called an FL_Port, and the nodes' ports are called NL_Ports. The 303 term Nx_Port is used to refer to either an N_Port or an NL_Port. The 304 term Fx_Port is used to refer to either an F_Port or an FL_Port. A 305 switch port, which is interconnected to another switch port via an 306 Inter-Switch Link (ISL), is called an E_Port. A B_Port connects a 307 bridge device with an E_Port on a switch; a B_Port provides a subset 308 of E_Port functionality. 310 Many Fibre Channel components, including the fabric, each node, and 311 most ports, have globally-unique names. These globally-unique names 312 are typically formatted as World Wide Names (WWNs). More information 313 on WWNs can be found in [FC-FS]. WWNs are expected to be persistent 314 across agent and unit resets. 316 Fibre Channel frames contain 24-bit address identifiers which 317 identify the frame's source and destination ports. Each FC port has 318 both an address identifier and a WWN. For an Nx_Port, its WWN is 319 called a N_Port_Name and its address identifier is called a 320 N_Port_ID. When a fabric is in use, the FC address identifiers are 321 dynamic and are assigned by a switch. Each octet of a 24-bit address 322 represents a level in an address hierarchy, with a Domain_ID being 323 the highest level of the hierarchy. 325 3.2. Zoning 327 Zones within a fabric provide a mechanism to control frame delivery 328 between Nx_Ports ("Hard Zoning") or to expose selected views of Name 329 Server information ("Soft Zoning"). 331 Communication is only possible when the communicating endpoints are 332 members of a common zone. This technique is similar to virtual 333 private networks in that the fabric has the ability to group devices 334 into Zones. 336 Hard zoning and soft zoning are two different means of realizing 337 this. Hard zoning is enforced in the fabric (i.e., switches) whereas 338 soft zoning is enforced at the endpoints (e.g., HBAs) by relying on 339 the endpoints to not send traffic to an N_Port_ID not obtained from 340 the Name Server with a few exceptions for well known N_Port_IDs used 341 to bootstrap the fabric (e.g., talk to the Name Server). 343 Administrators create Zones to increase network security, and prevent 344 data loss or corruption, by controlling access between devices or 345 user groups. Zones may be specifically used to create: 347 a) Barriers between devices that use different operating systems. 348 It is often critical to separate servers and storage devices 349 with different operating systems because accidental transfer of 350 information from one to another may delete or corrupt data; 352 b) Logical subsets of closed user groups. Administrators may 353 authorize access rights to specific Zones for specific user 354 groups, thereby protecting confidential data from unauthorized 355 access; 357 c) Groups of devices that are separate from devices in the rest of 358 a fabric. Zones allow certain processes to be performed on 359 devices in a group without interrupting devices in other 360 groups; or 362 d) Temporary access between devices for specific purposes. 363 Administrators may remove Zone restrictions temporarily, then 364 restore Zone restrictions to perform normal processes. 366 3.3. Zoning Configuration and Management 368 Zones are configured via a Fabric Zone Server, using requests defined 369 in FC-GS-5 [FC-GS-5]), or via the T11-FC-ZONE-SERVER-MIB module 370 defined in this memo, or via some other mechanism. 372 An Nx_Port may be a member of one or more Zones. Zone membership may 373 be specified by: 375 a) The N_Port_Name of the Nx_Port connected to the switch; 376 b) The N_Port_ID assigned during Fabric Login; 377 c) The Node_Name associated with the Nx_Port; note that the 378 Node_Name may include more than one Nx_Port; 379 d) The F_Port_Name of the Fx_Port to which the Nx_Port is 380 connected; or 381 e) The domain identification (Domain_ID) and physical port number 382 of the Switch Port to which the Nx_Port is attached. 384 A fabric's Zone Server may be used to create a Zone by specifying the 385 Zone Members. One or more Zones may be collected into a Zone Set, and 386 a Zone may be a member of more than one Zone Set. A Zone Set creates 387 a collection of Zones that may be activated or deactivated as a 388 single entity across all Switches in a fabric (e.g., having two Zone 389 Sets, one for normal operation, and a second for backup during off- 390 hours). Only one Zone Set may be activated at one time. 392 Other terminology defined in [FC-GS-5] is: an Active Zone Set is the 393 Zone Set currently enforced by a fabric; a Zone Set Database is a 394 database of the Zone Sets available to be activated within a fabric; 395 and a Zoning Database is a generic term used to indicate a 396 combination of an Active Zone Set and a Zone Set Database. 398 Two distinct sets of management requests, Enhanced and Basic, are 399 defined in [FC-GS-5] to interact with a Fabric Zone Server. Basic 400 Zoning provides compatibility with [FC-GS-4] and earlier versions of 401 Fibre Channel's Generic Services specification. If all the Switches 402 in a fabric support the Enhanced request set, then it may be used to 403 manage zoning; otherwise only the Basic request set may be used, in 404 order to support backward compatibility. 406 In the context of Enhanced Zoning Management, a management action 407 (i.e., write access to the Zoning Database) to the Zone Server can 408 only occur inside a server session. A server session is setup using 409 the FC-GS-5's Common Transport (CT) protocol defined in [FC-GS-5]. A 410 server session is delimited by CT protocol requests, Server Session 411 Begin (SSB) and Server Session End (SSE), which are directed to the 412 Management Service and which have the GS_Subtype specifying the Zone 413 Server. Query requests that result in read access to the Zoning 414 Database are not required to be issued inside a server session, 415 although the information returned is not guaranteed to be consistent 416 when supplied outside of a server session. 418 When setting-up a server session for Enhanced Zoning, the Zone Server 419 is required to lock the fabric. This ensures serialized management 420 access to the Zoning Database and guarantees a deterministic 421 behavior. The switch which receives the SSB request is called the 422 'managing' switch, and it tries to lock the fabric using the Fabric 423 Management Session Protocol (see section 10.6 of [FC-SW-4]) by 424 sending an Acquire Change Authorization (ACA) request to all other 425 switches in the fabric. If any switch(es) respond with an SW_RJT 426 indicating failure, then the attempt to lock the fabric fails and the 427 SSB request is rejected. If all the other switches respond with an 428 SW_ACC indicating success, then the fabric is locked and the server 429 session can be established. The subsequent SSE request causes a 430 Release Change Authorization (RCA) request to all other switches, and 431 thus, the fabric to be unlocked. 433 For at least one application other than Zoning, the managing switch 434 uses a different type of request to lock the fabric, i.e., it sends 435 an Enhanced Acquire Change Authorization (EACA) request to all other 436 switches in the fabric. An EACA reserves local resources associated 437 with a designated application to ensure the consistency of that 438 application's data. The application is identified in the EACA using 439 an Application_ID (see Table 116 in [FC-SW-4]). A lock which was 440 established via an EACA is released using an Enhanced Release Change 441 Authorization (ERCA) request. 443 Changes requested in a Zoning Database by Enhanced Zoning commands 444 persist after the end of the Zoning (server) session only if the 445 commands are followed, within the same server session, by a Commit 446 Zone Changes (CMIT) request. On receipt of a CMIT request, the Zone 447 Server checks that the Zoning Database as modified by the outstanding 448 changes will pass the applicable consistency checks, and then 449 distributes it to all other switches in the fabric using a Stage 450 Fabric Configuration Update (SFC) request. If all other switches 451 accept the SFC request, then the "managing" switch sends an Update 452 Fabric Configuration (UFC) Request to each other switch, and the 453 staged Zoning Database thereby becomes the fabric's (active) Zoning 454 Database. 456 The latest standard for an interconnecting Fabric containing multiple 457 Fabric Switch elements is [FC-SW-4]. [FC-SW-4] carries forward the 458 earlier specification for the operation of a single Fabric in a 459 physical infrastructure, and augments it with the definition of 460 Virtual Fabrics and with the specification of how multiple Virtual 461 Fabrics can operate within one (or more) physical infrastructures. 462 The use of Virtual Fabrics provides for each frame to be tagged in 463 its header to indicate which one of several Virtual Fabrics that 464 frame is being transmitted on. All frames entering a particular 465 "Core Switch" [FC-SW-4] (i.e., a physical switch) on the same Virtual 466 Fabric are processed by the same "Virtual Switch" within that Core 467 switch. 469 4. Relationship to Other MIBs 471 The Fibre Channel Management MIB [RFC4044] defines basic information 472 for Fibre Channel hosts and switches, including extensions to the 473 standard IF-MIB [RFC2863] for Fibre Channel interfaces. 475 This MIB extends beyond [RFC4044] to cover the management of Fibre 476 Channel Zoning Servers, both for Basic Zoning Management and for 477 Enhanced Zoning Management, as defined in the FC-GS-5 specification. 479 This MIB imports some common Textual Conventions from T11-TC-MIB, 480 defined in [RFC4439]. It also imports a TC from T11-FC-NAME-SERVER- 481 MIB, defined in [RFC4438], plus InetAddressType and InetAddress from 482 INET-ADDRESS-MIB [RFC4001]. It also includes a reference to 483 snmpCommunitySecurityName defined in [RFC3584]. 485 5. MIB Overview 487 This document defines two MIB modules: T11-FC-FABRIC-LOCK-MIB and 488 T11-FC-ZONE-SERVER-MIB. 490 T11-FC-FABRIC-LOCK-MIB supports FC-GS-5's generic capability of 491 locking the fabric for a particular "application" such as (the 492 management of) Enhanced Zoning. The MIB contains one table in which 493 each entry represents a particular switch being the 'managing' switch 494 of a particular application's fabric lock. 496 T11-FC-ZONE-SERVER-MIB is specific to the operation of Zone Servers, 497 which can operate in Basic mode or in Enhanced mode. This MIB module 498 imports the T11NsGs4RejectReasonCode textual convention defined in 499 T11-FC-NAME-SERVER-MIB [RFC4438]. 501 5.1. Fibre Channel management instance 503 A Fibre Channel management instance is defined in [RFC4044] as a 504 separable managed instance of Fibre Channel functionality. Fibre 505 Channel functionality may be grouped into Fibre Channel management 506 instances in whatever way is most convenient for the 507 implementation(s). For example, one such grouping accommodates a 508 single SNMP agent having multiple AgentX [RFC2741] sub-agents, with 509 each sub-agent implementing a different Fibre Channel management 510 instance. 512 The object, fcmInstanceIndex, is IMPORTed from the FC-MGMT-MIB 513 [RFC4044] as the index value to uniquely identify each Fibre Channel 514 management instance, for example within the same SNMP context 515 ([RFC3411] section 3.3.1). 517 5.2. Switch Index 519 The FC-MGMT-MIB [RFC4044] defines the fcmSwitchTable as a table of 520 information about Fibre Channel switches which are managed by Fibre 521 Channel management instances. Each Fibre Channel management instance 522 can manage one or more Fibre Channel switches. The Switch Index, 523 fcmSwitchIndex, is IMPORTed from the FC-MGMT-MIB as the index value 524 to uniquely identify a Fibre Channel switch amongst those (one or 525 more) managed by the same Fibre Channel management instance. 527 5.3. Fabric Index 529 Whether operating on a physical fabric (i.e., without Virtual 530 Fabrics) or within a Virtual Fabric, the operation of a Zone Server 531 within a fabric is identical. Therefore, this MIB defines all 532 fabric-related information in tables which are INDEX-ed by an 533 arbitrary integer, named a "Fabric Index", having the syntax, 534 T11FabricIndex, which is IMPORTed from the T11-TC-MIB [RFC4439]. 535 When a device is connected to a single physical fabric, without use 536 of any Virtual Fabrics, the value of this Fabric Index will always be 537 1. In an environment of multiple virtual and/or physical fabrics, 538 this index provides a means to distinguish one fabric from another. 540 It is quite possible, and may even be likely, that a Fibre Channel 541 switch will have ports connected to multiple virtual and/or physical 542 Fabrics. Thus, in order to simplify a management protocol query 543 concerning all the Fabrics to which a single switch is connected, 544 fcmSwitchIndex will be listed before an object with FabricIndex as 545 its syntax when both appear in the same INDEX clause. 547 5.4. Locking the Fabric 549 The T11-FC-FABRIC-LOCK-MIB module provides for the management of 550 locks on a Fibre Channel fabric. A Fibre Channel fabric lock is used 551 to ensure serialized access to some types of management data related 552 to a fabric, e.g., the fabric's Zoning Database. 554 Some (managing) applications obtain a lock by initiating server 555 sessions and the fabric is locked so as to reserve local resources in 556 each Switch. For this usage, the managing switch sends an Acquire 557 Change Authorization (ACA) request to other switches in order to lock 558 the fabric. 560 For some other applications, a managing switch locks the fabric using 561 an Enhanced Acquire Change Authorization (EACA) request, which 562 identifies the application on whose behalf the fabric is being locked 563 with an Application_ID. In this case, only local resources 564 associated with the designated application are reserved. 566 Locks established via ACAs and via EACAs are both represented in the 567 t11FLockTable in the T11-FC-FABRIC-LOCK-MIB. The Application_ID 568 provided by the EACA serves to distinguish between multiple 569 concurrent locks established by EACAs. In order to use this same 570 mechanism to distinguish a lock established via an ACA from each of 571 those established via EACAs, an additional (special) value of 572 Application_ID has been assigned [APPL-ID] for use by this MIB 573 module. Specifically, this newly assigned value will never be used 574 to indicate an Application locked by an EACA, and therefore this MIB 575 module uses it to uniquely distinguish a lock established via an ACA. 576 In other words, with this additional assignment, an Application_ID 577 value can be used to uniquely identify any active lock amongst all 578 those established (on the same fabric) either by an EACA or an ACA. 580 5.5. Basic and Enhanced Modes 582 The t11ZsServerOperationMode object indicates whether a fabric's Zone 583 Server is operating in Basic mode or in Enhanced mode. These two 584 modes have a sufficient amount of commonality to make it worthwhile 585 to have one set of MIB objects which are used for the subset of 586 functionality which is common to both modes. To accommodate the 587 differences, additional MIB objects are defined. 589 For Enhanced mode, the additional objects are defined in a group, 590 t11ZsEnhancedModeGroup, which is only required to be implemented in a 591 Zone Server capable of supporting Enhanced mode. The objects 592 specific to Basic mode are always (even in Enhanced mode) expected to 593 be implemented, but when in Enhanced mode, their values are either 594 restricted or do not affect current operations, e.g., 595 - an example of "restricted" is: the distribution of updates to the 596 Zone Server database throughout the fabric has to be requested 597 explicitly in Basic mode; this functionality is provided in the 598 MIB by the t11ZsServerDistribute object. In contrast, in Enhanced 599 mode, the distribution is an implicit part of the commit function 600 which is initiated using the t11ZsServerCommit object. Thus, when 601 operating in Enhanced mode, t11ZsServerDistribute has a fixed 602 value, and when operating in Basic mode, t11ZsServerCommit has a 603 fixed value. 605 - an example of "do not affect current operations" is: 606 t11ZsServerHardZoning which specifies whether a switch enforces 607 hard Zoning on a fabric when in Basic mode. This object is 608 instantiated and could even be modified while in Enhanced mode, 609 but its value only takes effect when in Basic mode. (Note that in 610 Enhanced mode, t11ZsActiveZoneHardZoning specifies whether hard 611 Zoning is enabled on a particular Zone.) 613 5.6. Persistent Storage 615 A Zone Server Database for a given fabric consists of the combination 616 of many of the tables defined in this MIB module. In order to ensure 617 that such a Database is consistent, this MIB module defines just one 618 object (t11ZsServerDatabaseStorageType) with a syntax of StorageType, 619 whose value for a given fabric is defined to be applicable to all of 620 that fabric's Zone Server Database as defined in all the tables in 621 this MIB module. 623 5.7. The Active Zone Set and the Zone Set Database 625 As described in FC-GS-5 [FC-GS-5], one of the Zone Sets in the Zone 626 Set Database can be activated to become the Active Zone Set, i.e., 627 the one which is enforced on the fabric. Get/Add/Remove-type 628 requests are defined in FC-GS-5 to allow access to the Zone Set 629 Database. When the Zone Set Database is modified, such modifications 630 don't affect the Active Zone Set unless and until a subsequent 631 activation. Interaction directly with the Active Zone Set is also 632 possible via the FC-GS-5 requests: 'Activate Direct' and 'Get Active 633 Zone Set'. This is illustrated in the following rendition of Figure 634 15 of [FC-GS-5]: 636 Zone Set Database 637 +------------------+ 638 | +--------------+ | 639 Get | | Zone Set A | | 640 <=========| |(zones, zone | | 641 | | members,etc.)| | 642 | +--------------+ | 643 Add/ | | Zone Set B | | Activate +------------+ 644 Remove | +------------+ | Zone Set | | 645 =========>| |Zone Set C| |================>| | 646 | +----------+ | | Active | 647 +------------------+ | Zone | 648 | Set | 649 Get Active Zone Set | (enforced) | 650 <==============================================| | 651 | | 652 Activate Direct | | 653 ==============================================>| | 654 | | 655 Deactivate | | 656 ==============================================>| | 657 +------------+ 659 The T11-FC-ZONE-SERVER-MIB module, defined in section 7, models the 660 above structure by having one set of MIB tables for the Zone Set 661 Database and a separate set for the Active Zone Set, specifically: 663 - seven tables for the Zone Set Database: t11ZsSetTable, 664 t11ZsZoneTable, t11ZsSetZoneTable, t11ZsAliasTable, 665 t11ZsZoneMemberTable, t11ZsAttribBlockTable and t11ZsAttribTable. 667 - four tables for the Active Zone Set: t11ZsActiveTable, 668 t11ZsActiveZoneTable, t11ZsActiveZoneMemberTable and 669 t11ZsActiveAttribTable. 671 5.8. Conformance Groups 673 5.8.1. The t11ZsBasicGroup 675 This group contains objects to retrieve and to modify the Zoning 676 configuration of a Zone Server capable of operating in Basic mode. 678 5.8.2. The t11ZsEnhancedModeGroup 680 This group contains objects to retrieve and to modify the Zoning 681 configuration of a Zone Server capable of operating in Enhanced mode. 683 5.8.3. The t11ZsActivateGroup 685 This group contains objects which allow a Zone Set to be activated 686 via SNMP SetRequests and provide the status and result of such an 687 activation. 689 5.8.4. The t11ZsStatisticsGroup 691 This group contains objects for collecting Zone Server statistics. 693 5.8.5. The t11ZsNotificationGroup 695 This group contains notifications for monitoring: Zone merge 696 successes and failures, Zone Server request rejections, changes in 697 the Default Zoning behaviour, and the success or failure of an 698 attempt to activate or deactivate a Zone Set. 700 5.8.5.1. Flow-Control for Notifications 702 When defining SNMP notifications for events which occur in the data- 703 plane, the maximum frequency of their generation needs to be 704 considered. Unless there is some limiting factor, such notifications 705 need to be flow-controlled in some way, e.g., defined such that after 706 some maximum number have occurred within a specified time interval, 707 further notifications are suppressed for some subsequent time 708 interval. However, as and when such a suppression occurs, the NMS 709 which didn't receive the notifications (because they were suppressed) 710 needs an indication of how many were suppressed. Therefore, an 711 additional Counter32 object needs to be defined, and/or a new type of 712 notification needs to be defined for use at the end of the interval. 713 While this is extra complexity, it is necessary for notifications 714 which need to be flow-controlled. 716 In contrast, for notifications such as all those defined in this MIB 717 module, which are generated due to control plane events (and are not 718 able to start a chain-reaction): 720 - estimating the maximum number that could be generated per unit time 721 for each type of notification is too simplistic. E.g., it's 722 unreasonable to ask how many of the t11ZsDefZoneChangeNotify 723 notifications can be generated in a time interval -- how many 724 operators can be re-configuring the network at the same time, and how 725 frequently can each of them change the Default Zone Setting ?? 727 - the extra complexity of flow-controlling these types of 728 notifications is not warranted. 730 5.8.6. The t11ZsNotificationControlGroup 732 This group contains objects which allow each type of notification (in 733 the t11ZsNotificationGroup group) to be independently enabled or 734 disabled. It also contains objects which are used to include useful 735 information in those notifications; these objects are defined as 736 read-only to allow the values contained in the most recent 737 notification to be queried. 739 6. The T11-FC-FABRIC-LOCK-MIB Module 741 T11-FC-FABRIC-LOCK-MIB DEFINITIONS ::= BEGIN 743 IMPORTS 744 MODULE-IDENTITY, OBJECT-TYPE, 745 mib-2 FROM SNMPv2-SMI -- [RFC2578] 746 RowStatus FROM SNMPv2-TC -- [RFC2579] 747 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] 748 InetAddressType, InetAddress FROM 749 INET-ADDRESS-MIB -- [RFC4001] 750 fcmInstanceIndex, fcmSwitchIndex FROM FC-MGMT-MIB -- [RFC4044] 751 T11NsGs4RejectReasonCode FROM 752 T11-FC-NAME-SERVER-MIB -- [RFC4438] 753 T11FabricIndex FROM T11-TC-MIB; -- [RFC4439] 755 t11FabricLockMIB MODULE-IDENTITY 756 LAST-UPDATED "200701080000Z" 757 ORGANIZATION "For the initial versions, T11. 758 For later versions, the IETF's IMSS Working Group." 759 CONTACT-INFO 760 " Claudio DeSanti 761 Cisco Systems, Inc. 762 170 West Tasman Drive 763 San Jose, CA 95134 USA 764 EMail: cds@cisco.com 765 Keith McCloghrie 766 Cisco Systems, Inc. 767 170 West Tasman Drive 768 San Jose, CA 95134 USA 769 Email: kzm@cisco.com" 770 DESCRIPTION 771 "The MIB module for the management of locks on a Fibre 772 Channel fabric. A Fibre Channel fabric lock is used to 773 ensure serialized access to some types of management data 774 related to a fabric, e.g., the fabric's Zoning Database. 776 Some (managing) applications generate fabric locks by 777 initiating server sessions. Server sessions are 778 defined generically in FC-GS-5 to represent a collection of 779 one or more requests to the session's server, e.g., to the 780 Zone Server. Such a session is started by a Server Session 781 Begin (SSB) request, and terminated by a Server Session End 782 (SSE) request. The switch receiving the SSB is called the 783 'managing' switch. Some applications require the 784 'managing' switch to lock the fabric for the particular 785 application, e.g., for Enhanced Zoning, before it can 786 respond successfully to the SSB. On receipt of the 787 subsequent SSE, the lock is released. For this usage, the 788 managing switch sends an Acquire Change Authorization (ACA) 789 request to other switches to lock the fabric. 791 For some other applications, a managing switch locks the 792 fabric using an Enhanced Acquire Change Authorization (EACA) 793 request, which identifies the application on whose behalf 794 the fabric is being locked with an Application_ID. 796 Fabric locks can also be requested more directly, e.g., 797 through the use of this MIB. In these situations, the term 798 'managing' switch is used to indicate the switch which 799 receives such a request and executes it by issuing either 800 ACA or EACA requests to other switches in the fabric. 802 This MIB module defines information about the 'managing' 803 switch for currently-active fabric locks. 805 Copyright (C) The IETF Trust (2007). This version 806 of this MIB module is part of RFC yyyy; see the RFC 807 -- RFC Editor: replace yyyy with actual RFC number & remove this note 808 itself for full legal notices." 809 REVISION "200701080000Z" 810 DESCRIPTION 811 "Initial version of this MIB module, published as RFC yyyy." 812 -- RFC-Editor, replace yyyy with actual RFC number & remove this note 813 ::= { mib-2 nnn } -- to be assigned by IANA 814 -- RFC Editor: replace nnn with IANA-assigned number & remove this note 816 t11FLockMIBObjects OBJECT IDENTIFIER ::= { t11FabricLockMIB 1 } 817 t11FLockMIBConformance OBJECT IDENTIFIER ::= { t11FabricLockMIB 2 } 818 t11FLockMIBNotifications OBJECT IDENTIFIER ::= { t11FabricLockMIB 0 } 819 t11FLockConfiguration OBJECT IDENTIFIER ::= { t11FLockMIBObjects 1 } 821 -- 822 -- The table of Managing Switches and their Fabric Locks 823 -- 825 t11FLockTable OBJECT-TYPE 826 SYNTAX SEQUENCE OF T11FLockEntry 827 MAX-ACCESS not-accessible 828 STATUS current 829 DESCRIPTION 830 "A table containing information about the 'managing' 831 switch of each current fabric lock, e.g., for the 832 types of Servers defined in FC-GS-5. 834 Each entry in this table represents either: 836 1) a current fabric lock, 837 2) an in-progress attempt, requested via SNMP, to setup 838 a lock, or 839 3) a failed attempt, requested via SNMP, to setup a lock. 841 If an entry is created via t11FLockRowStatus, but the 842 attempt to obtain the lock fails, then the entry continues 843 to exist until it is deleted via t11FLockRowStatus, or 844 it is overwritten by the lock being established via 845 a means other than SNMP. However, rows created via 846 t11FLockRowStatus are not retained over restarts." 847 REFERENCE 848 "Fibre Channel - Generic Services-5 (FC-GS-5), 849 ANSI INCITS 427-2006, sections 4.9.5 and 6.4.10.2." 850 ::= { t11FLockConfiguration 1 } 852 t11FLockEntry OBJECT-TYPE 853 SYNTAX T11FLockEntry 854 MAX-ACCESS not-accessible 855 STATUS current 856 DESCRIPTION 857 "Each entry contains information specific to a current 858 fabric lock setup by a particular 'managing' switch on a 859 particular fabric. The 'managing switch' is identified by 860 values of fcmInstanceIndex and fcmSwitchIndex. 862 Server sessions for several different types of servers 863 are defined in FC-GS-5. The behavior of a server with 864 respect to commands received within a server session is 865 specified for each type of server. For some types, 866 parameter changes can only be made within the context of a 867 session, and the setting up of a session requires that the 868 fabric be locked. A fabric is locked by one switch, called 869 the 'managing' switch, sending Acquire Change Authorization 870 (ACA) requests to all other switches in the fabric. 872 For other applications, a fabric lock is established by the 873 'managing' switch sending Enhanced Acquire Change 874 Authorization (EACA) requests to other switches in the 875 fabric. Each EACA request includes an Application_ID 876 value to identify the application requesting the lock. 878 For the benefit of this MIB module, a distinct value of 879 Application_ID has also been assigned/reserved (see 880 ANSI INCITS T11/06-679v0, entitiled 'FC-SW-5 Letter to 881 T11.5') as a means of distinguishing locks established via 882 Acquire Change Authorization (ACA) requests. This 883 additional assignment allows an Application_ID to be used to 884 uniquely identify any active lock amongst all those 885 established either by an EACA or by an ACA. 887 Whenever a fabric is locked, by the sending of either an ACA 888 or an EACA, a row gets created in the representation of this 889 table for the 'managing' switch. 891 In order to process SNMP SetRequests which make parameter 892 changes for the relevant types of servers (e.g., to the 893 Zoning Database), the SNMP agent must get serialized access 894 to the fabric (for the relevant type of management data), 895 i.e., the fabric must be locked by creating an entry in 896 this table via an SNMP SetRequest. Creating an entry in 897 this table via an SNMP SetRequest causes an ACA or an EACA 898 to be sent to all other switches in the fabric. The value 899 of t11FLockApplicationID for such an entry determines 900 whether an ACA or an EACA is sent. 902 If an entry in this table is created by an SNMP SetRequest, 903 the value of the t11FLockInitiatorType object in that entry 904 will normally be 'snmp'. A row for which the value of 905 t11FLockInitiatorType is not 'snmp' cannot be modified 906 via SNMP. In particular, it cannot be deleted via 907 t11FLockRowStatus. Note that it's possible for a row to be 908 created by an SNMP SetRequest but for the setup of the lock 909 to fail, and immediately thereafter be replaced by a lock 910 successfully setup by some other means; in such a case, the 911 value of t11FLockInitiatorType would change as and when the 912 lock was setup by the other means, and so the row could 913 not thereafter be deleted via t11FLockRowStatus. 915 FC-GS-5 mentions various error situations in which a 916 fabric lock is released so as to avoid a deadlock. In 917 such situations, the agent removes the corresponding row 918 in this table as and when the lock is released. This can 919 happen for all values of t11FLockInitiatorType." 920 REFERENCE 921 "Fibre Channel - Generic Services-5 (FC-GS-5), 922 ANSI INCITS 427-2006, sections 4.9.5.5 and 6.4.7.1. 924 Fibre Channel - Switch Fabric-4 (FC-SW-4), 925 ANSI INCITS 418-2006, sections 6.1.17, 10.6.6 and 13.2, 926 and table 116. 928 'FC-SW-5 Letter to T11.5' ANSI INCITS T11/06-679v0, 929 http://www.t11.org/ftp/t11/pub/fc/sw-5/06-679v0.pdf, 930 21 September, 2006." 931 INDEX { fcmInstanceIndex, fcmSwitchIndex, t11FLockFabricIndex, 932 t11FLockApplicationID } 933 ::= { t11FLockTable 1 } 935 T11FLockEntry ::= SEQUENCE { 936 t11FLockFabricIndex T11FabricIndex, 937 t11FLockApplicationID OCTET STRING, 938 t11FLockInitiatorType INTEGER, 939 t11FLockInitiator OCTET STRING, 940 t11FLockInitiatorIpAddrType InetAddressType, 941 t11FLockInitiatorIpAddr InetAddress, 942 t11FLockStatus INTEGER, 943 t11FLockRejectReasonCode T11NsGs4RejectReasonCode, 944 t11FLockRejectReasonCodeExp OCTET STRING, 945 t11FLockRejectReasonVendorCode OCTET STRING, 946 t11FLockRowStatus RowStatus 947 } 949 t11FLockFabricIndex OBJECT-TYPE 950 SYNTAX T11FabricIndex 951 MAX-ACCESS not-accessible 952 STATUS current 953 DESCRIPTION 954 "A unique index value which uniquely identifies a 955 particular fabric. 957 In a fabric conformant to FC-SW-4, multiple Virtual Fabrics 958 can operate within one (or more) physical infrastructures, 959 and this index value is used to uniquely identify a 960 particular (physical or virtual) fabric within a physical 961 infrastructure. 963 In a fabric conformant to versions earlier than FC-SW-4, 964 only a single fabric could operate within a physical 965 infrastructure, and thus, the value of this fabric index 966 was defined to always be 1." 967 ::= { t11FLockEntry 1 } 969 t11FLockApplicationID OBJECT-TYPE 970 SYNTAX OCTET STRING (SIZE (1)) 971 MAX-ACCESS not-accessible 972 STATUS current 973 DESCRIPTION 974 "The Application_ID value which identifies the type of 975 application for which the fabric is locked. 977 A lock established via Acquire Change Authorization (ACA) 978 does not, strictly speaking, have an Application_ID value. 979 However, the value 'FF'h (255 decimal) has been reserved 980 by T11 to be used as the value of this MIB object as and 981 when a lock is established by an ACA. This value was 982 initially documented in a letter from the FC-SW-5 Editor 983 to T11.5, which was approved by the T11 and T11.5 plenary 984 meetings on October 5, 2006." 985 REFERENCE 986 "Fibre Channel - Switch Fabric-4 (FC-SW-4), 987 ANSI INCITS 418-2006, April 2006, table 116. 989 'FC-SW-5 Letter to T11.5' ANSI INCITS T11/06-679v0, 990 http://www.t11.org/ftp/t11/pub/fc/sw-5/06-679v0.pdf, 991 21 September, 2006." 992 ::= { t11FLockEntry 2 } 994 t11FLockInitiatorType OBJECT-TYPE 995 SYNTAX INTEGER { 996 other(1), 997 ssb(2), 998 cli(3), 999 snmp(4) 1000 } 1001 MAX-ACCESS read-only 1002 STATUS current 1003 DESCRIPTION 1004 "This object specifies what type of initiator generated 1005 the request which caused this lock to be established: 1007 other - none of the following. 1008 ssb - this lock was established due to the 1009 receipt of an SSB, e.g., from a GS-5 1010 client. 1011 cli - this lock was established in order 1012 to process a Command Line Interface 1013 (CLI) command. 1014 snmp - this lock was established as a result 1015 of an SNMP SetRequest. 1016 " 1017 ::= { t11FLockEntry 3 } 1019 t11FLockInitiator OBJECT-TYPE 1020 SYNTAX OCTET STRING (SIZE(0..64)) 1021 MAX-ACCESS read-only 1022 STATUS current 1023 DESCRIPTION 1024 "This object specifies the initiator whose request 1025 caused this lock to be established. 1027 If the value of the corresponding instance 1028 of t11FLockInitiatorType is 'ssb', this 1029 object will contain the FC_ID of the client 1030 which issued the Server Session Begin (SSB) 1031 which required the lock to be established. 1033 If the value of the corresponding instance 1034 of t11FLockInitiatorType object is 'cli', this 1035 object will contain the user name of the CLI 1036 (Command Line Interface) user on whose behalf 1037 the lock was established. 1039 If the value of the corresponding instance of 1040 t11FLockInitiatorType is 'snmp', this object 1041 will contain the SNMP securityName used by the 1042 SNMPv3 message containing the SetRequest which 1043 created this row. (If the row was created via 1044 SNMPv1 or SNMPv2c, then appropriate value of the 1045 snmpCommunitySecurityName is used.)" 1046 REFERENCE 1047 "Fibre Channel - Generic Services-5 (FC-GS-5), 1048 ANSI INCITS 427-2006, section 4.9.5.2. 1050 SNMP securityName is defined in RFC 3411, 'An 1051 Architecture for Describing Simple Network 1052 Management Protocol (SNMP) Management Frameworks'. 1054 snmpCommunitySecurityName is defined in RFC 3584, 1055 'Coexistence between Version 1, Version 2, and 1056 Version 3 of the Internet-standard Network 1057 Management Framework.'" 1058 ::= { t11FLockEntry 4 } 1060 t11FLockInitiatorIpAddrType OBJECT-TYPE 1061 SYNTAX InetAddressType 1062 MAX-ACCESS read-only 1063 STATUS current 1064 DESCRIPTION 1065 "This object specifies the type of IP address contained 1066 in the corresponding instance of t11FLockInitiatorIpAddr. 1067 If the IP address of the location of the initiator is 1068 unknown or not applicable, this object has the value: 1069 'unknown'." 1070 ::= { t11FLockEntry 5 } 1072 t11FLockInitiatorIpAddr OBJECT-TYPE 1073 SYNTAX InetAddress 1074 MAX-ACCESS read-only 1075 STATUS current 1076 DESCRIPTION 1077 "This object specifies the IP address of the location 1078 of the initiator which established this lock via a 1079 request of the type given by the corresponding instance 1080 of t11FLockInitiatorType. In cases where the 1081 corresponding instance of t11FLockInitiatorIpAddrType has 1082 the value: 'unknown', the value of this object is the 1083 zero-length string." 1084 ::= { t11FLockEntry 6 } 1086 t11FLockStatus OBJECT-TYPE 1087 SYNTAX INTEGER { 1088 active(1), 1089 settingUp(2), 1090 rejectFailure(3), 1091 otherFailure(4) 1092 } 1093 MAX-ACCESS read-only 1094 STATUS current 1095 DESCRIPTION 1096 "This object gives the current status of the lock: 1098 'active' -- the lock is currently established. 1099 'settingUp' -- the 'managing' switch is currently 1100 attempting to setup the lock, e.g., 1101 it is waiting to receive Accepts 1102 for ACAs from every switch in the 1103 fabric. 1104 'rejectFailure' -- the 'managing' switch's attempt to 1105 setup the lock was rejected with 1106 the reason codes given by: 1107 t11FLockRejectReasonCode, 1108 t11FLockRejectReasonCodeExp and 1109 t11FLockRejectReasonVendorCode. 1110 'otherFailure' -- the 'managing' switch's attempt 1111 to setup the lock failed (but no 1112 reason codes are available). 1114 For values of t11FLockInitiatorType other than 'snmp', 1115 a row is only required to be instantiated in this table 1116 when the value of this object is 'active'. 1118 If the value of the corresponding instance of 1119 t11FLockInitiatorType is 'snmp', the initial value of this 1120 object when the row is first created is 'settingUp'. As 1121 and when the setup succeeds, the value transitions to 1122 'active'. If the setup fails, the value transitions to 1123 either 'rejectFailure' or 'otherFailure'. Note that such a 1124 failure value is overwritten on the next attempt to obtain 1125 the lock, which could be immediately after the failure, 1126 e.g., by a GS-5 client. 1128 When the value of this object is 'rejectFailure', the 1129 rejection's reason codes are given by the corresponding 1130 values of t11FLockRejectReasonCode, 1131 t11FLockRejectReasonCodeExp and 1132 t11FLockRejectReasonVendorCode." 1133 ::= { t11FLockEntry 7 } 1135 t11FLockRejectReasonCode OBJECT-TYPE 1136 SYNTAX T11NsGs4RejectReasonCode 1137 MAX-ACCESS read-only 1138 STATUS current 1139 DESCRIPTION 1140 "When the value of the corresponding instance of 1141 t11FLockStatus is 'rejectFailure', this object contains 1142 the rejection's reason code." 1143 REFERENCE 1144 "Fibre Channel - Generic Services-5 (FC-GS-5), 1145 ANSI INCITS 427-2006, section 4.4.4 and table 10." 1146 ::= { t11FLockEntry 8 } 1148 t11FLockRejectReasonCodeExp OBJECT-TYPE 1149 SYNTAX OCTET STRING (SIZE(0 | 1)) 1150 MAX-ACCESS read-only 1151 STATUS current 1152 DESCRIPTION 1153 "When the value of the corresponding instance of 1154 t11FLockStatus is 'rejectFailure', this object contains 1155 the rejection's reason code explanation." 1156 REFERENCE 1157 "Fibre Channel - Generic Services-5 (FC-GS-5), 1158 ANSI INCITS 427-2006, sections 4.4.4 and 6.4.9, 1159 tables 10 and 252." 1160 ::= { t11FLockEntry 9 } 1162 t11FLockRejectReasonVendorCode OBJECT-TYPE 1163 SYNTAX OCTET STRING (SIZE(0 | 1)) 1164 MAX-ACCESS read-only 1165 STATUS current 1166 DESCRIPTION 1167 "When the value of the corresponding instance of 1168 t11FLockStatus is 'rejectFailure', this object contains 1169 the rejection's vendor-specific code." 1171 REFERENCE 1172 "Fibre Channel - Generic Services-5 (FC-GS-5), 1173 ANSI INCITS 427-2006, section 4.4.4." 1174 ::= { t11FLockEntry 10 } 1176 t11FLockRowStatus OBJECT-TYPE 1177 SYNTAX RowStatus 1178 MAX-ACCESS read-create 1179 STATUS current 1180 DESCRIPTION 1181 "The status of this conceptual row. 1183 A row in this table can be modified or deleted via 1184 this object only when the row's value of 1185 t11FLockInitiatorType is 'snmp'." 1186 ::= { t11FLockEntry 11 } 1188 -- Conformance 1190 t11FLockMIBCompliances 1191 OBJECT IDENTIFIER ::= { t11FLockMIBConformance 1 } 1192 t11FLockMIBGroups OBJECT IDENTIFIER ::= { t11FLockMIBConformance 2 } 1194 t11FLockMIBCompliance MODULE-COMPLIANCE 1195 STATUS current 1196 DESCRIPTION 1197 "The compliance statement for entities which support 1198 fabric locks in support of GS-5 Server applications." 1199 MODULE MANDATORY-GROUPS { t11FLockActiveGroup } 1201 OBJECT t11FLockRowStatus 1202 MIN-ACCESS read-only 1203 DESCRIPTION 1204 "Write access is not required." 1206 ::= { t11FLockMIBCompliances 1 } 1208 -- Units of Conformance 1210 t11FLockActiveGroup OBJECT-GROUP 1211 OBJECTS { t11FLockInitiatorType, 1212 t11FLockInitiator, 1213 t11FLockInitiatorIpAddrType, 1214 t11FLockInitiatorIpAddr, 1215 t11FLockStatus, 1216 t11FLockRejectReasonCode, 1217 t11FLockRejectReasonCodeExp, 1218 t11FLockRejectReasonVendorCode, 1219 t11FLockRowStatus 1220 } 1221 STATUS current 1222 DESCRIPTION 1223 "A collection of objects containing information 1224 about current fabric locks." 1225 ::= { t11FLockMIBGroups 1 } 1227 END 1229 7. The T11-FC-ZONE-SERVER-MIB Module 1231 T11-FC-ZONE-SERVER-MIB DEFINITIONS ::= BEGIN 1233 IMPORTS 1234 MODULE-IDENTITY, OBJECT-TYPE, 1235 NOTIFICATION-TYPE, mib-2, 1236 Counter32, Unsigned32 1237 FROM SNMPv2-SMI -- [RFC2578] 1238 MODULE-COMPLIANCE, OBJECT-GROUP, 1239 NOTIFICATION-GROUP 1240 FROM SNMPv2-CONF -- [RFC2580] 1241 TEXTUAL-CONVENTION, RowStatus, 1242 StorageType, 1243 TruthValue, TimeStamp 1244 FROM SNMPv2-TC -- [RFC2579] 1245 SnmpAdminString 1246 FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 1247 ifIndex FROM IF-MIB -- [RFC2863] 1248 fcmInstanceIndex, fcmSwitchIndex, 1249 FcNameIdOrZero, 1250 FcDomainIdOrZero FROM FC-MGMT-MIB -- [RFC4044] 1251 T11NsGs4RejectReasonCode 1252 FROM T11-FC-NAME-SERVER-MIB -- [RFC4438] 1253 T11FabricIndex FROM T11-TC-MIB -- [RFC4439] 1254 t11FamLocalSwitchWwn 1255 FROM T11-FC-FABRIC-ADDR-MGR-MIB; -- [RFC4439] 1257 t11ZoneServerMIB MODULE-IDENTITY 1258 LAST-UPDATED "200701080000Z" 1259 ORGANIZATION "For the initial versions, T11. 1260 For later versions, the IETF's IMSS Working Group." 1261 CONTACT-INFO 1262 " Claudio DeSanti 1263 Cisco Systems, Inc. 1264 170 West Tasman Drive 1265 San Jose, CA 95134 USA 1266 EMail: cds@cisco.com 1268 Keith McCloghrie 1269 Cisco Systems, Inc. 1270 170 West Tasman Drive 1271 San Jose, CA 95134 USA 1272 Email: kzm@cisco.com" 1273 DESCRIPTION 1274 "The MIB module for the management of Fibre Channel Zoning 1275 Servers, both for Basic Zoning Management and for Enhanced 1276 Zoning Management, as defined in the FC-GS-5 specification. 1278 FC-GS-5 defines (in-band) management operations for 1279 manipulating the Zone Set Database, some for use in Basic 1280 mode (e.g., 'Add Zone Set (AZS)', etc.), and some for use in 1281 Enhanced mode (e.g., Create Zone Set (CZS)', etc.). When 1282 Enhanced Zoning Management is in use, FC-GS-5 requires that 1283 these in-band management operations be rejected unless they 1284 are issued within the context of a GS-5 server session. The 1285 use of a server session ensures serialized access to the 1286 Zoning Database since the fabric lock for the Zone Server 1287 must be obtained as a part of establishing the server 1288 session to the Zone Server. 1290 Thus, if and when this MIB is used for Enhanced Zoning 1291 Management, SNMP SetRequests which request the modification 1292 of zoning definitions must be serialized with respect to 1293 the GS-5 requests to modify the Zoning Database. This is 1294 achieved by requiring that an SNMP management application 1295 must first obtain the fabric lock for the Zone Server 1296 before attempting to modify any zoning definitions. The 1297 companion T11-FC-FABRIC-LOCK-MIB module is defined as a means 1298 of obtaining the fabric lock for the Zone Server (or any 1299 other server). 1301 In Enhanced Zoning Management, a Zone Server keeps track of 1302 changes requested in the zoning definitions, but does not 1303 update its Zone Set Database unless and until a 'commit' 1304 operation. To model this behaviour, this MIB module assumes 1305 that a Zone Server (in Enhanced mode) takes a snapshot of 1306 its Zone Set Database as and when the fabric lock (for the 1307 Zone Server application) is obtained; this snapshot is used 1308 to create what is herein called the 'copy' database. It is 1309 this 'copy' database which is then updated by SNMP 1310 SetRequests (while the fabric is locked). If and when a 1311 'commit' operation is requested (while the fabric is still 1312 locked), the 'copy' database is then used to overwrite the 1313 previously-committed contents of the Zone Set Database, and 1314 the new Zone Set Database is distributed to all other 1315 switches in the fabric. When the lock is released, any 1316 changes made which were not 'committed' are discarded. 1318 When this MIB is used for Basic Zoning Management, the same 1319 set of MIB objects as used for Enhanced mode are used to 1320 make changes to the Database of a Zone Server on a 1321 particular switch, but the changes take immediate effect at 1322 that switch without an explicit commit. The distribution of 1323 those changes to Zone Servers on other switches in the 1324 fabric is subsequently requested through the use of a 1325 separate set of MIB objects. 1327 The management information specified in this MIB module 1328 includes the Zoning Database for each of one or more Fibre 1329 Channel Fabrics. A Zoning Database is a combination of the 1330 Fabric's Zone Set Database and its Active Zone Set. The 1331 Active Zone Set is the Zone Set currently enforced by the 1332 Fabric; a Zone Set Database is a database of the Zone Sets 1333 available to be activated within a Fabric. All the MIB 1334 objects representing a Zone Set Database are modifiable at 1335 any time (irrespective of the value of any RowStatus 1336 object), whereas all objects representing the Active Zone 1337 Set are always read-only (except to de-activate it and/or 1338 activate a different one). 1340 Copyright (C) The IETF Trust (2007). This version 1341 of this MIB module is part of RFC yyyy; see the RFC 1342 itself for full legal notices." 1343 -- RFC Editor: replace yyyy with actual RFC number & remove this note 1344 REVISION "200701080000Z" 1345 DESCRIPTION 1346 "Initial version of this MIB module, published as RFC yyyy." 1347 -- RFC-Editor, replace yyyy with actual RFC number & remove this note 1348 ::= { mib-2 nnn } -- to be assigned by IANA 1350 -- RFC Editor: replace nnn with IANA-assigned number & remove this note 1352 t11ZsMIBObjects OBJECT IDENTIFIER ::= { t11ZoneServerMIB 1 } 1353 t11ZsMIBConformance OBJECT IDENTIFIER ::= { t11ZoneServerMIB 2 } 1354 t11ZsMIBNotifications OBJECT IDENTIFIER ::= { t11ZoneServerMIB 0 } 1355 t11ZsConfiguration OBJECT IDENTIFIER ::= { t11ZsMIBObjects 1 } 1356 t11ZsStatistics OBJECT IDENTIFIER ::= { t11ZsMIBObjects 2 } 1358 -- Textual Conventions 1360 T11ZsZoneMemberType ::= TEXTUAL-CONVENTION 1361 DISPLAY-HINT "x" 1362 STATUS current 1363 DESCRIPTION 1364 "Represents the addressing mechanism by 1365 which a member is identified: 1367 01 - N_Port_Name 1368 02 - Domain_ID and physical port 1369 03 - N_Port_ID 1370 04 - Node_Name 1371 05 - Alias Name 1372 06 - F_Port_Name 1373 E0-FF (hex) - Vendor Specific. 1374 " 1375 REFERENCE 1376 "Fibre Channel - Generic Services-5 (FC-GS-5), 1377 ANSI INCITS 427-2006, section 6.4.8.3.6." 1378 SYNTAX Unsigned32 (0..255) 1380 T11ZsRejectReasonExplanation ::= TEXTUAL-CONVENTION 1381 STATUS current 1382 DESCRIPTION 1383 "The reason code explanation when rejecting a 1384 Zone Server request: 1386 'other' 1387 - e.g., a reason code assigned too recently 1388 to be included in this version of this MIB 1389 'noAdditionalExplanation' 1390 - there is no additional explanation 1391 'zonesNotSupported' 1392 - Zones are not supported 1393 'zoneSetNameUnknown' 1394 - Zone Set name is not known 1395 'noZoneSetActive' 1396 - no Zone Set is currently active 1397 'zoneNameUnknown' 1398 - Zone name is unknown 1399 'zoneStateUnknown' 1400 - state of the Zone is not known 1401 'incorrectPayloadLen' 1402 - payload length is not correct 1403 'tooLargeZoneSet' 1404 - Zone Set is larger than permitted size 1405 'deactivateZoneSetFailed' 1406 - deactivation of Zone Set failed 1407 'reqNotSupported' 1408 - request is not supported 1409 'capabilityNotSupported' 1410 - capability is not supported 1411 'zoneMemberIDTypeNotSupp' 1412 - Zone Member Identifier Type is not supported 1413 'invalidZoneSetDefinition' 1414 - Zone Set definition is invalid 1415 'enhancedZoningCmdsNotSupported' 1416 - Enhanced Zoning commands are not supported 1417 'zoneSetExists' 1418 - Zone Set already exists 1419 'zoneExists' 1420 - Zone already exists 1421 'aliasExists' 1422 - Zone Alias already exists 1423 'zoneSetUnknown' 1424 - Zone Set unknown 1425 'zoneUnknown' 1426 - Zone unknown 1427 'aliasUnknown' 1428 - Zone Alias unknown 1429 'zoneAliasTypeUnknown' 1430 - unknown Zone attribute type 1431 'unableEnhancedMode' 1432 - fabric unable to work in Enhanced Mode 1433 'basicZoningCmdsNotSupported' 1434 - Basic Zoning commands are not supported 1435 'zoneAttribObjectExists' 1436 - Zone attribute object already exists 1437 'zoneAttribObjectUnknown' 1438 - Zone attribute object unknown 1440 'requestInProcess' 1441 - request in process 1442 'cmitInProcess' 1443 - CMIT in process 1444 'hardEnforcementFailed' 1445 - hard enforcement failed 1446 'unresolvedReferences' 1447 - unresolved references in the Zone Set Database 1448 'consistencyChecksFailed' 1449 - consistency checks failed." 1450 REFERENCE 1451 "Fibre Channel - Generic Services-5 (FC-GS-5), 1452 ANSI INCITS 427-2006, section 6.4.9." 1453 SYNTAX INTEGER { 1454 other(1), 1455 noAdditionalExplanation(2), 1456 zonesNotSupported(3), 1457 zoneSetNameUnknown(4), 1458 noZoneSetActive(5), 1459 zoneNameUnknown(6), 1460 zoneStateUnknown(7), 1461 incorrectPayloadLen(8), 1462 tooLargeZoneSet(9), 1463 deactivateZoneSetFailed(10), 1464 reqNotSupported(11), 1465 capabilityNotSupported(12), 1466 zoneMemberIDTypeNotSupp(13), 1467 invalidZoneSetDefinition(14), 1468 enhancedZoningCmdsNotSupported(15), 1469 zoneSetExists(16), 1470 zoneExists(17), 1471 aliasExists(18), 1472 zoneSetUnknown(19), 1473 zoneUnknown(20), 1474 aliasUnknown(21), 1475 zoneAliasTypeUnknown(22), 1476 unableEnhancedMode(23), 1477 basicZoningCmdsNotSupported(24), 1478 zoneAttribObjectExists(25), 1479 zoneAttribObjectUnknown(26), 1480 requestInProcess(27), 1481 cmitInProcess(28), 1482 hardEnforcementFailed(29), 1483 unresolvedReferences(30), 1484 consistencyChecksFailed(31) 1486 } 1488 T11ZoningName ::= TEXTUAL-CONVENTION 1489 STATUS current 1490 DESCRIPTION 1491 "This datatype is a refinement of an SnmpAdminString, 1492 and is used to represent a name stored in a Fibre 1493 Channel Zoning Data Structure. 1495 The value begins with an ASCII letter (upper or lower 1496 case) followed by zero or more characters from the set: 1497 lower case letters, upper case letters, numbers, and 1498 the symbols ($-^_). 1500 The value does not include fill bytes." 1501 REFERENCE 1502 "Fibre Channel - Generic Services-5 (FC-GS-5), 1503 ANSI INCITS 427-2006, section 6.4.8.1." 1504 SYNTAX OCTET STRING (SIZE (1..64)) 1506 -- 1507 -- The table of Zone Servers 1508 -- 1510 t11ZsServerTable OBJECT-TYPE 1511 SYNTAX SEQUENCE OF T11ZsServerEntry 1512 MAX-ACCESS not-accessible 1513 STATUS current 1514 DESCRIPTION 1515 "A table containing information about the Zone Servers 1516 on each fabric in one or more switches, and providing 1517 the capability to perform operations on their Zone 1518 Server databases." 1519 ::= { t11ZsConfiguration 1 } 1521 t11ZsServerEntry OBJECT-TYPE 1522 SYNTAX T11ZsServerEntry 1523 MAX-ACCESS not-accessible 1524 STATUS current 1525 DESCRIPTION 1526 "Each entry contains information specific to a 1527 Zone Server for a particular fabric (identified by 1528 the value of t11ZsServerFabricIndex) on a particular 1529 switch (identified by values of fcmInstanceIndex 1530 and fcmSwitchIndex). 1532 The persistence across reboots of writable values in 1533 a row of this table is given by the instance of 1534 t11ZsServerDatabaseStorageType in that row." 1535 INDEX { fcmInstanceIndex, fcmSwitchIndex, 1536 t11ZsServerFabricIndex } 1537 ::= { t11ZsServerTable 1 } 1539 T11ZsServerEntry ::= SEQUENCE { 1540 t11ZsServerFabricIndex T11FabricIndex, 1541 t11ZsServerCapabilityObject BITS, 1542 t11ZsServerDatabaseStorageType StorageType, 1543 t11ZsServerDistribute INTEGER, 1544 t11ZsServerCommit INTEGER, 1545 t11ZsServerResult INTEGER, 1546 t11ZsServerReasonCode T11NsGs4RejectReasonCode, 1547 t11ZsServerReasonCodeExp OCTET STRING, 1548 t11ZsServerReasonVendorCode OCTET STRING, 1549 t11ZsServerLastChange TimeStamp, 1550 t11ZsServerHardZoning TruthValue, 1551 t11ZsServerReadFromDatabase INTEGER, 1552 t11ZsServerOperationMode INTEGER, 1553 t11ZsServerChangeModeResult INTEGER, 1554 t11ZsServerDefaultZoneSetting INTEGER, 1555 t11ZsServerMergeControlSetting INTEGER, 1556 t11ZsServerDefZoneBroadcast TruthValue 1557 } 1559 t11ZsServerFabricIndex OBJECT-TYPE 1560 SYNTAX T11FabricIndex 1561 MAX-ACCESS not-accessible 1562 STATUS current 1563 DESCRIPTION 1564 "A unique index value which uniquely identifies a 1565 particular fabric." 1566 ::= { t11ZsServerEntry 1 } 1568 t11ZsServerCapabilityObject OBJECT-TYPE 1569 SYNTAX BITS { 1570 enhancedMode(0), 1571 zoneSetDb(1), 1572 activateDirect(2), 1573 hardZoning(3) 1574 } 1575 MAX-ACCESS read-only 1576 STATUS current 1577 DESCRIPTION 1578 "This bitmap represents the capability of the switch 1579 on this fabric: 1581 'enhancedMode' - able to support enhanced Zoning 1582 mode of operation. 1584 'zoneSetDb' - able to support maintaining of 1585 a Zone Set Database. 1587 'activateDirect' - able to support the Activate 1588 Direct command. 1590 'hardZoning' - able to support Hard Zoning." 1591 REFERENCE 1592 "Fibre Channel - Switch Fabric-4 (FC-SW-4), 1593 ANSI INCITS 418-2006, April 2006, section 6.1.23.4.4" 1594 ::= { t11ZsServerEntry 2 } 1596 t11ZsServerDatabaseStorageType OBJECT-TYPE 1597 SYNTAX StorageType 1598 MAX-ACCESS read-write 1599 STATUS current 1600 DESCRIPTION 1601 "This object specifies the memory realization, on a 1602 particular switch, of the Zone Set database for a 1603 particular fabric. Specifically, each row in the 1604 following tables: 1606 t11ZsSetTable 1607 t11ZsZoneTable 1608 t11ZsSetZoneTable 1609 t11ZsAliasTable 1610 t11ZsZoneMemberTable 1611 t11ZsAttribBlockTable 1612 t11ZsAttribTable 1614 has a StorageType as specified by the instance of 1615 this object which is INDEX-ed by the same values of 1616 fcmInstanceIndex, fcmSwitchIndex and 1617 t11ZsServerFabricIndex. 1619 The value of this object is also used to indicate 1620 the persistence across reboots of writable values in 1621 its row of the t11ZsServerTable, as well as the 1622 corresponding row in the t11ZsNotifyControlTable. 1624 If an instance of this object has the value 1625 'permanent(4)', the Zone Set database for the given 1626 fabric on the given switch is not required to be 1627 writeable." 1628 DEFVAL { nonVolatile } 1629 ::= { t11ZsServerEntry 3 } 1631 t11ZsServerDistribute OBJECT-TYPE 1632 SYNTAX INTEGER { 1633 noop(1), 1634 zoneSetDb(2) 1635 } 1636 MAX-ACCESS read-write 1637 STATUS current 1638 DESCRIPTION 1639 "This object can be set only in Basic mode. When set 1640 to the value 'zoneSetDb', it requests that the Zone Set 1641 database of a particular switch for a particular fabric 1642 be distributed to every other switch in that fabric, 1643 e.g., by using Stage Fabric Configuration Update (SFC) 1644 and Update Fabric Configuration (UFC) requests. 1646 Setting this object to 'noop' has no effect. 1647 When read, the value of this object is always 'noop'. 1649 When the corresponding instance of t11ZsServerOperationMode 1650 has the value 'enhanced', or when the corresponding instance 1651 of t11ZsZoneSetResult has the value 'inProgress', it 1652 is inconsistent to try to set the value of this object." 1653 REFERENCE 1654 "Fibre Channel - Switch Fabric-4 (FC-SW-4), 1655 ANSI INCITS 418-2006, April 2006, section 6.1.19.1." 1656 ::= { t11ZsServerEntry 4 } 1658 t11ZsServerCommit OBJECT-TYPE 1659 SYNTAX INTEGER { 1660 commitZoneChanges(1), 1661 noop(2) 1662 } 1663 MAX-ACCESS read-write 1664 STATUS current 1665 DESCRIPTION 1666 "This object is only used in Enhanced mode. 1668 In Enhanced mode, it can only be modified when the fabric 1669 lock for the Zone Server on the particular fabric has been 1670 obtained for use by SNMP SetRequests, and even then, only 1671 by the SNMP entity identified by the value of corresponding 1672 instance of t11FLockInitiator. 1674 Setting the object requests an action: 1676 commitZoneChanges - requests that the changes made 1677 within this session to the Zone 1678 Set Database be committed. 1679 noop - requests nothing. 1681 When read, the value is always 'noop'." 1682 REFERENCE 1683 "Fibre Channel - Generic Services-5 (FC-GS-5), 1684 ANSI INCITS 427-2006, section 6.4.10.2." 1685 ::= { t11ZsServerEntry 5 } 1687 t11ZsServerResult OBJECT-TYPE 1688 SYNTAX INTEGER { 1689 none(1), 1690 inProgress(2), 1691 success(3), 1692 rejectFailure(4), 1693 otherFailure(5) 1694 } 1695 MAX-ACCESS read-only 1696 STATUS current 1697 DESCRIPTION 1698 "In Basic mode, this object indicates the status/result 1699 of the last distribution of the Zone Set database which 1700 was invoked via the corresponding instance of 1701 t11ZsZoneSetDistribute, e.g., the status/result of 1702 Stage Fabric Configuration Update (SFC) request(s) used 1703 to implement the setting of t11ZsZoneSetDistribute. 1705 In Enhanced mode, this object indicates the status/result 1706 of the last commit of changes to the Zone Set database 1707 which was invoked via the corresponding instance of 1708 t11ZsServerCommit. 1710 'none' - no distribution/commit invoked 1711 via the corresponding instance of 1712 t11ZsZoneSetDistribute (Basic mode) 1713 or t11ZsServerCommit (Enhanced mode). 1714 'inProgress' - distribution/commit is still in 1715 progress. 1716 'success' - distribution/commit completely 1717 successfully. 1718 'rejectFailure' - distribution/commit failed due to 1719 a SW_RJT. 1720 'otherFailure' - distribution/commit failed for some 1721 other reason. 1723 When the value is 'rejectFailure', the corresponding 1724 instances of t11ZsServerReasonCode, 1725 t11ZsServerReasonCodeExp and t11ZsServerReasonVendorCode 1726 contain the reason codes. " 1727 REFERENCE 1728 "Fibre Channel - Generic Services-5 (FC-GS-5), 1729 ANSI INCITS 427-2006, section 6.4.10.2.3." 1730 ::= { t11ZsServerEntry 6 } 1732 t11ZsServerReasonCode OBJECT-TYPE 1733 SYNTAX T11NsGs4RejectReasonCode 1734 MAX-ACCESS read-only 1735 STATUS current 1736 DESCRIPTION 1737 "When the corresponding instance of t11ZsZoneSetResult 1738 has the value 'rejectFailure', this object contains 1739 the rejection's reason code. 1741 When the corresponding instance of t11ZsServerResult 1742 has a value other than 'rejectFailure', this object 1743 should contain the value 'none'." 1744 REFERENCE 1745 "Fibre Channel - Switch Fabric-4 (FC-SW-4), 1746 ANSI INCITS 418-2006, April 2006, section 6.1.3 and 1747 tables 4, 5 & 6." 1748 ::= { t11ZsServerEntry 7 } 1750 t11ZsServerReasonCodeExp OBJECT-TYPE 1751 SYNTAX OCTET STRING (SIZE (0 | 1)) 1752 MAX-ACCESS read-only 1753 STATUS current 1754 DESCRIPTION 1755 "When the corresponding instance of t11ZsZoneSetResult 1756 has the value 'rejectFailure', this object contains 1757 the rejection's reason code explanation. 1759 When the corresponding instance of t11ZsServerResult 1760 has a value other than 'rejectFailure', this object 1761 should contain the zero-length string." 1762 REFERENCE 1763 "Fibre Channel - Switch Fabric-4 (FC-SW-4), 1764 ANSI INCITS 418-2006, April 2006, section 6.1.3 and 1765 tables 4, 5 & 6." 1766 ::= { t11ZsServerEntry 8 } 1768 t11ZsServerReasonVendorCode OBJECT-TYPE 1769 SYNTAX OCTET STRING (SIZE (0 | 1)) 1770 MAX-ACCESS read-only 1771 STATUS current 1772 DESCRIPTION 1773 "When the corresponding instance of t11ZsZoneSetResult 1774 has the value 'rejectFailure', this object contains 1775 the rejection's reason vendor-specific code. 1777 When the corresponding instance of t11ZsServerResult 1778 has a value other than 'rejectFailure', this object 1779 should contain the zero-length string." 1780 REFERENCE 1781 "Fibre Channel - Switch Fabric-4 (FC-SW-4), 1782 ANSI INCITS 418-2006, April 2006, section 6.1.3 and 1783 tables 4, 5 & 6." 1784 ::= { t11ZsServerEntry 9 } 1786 t11ZsServerLastChange OBJECT-TYPE 1787 SYNTAX TimeStamp 1788 MAX-ACCESS read-only 1789 STATUS current 1790 DESCRIPTION 1791 "The value of sysUpTime at the time of the last change 1792 (creation, modification or deletion) to the Zone Set 1793 database for the Zone Server for a particular fabric. 1794 If said Zone Set database has not changed since the 1795 last re-initialization of the local network management 1796 system, then this object will contain a zero value." 1797 ::= { t11ZsServerEntry 10 } 1799 t11ZsServerHardZoning OBJECT-TYPE 1800 SYNTAX TruthValue 1801 MAX-ACCESS read-only 1802 STATUS current 1803 DESCRIPTION 1804 "This object indicates whether this switch, if and when it 1805 is in Basic mode, enforces Hard Zoning on this fabric." 1806 REFERENCE 1807 "Fibre Channel - Generic Services-5 (FC-GS-5), 1808 ANSI INCITS 427-2006, section 6.4.10.3.2." 1809 ::= { t11ZsServerEntry 11 } 1811 t11ZsServerReadFromDatabase OBJECT-TYPE 1812 SYNTAX INTEGER { 1813 committedDB(1), 1814 copyDB(2) 1815 } 1816 MAX-ACCESS read-write 1817 STATUS current 1818 DESCRIPTION 1819 "In Enhanced mode, this object specifies whether 1820 subsequent SNMP Responses (generated by the local SNMP 1821 agent) to operations which read the configuration of 1822 Zone Sets, Zones, Members, Aliases and Attributes will 1823 reflect the values stored in the current (committed) 1824 Zone Set database, or those stored in the 'copy' 1825 database. 1827 In Basic mode, the value of this object is always 1828 'committedDB' (since there is no 'copy' database in 1829 Basic mode). In SNMP agents which don't support 1830 write access to the Zone Set database, this object 1831 is always 'committedDB' (since the copy database, 1832 if it were to exist, would be identical)." 1833 DEFVAL { committedDB } 1834 ::= { t11ZsServerEntry 12 } 1836 t11ZsServerOperationMode OBJECT-TYPE 1837 SYNTAX INTEGER { 1838 basic(1), 1839 enhanced(2) 1840 } 1841 MAX-ACCESS read-write 1842 STATUS current 1843 DESCRIPTION 1844 "The operational mode of the Zone Server. 1846 Setting this object to 'enhanced' is a request that the mode 1847 of operation of the Zone Server be Enhanced mode, which is 1848 only possible if all devices in the Fibre Channel fabric are 1849 capable of working in Enhanced mode. If not, the request 1850 will fail and the corresponding value of 1851 t11ZsServerChangeModeResult will so indicate. 1853 Setting this object to 'basic' requests the mode of 1854 operation of the Zone Server be Basic mode. However, 1855 such a set may fail while operating in Enhanced mode, 1856 since FC-GS-5 makes no provision for changing (back) 1857 to Basic mode. 1859 Note that setting this object does not cause or require 1860 that the fabric lock for the Zone Server be obtained. 1861 However, when this object has the value 'enhanced', any SNMP 1862 SetRequests which attempt to modify the copy database can 1863 not be successful if the fabric lock has not been obtained 1864 or has since been released." 1865 REFERENCE 1866 "Fibre Channel - Generic Services-5 (FC-GS-5), 1867 ANSI INCITS 427-2006, sections 6.4.10.1.1 and 6.4.10.1.2." 1868 DEFVAL { basic } 1869 ::= { t11ZsServerEntry 13 } 1871 t11ZsServerChangeModeResult OBJECT-TYPE 1872 SYNTAX INTEGER { 1873 success(1), 1874 failure(2), 1875 inProgress(3), 1876 none(4) 1877 } 1878 MAX-ACCESS read-only 1879 STATUS current 1880 DESCRIPTION 1881 "When this object has the value of 'success' or 1882 'failure', the value indicates the outcome of the most 1883 recent request, invoked via t11ZsServerOperationMode, 1884 to change the mode of operation of the Zone Server. 1885 When such a request is in progress, this object has the 1886 value 'inProgress'. Prior to the first such request, 1887 the value of this object is 'none'." 1888 ::= { t11ZsServerEntry 14 } 1890 t11ZsServerDefaultZoneSetting OBJECT-TYPE 1891 SYNTAX INTEGER { 1892 permit(1), 1893 deny(2) 1895 } 1896 MAX-ACCESS read-write 1897 STATUS current 1898 DESCRIPTION 1899 "This object controls the Enhanced Zoning flag which 1900 governs the behaviour of the Default Zone on this fabric. 1902 If this object is set to 'permit', then the members of 1903 the Default Zone on this fabric can communicate with 1904 each other. 1906 If this object is set to 'deny', then the members of the 1907 Default Zone on this fabric cannot communicate with each 1908 other." 1909 REFERENCE 1910 "Fibre Channel - Generic Services-5 (FC-GS-5), 1911 ANSI INCITS 427-2006, section 6.4.10.1.1." 1912 DEFVAL { deny } 1913 ::= { t11ZsServerEntry 15 } 1915 t11ZsServerMergeControlSetting OBJECT-TYPE 1916 SYNTAX INTEGER { 1917 allow(1), 1918 restrict(2) 1919 } 1920 MAX-ACCESS read-write 1921 STATUS current 1922 DESCRIPTION 1923 "This object controls the Enhanced Zoning flag which 1924 indicates the Merge Control Setting for this fabric: 1926 'allow' - a switch may join the fabric only if 1927 its Zoning Database is able to merge 1928 with the fabric's Zoning Database. 1929 'restrict' - a switch may join the fabric only if 1930 its Zoning Database is equal to the 1931 fabric's Zoning Database." 1932 REFERENCE 1933 "Fibre Channel - Generic Services-5 (FC-GS-5), 1934 ANSI INCITS 427-2006, section 6.4.10.1.1." 1935 DEFVAL { allow } 1936 ::= { t11ZsServerEntry 16 } 1938 t11ZsServerDefZoneBroadcast OBJECT-TYPE 1939 SYNTAX TruthValue 1940 MAX-ACCESS read-write 1941 STATUS current 1942 DESCRIPTION 1943 "This object controls an Enhanced Zoning capability: 1944 it indicates whether Broadcast Zoning is enabled on 1945 the Default Zone on this fabric. If this object is 1946 set to 'true', then it is enabled. If this object is 1947 set to 'false', then it is disabled. 1949 If broadcast Zoning is enabled on a Default Zone, 1950 then broadcast frames generated by a member in that 1951 Default Zone will be restricted to members in that 1952 Default Zone." 1953 REFERENCE 1954 "Fibre Channel - Generic Services-5 (FC-GS-5), 1955 ANSI INCITS 427-2006, section 6.4.7.2.2." 1956 ::= { t11ZsServerEntry 17 } 1958 -- 1959 -- The table of Zone Sets 1960 -- 1962 t11ZsSetTable OBJECT-TYPE 1963 SYNTAX SEQUENCE OF T11ZsSetEntry 1964 MAX-ACCESS not-accessible 1965 STATUS current 1966 DESCRIPTION 1967 "A table containing information on every Zone 1968 Set in the Zone Set database of the Zone Servers 1969 on each fabric in one or more switches. 1971 In Enhanced mode, changes to a database made via this 1972 table are always made to the 'copy' database, but 1973 values read from this table reflect the contents of 1974 either the 'copy' database or the current (committed) 1975 database as indicated by the corresponding value of 1976 t11ZsServerReadFromDatabase." 1977 ::= { t11ZsConfiguration 2 } 1979 t11ZsSetEntry OBJECT-TYPE 1980 SYNTAX T11ZsSetEntry 1981 MAX-ACCESS not-accessible 1982 STATUS current 1983 DESCRIPTION 1984 "Each entry contains information about a Zone Set 1985 in the Zone Set database of a particular fabric 1986 (identified by the value of t11ZsServerFabricIndex) 1987 on a particular switch (identified by values of 1988 fcmInstanceIndex and fcmSwitchIndex). 1990 A Zone Set can be created in an existing Zone Set 1991 database, and can contain zero or more existing 1992 Zones. As and when new Zones are created 1993 (as rows in the t11ZsZoneTable), they can be added 1994 to a Zone Set by creating an entry for each in the 1995 t11ZsSetZoneTable. Deleting a row from this table 1996 deletes the Zone Set from the Zone Set database 1997 maintained by the Zone Server, but does not otherwise 1998 affect the Zone Server. 2000 The StorageType of a row in this table is specified by 2001 the instance of t11ZsServerDatabaseStorageType which is 2002 INDEX-ed by the same values of fcmInstanceIndex, 2003 fcmSwitchIndex and t11ZsServerFabricIndex." 2004 INDEX { fcmInstanceIndex, fcmSwitchIndex, 2005 t11ZsServerFabricIndex, t11ZsSetIndex } 2006 ::= { t11ZsSetTable 1 } 2008 T11ZsSetEntry ::= SEQUENCE { 2009 t11ZsSetIndex Unsigned32, 2010 t11ZsSetName T11ZoningName, 2011 t11ZsSetRowStatus RowStatus 2012 } 2014 t11ZsSetIndex OBJECT-TYPE 2015 SYNTAX Unsigned32 (1..4294967295) 2016 MAX-ACCESS not-accessible 2017 STATUS current 2018 DESCRIPTION 2019 "The index of a Zone Set. This object uniquely 2020 identifies a Zone Set in the Zone Set database 2021 for a particular fabric on a particular switch." 2022 ::= { t11ZsSetEntry 1 } 2024 t11ZsSetName OBJECT-TYPE 2025 SYNTAX T11ZoningName 2026 MAX-ACCESS read-create 2027 STATUS current 2028 DESCRIPTION 2029 "The name of this Zone Set. The t11ZsSetName should 2030 be unique within a fabric. 2032 The Zone Set can be renamed at any time (i.e., even 2033 when the row in an active state) by setting this object 2034 to a new value." 2035 ::= { t11ZsSetEntry 2 } 2037 t11ZsSetRowStatus OBJECT-TYPE 2038 SYNTAX RowStatus 2039 MAX-ACCESS read-create 2040 STATUS current 2041 DESCRIPTION 2042 "The status of this conceptual row. 2044 This object can not be set to 'active' unless the 2045 corresponding value of t11ZsSetName is unique within 2046 the fabric's Zone Server database on this switch." 2047 ::= { t11ZsSetEntry 3 } 2049 -- 2050 -- The table of Zones 2051 -- 2053 t11ZsZoneTable OBJECT-TYPE 2054 SYNTAX SEQUENCE OF T11ZsZoneEntry 2055 MAX-ACCESS not-accessible 2056 STATUS current 2057 DESCRIPTION 2058 "This table gives information on all the Zones in the 2059 Zone Set database of the Zone Servers on each fabric 2060 in one or more switches. 2062 In Enhanced mode, changes to a database made via this 2063 table are always made to the 'copy' database, but 2064 values read from this table reflect the contents of 2065 either the 'copy' database or the current (committed) 2066 database as indicated by the corresponding value of 2067 t11ZsServerReadFromDatabase." 2068 ::= { t11ZsConfiguration 3 } 2070 t11ZsZoneEntry OBJECT-TYPE 2071 SYNTAX T11ZsZoneEntry 2072 MAX-ACCESS not-accessible 2073 STATUS current 2074 DESCRIPTION 2075 "Each entry contains information about a Zone 2076 in the Zone Set database of a particular fabric 2077 (identified by the value of t11ZsServerFabricIndex) 2078 on a particular switch (identified by values of 2079 fcmInstanceIndex and fcmSwitchIndex). 2081 A Zone can be created in an existing Zone Set 2082 database, by first creating an entry in this table, 2083 and then adding members to it by creating entries in the 2084 t11ZsZoneMemberTable. 2086 The StorageType of a row in this table is specified by 2087 the instance of t11ZsServerDatabaseStorageType which is 2088 INDEX-ed by the same values of fcmInstanceIndex, 2089 fcmSwitchIndex and t11ZsServerFabricIndex." 2090 INDEX { fcmInstanceIndex, fcmSwitchIndex, 2091 t11ZsServerFabricIndex, t11ZsZoneIndex } 2092 ::= { t11ZsZoneTable 1 } 2094 T11ZsZoneEntry ::= SEQUENCE { 2095 t11ZsZoneIndex Unsigned32, 2096 t11ZsZoneName T11ZoningName, 2097 t11ZsZoneAttribBlock Unsigned32, 2098 t11ZsZoneRowStatus RowStatus 2099 } 2101 t11ZsZoneIndex OBJECT-TYPE 2102 SYNTAX Unsigned32 (1..4294967295) 2103 MAX-ACCESS not-accessible 2104 STATUS current 2105 DESCRIPTION 2106 "An index value which uniquely identifies this 2107 Zone within a particular fabric's Zone Set database 2108 on a particular switch." 2109 ::= { t11ZsZoneEntry 1 } 2111 t11ZsZoneName OBJECT-TYPE 2112 SYNTAX T11ZoningName 2113 MAX-ACCESS read-create 2114 STATUS current 2115 DESCRIPTION 2116 "The name of this Zone. The t11ZsZoneName should be 2117 unique within a fabric. 2119 The Zone can be renamed by setting this object 2120 to a new value." 2121 ::= { t11ZsZoneEntry 2 } 2123 t11ZsZoneAttribBlock OBJECT-TYPE 2124 SYNTAX Unsigned32 (0..4294967295) 2125 MAX-ACCESS read-create 2126 STATUS current 2127 DESCRIPTION 2128 "This object specifies the index value of the 2129 Zone Attribute Block which contains the Attributes 2130 of this Zone. 2132 In Enhanced mode, a value of zero indicates this 2133 Zone has no Zone Attributes. In Basic mode, this 2134 object always has the value of zero." 2135 ::= { t11ZsZoneEntry 3 } 2137 t11ZsZoneRowStatus OBJECT-TYPE 2138 SYNTAX RowStatus 2139 MAX-ACCESS read-create 2140 STATUS current 2141 DESCRIPTION 2142 "The status of this conceptual row. 2144 This object can not be set to 'active' unless the 2145 corresponding value of t11ZsZoneName is unique within 2146 the fabric's Zone Server database on this switch." 2147 ::= { t11ZsZoneEntry 4 } 2149 -- 2150 -- The table specifying the Zones which belong to each Zone Set 2151 -- 2153 t11ZsSetZoneTable OBJECT-TYPE 2154 SYNTAX SEQUENCE OF T11ZsSetZoneEntry 2155 MAX-ACCESS not-accessible 2156 STATUS current 2157 DESCRIPTION 2158 "This table specifies which Zones belong to which Zone 2159 Sets in the Zone Set database of the Zone Servers 2160 on each fabric in one or more switches." 2161 ::= { t11ZsConfiguration 4 } 2163 t11ZsSetZoneEntry OBJECT-TYPE 2164 SYNTAX T11ZsSetZoneEntry 2165 MAX-ACCESS not-accessible 2166 STATUS current 2167 DESCRIPTION 2168 "Each entry specifies that a particular Zone (identified 2169 by the value of t11ZsZoneIndex) is one of the Zones 2170 which form a particular Zone Set (identified by the 2171 value of t11ZsSetIndex) in the Zone Set database of a 2172 particular fabric (identified by the value of 2173 t11ZsServerFabricIndex) on a particular switch 2174 (identified by values of fcmInstanceIndex and 2175 fcmSwitchIndex). 2177 When a row in this table exists, it references one row in 2178 the t11ZsSetTable and one row in the t11ZsZoneTable. The 2179 agent must ensure that both such rows when referenced by an 2180 active row in this table, do exist and have a status of 2181 'active', either by refusing to create new rows in this 2182 table, or by automatically deleting rows in this table. 2184 An 'active' row in this table references one row in the 2185 t11ZsSetTable and one in the t11ZsZoneTable. The agent must 2186 ensure that all such referenced rows exist with a status of 2187 'active', either by refusing to create new active rows in 2188 this table, or by automatically deleting any rows in this 2189 table which reference a deleted row. 2191 The StorageType of a row in this table is specified by 2192 the instance of t11ZsServerDatabaseStorageType which is 2193 INDEX-ed by the same values of fcmInstanceIndex, 2194 fcmSwitchIndex and t11ZsServerFabricIndex." 2195 INDEX { fcmInstanceIndex, fcmSwitchIndex, 2196 t11ZsServerFabricIndex, 2197 t11ZsSetIndex, t11ZsZoneIndex } 2198 ::= { t11ZsSetZoneTable 1 } 2200 T11ZsSetZoneEntry ::= SEQUENCE { 2201 t11ZsSetZoneRowStatus RowStatus 2202 } 2204 t11ZsSetZoneRowStatus OBJECT-TYPE 2205 SYNTAX RowStatus 2206 MAX-ACCESS read-create 2207 STATUS current 2208 DESCRIPTION 2209 "The status of this conceptual row." 2211 ::= { t11ZsSetZoneEntry 1 } 2213 -- 2214 -- The table of Zone Aliases 2215 -- 2217 t11ZsAliasTable OBJECT-TYPE 2218 SYNTAX SEQUENCE OF T11ZsAliasEntry 2219 MAX-ACCESS not-accessible 2220 STATUS current 2221 DESCRIPTION 2222 "This table contains information about the Zone Aliases 2223 in the Zone Set database of the Zone Servers on each 2224 fabric in one or more switches. 2226 In Enhanced mode, changes to a database made via this 2227 table are always made to the 'copy' database, but 2228 values read from this table reflect the contents of 2229 either the 'copy' database or the current (committed) 2230 database as indicated by the corresponding value of 2231 t11ZsServerReadFromDatabase." 2232 ::= { t11ZsConfiguration 5 } 2234 t11ZsAliasEntry OBJECT-TYPE 2235 SYNTAX T11ZsAliasEntry 2236 MAX-ACCESS not-accessible 2237 STATUS current 2238 DESCRIPTION 2239 "Each entry contains information about a Zone Alias in 2240 the Zone Set database of a particular fabric 2241 (identified by the value of t11ZsServerFabricIndex) on 2242 a particular switch (identified by values of 2243 fcmInstanceIndex and fcmSwitchIndex). 2245 A Zone Member is added to a Zone Alias by creating 2246 an entry in the t11ZsZoneMemberTable pointing to a 2247 row of this table via t11ZsAliasIndex, i.e.,: 2249 - t11ZsZoneMemberParentType = 'alias', 2250 - t11ZsZoneMemberParentIndex = Alias's t11ZsAliasIndex, 2251 - t11ZsZoneMemberFormat != '05 - Alias Name', and 2252 - t11ZsZoneMemberID = Member's identifier. 2254 A Zone Alias is added to a Zone by creating 2255 an entry in the t11ZsZoneMemberTable pointing to a 2256 row of this table via t11ZsAliasName, i.e.,: 2258 - t11ZsZoneMemberParentType = 'zone', and 2259 - t11ZsZoneMemberParentIndex = Zone's t11ZsZoneIndex, 2260 - t11ZsZoneMemberFormat = '05 - Alias Name', 2261 - t11ZsZoneMemberID = Alias's t11ZsAliasName. 2263 The StorageType of a row in this table is specified by 2264 the instance of t11ZsServerDatabaseStorageType which is 2265 INDEX-ed by the same values of fcmInstanceIndex, 2266 fcmSwitchIndex and t11ZsServerFabricIndex." 2267 INDEX { fcmInstanceIndex, fcmSwitchIndex, 2268 t11ZsServerFabricIndex, t11ZsAliasIndex } 2269 ::= { t11ZsAliasTable 1 } 2271 T11ZsAliasEntry ::= SEQUENCE { 2272 t11ZsAliasIndex Unsigned32, 2273 t11ZsAliasName T11ZoningName, 2274 t11ZsAliasRowStatus RowStatus 2275 } 2277 t11ZsAliasIndex OBJECT-TYPE 2278 SYNTAX Unsigned32 (1..4294967295) 2279 MAX-ACCESS not-accessible 2280 STATUS current 2281 DESCRIPTION 2282 "An index value which uniquely identifies this Zone 2283 Alias within the Zone Set database of a particular 2284 fabric on a particular switch." 2285 ::= { t11ZsAliasEntry 1 } 2287 t11ZsAliasName OBJECT-TYPE 2288 SYNTAX T11ZoningName 2289 MAX-ACCESS read-create 2290 STATUS current 2291 DESCRIPTION 2292 "The name of this Zone Alias. The name of the Zone 2293 Alias should be unique within a fabric. 2295 The Zone Alias can be renamed by setting this object 2296 to a new value if and when it is not in a Zone, i.e., 2297 if and only if the current name is not the value of 2298 any t11ZsZoneMemberID in the same Zone Set database." 2299 ::= { t11ZsAliasEntry 2 } 2301 t11ZsAliasRowStatus OBJECT-TYPE 2302 SYNTAX RowStatus 2303 MAX-ACCESS read-create 2304 STATUS current 2305 DESCRIPTION 2306 "The status of this conceptual row. 2308 This object can not be set to 'active' unless the 2309 corresponding value of t11ZsAliasName is unique within 2310 the fabric's Zone Server database on this switch." 2311 ::= { t11ZsAliasEntry 3 } 2313 -- 2314 -- The table of Zone Members 2315 -- 2317 t11ZsZoneMemberTable OBJECT-TYPE 2318 SYNTAX SEQUENCE OF T11ZsZoneMemberEntry 2319 MAX-ACCESS not-accessible 2320 STATUS current 2321 DESCRIPTION 2322 "This table contains all members of a Zone/Zone Alias 2323 and information about those members in the Zone Set 2324 database of the Zone Servers on each fabric in one or 2325 more switches. 2327 In Enhanced mode, changes to a database made via this 2328 table are always made to the 'copy' database, but 2329 values read from this table reflect the contents of 2330 either the 'copy' database or the current (committed) 2331 database as indicated by the corresponding value of 2332 t11ZsServerReadFromDatabase." 2333 ::= { t11ZsConfiguration 6 } 2335 t11ZsZoneMemberEntry OBJECT-TYPE 2336 SYNTAX T11ZsZoneMemberEntry 2337 MAX-ACCESS not-accessible 2338 STATUS current 2339 DESCRIPTION 2340 "Each entry represents the relationship between a 2341 member and (one of) its 'parent(s)', i.e., a Zone 2342 or Zone Alias to which the member belongs, within 2343 a particular fabric (identified by the value of 2344 t11ZsServerFabricIndex) on a particular switch 2345 (identified by values of fcmInstanceIndex and 2346 fcmSwitchIndex). 2348 A Zone member (other than an alias) is added to a 2349 Zone by creating an entry in this table having: 2351 - t11ZsZoneMemberParentType = 'zone', and 2352 - t11ZsZoneMemberParentIndex = Zone's t11ZsZoneIndex, 2353 - t11ZsZoneMemberFormat != '05 - Alias Name', 2354 - t11ZsZoneMemberID = Member's identifier. 2356 An 'active' row in this table references rows in other 2357 tables. The agent must ensure that all such referenced 2358 rows exist with a status of 'active', either by refusing to 2359 create new active rows in this table, or by automatically 2360 deleting any rows in this table which reference a deleted 2361 row. 2363 The StorageType of a row in this table is specified by 2364 the instance of t11ZsServerDatabaseStorageType which is 2365 INDEX-ed by the same values of fcmInstanceIndex, 2366 fcmSwitchIndex and t11ZsServerFabricIndex." 2367 INDEX { fcmInstanceIndex, fcmSwitchIndex, 2368 t11ZsServerFabricIndex, t11ZsZoneMemberParentType, 2369 t11ZsZoneMemberParentIndex, t11ZsZoneMemberIndex } 2370 ::= { t11ZsZoneMemberTable 1 } 2372 T11ZsZoneMemberEntry ::= SEQUENCE { 2373 t11ZsZoneMemberParentType INTEGER, 2374 t11ZsZoneMemberParentIndex Unsigned32, 2375 t11ZsZoneMemberIndex Unsigned32, 2376 t11ZsZoneMemberFormat T11ZsZoneMemberType, 2377 t11ZsZoneMemberID OCTET STRING, 2378 t11ZsZoneMemberRowStatus RowStatus 2379 } 2381 t11ZsZoneMemberParentType OBJECT-TYPE 2382 SYNTAX INTEGER { 2383 zone(1), -- member belongs to a Zone 2384 alias(2) -- member belongs to a Zone Alias 2385 } 2386 MAX-ACCESS not-accessible 2387 STATUS current 2388 DESCRIPTION 2389 "This object determines whether this member belongs 2390 to a Zone or an Zone Alias." 2392 ::= { t11ZsZoneMemberEntry 1 } 2394 t11ZsZoneMemberParentIndex OBJECT-TYPE 2395 SYNTAX Unsigned32 (1..4294967295) 2396 MAX-ACCESS not-accessible 2397 STATUS current 2398 DESCRIPTION 2399 "This object contains the index value of the Zone or 2400 Zone Alias to which this member belongs. 2402 If the value of the corresponding instance of 2403 t11ZsZoneMemberParentType is 'zone', then this object 2404 will contain the value of the t11ZsZoneIndex object of 2405 the Zone to which this member belongs. 2407 If the value of the corresponding instance of 2408 t11ZsZoneMemberParentType is 'alias', then this object 2409 will contain the value of the t11ZsAliasIndex object 2410 of the Zone Alias to which this member belongs." 2411 ::= { t11ZsZoneMemberEntry 2 } 2413 t11ZsZoneMemberIndex OBJECT-TYPE 2414 SYNTAX Unsigned32 (1..4294967295) 2415 MAX-ACCESS not-accessible 2416 STATUS current 2417 DESCRIPTION 2418 "An index value which uniquely identifies this Zone 2419 Member amongst all Zone Members in the Zone Set 2420 database of a particular fabric on a particular switch." 2421 ::= { t11ZsZoneMemberEntry 3 } 2423 t11ZsZoneMemberFormat OBJECT-TYPE 2424 SYNTAX T11ZsZoneMemberType 2425 MAX-ACCESS read-create 2426 STATUS current 2427 DESCRIPTION 2428 "This object identifies the format of the 2429 Zone/Zone Alias member's identifier contained in 2430 t11ZsZoneMemberID. 2432 This object can not be modified while the corresponding 2433 value of t11ZsZoneMemberRowStatus object is 'active'." 2434 ::= { t11ZsZoneMemberEntry 4 } 2436 t11ZsZoneMemberID OBJECT-TYPE 2437 SYNTAX OCTET STRING (SIZE (1..255)) 2438 MAX-ACCESS read-create 2439 STATUS current 2440 DESCRIPTION 2441 "This object contains the Member Identifier of the 2442 Zone or Alias. The interpretation of this object 2443 depends on the value of the corresponding instance 2444 of t11ZsZoneMemberFormat: 2446 - if t11ZsZoneMemberFormat is 'N_Port_Name', then 2447 this object contains a N_Port_Name. 2449 - if t11ZsZoneMemberFormat is 'Domain_ID and physical 2450 port', then this object contains a 4-octet value in 2451 network-byte order. The first octet is zero, 2452 the second octet contains the Domain_ID, and the 2453 last two octets contain the physical port number. 2455 - if t11ZsZoneMemberFormat is 'N_Port_ID', then this 2456 object contains the 3-octet Nx_Port FC_ID. 2458 - if t11ZsZoneMemberFormat is 'Alias Name', then 2459 this object contains the value of t11ZsAliasName 2460 for some Alias in the same Zone Set database. 2462 - if t11ZsZoneMemberFormat is 'Node_Name', then 2463 this object contains an 8-octet Node_Name. 2465 - if t11ZsZoneMemberFormat is 'F_Port_Name', then 2466 this object contains an 8-octet F_Port_Name. 2468 - if t11ZsZoneMemberFormat is one of the 'Vendor 2469 Specific' values, then this object contains a 1 to 2470 255 octet value in a format defined by the relevant 2471 vendor. 2473 This object cannot be modified while the corresponding 2474 value of t11ZsZoneMemberRowStatus object is 'active'." 2475 ::= { t11ZsZoneMemberEntry 5 } 2477 t11ZsZoneMemberRowStatus OBJECT-TYPE 2478 SYNTAX RowStatus 2479 MAX-ACCESS read-create 2480 STATUS current 2481 DESCRIPTION 2482 "The status of this conceptual row. 2484 The corresponding instances of t11ZsZoneMemberID and 2485 t11ZsZoneMemberFormat objects must be set before or 2486 concurrently with setting this object to 'active'." 2487 ::= { t11ZsZoneMemberEntry 6 } 2489 -- 2490 -- The table of Zone Attribute Blocks 2491 -- 2493 t11ZsAttribBlockTable OBJECT-TYPE 2494 SYNTAX SEQUENCE OF T11ZsAttribBlockEntry 2495 MAX-ACCESS not-accessible 2496 STATUS current 2497 DESCRIPTION 2498 "This table gives information on all the Zone 2499 Attributes in the Zone Set database of the Zone 2500 Servers on each fabric in one or more switches. 2502 In Enhanced mode, changes to a database made via this 2503 table are always made to the 'copy' database, but 2504 values read from this table reflect the contents of 2505 either the 'copy' database or the current (committed) 2506 database as indicated by the corresponding value of 2507 t11ZsServerReadFromDatabase." 2508 ::= { t11ZsConfiguration 7 } 2510 t11ZsAttribBlockEntry OBJECT-TYPE 2511 SYNTAX T11ZsAttribBlockEntry 2512 MAX-ACCESS not-accessible 2513 STATUS current 2514 DESCRIPTION 2515 "Each entry contains information about a Zone Attribute 2516 Block (of Zone Attributes) in the Zone Set database 2517 of a particular fabric (identified by the value of 2518 t11ZsServerFabricIndex) on a particular switch 2519 (identified by values of fcmInstanceIndex and 2520 fcmSwitchIndex). 2522 An 'active' row in this table references a row in the 2523 t11ZsAttribBlockTable. The agent must ensure that the 2524 referenced rows exists with a status of 'active', either by 2525 refusing to create new active rows in this table, or by 2526 automatically deleting any rows in this table which 2527 reference a deleted row. 2529 The StorageType of a row in this table is specified by 2530 the instance of t11ZsServerDatabaseStorageType which is 2531 INDEX-ed by the same values of fcmInstanceIndex, 2532 fcmSwitchIndex and t11ZsServerFabricIndex." 2533 INDEX { fcmInstanceIndex, fcmSwitchIndex, 2534 t11ZsServerFabricIndex, t11ZsAttribBlockIndex } 2535 ::= { t11ZsAttribBlockTable 1 } 2537 T11ZsAttribBlockEntry ::= SEQUENCE { 2538 t11ZsAttribBlockIndex Unsigned32, 2539 t11ZsAttribBlockName T11ZoningName, 2540 t11ZsAttribBlockRowStatus RowStatus 2541 } 2543 t11ZsAttribBlockIndex OBJECT-TYPE 2544 SYNTAX Unsigned32 (1..4294967295) 2545 MAX-ACCESS not-accessible 2546 STATUS current 2547 DESCRIPTION 2548 "An index value which uniquely identifies this Zone 2549 Attribute within the Zone Set database of a particular 2550 fabric on a particular switch." 2551 ::= { t11ZsAttribBlockEntry 1 } 2553 t11ZsAttribBlockName OBJECT-TYPE 2554 SYNTAX T11ZoningName 2555 MAX-ACCESS read-create 2556 STATUS current 2557 DESCRIPTION 2558 "The name of this Zone Attribute Block, which should 2559 be unique within the fabric." 2560 ::= { t11ZsAttribBlockEntry 2 } 2562 t11ZsAttribBlockRowStatus OBJECT-TYPE 2563 SYNTAX RowStatus 2564 MAX-ACCESS read-create 2565 STATUS current 2566 DESCRIPTION 2567 "The status of this conceptual row." 2568 ::= { t11ZsAttribBlockEntry 3 } 2570 -- 2571 -- The table of Zone Attributes 2572 -- 2574 t11ZsAttribTable OBJECT-TYPE 2575 SYNTAX SEQUENCE OF T11ZsAttribEntry 2576 MAX-ACCESS not-accessible 2577 STATUS current 2578 DESCRIPTION 2579 "This table gives information on the Zone Attributes 2580 within the Zone Attribute Blocks in the Zone Set 2581 database of the Zone Servers on each fabric in one 2582 or more switches. 2584 In Enhanced mode, changes to a database made via this 2585 table are always made to the 'copy' database, but 2586 values read from this table reflect the contents of 2587 either the 'copy' database or the current (committed) 2588 database as indicated by the corresponding value of 2589 t11ZsServerReadFromDatabase." 2590 ::= { t11ZsConfiguration 8 } 2592 t11ZsAttribEntry OBJECT-TYPE 2593 SYNTAX T11ZsAttribEntry 2594 MAX-ACCESS not-accessible 2595 STATUS current 2596 DESCRIPTION 2597 "Each entry contains information about a Zone 2598 Attribute in a Zone Attribute Block (identified by 2599 t11ZsAttribBlockIndex) in the Zone Set database of 2600 a particular fabric (identified by the value of 2601 t11ZsServerFabricIndex) on a particular switch 2602 (identified by values of fcmInstanceIndex and 2603 fcmSwitchIndex). 2605 An entry in this table cannot be created prior to 2606 its associated entry in the t11ZsAttribBlockTable. 2608 The StorageType of a row in this table is specified by 2609 the instance of t11ZsServerDatabaseStorageType which is 2610 INDEX-ed by the same values of fcmInstanceIndex, 2611 fcmSwitchIndex and t11ZsServerFabricIndex." 2612 INDEX { fcmInstanceIndex, fcmSwitchIndex, 2613 t11ZsServerFabricIndex, 2614 t11ZsAttribBlockIndex, t11ZsAttribIndex } 2616 ::= { t11ZsAttribTable 1 } 2618 T11ZsAttribEntry ::= SEQUENCE { 2619 t11ZsAttribIndex Unsigned32, 2620 t11ZsAttribType Unsigned32, 2621 t11ZsAttribValue OCTET STRING, 2622 t11ZsAttribRowStatus RowStatus 2623 } 2625 t11ZsAttribIndex OBJECT-TYPE 2626 SYNTAX Unsigned32 (1..4294967295) 2627 MAX-ACCESS not-accessible 2628 STATUS current 2629 DESCRIPTION 2630 "An index value which uniquely identifies this 2631 Zone Attribute within its Zone Attribute Block in 2632 the Zone Set database of a particular fabric on a 2633 particular switch." 2634 ::= { t11ZsAttribEntry 1 } 2636 t11ZsAttribType OBJECT-TYPE 2637 SYNTAX Unsigned32 (0..65535) 2638 MAX-ACCESS read-create 2639 STATUS current 2640 DESCRIPTION 2641 "The type of attribute: 2643 0001 - Protocol 2644 0002 - Broadcast Zone 2645 0003 - Hard Zone 2646 00E0 (hex) - Vendor Specific." 2647 REFERENCE 2648 "Fibre Channel - Generic Services-5 (FC-GS-5), 2649 ANSI INCITS 427-2006, section 6.4.8.3.8, table 249." 2650 ::= { t11ZsAttribEntry 2 } 2652 t11ZsAttribValue OBJECT-TYPE 2653 SYNTAX OCTET STRING (SIZE (4..252)) 2654 MAX-ACCESS read-create 2655 STATUS current 2656 DESCRIPTION 2657 "The value of the attribute, formatted as specified 2658 in FC-GS-5 for the type given by the corresponding 2659 instance of t11ZsAttribType. 2661 Note that FC-GS-5 requires that the length of this 2662 value is a multiple of four bytes." 2663 REFERENCE 2664 "Fibre Channel - Generic Services-5 (FC-GS-5), 2665 ANSI INCITS 427-2006, section 6.4.8.3.8." 2666 ::= { t11ZsAttribEntry 3 } 2668 t11ZsAttribRowStatus OBJECT-TYPE 2669 SYNTAX RowStatus 2670 MAX-ACCESS read-create 2671 STATUS current 2672 DESCRIPTION 2673 "The status of this conceptual row." 2674 ::= { t11ZsAttribEntry 4 } 2676 -- 2677 -- Activating a Zone Set 2678 -- 2680 t11ZsActivateTable OBJECT-TYPE 2681 SYNTAX SEQUENCE OF T11ZsActivateEntry 2682 MAX-ACCESS not-accessible 2683 STATUS current 2684 DESCRIPTION 2685 "This table provides a mechanism to allow a Zone Set 2686 to be activated on a fabric." 2687 ::= { t11ZsConfiguration 9 } 2689 t11ZsActivateEntry OBJECT-TYPE 2690 SYNTAX T11ZsActivateEntry 2691 MAX-ACCESS not-accessible 2692 STATUS current 2693 DESCRIPTION 2694 "Each entry reflects the state of the activation of a 2695 Zone Set by a particular switch (identified by values 2696 of fcmInstanceIndex and fcmSwitchIndex) on a particular 2697 fabric (identified by the value of 2698 t11ZsServerFabricIndex)." 2699 INDEX { fcmInstanceIndex, fcmSwitchIndex, 2700 t11ZsServerFabricIndex } 2701 ::= { t11ZsActivateTable 1 } 2703 T11ZsActivateEntry ::= SEQUENCE { 2704 t11ZsActivateRequest Unsigned32, 2705 t11ZsActivateDeactivate INTEGER, 2706 t11ZsActivateResult INTEGER, 2707 t11ZsActivateFailCause SnmpAdminString, 2708 t11ZsActivateFailDomainId FcDomainIdOrZero 2709 } 2711 t11ZsActivateRequest OBJECT-TYPE 2712 SYNTAX Unsigned32 (0..4294967295) 2713 MAX-ACCESS read-write 2714 STATUS current 2715 DESCRIPTION 2716 "Setting this object to a value is a request for a 2717 Zone Set to be activated on the fabric which is 2718 represented by this row. The Zone Set to be 2719 activated is the one for which t11ZsSetIndex has 2720 the same value. 2722 If a Zone Set is already active on a fabric when a 2723 request is made to activate a different one on that 2724 fabric, then the existing Zone Set is automatically 2725 deactivated and the specified Zone Set is activated 2726 in its place. 2728 The value of this object when read is always 0." 2729 ::= { t11ZsActivateEntry 1 } 2731 t11ZsActivateDeactivate OBJECT-TYPE 2732 SYNTAX INTEGER { 2733 deactivate(1), 2734 noop(2) 2735 } 2736 MAX-ACCESS read-write 2737 STATUS current 2738 DESCRIPTION 2739 "Setting this object to 'deactivate' is a request 2740 to deactivate the currently active Zone Set on 2741 a fabric. 2743 Note that the deactivation of the active Zone Set 2744 allows all ports to communicate or no ports to 2745 communicate depending on the current Default Zone 2746 behaviour. 2748 No action is taken if this object is set to 'noop'. 2749 When read, the value of this object is always 'noop'." 2750 ::= { t11ZsActivateEntry 2 } 2752 t11ZsActivateResult OBJECT-TYPE 2753 SYNTAX INTEGER { 2754 activateSuccess(1), 2755 activateFailure(2), 2756 deactivateSuccess(3), 2757 deactivateFailure(4), 2758 inProgress(5), 2759 none(6) 2760 } 2761 MAX-ACCESS read-only 2762 STATUS current 2763 DESCRIPTION 2764 "This object indicates the outcome of the most recent 2765 activation/deactivation using this entry. 2767 When the value of this object is 'inProgress', the 2768 values of the corresponding instances of 2769 t11ZsActivateRequest and t11ZsActivateDeactivate 2770 cannot be modified. 2772 The value 'none' indicates activation/de-activation 2773 has not been attempted since the last restart of 2774 the management system." 2775 ::= { t11ZsActivateEntry 3 } 2777 t11ZsActivateFailCause OBJECT-TYPE 2778 SYNTAX SnmpAdminString (SIZE (0..64)) 2779 MAX-ACCESS read-only 2780 STATUS current 2781 DESCRIPTION 2782 "A textual message indicating the reason for the 2783 most recent failure of a Zone Set activation or 2784 de-activation, or the zero-length string if no 2785 information is available (e.g., because the 2786 corresponding instance of t11ZsActivateResult 2787 has the value 'none'). 2789 When the corresponding instance of 2790 t11ZsActivateResult is either 'activateFailure' 2791 or 'deactivateFailure', the value of this object 2792 indicates the reason for that failure." 2793 ::= { t11ZsActivateEntry 4 } 2795 t11ZsActivateFailDomainId OBJECT-TYPE 2796 SYNTAX FcDomainIdOrZero 2797 MAX-ACCESS read-only 2798 STATUS current 2799 DESCRIPTION 2800 "If the failure cause (as indicated by 2801 t11ZsSetFailCause) was specific to a particular 2802 device, this object contains the Domain_ID of that 2803 device. Otherwise, this object contains zero." 2804 ::= { t11ZsActivateEntry 5 } 2806 -- 2807 -- t11ZsActiveTable 2808 -- 2810 t11ZsActiveTable OBJECT-TYPE 2811 SYNTAX SEQUENCE OF T11ZsActiveEntry 2812 MAX-ACCESS not-accessible 2813 STATUS current 2814 DESCRIPTION 2815 "A table containing information on the currently 2816 enforced/active Zone Set on each fabric. 2817 An active Zone Set cannot be modified. 2818 This table will be empty when no Zone Set is 2819 activated." 2820 ::= { t11ZsConfiguration 10 } 2822 t11ZsActiveEntry OBJECT-TYPE 2823 SYNTAX T11ZsActiveEntry 2824 MAX-ACCESS not-accessible 2825 STATUS current 2826 DESCRIPTION 2827 "Each entry represents an active Zone Set of a 2828 particular fabric (identified by the value of 2829 t11ZsServerFabricIndex), according to a particular 2830 switch (identified by values of fcmInstanceIndex and 2831 fcmSwitchIndex)." 2832 INDEX { fcmInstanceIndex, fcmSwitchIndex, 2833 t11ZsServerFabricIndex } 2834 ::= { t11ZsActiveTable 1 } 2836 T11ZsActiveEntry ::= SEQUENCE { 2837 t11ZsActiveZoneSetName T11ZoningName, 2838 t11ZsActiveActivateTime TimeStamp 2839 } 2841 t11ZsActiveZoneSetName OBJECT-TYPE 2842 SYNTAX T11ZoningName 2843 MAX-ACCESS read-only 2844 STATUS current 2845 DESCRIPTION 2846 "The name of this Zone Set on this fabric." 2847 ::= { t11ZsActiveEntry 1 } 2849 t11ZsActiveActivateTime OBJECT-TYPE 2850 SYNTAX TimeStamp 2851 MAX-ACCESS read-only 2852 STATUS current 2853 DESCRIPTION 2854 "The value of sysUpTime at which this entry was most 2855 recently activated. If this row was activated prior to 2856 the last re-initialization of the local network management 2857 system, then this object will contain a zero value." 2858 ::= { t11ZsActiveEntry 2 } 2860 -- 2861 -- Zones in the Active/Enforced Zone Set 2862 -- 2864 t11ZsActiveZoneTable OBJECT-TYPE 2865 SYNTAX SEQUENCE OF T11ZsActiveZoneEntry 2866 MAX-ACCESS not-accessible 2867 STATUS current 2868 DESCRIPTION 2869 "This table contains all the Zones that are present in 2870 the active Zone Sets on all fabrics." 2871 ::= { t11ZsConfiguration 11 } 2873 t11ZsActiveZoneEntry OBJECT-TYPE 2874 SYNTAX T11ZsActiveZoneEntry 2875 MAX-ACCESS not-accessible 2876 STATUS current 2877 DESCRIPTION 2878 "Each entry represents a Zone in the active Zone Set 2879 of a particular fabric (identified by the value of 2880 t11ZsServerFabricIndex), according to a particular 2881 switch (identified by values of fcmInstanceIndex and 2882 fcmSwitchIndex)." 2883 INDEX { fcmInstanceIndex, fcmSwitchIndex, 2884 t11ZsServerFabricIndex, t11ZsActiveZoneIndex } 2885 ::= { t11ZsActiveZoneTable 1 } 2887 T11ZsActiveZoneEntry ::= SEQUENCE { 2888 t11ZsActiveZoneIndex Unsigned32, 2889 t11ZsActiveZoneName T11ZoningName, 2890 t11ZsActiveZoneBroadcastZoning TruthValue, 2891 t11ZsActiveZoneHardZoning TruthValue 2892 } 2894 t11ZsActiveZoneIndex OBJECT-TYPE 2895 SYNTAX Unsigned32 (1..4294967295) 2896 MAX-ACCESS not-accessible 2897 STATUS current 2898 DESCRIPTION 2899 "An index value which uniquely identifies this 2900 this Zone within the active Zone Set on a 2901 particular fabric." 2902 ::= { t11ZsActiveZoneEntry 1 } 2904 t11ZsActiveZoneName OBJECT-TYPE 2905 SYNTAX T11ZoningName 2906 MAX-ACCESS read-only 2907 STATUS current 2908 DESCRIPTION 2909 "The name of this Zone." 2910 ::= { t11ZsActiveZoneEntry 2 } 2912 t11ZsActiveZoneBroadcastZoning OBJECT-TYPE 2913 SYNTAX TruthValue 2914 MAX-ACCESS read-only 2915 STATUS current 2916 DESCRIPTION 2917 "This object indicates whether broadcast Zoning is 2918 enabled on this Zone. If broadcast Zoning is enabled, 2919 then broadcast frames generated by a member in this 2920 Zone will be restricted to members in this Zone. 2922 This object is only instantiated in Enhanced mode." 2923 ::= { t11ZsActiveZoneEntry 3 } 2925 t11ZsActiveZoneHardZoning OBJECT-TYPE 2926 SYNTAX TruthValue 2927 MAX-ACCESS read-only 2928 STATUS current 2929 DESCRIPTION 2930 "This object indicates whether hard Zoning is 2931 enabled on this Zone. 2933 This object is only instantiated in Enhanced mode." 2934 ::= { t11ZsActiveZoneEntry 4 } 2936 -- 2937 -- Zone Members in the Active/Enforced Zone Set 2938 -- 2940 t11ZsActiveZoneMemberTable OBJECT-TYPE 2941 SYNTAX SEQUENCE OF T11ZsActiveZoneMemberEntry 2942 MAX-ACCESS not-accessible 2943 STATUS current 2944 DESCRIPTION 2945 "This table contains all members of all Zones 2946 within the active Zone Set on any fabric." 2947 ::= { t11ZsConfiguration 12 } 2949 t11ZsActiveZoneMemberEntry OBJECT-TYPE 2950 SYNTAX T11ZsActiveZoneMemberEntry 2951 MAX-ACCESS not-accessible 2952 STATUS current 2953 DESCRIPTION 2954 "Each entry represents a member of a Zone in the active 2955 Zone Set of a particular fabric (identified by the value 2956 t11ZsServerFabricIndex), according to a particular 2957 switch (identified by values of fcmInstanceIndex and 2958 fcmSwitchIndex)." 2959 INDEX { fcmInstanceIndex, fcmSwitchIndex, 2960 t11ZsServerFabricIndex, 2961 t11ZsActiveZoneIndex, t11ZsActiveZoneMemberIndex } 2962 ::= { t11ZsActiveZoneMemberTable 1 } 2964 T11ZsActiveZoneMemberEntry ::= SEQUENCE { 2965 t11ZsActiveZoneMemberIndex Unsigned32, 2966 t11ZsActiveZoneMemberFormat T11ZsZoneMemberType, 2967 t11ZsActiveZoneMemberID OCTET STRING 2968 } 2970 t11ZsActiveZoneMemberIndex OBJECT-TYPE 2971 SYNTAX Unsigned32 (1..4294967295) 2972 MAX-ACCESS not-accessible 2973 STATUS current 2974 DESCRIPTION 2975 "An index value which uniquely identifies this 2976 member amongst the members of a particular Zone 2977 in the active Zone Set on a particular fabric." 2979 ::= { t11ZsActiveZoneMemberEntry 1 } 2981 t11ZsActiveZoneMemberFormat OBJECT-TYPE 2982 SYNTAX T11ZsZoneMemberType 2983 MAX-ACCESS read-only 2984 STATUS current 2985 DESCRIPTION 2986 "This object identifies the identifier format of the 2987 corresponding instance of t11ZsActiveZoneMemberID." 2988 ::= { t11ZsActiveZoneMemberEntry 2 } 2990 t11ZsActiveZoneMemberID OBJECT-TYPE 2991 SYNTAX OCTET STRING (SIZE (1..255)) 2992 MAX-ACCESS read-only 2993 STATUS current 2994 DESCRIPTION 2995 "This value of this object identifies the member 2996 using the format specified in the corresponding 2997 instance of t11ZsActiveZoneMemberFormat." 2998 ::= { t11ZsActiveZoneMemberEntry 3 } 3000 -- 3001 -- Zone Attributes in the Active/Enforced Zone Set 3002 -- 3004 t11ZsActiveAttribTable OBJECT-TYPE 3005 SYNTAX SEQUENCE OF T11ZsActiveAttribEntry 3006 MAX-ACCESS not-accessible 3007 STATUS current 3008 DESCRIPTION 3009 "This table contains information about some of the 3010 Attributes of the Zones within the active Zone Set 3011 on each fabric. 3013 This table contains all the types of attributes 3014 which might apply zero, one, or more times to a Zone. 3015 Attributes which apply once and only to a Zone are 3016 specified in the t11ZsActiveZoneTable. 3018 This table will always be empty in Basic mode. 3019 It will also be empty if there are no Zones in 3020 any active Zone Set having any of the applicable 3021 types of attributes." 3022 ::= { t11ZsConfiguration 13 } 3024 t11ZsActiveAttribEntry OBJECT-TYPE 3025 SYNTAX T11ZsActiveAttribEntry 3026 MAX-ACCESS not-accessible 3027 STATUS current 3028 DESCRIPTION 3029 "Each entry contains an Attribute of a particular 3030 Zone in the active Zone Set of a particular fabric 3031 (identified by the value of t11ZsServerFabricIndex), 3032 according to a particular switch (identified by 3033 values of fcmInstanceIndex and fcmSwitchIndex)." 3034 INDEX { fcmInstanceIndex, fcmSwitchIndex, 3035 t11ZsServerFabricIndex, 3036 t11ZsActiveZoneIndex, t11ZsActiveAttribIndex } 3037 ::= { t11ZsActiveAttribTable 1 } 3039 T11ZsActiveAttribEntry ::= SEQUENCE { 3040 t11ZsActiveAttribIndex Unsigned32, 3041 t11ZsActiveAttribType Unsigned32, 3042 t11ZsActiveAttribValue OCTET STRING 3043 } 3045 t11ZsActiveAttribIndex OBJECT-TYPE 3046 SYNTAX Unsigned32 (1..4294967295) 3047 MAX-ACCESS not-accessible 3048 STATUS current 3049 DESCRIPTION 3050 "An index value which uniquely identifies this 3051 attribute amongst the other attributes for a 3052 particular Zone in the active Zone Set on a 3053 particular fabric." 3054 ::= { t11ZsActiveAttribEntry 1 } 3056 t11ZsActiveAttribType OBJECT-TYPE 3057 SYNTAX Unsigned32 (0..65535) 3058 MAX-ACCESS read-only 3059 STATUS current 3060 DESCRIPTION 3061 "The type of attribute: 3063 0001 - Protocol 3064 00E0 (hex) - Vendor Specific 3066 Note that type 2 (Hard) and type 3 (Broadcast) 3067 do not need to be represented here, because they 3068 are represented by t11ZsActiveZoneBroadcastZoning and 3069 t11ZsActiveZoneHardZoning." 3070 REFERENCE 3071 "Fibre Channel - Generic Services-5 (FC-GS-5), 3072 ANSI INCITS 427-2006, section 6.4.8.3.8, table 249." 3073 ::= { t11ZsActiveAttribEntry 2 } 3075 t11ZsActiveAttribValue OBJECT-TYPE 3076 SYNTAX OCTET STRING (SIZE (0..252)) 3077 MAX-ACCESS read-only 3078 STATUS current 3079 DESCRIPTION 3080 "The value of the attribute, formatted according to 3081 its type as indicated by the corresponding instance 3082 of t11ZsActiveAttribType. 3084 As specified in FC-GS-5, the length of an attribute 3085 value is at least 4 bytes, and if necessary, the value 3086 is appended with zero bytes so that the length is a 3087 multiple of four. For a Vendor Specific attribute 3088 value, the first 8 bytes contains the T10 Vendor ID 3089 as described in FC-GS-5." 3090 REFERENCE 3091 "Fibre Channel - Generic Services-5 (FC-GS-5), 3092 ANSI INCITS 427-2006, section 6.4.8.3.8." 3093 ::= { t11ZsActiveAttribEntry 3 } 3095 -- 3096 -- Zone Server Statistics 3097 -- 3099 t11ZsStatsTable OBJECT-TYPE 3100 SYNTAX SEQUENCE OF T11ZsStatsEntry 3101 MAX-ACCESS not-accessible 3102 STATUS current 3103 DESCRIPTION 3104 "A table of statistics maintained by Zone Servers." 3105 ::= { t11ZsStatistics 1 } 3107 t11ZsStatsEntry OBJECT-TYPE 3108 SYNTAX T11ZsStatsEntry 3109 MAX-ACCESS not-accessible 3110 STATUS current 3111 DESCRIPTION 3112 "A set of statistics for a Zone Server on a 3113 particular fabric (identified by the value of 3114 t11ZsServerFabricIndex) on a particular switch 3115 (identified by values of fcmInstanceIndex and 3116 fcmSwitchIndex)." 3117 INDEX { fcmInstanceIndex, fcmSwitchIndex, 3118 t11ZsServerFabricIndex } 3119 ::= { t11ZsStatsTable 1 } 3121 T11ZsStatsEntry ::= SEQUENCE { 3122 t11ZsOutMergeRequests Counter32, 3123 t11ZsInMergeAccepts Counter32, 3124 t11ZsInMergeRequests Counter32, 3125 t11ZsOutMergeAccepts Counter32, 3126 t11ZsOutChangeRequests Counter32, 3127 t11ZsInChangeAccepts Counter32, 3128 t11ZsInChangeRequests Counter32, 3129 t11ZsOutChangeAccepts Counter32, 3130 t11ZsInZsRequests Counter32, 3131 t11ZsOutZsRejects Counter32 3132 } 3134 t11ZsOutMergeRequests OBJECT-TYPE 3135 SYNTAX Counter32 3136 MAX-ACCESS read-only 3137 STATUS current 3138 DESCRIPTION 3139 "The number of Merge Request Frames sent by this Zone 3140 Server to other Zone Servers in the same fabric. 3142 This counter has no discontinuities other than those 3143 which all Counter32's have when sysUpTime=0." 3144 ::= { t11ZsStatsEntry 1 } 3146 t11ZsInMergeAccepts OBJECT-TYPE 3147 SYNTAX Counter32 3148 MAX-ACCESS read-only 3149 STATUS current 3150 DESCRIPTION 3151 "The number of Merge Accept Frames received by this Zone 3152 Server from other Zone Servers in the same fabric. 3154 This counter has no discontinuities other than those 3155 which all Counter32's have when sysUpTime=0." 3156 ::= { t11ZsStatsEntry 2 } 3158 t11ZsInMergeRequests OBJECT-TYPE 3159 SYNTAX Counter32 3160 MAX-ACCESS read-only 3161 STATUS current 3162 DESCRIPTION 3163 "The number of Merge Request Frames received by this Zone 3164 Server from other Zone Servers in the same fabric. 3166 This counter has no discontinuities other than those 3167 which all Counter32's have when sysUpTime=0." 3168 ::= { t11ZsStatsEntry 3 } 3170 t11ZsOutMergeAccepts OBJECT-TYPE 3171 SYNTAX Counter32 3172 MAX-ACCESS read-only 3173 STATUS current 3174 DESCRIPTION 3175 "The number of Merge Accept Frames sent by this Zone 3176 Server to other Zone Servers in the same fabric. 3178 This counter has no discontinuities other than those 3179 which all Counter32's have when sysUpTime=0." 3180 ::= { t11ZsStatsEntry 4 } 3182 t11ZsOutChangeRequests OBJECT-TYPE 3183 SYNTAX Counter32 3184 MAX-ACCESS read-only 3185 STATUS current 3186 DESCRIPTION 3187 "The number of change requests sent (via the Fabric 3188 Management Session Protocol) by this Zone Server to 3189 other Zone Servers in the same fabric. 3191 This includes Acquire Change Authorization requests, Stage 3192 Fabric Config Update requests, Update Fabric Config requests 3193 and Release Change Authorization requests. It also includes 3194 the corresponding types of requests defined by the Enhanced 3195 Commit Service. 3197 This counter has no discontinuities other than those 3198 which all Counter32's have when sysUpTime=0." 3199 REFERENCE 3200 "Fibre Channel - Switch Fabric-4 (FC-SW-4), 3201 ANSI INCITS 418-2006, April 2006, sections 10.6 and 13." 3202 ::= { t11ZsStatsEntry 5 } 3204 t11ZsInChangeAccepts OBJECT-TYPE 3205 SYNTAX Counter32 3206 MAX-ACCESS read-only 3207 STATUS current 3208 DESCRIPTION 3209 "The number of SW_ACC messages received from other Zone 3210 Servers in the same fabric (according to the Fabric 3211 Management Session Protocol) in response to change 3212 requests by this Zone Server. 3214 This includes SW_ACC messages received in response to 3215 Acquire Change Authorization requests, to Stage Fabric 3216 Config Update requests, to Update Fabric Config requests 3217 and to Release Change Authorization requests. It also 3218 includes responses to the corresponding types of requests 3219 defined for the Enhanced Commit Service. 3221 This counter has no discontinuities other than those 3222 which all Counter32's have when sysUpTime=0." 3223 REFERENCE 3224 "Fibre Channel - Switch Fabric-4 (FC-SW-4), 3225 ANSI INCITS 418-2006, April 2006, sections 10.6 and 13." 3226 ::= { t11ZsStatsEntry 6 } 3228 t11ZsInChangeRequests OBJECT-TYPE 3229 SYNTAX Counter32 3230 MAX-ACCESS read-only 3231 STATUS current 3232 DESCRIPTION 3233 "The number of change requests received (via the Fabric 3234 Management Session Protocol) by this Zone Server from 3235 other Zone Servers in the same fabric. 3237 This includes Acquire Change Authorization requests, Stage 3238 Fabric Config Update requests, Update Fabric Config requests 3239 and Release Change Authorization requests. It also includes 3240 the corresponding types of requests defined by the Enhanced 3241 Commit Service. 3243 This counter has no discontinuities other than those 3244 which all Counter32's have when sysUpTime=0." 3245 REFERENCE 3246 "Fibre Channel - Switch Fabric-4 (FC-SW-4), 3247 ANSI INCITS 418-2006, April 2006, sections 10.6 and 13." 3248 ::= { t11ZsStatsEntry 7 } 3250 t11ZsOutChangeAccepts OBJECT-TYPE 3251 SYNTAX Counter32 3252 MAX-ACCESS read-only 3253 STATUS current 3254 DESCRIPTION 3255 "The number of SW_ACC messages sent by this Zone Server 3256 (according to the Fabric Management Session Protocol) in 3257 response to change requests from other Zone Servers in 3258 the same fabric. 3260 This includes SW_ACC messages sent in response to 3261 Acquire Change Authorization requests, to Stage Fabric 3262 Config Update requests, to Update Fabric Config requests 3263 and to Release Change Authorization requests. It also 3264 includes responses to the corresponding types of requests 3265 defined for the Enhanced Commit Service. 3267 This counter has no discontinuities other than those 3268 which all Counter32's have when sysUpTime=0." 3269 REFERENCE 3270 "Fibre Channel - Switch Fabric-4 (FC-SW-4), 3271 ANSI INCITS 418-2006, April 2006, sections 10.6 and 13." 3272 ::= { t11ZsStatsEntry 8 } 3274 t11ZsInZsRequests OBJECT-TYPE 3275 SYNTAX Counter32 3276 MAX-ACCESS read-only 3277 STATUS current 3278 DESCRIPTION 3279 "The number of Zone Server requests received by this 3280 Zone Server on this fabric, both those received in 3281 Basic mode and those received in Enhanced mode. 3283 This counter has no discontinuities other than those 3284 which all Counter32's have when sysUpTime=0." 3285 ::= { t11ZsStatsEntry 9 } 3287 t11ZsOutZsRejects OBJECT-TYPE 3288 SYNTAX Counter32 3289 MAX-ACCESS read-only 3290 STATUS current 3291 DESCRIPTION 3292 "The number of Zone Server requests rejected by this 3293 Zone Server on this fabric, both those rejected in 3294 Basic mode and those rejected in Enhanced mode. 3296 This counter has no discontinuities other than those 3297 which all Counter32's have when sysUpTime=0." 3298 ::= { t11ZsStatsEntry 10 } 3300 -- 3301 -- Notification Control Table 3302 -- 3304 t11ZsNotifyControlTable OBJECT-TYPE 3305 SYNTAX SEQUENCE OF T11ZsNotifyControlEntry 3306 MAX-ACCESS not-accessible 3307 STATUS current 3308 DESCRIPTION 3309 "A table of control information for notifications 3310 generated due to Zone Server events." 3311 ::= { t11ZsConfiguration 14 } 3313 t11ZsNotifyControlEntry OBJECT-TYPE 3314 SYNTAX T11ZsNotifyControlEntry 3315 MAX-ACCESS not-accessible 3316 STATUS current 3317 DESCRIPTION 3318 "Each entry contains notification control information 3319 specific to a Zone Server for a particular fabric 3320 (identified by the value of t11ZsServerFabricIndex) 3321 on a particular switch (identified by values of 3322 fcmInstanceIndex and fcmSwitchIndex). 3324 The persistence across reboots of writable values in 3325 a row of this table is specified by the instance of 3326 t11ZsServerDatabaseStorageType which is INDEX-ed by 3327 the same values of fcmInstanceIndex, fcmSwitchIndex 3328 and t11ZsServerFabricIndex." 3329 INDEX { fcmInstanceIndex, fcmSwitchIndex, 3330 t11ZsServerFabricIndex } 3331 ::= { t11ZsNotifyControlTable 1 } 3333 T11ZsNotifyControlEntry ::= SEQUENCE { 3334 t11ZsNotifyRequestRejectEnable TruthValue, 3335 t11ZsNotifyMergeFailureEnable TruthValue, 3336 t11ZsNotifyMergeSuccessEnable TruthValue, 3337 t11ZsNotifyDefZoneChangeEnable TruthValue, 3338 t11ZsNotifyActivateEnable TruthValue, 3339 t11ZsRejectCtCommandString OCTET STRING, 3340 t11ZsRejectRequestSource FcNameIdOrZero, 3341 t11ZsRejectReasonCode T11NsGs4RejectReasonCode, 3342 t11ZsRejectReasonCodeExp T11ZsRejectReasonExplanation, 3343 t11ZsRejectReasonVendorCode OCTET STRING 3344 } 3346 t11ZsNotifyRequestRejectEnable OBJECT-TYPE 3347 SYNTAX TruthValue 3348 MAX-ACCESS read-write 3349 STATUS current 3350 DESCRIPTION 3351 "This object specifies whether t11ZsRequestRejectNotify 3352 notifications should be generated by the Zone Server 3353 for this fabric." 3354 ::= { t11ZsNotifyControlEntry 1 } 3356 t11ZsNotifyMergeFailureEnable OBJECT-TYPE 3357 SYNTAX TruthValue 3358 MAX-ACCESS read-write 3359 STATUS current 3360 DESCRIPTION 3361 "This object specifies whether t11ZsMergeFailureNotify 3362 notifications should be generated by the Zone Server 3363 for this fabric." 3364 ::= { t11ZsNotifyControlEntry 2 } 3366 t11ZsNotifyMergeSuccessEnable OBJECT-TYPE 3367 SYNTAX TruthValue 3368 MAX-ACCESS read-write 3369 STATUS current 3370 DESCRIPTION 3371 "This object specifies whether t11ZsMergeSuccessNotify 3372 notifications should be generated by the Zone Server 3373 for this fabric." 3374 ::= { t11ZsNotifyControlEntry 3 } 3376 t11ZsNotifyDefZoneChangeEnable OBJECT-TYPE 3377 SYNTAX TruthValue 3378 MAX-ACCESS read-write 3379 STATUS current 3380 DESCRIPTION 3381 "This object specifies whether t11ZsDefZoneChangeNotify 3382 notifications should be generated by the Zone Server 3383 for this fabric." 3384 ::= { t11ZsNotifyControlEntry 4 } 3386 t11ZsNotifyActivateEnable OBJECT-TYPE 3387 SYNTAX TruthValue 3388 MAX-ACCESS read-write 3389 STATUS current 3390 DESCRIPTION 3391 "This object specifies whether t11ZsActivateNotify 3392 notifications should be generated by the Zone Server 3393 for this fabric." 3394 ::= { t11ZsNotifyControlEntry 5 } 3396 t11ZsRejectCtCommandString OBJECT-TYPE 3397 SYNTAX OCTET STRING (SIZE (0..255)) 3398 MAX-ACCESS read-only 3399 STATUS current 3400 DESCRIPTION 3401 "The binary content of the Zone Server request, 3402 formatted as an octet string (in network byte 3403 order) containing the CT_IU, as described in 3404 Table 2 of [FC-GS-5] (including the preamble), 3405 which was most recently rejected by the 3406 Zone Server for this fabric. 3408 This object contains the zero-length string 3409 if and when the CT-IU's content is unavailable. 3411 When the length of this object is 255 octets, it 3412 contains the first 255 octets of the CT-IU (in 3413 network-byte order)." 3414 ::= { t11ZsNotifyControlEntry 6 } 3416 t11ZsRejectRequestSource OBJECT-TYPE 3417 SYNTAX FcNameIdOrZero 3418 MAX-ACCESS read-only 3419 STATUS current 3420 DESCRIPTION 3421 "The WWN which was the source of the CT_IU 3422 contained in the corresponding instance of 3423 t11ZsRejectCtCommandString." 3424 ::= { t11ZsNotifyControlEntry 7 } 3426 t11ZsRejectReasonCode OBJECT-TYPE 3427 SYNTAX T11NsGs4RejectReasonCode 3428 MAX-ACCESS read-only 3429 STATUS current 3430 DESCRIPTION 3431 "The reason code corresponding to the most recent 3432 rejection of a request by the Zone Server for 3433 this fabric." 3434 ::= { t11ZsNotifyControlEntry 8 } 3436 t11ZsRejectReasonCodeExp OBJECT-TYPE 3437 SYNTAX T11ZsRejectReasonExplanation 3438 MAX-ACCESS read-only 3439 STATUS current 3440 DESCRIPTION 3441 "When the value of t11ZsRejectReasonCode is 3442 'Unable to perform command request', this 3443 object contains the corresponding reason code 3444 explanation." 3445 ::= { t11ZsNotifyControlEntry 9 } 3447 t11ZsRejectReasonVendorCode OBJECT-TYPE 3448 SYNTAX OCTET STRING (SIZE (1)) 3449 MAX-ACCESS read-only 3450 STATUS current 3451 DESCRIPTION 3452 "When the value of t11ZsRejectReasonCode is 3453 'Vendor Specific Error', this object contains 3454 the corresponding vendor-specific reason code." 3455 ::= { t11ZsNotifyControlEntry 10 } 3457 t11ZsFabricIndex OBJECT-TYPE 3458 SYNTAX Unsigned32 (0..4096) 3459 MAX-ACCESS accessible-for-notify 3460 STATUS current 3461 DESCRIPTION 3462 "This object contains either a value of 3463 T11FabricIndex to identify the fabric on which 3464 some occurrence has caused a notification to be 3465 generated, or it has the value 4096 to indicate 3466 all applicable fabrics." 3467 ::= { t11ZsConfiguration 15 } 3469 -- Notifications 3471 t11ZsRequestRejectNotify NOTIFICATION-TYPE 3472 OBJECTS { t11FamLocalSwitchWwn, 3473 t11ZsRejectRequestSource, 3474 t11ZsRejectCtCommandString, 3475 t11ZsRejectReasonCode, 3476 t11ZsRejectReasonCodeExp, 3477 t11ZsRejectReasonVendorCode } 3478 STATUS current 3479 DESCRIPTION 3480 "This notification is generated whenever a Zone Server 3481 (indicated by the value of t11FamLocalSwitchWwn) rejects 3482 a request. 3484 The value of t11ZsRejectCtCommandString indicates the 3485 rejected request, and the values of t11ZsRejectReasonCode, 3486 t11ZsRejectReasonCodeExp and t11ZsRejectReasonVendorCode 3487 indicate the reason for the rejection. The value of 3488 t11ZsRequestClient indicates the source of the request." 3489 ::= { t11ZsMIBNotifications 1 } 3491 t11ZsMergeFailureNotify NOTIFICATION-TYPE 3492 OBJECTS { ifIndex, t11ZsFabricIndex } 3493 STATUS current 3494 DESCRIPTION 3495 "This notification indicates that a Zone merge 3496 failure has occurred on the fabric indicated by the 3497 value of t11ZsFabricIndex, on the interface 3498 indicated by the value of ifIndex. 3500 If multiple Virtual Fabrics are configured on an 3501 interface, and all have a Zone merge failure 3502 at the same time, then just one notification is 3503 generated and t11ZsFabricIndex has the value 4096." 3504 ::= { t11ZsMIBNotifications 2 } 3506 t11ZsMergeSuccessNotify NOTIFICATION-TYPE 3507 OBJECTS { ifIndex, t11ZsFabricIndex } 3508 STATUS current 3509 DESCRIPTION 3510 "This notification indicates that a successful Zone 3511 merge has occurred on the fabric indicated by the 3512 value of t11ZsFabricIndex, on the interface 3513 indicated by the value of ifIndex. 3515 If multiple Virtual Fabrics are configured on an 3516 interface, and all have a successful Zone Merge 3517 at the same time, then just one notification is 3518 generated and t11ZsFabricIndex has the value 4096." 3519 ::= { t11ZsMIBNotifications 3 } 3521 t11ZsDefZoneChangeNotify NOTIFICATION-TYPE 3522 OBJECTS { t11ZsServerDefaultZoneSetting } 3523 STATUS current 3524 DESCRIPTION 3525 "This notification indicates that the 3526 value of a Default Zone Setting has changed. 3527 The value of t11ZsServerDefaultZoneSetting 3528 contains the value after the change." 3529 ::= { t11ZsMIBNotifications 4 } 3531 t11ZsActivateNotify NOTIFICATION-TYPE 3532 OBJECTS { t11FamLocalSwitchWwn, t11ZsActivateResult } 3533 STATUS current 3534 DESCRIPTION 3535 "This notification is generated whenever a switch 3536 (indicated by the value of t11FamLocalSwitchWwn) 3537 activates/deactivates a Zone Set on a fabric. 3538 The t11ZsActivateResult object denotes the outcome 3539 of the activation/deactivation." 3540 ::= { t11ZsMIBNotifications 5 } 3542 -- Conformance 3544 t11ZsMIBCompliances OBJECT IDENTIFIER ::= { t11ZsMIBConformance 1 } 3545 t11ZsMIBGroups OBJECT IDENTIFIER ::= { t11ZsMIBConformance 2 } 3547 t11ZsMIBCompliance MODULE-COMPLIANCE 3548 STATUS current 3549 DESCRIPTION 3550 "The compliance statement for entities which 3551 implement the Zone Server." 3552 MODULE MANDATORY-GROUPS {t11ZsBasicGroup, 3553 t11ZsNotificationControlGroup, 3554 t11ZsNotificationGroup } 3556 GROUP t11ZsEnhancedModeGroup 3557 DESCRIPTION 3558 "This group is mandatory only for those systems 3559 with Zone Servers which support Enhanced Mode." 3561 GROUP t11ZsActivateGroup 3562 DESCRIPTION 3563 "Only entities that provide write access for 3564 activating a Zone Set support need to support 3565 this group." 3567 GROUP t11ZsStatisticsGroup 3568 DESCRIPTION 3569 "These counters, containing Zone Server statistics, 3570 are mandatory only for those systems which count 3571 such events." 3573 OBJECT t11ZsSetRowStatus 3574 SYNTAX INTEGER { active(1) } 3575 MIN-ACCESS read-only 3576 DESCRIPTION 3577 "Write access is not required." 3579 OBJECT t11ZsZoneRowStatus 3580 SYNTAX INTEGER { active(1) } 3581 MIN-ACCESS read-only 3582 DESCRIPTION 3583 "Write access is not required." 3585 OBJECT t11ZsSetZoneRowStatus 3586 SYNTAX INTEGER { active(1) } 3587 MIN-ACCESS read-only 3588 DESCRIPTION 3589 "Write access is not required." 3591 OBJECT t11ZsAliasRowStatus 3592 SYNTAX INTEGER { active(1) } 3593 MIN-ACCESS read-only 3594 DESCRIPTION 3595 "Write access is not required." 3597 OBJECT t11ZsZoneMemberRowStatus 3598 SYNTAX INTEGER { active(1) } 3599 MIN-ACCESS read-only 3600 DESCRIPTION 3601 "Write access is not required." 3603 OBJECT t11ZsAttribBlockRowStatus 3604 SYNTAX INTEGER { active(1) } 3605 MIN-ACCESS read-only 3606 DESCRIPTION 3607 "Write access is not required." 3609 OBJECT t11ZsAttribRowStatus 3610 SYNTAX INTEGER { active(1) } 3611 MIN-ACCESS read-only 3612 DESCRIPTION 3613 "Write access is not required." 3615 OBJECT t11ZsServerDatabaseStorageType 3616 MIN-ACCESS read-only 3617 DESCRIPTION 3618 "Write access is not required." 3620 OBJECT t11ZsServerDistribute 3621 MIN-ACCESS read-only 3622 DESCRIPTION 3623 "Write access is not required." 3625 OBJECT t11ZsServerCommit 3626 MIN-ACCESS read-only 3627 DESCRIPTION 3628 "Write access is not required." 3630 OBJECT t11ZsServerReadFromDatabase 3631 MIN-ACCESS read-only 3632 DESCRIPTION 3633 "Write access is not required." 3635 OBJECT t11ZsServerOperationMode 3636 MIN-ACCESS read-only 3637 DESCRIPTION 3638 "Write access is not required." 3640 OBJECT t11ZsServerDefaultZoneSetting 3641 MIN-ACCESS read-only 3642 DESCRIPTION 3643 "Write access is not required." 3645 OBJECT t11ZsServerMergeControlSetting 3646 MIN-ACCESS read-only 3647 DESCRIPTION 3648 "Write access is not required." 3650 OBJECT t11ZsServerDefZoneBroadcast 3651 MIN-ACCESS read-only 3652 DESCRIPTION 3653 "Write access is not required." 3655 OBJECT t11ZsSetName 3656 MIN-ACCESS read-only 3657 DESCRIPTION 3658 "Write access is not required." 3660 OBJECT t11ZsZoneName 3661 MIN-ACCESS read-only 3662 DESCRIPTION 3663 "Write access is not required." 3665 OBJECT t11ZsZoneAttribBlock 3666 MIN-ACCESS read-only 3667 DESCRIPTION 3668 "Write access is not required." 3670 OBJECT t11ZsAliasName 3671 MIN-ACCESS read-only 3672 DESCRIPTION 3673 "Write access is not required." 3675 OBJECT t11ZsZoneMemberFormat 3676 MIN-ACCESS read-only 3677 DESCRIPTION 3678 "Write access is not required." 3680 OBJECT t11ZsZoneMemberID 3681 MIN-ACCESS read-only 3682 DESCRIPTION 3683 "Write access is not required." 3685 OBJECT t11ZsAttribBlockName 3686 MIN-ACCESS read-only 3687 DESCRIPTION 3688 "Write access is not required." 3690 OBJECT t11ZsAttribType 3691 MIN-ACCESS read-only 3692 DESCRIPTION 3693 "Write access is not required." 3695 OBJECT t11ZsAttribValue 3696 MIN-ACCESS read-only 3697 DESCRIPTION 3698 "Write access is not required." 3700 OBJECT t11ZsActivateRequest 3701 MIN-ACCESS read-only 3702 DESCRIPTION 3703 "Write access is not required." 3705 OBJECT t11ZsActivateDeactivate 3706 MIN-ACCESS read-only 3707 DESCRIPTION 3708 "Write access is not required." 3710 OBJECT t11ZsNotifyRequestRejectEnable 3711 MIN-ACCESS read-only 3712 DESCRIPTION 3713 "Write access is not required." 3715 OBJECT t11ZsNotifyMergeFailureEnable 3716 MIN-ACCESS read-only 3717 DESCRIPTION 3718 "Write access is not required." 3720 OBJECT t11ZsNotifyMergeSuccessEnable 3721 MIN-ACCESS read-only 3722 DESCRIPTION 3723 "Write access is not required." 3725 OBJECT t11ZsNotifyDefZoneChangeEnable 3726 MIN-ACCESS read-only 3727 DESCRIPTION 3728 "Write access is not required." 3730 OBJECT t11ZsNotifyActivateEnable 3731 MIN-ACCESS read-only 3732 DESCRIPTION 3733 "Write access is not required." 3735 ::= { t11ZsMIBCompliances 1 } 3737 -- Units of Conformance 3739 t11ZsBasicGroup OBJECT-GROUP 3740 OBJECTS { t11ZsServerCapabilityObject, 3741 t11ZsServerDatabaseStorageType, 3742 t11ZsServerDistribute, 3743 t11ZsServerResult, 3744 t11ZsServerReasonCode, 3745 t11ZsServerReasonCodeExp, 3746 t11ZsServerReasonVendorCode, 3747 t11ZsServerLastChange, 3748 t11ZsServerHardZoning, 3749 t11ZsServerReadFromDatabase, 3750 t11ZsServerOperationMode, 3751 t11ZsSetName, 3752 t11ZsSetRowStatus, 3753 t11ZsZoneName, 3754 t11ZsZoneAttribBlock, 3755 t11ZsZoneRowStatus, 3756 t11ZsSetZoneRowStatus, 3757 t11ZsZoneMemberFormat, 3758 t11ZsZoneMemberID, 3759 t11ZsZoneMemberRowStatus, 3760 t11ZsActiveZoneSetName, 3761 t11ZsActiveActivateTime, 3762 t11ZsActiveZoneName, 3763 t11ZsActiveZoneMemberFormat, 3764 t11ZsActiveZoneMemberID 3765 } 3766 STATUS current 3767 DESCRIPTION 3768 "A collection of objects for displaying and updating 3769 the Zone configuration of a Zone Server capable of 3770 operating in Basic mode." 3771 ::= { t11ZsMIBGroups 1 } 3773 t11ZsEnhancedModeGroup OBJECT-GROUP 3774 OBJECTS { t11ZsServerCommit, 3775 t11ZsServerChangeModeResult, 3776 t11ZsServerDefaultZoneSetting, 3777 t11ZsServerMergeControlSetting, 3778 t11ZsServerDefZoneBroadcast, 3779 t11ZsAliasName, 3780 t11ZsAliasRowStatus, 3781 t11ZsAttribBlockName, 3782 t11ZsAttribBlockRowStatus, 3783 t11ZsAttribType, 3784 t11ZsAttribValue, 3785 t11ZsAttribRowStatus, 3786 t11ZsActiveZoneBroadcastZoning, 3787 t11ZsActiveZoneHardZoning, 3788 t11ZsActiveAttribType, 3789 t11ZsActiveAttribValue 3790 } 3791 STATUS current 3792 DESCRIPTION 3793 "A collection of additional objects for displaying 3794 and updating the Zone configuration of a Zone Server 3795 capable of operating in Enhanced mode." 3796 ::= { t11ZsMIBGroups 2 } 3798 t11ZsStatisticsGroup OBJECT-GROUP 3799 OBJECTS { t11ZsOutMergeRequests, 3800 t11ZsInMergeAccepts, 3801 t11ZsInMergeRequests, 3802 t11ZsOutMergeAccepts, 3803 t11ZsOutChangeRequests, 3804 t11ZsInChangeAccepts, 3805 t11ZsInChangeRequests, 3806 t11ZsOutChangeAccepts, 3807 t11ZsInZsRequests, 3808 t11ZsOutZsRejects 3809 } 3810 STATUS current 3811 DESCRIPTION 3812 "A collection of objects for collecting Zone Server 3813 statistics information." 3814 ::= { t11ZsMIBGroups 3 } 3816 t11ZsNotificationControlGroup OBJECT-GROUP 3817 OBJECTS { t11ZsNotifyRequestRejectEnable, 3818 t11ZsNotifyMergeFailureEnable, 3819 t11ZsNotifyMergeSuccessEnable, 3820 t11ZsNotifyDefZoneChangeEnable, 3821 t11ZsNotifyActivateEnable, 3822 t11ZsRejectCtCommandString, 3823 t11ZsRejectRequestSource, 3824 t11ZsRejectReasonCode, 3825 t11ZsRejectReasonCodeExp, 3826 t11ZsRejectReasonVendorCode, 3827 t11ZsFabricIndex 3828 } 3829 STATUS current 3830 DESCRIPTION 3831 "A collection of notification control and 3832 notification information objects for monitoring 3833 Zone Server request rejection and Zone merge 3834 failures." 3835 ::= { t11ZsMIBGroups 4 } 3837 t11ZsActivateGroup OBJECT-GROUP 3838 OBJECTS { t11ZsActivateRequest, 3839 t11ZsActivateDeactivate, 3840 t11ZsActivateResult, 3841 t11ZsActivateFailCause, 3842 t11ZsActivateFailDomainId 3843 } 3844 STATUS current 3845 DESCRIPTION 3846 "A collection of objects which allow a Zone Set to 3847 be activated via SNMP SetRequests and provide the 3848 status and result of such an activation." 3849 ::= { t11ZsMIBGroups 5 } 3851 t11ZsNotificationGroup NOTIFICATION-GROUP 3852 NOTIFICATIONS { t11ZsRequestRejectNotify, 3853 t11ZsMergeFailureNotify, 3854 t11ZsMergeSuccessNotify, 3855 t11ZsDefZoneChangeNotify, 3856 t11ZsActivateNotify } 3857 STATUS current 3858 DESCRIPTION 3859 "A collection of notification(s) for monitoring 3860 Zone Server request rejection, Zone merge 3861 failures and successes and Default Zoning 3862 behavioural changes." 3863 ::= { t11ZsMIBGroups 6 } 3865 END 3866 8. Acknowledgements 3868 This document was originally developed and approved by the INCITS 3869 Task Group T11.5 (http://www.t11.org) as the SM-ZSM project. We wish 3870 to acknowledge the many contributions and comments from the INCITS 3871 Technical Committee T11, including the following: 3873 T11 Chair: Robert Snively, Brocade 3874 T11 Vice Chair: Claudio DeSanti, Cisco Systems 3875 T11.5 Chair: Roger Cummings, Symantec 3876 T11.5 Vice Chair: Scott Kipp, McData 3877 and T11.5 members. 3879 The document was subsequently a work item of the IETF's IMSS Working 3880 Group, chaired by David Black (EMC Corporation). We thank Bert 3881 Wijnen (Lucent Technologies) for his thorough review of the document. 3882 We also wish to acknowledge Dan Romascanu (Avaya), the IETF Area 3883 Director, for his comments and assistance. 3885 9. Normative References 3887 [RFC2578] 3888 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 3889 and S. Waldbusser, "Structure of Management Information Version 2 3890 (SMIv2)", STD 58, RFC 2578, April 1999. 3892 [RFC2579] 3893 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 3894 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 3895 2579, April 1999. 3897 [RFC2580] 3898 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 3899 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 3900 2580, April 1999. 3902 [RFC2863] 3903 McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB", RFC 3904 2863, June 2000. 3906 [RFC3411] 3907 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 3908 Describing Simple Network Management Protocol (SNMP) Management 3909 Frameworks", STD 58, RFC 3411, December 2002. 3911 [RFC3584] 3912 Frye, R., Levi, D., Routhier, S., and B. Wijnen, "Coexistence 3913 between Version 1, Version 2, and Version 3 of the Internet- 3914 standard Network Management Framework", RFC 3584, August 2003. 3916 [FC-GS-5] 3917 "Fibre Channel - Generic Services - 5 (FC-GS-5)", ANSI INCITS 3918 427-2006, http://www.t11.org/t11/stat.nsf/upnum/1677-d, December 3919 2006. 3921 [FC-GS-4] 3922 "Fibre Channel - Generic Services - 4 (FC-GS-4)", ANSI INCITS 3923 387-2004, http://www.t11.org/t11/stat.nsf/upnum/1505-d, February 3924 2004. 3926 [FC-SW-4] 3927 "Fibre Channel - Switch Fabric - 4 (FC-SW-4)", ANSI INCITS 3928 418-2006, http://www.t11.org/ftp/t11/pub/fc/sw-4/06-296v0.pdf 4 3929 April 2006. 3931 [FC-FS] 3932 "Fibre Channel - Framing and Signaling (FC-FS)", ANSI INCITS 3933 373-2003, April 2003. 3935 [RFC4001] 3936 Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, 3937 "Textual Conventions for Internet Network Addresses", RFC 4001, 3938 February 2005. 3940 [RFC4044] 3941 McCloghrie, K., "Fibre Channel Management MIB", RFC 4044, May 2005. 3943 [RFC4438] 3944 DeSanti, C., Gaonkar, V., Vivek, H., McCloghrie, K., and S. Gai, 3945 "Fibre-Channel Name Server MIB", RFC 4438, March 2006. 3947 [RFC4439] 3948 DeSanti, C., Gaonkar, V., McCloghrie, K., and S. Gai, "Fibre- 3949 Channel Fabric Address Manager MIB", RFC 4439, March 2006. 3951 [APPL-ID] 3952 Steven Wilson (FC-SW-5, Editor), "FC-SW-5 Letter to T11.5", ANSI 3953 INCITS T11/06-679v0, 3954 http://www.t11.org/ftp/t11/pub/fc/sw-5/06-679v0.pdf, 21 September, 3955 2006. Approved by the T11 and T11.5 plenary meetings on October 5, 3956 2006. 3958 [RFC2119] 3959 Bradner, S., "Key words for use in RFCs to Indicate Requirement 3960 Levels", BCP 14, RFC 2119, March 1997. 3962 10. Informative References 3964 [RFC2741] 3965 Daniele, M., Wijnen, B., Ellison, M., and D. Francisco, "Agent 3966 Extensibility (AgentX) Protocol Version 1", RFC 2741, January 2000. 3968 [RFC3410] 3969 Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and 3970 Applicability Statements for Internet- Standard Management 3971 Framework", RFC 3410, December 2002. 3973 11. IANA Considerations 3975 IANA is requested to make two MIB OID assignments, one for the 3976 T11-FC-ZONE-SERVER-MIB module, and one for the T11-FC-FABRIC-LOCK-MIB 3977 module, under the appropriate subtree(s). 3979 12. Security Considerations 3981 There are many management objects defined in these MIB modules with a 3982 MAX-ACCESS clause of read-write and/or read-create. Such objects may 3983 be considered sensitive or vulnerable in some network environments. 3984 The support for SET operations in a non-secure environment without 3985 proper protection can have a negative effect on network operations. 3987 Specifically, unauthorized write access to *any* of the writable 3988 objects in these MIB modules could cause unauthorized manipulation of 3989 the Zoning information on a Zone Server, and/or the activation of an 3990 unauthorized Active Zone Set in a fabric. This could result in 3991 allowing unauthorized connectivity, and/or denying authorized 3992 connectivity, between hosts connected to the Fibre Channel network. 3993 It could also cause the suppression of notifications (e.g., of 3994 unauthorized operations), or the disruption of network operations due 3995 to the generation of unwanted notifications. 3997 Some of the readable objects in this MIB module (i.e., objects with a 3998 MAX-ACCESS other than not-accessible) may be considered sensitive or 3999 vulnerable in some network environments. It is thus important to 4000 control even GET and/or NOTIFY access to these objects and possibly 4001 to even encrypt the values of these objects when sending them over 4002 the network via SNMP. 4004 Unauthorized read access to any of the readable objects in the 4005 t11ZsServerTable, t11ZsActiveZoneTable, t11ZsActiveZoneMemberTable, 4006 or t11ZsActiveAttribTable tables would reveal information about the 4007 currently authorized connectivity between hosts connected to the 4008 Fibre Channel network. 4010 Unauthorized read access to any of the readable objects in the 4011 t11ZsSetTable, t11ZsZoneTable, t11ZsSetZoneTable, t11ZsAliasTable, 4012 t11ZsZoneMemberTable, t11ZsAttribBlockTable or t11ZsAttribTable 4013 tables would reveal information about potential/alternative 4014 connectivity which could be authorized between hosts connected to the 4015 Fibre Channel network. 4017 SNMP versions prior to SNMPv3 did not include adequate security. 4018 Even if the network itself is secure (for example by using IPsec), 4019 even then, there is no control as to who on the secure network is 4020 allowed to access and GET/SET (read/change/create/delete) the objects 4021 in this MIB module. 4023 It is RECOMMENDED that implementors consider the security features as 4024 provided by the SNMPv3 framework (see [RFC3410], section 8), 4025 including full support for the SNMPv3 cryptographic mechanisms (for 4026 authentication and privacy). 4028 Further, deployment of SNMP versions prior to SNMPv3 is NOT 4029 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 4030 enable cryptographic security. It is then a customer/operator 4031 responsibility to ensure that the SNMP entity giving access to an 4032 instance of this MIB module is properly configured to give access to 4033 the objects only to those principals (users) that have legitimate 4034 rights to indeed GET or SET (change/create/delete) them. 4036 13. Authors' Addresses 4038 Claudio DeSanti 4039 Cisco Systems, Inc. 4040 170 West Tasman Drive 4041 San Jose, CA 95134 USA 4042 Phone: +1 408 853-9172 4043 EMail: cds@cisco.com 4045 H.K. Vivek 4046 Cisco Systems, Inc. 4047 71 Millers Rd 4048 Bangalore, India 4049 Phone: +91 80 2289933x5117 4050 EMail: hvivek@cisco.com 4052 Keith McCloghrie 4053 Cisco Systems, Inc. 4054 170 West Tasman Drive 4055 San Jose, CA USA 95134 4056 Phone: +1 408-526-5260 4057 Email: kzm@cisco.com 4059 Silvano Gai 4060 Retired 4062 Full Copyright Statement 4064 Copyright (C) The IETF Trust (2007). This document is subject to the 4065 rights, licenses and restrictions contained in BCP 78, and except as 4066 set forth therein, the authors retain all their rights. 4068 This document and the information contained herein are provided on an 4069 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 4070 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 4071 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 4072 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 4073 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 4074 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 4076 Disclaimer of validity 4078 The IETF takes no position regarding the validity or scope of any 4079 Intellectual Property Rights or other rights that might be claimed to 4080 pertain to the implementation or use of the technology described in 4081 this document or the extent to which any license under such rights 4082 might or might not be available; nor does it represent that it has 4083 made any independent effort to identify any such rights. Information 4084 on the procedures with respect to rights in RFC documents can be 4085 found in BCP 78 and BCP 79. 4087 Copies of IPR disclosures made to the IETF Secretariat and any 4088 assurances of licenses to be made available, or the result of an 4089 attempt made to obtain a general license or permission for the use of 4090 such proprietary rights by implementers or users of this 4091 specification can be obtained from the IETF on-line IPR repository at 4092 http://www.ietf.org/ipr. 4094 The IETF invites any interested party to bring to its attention any 4095 copyrights, patents or patent applications, or other proprietary 4096 rights that may cover technology that may be required to implement 4097 this standard. Please address the information to the IETF at 4098 ietf-ipr@ietf.org. 4100 Acknowledgment 4102 Funding for the RFC Editor function is currently provided by the 4103 Internet Society.