◦
If the server is set to perform graceful failover or restart, enter the
clear platform software vnic-if
nvtable
command before executing the failover or restart.
This issue is not seen if the maximum number of interfaces is configured.
•
When the Cisco CSR 1000v is installed on Microsoft Hyper-V, if you want to configure a VLAN, you
must configure the VLAN interfaces on Microsoft Hyper-V using the Hyper-V Power Shell CLI.
•
When the Cisco CSR 1000v is installed on Microsoft Hyper-V and an NSF-based virtual hard disk is
used, if there is a network connectivity issue between the Cisco CSR 1000v and the NSF server, the
Cisco CSR 1000v is unable to use the virtual hard disk even if the network connection is restored. You
must reboot the Cisco CSR 1000v to restore access to the virtual hard disk.
•
The Microsoft Hyper-V GUI only allows one VLAN to be specified for a Virtual Machine interface.
This limits deployments where multiple VLANS for a Virtual Machine interface are used.
•
When the MAC address of a Cisco CSR1000v interface is changed from the address assigned by the
hypervisor, then traffic to and from external devices is unsuccessful. This occurs even when MAC
address spoofing is enabled on the Microsoft Hyper-V vSwitch. Operation of protocols like FHRP,
CLNS, and Etherchannel that use their own MAC address may be unsuccessful.
•
In Microsoft Hyper-V environments, the following limitations apply when the Windows Power Shell
CLI is used to configure VLANs:
◦
The power shell CLI commands must be reapplied each time the Cisco CSR1000v is reloaded.
◦
When a large AllowedVlanIdList is configured, only lower numbered VLANS may successfully
pass traffic. For example, when the following Power Shell CLI command is used:
Set-VMNetworkAdapterVlan -VMName dr-vm-6-1 -Trunk -AllowedVlanIdList 1-2000 -NativeVlanId 0
Only VLANS lower than 300 may successfully pass traffic.
Cisco CSR 1000v and Hypervisor Limitations for Cisco IOS XE Release 3.10S
•
Configuring Network Based Application Recognition (NBAR), or Application Visibility and Control
(AVC) support on the Cisco CSR 1000v requires a minimum of 4GB of DRAM on the VM, even when
using the one vCPU configuration on the VM.
•
On the Cisco CSR 1000v, all the NICs are logically named as the Gigabit Ethernet interface. The Cisco
CSR 1000v does support the 10G IXGBE vNIC in passthrough mode; but that interface also is also
logically named as a Gigabit Ethernet interface. Note that with emulated devices like
VMXNET3/PV/VIRTIO from the hypervisor, the Cisco CSR 1000v is not aware of the underlying
interfaces. The vSwitch may be connected to a 10-GB physical NIC or 1-GB physical NICs or multiple
NICs (with NIC teaming on the hypervisor) as well.
•
The Cisco CSR 1000v supports an MTU range from 1500 to 9216 bytes. However, the maximum MTU
supported on your hypervisor version may be lower. The MTU value configured on the Cisco CSR
1000v should not exceed the maximum MTU value supported on the hypervisor.
Cisco CSR 1000v and Hypervisor Limitations for Cisco IOS XE Release 3.9S
The following are the Cisco CSR 1000v and VMware ESXi limitations for Cisco IOS XE Release 3.9S:
Cisco CSR 1000v Series Cloud Services Router Software Configuration Guide
25
Cisco CSR 1000v Series Cloud Services Router Overview
Hypervisor Support