Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o. c o m
Cisco MDS 9000 Family SMI-S Programming Reference

March, 2008

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-553-NETS (6387) Fax: 408 527-0883
Text Part Number: OL-16185-01
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0711R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental. Cisco MDS 9000 Family SMI-S Programming Reference 2008 Cisco Systems, Inc. All rights reserved.

CONTENTS

New and Changed Information Preface

ix ix ix x vii

Audience

Organization

Document Conventions
Related Documentation x Release Notes xi Compatibility Information xi Regulatory Compliance and Safety Information xi Hardware Installation xi Cisco Fabric Manager xii Command-Line Interface xii Intelligent Storage Networking Services Configuration Guides Troubleshooting and Reference xii Installation and Configuration Note xiii Obtaining Documentation and Submitting a Service Request Cisco.com xiii Product Documentation DVD xiii Ordering Documentation xiv Documentation Feedback

Cisco.com

You can access the most current Cisco documentation at this URL: http://www.cisco.com/techsupport You can access the Cisco website at this URL: http://www.cisco.com You can access international Cisco websites at this URL: http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have.PDF versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL: http://www.cisco.com/go/marketplace/

Ordering Documentation

Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL: http://www.cisco.com/go/marketplace/ Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 463-3487 in the United States and Canada, or elsewhere by calling 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 519-5001 in the United States and Canada, or elsewhere at 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com. You can submit comments about Cisco documentation by using the response card (if present) behind the front cover of your document or by writing to the following address: Cisco Systems Attn: Customer Document Ordering 170 West Tasman Drive San Jose, CA 95134-9883 We appreciate your comments.

Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL: http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html From this site, you will find information about how to:
Report security vulnerabilities in Cisco products. Obtain assistance with security incidents that involve Cisco products. Register to receive security information from Cisco.
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL: http://www.cisco.com/go/psirt To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL: http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
For Emergencies only security-alert@cisco.com An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
For Nonemergencies psirt@cisco.com 228-408 525-6532
In an emergency, you can also reach PSIRT by telephone:
We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x. Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL: http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html The link on this page has the current PGP key ID in use. If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

CH A P T E R

The Cisco MDS 9000 Family of multilayer directors and fabric switches provide an industry standard application programming interface (API) using the Storage Management Initiative Specification (SMI-S). SMI-S facilitates managing storage area networks (SANs) in a multivendor environment. This chapter includes the following sections:
About the Common Information Model, page 1-1 Understanding CIM and Unified Modeling Language Notation, page 1-3 About SMI-S and CIM in the Cisco MDS 9000 Family, page 1-4
About the Common Information Model
The Common Information Model (CIM) is an object-oriented information model that describes management information in a network or enterprise environment. Because it is object-oriented, CIM provides abstraction, inheritance, and dependency or association relationships between objects within the model. CIM is based on XML and is platform-independent and technology neutral. The management application developer does not need any information about how CIM was implemented on a vendor product; only the API is required to interact with a vendor product. CIM uses a client/server model. The CIM server can be embedded into the vendor product or can be implemented by a proxy server that provides the CIM server functionality for the legacy vendor product. The CIM client is the management application that communicates to multiple CIM servers to manage the SAN. The CIM client discovers CIM servers through the Service Location Protocol, version 2 (SLPv2) as defined in RFC 2608. SLPv2 uses UDP port 427 for communication and is a discovery protocol that is separate from the CIM client/server communication path. CIM defines the communications between the client and server in terms of technologies defined in the Web-Based Enterprise Management Initiative (WBEM). Figure 1-1 shows the full CIM client/server communications path.
Chapter 1 About the Common Information Model
Figure 1-1 CIM Client/Server Communications

CIM client

xmICIM encoding CIM operations over HTTP HTTP TCP/IP

CIM server

For more information about CIM, refer to the specification available through the Distributed Management Task Force (DMTF) website at http://www.dmtf.org.
About the Storage Management Initiative Specification
The Storage Management Initiative Specification (SMI-S) uses an object-oriented model based on CIM to define a set of objects and services that can manage elements of a SAN. By using a standardized architecture, SMI-S helps management application developers create common and extensible applications that work across multiple SAN vendor products. Figure 1-2 exemplifies SMI-S in a multivendor SAN.

