Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Primary FWSM strangely auto-reload again and again,Secnodary no problem?

Weh ave two Cat6513 switches runingg as primary/secondary. and there are one FWSM one each switch runing failover between them. The FWSM version is 2.3(1).

It work fine till yesterday. The Primary FWSM get auto-reload again and again. The syslog message is like this:

2005-12-12 14:15:08 Local0.Error 11.32.221.11 FirewallName %FWSM-3-319001: Acknowledge for arp update for IP address 11.32.221.12 to NP0 not received.

2005-12-12 14:15:08 Local0.Error 11.32.221.11 FirewallName %FWSM-3-319001: Acknowledge for arp update for IP address 192.168.253.2 to NP0 not received.

2005-12-12 14:15:09 Local0.Error 11.32.221.11 FirewallName %FWSM-3-319001: Acknowledge for arp update for IP address 11.35.232.12 to NP0 not received.

2005-12-12 14:15:16 Local0.Error 11.32.221.11 FirewallName %FWSM-3-319001: Acknowledge for arp update for IP address 11.32.221.12 to NP0 not received.

2005-12-12 14:15:31 Local0.Error 11.32.221.11 FirewallName %FWSM-3-319001: Acknowledge for arp update for IP address 11.32.221.12 to NP0 not received.

2005-12-12 14:15:46 Local0.Error 11.32.221.11 FirewallName %FWSM-3-319001: Acknowledge for arp update for IP address 11.32.221.12 to NP0 not received.

2005-12-12 14:15:58 Local0.Notice 11.32.221.11 FirewallName %FWSM-5-199001: FWSM reload command executed from FWSM console

2005-12-12 14:16:14 Local0.Alert 11.32.221.11 FirewallName %FWSM-1-103001: (Secondary) No response from other firewall (reason code = 1).

2005-12-12 14:16:14 Local0.Alert 11.32.221.11 FirewallName %FWSM-1-104001: (Secondary) Switching to ACTIVE - HELLO not heard from mate.

2005-12-12 14:18:04 Local0.Alert 11.32.221.11 FirewallName %FWSM-1-709003: (Secondary) Beginning configuration replication: Send to mate.

2005-12-12 14:18:08 Local0.Alert 11.32.221.11 FirewallName %FWSM-1-709004: (Secondary) End Configuration Replication (ACT)

2005-12-12 14:18:33 Local0.Alert 11.32.221.11 FirewallName %FWSM-1-105003: (Secondary) Monitoring on interface inside waiting

2005-12-12 14:18:38 Local0.Alert 11.32.221.12 FirewallName %FWSM-1-105006: (Primary) Link status 'Up' on interface inside

2005-12-12 14:18:38 Local0.Alert 11.32.221.12 FirewallName %FWSM-1-105003: (Primary) Monitoring on interface inside waiting

2005-12-12 14:19:33 Local0.Alert 11.32.221.11 FirewallName %FWSM-1-105004: (Secondary) Monitoring on interface inside normal

2005-12-12 14:19:38 Local0.Alert 11.32.221.12 FirewallName %FWSM-1-105004: (Primary) Monitoring on interface inside normal

It looks like the failover Arp packet was not received then it become reload, Why this happend? Really strange.

3 REPLIES
New Member

Re: Primary FWSM strangely auto-reload again and again,Secnodary

Can anybody Have a look on this message?

New Member

Re: Primary FWSM strangely auto-reload again and again,Secnodary

Today, the firewall module restart twice with following message:

Dec 13 13:10:12.376: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet11/1, changed state to down

Dec 13 13:10:12.376: reg_invoke_swif_goingdown: GigabitEthernet11/1 -> up, sw down

Dec 13 13:10:12.376: reg_invoke_if_statechange_complete: sw , hw GigabitEthernet11/1 -> up, hw down

Dec 13 13:10:12.392: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet11/2, changed state to down

Dec 13 13:10:12.396: reg_invoke_swif_goingdown: GigabitEthernet11/2 -> up, sw down

Dec 13 13:10:12.396: reg_invoke_if_statechange_complete: sw , hw GigabitEthernet11/2 -> up, hw down

Dec 13 13:10:12.396: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet11/3, changed state to down

Dec 13 13:10:12.396: reg_invoke_swif_goingdown: GigabitEthernet11/3 -> up, sw down

