[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring OSPF Passive Traffic Engineering Mode

Ordinarily, interior routing protocols such as OSPF are not run on links between ASs. 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 AS. This information is not normally included either in the 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 in the traffic engineering database. OSPF TE 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 ASs.

To configure OSPF passive mode for traffic engineering on an inter-AS interface, include the traffic-engineering statement at the [edit protocols ospf area area-id interface interface-name passive] hierarchy level:



[edit protocols ospf area area-id interface interface-name passive]

traffic-engineering {
remote-node-id address /* IP address
at far end of inter-AS link *
}

For more information, see the JUNOS MPLS Applications Configuration Guide.

[Contents] [Prev] [Next] [Index] [Report an Error]