We have a simple setup where we run EBGP with our ISP to learn default route. This is setup as follows:
show configuration protocols bgp
group ISP{
type external;
family inet {
unicast;
}
export connected-static;
peer-as 22222;
local-as 64333;
neighbor 172.31.255.89;
}
We are also running static route with next hop to customer router to learn some more range:
show configuration routing-options static
route 10.80.48.0/20 next-hop 10.80.48.33;
route 172.26.82.128/28 next-hop 10.80.48.33;
route 172.22.174.144/28 next-hop 10.80.48.33;
A requirement has come up to run EBGP with customer too to learn these routes. My question is do we just setup new neihbor within existing group ISP and send default to this customer and learn all these ranges with a policy statement only allowing above ranges OR do we need to setup IBGP with customer.
I have tried EBGP with the following@:
show | compare
[edit protocols bgp group ISP]
neighbor 172.31.255.89 { ... }
+ neighbor 10.80.48.33 {
+ import CUST_002-PLL048-A;
+ export default;
+ peer-as 65002;
+ }
[edit policy-options]
+ policy-statement CUST_002-PLL048 {
+ term accept {
+ from {
+ route-filter 10.80.48.0/20 exact;
+ route-filter 172.26.82.128/28 exact;
+ route-filter 172.22.174.144/28 exact;
+ }
+ then accept;
+ }
+ then reject;
+ }
+ policy-statement default {
+ term default-originate {
+ from {
+ protocol static;
+ route-filter 0.0.0.0/0 exact;
+ }
+ then accept;
+ }
+ then reject;
+ }
------------------------------
junos sky
------------------------------