Lab Objective:
The focus of this lab is to understand BGP implementation and configuration in Cisco IOS routers. Additional technologies tested include route reflectors, route-maps, and security.
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 interface fastethernet 0/0 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
Without using peer groups, configure internal BGP on R1, R2, R3, and R4 as follows:
- Statically configure a BGP router ID using the router number, e.g. 1.1.1.1 for R1, etc.
- All routers should peer using their physical interface addresses
- R1 should peer to R2 and R3
- R2 should peer to R1
- R3 should peer to R1 and R4
- R4 should peer to R3
- All routers should use the TCP MD5 authentication password ‘CCNP’
- BGP Hellos should be sent out every 5 seconds
- All of the BGP speakers should advertise a Hold Time of 15 seconds
- The COMMUNITIES attribute (standard) should be supported
Task 3
Advertise the 150.1.1.0/24, 150.2.2.0, and 150.3.3.0/24 subnets on R1, R2, and R3 via BGP. These prefixes must be advertised with the standard community values listed below. You are NOT allowed to redistribute these prefixes into BGP. Additionally, you are NOT allowed to use outbound or inbound route-maps when completing this task. Ensure that the community values are displayed in ASN:nn (RFC 1997 – BGP Communities Attribute) format. Verify your configuration using the appropriate commands.
- The 150.1.1.0/24: community value of 254:111
- The 150.2.2.0/24: community value of 254:222
- The 150.3.3.0/24: community value of 254:333
Task 4
Configure your network so that all 150.x.x.x/24 subnets can reach each other. You are NOT allowed to use any static routes in your solution. Additionally, you are NOT allowed to advertise or redistribute the 150.4.4.0/24 subnet into BGP on R4. Instead, consider other BGP features to complete this task. You are NOT allowed to configure R2 or R4. Additionally, you are NOT allowed to configure a dynamic routing protocol to complete this task.
Next, verify your configuration using the appropriate commands as well as the extended ping function. For example, on R1 use the extended ping function to send a ping to 150.2.2.2 sourced from 150.1.1.1, etc, etc. All pings should work when the task is completed correctly.