Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Step-by-Step Configuration and Troubleshooting Best Practices for the NGFW, NGIPS and AMP Technologies A Visual Guide to the Cisco Firepower Threat Defense (FTD)

FWSM module troubles...

Hi...

I have some issue regarding a FWSM module inserted on Catalyst 6509. This module is the stand-by of the primary module resident on other Catalyst 6509 that is fully working. No operations has been made in the failover mode.

Firts of all, I can't connect via "session" command.

If i do a complete hw module test this is the resultant log:

May  6 14:58:08.307: %DIAG-SP-6-TEST_RUNNING: Module 4: Running TestSynchedFabChannel{ID=4} ...

May  6 14:58:08.311: %DIAG-SP-3-TEST_NOT_SUPPORT: Module 4: TestSynchedFabChannel{ID=4} is not supported

May  6 14:58:08.311: %DIAG-SP-6-TEST_RUNNING: Module 4: Running TestFirmwareDiagStatus{ID=6} ...

May  6 14:58:08.323: %DIAG-SP-6-TEST_OK: Module 4: TestFirmwareDiagStatus{ID=6} has completed successfully

May  6 14:58:08.323: %DIAG-SP-6-TEST_RUNNING: Module 4: Running TestAsicSync{ID=7} ...

May  6 14:58:08.323: %DIAG-SP-6-TEST_OK: Module 4: TestAsicSync{ID=7} has completed successfully

May  6 14:58:08.323: %DIAG-SP-6-TEST_RUNNING: Module 4: Running TestErrorCounterMonitor{ID=8} ...

May  6 14:58:08.323: %DIAG-SP-3-TEST_SKIPPED: Module 4: TestErrorCounterMonitor{ID=8} is skipped

May  6 14:59:27.916: %DIAG-SP-6-TEST_RUNNING: Module 4: Running TestPortASICLoopback{ID=1} ...

May  6 14:59:27.916: SP: komodo_plus_test_loopback [4]: On-Demand test is not allowed

May  6 14:59:27.916: %DIAG-SP-3-TEST_SKIPPED: Module 4: TestPortASICLoopback{ID=1} is skipped

May  6 14:59:27.916: %DIAG-SP-6-TEST_RUNNING: Module 4: Running TestPCLoopback{ID=2} ...

May  6 14:59:27.916: SP: komodo_plus_test_loopback [4]: On-Demand test is not allowed

May  6 14:59:27.916: %DIAG-SP-3-TEST_SKIPPED: Module 4: TestPCLoopback{ID=2} is skipped

May  6 14:59:27.916: %DIAG-SP-6-TEST_RUNNING: Module 4: Running TestNetflowInlineRewrite{ID=3} ...

May  6 14:59:27.916: %DIAG-SP-3-TEST_SKIPPED: Module 4: TestNetflowInlineRewrite{ID=3} is skipped

May  6 14:59:27.916: %DIAG-SP-6-TEST_RUNNING: Module 4: Running TestFirmwareDiagStatus{ID=6} ...

May  6 14:59:27.928: %DIAG-SP-6-TEST_OK: Module 4: TestFirmwareDiagStatus{ID=6} has completed successfully

 

If i issue a reset of the module with full mem test I obtain this log:

 

May  6 15:02:55.465: SP: The PC in slot 4 is shutting down. Please wait ...

May  6 15:02:55.469: %C6KPWR-SP-4-DISABLED: power to module in slot 4 set off (Module  Failed SCP dnld)

May  6 15:03:00.468: SP: shutdown_pc_process:No response from module 4

May  6 15:03:10.469: %SM-SP-4-BADEVENT: Event 'pc_powered_off' is invalid for the current state 'stay_disabled': cygnus_oir_bay slot4

-Traceback= 40DB1EF4 41041CEC 40758968 40758954

May  6 15:03:10.469: SP: Last transition recorded: (disabled)-> stay_disabled (operator_power_on)-> can_power_on (yes_power)-> powered_on (real_power_on)-> check_power_on (timer)-> check_power_on (power_on_ok)-> wait_til_online (powered_off)-> shutdown_pc (disabled)-> disabled (disabled)-> disabled2 (disabled)-> stay_disabled

 

The commands related to power for the module is fully working. I can power off, power on and shutdown the module properly.

I also change slot for investigate back plane issue related but nothing changed.

 

Now, what else can I do? Can I extract the CF card and see if I can read through pc?

May I swap the CF from the working module to this module?

 

 

4 REPLIES
New Member

Try to remove the module and

Try to remove the module and add it again on the same slot or in different slot, if that does not help, then you need to RMA the module if you have valid support from Cisco.

As mentioned before I've

As mentioned before I've tried to reseat the module in the same slot and also in another slot.. but nothing changed.

 

But, If I reseat the module without the CF I have this log:

 

%C6KPWR-SP-4-DISABLED: power to module in slot 4 set off (Module  Failed SCP dnld)

 

 

Silver

Hi,The switch has its normal

Hi,

The switch has its normal vibrations and over time those vibrations can cause a module to slightly come away from the backplane. When this happens, the supervisors keepalive polling does not receive a response from the module within the allotted time and the supervisor reboots the module in order to try to gain a better connection to it. If the module still does not respond to the polls, the supervisor continuously reboots the module, and eventually puts it into error disable and does not allow any power to reach this module.

A simple reseat of the module corrects this issue 90 percent of the time. If you reseat the module, it realigns the switch fabric and ensures a firm connection to the backplane.

Also refer this post

HTH

"Please rate helpful posts"

Silver

Then better you go for

Then better you go for replacement

524
Views
0
Helpful
4
Replies
CreatePlease to create content