TOI Author :: Arpit Bansal

For MPLS forwarded traffic the tunnel destination needs to know the address-family of the payload IP/IPv6 packet to correctly parse the header. On some platforms this address-family is deduced from the address family of the Bottom of stack( BOS ) MPLS label seen by the router or by relying on the Ether Type in the Ethernet header.

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

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. IS-IS Traffic Engineering (IS-IS TE) feature extends IS-IS protocol in EOS to carry TE attributes as part of its Link State Protocol Data Units (LSPs).  Note that IS-IS in EOS only acts as a carrier for TE attributes and it is not used by any processing (e.g. SPF).

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

An IS IS router can be configured as Level 1 2 which can form adjacencies and exchange routing information with both

This feature allows to advertise routes learnt via BGP into IS IS network or IS IS routes into BGP network. It also