Tag :: IS-IS

The BGP-LS extension 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. The mechanism used by the controller to communicate the computed TE paths is outside the scope of this document. Using BGP-LS instead of an IGP peering with the controller to distribute IGP link state information has the following advantages.

EOS 4.22.1F adds support for disabling the IS IS authentication check for received IS IS PDUs. By enabling this

IGP shortcuts enable traffic to get forwarded along traffic engineered paths computed by RSVP using a modified SPF

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

IS IS area proxy allows the creation of more scalable networks. IS IS already has hierarchical mechanisms for

This feature allows configuration of the IS IS CSNP generation interval. The default CSNP interval is 10

IS-IS flexible algorithm (FlexAlgo) provides a lightweight, simplified mechanism for performing basic traffic engineering functions within a single IS-IS area. FlexAlgo requires the cooperation of all nodes within the IS-IS area but does not require an external controller. Paths are computed by each node within the area, resulting in an MPLS switched forwarding path to nodes that are advertising a node Segment Identifier (SID) for the algorithm. The results of the path computation are placed in the colored tunnel RIB or system tunnel RIB, which simplifies route resolution.

The IS IS maximum LSP size feature provides the ability to configure the maximum LSP size that the IS IS protocol will

Level 1 2 routers set attached bit in their Level 1 LSPs to indicate their reachability to the rest of the network. A

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. 

This feature allows a user to configure multiple static adjacency SIDs for an IS IS adjacency. This feature is an

IS IS adjacency is not formed between devices with different address families configured. For example,  a router

Traffic steering enables traffic for a specified set of prefixes to get forwarded along traffic engineered paths

This feature adds support for configuring multiple area addresses in an IS-IS instance.

Topology Independent Fast Reroute, or TI-LFA, uses IS-IS SR to build loop-free alternate paths along the post-convergence path. These loop-free alternates provide fast convergence.

EOS 4.23.0F adds support for redistributing DHCPv6 routes in IS IS when using the multi agent routing protocol mode.