[c-nsp] REP

[Siva Valliappan]

Hi Eric,

    REP and STP are incompatible with each other.  if you are running REP
on a set of links, you cannot run STP on them.  that said we have the 
capability for a node that is running STP on a different set of links to
work with the REP running on other links via the REP edge node neighbor 
feature.  REP is able to generate Spanning Tree Change Notifications to send
into the STP part of the network and propagate changes coming from the SPT
domain into the REP domain.

regards
.siva

On Fri, 26 Jun 2009, Eric Van Tol wrote:

> I'm looking at REP for use in a metro ethernet environment and am looking for some real world opinions on its effectiveness.  The available white paper and documentation aren't 100% clear to me that STP can be disabled completely, or whether it should still run in addition to REP.  My preference is to remove STP from any switch in our network, then burn it, spread its ashes in a field, let cattle graze on the grass, then burn the cattle and shoot their remains into space on a collision course with the sun.  Apologies to animal rights activists, but this should give you an idea of how I really feel about Spanning Tree Protocol.
>
> Can anyone share any experiences they've had using REP?  We primarily use ME3400s in a ring topology with each end of the ring terminating in a pair of 6509s.  The 6509s, however, will be repurposed over the next few months as we replace them with an alternate vendor's equipment.  Not sure if this matters, but figured I'd mention it.  Right now, we use strictly layer 3 on all links between nodes on a ring, preventing us from taking advantage of the more advanced layer 2 and vrf-lite features of the ME3400s.  This probably poor design decision was made due to previously perceived limitations with REP some years ago.
>
> Thanks in advance,
> evt
> _______________________________________________
> 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/
>