HP Cisco MDS 9140 Cisco MDS 9000 Family Storage Media Encryption Configuration - Page 186
copy running-config startup-config, Select Tape Drives, show tech, show tech-support sme
View all HP Cisco MDS 9140 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 186 highlights
Troubleshooting Scenarios Chapter 9 Cisco SME Troubleshooting Send documentation comments to [email protected] If you need to replace an MSM-18/4 module with another MSM-18/4 module In the existing MDS 9000 Family platform, a module can be replaced with another module and there is no change in configuration. In Cisco 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 Cisco SME interface will come up in an inactive state. The correct procedure is to remove the Cisco SME interface from the cluster and re-add the interface back into the cluster. If a Cisco SME cluster is not successfully created There are three main reasons that a Cisco SME cluster may not be successfully created: • SSH must be enabled on every switch that is part of a Cisco SME cluster. Note Only SSH/dsa or SSH/rsa are supported for Cisco SME cluster configurations using Fabric Manager Web Client. SSH/rsa1 is not supported for SME cluster config via FM web client in 3.2.2 (release with SME feature). It may (or may not) be supported in future releases. • If the Cisco 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 Fabric Manager Server after modifying the smeserver.properties file. • The DNS server must be configured. • Sometimes, improperly configured personal firewall software (running on Cisco Fabric Manager Server) 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 Fabric Manager Server/Fabric Manager web client/switches. A Cisco SME interface does not come up in a cluster If a Cisco SME interface does not come up, this can be due to the following: • A Cisco SME license is not installed or the license has expired. • An MSM-18/4 module has been replaced after the Cisco SME interface has been configured. • The copy running-config startup-config command was not entered after adding or deleting a Cisco SME interface from a cluster or before rebooting the switch. For the second and third scenarios, you must first remove and re-add the interface to the cluster and then enter the copy running-config startup-config command. When selecting paths, a "no paths found" message is displayed A tape library controller or robot can be shown as a target in the Select Tape 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 show tech and show tech-support sme command. Newly added tape drives are not showing in a cluster If you add new tape drives as LUNs to a tape library after Cisco SME has already discovered available tape drives, a rescan is required from the host to discover the new LUNs. Cisco MDS 9000 Family Storage Media Encryption Configuration Guide 9-8 OL-18091-01 Cisco MDS NX-OS Release 4.x