Topology for: EIGRP, BGP, Redistribution e1/0 10.0.12.1/24 10.0.12.2/24 e1/0 R1 s2/0 10.0.0.1/24 10.0.13.3/24 e0/0 10.0.23.2/24 e0/0 e0/0 10.0.13.1/24 R3 e1/0 10.0.23.3/24 R2 S2/0 10.0.0.2/24 PVC 104 PVC 204 10.0.0.4/24 PVC 401 s2/0 PVC 402 R4
Tasks - page 1 You may not use static or default routes. All IP addresses must be reachable from all devices. FRAME RELAY (3p): Use only PVCs from the diagram. Do not use Cisco proprietary encapsulation. No dynamic entries are allowed in routers FR map tables. No subinterfaces are allowed. No broadcasting is allowed over Frame Relay PVCs. EIGRP (3p): Configure EIGRP to run on all physical links. Use minimum network commands necessary. On each BGP router create loopback 0 interface. Assign this interface X.X.X.X/32 ip address. X is router number. Redistribute loopback 0 routes into EIGRP as external. No other subnets should be routed via EIGRP. Place R1 and R2 in AS 12. Place R4 in AS 4. Configure each BGP router with loopback 0 ip address as BGP router ID. Make sure this router ID will not change even in case of router reload. Configure BGP peerings in AS 12 using loopback 0 interfaces. Configure BGP peerings between AS 12 and AS 4 using loopback 0 interfaces. Use minimum neighbor commands necessary. Protect these sessions using MD5 with password CCIE-3.
Tasks - page 2 On each BGP router create loopback 1 interface. Assign this interface 10.X.X.X/24 ip address. X is router number. Import loopback 1 routes in AS 12 with Origin attribute of IGP. Do not use network command to accomplish this. In AS 4 import loopback 1 route on R4 with origin Incomplete. Do not use redistribute command to accomplish this. Configure R2 so that R1 prefers R2 as next hop toward 10.4.4.0/24. Configure R4 so that you achieve symmetric routing. Make sure loopback 1 routes are reachable even if Ethernet link between R1 and R2 fails.
Topology for: EIGRP, BGP, Redistribution AS 12 e1/0 10.0.12.1/24 10.0.12.2/24 e1/0 lo0 1.1.1.1/32 lo1 10.1.1.1/24 R1 s2/0 10.0.0.1/24 IBGP 10.0.13.3/24 e0/0 10.0.23.2/24 e0/0 e0/0 10.0.13.1/24 R3 e1/0 10.0.23.3/24 BGP lo0 2.2.2.2/32 lo1 10.2.2.2/24 R2 s2/0 10.0.0.2/24 PVC 104 PVC 204 EBGP EBGP AS 4 10.0.0.4/24 PVC 401 s2/0 PVC 402 R4 lo0 4.4.4.4/32 lo1 10.4.4.4/24
Tasks - page 1 You may not use static or default routes. All IP addresses must be reachable from all devices. FRAME RELAY (3p): Use only PVCs from the diagram. Do not use Cisco proprietary encapsulation. No dynamic entries are allowed in routers FR map tables. No subinterfaces are allowed. No broadcasting is allowed over Frame Relay PVCs. Do not use broadcast parameter in FR maps. Note however you will run EIGRP over FR so some adjustments will need to be done. Do not forget to map spoke IP addresses and your local IP addresses on FR interfaces or you will not fulfill all IP addresses must be reachable requirement.! R1 int s2/0 encap frame ietf ip add 10.0.0.1 255.255.255.0 frame map ip 10.0.0.1 104 frame map ip 10.0.0.2 104 frame map ip 10.0.0.4 104 no frame inverse no shu! R2 int s2/0 encap frame ietf ip add 10.0.0.2 255.255.255.0 frame map ip 10.0.0.1 204 frame map ip 10.0.0.2 204 frame map ip 10.0.0.4 204 no frame inverse no shu! R3 no config required! R4 int s2/0 encap frame ietf ip add 10.0.0.4 255.255.255.0 frame map ip 10.0.0.1 401 frame map ip 10.0.0.2 402 frame map ip 10.0.0.4 402 no frame inverse no shu
Tasks - page 1 EIGRP (3p): Configure EIGRP AS 1 to run on all physical links. Use minimum network commands necessary FR cloud needs split horizon for EIGRP on R4 disabled (on interface, not in router eigrp config mode) and neighbor commands on each router. Later you will configure 10.X.X.X/24 networks, but these must not be included in EIGRP. On each BGP router create loopback 0 interface. Assign this interface X.X.X.X/32 ip address. X is router number. Note the subnet mask is /32. If you don t configure these tasks exactly, you will loose points!!! Redistribute loopback 0 routes into EIGRP as external. Redistribute command in EIGRP needs metric keyword. Also add route-map where you will match only loopback 0 interface. No other subnets should be routed via EIGRP. Beware last BGP section.! R1 int lo0 ip add 1.1.1.1 255.255.255.255 router ei 1 net 10.0.0.0 0.0.255.255 nei 10.0.0.4 s2/0 red con route-map LO0 route-map LO0 ma int lo0! R2 int lo0 ip add 2.2.2.2 255.255.255.255 router ei 1 net 10.0.0.0 0.0.255.255 nei 10.0.0.4 s2/0 red con route-map LO0 route-map LO0 ma int lo0! R3 router ei 1 net 10.0.0.0 0.0.255.255! R4 int lo0 ip add 4.4.4.4 255.255.255.255 router ei 1 net 10.0.0.0 0.0.255.255 nei 10.0.0.1 s2/0 nei 10.0.0.2 s2/0 red con route-map LO0 route-map LO0 ma int lo0 int s2/0 no ip split-horizon eigrp 1
Tasks - page 1 Place R1 and R2 in AS 12. Place R4 in AS 4. Configure each BGP router with loopback 0 ip address as BGP router ID. Make sure this router ID will not change even in case of router reload. Use bgp router-id command under router bgp config mode. Configure BGP peerings in AS 12 using loopback 0 interfaces. You need also neighbor update-source command. Notice this loopback is also redistributed into EIGRP.! R1 bgp router-id 1.1.1.1 nei 2.2.2.2 remot 12 nei 2.2.2.2 updat lo0 nei 2.2.2.2 next-hop-s! R2 bgp router-id 2.2.2.2 nei 1.1.1.1 remot 12 nei 1.1.1.1 updat lo0 nei 1.1.1.1 next-hop-s! R3 no config required! R4 router bgp 4 bgp router-id 4.4.4.4
Tasks - page 1 Configure BGP peerings between AS 12 and AS 4 using loopback 0 interfaces. Use minimum neighbor commands necessary. You need neighbor ebgp-multihop as well as neighbor update-source and reachable loopback 0 interfaces (here this is fulfilled by redistribution to EIGRP). Minimum neighbor commands means BGP peer-groups. Protect these sessions using MD5 with password CCIE-3. Use neighbor password command.! R1 nei 4.4.4.4 remot 4 nei 4.4.4.4 updat lo0 nei 4.4.4.4 ebgp nei 4.4.4.4 pass CCIE-3! R2 nei 4.4.4.4 remot 4 nei 4.4.4.4 updat lo0 nei 4.4.4.4 ebgp nei 4.4.4.4 pass CCIE-3! R3 no config required! R4 router bgp 4 nei EBGP peer-g nei EBGP remot 12 nei EBGP updat lo0 nei EBGP ebgp nei EBGP pass CCIE-3 nei EBGP max 150 80 nei 1.1.1.1 peer EBGP nei 2.2.2.2 peer EBGP
Tasks - page 2 On each BGP router create loopback 1 interface. Assign this interface 10.X.X.X/24 ip address. X is router number. Import loopback 1 routes in AS 12 with Origin attribute of IGP. Do not use network command to accomplish this. Redistribute command with route-map where you set origin attribute to IGP. In AS 4 import loopback 1 route on R4 with origin Incomplete. Do not use redistribute command to accomplish this. Network command with route-map where you set origin attribute to incomplete.! R1 int lo1 ip add 10.1.1.1 255.255.255.0 red con route-map LO1 route-map LO1 ma int lo1 set origin IGP! R2 int lo1 ip add 10.2.2.2 255.255.255.0 red con route-map LO1 route-map LO1 ma int lo1 set origin IGP! R3 no config required! R4 int lo1 ip add 10.4.4.4 255.255.255.0 router bgp 4 net 10.4.4.0 mask 255.255.255.0 route-map LO1 route-map LO1 set origin incomplete
Tasks - page 2 Configure R2 so that R1 prefers R2 as next hop toward 10.4.4.0/24. Configure R4 so that you achieve symmetric routing.! R1 no config required! R2 ip pref R4 p 10.4.4.0/24 route-map R4 p 10 ma ip add pref R4 set local-pref 150 route-map R4 p 20! R3 no config required! R4 ip pref R1 p 10.1.1.0/24 route-map R1 p 10 ma ip add pref R1 set local-pref 150 route-map R1 p 20 nei 1.1.1.1 route-map R4 out router bgp 4 nei 2.2.2.2 route-map R1 in
Tasks - page 2 Make sure loopback 1 routes are reachable even if Ethernet link between R1 and R2 fails. Configure PBR on R3. Other way will be to redistribute, but you will not accomplish the requirement that no other subnets should be routed via EIGRP! R1 no config required! R2 no config required! R4 no config required! R3 access-list 111 p ip 10.1.1.0 0.0.0.255 10.2.2.0 0.0.0.255 access-list 111 p ip 10.1.1.0 0.0.0.255 10.4.4.0 0.0.0.255 access-list 122 p ip 10.4.4.0 0.0.0.255 10.1.1.0 0.0.0.255 access-list 122 p ip 10.2.2.0 0.0.0.255 10.1.1.0 0.0.0.255 route-map FROM-R1 ma ip add 111 set ip next-hop 10.0.23.2 route-map TO-R1 ma ip add 122 set ip next-hop 10.0.13.1 int e0/0 ip policy route-map FROM-R1 int e1/0 ip policy route-map TO-R1