- Overview of Cisco Catalyst 8000V Edge Software
- Using Cisco IOS XE Software
- Installation Overview
- Installing in VMware ESXi Environment
- Installing in KVM Environments
- Installing in Microsoft Hyper-V Environments
- Installing in Citrix XenServer Environments
- Configuring Day 0 Settings
- Cisco Catalyst 8000V Licensing
- Verifying the Cisco Catalyst 8000V Hardware and VM Requirements
- Configuring Console Access
- Configuring the vCPU Distribution across Data, Service, and Control Planes
- Web User Interface Management
- Finding Command Options
- Upgrading the Cisco IOS XE Software
- Accessing and Using GRUB Mode
- Performing a Factory Reset
- Troubleshooting VM Issues
- Mapping the Cisco Catalyst 8000V Network Interfaces to VM Network Interfaces
- Packet Trace
- Configuring VRF Route Sharing
- Radio Aware Routing
Verifying the Cisco Catalyst 8000V Hardware and VM Requirements
To help troubleshoot issues with Cisco Catalyst 8000V, ensure that the router is installed on the supported hardware and that the VM requirements are being met:
-
Verify that the server hardware is supported by the hypervisor vendor.
If you're 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 you're using VMware, ensure that the server has enough RAM to support both the VMs and VMware ESXi.
-
Verify the hypervisor version is supported by Cisco Catalyst 8000V.
-
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.
-
From Cisco IOS XE 17.6.1, you can enable the FIPS mode if the host and VM supports RDRAND or RDSEED, or both instructions. Otherwise, an error message is displayed.
Note
Some hypervisors have configuration options or runtime options to block the use of RDSEED or RDRAND, or both in a VM. These options must not be enabled. That is, RDSEED or RDRAND, or both must not be blocked by the hypervisor if you want to enable the FIPS mode.
Feedback