Tag :: SR Policy

Segment Routing Traffic Engineering Policy (SR-TE) aka SR Policy makes use of Segment Routing (SR) to allow a headend to steer traffic along any path without maintaining per flow state in every node. A headend steers traffic into an “SR Policy”. Class Based Forwarding (CBF) for SR-TE is a means for steering IP traffic into an SR Policy based on the ingress DSCP values. This mechanism is described in the section on Per-Flow Steering in the Segment Routing Policy Architecture Internet draft.

Class Based Forwarding (CBF) is a means for steering IP traffic into colored tunnels based on the ingress DSCP values. CBF may be used with SR-TE Policy, RSVP-TE or Flex-Algo colored tunnels.

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 to steer traffic along any path without maintaining per flow state in every node. A headend steers traffic into an “SR Policy”. EOS 4.21.0F adds support for SR Policy for the MPLS dataplane (SR-MPLS) for Type-1 SR Policy segments with BGP and locally configured policies as sources of SR Policies on Arista’s 7500, 7280 families of switches.

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