Friday, June 24, 2016

BGP-iBGP Route Reflection-Confederation

It offers an alternative to the logical full-mesh requirement of internal border gateway protocol (IBGP). A RR acts as a focal point for IBGP sessions.

1. Routes learned from EBGP peers can be sent to other EBGP peers, clients, and non-clients.
2. Routes learned from client peers can be sent to EBGP peers, other client peers, and non-clients.
3. Routes learned from non-client peers can be sent to EBGP peers, and client peers, but not other non-clients



R2(config-router)#do show run | s bgp
router bgp 100
 no synchronization
 bgp log-neighbor-changes
 network 2.2.2.0 mask 255.255.255.0
 neighbor 12.1.1.1 remote-as 100
 neighbor 12.1.1.1 route-reflector-client
 neighbor 23.1.1.3 remote-as 100
 neighbor 23.1.1.3 route-reflector-client

CLUSTER ID
R1:
router bgp 100
bgp cluster-id 150.1.1.1
network 150.1.1.1 mask 255.255.255.255

CONFEDERATION
In network routing, BGP confederation is a method to use BGP to subdivide a single autonomous system (AS) into multiple internal sub-AS's, yet still advertise as a single AS to external peers In confederation, a public AS is split into smaller Sub Autonomous Systems (Sub-ASs), which exhibit a hybrid behavior of both iBGP and EBGP. Inside a Sub-AS, the requirement for either fully meshed iBGP peerings or route reflection still applies, but between Sub-ASs, EBGP advertisement rules apply.

R1#
router bgp 65508
bgp confederation identifier 100
bgp confederation peers 65146 65379

network 150.1.5.5 mask 255.255.255.255
neighbor 155.1.0.1 remote-as 65146
neighbor 155.1.0.2 remote-as 200



No comments:

Post a Comment