Chapter 1 About SMI-S and CIM in the Cisco MDS 9000 Family

Understanding UML

UML draws a visual representation of the classes that describe a product or technology. UML contains many visual elements, but only a subset are described here. Refer to http://www.uml.org for a full explanation of UML. Figure 1-3 shows an example section from a UML diagram for CIM classes. This diagram shows:
blue lines for inheritance between classes green lines for aggregation between classes red lines for associations between classes

UML Example Diagram

Figure 1-3
ManagedElement Description: string Caption: string Inheritance

Dependency

ManagedSystemElement Name: string Description: string Caption: string Status: string InstallDate: datetime

Component

Association
Aggregation (a type of association)

Methods

Each switch or director in the Cisco MDS 9000 Family includes an embedded CIM server. The CIM server communicates with any CIM client to provide SAN management compatible with SMI-S. The CIM server includes the following standard profiles, subprofiles, and features as defined in SMI-S:
Service Location Protocol version 2 (SLPv2). Server profile. CIM indications. Fabric profile.
Zoning Control subprofile. Enhanced Zoning and Enhanced Zoning Control subprofile. FDMI subprofile.
Switch profile, including the Blade subprofile and Access Point subprofile. xmlCIM encoding and CIM operations over HTTP as specified by the WBEM initiative.

120526

Overview About SMI-S and CIM in the Cisco MDS 9000 Family
HTTPS, which uses Secure Socket Layer (SSL). HTTPS is optional but provides enhanced security by encrypting communications between the CIM server and the CIM client.
Table 1-1 shows the Cisco SAN-OS release that supports different versions of SMI-S.
Table 1-1 Cisco SAN-OS Support for SMI-S
Cisco SAN-OS Release 3.3(1)
SMI-S Support SMI-S 1.2.0 compliant with caveats SMI-S 1.1.0 compliant Supports SMI-S 1.0.2
All required indications are not supported limited WQL/CQL support

3.0(1) 2.0(1b)

Additional support for Server profile and Access Port subprofile. Supports SLPv2, CIM indications, and the Server profile.
Cisco MDS 9000 Family CIM Server Support
SMI-S defines a number of profiles that specify the managed objects used to control and monitor elements of a SAN. The Cisco MDS 9000 Family CIM server supports the standard profiles listed in this chapter. The CIM server also supports extensions to these profiles to support features in Cisco MDS SAN-OS that are not available from the standard profiles. This chapter includes the following sections:
Managing SANs Through SMI-S, page 2-1 Service Location Protocol, page 2-2 Server Profile, page 2-2 Switch Profile, page 2-2 Fabric Profile, page 2-4 Cisco MDS Extensions to the Switch and Fabric Profiles, page 2-8 CIM Indications, page 2-16

ComputerSystem

Cisco MDS 9000 Family CIM Server Support Fabric Profile
Table 2-4 Using the Fabric Profile (continued)

FCPort

How Used Represents the logical aspects of the link and data layers. Associates to the ProtocolEndpoint class by the DeviceSAPImplementation association class and associates to the ComputerSystem class by the SystemDevice association class. Represents the higher network layers for routing. Associates to the ConnectivityCollection class by the ConnectivityMemberOfCollection association class. Represents a link that associates two ProtocolEndpoint classes as a connection that is currently carrying traffic.

ProtocolEndpoint

ActiveConnection
The Cisco MDS 9000 Family CIM server only provides the LogicalPortGroup class for the fabric, not for hosts or storage systems. The CIM server requires that the name of the fabric or VSAN be unique within the same CIM namespace. Names are identified by the Name class property with an associated optional NameFormat property. A VSAN identifier is the VSAN identification followed by the world-wide name (WWN) of the principal switch, for example1_2001000530000A0A (the NameFormat indicates that it is a WWN). For VSANs, the fabric identifier is a string because there is no principal switch per fabric.
For a Fabric profile instance diagram, refer to the SMI-S at http://www.snia.org. The CIM server supports the following optional subprofiles from the Fabric profile:
Zone Control subprofile (see the Zone Control Subprofile section on page 2-5) Enhanced Zoning and Enhanced Zoning Control subprofile (see the Enhanced Zoning and Enhanced Zoning Control Subprofile section on page 2-6) FDMI subprofile (see the FDMI Subprofile section on page 2-7)
The Fabric profile also supports a number of extensions specific to the Cisco MDS 9000 Family. See the Cisco MDS Extensions to the Switch and Fabric Profiles section on page 2-8.

