BGP Lab 15 Control Inbound traffic w BGP Metric (CCNP Level)

Previous Next

Download Lab: GNS3

Image requirements:

 Cisco IOSv        (vios-adventerprisek9-m.vmdk.SPA.156-2.T)


Introduction:
Due to the capacity of the link between the routers ER1 and ISP1, it is necessary to accept incoming traffic to AS250 from AS101 via ER2 connection, leaving this link as a backup. Implement a routing policy that will change the way AS101 sends packets to AS250. You will configure BGP MED, the lowest is better, you need to influence router ISP1 to route all traffic destined to network 20.0.0.0/20 via the link to ER2.


Lab tasks:

1. Verify which link does router ISP1 use to reach AS250's prefix, also check the metric parameters for this prefix.

2. Verify that router ER1 does not have any outbound routing policy placed. 

3. Configure prefix-list defining routes originating in AS250 on the router ER1.

4. Configure route-map to match the prefix-list specified in the previous step and set metric to 200, router ER1.

5. Apply this route-map to bgp neighbor 50.0.0.100 in the outbound direction. 

6. Clear bgp session to that peer and verify the results of route policing.

Configuration example:

!
ER1(config)#ip prefix-list LOCAL_PRX permit 20.0.0.0/20

!
ER1(config)#route-map SET_METRIC permit  10
ER1(config-route-map)#match  ip address  prefix-list LOCAL_PRX
ER1(config-route-map)#set metric 200
ER1(config-route-map)#exit

!

ER1(config)#router bgp 250
ER1(config-router)#neighbor 50.0.0.100 route-map SET_METRIC out
ER1(config-router)#exit

Verify:
ER1# show ip bgp
ER1# show route-map
ER1# show run | section bgp


Topology: