Migrating from VRRP or Backup-LMS Redundancy

High Availability: Fast Failover provides redundancy for APs, but not for controllers. Deployments that require master controller redundancy should continue to use an existing VRRP Virtual Router Redundancy Protocol. VRRP is an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. redundancy solution. If your deployment currently uses a backup-LMS Local Management Switch. In multi-controller networks, each controller acts as an LMS and terminates user traffic from the APs, processes, and forwards the traffic to the wired network. or VRRP Virtual Router Redundancy Protocol. VRRP is an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. redundancy solution, use the following procedures to migrate to a High-Availability-based solution. For more information on this topology, see High Availability Deployment Models.

Migrating from VRRP Redundancy

The following procedure migrates from VRRP Virtual Router Redundancy Protocol. VRRP is an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. to High-Availability redundancy:

  1. Remove the VRRP Virtual Router Redundancy Protocol. VRRP is an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. IP address as the LMS Local Management Switch. In multi-controller networks, each controller acts as an LMS and terminates user traffic from the APs, processes, and forwards the traffic to the wired network. IP address of the AP.

    (host)[mynode](AP system profile) #no lms-ip

  2. Configure the AP to use the active controller’s IP address (not the VRRP Virtual Router Redundancy Protocol. VRRP is an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. IP address) as the LMS Local Management Switch. In multi-controller networks, each controller acts as an LMS and terminates user traffic from the APs, processes, and forwards the traffic to the wired network. -IP for the AP.

    (host)[mynode](AP system profile) #lms-ip <ipaddress>

  3. Configure the AP to use the standby controller IP address (not the VRRP Virtual Router Redundancy Protocol. VRRP is an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. IP address) as the backup LMS Local Management Switch. In multi-controller networks, each controller acts as an LMS and terminates user traffic from the APs, processes, and forwards the traffic to the wired network. -IP for the AP.

    (host)[mynode](AP system profile) #bkup-lms-ip <ipaddress>

  4. Configure the master controller with a dual role in the high-availability group profile.

    (host)[mynode](config) #ha group-profile grp1

    (host)[mynode](HA group information "grp1"): controller <ipaddress> role dual

  5. Configure the standby controller with a dual role in the high-availability group profile.

    (host)[mynode](HA group information "grp1"): controller <ipaddress> role dual

Migrating from Backup-LMS Redundancy

The following steps migrates from Backup-LMS Local Management Switch. In multi-controller networks, each controller acts as an LMS and terminates user traffic from the APs, processes, and forwards the traffic to the wired network. to High-Availability redundancy and maintains the existing configuration as defined by the lms-ip and bkup-lms-ip parameters in the AP system profile.

  1. Configure the controller serving the AP with a dual role in the high-availability group profile.

    (host)[mynode](config) #ha group-profile grp1

    (host) (HA group information "grp1"): controller <ipaddress> role dual

  2. Configure the AP’s standby controller with a dual role in the high-availability group profile.

    (host)[mynode](HA group information "grp1"): controller <ipaddress> role dual