Alcatel-Lucent AOS-W 6.5.3.x - Migrating from VRRP or Backup-LMS Redundancy

MIBs/SNMP Tables
The following are the new MIBs introduced in AOS-W 6.5.1.0 for High Availability Alerting:
n High Avalability Config Table: wlsxHighAvalabilityConfigTable—provides HA enabled/disabled status, HA
group membership, and parameters configured in HA group profile.
n HA AP Table: wlsxHighAvalabilityApTable—provides Active APs count, Standby APs count, and Total APs
count.
n Interswitch Heartbeat Table: wlsxIntercontrollerHbtTable—provides Active switch IPs, Reference count, and
heartbeat statistics for each active switch.
n HA State Sync Table: wlsxStateSyncTable—provides active/replicated/total PMK cache entries and key cache
entries count.
n HA Tunnel Table: wlsxHighAvalabilityTunnelTable—provides active/standby/total BSS tunnel count and total
heartbeat tunnel count.
All the MIBs for the HA Alerting feature are implemented in wlsxHaMIB.
For more information on the MIBs and OIDs, refer to the aruba-ha.my MIBfile, which is available within the
MIB files along with the release on https://support.esd.alcatel-lucent.com/.
SNMPTraps
The new SNMP traps introduced for High Availability Alerting in AOS-W 6.5.1.0 are as follows:
n HA State Trap: wlsxHaState—indicates that HA state has changed.
n Standby IP Sent Failed Trap: wlsxHaStandbyIpSentFailed—indicates that standby IP sent to an AP failed.
n HA Standby Connectivity State Trap: wlsxHaStandbyConnectivityState—indicates the standby connectivity
status for an AP.
n HA Interswitch Hbt Miss Trap: wlsxHaIntercontrollerHbtMiss—indicates that around half of the threshold
interswitch heartbeat was missed with serving switch.
n HA Failover Trigger Trap: wlsxHaFailoverTrigger—indicates that a standby switch has triggered HA failover to
APs belonging to a particular serving switch with which interswitch heartbeat was missed above threshold.
n HA Failover Request from AP Trap: wlsxHaFailoverRequestFromAp—indicates that an AP sent failover
request to the switch. This could be because of an AP missing heartbeat with the serving switch, on receiving
failover request from standby switch, or AP trying to preempt back to active switch.
For more information on the SNMP traps, refer to https://support.esd.alcatel-lucent.com/.
Migrating from VRRP or Backup-LMS Redundancy
AOS-W has a local management switch (LMS) and a backup LMS. In a typical deployment, the AP contacts the
master switch and is directed to the switch that handles the AP connection and traffic via the LMS parameter.
If the LMS becomes unreachable and a backup LMS is specified, the AP attempts to reconnect to that backup
switch. This function provides Layer 3 and site redundancy when this level of redundancy is required.
High Availability: Fast Failover provides redundancy for APs, but not for switches. Deployments that require master
switch redundancy should continue to use an existing VRRP redundancy solution.
If your deployment currently uses a backup-LMS or VRRP redundancy solution, use the following procedures
to migrate to a high availability-based solution. For more information on this topology, see Master-
Redundancy Deployment Model on page 635.
AOS-W 6.5.3.x | User Guide Increasing Network Uptime Through Redundancy and VRRP | 641