[c-nsp] VSS
Harry Hambi
harry.hambi at bbc.co.uk
Fri Jul 5 08:51:22 EDT 2013
Hi,
Thanx for your comments.....had a mainenance window early this morning tried to re-create problem with Tac on the line, rebooted the vss pair in question 4 times and could not recreate the prob.
Code version has been disgussed....pobably not the cause.
Rgds
Harry
Harry Hambi BEng(Hons) MIET Rsgb
-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of chris stand
Sent: 05 July 2013 11:38
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] VSS
I think you are telling us that you have 4 6500s ?
you might want to check the version of IOS on them as you are on real early VSS code
HSRP between 2 pairs ... seems ok, but a rather odd topology .. however I guess I understand it ... you absolutely, 100% + need packets to route, you are treating each VSS pair as a single router.
Yes, the links between individual VSS members can be odd, L2 &/or L3 any chance you can provide a simple topo ? even if drawn on whiteboard
1. Re: VSS (Mackinnon, Ian)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 3 Jul 2013 15:35:50 +0000
> From: "Mackinnon, Ian" <ian.mackinnon at atos.net>
> To: "cisco-nsp at puck.nether.net" <cisco-nsp at puck.nether.net>
> Subject: Re: [c-nsp] VSS
> Message-ID:
> <
> 8EA235F42C39DF45B871CA1489A9045D030945 at DEFTHW99EX1MSX.ww931.my-it-solu
> tions.net
> >
>
> Content-Type: text/plain; charset="us-ascii"
>
> Not really relevant to the problem, but why are you running HSRP
> between 2 separate VSS instances?
> Surely most of the point of VSS is it removed spanning trees and the
> need for HSRP, and you are now spreading vlans overs 2 switches again,
> giving you the potential for spanning tree again Why are you using
> VSS? What benefit is it giving you in this setup?
>
> Ian
>
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf
> Of Painting, Stuart
> Sent: Wednesday, July 03, 2013 4:17 PM
> To: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] VSS
>
>
> Me, I'd be checking ingress and/or egress ACLs on the surviving links.
> With vss1 switched off, traffic may be taking an "unusual" path to vss2.
>
>
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf
> Of Harry Hambi
> Sent: 03 July 2013 15:35
> To: 'cisco-nsp at puck.nether.net'
> Subject: [c-nsp] VSS
>
> Hi All,
> We have two vss pairs , lets call them vss 1, vss 2. Vss 1 was turned
> off in order to test HSRP capabilities, this made vss 2 the active
> router for several vlans. We found the follwing issues:
> Loopback address & HSRP address on vss 2 were not contactable. Vss 2
> was forwarding traffic. Could this be a management plane issue, hardware?.
> Vss pairs running 12.2.(33) sx14
>
> Rgds
> Harry
>
> Harry Hambi BEng(Hons) MIET Rsgb
>
>
>
> ------------------------------------
> http://www.bbc.co.uk
> This e-mail (and any attachments) is confidential and may contain
> personal views which are not the views of the BBC unless specifically stated.
> If you have received it in
> error, please delete it from your system.
> Do not use, copy or disclose the
> information in any way nor act in reliance on it and notify the sender
> immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
> ------------------------------------
>
> _______________________________________________
> 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/
>
> "To our Members we're the 4th Emergency Service"
> This electronic message contains information from The Automobile
> Association which may be privileged or confidential. The information
> is intended to be for the use of the individual(s) or entity named
> above. If you are not the intended recipient, please delete this e-mail immediately.
> The contents of this e-mail must not be disclosed or copied without
> the sender's consent. We cannot accept any responsibility for viruses,
> so please scan all attachments.
> No changes to Terms and Conditions of trade can be accepted through
> e-mail communication. All changes to Terms and Conditions must be in
> writing evidenced by a director of the company and in hard copy
> format. The statements and opinions expressed in this message are
> those of the author and do not necessarily reflect those of the
> company. The company does not take any responsibility for the views of the author.
>
> _______________________________________________
> 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/
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> cisco-nsp mailing list
> cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
>
> ------------------------------
>
> End of cisco-nsp Digest, Vol 128, Issue 10
> ******************************************
>
_______________________________________________
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/
-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------
More information about the cisco-nsp
mailing list