Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cisco: NSP

remove spanning-tree without being service effecting

 

 

Cisco nsp RSS feed   Index | Next | Previous | View Threaded


jurwiller at americanbb

Aug 2, 2012, 7:35 AM

Post #1 of 15 (1270 views)
Permalink
remove spanning-tree without being service effecting

I have a MSTP ring that I want to remove spanning-tree all together, and
manually shut down my "dead" link. How can I remove or disable
spanning-tree without driving to each site? If I use the commands
"spanning-tree bpdufilter" or "spanning-tree bpduguard" they both
err-disable the port; which would cause my connectivity to the switch to
go down. I also use the command "spanning-tree portfast trunk" if I do
that command first before the bpduguard/filters will it not err-disable
the port??



Is there a better way to go about this??



James Urwiller

Lead Internet Services Technician / Network Engineer

CCNA 11567125

American Broadband

402-426-6257 - Office

402-278-1875 - Cell

402-426-6273 - Fax

jurwiller [at] americanbb <mailto:mjurwiller [at] americanbb>



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


chuckchurch at gmail

Aug 2, 2012, 7:48 AM

Post #2 of 15 (1226 views)
Permalink
Re: remove spanning-tree without being service effecting [In reply to]

Figure out all the commands you need to enter for everything, put it in a
text file, and tftp that into the running config. Obviously test it well
before hand, and schedule a reload on the device just as a backup.

Chuck

-----Original Message-----
From: cisco-nsp-bounces [at] puck
[mailto:cisco-nsp-bounces [at] puck] On Behalf Of James Urwiller
Sent: Thursday, August 02, 2012 10:35 AM
To: cisco-nsp [at] puck
Subject: [c-nsp] remove spanning-tree without being service effecting

I have a MSTP ring that I want to remove spanning-tree all together, and
manually shut down my "dead" link. How can I remove or disable
spanning-tree without driving to each site? If I use the commands
"spanning-tree bpdufilter" or "spanning-tree bpduguard" they both
err-disable the port; which would cause my connectivity to the switch to go
down. I also use the command "spanning-tree portfast trunk" if I do that
command first before the bpduguard/filters will it not err-disable the
port??



Is there a better way to go about this??



James Urwiller

Lead Internet Services Technician / Network Engineer

CCNA 11567125

American Broadband

402-426-6257 - Office

402-278-1875 - Cell

402-426-6273 - Fax

jurwiller [at] americanbb <mailto:mjurwiller [at] americanbb>



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

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


jnovak123 at gmail

Aug 2, 2012, 8:05 AM

Post #3 of 15 (1236 views)
Permalink
Re: remove spanning-tree without being service effecting [In reply to]

Hi,

You should consider bpdu filter under interface.that one disables sending and filters received bpdu.

Why are actually disabling mst before shut down of the link? Mst Spanning tree only reacts on link up events. So bringing down a link should not be service affecting.

Bostjan
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

James Urwiller <jurwiller [at] americanbb> wrote:

I have a MSTP ring that I want to remove spanning-tree all together, and
manually shut down my "dead" link. How can I remove or disable
spanning-tree without driving to each site? If I use the commands
"spanning-tree bpdufilter" or "spanning-tree bpduguard" they both
err-disable the port; which would cause my connectivity to the switch to
go down. I also use the command "spanning-tree portfast trunk" if I do
that command first before the bpduguard/filters will it not err-disable
the port??



Is there a better way to go about this??



James Urwiller

Lead Internet Services Technician / Network Engineer

CCNA 11567125

American Broadband

402-426-6257 - Office

402-278-1875 - Cell

402-426-6273 - Fax

jurwiller [at] americanbb <mailto:mjurwiller [at] americanbb>



_____________________________________________

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

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


jurwiller at americanbb

Aug 2, 2012, 8:18 AM

Post #4 of 15 (1221 views)
Permalink
Re: remove spanning-tree without being service effecting [In reply to]

