[c-nsp] 6500 VSS question

[Church, Charles]

First one up is active, the first one up in the opposite chassis becomes the
standby.  The other sups fall into RPR mode.  Unfortunately the docs for
eFSU and ISSU don't cover the 4 sup method well, the placement of the VSLs
seems to be a bit of a mystery.  Doesn't sound like you can have too many.
Will know soon, tried to bring up another one today, but an odd bug
involving an etherchannel looping frames after change to 'performance mode'
killed us.  Will try again soon.

Chuck

-----Original Message-----
From: Matlock, Kenneth L [mailto:MatlockK at exempla.org] 
Sent: Tuesday, May 17, 2011 4:44 PM
To: Murphy, William; Church, Charles; nsp-cisco
Subject: RE: [c-nsp] 6500 VSS question

I haven't looked TOO in-depth on this yet, but with VSS and 4
supervisors, do all 4 come up in SSO mode, or do the first 2 come up in
SSO, and the other two come up in RPR+ mode? 

4 Supervisor VSS is still VERY new, and I wouldn't be surprised if it's
a hybrid of the 2 modes at this point still.

Ken Matlock
Network Analyst
Exempla Healthcare
(303) 467-4671
matlockk at exempla.org


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Murphy, William
Sent: Tuesday, May 17, 2011 1:09 PM
To: Church, Charles; nsp-cisco
Subject: Re: [c-nsp] 6500 VSS question

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/
*** Exempla Confidentiality Notice *** The information contained in this
message may be privileged and confidential and protected from disclosure. If
the reader of this message is not the intended recipient, or an employee or
agent responsible for delivering this message to the intended recipient, you
are hereby notified that any other dissemination, distribution or copying of
this communication is strictly prohibited. If you have received this
communication in error, please notify me immediately by replying to the
message and deleting it from your computer. Thank you. *** Exempla
Confidentiality Notice ***

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6514 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20110518/1259b01b/attachment-0001.bin>