cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1951
Views
0
Helpful
2
Replies

BGP advertised-routes MED INFO

philippe_seror
Level 1
Level 1

Hello,

I currently have two routers within the same AS.

Those two routers have IBGP session with one (the same) ISP router.

In the objective to control all routes announcement i have implemented rout-maps in&out with the ISP router to apply MED 100 on my primary router and MED 200 on my secondary router. (in+out)

Would somebody be able do confirm me why i cannot see the metric applied to the ISP router using the command "sh ip bgp neighbors x.x.x.x advertised-routes" ?

it seems the command shows only local metric instead of advertised metric.

Thank you in advance

Attached the schema

 

 

1 Accepted Solution

Accepted Solutions

jmperlewitz
Level 1
Level 1

Hello,

 

You will not see the metric being advertised when you run the "show ip bgp neigh x.x.x.x advertised-routes" .  This is just the pure routes that you are sending your ISP before any policies are applied.  You would have to have your ISP verify the metric from their end.

 

For example:

Here are my advertised-routes:

Network         Next Hop Metric LocPrf Weight Path
*> 1.1.1.1/32 0.0.0.0           32768             i

 

Here is my policy:

route-map SET-COMM permit 10
set metric 200

 

Here is my BGP on the remote end showing the metric:

BGP routing table entry for 1.1.1.1/32, version 23333
Paths: (1 available, best #1, table default)
Advertised to update-groups:
1 3
Refresh Epoch 2
65498
10.232.1.29 from 10.232.1.29 (99.0.0.1)
Origin IGP, metric 200, localpref 100, valid, external, best

 

 

Also, you may want to consider as-prepend rather than MED.  MED is not truly effective unless the ISP has deterministic-med enabled.

 

Hope this helps.

 

View solution in original post

2 Replies 2

jmperlewitz
Level 1
Level 1

Hello,

 

You will not see the metric being advertised when you run the "show ip bgp neigh x.x.x.x advertised-routes" .  This is just the pure routes that you are sending your ISP before any policies are applied.  You would have to have your ISP verify the metric from their end.

 

For example:

Here are my advertised-routes:

Network         Next Hop Metric LocPrf Weight Path
*> 1.1.1.1/32 0.0.0.0           32768             i

 

Here is my policy:

route-map SET-COMM permit 10
set metric 200

 

Here is my BGP on the remote end showing the metric:

BGP routing table entry for 1.1.1.1/32, version 23333
Paths: (1 available, best #1, table default)
Advertised to update-groups:
1 3
Refresh Epoch 2
65498
10.232.1.29 from 10.232.1.29 (99.0.0.1)
Origin IGP, metric 200, localpref 100, valid, external, best

 

 

Also, you may want to consider as-prepend rather than MED.  MED is not truly effective unless the ISP has deterministic-med enabled.

 

Hope this helps.

 

Hi thank you for the confirmation,

It would be great if such info would be available.

Maybe it will be feature request:)

Have a nice day

Kind regards
Philippe