Related Documentation
- ACX Series
- Example: Configuring OSPF Passive Traffic Engineering Mode
- M Series
- Example: Configuring OSPF Passive Traffic Engineering Mode
- MX Series
- Example: Configuring OSPF Passive Traffic Engineering Mode
- PTX Series
- Example: Configuring OSPF Passive Traffic Engineering Mode
- QFX Series
- Example: Configuring OSPF Passive Traffic Engineering Mode
- T Series
- Example: Configuring OSPF Passive Traffic Engineering Mode
OSPF Passive Traffic Engineering Mode
Ordinarily, interior routing protocols such as OSPF are not run on links between autonomous systems. However, for inter-AS traffic engineering to function properly, information about the inter-AS link—in particular, the address on the remote interface—must be made available inside the autonomous system (AS). This information is not normally included either in the external BGP (EBGP) reachability messages or in the OSPF routing advertisements.
To flood this link address information within the AS and make it available for traffic engineering calculations, you must configure OSPF passive mode for traffic engineering on each inter-AS interface. You must also supply the remote address for OSPF to distribute and include it in the traffic engineering database. OSPF traffic engineering mode allows MPLS label-switched paths (LSPs) to dynamically discover OSPF AS boundary routers and to allow routers to establish a traffic engineering LSP across multiple autonomous systems.
Related Documentation
- ACX Series
- Example: Configuring OSPF Passive Traffic Engineering Mode
- M Series
- Example: Configuring OSPF Passive Traffic Engineering Mode
- MX Series
- Example: Configuring OSPF Passive Traffic Engineering Mode
- PTX Series
- Example: Configuring OSPF Passive Traffic Engineering Mode
- QFX Series
- Example: Configuring OSPF Passive Traffic Engineering Mode
- T Series
- Example: Configuring OSPF Passive Traffic Engineering Mode