Zone Control Subprofile

Zoning enables the CIM client to set up access control between storage devices or user groups. The Zone Control subprofile is a subprofile of the Fabric profile and models zoning information for the fabric. It incorporates read and write functionality including the following operations:
Creating and deleting zones and zone sets Creating and deleting zone members (using ZoneMembershipSettingData) Adding and removing zone members to zones Adding and removing zones to zone sets Activating and deactivating a zone set

Cisco MDS 9000 Family CIM Server Support Cisco MDS Extensions to the Switch and Fabric Profiles
For more information about VSANs, refer to the Cisco MDS 9000 Family Fabric Manager Configuration Guide or the Cisco MDS 9000 Family CLI Configuration Guide. The VSAN extension provided by the Cisco MDS 9000 Family CIM server is both compatible with, and an extension of, the standard partition model. It models VSANs as a partitioned physical fabric. The E ports, F ports, PortChannels, and ports supporting FC IP and iSCSI on Cisco MDS switches all support the partitioning model. The HostedDependency association class can describe the following relationships:

Partitioning (fan in)

Antecedent is the partitioning entity Dependent is the partitioned entity

Clustering (fan out)

Figure 2-2 shows a UML diagram of a fabric partitioned into two VSANs. The physical switch is partitioned into two logical switches, Partitioned Switch 1 and Partitioned Switch 2. The partitions are identified as belonging to the physical switch using the HostedDependency association class. The VSANs are identified as belonging to the corresponding switch partitions using the Component association class.
Figure 2-2 UML Diagram of Fabric Partitioning
AdminDomain (SAN) Name="Physical Fabric" NameFormat="String" OperationalStatus={2} Hosted=false
ComputerSystem (Physical switch w/ partition support) Component Name=2000000000000000 Hosted Dependency

Contained domain

AdminDomain (VSAN 1) Name="1_2130405060708090" NameFormat="id with wwn" OperationalStatus={2} Hosted=true Component
ComputerSystem (Partitoned switch 1) Name=2100000000000000 Hosted dependency
AdminDomain (VSAN 2) Name="2_2230405060708090" NameFormat="id with wwn" OperationalStatus={2} Hosted=true Component
ComputerSystem (Partitoned switch 2) Name=2200000000000000

120469

Figure 2-3 isolates the VSAN component from Figure 2-2. The physical fabric is partitioned into two VSANs, VSAN 1 and VSAN 2. Each VSAN is identified by the AdminDomain class. The VSANs can be identified as belonging to the physical fabric using the ContainedDomain association class.
Figure 2-3 VSAN Partitioning Example
AdminDomain (Fabric) Name="Physical Fabric" NameFormat="String" OperationalStatus={2} The SAN
Contained Domain AdminDomain (VSAN 1) Name="1_2130405060708090" NameFormat="id with wwn" OperationalStatus={2} VSANs within the SAN Contained Domain AdminDomain (VSAN 2) Name="2_2230405060708090" NameFormat="id with wwn" OperationalStatus={2}

120468

TE Port Extensions
TE ports are E ports that can carry traffic for multiple VSANs. The CIM server uses the existing fabric-to-FC port association classes to model membership of TE ports in multiple VSANs. Figure 2-4 shows the physical and logical port relationship to the switch. The two illustrated physical ports are partitioned into logical ports, and the logical ports are identified as belonging to the physical ports using the HostedDependency association class. A physical TE port is partitioned into two logical ports, one for Partitioned switch 1(associated to VSAN 1 in Figure 2-2) and one for Partitioned switch 2 (associated to VSAN 2 in Figure 2-2). The physical ports are identified as components of the physical switch using the SystemDevice association class, and the partitioned ports are identified as components of the corresponding partitioned switch using the SystemDevice association class.
Figure 2-4 TE Port Partitioning Example
ComputerSystem (Physical switch w/ partition support) Name=2000000000000000

