Q5 – BGP (2 Points)

When R12 traces to the following routes,

194.1.1.0/24
8.8.8.8/32
123.0.0.0/8
134.0.0.0/8

It should get the same result as shown in the following exhibit.

R12#traceroute 194.1.1.1 probe 2

1 123.45.67.45
123.45.67.46
2 123.45.67.9 [MPLS
123.45.67.13 [MPLS
3 123.45.67.1 [MPLS
4 123.45.67.18 [MPLS
5 134.56.78.42
6 134.56.78.14

R12#traceroute 8.8.8.8 probe 2

1 123.45.67.45
123.45.67.46
2 123.45.67.9 [MPLS
 123.45.67.13 [MPLS
3 123.45.67.1 [MPLS
4 123.45.67.18 [MPLS
5 134.56.78.38
6 134.56.78.14
7 8.8.8.8

R12#traceroute 123.3.3.3 probe 2

1 123.45.67.45
2 123.45.67.9 [MPLS
3 123.45.67.1 [MPLS
4 123.45.67.6 [MPLS

R12#traceroute 134.21.21.21 probe 2

1 123.45.67.46
2 123.45.67.13 [MPLS
3 123.45.67.1 [MPLS
4 123.45.67.6 [MPLS
5 134.56.78.38

1. BGP IPv4 Neighbor

1. R26 needs EBGP with R21, R22. Ensure next-hop-self command is present
2. R21, R22, R3, R5 needs to be full mesh
3. R12 need EBGP with R4, R6
4. R3, R5 are route reflectors. R4 and R6 are associated with one of the resume’s neighbors

2. Routing Delivery
1. Start transfer from R26, 194.x.x.x and 8.8.8.8
2. Arrived R21, R22, then transfer to R3, R5 through next-hop-self
3. R1 and R5 as route reflectors transfer the routes to R4 and R6
4. R4 and R6 transfer to R12
3. BGP traceroute 194.1.1.1 probe 2
Load balanced between R4 and R6, R2 ->R1-> R5 -> R22 -> R26 -> Server4
3.1. MED Control Routing Path (smaller is better)
1. Does the prefix-list permit 194.1.x.x
a. #sh run | s list. Check if there is a call to 194 prefix-list on the route map
2. Call the 194 prefix list on route-map
3. Change the MED value on route-map. Finally, MED of 194 through R22 is smaller than
that of R21 (view BGP table on R5)

3.2. LP Control Routing Path (bigger is better)

1. Globally modified to 101 (default is 100)
a. Use route-map to modify a specific route
b. R21 – Change the LP to 101
c. R21 – Use prefix-list permit 194 subnet
d. Route-map match prefix-list 194
e. Change the LP to 99 on route-map (Less than the default 100)
f. For 194.x.x.x, if R22 LP is be bigger than R21; hence R22 will be preferred
2. Globally modified to 99 (default is 100)
a. Use route-map to modify specific route
b. R22 – Change LP to 99
c. R22 – Use prefix-list permit 194 subnet
d. Route-map match prefix-list 194
e. Change the LP to 101 on route-map
f. For 194.x.x.x, the R22 LP will be bigger than R21; hence R22 will be preferred

3.3. R12 to R4, R6 Load Balancing

1. Use MED to control route path
2. Use prefix-list permit 194 subnet
3. Route-map match prefix-list 194
4. Change MED to same value
 5. R12 load balancing. #maximum-path 2

4. Traceroute 8.8.8.8 probe 2

Same as 194.x.x.x except that R21 is preferred

5. Traceroute 134.21.21.21
R12-> R6 -> R2 -> R1 -> R3 ->R21
5.1. R21 to R3
1. Network 134 on the R12 IPV4 address-family
2. R12 transfer the ip route to R3

5.2. R3 to R6
1. R3 received the IP route form R12
2. Transfer the route again to the next hop through route reflector
3. R6 received the 134 subnet ip route through route reflector

5.3. R6 to R12
1. Use prefix-list permit 134 subnet
a. #sh run | s list check if prefix-list permit for 134 network
2. R6 route-map modified MED less than R4 for 134 subnet. Check the direction of the
route-map call. The modified MED value
3. R12 go to 134 network segment preferred on R6.

6. Traceroute 123.3.3.3
R12-> R4 -> R2 -> R1 -> R3
6.1. R3 ro R4
1. Need network 123 subnet on R3 ipv4 address-family
2. R4 received 123 subnet through bgp neighbor or route-reflector

6.2. R4 to R12

Mostly MED control

1. Use prefix-list permit 123 subnet
 a. #sh run | s list check the prefix-list permit 123 subnet
2. R4 route-map modified MED less than R6 for 123 subnet
3. R12 go to 123 network segment preferred R4

ANS Q5 – BGP
Concepts:

1. Path from R12 to 194.1.1.1 from R12 to R26 is as follows

a. Load balanced between R4 and R6, R2 ->R1-> R5 -> R22 -> R26 -> Server4
2. Path from R12 to 134.21.21.21 (Lo0 on R21) is as follows:
a. R6 -> R2 -> R1-> R3 -> R21
3. Path from R12 to 123.3.3.3 (Lo0 on R3) is as follows:
a. R4 -> R2 -> R1-> R3
4. Path from R12 to 8.8.8.8 (Lo0 on R3) is as follows:
a. Load balanced between R4 and R6, R2 ->R1-> R3 -> R21 -> R20 -> Server4
5. R26 needs to build EBGP neighbors with R21 and R22
6. R12 needs to build EBGP neighbors with E4 and R6

# Device Commands Validations

1 Check BGP Neighbor
R12 sh ip bgp summary 3 neighbors – R4 and R6 and R11
No neighbor with R4. Idle (Admin)
means shutdown
R4 sh ip bgp summary 3 neighbors – R5, R6 and R12
R6 sh ip bgp summary 3 neighbors – R3, R4 and R12
R3 sh ip bgp summary 4 neighbors - R5, R6, R21 and R22
R3 is RR for R6.
R5 sh ip bgp summary 4 neighbors - R3, R4, R21 and R22
R5 is RR for R4.
Missing BGP neighbor with R4. Issue
resolved next section
 R22 sh ip bgp summary 5 Neighbors – R3, R5, R21, R26, and
another router.
Ignore admin shutdown of 123.1.2.18 as it
is a fault for Q6
R21 sh ip bgp summary 4 Neighbors – R3, R5, R22, R26

R12 sh run | s r b Fault 1 – Neighbor 123.45.67.45 shutdown

Fix R12

router bgp 14567

no nei 123.45.67.45 shutdown

show ip bgp summary

R5 sh run | s r b Fault 2: #no neighbor 123.4.4.4 activate
under address-family ipv4
Fix R5

router bgp 12345

address-family ipv4
neighbor 123.4.4.4 activate
2 Check Load Balancing on R12
R12 sh ip bgp 8.8.8.8/32 Not load balanced. Check BGP
configuration

R12 sh run | s r b Fault 3: Missing maximum-path 2

Fix R12
router bgp 14567
maximum-paths 2

3 Check next-hop-self
R3 sh run | s r b Ensure for next-hop-self
R5 Fault 4: No next-hop-self appears in the
R21 peer-group
R22
Fix R21
router bgp 12345
 neighbor PEER next-hop-self

4 Check MPLS Interfaces

R1 sh mpls ldp discovery
R2 sh mpls ldp nei
R1 sh mpls interfaces Fault 5: R2 E0/0, E1/0, E2/0 should appear.
R2 Only E0/0 appears
Fix R1/R2
sh mpls int

int E1/0
mpls ip
int E2/0
mpls ip

5 Check Route-Map and Prefix List

R21 sh run | s r b Fault 6: MED out. Should be MED in
Fix R21
router bgp 12345
no neighbor 134.56.78.6 route-map MED out
neighbor 134.56.78.6 route-map MED in

R21 sh run | s route-map Found the following:

match ip address prefix-list 194
set local-preference 99
R21 sh run | s list Fault 7: Missing prefix on Prefix-list 194
Fix R21
ip prefix-list 194 permit 194.1.0.0/16 le 32

R6 sh run | s route-map Fault 8: For prefix-list 134 metric is 500

R6 sh run | s list Check to make sure prefix-list 134 is as
follows:
ip prefix list 134 seq 5 permit
134.0.0.0/8 le 32
Fix R6
route-map MED permit 20
no set metric 500
set metric 100 (Less than that of R4)
 clear ip bgp * soft

traceroute 134.21.21.21 /--Make sure output matches with Q --/

traceroute 123.3.3.3 /--Make sure output matches with Q --/
traceroute 8.8.8.8 probe 2 /--Make sure output matches --/
traceroute 194.1.1.1 probe 2 /--Make sure output matches--/

6 Testing
R3,R4 sh ip bgp Ensure 8.8.8.8 and 194.1.0.0 prefixes need
R5,R6 to be available. But, both are not available.
R21,R22
R12 sh ip bgp Ensure 8.8.8.8 and 194.1.0.0 prefixes
available
m should appear against 8.8.8.8 and
194.1.1.1 prefixes

Check prefix 134.21.21.21/32. Check

Metric, which is 200 for R4(.45) and 500 for
R6(.46)
For 123.3.3.3, Metric is 100 for R4(.45) and
150 for R6(.46)
R12 traceroute 8.8.8.8 If went to R2 (.9 and .13) and then died,
check MPLS IP on R1/R2
R3 sh ip bgp 8.8.8.8/32 If 134.56.78.6 is inaccessible from
134.21.21.21, next-hop-self is missed

TS1 Q5 – BGP Fault Summary and Remediation

# Device Fault Remediation

1 R12 Neighbor R4 no nei 123.45.67.45 shutdown
Shutdown
2 R5 No neighbor with Add nei 123.4.4.4
R4
3 R12 missing maximum- Add maximum-paths 2 to the router configuration
paths 2
4 R21 No next-hop-self Add next-hop-self to bgp configuration
5 R1/R2 Missing MPLS IP Add e0/0, e1/0, e2/0 to MPLS IP
6 R21 MED Add following to router configuration
misconfiguration neighbor 134.56.78.6 route-map MED in
7 R21 missing ip prefix-list 194 permit 194.1.0.0/16 le 32
194.1.0.0/16 in
prefix-list
8 R6 incorrect metric route-map MED permit 20
on route-map no set metric 500
MED set metric 100

Strategy
 R21, R22, R3, and R5 are full-mesh
 R5 is connected to R4 and R3 is connected to R6
 Path from R12 to Server4 (194.1.1.1) is as follows:

 Path from R12 to Internet (8.8.8.8)

 Path from R12 to Lo0 of R3 (123.3.3.3)

 Path from R12 to Lo0 of R21 (134.21.21.21)

 When you run R12#sh ip bgp, you should see 8.8.8.8/32 load balanced between R4
and R6. Make sure no metrics or local preference against this prefix
 When you run R12#sh ip bgp, you should see 194.1.1.1/32 load balanced between
R4 and R6. Make sure metric same (i.e. 200) for both from R4 and R6
 When you run R12#sh ip bgp 123.3.3.3, metric of 100 from 123.45.67.45 (R4) and
150 from 123.45.67.46 (R6) is OK, as R12 will select R4 to reach the R3 (123.3.3.3)
 When you run R12#sh ip bgp 123.21.21.21/32, metric of 200 from 123.45.67.45 (R4)
and 500 from 123.45.67.46 (R6) is not OK, as R12 is required to select R6 to reach the
R21 (123.21.21.21). Hence, we will need to change the metric on R6 to less than 200.
Change the Metric of R6 to 100.
R6#sh run | s r b
neighbor 123.45.67.44 route-map MED out
  If you find no issues with routes but can’t traceroute, the problem is LDP neighbor.
 Check LDP neighbor of R1 and R2 and mpls IP. Make sure all three interfaces of R1
and R2 (e0/0, e1/0, and e2/0) are enabled for MPLS (i.e. #mpls ip)
 If R12#traceroute 8.8.8.8 is not load balanced, add #maximum-path 2 to the
BGP configuration.
 The default local preference for R21 is 101 and that of R22 is 100. But, in R22, the LP
for 194.0.0.0/8 is configured as 100 and for R21 as 99. Hence, all traffic to the
194.0.0.0/8 from R12 will go through R22, which will meet the exam requirement.
But, when you run R21#sh ip bgp, you see the next-hop for 8.8.8.8 as R22 and
not R26. Hence, the problem is with the prefix-list.

High Level Steps

1. Check BGP neighbor

2. Check R4 and R6 about metric
3. Check R21 and R22 about metric or local-preference
4. Check LDP neighbor
Variation of Q5-BGP
There may be a variation of the question with traceroute requirements as follows. The strategy
adopted above will still work. The requirement is to load-balance traffic between R4 andR6 for
the prefix 194.1.x.1 (x is 0,1,2,3), and then have the traffic go through R22.

R12#tr 194.1.0.1 pr 2 nu
Type escape sequence to abort.
Tracing the route to 194.1.0.1
VRF info: (vrf in name/id, vrf out name/id)
1 123.45.67.45 0 msec
123.45.67.46 1 msec
2 123.45.67.9 [MPLS: Label 27 Exp 0] 0 msec
123.45.67.13 [MPLS: Label 27 Exp 0] 1 msec
3 123.45.67.1 [MPLS: Label 21 Exp 0] 0 msec 1 msec
4 123.45.67.18 [MPLS: Label 18 Exp 0] 0 msec 1 msec
5 134.56.78.42 0 msec 1 msec
6 134.56.78.14 1 msec *

R12#tr 194.1.1.1 pr 2 nu
Type escape sequence to abort.
Tracing the route to 194.1.1.1
VRF info: (vrf in name/id, vrf out name/id)
1 123.45.67.45 0 msec
123.45.67.46 0 msec
2 123.45.67.9 [MPLS: Label 27 Exp 0] 1 msec
123.45.67.13 [MPLS: Label 27 Exp 0] 1 msec
3 123.45.67.1 [MPLS: Label 21 Exp 0] 0 msec 1 msec
4 123.45.67.18 [MPLS: Label 18 Exp 0] 0 msec 1 msec
5 134.56.78.42 0 msec 1 msec
6 134.56.78.14 0 msec *

R12#tr 194.1.2.1 pr 2 nu
Type escape sequence to abort.
Tracing the route to 194.1.2.1
VRF info: (vrf in name/id, vrf out name/id)
1 123.45.67.45 1 msec
123.45.67.46 0 msec
2 123.45.67.9 [MPLS: Label 27 Exp 0] 0 msec
123.45.67.13 [MPLS: Label 27 Exp 0] 0 msec
3 123.45.67.1 [MPLS: Label 21 Exp 0] 1 msec 0 msec
4 123.45.67.18 [MPLS: Label 18 Exp 0] 1 msec 0 msec
5 134.56.78.42 1 msec 1 msec
6 134.56.78.14 0 msec *
R12#tr 194.1.3.1 pr 2 nu
Type escape sequence to abort.
Tracing the route to 194.1.3.1
VRF info: (vrf in name/id, vrf out name/id)
1 123.45.67.45 1 msec
123.45.67.46 0 msec
2 123.45.67.9 [MPLS: Label 27 Exp 0] 1 msec
123.45.67.13 [MPLS: Label 27 Exp 0] 1 msec
3 123.45.67.1 [MPLS: Label 21 Exp 0] 0 msec 1 msec
4 123.45.67.18 [MPLS: Label 18 Exp 0] 0 msec 1 msec
5 134.56.78.42 0 msec 1 msec
6 134.56.78.14 0 msec *

Troubleshooting Steps

1. Ensure R12 has #maximum-path 2 for the load balance to happen on R4 and R6
2. Ensure R4 and R6 has same metrics for 194.1.x.0/24 (x = 0,1,2,3) prefix on the prefix-list
3. Ensure that R21 has route-map for 194.1.x.0/24 (x = 0,1,2,3) in not out.
4. Ensure that R21 prefix-list has all the four entries 194.1.x.0/24 (x = 0,1,2,3)