1-- ******************************************************************** 2-- CISCO-FC-SDV-MIB.my: Fibre Channel SAN Device Virtualization MIB 3-- 4-- September 2006, Sanjeev C Joshi 5-- 6-- Copyright (c) 2006 by Cisco Systems, Inc. 7-- All rights reserved. 8-- 9-- ******************************************************************** 10CISCO-FC-SDV-MIB DEFINITIONS ::= BEGIN 11IMPORTS 12 MODULE-IDENTITY, OBJECT-TYPE, 13 Unsigned32 FROM SNMPv2-SMI 14 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 15 RowStatus, StorageType, 16 TEXTUAL-CONVENTION FROM SNMPv2-TC 17 vsanIndex FROM CISCO-VSAN-MIB 18 FcList FROM CISCO-ZS-MIB 19 FcAddressId, FcNameIdOrZero, 20 DomainIdOrZero FROM CISCO-ST-TC 21 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 22 ciscoMgmt FROM CISCO-SMI; 23 24ciscoFcSdvMIB MODULE-IDENTITY 25 LAST-UPDATED "200609260000Z" 26 ORGANIZATION "Cisco Systems, Inc." 27 CONTACT-INFO 28 " Cisco Systems 29 Customer Service 30 31 Postal: 170 W Tasman Drive 32 San Jose, CA 95134 33 USA 34 35 Tel: +1 800 553-NETS 36 37 E-mail: cs-mds9000@cisco.com" 38 DESCRIPTION 39 "This MIB instrumentation is for managing Fibre 40 Channel (FC) SAN Device Virtualization (SDV) 41 solution on Cisco Fibre Channel devices. 42 43 Glossary of the terms used in this MIB: 44 --------------------------------------- 45 Config Commit - User initiated action that triggers 46 commiting of configuration to local 47 device/fabric. Eg. CFS based config 48 'commit' as described in CISCO-CFS-MIB. 49 50 Domain - The highest or most significant 51 hierarchical level in the three-level 52 FC addressing hierarchy. 53 54 Device Aias - is a string which can be used to alias a 55 World Wide Name (WWN). 56 57 FCID - Fibre Channel Address ID. A 24 bit Fabric 58 unique address identifier. 59 60 FCNS - Fibre Channel Name Server. 61 62 Initiator - The system component that originates an 63 I/O command over an I/O bus or network. 64 65 NWWN - WWN associated with FC node. 66 67 PWWN - WWN associated with FC port. 68 69 Real Device - A hardware entity which includes Link 70 Control facility. It is directly 71 connected to a FC fabric and acts as 72 originator/responder or both. 73 74 RSCN - Registered State Change Notification. 75 RSCN Notifications are sent to Nx_ports 76 and other switches to notify that an 77 event has occurred. 78 79 SW_RSCN - Switch Registered State Change 80 Notification. SW_RSCN Notifications are 81 sent to neighbouring switches in a 82 fabric to notify that an event has 83 occurred. 84 85 SCSI - Acronym for Small Computer System 86 Interface. 87 88 Target - The system component that receives a 89 SCSI I/O command command. 90 91 Virtual Device - The virtual initiator/target having its 92 (VD) own device identity and proxies a Real 93 Device (Initiator/Target) in a FC fabric. 94 95 VT - Virtual Target. 96 97 VI - Virtual Initiator. 98 99 Virtual Domain - A logical Domain partition in a FC fabric 100 within which a Virtual Device exists. 101 102 VSAN - Virtual Storage Area Network, similar 103 to a VLAN. 104 105 WWN - Wide Name (WWN) associated with 106 a Fibre Channel (FC) entity. A 64 bit 107 identifier, with a 60 bit value preceded 108 with a four bit 109 Network_Address_Authority_Identifier, 110 used to identify physical entities in 111 Fibre Channel. 112 113 The primary motivation for SAN Device Virtualization 114 is the High availability of storage disk arrays with 115 no downtime. Redundancy is achieved by duplication 116 of information and hardware to ensure secondary 117 device can take over the function of a primary 118 device when the latter fails. The initiators 119 (servers) perform I/O to the primary target. 120 The secondary target is kept in sync to have a 121 mirrored copy of the primary target by a replication 122 mechanism. In the event of a disruption to primary 123 target, all I/O must be immediately re-routed to 124 secondary target so that services running on 125 initiators remain un-interrupted. The SDV solution 126 resides on a Cisco FC Switching Device. The target 127 failover is achieved by presenting a virtual proxy 128 target to initiator with the SDV acting as a conduit 129 for creating and deleting the proxy (virtual) 130 target on demand. The Virtual Target or in general 131 Virtual Device can virtualize (proxy) set of Real 132 Devices with one Real Device actively mapped as the 133 primary mapping and the rest as secondary mappings. 134 135 WWN2,FCID2 136 _____ 137 | | 138 [Switch Fabric] /| RT1 | 139 ''''''''''''''' / |_____| 140 WWN1,FCID1 ' ' / [Primary Real 141 ____ ' WWN4,FCID4 ' / Target Device] 142 | | ' +~~~~~~~+__'_/ 143 | I |->--->'->| VT |__'_ 144 |____| ' +~~~~~~~+ ' \ 145 [Real Host ' ' \{On Fail-Over} 146 (Initiator)] ' ' \ WWN3,FCID3 147 ''''''''''''''' \ _____ 148 [VT: Virtual Target] \| | 149 | RT2 | 150 |_____| 151 [Secondary Real 152 Target Device] 153 154 -<< Fig 1 >>- 155 156 In the above figure (Fig 1), 'Switch Fabric' 157 presents the Virtual Target 'VT' as a proxy device 158 for real targets 'RT1' and 'RT2'. The Host/Initiator 159 'I' can discover a virtual target VT and does not 160 see real targets RT1 and RT2 as accessible targets. 161 The Virtual Target VT is configured on the switch 162 and maps to one real target as a primary mapping. 163 The Initiator performs I/O with VT. When the primary 164 target RT1 fails, the secondary real target RT2 can 165 take over. For the Initiator, failover/migration is 166 transparent and continues to perform I/O with VT. 167 168 ___ ____ ____ 169 | |-->--[I->VT]-----[ ]---->--[I->T]---| | 170 | I | [ VT ] | RT | 171 | | [ ] | | 172 |___|--<--[I<-VT]-----[____]----<--[I<-T]---|____| 173 174 [Initiator] [Virtualized [Real 175 Target] Target] 176 177 -<< Fig 2 >>- 178 179 When the Initiator 'I' performs I/O with VT, the 180 SDV enabled switch performs FCID address translation 181 to route FC frames to the real target RT (refer 182 Fig 2). The I->VT frames are translated as I->T. 183 The T->I frames are translated as VT->I. The SDV 184 manages VT so that other devices (in the same zone) 185 perceive it as just another device in the fabric. 186 187 The cFcSdvVirtDeviceTable is table of Virtual Devices. 188 The cFcSdvVirtRealDevMapTable is a table of mapping 189 elements. 190 191 A Virtual Device is represented by a row in the 192 cFcSdvVirtDeviceTable, and if its value of 193 cFcSdvVdRealDevMapList has the value of zero, 194 then the Virtual Device is not currently mapped to 195 any Real Devices. Otherwise, the Virtual Device is 196 mapped to the set of Real Devices with each Real 197 Device identified by the instance indentifier value 198 of cFcSdvVirtRealDevMapIndex. 199 " 200 REVISION "200609260000Z" 201 DESCRIPTION 202 "Initial version of this MIB module." 203 ::= { ciscoMgmt 593 } 204 205ciscoFcSdvMIBNotifs OBJECT IDENTIFIER ::= { ciscoFcSdvMIB 0 } 206ciscoFcSdvMIBObjects OBJECT IDENTIFIER ::= { ciscoFcSdvMIB 1 } 207ciscoFcSdvMIBConform OBJECT IDENTIFIER ::= { ciscoFcSdvMIB 2 } 208 209cFcSdvConfig OBJECT IDENTIFIER ::= { ciscoFcSdvMIBObjects 1 } 210 211-- 212-- Textual Conventions 213-- 214 215CiscoFcSdvDevIdType ::= TEXTUAL-CONVENTION 216 STATUS current 217 DESCRIPTION 218 "The type of device identifier value. 219 220 'singleDevPWWN' - Single addressable device 221 identifiable by PWWN 222 223 'singleDevDevAlias' - Single addressable device 224 identifiable by Device Alias 225 " 226 SYNTAX INTEGER { 227 singleDevPWWN(1), 228 singleDevDevAlias(2) 229 } 230 231CiscoFcSdvDevId ::= TEXTUAL-CONVENTION 232 STATUS current 233 DESCRIPTION 234 "This denotes device identifier value to be used 235 with CiscoFcSdvDevIdType. The CiscoFcSdvDevId is 236 always interpreted within the context of a 237 CiscoFcSdvDevIdType value. Every usage of 238 CiscoFcSdvDevId textual convention is required 239 to specify a CiscoFcSdvDevIdType object which 240 provides the context. 241 242 The encoding of the CiscoFcSdvDevId object for a 243 specific device identifier type is as below: 244 245 ----------------------------------------------------------- 246 RealDeviceType Octets Contents Encoding 247 ----------------------------------------------------------- 248 singleDevPWWN 1-8 Device Port WWN As in FcNameId of 249 CISCO-ST-TC 250 ------------------------------------------------------------ 251 singleDevDevAlias 1-64 DeviceAlias As in 252 Name SnmpAdminString of 253 SNMP-v2-TC 254 ------------------------------------------------------------ 255 " 256 SYNTAX OCTET STRING (SIZE (1..255)) 257 258CiscoFcSdvRealDevMapType ::= TEXTUAL-CONVENTION 259 STATUS current 260 DESCRIPTION 261 "The type of mapping of Real Device(s) (Initiator/ 262 Target) to which the Virtual Device is virtualized 263 to. 264 265 'primaryDevMap' - primary (current) mapping 266 'secondaryDevMap' - secondary (standby) mapping 267 " 268 SYNTAX INTEGER { 269 primaryDevMap(1), 270 secondaryDevMap(2) 271 } 272 273-- 274-- FC Virtual Device Configuration 275-- 276cFcSdvVirtDeviceTable OBJECT-TYPE 277 SYNTAX SEQUENCE OF CFcSdvVirtDeviceEntry 278 MAX-ACCESS not-accessible 279 STATUS current 280 DESCRIPTION 281 "This table lists all the virtual devices configured 282 on this device. 283 284 The successful creation of a row in this table, 285 through the use of the cFCSDMVdRowStatus object, 286 followed by the 'Config Commit' will also cause 287 the creation of rows in other tables. Specifically: 288 289 - The Creation of Device Alias: An entry in the 290 'cfdaConfigTable' of CISCO-FC-DEVICE-ALIAS-MIB 291 gets created by the agent with the value of the 292 cFcSdvVdName as the instance identifier value of 293 cfdaConfigDeviceAlias, 'pwwn' as the value of 294 cfdaConfigDeviceType and the value of cFcSdvVdPwwn 295 as the value of cfdaConfigDeviceId. An attempt 296 to create an already existing Device Alias entry 297 mapping to different Real Device would fail and 298 hence results in failure to add Virtual Device 299 entry in this table. In general, any failure in 300 Device Alias creation/deletion will have 301 corresponding effect of Virtual Device creation 302 /deletion respectively. 303 304 Similarly the deletion of a row in this table causes 305 deletion of corresponding rows in other tables. 306 Specifically: 307 308 - An entry in the 'cfdaConfigTable' of 309 CISCO-FC-DEVICE-ALIAS-MIB that corresponding to 310 the value of cFcSdvVdName is deleted. 311 312 Once a Virtual Device gets created successfully, 313 such a device is available for zone configuration. 314 The Virtual Device added as Device Alias can be 315 used to create the zones and zoneSets using 316 CISCO-ZS-MIB. The Device Alias is identified as 317 the 'deviceAlias' type of ZoneMemberType in all 318 occurrences of usage of ZoneMemberType in the 319 zoning tables." 320 ::= { cFcSdvConfig 1 } 321 322cFcSdvVirtDeviceEntry OBJECT-TYPE 323 SYNTAX CFcSdvVirtDeviceEntry 324 MAX-ACCESS not-accessible 325 STATUS current 326 DESCRIPTION 327 "An entry (conceptual row) in the 328 cFcSdvVirtDeviceTable. 329 Each entry represents a Virtual Device in a 330 specific VSAN. 331 332 <cFcSdvVirtDeviceEntry> 333 +-------+---------+--- 334 |VdIndex| 335 +-------+---------+---- 336 | maps to 337 | <cFcSdvVirtRealDevMapEntry> 338 +--|----+-------------------+--------------------+-----------------+-- 339 | |____|VirtRealDevMapIndex|VirtRealDeviceIdType| VirtRealDeviceId|.. 340 |vdIndex| | | | 341 +-------+-------------------+--------------------+-----------------+-- 342 -<< Fig 3 >>- 343 344 The above figure (Fig 3) depicts the relationship 345 that this conceptual row has with conceptual rows 346 of the other tables for configuring the virtual 347 device. 348 349 The deletion of a row in this table also causes the 350 deletion of all the Real Device mapping entries for 351 the same combination of vsanIndex and cFcSdvVdIndex 352 in the cFcSdvVirtRealDevMapTable. 353 " 354 INDEX { vsanIndex, 355 cFcSdvVdIndex } 356 ::= { cFcSdvVirtDeviceTable 1 } 357 358CFcSdvVirtDeviceEntry ::= SEQUENCE { 359 cFcSdvVdIndex Unsigned32, 360 cFcSdvVdName SnmpAdminString, 361 cFcSdvVdVirtDomain DomainIdOrZero, 362 cFcSdvVdFcId FcAddressId, 363 cFcSdvVdPwwn FcNameIdOrZero, 364 cFcSdvVdNwwn FcNameIdOrZero, 365 cFcSdvVdAssignedFcId FcAddressId, 366 cFcSdvVdRealDevMapList FcList, 367 cFcSdvVdStorageType StorageType, 368 cFcSdvVdRowStatus RowStatus 369} 370 371cFcSdvVdIndex OBJECT-TYPE 372 SYNTAX Unsigned32 (1..4096) 373 MAX-ACCESS not-accessible 374 STATUS current 375 DESCRIPTION 376 "An arbitrary index number of a Virtual Device. 377 This instance value uniquely identifies a Virtual 378 Device within the context of a particular VSAN and 379 in the agent where an instance of this MIB 380 instrumentation is running." 381 ::= { cFcSdvVirtDeviceEntry 1 } 382 383cFcSdvVdName OBJECT-TYPE 384 SYNTAX SnmpAdminString (SIZE(1..32)) 385 MAX-ACCESS read-create 386 STATUS current 387 DESCRIPTION 388 "A human readable string representing the name of 389 this Virtual Device. The value of cFcSdvVdName 390 should be unique in the system." 391 ::= { cFcSdvVirtDeviceEntry 2} 392 393cFcSdvVdVirtDomain OBJECT-TYPE 394 SYNTAX DomainIdOrZero 395 MAX-ACCESS read-create 396 STATUS current 397 DESCRIPTION 398 "The user preference for a persistent Domain Id 399 for this Virtual Device to indicate a specific 400 partition (domain) of the Fabric that this 401 Virtual Device should belong to. 402 403 If the value of this object is not explicitly set 404 by the user, the system generates and uses a 405 Virtual Domain from the allowed domains. The value 406 of '0' indicates no user preference." 407 DEFVAL { 0 } 408 ::= { cFcSdvVirtDeviceEntry 3 } 409 410cFcSdvVdFcId OBJECT-TYPE 411 SYNTAX FcAddressId 412 MAX-ACCESS read-create 413 STATUS current 414 DESCRIPTION 415 "The user preference for a persistent 'FCID' for 416 this Virtual Device. 417 418 The value of the corresponding instance of 419 cFcSdvVdVirtDomain specifies the Domain identifier 420 part of the FCID. When the values for both 421 cFcSdvVdVirtDomain and cFcSdvVdFcId are specified 422 during row creation, the Domain ID part of 423 cFcSdvVdFcId value should exactly match the value 424 of cFcSdvVdVirtDomain. 425 426 If the value of this object is not explicitly set 427 by the user, the system generates and uses a 428 FCID for this Virtual Device. The value of 429 '000000'h indicates no user preference." 430 DEFVAL { '000000'h } 431 ::= { cFcSdvVirtDeviceEntry 4 } 432 433cFcSdvVdPwwn OBJECT-TYPE 434 SYNTAX FcNameIdOrZero 435 MAX-ACCESS read-only 436 STATUS current 437 DESCRIPTION 438 "The assigned 'PWWN' for this Virtual Device. 439 The agent assigns this value when the 440 configuration is committed." 441 ::= { cFcSdvVirtDeviceEntry 5 } 442 443cFcSdvVdNwwn OBJECT-TYPE 444 SYNTAX FcNameIdOrZero 445 MAX-ACCESS read-only 446 STATUS current 447 DESCRIPTION 448 "The assigned 'NWWN' for this Virtual Device. 449 The agent assigns this value when the 450 configuration is committed." 451 ::= { cFcSdvVirtDeviceEntry 6 } 452 453cFcSdvVdAssignedFcId OBJECT-TYPE 454 SYNTAX FcAddressId 455 MAX-ACCESS read-only 456 STATUS current 457 DESCRIPTION 458 "The assigned 'FCID' of this Virtual Device. The 459 agent assigns this value when the configuration is 460 committed and the Real Device that this Virtual 461 Device virtualizes (corresponding entry in the 462 cFcSdvVirtRealDevMapTable where the 463 value of cFcSdvVirtRealDevMapType is 464 'primaryDevMap') is on-line." 465 ::= { cFcSdvVirtDeviceEntry 7 } 466 467cFcSdvVdRealDevMapList OBJECT-TYPE 468 SYNTAX FcList(SIZE(0..16)) 469 MAX-ACCESS read-only 470 STATUS current 471 DESCRIPTION 472 "The set of Real Device(s) that this Virtual Device 473 virtualizes in this VSAN. 474 475 The Real Devices are identified by the instance 476 identifier object cFcSdvVirtRealDevMapIndex in the 477 cFcSdvVirtRealDevMapTable. 478 479 If a particular bit has a value of '1', then the 480 corresponding Real Device (indicated by the position 481 of bit and represented by cFcSdvVirtRealDevMapIndex) 482 is mapped for virtualization for this Virtual Device. 483 The bit value of '0' indicates that particular Real 484 Device is not mapped for virtualization in this 485 Virtual Device. 486 487 This object is read-only; changes to its value 488 are made by the agent as and when associated 489 entries are created/deleted in the 490 cFcSdvVirtRealDevMapTable. 491 492 The default value is the zero length string." 493 DEFVAL { ''H } 494 ::= { cFcSdvVirtDeviceEntry 8 } 495 496cFcSdvVdStorageType OBJECT-TYPE 497 SYNTAX StorageType 498 MAX-ACCESS read-create 499 STATUS current 500 DESCRIPTION 501 "The storage type for this conceptual row. 502 503 Conceptual rows having the value of this object as 504 'readOnly' can not be deleted by the user by setting 505 the value of cFcSdvVdRowStatus to 'destroy'." 506 DEFVAL { nonVolatile } 507 ::= { cFcSdvVirtDeviceEntry 9 } 508 509cFcSdvVdRowStatus OBJECT-TYPE 510 SYNTAX RowStatus 511 MAX-ACCESS read-create 512 STATUS current 513 DESCRIPTION 514 "The status of this conceptual row. The value of 515 this object can not be set to 'active' unless the 516 value of the corresponding instance of cFcSdvVdName 517 is unique across all the VSANs in the system. 518 519 Once value of this object is set to 'active', the 520 value of the corresponding instance of cFcSdvVdName 521 can not be modified. 522 523 Once value of this object is set to 'active', the 524 setting the values of the corresponding instance of 525 cFcSdvVdVirtDomain and cFcSdvVdFcId will take effect 526 and results into FCID/Domain allocation only after 527 the Virtual Device comes on-line the next time." 528 ::= { cFcSdvVirtDeviceEntry 10 } 529 530-- 531-- Virtual Device to Real Device Mapping Table 532-- 533cFcSdvVirtRealDevMapTable OBJECT-TYPE 534 SYNTAX SEQUENCE OF CFcSdvVirtRealDevMapEntry 535 MAX-ACCESS not-accessible 536 STATUS current 537 DESCRIPTION 538 "This table provides list of Real Devices which 539 are mapped to Virtual Device for Device 540 Virtualization." 541 ::= { cFcSdvConfig 2 } 542 543cFcSdvVirtRealDevMapEntry OBJECT-TYPE 544 SYNTAX CFcSdvVirtRealDevMapEntry 545 MAX-ACCESS not-accessible 546 STATUS current 547 DESCRIPTION 548 "An entry (conceptual row) in the 549 cFcSdvVirtRealDevMapTable. Each entry represents a 550 Real Device(s) mapped to a Virtual Device for 551 virtualization within the scope of a VSAN. 552 553 When the Real Device represented by an entry in 554 this table whose instance of cFcSdvVirtRealDevMapType 555 is 'primaryDevMap' comes on-line, the corresponding 556 Virtual Device that virtualizes such Real Device 557 also comes on-line and registers itself as one 558 of logged-in devices in the FCNS database - an 559 entry into 'fcNameServerTable' of CISCO-NS-MIB 560 and SW_RSCN and RSCN are appropriately generated." 561 INDEX { vsanIndex, 562 cFcSdvVdIndex, 563 cFcSdvVirtRealDevMapIndex } 564 ::= { cFcSdvVirtRealDevMapTable 1 } 565 566CFcSdvVirtRealDevMapEntry ::= SEQUENCE { 567 cFcSdvVirtRealDevMapIndex Unsigned32, 568 cFcSdvVirtRealDeviceIdType CiscoFcSdvDevIdType, 569 cFcSdvVirtRealDeviceId CiscoFcSdvDevId, 570 cFcSdvVirtRealDevMapType CiscoFcSdvRealDevMapType, 571 cFcSdvVirtRealDevMapStorageType StorageType, 572 cFcSdvVirtRealDevMapRowStatus RowStatus 573} 574 575cFcSdvVirtRealDevMapIndex OBJECT-TYPE 576 SYNTAX Unsigned32 (1..128) 577 MAX-ACCESS not-accessible 578 STATUS current 579 DESCRIPTION 580 "An arbitrary index number to identify a Real 581 Device(s) mapped to a Virtual Device. 582 583 This instance value uniquely identifies a 584 Real Device mapping entry for Virtual Device 585 within the context of a particular VSAN and 586 in the agent where an instance of this MIB 587 instrumentation is running. 588 589 When an entry is successfully created in this table, 590 the agent uses this instance identifier value to 591 update the value of cFcSdvVdRealDevMapList of 592 cFcSdvVirtDeviceTable to indicate that this 593 Real Device(s) entry is mapped for virtualization in 594 a Virtual Device (represented by cFcSdvVdIndex)." 595 ::= { cFcSdvVirtRealDevMapEntry 1 } 596 597cFcSdvVirtRealDeviceIdType OBJECT-TYPE 598 SYNTAX CiscoFcSdvDevIdType 599 MAX-ACCESS read-create 600 STATUS current 601 DESCRIPTION 602 "The type of Real Device identifier represented 603 by the value of the corresponding instance of 604 'cFcSdvVirtRealDeviceId' that this Virtual Device 605 virtualizes to." 606 DEFVAL { singleDevPWWN } 607 ::= { cFcSdvVirtRealDevMapEntry 2 } 608 609cFcSdvVirtRealDeviceId OBJECT-TYPE 610 SYNTAX CiscoFcSdvDevId(SIZE(1..64)) 611 MAX-ACCESS read-create 612 STATUS current 613 DESCRIPTION 614 "This object represents a Real Device(s) identifier 615 that this Virtual Device virtualizes. 616 617 A Real Device element represented by the combination 618 of value of this object preceded by the value of 619 corresponding instance of cFcSdvVirtRealDeviceIdType 620 should be unique for a Virtual Device within a VSAN. 621 622 When the value of the corresponding instance of 623 cFcSdvVirtRealDeviceIdType is 'singleDevDevAlias', 624 the value of this object is the name of a Device 625 Alias pointing to a specific entry identified by 626 the instance identifier value of 627 'cfdaConfigDeviceAlias' of cfdaConfigTable in 628 the CISCO-FC-DEVICE-ALIAS-MIB." 629 DEFVAL { '0000000000000000'H } 630 ::= { cFcSdvVirtRealDevMapEntry 3 } 631 632cFcSdvVirtRealDevMapType OBJECT-TYPE 633 SYNTAX CiscoFcSdvRealDevMapType 634 MAX-ACCESS read-create 635 STATUS current 636 DESCRIPTION 637 "The mapping association type of the Real Device(s) 638 (Initiator/Target). There can only be one instance 639 of this object within a context of a vsan, virtual 640 device and MapID that can be marked as 641 'primaryDevMap'. The rest of the instances can only 642 be 'secondaryDevMap'." 643 DEFVAL { secondaryDevMap } 644 ::= { cFcSdvVirtRealDevMapEntry 4 } 645 646cFcSdvVirtRealDevMapStorageType OBJECT-TYPE 647 SYNTAX StorageType 648 MAX-ACCESS read-create 649 STATUS current 650 DESCRIPTION 651 "The storage type for this conceptual row. 652 Conceptual rows having a value of 'readOnly' need 653 not allow write-access to any of the columnar 654 objects of the same row." 655 DEFVAL { nonVolatile } 656 ::= { cFcSdvVirtRealDevMapEntry 5 } 657 658cFcSdvVirtRealDevMapRowStatus OBJECT-TYPE 659 SYNTAX RowStatus 660 MAX-ACCESS read-create 661 STATUS current 662 DESCRIPTION 663 "The status of this conceptual row. The value of 664 this object can not be set to 'active' unless the 665 value of the corresponding instance of 666 cFcSdvVirtRealDeviceIdType and cFcSdvVirtRealDeviceId 667 is unique for a virtual device within a VSAN. Once 668 value of this object is set to 'active', the values 669 of the corresponding instance of 670 cFcSdvVirtRealDeviceIdType and cFcSdvVirtRealDeviceId 671 can not be modified." 672 ::= { cFcSdvVirtRealDevMapEntry 6 } 673 674-- 675-- Conformance 676-- 677 678ciscoFcSdvMIBCompliances 679 OBJECT IDENTIFIER ::= { ciscoFcSdvMIBConform 1 } 680 681ciscoFcSdvMIBGroups 682 OBJECT IDENTIFIER ::= { ciscoFcSdvMIBConform 2 } 683 684ciscoFcSdvMIBCompliance MODULE-COMPLIANCE 685 STATUS current 686 DESCRIPTION 687 "The compliance statement for entities which 688 implement CISCO-FC-SDV-MIB." 689 MODULE MANDATORY-GROUPS { ciscoFcSdvConfigGroup } 690 691 OBJECT cFcSdvVdRowStatus 692 SYNTAX INTEGER { 693 active (1), 694 createAndGo (4), 695 destroy (6) 696 } 697 DESCRIPTION 698 "Only 'createAndGo', 'destroy' and 'active' need to 699 be supported." 700 701 OBJECT cFcSdvVirtRealDevMapRowStatus 702 SYNTAX INTEGER { 703 active (1), 704 createAndGo (4), 705 destroy (6) 706 } 707 DESCRIPTION 708 "Only 'createAndGo', 'destroy' and 'active' need to 709 be supported." 710 ::= { ciscoFcSdvMIBCompliances 1 } 711-- 712-- Units of Conformance 713-- 714 715ciscoFcSdvConfigGroup OBJECT-GROUP 716 OBJECTS { 717 cFcSdvVdName, 718 cFcSdvVdVirtDomain, 719 cFcSdvVdFcId, 720 cFcSdvVdPwwn, 721 cFcSdvVdNwwn, 722 cFcSdvVdAssignedFcId, 723 cFcSdvVdStorageType, 724 cFcSdvVdRealDevMapList, 725 cFcSdvVdRowStatus, 726 727 cFcSdvVirtRealDeviceIdType, 728 cFcSdvVirtRealDeviceId, 729 cFcSdvVirtRealDevMapType, 730 cFcSdvVirtRealDevMapStorageType, 731 cFcSdvVirtRealDevMapRowStatus 732 } 733 STATUS current 734 DESCRIPTION 735 "A collection of objects for FC SDV configuration." 736 ::= { ciscoFcSdvMIBGroups 1 } 737END 738 739