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

Advertising a Forwarding Adjacency Using OSPF

You can allow other routers to dynamically signal paths over a forwarding adjacency LSP by configuring OSPF. This configuration is optional.

If you configure OSPF to advertise a forwarding adjacency LSP, the LSP is added to the traffic engineering database on each router in the traffic engineering domain. Because the forwarding adjacency LSP is unidirectional, the corresponding traffic engineering link (forwarding adjacency) is also unidirectional. The forwarding adjacency LSP appears as a standard traffic engineering database half-link to all routers in the traffic engineering domain.

CSPF performs a bidirectional link check to ensure that traffic can flow in both directions. CSPF checks for a reverse link, either the exact reverse forwarding adjacency or another reverse link. If there is no reverse link from the forwarding adjacency LSP egress router to the forwarding adjacency LSP ingress router, the CSPF check fails.

CSPF might find another parallel reverse link. However, the LSP cannot function properly over the forwarding adjacency unless you have explicitly configured a corresponding forwarding adjacency LSP to handle the traffic flowing in the opposite direction on the forwarding adjacency LSP egress router.

To advertise the traffic engineering properties of a forwarding adjacency to a specific peer router, include the peer-interface statement:




peer-interface peer-interface-name {

dead-interval seconds;

disable;

hello-interval seconds;

retransmit-interval seconds;

transit-delay seconds;
}

You can configure this statement at the following hierarchy levels:

[edit logical-systems logical-system-name protocols ospf area area-name]
[edit protocols ospf area area-name]

For more information on how to configure the peer-interface statement, see Configuring Peer Interfaces in RSVP and OSPF.

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