This is exactly what we so in production. We split up our clouds by communities, marking them on their way out. We block other communities on the way in. This way our default route stays in that region. We have multiple Tier1 datacenters in regions that mark their default route and we accept or deny it if a better one exists in the existing table.
Works extremely well. The challenge is that we have 6 MPLS providers due to the countries we operate in.
Regards,
Jay McMickle- CCIE #35355 (RS), 3x CCNP (RS,Security,Design)
Sent from my iPhone
On Sep 27, 2012, at 10:27 AM, Sunil pareek <skpareek84_at_gmail.com> wrote:
> Hi All
>
> We have a scanrio like this where we have two data centers that are
> advertising the default route into the MPLS/VPN network and wed like some
> PE-routers to prefer Data Center 1, while the others should prefer Data
> Center 2 (and all PE-routers have to receive both default routes for
> redundancy reasons).
>
> Got some solution for this like to manipulate any bgp
> attribute(weight;local pref) by matching the ext. community attribute in a
> route-map but this manipulation needs to be done at vpnv4 level.Is there
> any other solution for this.
>
> Thanks
> Sunil
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Thu Sep 27 2012 - 13:34:19 ART
This archive was generated by hypermail 2.2.0 : Mon Oct 01 2012 - 06:40:29 ART