Under Disk Format, select the disk format option (select the default). Under Deployment Configuration, select the desired hardware configuration (AP and client scale) profile from the drop-down menu and click Next. Under Name and Location, specify the name for the VM and click Next. Verify the OVA template details and click Next. In the OVA wizard, point the source to the Cisco wireless controller OVA to be deployed. From the vSphere client menu bar, choose File > Deploy OVF Template. Perform the following steps in the VMware vSphere client. VMware ESXi provides a direct deployment of the virtual Catalyst 9800-CL wireless controller without bootstrap customization (see “Deploying the OVA to ESXi 6.0 with vCenter Server”).
At FCS the serial console port is not supported for large-scale deployments Appendix A describes how to configure it, in case you want to use it.ĭeploying the 9800-CL OVA to an ESXi 6.0 host using the vSphere client A virtual serial port is optional and can be added after deploying the OVA. You can monitor the installation process on the virtual VGA console or the console on the virtual serial port.When deploying using the OVA template, the VM will bootstrap with three interfaces: one is for out-of-band management, one is for wireless management (usually mapped to a trunk interface on the switch side), and the third is for HA to connect to the SSO peer.We do not recommend changing the virtual CPU and memory configuration after deployment. The hard disk requirement will be the same-8 GB-for any wireless controller type. Selecting a profile specifies the required virtual CPU and memory. The single OVA package creates a VM with options for three types of virtual wireless controllers, small, medium, and large.The following considerations apply when deploying the OVA package to the VM: The OVA package includes an OVF file that contains a default VM configuration based on the Cisco IOS ® XE release and the supported hypervisor. You can use the provided OVA file package to deploy the Cisco wireless controller to the VM.
High Availability (HA) is supported on the 9800-CL VM hosts using virtual redundant ports, in a stateful switchover (SSO) configuration.Ĭatalyst 9800-CL deployment OVA template (OVA)Ĭatalyst 9800-CL upgrade and patches (bin)ĭeploying the 9800-CL OVA to ESXi using the vSphere client
Note: To avoid stability and performance issues, it’s advisable to fully reserve the vCPU resources needed for the 9800-CL and never oversubscribe them. Note: For the Cisco ENCS platform, only the small size is supported (1000 APs and 10,000 wireless clients). Note: In the low throughput templates 2 cores are allocated to dataplane (packet processing) and in the high throughput templates 5 cores are allocated to dataplane functionality Note: Cloning from snapshots is not supported. Note: VM operations like DRS, Snapshot, vMotion, vNIC teaming are not supported with SR-IOV. Minimum Number of vCPUs (Hyperthreading is not supported) Templates added as part of IOS XE 17.3 release Existing supported templates Pre IOS XE 17.3 release