That kind of defeats the whole "not service effecting" issue.. thanks
anyway.

James Urwiller
Lead Internet Services Technician / Network Engineer
CCNA 11567125
American Broadband
402-426-6257 - Office
402-278-1875 - Cell
402-426-6273 - Fax
jurwiller [at] americanbb


-----Original Message-----
From: Chuck Church [mailto:chuckchurch [at] gmail]
Sent: Thursday, August 02, 2012 9:49 AM
To: James Urwiller; cisco-nsp [at] puck
Subject: RE: [c-nsp] remove spanning-tree without being service
effecting

Figure out all the commands you need to enter for everything, put it in
a text file, and tftp that into the running config. Obviously test it
well before hand, and schedule a reload on the device just as a backup.

Chuck

-----Original Message-----
From: cisco-nsp-bounces [at] puck
[mailto:cisco-nsp-bounces [at] puck] On Behalf Of James Urwiller
Sent: Thursday, August 02, 2012 10:35 AM
To: cisco-nsp [at] puck
Subject: [c-nsp] remove spanning-tree without being service effecting

I have a MSTP ring that I want to remove spanning-tree all together, and
manually shut down my "dead" link. How can I remove or disable
spanning-tree without driving to each site? If I use the commands
"spanning-tree bpdufilter" or "spanning-tree bpduguard" they both
err-disable the port; which would cause my connectivity to the switch to
go down. I also use the command "spanning-tree portfast trunk" if I do
that command first before the bpduguard/filters will it not err-disable
the port??



Is there a better way to go about this??



James Urwiller

Lead Internet Services Technician / Network Engineer

CCNA 11567125

American Broadband

402-426-6257 - Office

402-278-1875 - Cell

402-426-6273 - Fax

jurwiller [at] americanbb <mailto:mjurwiller [at] americanbb>



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


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


chuckchurch at gmail

Aug 2, 2012, 8:25 AM

Post #5 of 15 (1224 views)
Permalink
Re: remove spanning-tree without being service effecting [In reply to]

Well, the scheduled reload is just your safety net. The copying of tftp
into running config will let you enter an entire command set that had you
tried to enter interactively would have bumped out off before they were all
in there, leaving the device down. So you schedule the reload for 2 minutes
out, then copy the config via TFTP. Assuming it goes well, you never lose
your CLI session to the device, or worst case you do, but can get right back
in. Then you cancel the reload before that 2 minutes elapses.

Chuck


-----Original Message-----
From: James Urwiller [mailto:jurwiller [at] americanbb]
Sent: Thursday, August 02, 2012 11:19 AM
To: Chuck Church; cisco-nsp [at] puck
Subject: RE: [c-nsp] remove spanning-tree without being service effecting

That kind of defeats the whole "not service effecting" issue.. thanks
anyway.

James Urwiller
Lead Internet Services Technician / Network Engineer CCNA 11567125 American
Broadband
402-426-6257 - Office
402-278-1875 - Cell
402-426-6273 - Fax
jurwiller [at] americanbb


-----Original Message-----
From: Chuck Church [mailto:chuckchurch [at] gmail]
Sent: Thursday, August 02, 2012 9:49 AM
To: James Urwiller; cisco-nsp [at] puck
Subject: RE: [c-nsp] remove spanning-tree without being service effecting

Figure out all the commands you need to enter for everything, put it in a
text file, and tftp that into the running config. Obviously test it well
before hand, and schedule a reload on the device just as a backup.

Chuck

-----Original Message-----
From: cisco-nsp-bounces [at] puck
[mailto:cisco-nsp-bounces [at] puck] On Behalf Of James Urwiller
Sent: Thursday, August 02, 2012 10:35 AM
To: cisco-nsp [at] puck
Subject: [c-nsp] remove spanning-tree without being service effecting

