IP Router Configuration Command Reference
174 Router Configuration Guide
The no form of this command reverts the SAP/network interface to use per-flow, service or link hash
as configured for the service/LAG.
Default no lag-link-map-profile
Parameters link-map-profile-id — An integer from 1 to 32 that defines a unique lag link map profile on which
the LAG the SAP/network interface exist.
lag-per-link-hash
Syntax lag-per-link-hash class {1 | 2 | 3} weight [1..1024]
no per-link-hash
Context config>router>if
Description This command configures weight and class to this interface to be used on LAG egress when the LAG
uses weighted per-link-hash.
The no form of this command restores the default configuration.
Default no lag-per-link-hash (equivalent to weight 1 class 1)
ldp-shortcut
Syntax [no] ldp-shortcut
Context config>router
Description This command enables the resolution of IGP routes using LDP LSP across all network interfaces
participating in the IS-IS and OSPF routing protocol in the system.
When LDP shortcut is enabled, LDP populates the routing table with next-hop entries corresponding
to all prefixes for which it activated an LDP FEC. For a given prefix, two route entries are populated
in the system routing table. One route corresponds to the LDP shortcut next-hop and has an owner of
LDP. The other route is the regular IP next-hop. The LDP shortcut next-hop always has preference
over the regular IP next-hop for forwarding user packets and specified control packets over a given
outgoing interface to the route next-hop.
All user and specified control packets for which the longest prefix match in RTM yields the FEC prefix
will be forwarded over the LDP LSP.
When an IPv4 packet is received on an ingress network interface, a subscriber IES interface, or a
regular IES interface, the lookup of the packet by the ingress IOM, IMMM, or XMA will result in the
packet being sent labeled with the label stack corresponding to the NHLFE of the LDP LSP when the
preferred RTM entry corresponds to an LDP shortcut.
If the preferred RTM entry corresponds to an IP next-hop, the IPv4 packet is forwarded unlabeled.