Redundancy issue with WS-SUP720-3BXL module

HCL Support · ‎03-21-2012

Hi Team,

We have Router CISCO7613,SSO redundancy configured with two Sup 720-3BXL running 12.2(33)SRC1 image. Even thought I've configured SSO, my standby sup remains in COLD state with the following logs generated.

Mar 20 22:07:32.514 IST: %ISSU-SP-3-PEER_IMAGE_INCOMPATIBLE: Peer image (c7600s72033_sp-ADVENTERPRISEK9-M), version (12.2(33)SRC1) on peer uid (8) is incompatible

Mar 20 22:08:48.263 IST: %PFREDUN-SP-4-INCOMPATIBLE: Defaulting to RPR mode (Runtime incompatible)

Mar 20 22:08:51.319 IST: %FABRIC-SP-5-CLEAR_BLOCK: Clear block option is off for the fabric in slot 8.

Mar 20 22:08:51.415 IST: %FABRIC-SP-5-FABRIC_MODULE_BACKUP: The Switch Fabric Module in slot 8 became standby

Mar 20 22:08:53.095 IST: %DIAG-SP-6-RUN_MINIMUM: Module 8: Running Minimal Diagnostics...

Mar 20 22:08:53.991 IST: %DIAG-SP-6-DIAG_OK: Module 8: Passed Online Diagnostics

Mar 20 22:08:54.427 IST: %OIR-SP-6-INSCARD: Card inserted in slot 8, interfaces are now online

Mar 20 22:09:11.919 IST: %BGP-3-NOTIFICATION: sent to neighbor 172.30.215.178 active 4/0 (hold time expired) 0 bytes

Mar 20 22:09:41.995 IST: %BGP-5-ADJCHANGE: neighbor 172.30.215.178 Up

Mar 20 22:11:19.277 IST: %PFREDUN-SP-6-ACTIVE: Standby initializing for RPR mode

Mar 20 22:11:19.469 IST: %SYS-SP-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output.

Mar 20 22:11:28.037 IST: %RF-SP-5-RF_TERMINAL_STATE: Terminal state reached for (RPR)

These logs says that due to some reasons, the configuration is not being synchronized with active and standby sups and hence the redundancy mode remains in RPR mode and SSO not achieved, and hence COLD state.

However, I couldn't find a reason why the configuration is not being synchronized, I've issued the command, redundancy config-sync ignore mismatched-commands, and everying worked fine, SSO achieved and standby sup came to HOT state.

Now my query is,

1. Why the configuration was not synchronized and standby SUP got in COLD state??

2. Since I issued the suggested command, at least, some of the mismatched lines in configuration will be ignored, Will that create a problem when my Active sup fails and standby become active??

Please clarify this case and confirm if any specific bug impact, also confirm the future impact as per above questions.

Regards,

Ashutosh

nkarpysh · ‎03-21-2012

Hello,

Peer image is showing up as incompatible -

Mar 20 22:07:32.514 IST: %ISSU-SP-3-PEER_IMAGE_INCOMPATIBLE: Peer image (c7600s72033_sp-ADVENTERPRISEK9-M), version (12.2(33)SRC1) on peer uid (8) is incompatible

so that is the reason for sup being cold.

Can you please attach

- show ver

- show mod

- remote command standby-rp show ver

Nik

HTH,
Niko

AKIL HASAN · ‎03-21-2012

Hello,

Thanks for responding on this SUP case.

Again informing that we have issued the command, redundancy config-sync ignore mismatched-commands, and everying worked fine, SSO achieved and standby sup came to HOT state.

This event happened yesterday night asper logs " Mar 20 22:11:28.037 IST: %RF-SP-5-RF_TERMINAL_STATE: Terminal state reached for (RPR) "

Now SUP is showing HOT status but my query is,

1. Why the configuration was not synchronized and standby SUP got in COLD state??

2. Since I issued the suggested command, at least, some of the mismatched lines in configuration will be ignored, Will that create a problem when my Active sup fails and standby become active??

Please clarify this case and confirm if any specific bug impact, also confirm the future impact as per above questions.

Also attaching show version, show module here.

Ashutosh

HCL Support · ‎03-21-2012

Hi Nikolay,

Now adding show version and show module as requested.

Also confirm my query of the two question arises above in original post.

Ashutosh

nkarpysh · ‎03-21-2012

Right,

Coming to your questions

1. So basically I guess now you will not see what commands are failing though you can still try to check it with show redundancy config-sync failures mcl". You can revert back to

"redundancy config-sync validate mismatched-commands " and check the logs message ones it is configued first. Then see

misconfiguration inf applicable with "show redundancy config-sync failures mcl". You can try new switchover during MW to see if problem reoccures and check the show command again to see what is failing.

2. I don't think it will create much problem as the config now pushed to standby and the only thing it can have - are some extra commands which caused this issue with SSO before. Though again that will depend on what extra commands are there - so may be better first to fix the steps 1 above.

Nik

HTH,
Niko