Wireless Access

Reply
Highlighted
Contributor I

Hitless Failover

Hi All,

 

AirWave is reporting that hitless failover is not possible on our cluster. Unfortunately it doesn't seem to offer any detail as to why it's not possible. I believe I have everything configured correctly and redundancy is enabled. Controllers are running 8.3.0.2 and AirWave is running 8.2.7.

 

Anyone have any insights as to why AirWave is reporting this?

 

Cluster Membership:
(bmh-kp02-wlc-01) [MDC] *#show lc-cluster group-membership

Cluster Enabled, Profile Name = "BNH-Cluster-01"
Redundancy Mode On
Active Client Rebalance Threshold = 50%
Standby Client Rebalance Threshold = 75%
Unbalance Threshold = 5%
AP Load Balancing: Enabled
Active AP Rebalance Threshold = 50%
Active AP Unbalance Threshold = 5%
Active AP Rebalance AP Count = 30
Active AP Rebalance Timer = 1 minutes
Cluster Info Table
------------------
Type IPv4 Address Priority Connection-Type STATUS
---- --------------- -------- --------------- ------
self 10.134.127.21 128 N/A CONNECTED (Leader)
peer 10.134.127.22 128 L3-Connected CONNECTED (Member, last HBT_RSP 56ms ago, RTD = 0.000 ms)


Accepted Solutions
Highlighted
MVP Expert

Re: Hitless Failover

On one of the mobility controllers you can run the following command :
Show lc-cluster vlan-probe status

This will show if there’s a particular VLAN that might be causing the issue

Make sure you exclude VLAN 1 if is not in use or any other VLANs that are not trunked or are local to the controller



Thank you

Victor Fabian

Pardon typos sent from Mobile

Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA

View solution in original post

Highlighted
Frequent Contributor I

Re: Hitless Failover

So the goal is to get a layer 2 cluster instead of layer 3 by excluding the vlans as Victor posted.

View solution in original post


All Replies
Highlighted
MVP Expert

Re: Hitless Failover

On one of the mobility controllers you can run the following command :
Show lc-cluster vlan-probe status

This will show if there’s a particular VLAN that might be causing the issue

Make sure you exclude VLAN 1 if is not in use or any other VLANs that are not trunked or are local to the controller



Thank you

Victor Fabian

Pardon typos sent from Mobile

Thank you

Victor Fabian
Lead Mobility Architect @WEI
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA

View solution in original post

Highlighted
Frequent Contributor I

Re: Hitless Failover

So the goal is to get a layer 2 cluster instead of layer 3 by excluding the vlans as Victor posted.

View solution in original post

Highlighted
Contributor I

Re: Hitless Failover

Thank you both for the reply!

 

I found and exluded the offending VLAN. The connection type is now L2 and AirWave is reporting hitless failover as possible.

Before:

(bmh-ep01-wlc-02) [MDC] #show lc-cluster vlan-probe status

Cluster VLAN Probe Status
-------------------------
Type IPv4 Address REQ-SENT REQ-FAIL ACK-SENT ACK-FAIL REQ-RCVD ACK-RCVD VLAN_FAIL CONN-TYPE START/STOP
---- --------------- -------- -------- -------- -------- -------- -------- --------- --------- ----------
peer 10.134.127.21 157 0 91 0 91 79 1108 L3 Conn 8/ 19

 

After:

(bmh-ep01-wlc-02) [MDC] #show lc-cluster vlan-probe status

Cluster VLAN Probe Status
-------------------------
Type IPv4 Address REQ-SENT REQ-FAIL ACK-SENT ACK-FAIL REQ-RCVD ACK-RCVD VLAN_FAIL CONN-TYPE START/STOP
---- --------------- -------- -------- -------- -------- -------- -------- --------- --------- ----------
peer 10.134.127.21 193 0 129 0 129 115 0 L2 Conn 18/ 18

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: