Bgp Route Reflector Configuration - H3C LS-3100-52P-OVS-H3 Operation Manual

[SwitchA-route-policy] apply community no-export
[SwitchA-route-policy] quit
# Apply the routing policy.
[SwitchA] bgp 10
[SwitchA-bgp] peer 200.1.2.2 route-policy comm_policy export
[SwitchA-bgp] peer 200.1.2.2 advertise-community
# Display the routing table on Switch B.
[SwitchB] display bgp routing-table 9.1.1.0
BGP local router ID : 2.2.2.2
Local AS number : 20
Paths: 1 available, 1 best
BGP routing table entry information of 9.1.1.0/24:
From
Original nexthop: 200.1.2.1
Community
AS-path
Origin
Attribute value : MED 0, pref-val 0, pre 255
State
Not advertised to any peers yet
The route 9.1.1.0/24 is not available in the routing table of Switch C.

BGP Route Reflector Configuration

Network requirements
In the following figure, all switches run BGP.
Between Switch A and Switch B is an eBGP connection, between Switch C and Switch B, and
between Switch C and Switch D are iBGP connections.
Switch C is a route reflector with clients Switch B and D.
Switch D can learn route 1.0.0.0/8 from Switch C.
Figure 1-24 Network diagram for BGP route reflector configuration
: 200.1.2.1 (1.1.1.1)
: No-Export
: 10
: igp
: valid, external, best,
1-52