Feedback
Table Of Contents
Cisco MDS 9000 Family CIM Server Support
Enhanced Zoning and Enhanced Zoning Control Subprofile
Cisco MDS Extensions to the Switch and Fabric Profiles
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:
•
Cisco MDS Extensions to the Switch and Fabric Profiles
Managing SANs Through SMI-S
SANs are created in a multivendor environment. Hosts, fabric elements (switches, directors), and data storage devices are integrated from different vendors to create an interoperable storage network. Managing these elements from different vendors is problematic to the network administrator. Each element has its own management interface that may be proprietary. A network administrator must work with these disparate management APIs to build a cohesive management application that controls and monitors the SAN.
The SMI-S addresses this management problem by creating a suite of flexible, open management API standards based on the vendor- and technology-independent CIM. Using the SMI-S APIs, collected in profiles of common management classes, a network administrator can create a simplified management application CIM client to control and monitor the disparate SAN elements that support SMI-S and CIM. With CIM servers either embedded on the SAN elements or supported by a proxy CIM server, these elements are accessible to the network administrator's CIM client application.
SMI-S uses the Service Location Protocol version 2 (SLPv2) to discover CIM servers. Once the CIM servers are identified, the CIM client determines the profiles supported on the CIM servers through the Server profile. This profile is mandatory on all SMI-S based CIM servers.
Besides the control and monitoring support provided by profiles, the CIM server also supports asynchronous delivery of events through CIM indications. Indications provide immediate notification of important occurrences such as when an interface goes down.
Service Location Protocol
The first step in managing a network of SAN elements with CIM servers is discovering the location and support available on the CIM servers. The SLPv2 provides this discovery mechanism. A CIM client uses SLPv2 to discover CIM servers, gathering generic information about what services the CIM servers provide and the URL where these services are located.
The Cisco MDS 9000 Family CIM server supports SLPv2 as defined in RFC 2608.
Note
Server Profile
Once the CIM client discovers the CIM servers within the SAN, the CIM client must determine the level of support each CIM server provides. The Server profile defines the capabilities of the CIM server. This includes providing the namespace and all profiles and subprofiles supported by the CIM server.
For each supported profile, the Server profile instantiates the RegisteredProfile class. Each instance of this class gives the CIM client the profile name and unique ID that is supported by the CIM server. Similarly, the CIM server lists all supported optional subprofiles, using the RegisteredSubProfile class and the SubprofileRequiresProfile association class to associate the subprofile with the profile.
Note
Note
Switch Profile
The Switch profile models the physical and logical aspects of switches. The CIM client uses the Switch profile to identify that the CIM server is on a switch and uses classes in the Switch profile to identify and manage Fibre Channel ports on the switch.
The Switch profile also supports the optional Blade subprofile (see the "Blade Subprofile" section) and the optional Access Point subprofile (see the "Access Point Subprofile" section).
Note
Table 2-1 shows how to use the Switch profile classes and association classes to model the switch and ports.
Blade Subprofile
The CIM client uses the optional Blade subprofile to model the physical and logical aspects of a supervisor module, switching module, or services module in a switch. Combining this with the Switch profile, the CIM client gains a chassis-level view into the switch, associating ports to modules and modules to a switch.
Table 2-2 shows how to use the classes and association classes to model a module.
Note
Access Point Subprofile
The CIM client uses the Access Point subprofile to return the URL to access the switch and install or launch Fabric Manager or Device Manager. If Fabric Manager or Device Manager have not been installed, then the URL gives the option to install them. If Fabric Manager or Device Manager have been installed, then the URL gives the option to launch either of them.
Table 2-3 shows how to use the classes and association classes to model a module.
Note
Fabric Profile
A fabric is composed of one or more switches and network elements interconnected in a SAN. The Fabric profile models the physical and logical aspects of the fabric containing the SAN switches listed by the Switch profile.
Fabrics can contain one or more virtual SANs, or VSANs. See the "Cisco MDS Extensions to the Switch and Fabric Profiles" section for more information on the Cisco VSAN extension. Because routing in the Cisco MDS 9000 Family is based on the VSAN, the ConnectivityCollection and ProtocolEndpoint classes must be associated with the VSAN, not the fabric.
Table 2-4 shows how to use the classes and association classes of the Fabric profile to model the fabric.
Note
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 example—"1_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.
Note
The CIM server supports the following optional subprofiles from the Fabric profile:
•
•
•
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.
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:
•
•
•
•
•
The CIM server supports all the CIM classes and association classes described by the SMI-S zoning model.
Enhanced Zoning and Enhanced Zoning Control Subprofile
The Enhanced Zoning and Enhanced Zoning Control subprofile is a subprofile of the Fabric profile and provides additional modeling of Cisco zoning information for management purposes. This includes support for the following:
•
•
This subprofile supports all CIM classes and association classes described by the SMI-S zoning model except the concept of sessions for zoning.
Using the Zoning Subprofile
In the Cisco MDS CIM implementation, zoning occurs under the VSAN, not the fabric.
Note
Table 2-5 shows how to use the classes and association classes of the Zoning subprofiles to model zoning.
Zones and zone sets that are active have the Active property set to True by the CIM server. Zones can only contain the following types of objects:
•
•
FDMI Subprofile
The Fabric Device Management Interface (FDMI) manages host bus adapters (HBA) through the Fabric and complements data in the fabric profile. It allows any entity in the fabric to expose the HBA information through the SMI without having an agent resident on the host containing the HBA. The fabric profile only addresses HBA type devices. The HBA Management Interface defined by FDMI is a subset of the interface defined by the Fibre Channel HBA API specification.
Figure 2-1 shows the FDMI subprofile instance diagram. The classes are defined in CISCO_HBA.mof. If the FDMI- enabled HBA supports the host name, then CISCO_PortController associates to a platform through CISCO_PortControllerInPlatform.If the FDMI-enabled HBA does not support the host name, then CISCO_PortController associates to a fabric, through CISCO_PortControllerInFabric.
Figure 2-1 UML Diagram for FDMI Subprofile
Using the FDMI Subprofile
In the Cisco MDS CIM implementation, the FDMI subprofile occurs under the fabric.
Note
Table 2-6 shows how to use the classes and association classes of the FDMI subprofile.
Cisco MDS Extensions to the Switch and Fabric Profiles
The Cisco MDS 9000 Family CIM server supports additional classes that provide management for SAN features not covered by the standard SMI-S profiles. These extensions include:
VSAN Extensions
A VSAN is a virtual SAN that is created by partitioning the physical fabric into one or more logical fabrics. The Cisco MDS switches base routing on VSANs. The CIM client uses these VSAN extensions to identify VSANs and their associations to physical fabrics and switches.
The VSAN model in the CIM server uses the DMTF partition model. Partitioning, as defined by DMTF, is the virtual division of a single entity into multiple entities. It applies to any resource and can span namespaces and CIM object managers. Each partitioning entity manages its underlying partitions. A partitioned entity may be unaware that it is partitioned, and users may be unaware that a resource is shared. Refer to the standard partitioning model described in the CIM 2.8 schema, available from the DMTF website at http://www.dmtf.org.
Note
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:
•
–
–
•
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
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
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
Note
Figure 2-5 shows the full UML diagram for VSAN fabric and port partitioning in a SAN switch.
Figure 2-5 UML Diagram for VSAN Partitioning
PortChannel Extensions
A PortChannel is the aggregation of multiple physical Fibre Channel ports into one logical port to provide aggregated bandwidth, load balancing, and link redundancy. The CIM server supports a PortChannel port type in the Cisco_FCPort class. The Component association class can be used to associate individual ports with a PortChannel.
PortChannels are supported by the CIM server only for the local switch on which the CIM server is running. The CIM server also exports active connections for remote PortChannels, with two limitations:
•
•
Note
Figure 2-6 shows the relationships among ports and PortChannels on the switch that is running the CIM server. In this example:
•
•
Figure 2-6 UML Instance Diagram of the Relationships Among Ports Using FCIP, PortChannels, and Ethernet Ports
FCIP Extensions
The CIM server uses the current FCPort class to discover information about ports supporting FCIP. For the local switch (the switch on which the CIM server is running), the CIM server uses the LogicalIdentity association class to link ports supporting FCIP that are on the same module.
The CIM server exports active connections for remote ports running FCIP, with two limitations:
•
•
Note
Figure 2-6 shows the relationships among ports running FCIP and other entities. In this example:
•
•
iSCSI Extensions
You can use the current EthernetPort class to discover information about the port and use the LogicalIdentity association class to associate Gigabit Ethernet ports with iSCSI. This association class is only available for ports local to the CIM server.
Figure 2-6 shows the relationships among ports running iSCSI and other entities. In this example:
•
•
Note
Fabric Profile Extensions
In addition to the standard Fabric profile, the following classes and association classes that are specific to the Cisco MDS 9000 Family are supported:
CISCO_ActiveConnectionCISCO_AdminDomainCISCO_FCPortCISCO_FCPortCapabilitiesCISCO_FCPortSettingsCISCO_VsanCISCO_ComponentCISCO_ComputerSystemCISCO_ConnectivityCollectionCISCO_ConnectivityMemberOfCollectionCISCO_ContainedDomainCISCO_DeviceSAPImplementationCISCO_FCPortStatisticsCISCO_HostedAccessPointCISCO_HostedCollectionCISCO_ProtocolEndPointCISCO_PhysicalPackageCISCO_PhysicalElementCISCO_ProductCISCO_RealizesCISCO_SystemDeviceCISCO_ComputerSystemPackageCISCO_ElementStatisticalDataCISCO_LogicalPortGroupCISCO_LogicalModuleCISCO_ModulePortCISCO_HostedDependencyCISCO_LogicalIdentityCISCO_PhysicalComputerSystemCISCO_LogicalComputerSystemCISCO_FCNodeMemberOfCollectionThe port identifiers for the CISCO_FCPort class that are supported by the CIM server are described in Table 2-7. Port Identifiers 16004 through 16012 are Cisco extensions.
See the "Cisco Fabric MOF" section on page A-1 for the full definition of the Cisco fabric extensions.
Zoning Subprofile Extensions
In addition to the standard zoning subprofiles, the following classes and association classes that are specific to Cisco are supported:
CISCO_HostedServiceCISCO_ZoneMemberOfCollectionCISCO_ZoneMembershipSettingDataCISCO_ZoneSetCISCO_ZoneCISCO_ZoneCapabilitiesCISCO_ZoneAliasCISCO_ElementSettingDataCISCO_ZoneServiceCISCO_SystemSpecificCollectionSee 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:
PortControllerRealizesPlatformPackagePortControllerSoftwareIdentityHBASoftwareInstalledOnPlatformNodeFCPortControlledByPortControllerProductPhysicalHBAPlatformInFabricNodePortInPlatformNodeInPlatformPortControllerInPlatformPortControllerInFabricSee 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:
•
•
•
•
•
•
•
•
•
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_LinkStateChangeCISCO_LinkUpCISCO_LinkdownCISCO_MediaFRUInsertedCISCO_MediaFRURemovedCISCO_VSANChangedCISCO_ZoneSetAlertCISCO_EnvironmentalAlertCISCO_FanAlertCISCO_PowerAlertCISCO_TempAlertCISCO_NameServerDatabaseChangedSee the "Cisco Indications MOF" section on page A-15 for the Cisco Indications MOF file.
