[c-nsp] ISP / MPLS "POP" design

[Phil Bedard]

Like Mark mentioned the concept of stateful failure using virtual
chassis has been popular but nothing you listed supports doing that.
Making L2 terminations redundant is difficult, always has been without
doing something exotic. We do the VRRP thing in some instances, use
MC-LAG in others. In the past I have also used relatively inexpensive
optical failover devices. They are like an active Y-cable and switch
the signal when loss occurs, or you can do it manually during a
maintenance. That requires duplicate configs on both boxes. I don't
consider it scalable.

Most of the time though it involves the customer buying a second
circuit.

Phil From: CiscoNSP List
Sent: 11/8/2013 1:13
To: mark.tinka at seacom.mu
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] ISP / MPLS "POP" design
Thanks again for your responses Mark,

>
> We dealt with this commercially.
>
> We provided customers with a single uplink. Redundancy was
> never a native part of the solution. If a customer wanted
> redundancy, they paid for it. In such a case, we just
> deliver to live links, and let the customer configure to
> their pleasure.


If you lost a PE, would you migrate those customer tails to an
alternate PE? (Assume you would to minimise downtime?)

Im interested in how PE failures are dealt with in large networks.

Cheers.
 		 	   		
_______________________________________________
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/