[ietf79-tech] default route?

[Jim Martin]

Leon,
	If the backup is to CERNET2, and it's pure v6, what exactly is the plan for v4 connectivity if the primary link goes down? I have two specific concerns:

	a) That we have reasonably high performance and solid v4 connectivity should the primary ISP link fail
	b) That the backup path is unfiltered just as we expect of  the primary

	Can you explain a bit more? Perhaps this would be easier once we can see the external connectivity diagram Randy asked for during the tech call.

	Thanks!

	- Jim

On Oct 12, 2010, at 9:06 PM, Xiaoliang Zhao wrote:

> Hi Jim,
> 
> In our case, the backup link is connecting to CERNET2, which is a pure IPv6 network. in other words, the backup link has very few ipv4 traffic per design. Usual TE tricks may not work well here, i'm afraid.
> 
> thanks,
> Leon
> 
> On Wed, Oct 13, 2010 at 11:22 AM, Jim Martin <jim at daedelus.com> wrote:
> Leon,
>        My personal preference is to take full routes from all sources so you have maximum control on our side. The usual approach is to allow simple best path, taking everything from everyone, and letting the usual BGP rules take control. However, you then have the ability to apply LocalPref as a knob to make fine adjustments if you need/want to. This works well if a particular site is having problems over one link and you want to force it out the other. It also allows you to set localpref based upon incoming communities, to say, for example, prefer a R&E path over a commodity.
> 
>        - Jim
> 
> On Oct 12, 2010, at 8:09 PM, Xiaoliang Zhao wrote:
> 
> > Hi,
> >
> > We are thinking to get default route from our ISPs with the intention to simplify the policy. So the basic idea is we get 0/0 from both primary and backup link via bgp, we do local pref to engineer the traffic. Any thoughts on potential issues?
> >
> > thanks,
> > Leon
> > _______________________________________________
> > ietf79-tech mailing list
> > ietf79-tech at daedelus.com
> > http://www.daedelus.com/mailman/listinfo/ietf79-tech
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.daedelus.com/pipermail/ietf79-tech/attachments/20101013/04aacfd5/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3675 bytes
Desc: not available
Url : http://www.daedelus.com/pipermail/ietf79-tech/attachments/20101013/04aacfd5/attachment.bin