I have a MSTP ring that I want to remove spanning-tree all together, and
manually shut down my "dead" link. How can I remove or disable
spanning-tree without driving to each site? If I use the commands
"spanning-tree bpdufilter" or "spanning-tree bpduguard" they both
err-disable the port; which would cause my connectivity to the switch to go
down. I also use the command "spanning-tree portfast trunk" if I do that
command first before the bpduguard/filters will it not err-disable the
port??



Is there a better way to go about this??



James Urwiller

Lead Internet Services Technician / Network Engineer

CCNA 11567125

American Broadband

402-426-6257 - Office

402-278-1875 - Cell

402-426-6273 - Fax

jurwiller [at] americanbb <mailto:mjurwiller [at] americanbb>



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

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


petelists at templin

Aug 2, 2012, 8:37 AM

Post #6 of 15 (1223 views)
Permalink
Re: remove spanning-tree without being service effecting [In reply to]

On 8/2/12 7:35 AM, James Urwiller wrote:
> I have a MSTP ring that I want to remove spanning-tree all together,
> and manually shut down my "dead" link. How can I remove or disable
> spanning-tree without driving to each site? If I use the commands
> "spanning-tree bpdufilter" or "spanning-tree bpduguard" they both
> err-disable the port; which would cause my connectivity to the switch
> to go down. I also use the command "spanning-tree portfast trunk"
> if I do that command first before the bpduguard/filters will it not
> err-disable the port??

Why remove STP?

Why would bpdufilter errdisable the port?

> Is there a better way to go about this??

Leave STP running.

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


petelists at templin

Aug 2, 2012, 8:40 AM

Post #7 of 15 (1219 views)
Permalink
Re: remove spanning-tree without being service effecting [In reply to]

On 8/2/12 8:18 AM, James Urwiller wrote:
> That kind of defeats the whole "not service effecting" issue.. thanks
> anyway.

He clearly said 'just as a backup'. You clearly said "without driving
to each site". What do you want? Get over it, there's risk involved in
what you want to do (that risk entered as soon as you chose to remove
STP, maybe as soon as you thought of it), you might want to implement a
safety net.

> -----Original Message-----
> From: Chuck Church [mailto:chuckchurch [at] gmail]
> Sent: Thursday, August 02, 2012 9:49 AM
> To: James Urwiller; cisco-nsp [at] puck
> Subject: RE: [c-nsp] remove spanning-tree without being service
> effecting
>
> Figure out all the commands you need to enter for everything, put it in
> a text file, and tftp that into the running config. Obviously test it
> well before hand, and schedule a reload on the device just as a backup.

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


jurwiller at americanbb

Aug 2, 2012, 9:08 AM

Post #8 of 15 (1224 views)
Permalink
Re: remove spanning-tree without being service effecting [In reply to]

I understand what you are saying now.. thanks

James Urwiller
Lead Internet Services Technician / Network Engineer
CCNA 11567125
American Broadband
402-426-6257 - Office
402-278-1875 - Cell
402-426-6273 - Fax
jurwiller [at] americanbb


-----Original Message-----
From: Chuck Church [mailto:chuckchurch [at] gmail]
Sent: Thursday, August 02, 2012 10:25 AM
To: James Urwiller; cisco-nsp [at] puck
Subject: RE: [c-nsp] remove spanning-tree without being service
effecting

Well, the scheduled reload is just your safety net. The copying of tftp
into running config will let you enter an entire command set that had
you tried to enter interactively would have bumped out off before they
were all in there, leaving the device down. So you schedule the reload
for 2 minutes out, then copy the config via TFTP. Assuming it goes
well, you never lose your CLI session to the device, or worst case you
do, but can get right back in. Then you cancel the reload before that 2
minutes elapses.

Chuck


-----Original Message-----
From: James Urwiller [mailto:jurwiller [at] americanbb]
Sent: Thursday, August 02, 2012 11:19 AM
To: Chuck Church; cisco-nsp [at] puck
Subject: RE: [c-nsp] remove spanning-tree without being service
effecting

That kind of defeats the whole "not service effecting" issue.. thanks
anyway.

