cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1274
Views
5
Helpful
1
Replies

c9800-L-F RMI+RP HA failover scenario

J_Vansen_S
Level 3
Level 3

Hi All, 

We have two physical units of c9800 configured with RMI+RP ip address, & connected back2back on their RP port. 

We were trying to test failover scenario by unplugging the uplink trunk port to our switch. 

1. It failover successfully, ie standby WLC becomes active.

2. However is it correct behavior for the active WLC to REBOOT itself? from the logs we can see that active unit has gone to ActiveRecovery state. 

Chassis 1 reloading, reason - Reload Command - RIF: GW DOWN
Ewlc: triggered dual-active recovery,setting hostname to
% Hostname "DA_WLC9800_01(RE            " is not a legal LAT node name, Using "CISCO_1DBD2C"
Sep 22 05:19:20.321: RMI-HAINFRA-INFO: Originating event to Shut all Interfaces
Sep 22 05:19:20.321: RMI-HAINFRA-INFO: Shutting down all interfaces in ActiveRecovery
Sep 22 05:19:20.322: RMI-HAINFRA-INFO: Not shutting down the interface-rmi: Vlan10
.Sep 22 05:19:20.303: %RIF_MGR_FSM-6-GW_UNREACHABLE_ACTIVE: Chassis 1 R0/0: rif_mgr: Gateway not reachable from Active
.Sep 22 05:19:20.307: %STACKMGR-1-RELOAD: Chassis 1 R0/0: stack_mgr: Reloading due to reason Reload Command - RIF: GW DOWN
.Sep 22 05:19:20.310: %RIF_MGR_FSM-6-RMI_ACTIVE_RECOVERY_MODE: Chassis 1 R0/0: rif_mgr: Going to Active(Recovery) from Active state
.Sep 22 05:19:21.303: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel1, changed state to down
.Sep 22 05:19:22.302: %LINK-3-UPDOWN: Interface TenGigabitEthernet0/1/0, changed state to down
.Sep 22 05:19:22.306: %LINK-3-UPDOWN: Interface Vlan10, changed state to down
.Sep 22 05:19:22.309: %LINK-3-UPDOWN: Interface Port-channel1, changed state to down
.Sep 22 05:19:22.326: %LINK-5-CHANGED: Interface GigabitEthernet0, changed state to administratively down
.Sep 22 05:19:23.302: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet0/1/0, changed state to down
.Sep 22 05:19:23.306: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to down
.Sep 22 05:19:30.587: %RIF_MGR_FSM-6-RMI_LINK_DOWN: Chassis 1 R0/0: rif_mgr: The RMI link is DOWN.Sep 22 13:19:37.055: %PMAN-5-EXITACTION: C0/0: pvp: Process manager is exiting:
Sep 22 13:19:37.505: %PMAN-5-EXITACTION: F0/0: pvp: Process manager is exiting:
Sep 22 13:19:38.722: %PMAN-5-EXITACTION: R0/0: pvp: Process manager is exiting: process exit with reload fru code
Sep 22 13:20:00.530: %PMAN-3-PROCESS_NOTIFICATION: R0/0: pvp: System report core/DA_WLC9800_01_1_RP_0-system-report_20220922-131938-GMT.tar.gz (size: 39348 KB) generated and System report info at core/DA_WLC9800_01_1_RP_0-system-report_20220922-131938-GMT-info.txt
 
1 Reply 1

ammahend
VIP
VIP

Yes its expected behavior, if you look at deployment guide below on page 30, in second table row 4 it explains this exact scenario and how active 9800 will behave. you can use this guide for testing expected behavior in other fail over scenarios as well.

https://www.cisco.com/c/dam/en/us/td/docs/wireless/controller/9800/17-1/deployment-guide/c9800-ha-sso-deployment-guide-rel-17-1.pdf

 

-hope this helps-
Review Cisco Networking for a $25 gift card