SystemDevice

FCPort (Physical TE port) DeviceID=2A00000000000000 SystemName=2000000000000000 PortType=14
FCPort (Physical TE port) HostedDependency SystemDevice DeviceID=2B00000000000000 SystemName=2000000000000000 PortType=14 HostedDependency SystemDevice FCPort (Logical E port) DeviceID=2B00000000000000 SystemName=2100000000000000 PortType=14 FCPort (Partitioned port switch 1) ComputerSystem (Partitoned switch 2) Name=2200000000000000 FCPort (Partitioned port switch 2) SystemDevice DeviceID=2A00000000000000 SystemName=2200000000000000 PortType=14 DeviceID=2A00000000000000 SystemName=2100000000000000 PortType=14 Hosted Dependency Hosted dependency
ComputerSystem (Partitoned switch 1) Name=2100000000000000

Hosted dependency

For more information about trunking, refer to the Cisco MDS 9000 Family Fabric Manager Configuration Guide or the Cisco MDS 9000 Family CLI Configuration Guide.

120471

Figure 2-5 shows the full UML diagram for VSAN fabric and port partitioning in a SAN switch.

Chapter 2 CIM Indications
Zoning Subprofile Extensions
In addition to the standard zoning subprofiles, the following classes and association classes that are specific to Cisco are supported:
CISCO_HostedService CISCO_ZoneMemberOfCollection CISCO_ZoneMembershipSettingData CISCO_ZoneSet CISCO_Zone CISCO_ZoneCapabilities CISCO_ZoneAlias CISCO_ElementSettingData CISCO_ZoneService CISCO_SystemSpecificCollection
See the Cisco Zone MOF section on page A-4 for the full definition of the Cisco zoning extensions.
FDMI Subprofile Extensions
In addition to the standard FDMI subprofile, the following classes and association classes that are specific to the Cisco MDS 9000 Family are supported:
PortControllerRealizes PlatformPackage PortControllerSoftwareIdentity HBASoftwareInstalledOnPlatform NodeFCPortControlledByPortController ProductPhysicalHBA PlatformInFabric NodePortInPlatform NodeInPlatform PortControllerInPlatform PortControllerInFabric
See the Cisco FDMI MOF section on page A-5 for the full definition of the Cisco FDMI extensions.

CIM Indications

SMI-S provides asynchronous indications for changes in the CIM server or the managed elements controlled by the CIM server. These indications can inform a CIM client that:
The SAN configuration has changed. The SAN switch health has degraded. The SAN fabric performance has degraded. Nameserver Database has changed. VSAN added/deleted/modified. Fan status has changed. Temperature status has changed. Power Supply status has changed.
Cisco MDS 9000 Family CIM Server Support CIM Indications
FRU inserted/ removed/changed.
Indications can also be used when a CIM class method is invoked that will take a long time to finish. Rather than tie up the CIM server (block) until the operation completes, the CIM server responds that the operation started, and the CIM server continues handling other requests (non-blocking). When the original, long operation completes, the CIM server sends a CIM indication asynchronously to the CIM client, showing the result of the operation. A CIM client must subscribe to indications it wants to receive from the CIM server. The Cisco MDS 9000 Family CIM server supports the following Cisco-specific indications:
CISCO_LinkStateChange CISCO_LinkUp CISCO_Linkdown CISCO_MediaFRUInserted CISCO_MediaFRURemoved CISCO_VSANChanged CISCO_ZoneSetAlert CISCO_EnvironmentalAlert CISCO_FanAlert CISCO_PowerAlert CISCO_TempAlert CISCO_NameServerDatabaseChanged

[Write, Description( "The set of management IP Addresses used to access this " "platform.")] string MgmtAddressList[]; }; // CISCO_PortController [Description("CISCO_PortController represents the port controller of an FDMI enabled HBA.")] class CISCO_PortController: CIM_PortController { [Override("SystemCreationClassName"), Key, MaxLen (256), Description ( "The scoping system's creation class name. The " "scoping system is the CISCO_Platform or " "CISCO_Fabric of which this device is part.")] string SystemCreationClassName; [Override("SystemName"), Key, MaxLen (256), Description ( "The scoping system's Name property. The value " "is equivalent to the platform name if the scoping system is an " "instance of CISCO_Platform or the Proxy Switch WWN if the " "scoping system is an instance of CISCO_Fabric.")] string SystemName; [Override("CreationClassName"), Key, MaxLen (256), Description ( "CreationClassName indicates the name of the CISCO_PortController " "class that, when used with the other key properties of this " "class, uniquely identifies an instance of the " "CISCO_PortController class.")] string CreationClassName= "CISCO_PortController"; [Override("DeviceID"), Key, MaxLen (64), Description ( "This is the Serial Number of the HBA")] string DeviceID; [Override("ControllerType"),Required,Description ( "The type or model of the port controller. Specific values " "will be enumerated in a later release of this schema. When " "set to 1 (\"Other\"), the related property " "OtherControllerType contains a string description of the " "controller's type."), ValueMap { "0", "1", "2", "3", "4", "5", "6", "7", "8" }, Values { "Unknown", "Other", "Ethernet", "IB", "FC", "FDDI", "ATM", "Token Ring", "Frame Relay" }] uint16 ControllerType = 4; };
class CISCO_HBASoftwareIdentity : CIM_SoftwareIdentity {}; class CISCO_ElementSoftwareIdentity : CIM_ElementSoftwareIdentity {}; // Associations // CISCO_PortControllerRealizes [Association, Provider("FDMIProvider"), Description ( "CISCO_PortControllerRealizes is the association that defines " "the mapping between devices and the physical elements " "that implement them.")]
class CISCO_PortControllerRealizes: CIM_Realizes { [Override ("Antecedent"), Description ( "The physical HBA that implements the Device.")] CISCO_PhysicalHBA REF Antecedent; [Override ("Dependent"), Description ( "The Device.")] CISCO_PortController REF Dependent; }; // CISCO_PlatformPackage [Association, Description ( "This association denotes one or more physical HBAs that " "realize a Platform.")] class CISCO_PlatformPackage: CIM_ComputerSystemPackage { [Override ("Antecedent"), Description ( "The physical HBA that realizes a Platform.")] CISCO_PhysicalHBA REF Antecedent; [Override ("Dependent"), Description ( "The Platform.")] CISCO_Platform REF Dependent; }; // CISCO_PortControllerSoftwareIdentity [Association, Description ( "The PortControllerSoftwareIdentity relationship identifies any " "software that is associated with the device and this association " "can return multiple instances.")] class CISCO_PortControllerSoftwareIdentity: CIM_ElementSoftwareIdentity { [Override ("Antecedent"), Description ( "The SoftwareIdentity on the device.")] CISCO_HBASoftwareIdentity REF Antecedent; [Override ("Dependent"), Description ( "The logical device that requires or uses the software.")] CISCO_PortController REF Dependent; }; // CISCO_HBASoftwareInstalledOnPlatform [Association, Description ( "The SofwareInstalledOnPlatform relationship allows the " "identification of the platform on which HBA driver " "is installed and this association can return multiple instances.")] class CISCO_HBASoftwareInstalledOnPlatform: CIM_InstalledSoftwareIdentity { [Key, Override("System"), Max (1), Description ( "Reference to the platform hosting a particular " "SoftwareIdentity.")] CISCO_Platform REF System; [Key, Override("InstalledSoftware"), Description ( "Reference to the driver that is installed on the " "platform.")] CISCO_HBASoftwareIdentity REF InstalledSoftware; }; // CISCO_NodeFCPortControlledByPortController

