Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Knowledge
Base
Home
BGP
Data Center
GPON
Hadoop
IP Multicast
IPv6
IS-IS
Juniper-JUNOS
L2VPN
LAN
Link Aggregation
LTE Notes
MPLS
NAT
OAM
OSPF
PBB
PPP
QoS
Security
Configuration:
Client1 and Client3 routers are clients of RR1 router while Client2 and Client4
are the clients of RR2 router. There is a single IBGP session between each
router.
Client1 advertises 11.1.1.1/32 route to RR1 router and Client2 advertises
12.1.1.1/32 route to RR2 router.
Traffic Engineering
VPLS
VPN
Attachments
https://sites.google.com/site/amitsciscozone/home/bgp/bgp-route-reflectors
1/5
9/8/2014
11.1.1.1/32 on RR1
!--------- Client1 router advertises 11.1.1.1/32 to RR1 router
Client1# show ip bgp 11.1.1.1
BGP routing table entry for 11.1.1.1/32, version 2
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Advertised to update-groups:
1
Local
0.0.0.0 from 0.0.0.0 (172.16.1.2)
Origin IGP, metric 0, localpref 100, weight 32768, valid, sourced,
https://sites.google.com/site/amitsciscozone/home/bgp/bgp-route-reflectors
2/5
9/8/2014
local, best
Client1# show ip bgp update-group
BGP version 4 update-group 1, internal, Address Family: IPv4 Unicast
BGP Update version : 5/0, messages 0
Update messages formatted 1, replicated 0
Number of NLRIs in the update sent: max 1, min 1
Minimum time between advertisement runs is 0 seconds
Has 1 member (* indicates the members currently being sent updates):
172.16.1.1
RR1 router advertises this "best" route to all its IBGP peers including the peer
it received from.
RR2 receives 11.1.1.1/32 prefix from RR1 router. RR1 adds the Originator ID
attribute (Router ID of Client1 router 172.16.1.2) and Cluster List
attribute (Router ID of RR1 router 1.1.1.1).
3/5
9/8/2014
When RR2 receives the prefix 11.1.1.1/32, it accepts the prefix and
advertises to Client2 after appending its Router ID (2.2.2.2) to the Cluster
List attribute. The Originator ID attribute remains unchanged.
Summary:
BGP route reflector rules1. An IBGP prefix received from a RR-client is advertised to all peers
including the RR-client that advertised the prefix.
2. Routes originated by the router and routes received from EBGP
neighbors and selected as "best" routes are advertised to all internal
and external BGP peers.
3. A RR non-client advertising a prefix is advertised to all EBGP peers and
IBGP RR-clients.
4. Routes received from RR-clients and selected as "best" routes are
advertised to all internal and external BGP peers.
5. The RR adds the Originator ID to the routes received from its RRclients.
6. The RR appends its own Router ID to the Cluster List attribute.
Further reading:
http://wiki.nil.com/BGP_route_reflectors
Comments
https://sites.google.com/site/amitsciscozone/home/bgp/bgp-route-reflectors
4/5
9/8/2014
https://sites.google.com/site/amitsciscozone/home/bgp/bgp-route-reflectors
Google Sites
5/5