UC Voice Application Connectivity in a VMware UCS Environment

Available Languages

Download Options

PDF (513.0 KB)
View with Adobe Reader on a variety of devices
ePub (71.7 KB)
View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle) (69.5 KB)
View on Kindle device or Kindle app on multiple devices

Updated:November 19, 2013

Document ID:116743

Bias-Free Language

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.

Introduction

Troubleshoot

Introduction

This document describes how to troubleshoot connectivity issues when Cisco Unified Communications Manager (CUCM), Cisco Unity Connection, or Cisco Unified Contact Center Express (UCCX) is installed on a Unified Computing System (UCS) platform but cannot be reached.

This document uses the example of a CUCM that is a virtual machine (VM) on the VMware ESXi host on the UCS platform.

Troubleshoot

This procedure describes how to troubleshoot connectivity issues between a CUCM VM and a UCS. The steps are:

Verify the VM Network Interface Controller (NIC) state.
Check connectivity.
Verify the Layer 2 (L2) connectivity.
Verify the Layer 3 (L3) connectivity.
Verify the port-group configuration.
Verify the VSwitch configuration.
Remove any improperly configured adapters.

Notes:

Use the Command Lookup Tool (registered customers only) in order to obtain more information on the commands used in this section.

The Output Interpreter Tool (registered customers only) supports certain show commands. Use the Output Interpreter Tool in order to view an analysis of show command output.

On the CUCM command-line interface (CLI) console, enter the show network eth0 command, and verify the VM NIC state:
- Status: up
- Link Detected: yes
- Mode: Auto enabled, Full, 1000 Mbits/s
- Duplicate IP: no
- Confirm the configured IP Address
Attempt to ping the default gateway with the utils network ping default gateway IP command in order to check connectivity. If the gateway is not accessible, continue with the next steps.
Log in to the upstream switch that is connected to the UCS, and enter the show mac-address command in order to verify L2 connectivity. Verify that the CUCM VM address has been learned by the upstream switch. In VSphere, right-click the VM, select Edit-Settings, navigate to the Hardware tab, and select the Network Adapter:
If Step 3 confirmed that the MAC address has been learned, verify L3 connectivity. Create a VLAN interface, and ping the default gateway from the switch in order to verify that the upstream switch can route on the VLAN. Verify the port-group used by the CUCM VM. In this example, the port-group is assigned to VLAN-475.
Navigate to the UCS host Configuration tab. In the Hardware section, click Networking in order to verify port-group configuration. Check the port-group identified in Step 4, and verify the associated physical adapters:
Click the blue icon next to each physical adapter in order to verify VSwitch configuration and view the Cisco Discovery Protocol (CDP) neighbor details. In this example, the switches are vmnic1 amd vmnic3. If the CDP details are not shown, the switch is not configured properly.

See the VMware document, "Cisco Discovery Protocol (CDP) network information (1007069) ," for more information.

Note: If there are multiple physical adapters, all devices should show the CDP details properly. Even if only one is not shown properly, the communication might be disrupted because the load is balanced among all of the added or configured physical adapters.
Verify the configuration on the upstream port shown in the CDP information. For example, ensure that the interface is set to trunking and the port-group VLAN is allowed. If the port-group does not have a VLAN mapping, ensure that the upstream switch has the correct native VLAN set or is accessing the correct VLAN.

This is a sample configuration for the VLAN-475 setup for trunking:
```
interface gigabitEthernet1/0/2
    switchport mode trunk
    switchport trunk allowed vlan 400-475
    spanning-tree portfast trunk 
```
This is a sample configuration with trunking, but no VLAN tagging in the port-group:
```
interface gigabitEthernet1/0/2
    switchport mode trunk
    switchport trunk allowed vlan 400-475
    spanning-tree portfast trunk
    switchport trunk native vlan 4
```
Step 6 might reveal that CDP neighbor details are not shown for the physical adapters and that other adapters do have CDP details. A temporary workaround is to remove the improperly configured physical adapter:
1. Click Properties:
2. Click the Network Adapters tab, click the device name, and click Remove:
3. Confirm that the network connectivity from the CUCM VM has been restored.