You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

In this section:

Typical VMware ESXi Virtual Environment

Top-Level Troubleshooting Flow

After switchover,  if Calls/Registrations do not work, then  check the GARP settings at the router. Generally, by default,  in routers such Juniper SRX, this setting is disabled. For details, see the link:

http://kb.juniper.net/InfoCenter/index?page=content&id=KB24349


Troubleshooting at VM Level

Troubleshoot SBC SWe inside VM using available CLI commands, DBG/SYS logs and call trace filter rules for both signaling and media traffic.

Troubleshooting at ESXi Host Level

Please refer to VMware documentation for troubleshooting guidance. For VMware ESXi troubleshooting, please refer to vsphere-esxi-vcenter-server-51-troubleshooting-guide.pdf.

Collecting Diagnostic information at VMware ESXi Hypervisor

Use "vm-support" command to create a .tgz archive file of the ESXi logs, command results, and configuration information at the ESXi.

Accomplish the following steps:

  1. Login to ESXi host shell using ESXi Management IP address.
  2. Ensure “ssh” is enabled on ESXi host (use vSphere to enable it if not already enabled).

  3. Enter the following command to view a list of vm-support command options:

    vm-support -h

Send the bundled file to

Unable to show "metadata-from": No such page "_space_variables"
 for further debugging.

Reference:

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1010705

Troubleshooting During Switchover

As a part of the

Unable to show "metadata-from": No such page "_space_variables"
 switch-over process, the
Unable to show "metadata-from": No such page "_space_variables"
 moves the IP (Floating IP) to a a different NIC. The
Unable to show "metadata-from": No such page "_space_variables"
 then reconfigures the NICs appropriately and broadcasts a GARP reply to inform neighboring devices about the change in the MAC address for the floating IP.Devices that receive the ARP packet then update their ARP tables with the new MAC address.

When the system experiences RTP issues after failovers, it is probably due to the fact that newly active interfaces are not discovered on the switch.   

The link provides the recommended settings:

http://kb.juniper.net/InfoCenter/index?page=content&id=KB24349

  • No labels