[Version ("1.0.0"), Description ( "cisco zoneset class")] class CISCO_ZoneSet : CIM_ZoneSet { }; class CISCO_Zone : CIM_Zone {}; class CISCO_ZoneAlias : CIM_NamedAddressCollection {}; class CISCO_ZoneMemberSettingData : CIM_ZoneMembershipSettingData {}; class CISCO_ZoneService : CIM_ZoneService {}; class CISCO_SystemSpecificCollection : CIM_SystemSpecificCollection {}; class CISCO_ZoneMemberOfCollection : CIM_MemberOfCollection {}; class CISCO_ElementSettingData : CIM_ElementSettingData {}; class CISCO_HostedService : CIM_HostedService {};
Managed Object Format Files Cisco Indications MOF

Cisco Indications MOF

The Cisco Indications MOF provides extensions to the SMI-S standard indications to provide indications of link state changes. This MOF supports Cisco SAN-OS Release 2.0(1a) or later. See the FDMI Subprofile Extensions section on page 2-16.
[Version ("2.2.0")] class CISCO_LinkStateChange : CISCO_AlertIndication { [Description ( "The desired state of the interface. The testing (3) state" "indicates that no operational packets can be passed. When a" "managed system initializes, all interfaces start with" "ifAdminStatus in the down(2) state. As a result of either" "explicit management action or per configuration information" "retained by the managed system, ifAdminStatus is then" "changed to either the up(1) or testing(3) states (or remains" "in the down(2) state)."), ValueMap {"1", "2", "3"}, Values { "up", "down", "testing"}] uint32 ifAdminStatus; [Description ( "The current operational state of the interface. "), ValueMap {"1", "2", "3", "4", "5", "6", "7"}, Values { "up", "down", "testing", "unknown", "dormant", "notPresent", "lowerLayerDown"}] uint32 ifOperStatus; uint32 ifIndex; }; class CISCO_LinkUp : CISCO_LinkStateChange {}; class CISCO_LinkDown : CISCO_LinkStateChange {}; class CISCO_MediaFRU : CISCO_AlertIndication { uint32 PhysicalIndex; string PhysicalDescr; uint32 PhysicalVendorType_len; uint32 PhysicalContainedIn; [ Description ("Entity Physical Class Type "), ValueMap {"1", "2", "3","4" , "5", "6", "7", "8", "9","10", "11" } , Values {"ENT_OTHER","UNKNOWN_ENTITY", "CHASSIS", "BACKPLANE","CONTAINER", "POWERSUPPLY", "FAN", "SENSOR", "MODULE", "PORT", "STACK"} ] uint32 PhysicalClass; uint32 PhysicalParRelPos; string PhysicalName; string PhysicalHardwareRev; string PhysicalFirmwareRev; string PhysicalSoftwareRev; string PhysicalSerialNum; string PhysicalMfgName; string PhysicalModelName; string PhysicalAlias; string PhysicalAssetID; boolean PhysicalIsFRU;

Appendix A Cisco Indications MOF
boolean Valid; [ Description ( "Module Admin Status Status"), ValueMap {"1", "2", "3","4"}, Values {"CEFC_PHYS_STATUS_OTHER ","CEFC_PHYS_STATUS_SUPPORTED", "CEFC_PHYS_STATUS_UNSUPPORTED", "CEFC_PHYS_STATUS_INCOMPATIBLE"} ] uint16 PhysicalStatus; string string string string string uint16 string }; class CISCO_MediaFRUInserted : CISCO_MediaFRU {}; class CISCO_MediaFRURemoved : CISCO_MediaFRU {}; class CISCO_MediaFRUChanged: CISCO_AlertIndication { uint32 PhysicalIndex; [Description ( "Module Operational Status"), ValueMap {"1", "2","4","5","6","7","8","9","10","11","12", "13","14","15","16","17","18","19","20","21"}, Values { "MOD_OPER_UNKNOWN","MOD_OPER_OK","MOD_OPER_DISABLED","MOD_OPER_OKBUTDIAGFAILED", "MOD_OPER_BOOT","MOD_OPER_SELFTEST", " MOD_OPER_FAILED", "MOD_OPER_MISSING", "MOD_OPER_MISMATCHWITHPARENT", "MOD_OPER_MISMATCHCONFIG", "MOD_OPER_DIAGFAILED", "MOD_OPER_DORMANT" , " MOD_OPER_OUTOFSERVICEADMIN", "MOD_OPER_OUTOFSERVICEENVTEMP", "MOD_OPER_POWEREDDOWN", "MOD_OPER_POWEREDUP", " MOD_OPER_POWERDENIED", "MOD_OPER_POWERCYCLED", "MD_OPER_OKBUTPOWEROVERWARNING"," MOD_OPER_OKBUTPOWEROVERCRITICAL", "MOD_OPER_SYNCINPROGRESS" } ] uint16 ModuleOperStatus; [Description ( "Module Admin Status Status"), ValueMap {"1", "2", "3","4"}, Values {"Admin Enabled","Admin Disabled", "Admin Reset", "Admin Out of Service"} ] uint16 ModuleAdminStatus; [Description ( "Module Admin Status Status"), ValueMap {"1", "2", "3","4","5"}, Values {"UNKNOWN_RESET ","POWERUP", "PARITYERROR", "CLEARCONFIGRESET","MANUALRESET"} ] uint16 ModuleResetReason; string ModuleResetReasonDescription; uint32 numPorts; uint32 boot_mode; uint8 isValid; PhySecondSerialNum; PhyProductNumber; PhyPartRevision; PhyMfgDate; PhysicalCLEICode; PhySramSize; PhysicalNameofSlot;
uint8 uint8 uint8 uint32 uint32 uint32 }; class CISCO_VSANChanged: CISCO_AlertIndication {}; class CISCO_ZoneSetAlert: CISCO_AlertIndication { string ZoneSetName; uint32 VsanId; }; class CISCO_EnvironmentalAlert: CISCO_AlertIndication { string EnvAlertDescription; uint32 PhysicalIndex; uint32 OperationalStatus; }; class CISCO_FanAlert: CISCO_EnvironmentalAlert {}; class CISCO_PowerAlert: CISCO_EnvironmentalAlert { uint32 FRUPowerAdminStatus; uint32 FRUCurrent; }; class CISCO_TempAlert: CISCO_EnvironmentalAlert { uint32 SensorValue; uint32 SensorThresholdValue; uint32 SensorThresholdIndex; }; class CISCO_NameServerDatabaseChanged: CISCO_AlertIndication { }; mod_state; mod_type; pad[2]; mod_no; ModuleUpTime; numFcPorts;

