Re: 6504 vss pair shows Active/Active on led's but not in config

donald.james · ‎10-31-2012

After rebooting a pair of 6504's configured for vss, both switches show active on the sup modules. A show switch virtual redundancy however shows the pair working in an active/standby mode. We have 6509's in vss pairs and they show active on switch1 and standby on switch2 led's. For the 6504's switch 1 was booted first and then the second switch about 30 seconds later. Is there something different with the 6504's?

                 My Switch Id = 1
                Peer Switch Id = 2
        Last switchover reason = none
    Configured Redundancy Mode = sso
     Operating Redundancy Mode = sso

Switch 1 Slot 1 Processor Information :
-----------------------------------------------
        Current Software state = ACTIVE
       Uptime in current state = 20 hours, 42 minutes
                 Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(33)SXH7, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Thu 11-Mar-10 22:30 by prod_rel_team
                          BOOT = sup-bootdisk:s72033-ipservicesk9_wan-mz.122-33.SXH7.bin,1;disk0:s72033-ipservicesk9_wan-mz.122-33.SXH7.bin,1;sup-bootdisk:,1;disk0:,1;
        Configuration register = 0x2102
                  Fabric State = ACTIVE
           Control Plane State = ACTIVE

Switch 2 Slot 1 Processor Information :
-----------------------------------------------
        Current Software state = STANDBY HOT (switchover target)
       Uptime in current state = 20 hours, 41 minutes
                 Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(33)SXH7, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Thu 11-Mar-10 22:30 by prod_rel_team
                          BOOT = sup-bootdisk:s72033-ipservicesk9_wan-mz.122-33.SXH7.bin,1;disk0:s72033-ipservicesk9_wan-mz.122-33.SXH7.bin,1;sup-bootdisk:,1;disk0:,1;
        Configuration register = 0x2102
                  Fabric State = ACTIVE
           Control Plane State = STANDBY

Thanks, Donald

Reza Sharifi · ‎10-31-2012

VSS is the same across all the 6500 models.

Can you post the ouput of

"sh switch virt role"?

Are you using fast hello for dual-active detection of ePAGP?

"sh swit virt dual"

HTH

donald.james · ‎11-01-2012

#sh switch virt role

Switch Switch Status Preempt    Priority Role     Session ID
        Number         Oper(Conf) Oper(Conf)         Local Remote
------------------------------------------------------------------
LOCAL    1     UP      FALSE(N )   200(200) ACTIVE   0      0
REMOTE   2     UP      FALSE(N )   100(100) STANDBY 84     8485

In dual-active recovery mode: No

#sh switch virt dual-active summary
Pagp dual-active detection enabled: Yes
Bfd dual-active detection enabled: Yes

No interfaces excluded from shutdown in recovery mode

In dual-active recovery mode: No

#sh switch virt dual-active pagp
PAgP dual-active detection enabled: Yes
PAgP dual-active version: 1.1

No PAgP channel groups configured

Below are the same commands on a pair of 6509's configured as a vss pair running Version 12.2(33)SXI3.

NDCVSCRMDS01#sh swit virt dual-active summary
Pagp dual-active detection enabled: Yes
Bfd dual-active detection enabled: Yes
Fast-hello dual-active detection enabled: Yes

No interfaces excluded from shutdown in recovery mode

In dual-active recovery mode: No

Reza Sharifi · ‎11-01-2012

LOCAL 1 UP FALSE(N ) 200(200) ACTIVE 0 0

REMOTE 2 UP FALSE(N ) 100(100) STANDBY 84 8485

You have assigned priority 200 to one and 100 to the other one. No need to do that. When you configure VSS, switch one is always primary and switch 2 is stand-by. I agreed that you are running a very old code. You need to move to SXI or SXJ. No enhancemnet is being done is SXH.

HTH

Arumugam Muthaiah · ‎10-31-2012

Hi,

I would like to add my comments along with Reza,

When did you started to see this behavior? This issue looks like some enhancement issue issue for the code 12.2(33)SXH. The fix is available in 12.2(33)SXI releases

The ACTIVE LED is showing incorrectly showing as GREEN. In 12.2(33)SXH releases, the color of active LED in standby sup (in VSS) is GREEN. Later changed the standby LED color to ORANGE.

This is not hardware issue.

Regards,

Aru

*** Please rate if the post is useful ***

Regards, Aru *** Please rate if the post useful ***