James Urwiller
Lead Internet Services Technician / Network Engineer CCNA 11567125
American Broadband
402-426-6257 - Office
402-278-1875 - Cell
402-426-6273 - Fax
jurwiller [at] americanbb


-----Original Message-----
From: Chuck Church [mailto:chuckchurch [at] gmail]
Sent: Thursday, August 02, 2012 9:49 AM
To: James Urwiller; cisco-nsp [at] puck
Subject: RE: [c-nsp] remove spanning-tree without being service
effecting

Figure out all the commands you need to enter for everything, put it in
a text file, and tftp that into the running config. Obviously test it
well before hand, and schedule a reload on the device just as a backup.

Chuck

-----Original Message-----
From: cisco-nsp-bounces [at] puck
[mailto:cisco-nsp-bounces [at] puck] On Behalf Of James Urwiller
Sent: Thursday, August 02, 2012 10:35 AM
To: cisco-nsp [at] puck
Subject: [c-nsp] remove spanning-tree without being service effecting

I have a MSTP ring that I want to remove spanning-tree all together, and
manually shut down my "dead" link. How can I remove or disable
spanning-tree without driving to each site? If I use the commands
"spanning-tree bpdufilter" or "spanning-tree bpduguard" they both
err-disable the port; which would cause my connectivity to the switch to
go down. I also use the command "spanning-tree portfast trunk" if I do
that command first before the bpduguard/filters will it not err-disable
the port??



Is there a better way to go about this??



James Urwiller

Lead Internet Services Technician / Network Engineer

CCNA 11567125

American Broadband

402-426-6257 - Office

402-278-1875 - Cell

402-426-6273 - Fax

jurwiller [at] americanbb <mailto:mjurwiller [at] americanbb>



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


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


jurwiller at americanbb

Aug 2, 2012, 9:24 AM

Post #9 of 15 (1221 views)
Permalink
Re: remove spanning-tree without being service effecting [In reply to]

I got clarification on his suggestion, and I will proceed with that. I
am aware of the risks, the question was how do I mitigate those risks..
your comment on leaving it alone doesn't help. if you don't have
anything good to say; then don't. Im sure the forum doesn't need your
attitude, I know I don't.

James Urwiller
Lead Internet Services Technician / Network Engineer
CCNA 11567125
American Broadband
402-426-6257 - Office
402-278-1875 - Cell
402-426-6273 - Fax
jurwiller [at] americanbb


-----Original Message-----
From: Pete Templin [mailto:petelists [at] templin]
Sent: Thursday, August 02, 2012 10:40 AM
To: James Urwiller
Cc: cisco-nsp [at] puck
Subject: Re: [c-nsp] remove spanning-tree without being service
effecting

On 8/2/12 8:18 AM, James Urwiller wrote:
> That kind of defeats the whole "not service effecting" issue.. thanks
> anyway.

He clearly said 'just as a backup'. You clearly said "without driving
to each site". What do you want? Get over it, there's risk involved in
what you want to do (that risk entered as soon as you chose to remove
STP, maybe as soon as you thought of it), you might want to implement a
safety net.

> -----Original Message-----
> From: Chuck Church [mailto:chuckchurch [at] gmail]
> Sent: Thursday, August 02, 2012 9:49 AM
> To: James Urwiller; cisco-nsp [at] puck
> Subject: RE: [c-nsp] remove spanning-tree without being service
> effecting
>
> Figure out all the commands you need to enter for everything, put it
> in a text file, and tftp that into the running config. Obviously test

> it well before hand, and schedule a reload on the device just as a
backup.


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


peter at rathlev

Aug 2, 2012, 11:13 AM

Post #10 of 15 (1247 views)
Permalink
Re: remove spanning-tree without being service effecting [In reply to]

On Thu, 2012-08-02 at 08:40 -0700, Pete Templin wrote:
> He clearly said 'just as a backup'. You clearly said "without
> driving to each site". What do you want? Get over it, there's risk
> involved in what you want to do (that risk entered as soon as you
> chose to remove STP, maybe as soon as you thought of it), you might
> want to implement a safety net.

On Thu, 2012-08-02 at 11:24 -0500, James Urwiller wrote:
> if you don't have anything good to say; then don't. Im sure the forum
> doesn't need your attitude, I know I don't.

Huh? You're seriously writing that? As a reply to what Pete wrote? I
need Pete's attitude a hell of a lot more than I need yours.

Converting between STP protocols (ieee/pvst/rapid-pvst) just can't be
done without convergence time. What "service effecting" is for people
might vary. I personally consider more than 50ms as service effecting.

Chuck wrote solid advice, what I'd consider simple best practice. That's
the way people do it. You reply:

On Thu, 2012-08-02 at 10:18 -0500, James Urwiller wrote:
> That kind of defeats the whole "not service effecting" issue.. thanks
> anyway.

Now tell me, who has an attitude problem?

--
Peter


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


andrew at 2sheds

Aug 2, 2012, 2:11 PM

Post #11 of 15 (1204 views)
Permalink
Re: remove spanning-tree without being service effecting [In reply to]

Sent from a mobile device

On 03/08/2012, at 2:24, "James Urwiller" <jurwiller [at] americanbb> wrote:

> I got clarification on his suggestion, and I will proceed with that. I
> am aware of the risks, the question was how do I mitigate those risks..
> your comment on leaving it alone doesn't help. if you don't have
> anything good to say; then don't. Im sure the forum doesn't need your
> attitude, I know I don't.

Stupid question, why do you actually want to disable spanning tree?

How do you plan on setting up redundant links?

How will you connect remotely to a switch and enable it when one goes down?

What happens when the broken link comes up again suddenly?

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


jurwiller at americanbb

Aug 2, 2012, 2:39 PM

Post #12 of 15 (1220 views)
Permalink
Re: remove spanning-tree without being service effecting [In reply to]

I have been having an issue with my few brocade devices in the ring not
blocking BPDU's properly towards my customers so when they hook a switch
up that has spanning-tree on by default, it causes a topology change.
Not cool!! :) I have made Brocade aware of the issues, and they are
working on a firmware patch to fix the issue, but until then I want to
turn off all my spanning-tree so that I don't have random topology
changes occur. Until I have verified that the Brocades block BPDU's
properly, I will have to manually shut down one of my links completing
the ring, and hope that if an actual equipment failure or fiber cut
happens that I can still get to that node to turn up the protection
link.

Hopefully next year's budget will allow me to upgrade the appropriate
equipment so that I can use another ring protection mechanism such as
REP, ERP, or MRP. This is just a stop gap until the brocades are fixed
or I can upgrade my core network. With all the voice and video I have
running, spanning-tree wasn't really doing the trick for me anyway with
the long protection times.

I just wanted to know if there was an easy way to disable it across my
switch-to-switch links without causing any outages; from research, it
seems that bpdu-filter, and then portfast-trunk might do it with no hit
to the network. I just wanted to see if that was truly the case.. I
have tried bpdu-guard with undesired results.

I have no idea what to do if the broken link would come back up; but I
have to do something about customers equipment causing topology changes
all the time, and for now that seems like the best way; this firmware
bug in the fastIron code has really put me in a pickle!



James Urwiller
Lead Internet Services Technician / Network Engineer
CCNA 11567125
American Broadband
402-426-6257 - Office
402-278-1875 - Cell
402-426-6273 - Fax
jurwiller [at] americanbb


-----Original Message-----
From: Andrew Miehs [mailto:andrew [at] 2sheds]
Sent: Thursday, August 02, 2012 4:11 PM
To: James Urwiller
Cc: Pete Templin; cisco-nsp [at] puck
Subject: Re: [c-nsp] remove spanning-tree without being service
effecting

Sent from a mobile device

