Tag :: Traffic Engineering

The BGP-LS extension to be obsoleted allows IGP (OSPF/IS-IS) link state database information to be injected into BGP. This is typically used in deployments where some external component, (like a controller or Path Computation Engine) can do centralized path computations by learning the entire IGP topology through BGP-LS. The controller can then communicate the computed paths based on the BGP-LS updates to the head end device in the network. 

This feature implements RFC6119, which allows the extension of IS IS protocol to carry IPv6 Traffic Engineering

Traffic Engineering (TE) provides a mechanism to network administrators to control the path that a data packet takes, bypassing the standard routing model which uses routes along the shortest path. Traffic engineered paths are generally computed on the head-end routers of the topology based on various constraints (e.g. minimum bandwidth, affinity) configured for those paths and attributes (e.g available bandwidth, color) received from devices in the network topology. 

Multipath color is a new multicast multipath mode for controlling PIM RPF selection. In the default multipath

OSPF supports all of RFC3630 and parts of RFC4203. When configured, OSPF generates the following information in

This feature adds support to interface traffic policies for routing matched unicast IPv4 or IPv6 traffic which ingresses on L3 interfaces according to the routing table of a secondary VRF.

Bidirectional Forwarding Detection (BFD) is a protocol that provides low-overhead, short-duration detection of failures of arbitrary paths between two systems.

Segment Routing Traffic Engineering Policy (SR TE) aka SR Policy makes use of Segment Routing (SR) to allow a headend

Segment Routing Traffic Engineering Policy (SR TE) aka SR Policy makes use of Segment Routing (SR) to allow a headend