Equipment List

Part II

Section VIII: BGP Configuration

1. R1, R2, and R3 are in autonomous system 2001. R5 is in autonomous system 65001. Configure an EBGP peer from R2 to 192.128.128.1, which is in autonomous system 2010. Configure an EBGP peer from R5 to R2.

2. Configure IBGP from R2 to R1 and R1 to R3; do not configure a peer R2 to R3. Ensure that all BGP routers are receiving the routes 128.20 x. 1.0 from the backbone router.

3. Have R2 advertise the supernet of 128.200.0.0 into the rest of the lab network, R1, R2, R3, R4, R6, R7; suppress all other subnets of 128.200.0.0.

4. Have R5 advertise the 172.16.1.0/24 subnet via BGP. Advertise the routes with a metric of 75.

5. When the backbone router receives the 172.16.1.0 route, it should appear to come from AS 2011.

6. Change the BGP hello timer on R5 to be 5 minutes.

Section IX: DLSw Configuration

1. Configure a DLSw TCP peer between Ring 2 and Ring 3.

2. Configure a DLSw FST peer between Ring 1 and Ring 4.

3. Configure an additional peer between R1 and R4 so that full NetBIOS reachability will occur from Ring 3 to Ring 4, while minimizing explorer traffic.

4. Configure a TCP peer from Ring 2 to Ring 1; allow this peer to always stay up and active, even upon a loss of Frame Relay service.

5. Configure the peer of R5 to forward only frames destined toward the MAC address 3745.0001.0101.

Section X: Miscellaneous Cisco IOS Software Features

1. The 10's network on VLAN 2 of R6 should not be advertised by a routing protocol. Configure the users of this VLAN so that they can reach the entire network, without changing the IP address or advertising the subnet 10.10.10.0.

2. Configure multicast routing on R1, R3, and R6. R6 will join the multicast group of 224.10.10.10. R6 should respond to ping s from R3 and R1.