Lab Objective:
The focus of this lab is to understand BGP implementation and configuration in Cisco IOS routers. Additional technologies include route filtering and path control.
Lab Topology:
The lab network topology is illustrated below:
|
IMPORTANT NOTE If you are using the www.howtonetwork.net racks, please bring up the LAN interfaces connected to the routers by issuing the no shutdown command on the connected switches. If you are using a home lab with no Switches, you can bring up the LAN interfaces using the following configurations on your routers: interface fastethernet 0/0 no keepalive loopback no shutdown Alternately, you can simply connect the interfaces to a hub or switch if you have one available in your own lab. |
Task 1
Configure hostnames and IP addressing on all routers as illustrated in the network topology.
Task 2
Configure BGP as illustrated in the topology. R1 will peer with R2 and R3. R2 will peer with R1 and R3. R3 will peer with R1, R2 and R4. R4 will peer only with R3. The routers should all use their physical interface addresses for BGP peering. Verify your configuration.
Task 3
Advertise the 150.x.x.x LAN subnets on all routers via BGP. These should be injected using the network command on all routers. Verify that all routers’ LAN subnets can ping every other routers LAN subnet. Use an extended ping to perform this verification.
Task 4
Configure BGP so that R1 prefers the path via R2 to reach the 150.4.4.0/24 subnet. You are NOT allowed to make any changes on R1 or R2 when completing this task. Ensure that when R2 is down, R1 can still reach the 150.4.4.0/24 subnet. Verify your configuration using the appropriate commands and simulating a R2 failure.
Task 5
Configure the following Loopback interfaces on R1:
Loopback 192: IP Address 192.1.1.1/32 Loopback 193: IP Address 193.1.1.1/32
Advertise the 192.1.1.1/32 subnet only to R2. Ensure that this is NOT re-advertised to R3. Next, advertise the 193.1.1.1/32 subnet only to R3. Ensure that this is NOT re-advertised to R2 or R4.
Task 6
Configure BGP in such a way that R4 can reach the 192.1.1.1/32 and 193.1.1.1/32 from its local LAN subnet. You are allowed to configure on R1 to complete this task; however, do NOT modify the existing configuration. You are NOT allowed to configure any static routes when completing this task. Ensure that R4 can always reach these prefixes even if the R1-R3 or R2-R3 link is down. Verify your configuration by pinging from the 150.4.4.0/24 subnet to the 193.1.1.1/32 host address on R1.