Cisco Cisco Expressway Installation Guide
VMware Checklist
1.
Check the accessibility to the VM host server (by ping, physical console access, ssh remote access, KVM-
over-IP console, and so on).
over-IP console, and so on).
2.
Check the network connectivity of the VMkernel (by executing the
vmkping
command using Tech Support
Mode to verify network connectivity from the VMkernel NIC level).
3.
If you are having problems connecting to the vSphere Client management console, execute the command
/sbin/services.sh
from an SSH session to restart the ESXi management agent.
4.
Check the utilization of the VM host server (CPU utilization, memory utilization, disk access speed, storage
access speed, network access status, power utilization, and so on).
access speed, network access status, power utilization, and so on).
If any specific application causes high utilization, stop or restart this application to isolate the overall VM host
performance level. Alternatively execute the command
performance level. Alternatively execute the command
esxtop
from Tech Support Mode to list all system
processes running on the ESXi host application.
5.
Check the ESXi server file log (hostd.logs) under the folder /var/log/vmware.
This log contains common error logs such as iSCI naming error, authentication error, host convertibility error,
and so on.
and so on.
6.
Verify that there is adequate disk space available on the physical volume that stores the database files, and
free up disk space if necessary.
free up disk space if necessary.
7.
Validate the authentication to the vCenter Server database. The vCenter Server service may not be able to
authenticate with the database if:
authenticate with the database if:
a.
There are permission issues with the database when importing from one instance to another.
b.
The password on the account you are using to authenticate to the database has changed but the
password in the registry has not changed as well.
password in the registry has not changed as well.
c.
The vCenter Server database user is not granted correct permissions.
Isolating a Possible Root Cause
Potential
issue area
issue area
What to look for
Storage
Look for the VM store application image stored either on the local drive, SAN or NFS. VMs often freeze
or hang up if the application failed to access the storage. Possible error messages are:
or hang up if the application failed to access the storage. Possible error messages are:
■
vCenter Server does not start
■
vCenter Server is slow to respond
■
vCenter Server fails after an indefinite amount of time
Network
Any network failure or locking causes a connection failure between the VM and the virtual network.
Also, if using NFS or iSCSI, storage may cause application failures because the application cannot
access the file system.
Also, if using NFS or iSCSI, storage may cause application failures because the application cannot
access the file system.
DNS
DNS server failures or communication failures between DNS and the VM server may cause the
VMware application or the VM Expressway application to fail.
VMware application or the VM Expressway application to fail.
vCenter
Server
Server
If vCenter is not operating properly, even though the VM Expressway application is still up and
running, you may lose connection to the VM Expressway application from the network.
running, you may lose connection to the VM Expressway application from the network.
Host
application
application
Check any critical alarms on the VM application for events on the host or application level (check the
event information from vSphere Client).
event information from vSphere Client).
20
Cisco Expressway on Virtual Machine Installation Guide
Appendix 1: Troubleshooting