Configuring and Using Cisco DCNM SMI-S Server

This chapter provides the steps to configure Cisco DCNM SMI-S Server in Cisco DCNM products and provides some sample scenarios for using CIM objects to manage your SAN. This chapter includes the following sections:

Installing Cisco DCNM SMI-S Server

Cisco DCNM SMI-S Server is installed as part of the Cisco DCNM-SAN installation. You can use Cisco DCNM-SAN installed locally to discover the SAN fabric. For more information on discovering the fabric using Cisco DCNM-SAN client, see the Cisco DCNM for SAN Configuration Guide.

Note All the platforms supported by Cisco DCNM are supported by SMI-S Server. SMI-S Server is configured as a startup service.

Changing the Default SMI-S Port

To change the default SMI-S port, follow these steps:

Step 1 Stop the Cisco SMI-S agent service.

Step 2 Enter the following command and change the port numbers for HTTP port <http-port> and HTTPS port <https-port> to be used by CISCO SMI-S agent.

>cd <install dir>/dcm/smis/server/jserver/bin

>echo HTTPSPort=<https-port> cimxmlscpa.properties

>echo HTTPPort=<http-port> cimxmlcpa.properties

Step 3 Start the Cisco SMI-S agent service.

Note SMI-S agent should be accessible from the port numbers mentioned in Step 2.

Performing Discovery and Performance Monitoring

Discovery provides information about the physical and logical entities within the SAN. This information changes dynamically as SAN entities are added, moved, or removed. Discovery also includes the discovery of object classes as well as related association classes, properties, and return status codes that are provided by servers in the managed environment.

Table 2-1 shows how to perform discovery, using the intrinsic methods defined by CIM. Use these methods to retrieve information about the switch and fabric.

Table 2-1 Performing Discovery

Method

How Used

enumerateInstances()

Enumerates instances of a CIM class.

enumerateInstanceNames()

Enumerates names of instances of a CIM class.

getInstance()

Gets a CIM instance.

associators()

Enumerates associators of a CIM object.

associatorName()

Enumerates names of associators of a CIM object.

references()

Enumerates references to a CIM object.

referenceName()

Enumerates names of references to a CIM object.

The target of these methods is the location of Cisco DCNM SMI-S Server, which is identified by the switch IP address.

Performance monitoring provides the status and statistics for the local ports. Only ports on the local switch can be monitored. You can retrieve statistics from the properties of the FCPortStatistics class for FCPort class instances on Cisco DCNM SMI-S Server.

Note The namespace of Cisco DCNM SMI-S Server is cimv2.

Modeling a Module Using the Blade Subprofile

You can use the Blade subprofile to model a supervisor module, switching module, or services module within a switch. Table 2-2 shows how to use the association classes in this subprofile to map ports to modules and modules to switches.

Table 2-2 Using the Blade Subprofile Association Classes

Class

How Used

Realizes

Associates the LogicalModule class to the PhysicalPackage class. Use this class to map modules to the switch.

ModulePort

Associates the FCPort class to the LogicalModule class. Use this class to map individual ports to modules within the switch.

Configuring Zoning

The zoning model in the SMI-S uses extrinsic and intrinsic methods to manage zoning within the SAN fabric. Extrinsic methods are methods specific to a particular class. Intrinsic methods are methods inherited from the CIM and present in every applicable class.

To create a zone member (referred to as ZoneMembershipSettingData), zone, zone alias, or zone set, use invokeMethod(operand). The operand can be one of the extrinsic methods from the zoning subprofiles as shown in Table 2-3.

Table 2-3 Zoning Extrinsic Methods

Extrinsic Method

How Used

CreateZoneMembershipSettingData()

Creates a ZoneMembershipSettingData and adds it to the specified Zone or NamedAddressCollection. The ConnectivityMemberID is dependent upon the ConnectivityMemberType.

CreateZone()

Creates a Zone and associates it to AdminDomain where the ZoneService is hosted.

CreateZoneAlias()

Creates a ZoneAlias and associates it to AdminDomain where the ZoneService is hosted.

CreateZoneSet()

Creates a ZoneSet and associates it to the AdminDomain where the ZoneService is hosted.

AddZone()

Adds the Zone to the specified ZoneSet. Adding a Zone to a ZoneSet extends the zone enforcement definition of the ZoneSet to include the members of that Zone. If adding the Zone is successful, the Zone should be associated to the ZoneSet by MemberOfCollection.

AddZoneMembershipSettingData()

Adds ZoneMembershipSettingDatato the Zone or NamedAddessCollection.

AddZoneAlias()

Adds the Zone Alias to the Zone.

ActivateZoneSet ()

Sets the ZoneSet to active.

ZoneSetDistribute()

Distributes the full ZoneSet along with active zone set per VSAN in the fabric.

CreatDeviceAlias()

Creates a device alias with the given device alias name and PWWN.

Use the DeleteInstance(instance_name) intrinsic method to remove a zoning item from a collection or to delete the zoning item entirely. The DeleteInstance() method requires a reference to one of the instances shown in Table 2-4.

Table 2-4 Deleting Zoning Entities

Class

How Used

CIM_ElementSettingData

Removes a zone member from a zone or zone alias. Use deleteInstance() to delete the instance of ElementSettingData that associates the zone member to the zone.

CIM_MemberOfCollection

Removes a zone or zone alias from a zone set. Use deleteInstance() to delete the instance of MemberOfCollection that associates the zone or zone alias to the zone set.

CIM_ZoneMembershipSettingData

Deletes a zone member. This automatically removes it from any zone or zone alias.