The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
If following the troubleshooting scenarios in this chapter does not resolve your problem, you can access and examine the logs for a possible solution.
This chapter contains the following sections:
This section includes symptoms, possible causes, and solutions for the following problems while you install the Cisco Virtual Switch Update Manager (VSUM).
Symptom |
Possible Causes |
Verification and Solution |
||
---|---|---|---|---|
After deploying the Open Virtualization Appliance (OVA) file, the Cisco Virtual Switch Update Manager tab does not appear in the vCenter vSphere Web Client home page. |
The OVA file is corrupt. |
|
||
After deploying the OVA file, the Cisco Virtual Switch Update Manager tab does not appear in the vCenter vSphere Web Client home page. |
Either a wrong IP address or port group has been assigned to the appliance. |
|
||
After deploying the OVA file, the Cisco Virtual Switch Update Manager tab does not appear in the vCenter vSphere Web Client home page. |
The vCenter vSphere Web Client credentials are incorrect. |
|
||
After deploying the OVA file, the Cisco Virtual Switch Update Manager tab does not appear in the vCenter vSphere Web Client home page. |
An older version of the com.cisco.n1kv is already available on the vCenter vSphere Web Client. |
|
||
VSUM is not working after changing vCenter port number. |
The new port number may not be open on vCenter, or the new port number is not updated in VSUM. |
Ensure that the newly changed port number is configured correctly on vCenter and is listening with new port. You can verify the configuration two different ways:
|
||
Logs show a problem with VSUM installation. See the section "Troubleshooting Virtual Switch Update Manager Installation with Logs". |
VSUM did not install correctly. |
For vCenter on Windows, do a clean uninstall and reinstall of VSUM by performing the following steps:
|
||
For vCenter on Linux, do a clean uninstall and reinstall of VSUM by performing the following steps:
|
If you have a problem installing Cisco Virtual Switch Update Manager and cannot solve it by methods listed earlier in this chapter, you can access and view logs in the Cisco Virtual Switch Update Manager for a possible solution.
Use Secure Shell (SSH) to connect to Cisco Virtual Switch Update Manager. The default username is root and the password is cisco.
Navigate to /etc/cisco/app_install/logs/n1kv-manager_install.log and check for the following log snippets:
193 [main] DEBUG com.cisco.vcenter.extension.register.ServiceUtil - host=10.193.216.91, clearPort=80, securePort=443, secure=true, tunnel=true, vCenterURL=https://10.193.216.91:80 /sdk 345 [main] DEBUG com.virtuata.security.TunnelFactory - Tryig to read 0 bytes long response 345 [main] DEBUG com.virtuata.security.TunnelFactory - CONNECT Response Body: 367 [main] DEBUG com.virtuata.security.TunnelFactory - VC SSL Tunnel Opened from localhost 51672 to 10.193.216.91:80 613 [main] DEBUG com.virtuata.security.TunnelFactory - Tunneled socket opening is complete 613 [main] DEBUG com.virtuata.security.VirtuataTunneledSSLSocketFactory - Tunneled socket is created 732 [main] DEBUG com.virtuata.security.VirtuataHostnameVerifier - Returning original verifier of type javax.net.ssl.HttpsURLConnection.DefaultHostnameVerifier 1212 [main] DEBUG com.cisco.vcenter.extension.register.ExtensionRegister - Received version=5.1.0 from vCenter. Parsed it as 5.1.0 (v-j5-n1-u0-l-b-v) 1983 [main] INFO com.cisco.vcenter.extension.register.ExtensionRegister - Examining extension with key=com.cisco.n1kv 1983 [main] INFO com.cisco.vcenter.extension.register.ExtensionRegister - Ignoring extension with key=com.cisco.n1kv 1983 [main] INFO com.cisco.vcenter.extension.register.ExtensionRegister - Legacy vcplugin was not installed. Nothing to remove 1989 [main] DEBUG com.cisco.vcenter.extension.register.KeyValueStore - Using /etc/cisco as the prefDir, and /etc/cisco/n1kvCfgData.properties as the file, full path is /etc/cisco/ n1kvCfgData.properties Using CATALINA_BASE: /usr/local/tomcat Using CATALINA_HOME: /usr/local/tomcat Using CATALINA_TMPDIR: /usr/local/tomcat/temp Using JRE_HOME: /usr/java/default Using CLASSPATH: /usr/local/tomcat/bin/bootstrap.jar:/usr/local/tomcat/bin/tomcat-juli.jar Using CATALINA_PID: /usr/local/tomcat/catalina.pid Registered app with vCenter. Thu Jul 31 15:21:46 PDT 2014 Finished initial configuration. Thu Jul 31 15:21:46 PDT 2014
If there are no issues in the above log snippet, check the vCenter Managed Object Browser (MOB) to verify that the Cisco Virtual Switch Update Manager plug-in is registered successfully.
Enter https://vcenterip/mob in a web browser and log in with the vCenter credentials.
Choose Content > Extension Manager and verify that the com.cisco.n1kv extension is listed.
Choose cisco.com.n1kv > Server and verify that the URL value displays the IP address of the Cisco VSUM VM.
If the IP address is displayed, the extension is registered successfully.If Cisco Virtual Switch Update Manager is not visible on vCenter vSphere Web Client, collect the vCenter and Cisco VSUM logs and send it to the Cisco Technical Assistance Center.