JNCIP part 5

JNCIP part 5

The JNCIP iBGP case study, we will look at each requirement:

• Redistribute the static routes shown earlier in Figure 5.7 into IBGP, and using communities, ensure that all routers prefer r2's 192.168.100/24 IBGP route. You must not alter the default local preference of this route

Both R1,R2 will adv 192.168.100/24 to bgp peer, and R2 as primary with change Local-P. First at all, how many BGP attribute we can used ?

1, No weight here, it's Junos not IOS. forget it.
2, No Local-P, The requirement said can't change Local-P.
3, as-path, The iBGP update will not change as-path.
4, Origin code, The JNCIP ebook didn't using this way, but I DO.

policy-statement ibgp-exp {
term 1 {
from protocol static;
then {
metric 111;
origin incomplete;
accept;
}
}
}

Both R3,R4 will not select R1 as best route for 192.168.100/24
R3
192.168.100.0/24 *[BGP/170] 00:00:10, localpref 100
AS path: I
> to 10.0.4.2 via fe-0/1/0.23
[BGP/170] 00:00:10, localpref 100, from 10.0.3.4
AS path: I
> to 10.0.4.2 via fe-0/1/0.23
[BGP/170] 02:59:50, MED 111, localpref 100
AS path: ?
> to 10.0.4.14 via fe-0/1/2.13

so, It work for me!