3-7
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 3 Installation
Managing Extension Keys
Known Extension Problems and Resolutions
Use the following table to troubleshoot and resolve known problems with plug-ins and extensions.
Resolving a Plug-In Conflict
If you see “The specified parameter was not correct,” when Creating a Nexus 1000V 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_nexus1000v_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 on page 3-8 to compare the
extension key installed on the VSM with the plug-in installed on the vCenter Server.
Finding the Extension Key on the Cisco Nexus 1000V
You can find the extension key on the Cisco Nexus 1000V.
BEFORE YOU BEGIN
• Log in to the Cisco Nexus 1000V VSM CLI in EXEC mode.
• Know that you can use the extension key in the “Unregistering the Extension Key in the vCenter
Server” section on page 3-12.
DETAILED STEPS
Step 1 From the Cisco Nexus 1000V for the VSM whose extension key you want to view, enter the following
command:
show vmware vc extension-key
Example:
switch# show vmware vc extension-key
Problem Resolution
The extension does not show up immediately in
the plugin.
Close the VI client and then open the VI client again.
You cannot delete the extension from the VI
client.
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 click the download and install link for the
extension. you see an invalid URI.
None.You do not need to click download and install. If you do, it has no
effect on the installation or connectivity. The plug-in only needs to be
registered with vCenter.