Dec 13 13:10:12.396: reg_invoke_if_statechange_complete: sw , hw GigabitEthernet11/3 -> up, hw down

Dec 13 13:10:12.416: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet11/4, changed state to down

Dec 13 13:10:12.416: reg_invoke_swif_goingdown: GigabitEthernet11/4 -> up, sw down

Dec 13 13:10:12.416: reg_invoke_if_statechange_complete: sw , hw GigabitEthernet11/4 -> up, hw down

Dec 13 13:10:12.424: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet11/5, changed state to down

Dec 13 13:10:12.424: reg_invoke_swif_goingdown: GigabitEthernet11/5 -> up, sw down

Dec 13 13:10:12.424: reg_invoke_if_statechange_complete: sw , hw GigabitEthernet11/5 -> up, hw down

Dec 13 13:10:12.428: reg_invoke_net_cstate: Port-channel280 -> down, hw down

Dec 13 13:10:12.436: reg_invoke_net_cstate: GigabitEthernet11/1 -> down, hw down

Dec 13 13:10:12.436: reg_invoke_net_cstate: GigabitEthernet11/2 -> down, hw down

Dec 13 13:10:12.436: reg_invoke_net_cstate: GigabitEthernet11/3 -> down, hw down

Dec 13 13:10:12.436: reg_invoke_net_cstate: GigabitEthernet11/4 -> down, hw down

Dec 13 13:10:12.436: reg_invoke_net_cstate: GigabitEthernet11/5 -> down, hw down

Dec 13 13:10:12.440: reg_invoke_net_cstate: GigabitEthernet11/6 -> down, hw down

Dec 13 13:10:12.440: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet11/6, changed state to down

Dec 13 13:10:12.456: reg_invoke_hwif_goingdown: GigabitEthernet11/1 -> down, hw down

Dec 13 13:10:12.456: reg_invoke_swif_goingdown: GigabitEthernet11/1 -> down, sw down

Dec 13 13:10:12.456: reg_invoke_net_cstate: GigabitEthernet11/1 -> admindown, hw down

Dec 13 13:10:12.460: %SNMP-5-MODULETRAP: Module 11 [Down] Trap

Dec 13 13:10:12.460: reg_invoke_if_statechange_complete: sw , hw GigabitEthernet11/1 -> admindown, hw down

Dec 13 13:10:12.460: reg_invoke_hwif_goingdown: GigabitEthernet11/2 -> down, hw down

Dec 13 13:10:12.460: reg_invoke_swif_goingdown: GigabitEthernet11/2 -> down, sw down

Dec 13 13:10:12.460: reg_invoke_net_cstate: GigabitEthernet11/2 -> admindown, hw down

Dec 13 13:10:12.468: reg_invoke_if_statechange_complete: sw , hw GigabitEthernet11/2 -> admindown, hw down

Dec 13 13:10:12.468: reg_invoke_hwif_goingdown: GigabitEthernet11/3 -> down, hw down

Dec 13 13:10:12.468: reg_invoke_swif_goingdown: GigabitEthernet11/3 -> down, sw down

Dec 13 13:10:12.468: reg_invoke_net_cstate: GigabitEthernet11/3 -> admindown, hw down

Dec 13 13:10:12.472: reg_invoke_if_statechange_complete: sw , hw GigabitEthernet11/3 -> admindown, hw down

Dec 13 13:10:12.476: reg_invoke_hwif_goingdown: GigabitEthernet11/4 -> down, hw down

Dec 13 13:10:12.476: reg_invoke_swif_goingdown: GigabitEthernet11/4 -> down, sw down

Dec 13 13:10:12.476: reg_invoke_net_cstate: GigabitEthernet11/4 -> admindown, hw down

Dec 13 13:10:12.480: reg_invoke_if_statechange_complete: sw , hw GigabitEthernet11/4 -> admindown, hw down

to be conntinue....

It looks like the interal Etherchannel of Firewall Module is down. is it a hardware problem?

New Member

Re: Primary FWSM strangely auto-reload again and again,Secnodary

last lines of message:

Dec 13 13:10:12.460: reg_invoke_net_cstate: GigabitEthernet11/2 -> admindown, hw down

Dec 13 13:10:12.468: reg_invoke_if_statechange_complete: sw , hw GigabitEthernet11/2 -> admindown, hw down

