Cisco CSR 1000V Series Cloud Services Router Software Configuration Guide
Troubleshooting Cisco CSR 1000V VM Issues
Downloads: This chapterpdf (PDF - 171.0KB) The complete bookPDF (PDF - 3.44MB) | Feedback

Table of Contents

Troubleshooting Cisco CSR 1000V VM Issues

Verifying the Cisco CSR 1000V Hardware and VM Requirements

Troubleshooting Network Connectivity Issues

Troubleshooting VM Performance Issues

Verifying the Cisco CSR 1000V Hardware and VM Requirements

To help troubleshoot issues with the Cisco CSR 1000V, make sure that the router is installed on supported hardware and that the VM requirements are being met:

  • Verify that the server hardware is supported by the hypervisor vendor.

If using VMware, verify that the server is listed on the VMware Hardware Compatibility List. See the VMware documentation for more information.

  • Verify that the I/O devices (for example, FC, iSCSI, SAS) being used are supported by the VM vendor.
  • Verify that sufficient RAM is allocated on the server for the VMs and the hypervisor host.

If using VMware, make sure the server has enough RAM to support both the VMs and ESXi.

  • Verify the hypervisor version is supported by the Cisco CSR 1000V.
  • Verify that the correct VM settings for the amount of memory, number of CPUs, and disk size are configured.
  • Verify that the vNICs are configured using a supported network driver. See the “Installation Overview” section.

See the “Cisco CSR 1000V Series Cloud Services Router Overview” section, and the Cisco CSR 1000V Series Cloud Services Router Release Notes .

Troubleshooting Network Connectivity Issues

To troubleshoot network connectivity issues for the Cisco CSR 1000V, do the following:

  • Verify that there is an active and unexpired license installed on the VM.

Enter the show license command. The License State should be shown as “Active, In Use”.

  • Verify that the vNIC for the VMs are connected to the correct physical NIC, or to the proper vSwitch.
  • If using virtual LANS (VLANs), make sure the vSwitch is configured with the correct VLAN.
  • If using static MAC addresses, or VMs that are cloned, make sure there are no duplicate MAC addresses.

Duplicate MAC addresses can cause the Cisco CSR 1000V feature license to become invalidated, which will disable the router interfaces.

Troubleshooting VM Performance Issues

The Cisco CSR 1000V operates within a set of supported VM parameters and settings to provide certain levels of performance that have been tested by Cisco.

Use vSphere Client to view data to troubleshoot VM performance. If you’re using vCenter, you can view historical data. If you’re not using vCenter, you can view live data from the host.

Do the following to troubleshoot performance issues:

  • Verify that the router is configured for the correct MTU setting.

By default, the maximum MTU setting on the router is set to 1500. To support jumbo frames, you need to edit the default VMware vSwitch settings. For more information, see the VMware vSwitch documentation.


Note ESXi 5.0 supports a maximum MTU size of 9000, even if jumbo frames are enabled on the router.


  • The Cisco CSR 1000V does not support memory sharing between VMs. On the ESXi host, check the memory counters to find out how much used memory and shared memory is on the VM. Verify that the balloon and swap used counters are zero.
  • If a given VM does not have enough memory to support the Cisco CSR 1000V, increase the size of the VM’s memory. Insufficient memory on the VM or the host can cause the Cisco CSR 1000V console to hang and be non-responsive.

Note When troubleshooting performance issues, note that other VMs on the same host as the Cisco CSR 1000V can impact the performance of the Cisco CSR 1000V VM. Verify that other VMs on the host are not causing memory issues that are impacting the Cisco CSR 1000V VM.


  • Verify that no network packets are being dropped. On the ESXi host, check the network performance and view the counters to measure the number of receive packets and transmit packets dropped.
  • Verify the current maximum throughput level with the show platform hardware throughput level command.