Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
QID:RTE227
#5
The reason your answer is wrong is because the traffic is already going across the Rtr A -> Rtr E link
They are wanting the traffic for the 10.10.1.32 network to choose the B -> F Link.

By using the neighbor statement::
neighbor 192.168.30.2 route-map as_50 out
You are just enforcing what is already in place, and that is that traffic will go through the A -> E link
Because you are setting the metric across the B -> F link with a metric of 150
While A -> E will be 0, and thus the lower metric of the two links.
And BGP prefers the lower MED over the higher MED.

Does that help??

Keep in mind that there is already (in your answer's case) the neighbor statement
RtrB# neighbor 192.168.30.2 remote-as 200
has been issued, so you are working from Rtr B, when you should be on Rtr A

neighbor 192.168.30.2 route-map as_50 out  /* This will apply a policy to a neighbor that has been setup already (going across B -> F link)
route-map as_50 permit 10  /*  Create a route map call as_50
match ip address 50  /*  Match IP address that are found in access list '50'
set metric 150  /* If an IP address match has occurred, then set its metric/MED to 150
access-list 50 permit 10.10.1.32 0.0.0.240  /* standard access list is created, named '50'
Reply


Messages In This Thread
QID:RTE227 - by angelo8888 - 03-23-2011, 09:13 AM
Re: QID:RTE227 - by sdunn96 - 03-28-2011, 01:34 PM
Re: QID:RTE227 - by sdunn96 - 03-28-2011, 01:44 PM
Re: QID:RTE227 - by angelo8888 - 04-05-2011, 06:06 AM
Re: QID:RTE227 - by sdunn96 - 04-06-2011, 06:26 PM

Forum Jump:


Users browsing this thread: 2 Guest(s)