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

Configuring OSPF Passive TE 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 EBGP reachability messages or in 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 (TED).

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



passive {


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


}

OSPF must be properly configured on the router. The following example configures the inter-AS link so-1/1/0 to distribute traffic engineering information with OSPF within the AS. The local IP address on the link is 192.168.207.1 and the remote address is 192.168.207.2.



[edit protocols ospf area 0.0.0.0]
interface so-1/1/0 {


unit 0 {


passive {


traffic-engineering {
remote-node-id 192.168.207.2;
}


}




family inet {
address 192.168.207.1;
}


}


}

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