Hi,

The post gives a perspective on usage of Mpls traffic-Engineering bgp-igp. We all know Juniper has Different set of tables.

  1. inet.0 – igp populated
  2. inet.3 (ldp/rsvp) populated (used by BGP for Routing-Lookups)

Below is the Topology

Topology

https://www.juniper.net/documentation/en_US/junos13.3/topics/usage-guidelines/mpls-configuring-traffic-engineering-for-lsps.html

“If you configure the bgp-igp or bgp-igp-both-ribs options for the traffic-engineering statement, high-priority LSPs can supersede IGP routes in the inet.0 routing table. IGP routes might no longer be redistributed since they are no longer the active routes.”

Lets look at the routing-table without the command, a general output with both the ribs.

output_without_command

Lets add “set protocols mpls traffic-engineering bgp-igp”

output_with_command.png

The entire inet.3 has been removed and all the mpls routes got into inet.0. There is one major problem with this though, will write up in next-post

 

looking_at_tables.png

Regards

Rakesh M