On 03/08/2012, at 2:24, "James Urwiller" <jurwiller [at] americanbb>
wrote:

> I got clarification on his suggestion, and I will proceed with that. I

> am aware of the risks, the question was how do I mitigate those
risks..
> your comment on leaving it alone doesn't help. if you don't have
> anything good to say; then don't. Im sure the forum doesn't need your

> attitude, I know I don't.

Stupid question, why do you actually want to disable spanning tree?

How do you plan on setting up redundant links?

How will you connect remotely to a switch and enable it when one goes
down?

What happens when the broken link comes up again suddenly?

Andrew

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


Friedrich at pdv-sachsen

Aug 3, 2012, 2:38 AM

Post #13 of 15 (1183 views)
Permalink
Re: remove spanning-tree without being service effecting [In reply to]

Hi James,

I think it's a design problem. Ethernet L2 ring sounds bad to me. Especially multi-vendor rings are not a good idea.
What about to replace the Brocade stuff with cisco, there are only 2 in your ring? Or do you really need a L2 ring, why not L3 with routing protocol? Or cloud you filter spanning tree facing to the customer, at least. That is best practise.

Also REP would work better, but has to be tested in lab of course!

Thanks Gregor


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


jurwiller at americanbb

Aug 3, 2012, 6:03 AM

Post #14 of 15 (1181 views)
Permalink
Re: remove spanning-tree without being service effecting [In reply to]

I can't use REP on any of the cisco boxes I have in the ring, not
supported. Unless I am missing something? I have lots of L2 only
circuits, so I cant use something like OSPF entirely; even though I do
use it for my Internal routing. And the problem I am having is exactly
that.. not being able to filter spanning-tree facing the customer
because of the Brocade bug. I appreciate everyones comments, but I
think we are getting a little off track here, I am not asking a design
question, but rather how to remove spanning-tree from my existing
equipment with the least amount of impact to existing traffic. Thank
you!

James Urwiller
Lead Internet Services Technician / Network Engineer
CCNA 11567125
American Broadband
402-426-6257 - Office
402-278-1875 - Cell
402-426-6273 - Fax
jurwiller [at] americanbb

-----Original Message-----
From: cisco-nsp-bounces [at] puck
[mailto:cisco-nsp-bounces [at] puck] On Behalf Of Friedrich,
Gregor
Sent: Friday, August 03, 2012 4:39 AM
To: cisco-nsp [at] puck
Subject: Re: [c-nsp] remove spanning-tree without being service
effecting

Hi James,

I think it's a design problem. Ethernet L2 ring sounds bad to me.
Especially multi-vendor rings are not a good idea.
What about to replace the Brocade stuff with cisco, there are only 2 in
your ring? Or do you really need a L2 ring, why not L3 with routing
protocol? Or cloud you filter spanning tree facing to the customer, at
least. That is best practise.

Also REP would work better, but has to be tested in lab of course!

Thanks Gregor


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

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


mark.tinka at seacom

Oct 1, 2012, 6:29 AM

Post #15 of 15 (859 views)
Permalink
Re: remove spanning-tree without being service effecting [In reply to]

On Thursday, August 02, 2012 11:39:32 PM James Urwiller
wrote:

> Hopefully next year's budget will allow me to upgrade the
> appropriate equipment so that I can use another ring
> protection mechanism such as REP, ERP, or MRP. This is
> just a stop gap until the brocades are fixed or I can
> upgrade my core network. With all the voice and video I
> have running, spanning-tree wasn't really doing the
> trick for me anyway with the long protection times.

For next year's budget, might be time to consider going
IP/MPLS.

Much has been said about Cisco's ME3600X. Brocade also have
the CER/CES 2000 device. These will support IP and MPLS in
the Access layer, and you can forget about spanning tree
forever.

We did, and have been in deep sleep everytime the hour hand
chimes 3AM :-).

Mark.
Attachments: signature.asc (0.82 KB)

Cisco nsp RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.