Access Point subprofile description

2-4 2-4

documentation additional publications conventions

1-x 1-xiii 1-x

related documents
using Access Point subprofile classes (table)
Blade subprofile description

2-3 2-3, 3-4

Enhanced Zoning and Enhanced Zoning Control subprofile description 2-6 extensions Fabric profile FCIP iSCSI

2-13 2-14 2-12 2-14

using Blade subprofile classes (table)
CIM client/server communications path (figure) configuring the server description
1-1 1-3 3-1 1-5 3-1 3-1 1-2

PortChannel TE port VSAN

2-10 2-8

Zone Control subprofile

creating a certificate (procedure) Operations over HTTP
Fabric profile description extensions FCIP extensions FDMI Extensions

2-4 3-3

sample scenarios for using objects CIM indications. See indications CIM server
support by Cisco SAN-OS release (table)
discovery and performance data
Cisco extensions. See extensions Cisco FDMI MOF
using Fabric profile classes (table)

2-13 2-16

Common Information Model. See CIM configuring the CIM server
discovery and performance data DMTF website

1-1 3-3

HTTP and HTTPS protocols (procedures)
Se n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a ck - d o c @ c i s c o. c o m I
indications Cisco-specific description iSCSI extensions

2-17 2-16 2-14

configuring the CIM server configuring zoning performing discovery profiles Fabric Server Switch

2-4 2-2 2-2 3-4

gathering performance data
Managed Object Format files. See MOFs managing zones module, modeling MOFs Cisco Fabric for Release 2.x Cisco Fabric for Release 3.x Cisco Zone for Release 2.x Cisco Zone for Release 3.x description
A-12 A-1, A-5 A-14 A-4 3-4 3-4
Server profile, description SLP, description SMI-S description

1-2 1-2 2-2 2-2

Service Location Protocol. See SLP
in multivendor SAN (figure) managing SANs
new and changed information (table)