http://www.routexp.com/2018/04/bgp-route-reflector-with-single-cluster.html
BGP Route Reflector amongst Single Cluster as well as Default Settings
Today I am going to utter most the BGP road reflector amongst unmarried cluster as well as default settings. I already utter most the basics of the road reflector inward my before article amongst the configuration example. If y'all would similar to hold off on that article, below is the link for the reference.
iBGP Full meshed solution: BGP Route Reflectors
Now starting from the rootage a niggling bit, nosotros take away to accept a snapshot on BGP road reflector. So the concept of BGP road reflectors resolves the expensive iBGP total meshed topology or y'all tin say BGP road reflector are about other solution for the explosion of iBGP peering inside the AS. Now let's rootage amongst the scenario where i volition utter most the unmarried cluster as well as the default settings
iBGP Full meshed solution: BGP Route Reflectors
Now starting from the rootage a niggling bit, nosotros take away to accept a snapshot on BGP road reflector. So the concept of BGP road reflectors resolves the expensive iBGP total meshed topology or y'all tin say BGP road reflector are about other solution for the explosion of iBGP peering inside the AS. Now let's rootage amongst the scenario where i volition utter most the unmarried cluster as well as the default settings
 |
| Fig 1.1- BGP RR amongst Single Cluster |
RR#show run | sec bgp
router bgp 1
bgp log-neighbor-changes
neighbor 10.0.10.2 remote-as 1
neighbor 10.0.10.2 route-reflector-client
neighbor 10.0.20.2 remote-as 1
neighbor 10.0.20.2 route-reflector-client
neighbor 10.0.40.2 remote-as 1
In this case, RouteXP_PE1 as well as RouteXP_PE3 are clients of RR spell RouteXP_PE2 is non-client. In conventional designs, non-client router volition be road reflector for routers inward the adjacent hierarchy grade but inward this representative merely about other PE is used for simplicity.
RR#show ip bgp cluster-ids
Global cluster-id: 172.16.3.3 (configured: 0.0.0.0)
BGP client-to-client reflection: Configured Used
all (inter-cluster as well as intra-cluster): ENABLED
intra-cluster: ENABLED ENABLED
List of cluster-ids:
Cluster-id #-neighbors C2C-rfl-CFG C2C-rfl-USE
RR#sh ip bgp 172.16.1.1
BGP routing tabular array entry for 172.16.1.1/32, version 2
Paths: (1 available, best #1, tabular array default)
Advertised to update-groups:
1 2
Refresh Epoch 2
Local, (Received from a RR-client)
10.0.10.2 from 10.0.10.2 (172.16.1.1)
Origin IGP, metric 0, localpref 100, valid, internal, best
rx pathid: 0, tx pathid: 0x0
RR#show ip bgp update-group 1
BGP version four update-group 1, internal, Address Family: IPv4 Unicast
BGP Update version : 4/0, messages 0
Topology: global, highest version: 4, tail marker: 4
Format state: Current working (OK, concluding non inward list)
Refresh blocked (not inward list, concluding non inward list)
Update messages formatted 2, replicated 2, electrical current 0, refresh 0, restrain 1000
Number of NLRIs inward the update sent: max 1, minute 0
Minimum fourth dimension betwixt promotion runs is 0 seconds
Has 1 member:
10.0.40.2
RR#show ip bgp update-group 2
BGP version four update-group 2, internal, Address Family: IPv4 Unicast
BGP Update version : 4/0, messages 0
Route-Reflector Client
Topology: global, highest version: 4, tail marker: 4
Format state: Current working (OK, concluding non inward list)
Refresh blocked (not inward list, concluding non inward list)
Update messages formatted 3, replicated 6, electrical current 0, refresh 0, restrain 1000
Number of NLRIs inward the update sent: max 1, minute 0
Minimum fourth dimension betwixt promotion runs is 0 seconds
Has two members:
10.0.10.2 10.0.20.2
These outputs demo that RR receives the 172.16.1.1/32 prefix from RouteXP_PE1 as well as reflects it to the customer RouteXP_PE3 as well as non-client RouteXP_PE2. In this detail case, update is every bit good sent dorsum to S1PE1, but it happens because RouteXP_PE1 as well as RouteXP_PE3 lead maintain the same routing policy and, therefore, shape the same update group.
