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.
This chapter contains the following sections.
Use the following order to manually clean the Cisco VACS environment.
Step 1 | Ensure that all the containers are deleted. However, if the deletion or rollback fails, you must manually remove the VMs from the VC, and run the VC inventory in the Cisco UCS Director. |
Step 2 | Remove all the
hosts that were added to Nexus1000V DVS
For information on how to manually remove hosts, see Removing the Hosts Manually. |
Step 3 | Remove Cisco
Nexus 1000V.
For information on how to manually remove the Cisco Nexus 1000V VSM, see Removing the Cisco Nexus 1000V VSM Manually. |
Step 4 | Remove Cisco
VSUM.
For information on how to manually remove Cisco VSUM, see Removing a Cisco Virtual Switch Update Manager Installation Manually. |
Step 5 | Remove Cisco
PNSC.
For information on how to manually remove Cisco PNSC, see Removing a PNSC Installation Manually. |
This section includes symptoms, possible causes, and solutions for issue (s) encountered while applying the Cisco VACS patch.
Symptom:When you apply the Cisco VACS patch to the Cisco UCS Director using the Hypertext Transfer Protocol (HTTP) from an IIS based HTTP Server, the patch installation fails with an error message. During this installation failure, there is no network connectivity issues between the HTTP server and the Cisco UCS Director.
(TestAdapter.java:699) [TestAdapter] downloadPackageUrl - caught an exception java.net. SocketException: Connection reset
Possible Causes: This occurs when you use a Windows machine as the Web/HTTP Server (IIS).
Verification and Solution: To resolve this problem, configure a website that is dedicated to download large files by disabling the HTTP Keep-Alives Enabled option for a website that the ISS hosts. To disable this option, do the following:
Symptom: The Cisco VACS upgrade process fails with an error.
tar: /opt /infra/install/<VACS_PATCH>/patch.tar: Not found in archive localhost logger: tar: Error exit delayed from previous errors
Possible Causes: This occurs when the installation of the previous upgrade patch was stopped abruptly, possible because Cisco UCS Director re-booted by itself.
Symptom:The Cisco VSUM upgrade process fails with an error.
Cannot update the Extension info at vCenter. update_extension.sh failed with an exception: Exception in thread "main" com.vmware.ciscon1kvim25.InvalidArgument
Go to https://VCIP/mob and log in with the vCenter credentials.
In a web browser, choose
.Click UnregisterExtension, enter com.cisco.n1kv and then click Invoke method.
Go to C:\ProgramData\VMware\vSphere and in the Web Client\ vc-packages\vsphere-client-serenity directory, delete the entire com.cisco.n1kv folder.
Choose Start and then run services.msc.
Right-click the VMware vSphere Web Client and then click Start.
Go to https://VCIP/mob and log in with the default credentials.
In a web browser, choose
.Click UnregisterExtension, enter com.cisco.n1kv, and then click Invoke method.
Go to the /var/lib/vmware/ vsphere-client/vc-packages/vsphere- client-serenity/ directory in the vCenter VM and delete the entire com.cisco.n1kv folder using the following command:
rm -rf /var/lib/vmware/vsphere-client/ vc-packages/ vsphere- client-serenity/com.cisco.n1kv-x-x
Restart VMware vSphere Web Client service using the following command:
/etc/init.d/vsphere-client restart
Check if the web client UI is working after starting the service and logging out.
Log in to Cisco VSUM using the default credentials (root/cisco).
Navigate to /etc/cisco/app_install.
Copy the app.cfg template file to app.cfg using the following command:
![]() Note | The app.cfg template file is a hidden file in the /etc/cisco/app_install folder. |
Open the app.cfg file by using the following command:
vi app.cfg
Update the IP address and change the vCenterUsernameFormat and vCenterPasswordFormat values from hex to plain.
Enter the administrator credentials in the vCenterUsername and vCenterPassword fields and save this configuration.
Navigate to /etc/cisco/app_install and run the following command to re-register Cisco VSUM:
service tomcat stop; bash config_app.sh -rf; service tomcat start
Log in to Cisco UCS Director using the root credentials.
Navigate to /opt/infra/inframgr/resources.
Execute the managevsm.sh script using the following command:
./managevsm.sh
![]() Note | If you see problems while you add hosts or perform any other VSM related operations, you can flap the svs connection on the vCenter and redo the operation. |
Troubleshooting Cisco PNSC Installation Issues
You can manually remove an unsuccessful or a failed PNSC installation using the following steps.
Step 1 | Delete the
database entry for the <pnsc-vm-name> you want to delete, from the UCSD
table STINGRAY_AJAX_DATA.
To delete the database entry from the UCS Director database table, see Deleting a Database Entry From UCS Director Database Table. |
Step 2 | From the UCS Director UI, delete the entry for the respective <pnsc-name> from . |
Step 3 | Select the particular PNSC entry that you want to delete from the table and click Delete. |
Step 4 | Power off the PNSC-VM from the vSphere Client and delete the VM. |
This section includes symptoms, possible causes, and solutions for issues encountered while installing Cisco PNSC.
Symptom:The Cisco PNSC installation workflow fails with an error message.
java.net.UnknownHostException:< hostname_of_the_server >, selectedContext=<None>
Possible Causes:This occurs when the hosts are added to the VC via the host names and the DNS settings on the UCS Director are incorrect. The reachability to the host and the PNSC OVA deployment fails when either the DNS server is wrong, or when the DNS server is not listed as the first one in the UCS Director.
Troubleshooting Cisco Virtual Switch Update Manager Installation Issues
Use the following procedure to manually remove Cisco Virtual Switch Update Manager while installing the Cisco Nexus 1000V for Cisco VACS.
Step 1 | Delete the
database entry for the respective <vsum-vm-name> from the UCSD (Cisco UCS
Director) table ‘STINGRAY_AJAX_DATA’.
Delete the <vsum-vm>. For detailed instructions about deleting a database entry, see Deleting a Database Entry From UCS Director Database Table. |
Step 2 | Delete the extension - 'com.cisco.n1kv.headless' from the vCenter Server MOB from https://<vcenter-server-ip>/mob and click . |
Step 3 | Click UnregisterExtension and add the Extension key Value = com.cisco.n1kv.headless. |
Step 4 | Power off the <vsum-VM> from the vSphere Client and delete it. |
Troubleshooting Cisco Nexus 1000V VSM Installation Issues
Use the following procedure to manually remove a Cisco Nexus 1000V VSM.
Step 1 | From the Cisco
Nexus 1000V console, execute the following commands:
n1k-dvs-name# configure terminal n1k-dvs-name(config)#svs connection vCenter n1k-dvs-name(config-svs-conn)#no vmware dvs This will remove the DVS from the vCenter Server and any associated port-groups. Do you really want to proceed(yes/no)? [yes] yes n1k-dvs-name(config-svs-conn)#no connect n1k-dvs-name(config-svs-conn)#end n1k-dvs-name#copy running-config startup-config (optional) |
Step 2 | Power off the primary and secondary VSM VMs from the vSphere Client and delete both the VMs. |
Step 3 | Delete the
database entry for the respective <Nexus1000V-dvs-name> from the Cisco
UCSD table STINGRAY_AJAX_DATA.
To delete the database entry, see Deleting a Database Entry From UCS Director Database Table. |
Step 4 | Select the entry for the respective <Nexus1000V dvs> from Cisco UCS Director UI from Delete Nework Element. and click |
Step 5 | Delete the lock entry for a Cisco Nexus 1000V from the STINGRAY_LOCK_DATA table using the DELETE FROM STINGRAY_LOCK_DATA WHERE LOCKID=’<VSM-IP>’ ; command. |
This section includes symptoms, possible causes, and solutions for issues encountered while installing Cisco Nexus 1000V.
Symptom:The Cisco Nexus 1000V installation fails.
Handler failed with error - No route to host
Verification and Solution:Check if the ESX host is added to VCenter via the hostname or the IP address. Ping that hostname or IP address from the VSUM console and see if the ping is successful or not. If it is not successful, rectify the network/DNS settings and retry.
Symptom:The Cisco Nexus1000V Installation fails with nsc-pa-agent install failure. (PNSC-N1kv connection).
Possible Causes:Time sync issues between Cisco PNSC and Cisco Nexus 1000V.
Choose
to perform an inventory collection for the virtual account, Cisco PNSC, and Cisco Nexus 1000V:Check the connectivity between Cisco Nexus 1000V and Cisco PNSC. If the connectivity is fine, proceed to step 4.
Verify the connectivity between Cisco Nexus 1000V and the NTP server.
Check the time stamp using the and the show clock and the show ntp peer status commands.
If the NTP server is not reachable and if you want to configure a new NTP server, use the ntp server < NTP server IP address > command.
Verify the time and the NTP synchronization status using the show clock and the show ntp peer-status commands.
nsc-policy-agent no policy-agent-image no shared-secret no registration-ip
nsc-policy-agent registration-ip <PNSC Ip address> shared-secret <shared Secret used during PNSC deployment > policy-agent-image bootflash:/vsmcpa.3.2.2b.bin
show nsc-pa status
If the status shows an error message, then unconfigure the NTP server on Cisco 1000V using the no ntp server < NTP server IP address > command and configure the system clock using the clock set command, where the time should be 30 seconds ahead of the PNSC time stamp. Once configured, repeat step 9 and step 10.
After the installation of the PA is successful, perform step 1 and create a template.
Troubleshooting Adding Hosts Issues
Use the following procedure to manually remove the hosts added to the Cisco Nexus 1000V distributed virtual switch (DVS).
This section includes symptoms, possible causes, and solutions for issues encountered while adding hosts.
Symptom:The Port-profile screen does not show any port-profiles and manually adding one, throws an error stating that the vSwitch migration spec is missing.
Symptom:The add host operation fails when you add a host that has a VMWare DVS installed on it.
Verification and Solution:Either remove the VMWare DVS from that host or use another host that does not have the VMWare DVS installed on it.
Symptom:The add host operation could fail when you add a host which has a previous Cisco Nexus 1000V vib version.
Verification and Solution:Remove the Cisco Nexus 1000V vib version and add it again.
Symptom:The add host screen does not display the list of available hosts.
Verification and Solution:Reboot the VSUM.
Symptom: The add host operation fails with an error message.
INTERNAL_ERROR, VSUM Error Message : null
Possible Causes: The vSwitch of the PNIC that was used for the add host operation does not have any port groups.
Symptom: vm_kernel_IP_in_use VSUM Error Message : null
Verification and Solution:Change the VMKNIC IP (L3 or vteps) and submit the Add-host operation.
Symptom:virtualNIC_dendency_on_PNIC, VSUM Error Message : null
Verification and Solution:There was a VM template using VM network pg on that vSwitch. When you try to migrate the pnic mapped to vswitch to dvs, VSUM(Nexus1000V installer) throws an error.
Symptom: Vlans_not_backed, VSUM Error Message : null
Verification and Solution: If VLANs of existing vmknics/new L3 control vmknic/Vteps/VMs are not present in the uplink port-profile chosen for the pnics.
Symptom: VSM_operation error, VSUM Error Message : null
Verification and Solution: Some of the configuration commands have failed on the Nexus 1000V. Log in to Nexus 1000V and check the accounting log. The show accounting log will show some commands as 'FAILURE'.
Symptom:The add host operation completes without VSUM throwing up an exception, but the workflow times out.
Verification and Solution: Reboot the VSUM
This section includes symptoms, possible causes, and solutions for issue(s) encountered while creating a new template or editing an existing template.
Symptom:Creating a new template or editing an existing template fails with an error message.
No Registered PNSC Account found for the selected virtual account < Account Name > and switch < switch Name >
Possible Causes:Communication issues between Cisco PNSC and Cisco Nexus 1000V.
Choose
to perform an inventory collection for the virtual account, Cisco PNSC, and Cisco Nexus 1000V:Verify that the Cisco Nexus 1000V status is in a running mode in the Cisco PNSC. To verify this, do the following:
Check the connectivity between Cisco Nexus 1000V and Cisco PNSC. If the connectivity is fine, proceed to step 4.
Ensure that the NTP server is reachable from Cisco PNSC, and the time synchronization has happened properly. To verify this, log into Cisco PNSC using SSH and verify the time stamp using the show clock command. If the NTP server is not reachable from Cisco PNSC and if you want to change the NTP server, do the following:
Verify the connectivity between Cisco Nexus 1000V and the NTP server.
Check the time stamp using the and the show clock and the show ntp peer status commands.
If the NTP server is not reachable and if you want to configure a new NTP server, use the ntp server < NTP server IP address > command.
Verify the time and the NTP synchronization status using the show clock and the show ntp peer-status commands.
nsc-policy-agent no policy-agent-image no shared-secret no registration-ip
nsc-policy-agent registration-ip <PNSC Ip address> shared-secret <shared Secret used during PNSC deployment > policy-agent-image bootflash:/vsmcpa.3.2.2b.bin
show nsc-pa status
If the status shows an error message, then unconfigure the NTP server on Cisco 1000V using the no ntp server < NTP server IP address > command and configure the system clock using the clock set command, where the time should be 30 seconds ahead of the PNSC time stamp. Once configured, repeat step 9 and step 10.
After the installation of the PA is successful, perform step 1 and create a template.
Step 1 | Log on to Cisco
UCS Director as root user and enter
mysql
--user=admin --password=<ucsd db password> <db-name> to
access the UCS Director database.
example: mysql --user=admin --password=cloupia db_private_admin |
Step 2 | Enter the
following SQL query to delete a database entry from the UCS Director database
table:
DELETE FROM <table_name> WHERE <some_column>=<some_value>; example: DELETE FROM STINGRAY_AJAX_DATA WHERE VMNAME = ’vsum_vm’; |
Step 3 | Enter the following SQL query to examine the entries in the table
before or after the deletion:
SELECT ALL <comumn_name> FROM <table_name>; Example: SELECT ALL VMNAME FROM STINGRAY_AJAX_DATA; |