I thought the idea behind the subcommand "absolute" was that all prefixes behind the tunnel would be given this metric?
interface Tunnel1
ip unnumbered Loopback0
tunnel destination 4.4.4.4
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng autoroute metric absolute 10
tunnel mpls traffic-eng path-option 5 explicit name TEST
no routing dynamic
R2#sh ip route 4.4.4.4
Routing entry for 4.4.4.4/32
Known via "ospf 1", distance 110, metric 11, type intra area
Last update from 4.4.4.4 on Tunnel1, 00:14:56 ago
Routing Descriptor Blocks:
* 4.4.4.4, from 4.4.4.4, 00:14:56 ago, via Tunnel1
Route metric is 11, traffic share count is 1
R2#sh ip route 8.8.8.8
Routing entry for 8.8.8.8/32
Known via "ospf 1", distance 110, metric 21, type intra area
Last update from 4.4.4.4 on Tunnel1, 00:15:02 ago
Routing Descriptor Blocks:
* 4.4.4.4, from 8.8.8.8, 00:15:02 ago, via Tunnel1
Route metric is 21, traffic share count is 1
I was expecting both prefixes to have a cost of 10.
If i remove the absolute and just have metric i get the same result.
interface Tunnel1
ip unnumbered Loopback0
tunnel destination 4.4.4.4
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng autoroute metric 10
tunnel mpls traffic-eng path-option 5 explicit name TEST
no routing dynamic
R2#sh ip route 4.4.4.4
Routing entry for 4.4.4.4/32
Known via "ospf 1", distance 110, metric 11, type intra area
Last update from 4.4.4.4 on Tunnel1, 00:01:23 ago
Routing Descriptor Blocks:
* 4.4.4.4, from 4.4.4.4, 00:01:23 ago, via Tunnel1
Route metric is 11, traffic share count is 1
R2#sh ip route 8.8.8.8
Routing entry for 8.8.8.8/32
Known via "ospf 1", distance 110, metric 21, type intra area
Last update from 4.4.4.4 on Tunnel1, 00:01:25 ago
Routing Descriptor Blocks:
* 4.4.4.4, from 8.8.8.8, 00:01:25 ago, via Tunnel1
Route metric is 21, traffic share count is 1
So what exactly is the absolute subcommand doing for me?