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.
|
-
Copy
the OVA file to your local machine.
-
Verify
the file integrity by using the
bash$ls n1kv-manager.ova
n1kv-manager.ova.md5 bash$md5sum n1kv-manager.ova command. The
output displays the OVA file contents.
-
The
contents of the OVA file must match the MD5 file contents. to those of the md5
file.
If the
contents do not match, copy the OVA file once again.
|
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.
|
-
Log in
to Cisco Virtual Switch Update Manager using the default credentials.
-
View
the installation log available at
/etc/cisco/app_install/logs/ n1kv-manager_install.log
to view the NoRouteToHostEx error.
-
Ensure
that the correct port group is selected for the virtual machine (VM) and ping
the default gateway.
To add or
edit the IP address of the VM, do the following:
-
Navigate to
/etc/cisco/app_install.
-
Copy
the cfg template to app.cfg using the
cp app.cfg.template
app.cfg command.
-
Open
the cfg template by using the
vi app.cfg
command.
-
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
./config_app.sh
-n command to re-register and update the network parameters.
|
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.
|
-
Log in
to Cisco Virtual Switch Update Manager using the default credentials.
-
View
the installation log available at
/etc/cisco/app_install/logs/ n1kv-manager_install.log
to view the InvalidLogin error.
-
Ensure
that all the networking issues are resolved and redeploy Cisco Virtual Switch
Update Manager with the correct credentials.
To add or
edit the IP address or the credentials of the VM, do the following:
-
Navigate to
/etc/cisco/app_install.
-
Copy
the cfg template to app.cfg using the
cp app.cfg.template
app.cfg command.
-
Open
the cfg template by using the
vi app.cfg
command.
-
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
./config_app.sh
-r command to re-register the Cisco Virtual Switch Update
Manager.
|
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.
|
-
Enter
https://<the assigned vCenter IP address>mob in a web
browser.
-
Choose
Content
> Extension Manager.
-
Unregister the file with extension cisco.cisco.n1kv.
-
Delete
the
com.cisco.n1kv-1.0 folder:
Note
|
com.cisco.n1kv-1.0 is the version used for VSUM 1.0.
If you are using VSUM 1.1/1.2/1.3/1.x, select the corresponding version folder.
|
- In a Windows server, this
folder is available at
C:\ProgramData\VMware|vSphere Web Client\
vc-packages\vsphere-client-serenity.
-
In
a Linux server, this folder for vCenter 5.1 and 5.5 is available at
"rm -rf
/var/lib/vmware/vsphere-client/ vc-packages/ vsphere-
client-serenity/com.cisco.n1kv-1.0/.
-
In
a Linux server, this folder for vCenter 6.0 is
etc/vmware/vsphere-client/
vc-packages/vsphere-client-serenity/ com.cisco.*
-
Restart vCenter vSphere Web Client:
-
For a Windows server, choose
to restart vCenter
vSphere Web Client.
-
For the Linux server, run the
/etc/init.d/vsphere-client
restart
command.
-
Redeploy the VM to register it.
|
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:
Note
|
Changing the port number on vCenter requires a reboot of
vCenter. Ensure that port 8443 is open. Cisco VSUM uses port 8443 for
communication with vCenter.
|
|
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:
-
Power
off the current active VSUM VM and delete it.
-
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.
If the
com.cisco.n1kv extension not available, move to the next step.
- Choose
Start and then run
services.msc.
- Right-click the VMware
vSphere Web Client and click
Stop.
-
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.
-
Check
if the web client UI is working after starting the service and logging out.
-
Install the new Cisco VSUM using the OVA.
Ensure that all parameters such as port group, IP address, vCenter credentials,
and port number are correct during installation.
-
After
Cisco VSUM is successfully deployed, login to the VMware vSphere Web Client to
view the Cisco VSUM plugin.
|
For
vCenter on Linux, do a clean uninstall and reinstall of VSUM by performing the
following steps:
-
Power
off the current active VSUM VM and delete it.
-
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.
If the
com.cisco.n1kv extension not available, move to the next step.
-
Go to
the
/var/lib/vmware/ vsphere-client/vc-packages/vsphere-
client-serenity/ directory and delete the entire com.cisco.n1kv
folder using the
rm -rf
com.cisco.n1kv* command.
-
Restart VMware vSphere Web Client service using the
/etc/init.d/vsphere-client
restart command.
-
Check
if the web client UI is working after starting the service and logging out.
-
Install new the Cisco VSUM using the OVA.
Ensure that all parameters such as port group, IP address, vCenter credentials,
and port number are correct during installation.
-
After
Cisco VSUM is successfully deployed, login to the VMware vSphere Web Client to
view the Cisco VSUM plugin.
|