3.7.e Implement and troubleshoot scalability

3.7.e [i] Route-reflector, cluster

you might recognize this as rene’s bgp rr lab… i made some modifications…

rene_bgp_rr

the point of this lab is to prove the veracity of route-reflection, and to use the cluster-id… if you set it up with an igp, you won’t need route-reflection… you can prove that for yourself… i want to use route reflection in this topology in the most economical way, meaning the least commands… one of the great things about bgp is that you have so many choices, which is also one of the drawbacks for the lab exam because you’ll need to disregard your own methods and instead follow the directives set forth… but for me now this is about economy…

r1(config-router)#do sh run | b router
router bgp 1
no synchronization
bgp log-neighbor-changes
network 1.1.1.0 mask 255.255.255.0
 neighbor 192.168.12.2 remote-as 1
no auto-summary

r2(config-router)#do sh run | b router
router bgp 1
no synchronization
bgp log-neighbor-changes
 network 2.2.2.0 mask 255.255.255.0
 neighbor 192.168.12.1 remote-as 1
no auto-summary

arguably no the best choice (using update-source would require more commands) however…

r2(config-router)#do ping 2.2.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

we have liftoff… add r3 the same exact way and we have connectivity from the hub to the spokes, but not from spoke to spoke, naturally…

r3(config-router)#do ping 2.2.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:
…..
Success rate is 0 percent (0/5)

r2(config-router)#do sh ip bgp
BGP table version is 7, local router ID is 2.2.2.2
Status codes: s suppressed, d damped, h history, * valid, > best, i – internal,
r RIB-failure, S Stale
Origin codes: i – IGP, e – EGP, ? – incomplete

Network          Next Hop            Metric LocPrf Weight Path
*>i1.1.1.0/24       192.168.12.1             0    100      0 i
*> 2.2.2.0/24       0.0.0.0                  0         32768 i

we’ll have to advertise 192.168.12.0 and 192.168.13.0 but we need only do that from r1… more economy…

r1(config-router)#do sh run | b router
router bgp 1
no synchronization
bgp log-neighbor-changes
network 1.1.1.0 mask 255.255.255.0
 network 192.168.12.0
 network 192.168.13.0
neighbor 192.168.12.2 remote-as 1
neighbor 192.168.13.3 remote-as 1
no auto-summary

but still no connectivity…

r2(config-router)#do sh ip bgp
BGP table version is 23, local router ID is 2.2.2.2
Status codes: s suppressed, d damped, h history, * valid, > best, i – internal,
r RIB-failure, S Stale
Origin codes: i – IGP, e – EGP, ? – incomplete

Network          Next Hop            Metric LocPrf Weight Path
*>i1.1.1.0/24       192.168.12.1             0    100      0 i
*> 2.2.2.0/24       0.0.0.0                  0         32768 i
r>i192.168.12.0     192.168.12.1             0    100      0 i
*>i192.168.13.0     192.168.12.1             0    100      0 i

route-reflector client will mesh it up…

r1(config-router)#neigh 192.168.12.2 route-ref
r1(config-router)#neigh 192.168.12.2 route-reflector-client
*Mar  1 01:27:39.319: %BGP-5-ADJCHANGE: neighbor 192.168.12.2 Down RR client config change
r1(config-router)#neigh
*Mar  1 01:27:41.479: %BGP-5-ADJCHANGE: neighbor 192.168.12.2 Up
r1(config-router)#neigh 192.168.13.3 route-ref
r1(config-router)#neigh 192.168.13.3 route-reflector-client
r1(config-router)#
*Mar  1 01:27:55.619: %BGP-5-ADJCHANGE: neighbor 192.168.13.3 Down RR client config change
r1(config-router)#
*Mar  1 01:27:56.751: %BGP-5-ADJCHANGE: neighbor 192.168.13.3 Up

better…

r3(config-router)#do sh ip bgp
BGP table version is 29, local router ID is 3.3.3.3
Status codes: s suppressed, d damped, h history, * valid, > best, i – internal,
r RIB-failure, S Stale
Origin codes: i – IGP, e – EGP, ? – incomplete

Network          Next Hop            Metric LocPrf Weight Path
*>i1.1.1.0/24       192.168.13.1             0    100      0 i
*>i2.2.2.0/24       192.168.12.2             0    100      0 i
*> 3.3.3.0/24       0.0.0.0                  0         32768 i
*>i192.168.12.0     192.168.13.1             0    100      0 i
r>i192.168.13.0     192.168.13.1             0    100      0 i
r3(config-router)#do ping 2.2.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/38/48 ms

we have a good route table and reachability… add a cluster-id for each hub, advertise the connected networks between them, finish up the spokes and bgp is  almost as good as ospf, just takes 11 years to set it up is all…