[c-nsp] 6500 VSS question

[Murphy, William]

Is your redundancy mode set to RPR?  I think what you are doing only works
if the mode is set to SSO...

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Church, Charles
Sent: Tuesday, May 17, 2011 10:31 AM
To: nsp-cisco
Subject: Re: [c-nsp] 6500 VSS question

Anyone?  Otherwise gonna ask TAC, just want to verify my thoughts.

Thanks,

Chuck

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Church, Charles
Sent: Monday, May 16, 2011 6:07 PM
To: nsp-cisco
Subject: [c-nsp] 6500 VSS question

All,

        Noticed an unexpected result today when testing VSS failover.  Our
setup has dual sups in each chassis, with a supervisor port of each chassis
connecting to the matching supervisor port on the other chassis, i.e. 1/5/4
connects to 2/5/4, and 1/6/4 connects to 2/6/4.  Today when pulling out the
active sup, the hot-standby took over immediately as it should, but we
noticed all the linecards in the chassis with the pulled sup resetting.  I
was under the assumption that a sup transitioning from RPR-warm to standby
hot would remain forwarding at L2, thus keeping the VSL up.  Now I'm
questioning that.  It would explain the result, as the linecards couldn't
get to an active supervisor.  I'm thinking I should have a third VSL link
(of that port channel) on a non-sup linecard.  When we did the eFSU, we
noticed real long outages of the linecards of the chassis getting the final
reload as well.  Possibly the same issue, no connectivity to the active sup?

Thanks,

Chuck

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/