Table of Contents
Advertisement
Router Interface Commands
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
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 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 unlabelled.
When ECMP is enabled and multiple equal-cost next-hops exit for the IGP route, the ingress IOM
will spray the packets for this route based on hashing routine currently supported for IPv4 packets.
When the preferred RTM entry corresponds to an LDP shortcut route, spraying will be performed
across the multiple next-hops for the LDP FEC. The FEC next-hops can either be direct link LDP
neighbors or T-LDP neighbors reachable over RSVP LSPs in the case of LDP-over-RSVP but not
both.
When the preferred RTM entry corresponds to a regular IP route, spraying will be performed across
regular IP next-hops for the prefix..
The no form of this command disables the resolution of IGP routes using LDP shortcuts.
Default
no ldp-shortcut
ldp-sync-timer
Syntax
ldp-sync-timer seconds
no ldp-sync-timer
Page 158
LAG the SAP/network interface exist.
7750 SR OS Router Configuration Guide
Advertisement
Table of Contents
