Stack switch 2 restarted, and generated the following logs

[RicardoFranca8027]

Stack switch 2 restarted, and generated the following logs

.Aug 30 18:39:13 BRST: Config Sync: Line-by-Line sync verifying failure on command:
30 deny ip any any log
due to parser return error

.Aug 30 18:39:14 BRST: %RF-5-RF_RELOAD: Peer reload. Reason: Configuration mismatch
.Aug 30 18:39:14 BRST: %PLATFORM_HA-4-RELOAD_PEER: Reloading the Standby, due to Config-Sync (Configuration mismatch)
.Aug 30 18:39:14 BRST: %STACKMGR-1-RELOAD_REQUEST: 1 stack-mgr: Received reload request for switch 2, reason Configuration mismatch
Aug 30 18:39:14 BRST: %STACKMGR-1-RELOAD: STANDBY:2 stack-mgr: Reloading due to reason Configuration mismatch (SWCOREMFALS-2)
.Aug 30 18:39:15 BRST: %STACKMGR-1-STACK_LINK_CHANGE: 1 stack-mgr: Stack port 1 on switch 1 is down
.Aug 30 18:39:15 BRST: %STACKMGR-6-SWITCH_REMOVED: 1 stack-mgr: Switch 2 has been removed from the stack.
.Aug 30 18:39:15 BRST: Starting SWITCH-DELETE sequence, switch 2
.Aug 30 18:39:15 BRST: SPI(FED QoS) server dead
.Aug 30 18:39:15 BRST: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_NOT_PRESENT)
.Aug 30 18:39:15 BRST: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby removal (raw-event=PEER_NOT_PRESENT(3))

.Aug 30 18:39:15 BRST: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)
.Aug 30 18:39:15 BRST: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected standby down or crashed (raw-event=PEER_DOWN(2))

.Aug 30 18:39:15 BRST: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_REDUNDANCY_STATE_CHANGE)
.Aug 30 18:39:15 BRST: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby removal (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))

.Aug 30 18:39:15 BRST: SWITCH-DELETE sequence complete, switch 2
.Aug 30 18:39:16 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel13, changed state to down
.Aug 30 18:39:16 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel14, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/3, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/5, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/6, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/7, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/8, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/9, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/10, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/11, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/13, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/14, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/15, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/16, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/17, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/18, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/21, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface Port-channel13, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/22, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface Port-channel14, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/23, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/1, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/2, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/3, changed state to down
.Aug 30 18:39:17 BRST: %LINK-3-UPDOWN: Interface GigabitEthernet2/1/4, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/3, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/4, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/5, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/6, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/7, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/8, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/9, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/10, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/11, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/13, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/14, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/15, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/16, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/17, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/18, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/21, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/22, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/0/23, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/1, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/2, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/3, changed state to down
.Aug 30 18:39:18 BRST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/1/4, changed state to down

[Bruno Rangel]

Olá Ricardo

Importante informar o que foi alterado na sua pilha de Stack, assim como a versão do seu IOS e Plataforma uma vez que existem alguns Defeitos/Bugs que podem estar relacionados a esse evento.

Note a Linha:

Aug 30 18:39:14 BRST: %PLATFORM_HA-4-RELOAD_PEER: Reloading the Standby, due to Config-Sync (Configuration mismatch)

Após isso o seus Switches "Perderam o Stack"

[RicardoFranca8027]

Switch Ports Model SW Version SW Image Mode
------ ----- ----- ---------- ---------- ----
* 1 32 WS-C3850-24P 03.06.06E cat3k_caa-universalk9 INSTALL
2 32 WS-C3850-24P 03.06.06E cat3k_caa-universalk9 INSTALL

Yes, apparently it was CPU increase in Stack where Switch 2 ended up restarting.

We validate that from the moment that the activation of logging of a certain ACL in the Switch is configured to monitor the accesses, there was CPU increase that ended up restarting the switch.
ACL logging is currently disabled.

Should this really happen? Considering that the number of logs in the terminal is low when generated