Routing

I have a very basic configuration and am testing some BGP metrics. I am currently testing Multi-Exit-Discrminators.

3 vMX systems running Junos: 18.2R1.9.

1 x MX in AS110 and 2 x MX in AS100.

MX 1 has 2 eBGP connections. one to MX2 and one to MX3.

I have configured a basic route that is being advertised correctly and is utilising the lowest RID, which when all other attributes are equal, is the correct default for the BGP route algortithm.

Now the route for the prefix is utilising, let's say MX2 from MX1 and I want to change it to use MX3 instead. So rather than an exact match on the prefix, I made the metric (MED) to be 50 for all routes to MX2 which should now force the algorithm to utilise MX3. However, this is not occuring and when checking the route detail I am not seeing a metric marker in the readout. I also included an accept for the metrics to be used and accepted within the group.

Here is the very basic config:

set policy-options policy-statement set-med term prefer-link1 then metric 50
set policy-options policy-statement set-med term prefer-link1 then accept

set protocols bgp group R2-AS100 export set-med

The output of "show route <prefix> detail" should show the metric being used as per the following:

Metric: 50

But nothing appears. 

Is there something that stops the MED (Metric) from being used on MX series systems? There should not be.

Hi,

If the policy is configured on MX1, please change it to an import policy ( set protocols bgp group R2-AS100 import set-med)

Regards

I have a very basic configuration and am testing some BGP metrics. I am currently testing Multi-Exit-Discrminators.

3 vMX systems running Junos: 18.2R1.9.

1 x MX in AS110 and 2 x MX in AS100.

MX 1 has 2 eBGP connections. one to MX2 and one to MX3.

I have configured a basic route that is being advertised correctly and is utilising the lowest RID, which when all other attributes are equal, is the correct default for the BGP route algortithm.

Now the route for the prefix is utilising, let's say MX2 from MX1 and I want to change it to use MX3 instead. So rather than an exact match on the prefix, I made the metric (MED) to be 50 for all routes to MX2 which should now force the algorithm to utilise MX3. However, this is not occuring and when checking the route detail I am not seeing a metric marker in the readout. I also included an accept for the metrics to be used and accepted within the group.

Here is the very basic config:

set policy-options policy-statement set-med term prefer-link1 then metric 50
set policy-options policy-statement set-med term prefer-link1 then accept

set protocols bgp group R2-AS100 export set-med

The output of "show route <prefix> detail" should show the metric being used as per the following:

Metric: 50

But nothing appears. 

Is there something that stops the MED (Metric) from being used on MX series systems? There should not be.