Standby Sup synchronization verification

[umeshpunjabi]

My redundant supervisor crashed sometime back. The following error was observed

%SYS-3-SYS_LCPERR3:Module 2: Bus Asic #0 out of sync error:

Module requires attention - troubleshoot or contact TAC for assistance

This problem was resolved later.

My question is how do i verify that my standby sup will function properly when the active one fails? This is a production network, can't bring it down for testing.

I tried to verify if the bootflash in module 2 had synchronized with the image in the active sup using the command

show flash 2/bootflash:

But this command gives me the message File system in use (8). Try again later.

Is this normal? should i be concerned?

Is there any other way to check if the standby sup will function properly in the event of the primary failing

[lgijssel]

The URL below contains a lot of info on the subject:

http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_guide_chapter09186a0080160a91.html

It also depicts how to check an operational system.

Regards,

Leo

[umeshpunjabi]

Hi Leo,

The link that you've mentioned talks about the route processor redundancy. I need info on the switching SUP

~UDP

[ankurbhasin]

HI Umesh,

Can you check the boot parameters with "sh boot 2" command and also check one "dir 2/bootflash:"

Just try this and update of it works.

Ankur

[umeshpunjabi]

Hi Ankur,

Sw> (enable) sh boot 2

BOOT variable = bootflash:BTSYNC_cat6000-supk8.7-6-14.bin,1;slot0:cat6000-supk8.

7-6-14.bin,1;

CONFIG_FILE variable = slot0:switch.cfg

Configuration register is 0x102

ignore-config: disabled

auto-config: non-recurring, overwrite, sync disabled

ROMMON console baud: 9600

boot: image specified by the boot system commands

Which is the same as the sup 1 image .. thats fine so far ..!!

However,

sw> (enable) dir 2/bootflash:

File system in use (8). Try again later.

Is this normal!? Why does it not show the image file? What happens when the active sup fails in such a scenario?

~UDP

[jarathbu]

Hello,

From the output you're seeing from the dir 2/bootflash: it appears that the bootflash is being locked by another process. I've provided a sample of the same outputs for your review from another switch to compare.

SR3-Cat6509a (enable) dir bootflash:

-#- -length- -----date/time------ name

1 9720136 Jan 25 2006 22:27:08 cat6000-sup2k8.8-4-5.bin

2 8828948 Feb 19 2006 02:30:34 cat6000-sup2k8.8-3-5.bin

3 7671080 Feb 19 2006 02:57:13 RTSYNC_cat6000-sup2k8.7-6-9.bin

5761020 bytes available (26220548 bytes used)

SR3-Cat6509a (enable) dir 2/bootflash:

-#- -length- -----date/time------ name

1 7671080 Feb 03 2006 19:40:21 cat6000-sup2k8.7-6-9.bin

2 8828948 Feb 19 2006 03:16:16 cat6000-sup2k8.8-3-5.bin

15481284 bytes available (16500284 bytes used)

Hope this helps.

Regards,

James

[umeshpunjabi]

Thanks James,

However, my question still remains unanswered..

sw> (enable) dir 2/bootflash:

File system in use (8). Try again later.

IS THIS A CONCERN?

If i issue the following

sw> (enable) sh boot 2

BOOT variable = bootflash:BTSYNC_cat6000-supk8.7-6-14.bin,1;slot0:cat6000-supk8.

7-6-14.bin,1;

CONFIG_FILE variable = slot0:switch.cfg

Configuration register is 0x102

ignore-config: disabled

auto-config: non-recurring, overwrite, sync disabled

ROMMON console baud: 9600

boot: image specified by the boot system commands

I do get the requied info,

Why does the previous command (dir 2/bootflash:) show file system in use?

IS THIS A PROBLEM?

~UDP