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 describes how to identify and resolve installation problems and includes the following topics:
This section explains how to isolate possible installation problems.
Before you begin to troubleshoot any installation issues, you should verify that your ESX server has the VMware Enterprise Plus license that includes the Distributed Virtual Switch feature.
Before you begin, you must know or do the following:
Step 1 From the vSphere web client, choose the host whose Enterprise Plus license you want to check.
Step 2 Click the Configuration tab and choose Licensed Features .
The Enterprise Plus licensed features are displayed.
Step 3 Verify that the following are included in the Licensed Features:
Step 4 Do one of the following:
If you have added hosts and adapters with your VSM, you must also add them in the vCenter Client Add Host to Distributed Virtual Switch dialog box shown in Figure 3-1.
Figure 3-1 Host is Visible from the Distributed Virtual Switch
If the hosts and adapters do not appear in this dialog box, you might have the incorrect VMware license installed on your ESX server.
Use the Verifying Your VMware License Version to confirm.
Figure 3-2 Host is Not Visible from the Distributed Virtual Switch
If wrong map of management port group is configured during VSE deployment, host is not visible from the distributed virtual switch. Complete the following steps to resolve this issue:
Step 1 Log into the plug-in and select the correct data center and switch.
Step 2 Select the host and pNICs.
Step 3 Enter all the parameters.
Step 4 Map to the correct Management port group .
You can refresh the connection between the Cisco Nexus 1000VE and vCenter Server.
Step 1 From the Cisco Nexus 1000VE Connection Configuration mode on the Virtual Supervisor Module (VSM), enter the following command sequence:
Step 2 You have completed this procedure.
Use the following pointers to improve performance on the ESX host and the VMs.
The Virtual Supervisor Module (VSM) and Virtual Service Engine Module (VSE) are separated within a Layer 2 domain. To allow VSM-VSE pairs to communicate within the same Layer 2 domain, each pair must have a unique identifier. The domain ID serves as the unique identifier that allows multiple VSM-VSE pairs to communicate inside the same Layer 2 domain.
Following the installation of the Cisco Nexus 1000VE, make certain that you configure a domain ID. Without a domain ID, the VSM cannot connect to the vCenter Server. Follow these guidelines:
You can verify that two port groups are created on the ESX hosting the VSM VM through the vCenter Server. The following port groups (PG) should be created:
Make sure the port groups are assigned to the three virtual interfaces of the VSM VM in the following order:
To verify if the VSM VM network adapter 1, network adapter 2, and network adapter 3 are carrying the control VLAN, management VLAN, and the packet VLAN, follow these steps:
Step 1 Enter the show mac address-table dynamic interface vlan control-vlan command on the upstream switch.
Expected output: the network adapter1 MAC address of the VSM VM.
Step 2 Enter the show mac address-table dynamic interface vlan mgmt-vlan command on the upstream switch.
Expected output: the network adapter2 MAC address of the VSM VM.
Step 3 Enter the show mac address-table dynamic interface vlan packet-vlan command on the upstream switch.
Expected output: the network adapter3 MAC address of the VSM VM.
When troubleshooting connectivity between the VSM and vCenter Server, follow these guidelines:
Step 1 Ensure that the Nexus 1000VE VSM VM network adapters are configured properly.
Step 2 Make sure that the Windows VM machine hosting the vCenter Server has the following ports open:
Step 3 Ping the vCenter Server from the Cisco Nexus 1000VE VSM.
Step 4 Ensure that the VMware VirtualCenter Server service is running.
For information about recovering the network administrator password, see the Cisco Nexus 1000V Password Recovery Guide .
This section includes the following topics:
Use the following table to troubleshoot and resolve known problems with plug-ins and extensions.
If you delete the extension using Manager Object Browser (MOB), the VI client screen might not refresh and indicate that the extension was deleted. In this case, close the VI client and then open the VI client again.
If you see “The specified parameter was not correct,” when Creating a Nexus 1000VE plug-in on vCenter Server, you have tried to register a plug-in that is already registered.
Use the following procedure to resolve this problem.
Step 1 Make sure that you are using the correct cisco_nexus1000ve_extension.xml file.
Step 2 Make sure that you have refreshed your browser because it caches this file and unless refreshed it might cache obsolete content with the same filename.
Step 3 Follow the steps described in the “Verifying Extension Keys” section to compare the extension key installed on the VSM with the plug-in installed on the vCenter Server.
Step 1 From the Cisco Nexus 1000VE for the VSM whose extension key you want to view, enter the following command:
You can find the extension key tied to a specific DVS.
Step 1 From the vSphere Client, choose the DVS whose extension key you want to find.
The Summary tab opens with the extension key displayed in the Notes section of the Annotations block.
You can verify that the Cisco Nexus 1000VE and vCenter Server are using the same extension key.
Step 1 Find the extension key used on the Cisco Nexus 1000VE using the “Finding the Extension Key on the Cisco Nexus 1000VE” section.
Step 2 Find the extension key used on the vCenter Server using the “Finding the Extension Key Tied to a Specific DVS” section.
Step 3 Verify that the two extension keys (the one found in Step 1 with that in Step 2) are the same.
You can re-create the complete Cisco Nexus 1000VE configuration in the event of a persistent problem that cannot be resolved using any other workaround.
Flowchart: Re-creating the Cisco Nexus 1000VE Installation
Step 1 From vSphere Client, choose Inventory > Networking .
Step 2 Choose the DVS for the Cisco Nexus 1000VE and click the Hosts tab.
Step 3 Right-click each host, and choose Remove from Distributed Virtual Switch .
The hosts are now removed from the DVS.
You can remove the Cisco Nexus 1000VE DVS from vCenter Server.
Step 1 From the Cisco Nexus 1000VE VSM, use the following commands to remove the DVS from the vCenter Server.
The DVS is removed from vCenter Server.
Step 2 You have completed this procedure.
Return to the “Flowchart: Re-creating the Cisco Nexus 1000VE Installation” section.
You can unregister the Cisco Nexus 1000VE extension key in vCenter Server.
Before beginning this procedure, you must know or do the following:
Step 1 Point your browser to the following URL:
The Extension Manager opens in your Manager Object Browser (MOB).
Step 2 Click Unregister Extension .
A dialog box opens to unregister the extension.
Step 3 In the value field, paste the extension key that you found in the “Finding the Extension Key on the Cisco Nexus 1000VE” section, and then click Invoke Method.
The extension key is unregistered in vCenter Server so that you can start a new installation of the Cisco Nexus 1000VE VSM software.
Step 4 You have completed this procedure.
Return to “Flowchart: Re-creating the Cisco Nexus 1000VE Installation” section.
The following are possible problems and their solutions.
After loading the previously saved configuration file, the installation application does not complete.
Note You might need to change a few of the fields before reusing the previously saved files.
This can be identified by reviewing the Virtual Machine field in the configuration file.
The VSE loses its management IP after reboot and gets disconnected from the VSM.
When VSE is installed using a static IP pool from vCenter with multiple DNS server addresses, after reboot VSE gets disconnected from VSM.
– Manually configure multiple DNS addresses in the VSE using the nmtui command as root.
– Use only a single DNS server in the IP pool in vCenter and then re-deploy the VSE.