|
Within an AS, IBGP must require fully connected logically, but with the increasing complexity of network topology, the fully network connection is costly, in order to solve this problem, we get the idea of BGP reflection. The basic idea of route reflector concept is: specify a centralized router as the center of the session point, a plurality of BGP routers to establish the peer session with this center point, and then more than one reflector router to establish the BGP peer session.
Characteristics of routing reflector:
1. Easy to understand
2. Transplantation (without changing the existing network topology)
3. Good compatibility (do not need all routers support reflection mechanism, reflection is transparent for customers)
Please note that when the reflector reflects routes, NEXT-HOP, AS_PATH, MED, and LOCAL_PRE properties should not be modified. At the same times, after the attributes applied in the routing policy in reflector was modified, the new attributes will not be applied to the reflecting route.
V5 reflector support general BGP, VPNV4, BGP VPN, in the specified view it should be configured as following:
Reflector cluster-id 4294967295 / / reflector ID
Peer 104.104.104.104 reflect-client / / specified the IBGP peer as reflector client
reflect between-clients / / the default configuration
|
|
|