Information Technology Reference
In-Depth Information
Example 12-3 provides the basic route reflector configuration in the case study network.
Peer groups are used, and there is a single eBGP client, R7.
Example 12-3
R1 BGP Configuration
router bgp 65000
no synchronization
bgp log-neighbor-changes
neighbor IPv4_RR peer-group
neighbor IPv4_RR remote-as 65000
neighbor IPv4_RR update-source Loopback0
neighbor IPv4_RRC peer-group
neighbor IPv4_RRC remote-as 65000
neighbor IPv4_RRC update-source Loopback0
neighbor IPv4_RRC route-reflector-client
neighbor 10.1.1.2 peer-group IPv4_RR
neighbor 10.1.1.3 peer-group IPv4_RR
neighbor 10.1.1.6 peer-group IPv4_RRC
neighbor 192.168.1.1 remote-as 65001
no auto-summary
!
Example 12-4 shows the configuration of R6.
Example 12-4
R6 BGP Configuration
router bgp 65000
no synchronization
bgp log-neighbor-changes
network 10.6.0.0 mask 255.255.0.0
neighbor 10.1.1.1 remote-as 65000
neighbor 10.1.1.1 update-source Loopback0
no auto-summary
!
Planned IPv6 Overlay
The IPv6 BGP deployment follows the same topology as the IPv4 network. The core
routers (R1, R2, and R3) act as route reflectors for the IPv6 prefix information. The
edge routers (R4, R5, and R6) are route reflector clients.
The following steps outline the process of configuring the IPv6 BGP network:
If IPv6 forwarding is not enabled, IPv6 packets will not be routed. It is
possible to configure IPv6 routing and have IPv6 routing information in
the routing table, but packets will not be forwarded if forwarding is not
enabled. The command is
ipv6 unicast-routing
in global configuration
mode.
Step 1
