Wireless management interface of both VMs must be in the same subnet.Both devices have their own wireless management interface.The IP addresses of the Redundant Port should be on the same subnet.Both VMs are running in the same installation mode.Both VMs are running the same version of software.Keep the VMs on the same platform (ESXi, KVM, AWS, etc).There are some restrictions to keep in mind before configuring High Availability:
This post describes configuring High Availability for the Catalyst 9800-CL in VMware ESXi 6.7. The third interface, GigabitEthernet3, is used as the dedicated Redundancy Port (RP). When deploying the Catalyst 9800-CL, there are three interfaces binded in the configuration. The access points will not go into a Discovery state and clients will not get disconnected. In summary, when the Active wireless controller fails, the Standby takes over with the access points and clients still connected seamlessly. Additionally, a client database is copied to the Standby wireless controller. The Active controller will copy a database of joined access points to the Standby wireless controller. Stateful switchover allows access points to establish a CAPWAP tunnel to the Active controller. In this configuration, there will be an Active and Standby wireless controller. High availability (HA) will provide minimal downtime for the wireless controllers. In regards to the Catalyst 9800-CL wireless LAN controller, we have the ability to configure two instances in high availability with stateful switchover. If that host failed, you lose everything. I’d be nervous to have all my virtual machines on a single host. With Catalyst 9800 wireless LAN controller capable of being installed as a virtual machine, do you really need high availability? Everyone wants high availability with their infrastructure.
0 kommentar(er)
