Establish BGP Peering to Multiple Upstream Provider [ Edited ]

[chenoi]

Hai Guys...

Need some advise and assistant.

Currently my M10 establish bgp to only one upstream provider (international) and all the request for local/international will go through this provider due to this setup, i have some delay when customer request for local web site.

Iam intend to connect to more upstream provider as peering partner and resolve the issues above and to have multiple service provider connected to my ASN.

1. Now i want to estbalish BGP with one new upstream provider (Local Provider).

How can this be done...and ensure domestic request via this local provider and international request via my international provider and impove the latency issues.

this is current  config to existing upstream (international) and i have add new ebgp group for local provider which i will peering later.

Your comment and some example would be much appreciate.

SAMPLE OF CONFIG:-

routing-options {
    graceful-restart;
    static {
        route 0.0.0.0/0 next-hop 1.1.1.1;  //current setup all to international provider
        route 10.10.10.0/22 discard;
            }
    autonomous-system 11223;
}
protocols {
    bgp {
        traceoptions {
            file flag;
            flag keepalive detail;
            flag update detail;
            flag open detail;
        }
        local-as 11223;
        group InternationalProvider {  //Existing Upstream connected bgp
            type external; 
            import bogon;
            export transit;
            peer-as 44556;
            graceful-restart;
            neighbor 1.1.1.1;
        }
        group DomesticProvider {    //Create new group as 2nd Upstream
            type external;
            import bogon;           //Import and Export Policy
           export transit;
            peer-as 77889;          //ASN 2nd Upstream
            graceful-restart;
            neighbor 2.2.2.1;
        }
    }
}
policy-options {
    prefix-list fcbvcom-prefixes {
        10.10.10.0/22;
    }
    policy-statement bogon {
        term fcbvcom {
            from {
                route-filter 10.10.10.0/22 exact;
            }
            then reject;
        }

        
        term therest {
            then reject;
        }
    }
   
     
    policy-statement transit {
        term transit1 {
            from {
                route-filter 10.10.10.0/22 exact;
            }
            then accept;
        }
       
        term others {
            then reject;
        }
    }
}

Your kind assistant and help much appreciate and useful to me.

Thank you.

[davidjdv]

Hello,

Can you clarify what you call "local/domestic" traffic ? Is it based on set of IP prefixes or maybe one or more ASNs ?

Basically, the idea would be to assign a higher local-pref to the routes which you want to learn from your local provider.

Regards,

/david

[chenoi]

Hai Davidjdv,

local/domestic traffic - iam refer when my customer request for local content/local web site.

International upstream --- when request international content (nortel web site/juniper web site/google/etc)

currently iam only have 1 peering with international provider and problem of high latency when my customer request for local content where it will be a boomerang traffic.

i hope when i have a connection with new local provider it will resolve the latency problem for local content request. and at the same time to have redundant provider.

Iam thinking if  the router will route automatically the traffic request either to international or local provider. i dont know if the customer traffic more to local content or international content but i hope this new setup will improve the latency and at the same time i have redundant provider at less if one provider fail i still got backup.. :-)

[aarseniev]

I think the problem is two-fold.

1st, your router has to prefer local/domestic prefixes via local provider which is best achieved with inflating the Local Preference. This is typically done in import BGP policy.

2nd, you have to ensure that return traffic from local/domestic prefixes to your customers also travels via local provider. In order to do that, you have to make your customer prefixes more attractive to whoever hosts these local/domestic prefixes. If the hoster is single-homed to local provider then probably nothing needs to be done. If the hoster is multihomed to several providers including international, then you probably needs to prepend your outbound updates differently for local provider and for international provider. This is done in BGP export policy.

Good luck!

Rgds

Alex

[chenoi]

Hai aarseniev,

Thank you for the comment...

Some configuration would be much appreciate...

expecially on the preference and policy apply for this setup.

i have thinking and consider that all in/out trafc frm local traffic have to go through the local provider and international traffic will go through international provider and ensure the traffic in and out to the righ provider/gw.

i dont think so my current router config can fullfill the requirement.

[aarseniev]

Sure.

See below for config example

set policy-options prefix-list localroutes <prefix1>/<masklen1>
set policy-options prefix-list customerroutes <prefix2>/<masklen2>
set policy-options prefix-list ownrroutes <prefix3>/<masklen3>

set policy-options policy-statement domestic-import term 1 from prefix-list localroutes orlonger
set policy-options policy-statement domestic-import term 1 then local-preference 150
set policy-options policy-statement domestic-import term 1 then accept

set policy-options policy-statement transit-intl term intl-prepend from prefix-list customerroutes exact
set policy-options policy-statement transit-intl term intl-prepend then as-path-prepend 11223 11223
set policy-options policy-statement transit-intl term intl-prepend then accept
set policy-options policy-statement transit-intl term ownroutes prefix-list ownroutes exact
set policy-options policy-statement transit-intl term ownroutes then accept
set policy-options policy-statement transit-intl term others then reject

set policy-options policy-statement transit-dom term dom-prepend from prefix-list customerroutes exact
set policy-options policy-statement transit-dom term dom-prepend then as-path-prepend 11223
set policy-options policy-statement transit-dom term dom-prepend then accept
set policy-options policy-statement transit-dom term ownroutes prefix-list ownroutes exact
set policy-options policy-statement transit-dom term ownroutes then accept
set policy-options policy-statement transit-dom term others then reject

delete protocols bgp group DomesticProvider export
delete protocols bgp group InternationalProvider export

set protocols bgp group DomesticProvider import [ domestic-import bogon ]
set protocols bgp group DomesticProvider export transit-dom
set protocols bgp group InternationalProvider export transit-intl

[chenoi]

Hai aarseniev,

Thank you. i will try this.