This does not work:
Switch A ------------------ REP switch 1
| (REP ring)
|------------------ REP switch 2
You have to use backup links on Switch A so that both links aren't active at
the same time.
Mike
--
Michael K. Smith - CISSP, GSEC, GISP
Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com
w: +1 (206) 404-9500 f: +1 (206) 404-9050
PGP: B49A DDF5 8611 27F3 08B9 84BB E61E 38C0 (Key ID: 0x9A96777D)
> -----Original Message-----
> From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-
> boun...@puck.nether.net] On Behalf Of Lukasz Bromirski
> Sent: Monday, November 28, 2011 9:15 AM
> To: cisco-nsp@puck.nether.net
> Subject: Re: [c-nsp] Applying cisco REP
>
> On 2011-11-28 17:55, Michael K. Smith - Adhost wrote:
> > Hello:
> >
> > The one limitation of REP is no spanning tree.
>
> Well, isn't it obvious, as REP was developed to eliminate
> need for STP?
>
> REP can perfectly interwork with STP at the edges.
>
> --
> "There's no sense in being precise when | Łukasz Bromirski
> you don't know what you're talking | jid:lbromir...@jabber.org
> about." John von Neumann | http://lukasz.bromirski.net
> _______________________________________________
> cisco-nsp mailing list cisco-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
