[c-nsp] Layer 2 redundancy

[Alban Dani]

Bruce your observation is correct.

Thank you,

alban




On 11/17/06, Bruce Pinsky <bep at whack.org> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Alban Dani wrote:
> > ---SW1----|---------------------------------|CORE1|
> >      |                Provider A               |
> >      |                                              | hsrp
> >      |                                              |
> > ----SW2----|--------------------------------|CORE2|
> >                      ProviderB
> >
> > In the above diagram CORE1 and CORE2 are configured as hsrp peers.
> > SW1 connects to CORE1 on a layer 2 connection via Provider A and SW2
> > connects layer2 to CORE2 via provider B.
> >
> > There is no spanning tree running accross those links.
> > How can one can provide redundancy so that in case the link from
> Provider A
> > (considered primary) fails the traffic passes through the Provider B
> link.
> >
>
> I presume CORE1 and CORE2 have ethernet connections to the providers.  In
> that case, your interface(s) may or may not go down.  Generally, I'd
> recommend basic interface tracking, but in this case you may need to look
> at enhanced object tracking.  Check out:
>
>
> http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a00801541be.html
>
> - --
> =========
> bep
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.4 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFXcpmE1XcgMgrtyYRAhDuAJwP+ZNDMftyykbmqzTCQUy8cUmTuACgqdjI
> MHGcW8ZtXz3p/+vMziVnyVY=
> =WnPM
> -----END PGP SIGNATURE-----
>