The following scenarios are described in this section:
If DNS is not configured on all switches in a cluster
You can use sme.useIP for IP address or name selection when DNS is
not configured on all switches in a cluster.
sme.useIP can be used in smeserver.properties to enable the use of IP
addresses instead of switch names. By default sme.useIP is set to false and DNS
names will be used. When DNS is not configured, DCNM-SAN cannot resolve the
When sme.useIP is set to true, DCNM-SAN uses an IP address to
communicate with switch in the cluster using SSH. All switches are added to the
cluster with an IP address. When you add a local switch, the switch name is
used if the name server is configured on the switch, otherwise, the IP address
When sme.useIP is false, DCNM-SAN will use the switch name to select
interfaces. All the switches added to the clusters will be identified with
names. A name server is required for this type of configuration. Otherwise,
switches will not be able to communicate with other switches to form the
cluster and DCNM-SAN will not be able to resolve the switch name.
If you need to replace an MSM-18/4 module with another MSM-18/4
In the existing MDS 9000 Family platform, a module can be replaced
with another module and there is no change in configuration. In SME, due to
security reasons, when an MSM-18/4 module is configured as part of a cluster it
cannot be replaced with another MSM-18/4 module, otherwise, the SME interface
will come up in an inactive state. The correct procedure is to remove the SME
interface from the cluster and re-add the interface back into the cluster.
If an SME cluster is not successfully created
There are three main reasons that a SME cluster may not be
Only SSH/dsa or SSH/rsa are supported for SME cluster
configurations using DCNM-SAN Web Client. SSH/rsa1 is not supported for SME
cluster config via DCNM-SAN web client in 3.2.2 (release with SME feature). It
may (or may not) be supported in future releases.
If the SME switches are managed using their IP addresses (instead
of host names or FQDN), the entry “sme.useIP=true” must be set in the
smeserver.properties file. Be sure to restart the DCNM-SAN after modifying the
The DNS server must be configured.
Sometimes improperly configured personal firewell software
(running on Cisco DCNM-SAN) may also cause a created SME cluster to stay in the
“pending” state. Be sure to create proper firewall rules to allow necessary
traffic between DCNM-SAN and the DCNM-SAN Web Client and switches.
SME Interface creation error
If there are any errors while SME interface creation, ensure the
- Ensure that the service module status is online.
- Ensure that the Storage Service Interface (SSI) boot variable is
not configured for the service module. If the SSI boot variable is configured
for the service module, then the SME interface creation fails.
An SME interface does not come up in a cluster
If an SME interface does not come up, this can be due to the
- An SME license is not installed or the license has expired.
- An MSM-18/4 module has been replaced after the SME interface has
startup-config command was not entered after
adding or deleting an SME interface from a cluster or before rebooting the
For the second and third scenarios, you must first remove and re-add
the interface to the cluster and then enter the
When selecting paths, a “no paths found” message is
A tape library controller or robot can be shown as a target in the
Drives wizard. If you select the controller or
robot as a target, a “no paths found” message is displayed. You will need to
verify whether or not the selected target is a controller or robot.
When the “no paths found” message is displayed, enter the
Newly added tape drives are not showing in a cluster
If you add new tape drives as LUNs to a tape library after SME has
already discovered available tape drives, a rescan is required from the host to
discover the new LUNs.
If you need to contact your customer support representative or
At some point, you may need to contact your customer support
representative or Cisco TAC for some additional assistance. Before doing so,
details and the
sme commands and collect all logs from the
9000\logs directory before contacting your support
A syslog message is displayed when a Cisco MDS switch configured
with SME in the startup configuration boots up
When you reboot a Cisco MDS switch that has the cluster configuration
stored in the startup-config file, the following syslog message may be
<timestamp> <switch name> %CLUSTER-2-CLUSTER_DB_SYNC_FAIL: Cluster <cluster-id> application 3 dataset 1 database synchronization failed, reason="Invalid cluster API registration"
This error message is expected and can be ignored.
Importing a volume group file causes a 'wrap key object not found'
A tape volume group was created and the volume group was exported to
a file. The tape volume group was deleted and a new tape volume group was
created. When the same volume group was imported, the import operation fails
and the error message “wrap key object not found” is displayed.
This error occurs because there is another volume group key active in
the Key Management Center with the same index (but different versions) as the
current volume group into which the import operation is performed.
Accounting log file shows the replication of keys failed
The replication of a key for a cluster fails when the transaction
context is invalid or is expired. The key entry will be moved to
Sme_repl_error_key table. You should manually remove this record from the
Sme_repl_error_key table to the Sme_repl_pending_key table and retry the
Issues with smart card(s) or card reader
If you have issues with smartcard operations, the following will help
- After a reboot, use only one instance of a supported browser.
- Ensure that there is no smart card in the reader while the
applet/wizard starts loads.
- When you insert a card and the wizard does not recognize the
change, take out the card and reseat it in the reader. Sometimes this triggers
- As a last resort, clearing the java classloader cache will help.
Open the java console, and press x to clear the classloader cache. Then restart
the browser and try again.