OSPF TE Extension

To help provide traffic engineering and MPLS with information about network topology and loading, extensions have been added to the OSPF implementation. When traffic engineering is enabled on the routing device, traffic engineering support for OSPF can be enabled as well, so that the shortest-path-first (SPF) algorithm takes into account the various label-switched paths (LSPs) configured under MPLS and configures OSPF to generate opaque link-state advertisements (LSAs) that carry traffic engineering parameters. The parameters are used to populate the traffic engineering database. The traffic engineering database is used exclusively for calculating explicit paths for the placement of LSPs across the physical topology. The Constrained Shortest Path First (CSPF) algorithm uses the traffic engineering database to compute the paths that MPLS LSPs take. RSVP uses this path information to set up LSPs and to reserve bandwidth for them. Specifically, the following OSPF traffic engineering extensions are added through this feature: * advertise-unnumbered-interfaces-(OSPFv2 only) Advertises the link-local identifier in the link-local traffic engineering LSA packet. * credibility-protocol-preference-(OSPFv2 only) Assigns a credibility value to OSPF routes in the traffic engineering database. * ignore-lsp-metrics-Ignores RSVP LSP metrics in OSPF traffic engineering shortcut calculations or when you configure LDP over RSVP LSPs. * multicast-rpf-routes-(OSPFv2 only) Installs unicast IPv4 routes (not LSPs) in the multicast routing table (inet.2) for multicast reverse-path forwarding (RPF) checks. * no-topology-(OSPFv2 only) To disable the dissemination of link-state topology information. * shortcuts-Configures IGP shortcuts, which allows OSPF to use an LSP as the next hop as if it were a logical interface from the ingress routing device to the egress routing device. * lsp-metric-info-summary-Advertises the LSP metric in summary LSAs to treat the LSP as a link.