Tags

,

inet.0 is the route table used for regular IGP recursion. Inet.3 is only used by BGP to resolve next-hops by default. This means that only traffic sent to destinations learned by BGP will be label-switched.

If you have a requirement that all traffic uses labeled next-hops you can move routes from inet.3 into inet.0

set protocols mpls traffic-engineering bgp-igp-both-ribs

Before

dhakacom@rt-01-mx.dhakacom.com> show route 118.179.191.6
inet.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
118.179.191.6/32 *[OSPF/10] 3d 02:49:03, metric 2
 > to 202.4.100.21 via ge-1/0/0.0
inet.3: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
118.179.191.6/32 *[LDP/9] 08:40:00, metric 1> to 202.4.100.21 via ge-1/0/0.0, Push 299936

After

dhakacom@rt-01-mx.dhakacom.com> show route 118.179.191.6
inet.0: 20 destinations, 26 routes (20 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
118.179.191.6/32 *[LDP/9] 00:05:42, metric 1
 > to 202.4.100.21 via ge-1/0/0.0, Push 299936
 [OSPF/10] 00:06:34, metric 2
 > to 202.4.100.21 via ge-1/0/0.0
inet.3: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
118.179.191.6/32 *[LDP/9] 00:02:37, metric 1
 > to 202.4.100.21 via ge-1/0/0.0, Push 299936