Dec 13 13:10:12.468: reg_invoke_hwif_goingdown: GigabitEthernet11/3 -> down, hw down

Dec 13 13:10:12.468: reg_invoke_swif_goingdown: GigabitEthernet11/3 -> down, sw down

Dec 13 13:10:12.468: reg_invoke_net_cstate: GigabitEthernet11/3 -> admindown, hw down

Dec 13 13:10:12.472: reg_invoke_if_statechange_complete: sw , hw GigabitEthernet11/3 -> admindown, hw down

Dec 13 13:10:12.476: reg_invoke_hwif_goingdown: GigabitEthernet11/4 -> down, hw down

Dec 13 13:10:12.476: reg_invoke_swif_goingdown: GigabitEthernet11/4 -> down, sw down

Dec 13 13:10:12.476: reg_invoke_net_cstate: GigabitEthernet11/4 -> admindown, hw down

Dec 13 13:10:12.480: reg_invoke_if_statechange_complete: sw , hw GigabitEthernet11/4 -> admindown, hw down

Dec 13 13:10:12.480: reg_invoke_hwif_goingdown: GigabitEthernet11/5 -> down, hw down

Dec 13 13:10:12.480: reg_invoke_swif_goingdown: GigabitEthernet11/5 -> down, sw down

Dec 13 13:10:12.480: reg_invoke_net_cstate: GigabitEthernet11/5 -> admindown, hw down

Dec 13 13:10:12.480: reg_invoke_hwif_state_change: Port-channel280 -> down, hw down

Dec 13 13:10:12.484: reg_invoke_swif_goingdown: Port-channel280 -> down, sw down

Dec 13 13:10:12.484: reg_invoke_if_statechange_complete: sw , hw Port-channel280 -> down, hw down

Dec 13 13:10:12.484: reg_invoke_if_statechange_complete: sw , hw GigabitEthernet11/5 -> admindown, hw down

Dec 13 13:10:12.484: reg_invoke_hwif_goingdown: GigabitEthernet11/6 -> down, hw down

Dec 13 13:10:12.484: reg_invoke_swif_goingdown: GigabitEthernet11/6 -> down, sw down

Dec 13 13:10:12.484: reg_invoke_net_cstate: GigabitEthernet11/6 -> admindown, hw down

Dec 13 13:10:12.488: %LINK-5-CHANGED: Interface GigabitEthernet11/1, changed state to administratively down

Dec 13 13:10:12.488: reg_invoke_hwif_state_change: GigabitEthernet11/1 -> admindown, hw down

Dec 13 13:10:12.488: reg_invoke_swif_goingdown: GigabitEthernet11/6 -> admindown, sw down

Dec 13 13:10:12.488: reg_invoke_if_statechange_complete: sw , hw GigabitEthernet11/6 -> admindown, hw down

Dec 13 13:10:12.492: reg_invoke_hwif_goingdown: Port-channel280 -> down, hw down

Dec 13 13:10:12.492: reg_invoke_swif_goingdown: Port-channel280 -> down, sw down

Dec 13 13:10:12.492: reg_invoke_net_cstate: Port-channel280 -> admindown, hw down

Dec 13 13:10:12.496: %LINK-5-CHANGED: Interface GigabitEthernet11/2, changed state to administratively down

Dec 13 13:10:12.496: reg_invoke_hwif_state_change: GigabitEthernet11/2 -> admindown, hw down

Dec 13 13:10:12.496: reg_invoke_if_statechange_complete: sw , hw Port-channel280 -> admindown, hw down

Dec 13 13:10:12.508: reg_invoke_hwif_state_change: GigabitEthernet11/3 -> admindown, hw down

Dec 13 13:10:12.516: reg_invoke_hwif_state_change: GigabitEthernet11/4 -> admindown, hw down

Dec 13 13:10:12.520: reg_invoke_hwif_state_change: GigabitEthernet11/5 -> admindown, hw down

Dec 13 13:10:12.524: reg_invoke_hwif_state_change: GigabitEthernet11/6 -> admindown, hw down

Dec 13 13:10:12.548: reg_invoke_hwif_state_change: Port-channel280 -> admindown, hw down

Dec 13 13:10:12.458: SP: The PC in slot 11 is shutting down. Please wait ...

481
Views
0
Helpful
3
Replies
CreatePlease to create content