l Commands – Part I

Context

[Tree] (config>service>vpls>spoke-sdp l2pt-termination)

[Tree] (config>service>template>vpls-sap-template l2pt-termination)

[Tree] (config>service>vpls>sap l2pt-termination)

Full Context

configure service vpls spoke-sdp l2pt-termination

configure service template vpls-sap-template l2pt-termination

configure service vpls sap l2pt-termination

Description

This command enables Layer 2 Protocol Tunneling (L2PT) termination on a specified SAP or spoke-SDP. L2PT termination is supported only for STP BPDUs. PDUs of other protocols are discarded.

This feature can be enabled only if STP is disabled in the context of the specified VPLS service.

The no form of this command reverts to the default.

Default

no l2pt-termination

Parameters

cdp

Specifies the Cisco discovery protocol

dtp

Specifies the dynamic trunking protocol

pagp

Specifies the port aggregation protocol

stp

Specifies all spanning tree protocols: stp, rstp, mstp, pvst (default)

udld

Specifies unidirectional link detection

vtp

Specifies the virtual trunk protocol

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>pw-template l2pt-termination)

Full Context

configure service pw-template l2pt-termination

Description

This command enables Layer 2 Protocol Tunneling (L2PT) termination on a given SAP or spoke SDP. L2PT termination will be supported only for STP BPDUs. PDUs of other protocols will be discarded.

This feature can be enabled only if STP is disabled in the context of the given VPLS service.

Default

no l2pt-termination

Parameters

cdp

Specifies the Cisco discovery protocol.

dtp

Specifies the dynamic trunking protocol.

pagp

Specifies the port aggregation protocol.

stp

Specifies all spanning tree protocols: stp, rstp, mstp, pvst (default).

udld

Specifies unidirectional link detection.

vtp

Specifies the virtual trunk protocol.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>redundancy>multi-chassis>peer>sync l2tp)

Full Context

configure redundancy multi-chassis peer sync l2tp

Description

This command enables L2TP.

The no form of this command disables L2TP.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>redundancy>mc>peer>mcr l3-ring)

Full Context

configure redundancy multi-chassis peer mc-ring l3-ring

Description

This command configures a Layer 3 multi-chassis ring.

The no form of this command reverts to the default.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>load-balancing l4-load-balancing)

Full Context

configure system load-balancing l4-load-balancing

Description

This command configures system-wide Layer 4 load balancing. The configuration at the system level can enable or disable load balancing based on Layer 4 fields. If enabled, the Layer 4 source and destination port fields will be included in hashing calculation for TCP/UDP packets.

The hashing algorithm addresses finer spraying granularity where many hosts are connected to the network.

To address more efficient traffic distribution between network links (forming a LAG group), a hashing algorithm extension takes into account L4 information (that is, src/dst L4-protocol port).

The hashing index can be calculated according to the following algorithm:

Example:

    — If [(TCP or UDP traffic) & enabled] 
        — hash (TCP/UDP ports, IP addresses) 
    — else if (IP traffic) 
        — hash (IP addresses) 
    — else 
        — hash (MAC addresses)
    — endif

This algorithm will be used in all cases where IP information in per-packet hashing is included (refer to "Traffic Load Balancing Options" in the 7705 SAR Gen 2 Interface Configuration Guide). However, the Layer 4 information (TCP/UDP ports) will not be used for fragmented packets.

Default

no l4-load-balancing

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>security>mgmt-access-filter>ip-filter>entry l4-src-port)

[Tree] (config>system>security>mgmt-access-filter>ipv6-filter>entry l4-src-port)

Full Context

configure system security management-access-filter ip-filter entry l4-src-port

configure system security management-access-filter ipv6-filter entry l4-src-port

Description

This command configures a destination TCP or UDP port number or port range for a management access filter match criterion.

The no form of this command reverts to the default values.

Default

no l4-src-port

Parameters

port

Specifies the destination TCP or UDP port number as a match criterion.

Values

1 to 65535

Default

6 (exact match)

mask

Specifies the mask used to select a range of source port numbers. Format Styles to Configure Mask lists the format styles to configure the 16-bit mask.

Table 1. Format Styles to Configure Mask

Format Style	Format Syntax	Example
Decimal	DDDDD	63488
Hexadecimal	0xHHHH	0xF800
Binary	0bBBBBBBBBBBBBBBBB	0b1111100000000000

To select a range from 1024 up to 2047, specify 1024 and 0xFC00 for port and mask, respectively.

Values

1 to 65535 (decimal)

Default

65535 (exact match)

Platforms

7705 SAR Gen 2

Context

[Tree] (debug>router>ldp>peer>packet label)

Full Context

debug router ldp peer packet label

Description

This command enables debugging for LDP Label packets.

The no form of the command disables the debugging output.

Parameters

detail

Displays detailed information.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp label-allocation)

Full Context

configure router bgp label-allocation

Description

This commands enables the context to configure the allocation of MPLS labels to specific BGP routes.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>bgp>multi-path label-ipv4)

Full Context

configure service vprn bgp multi-path label-ipv4

Description

This command sets ECMP multipath parameters that apply only to the label unicast IPv4 address family.

When multipath is enabled, traffic to the destination is load-shared across a set of paths (BGP routes) that the BGP decision process considers equal to the best path. The distribution of traffic over the multiple paths may or may not be equal. The distribution is based on weights derived from the Link Bandwidth Extended Community.

For more information about the criteria a non-best route must meet to qualify as a multipath, see "BGP route installation in the route table” in the 7705 SAR Gen 2 Unicast Routing Protocols Guide.

The no form of this command removes label-IPv4-specific overrides.

Default

no label-ipv4

Parameters

max-paths

Specifies the maximum number of multipaths per prefix or NLRI. Setting this value to 1 disables multipath. This limit only applies if neither the ebgp-max-paths limit nor the ibgp-max-paths limit apply.

Values

1 to 64

ebgp-max-paths

Specifies the maximum number of multipaths per prefix or NLRI when the best path is an EBGP learned route. If the ebgp option is configured, this value overrides the max-paths limit. If the best path is an EBGP learned route and this value is set to 1, multipath is disabled.

Values

1 to 64

ibgp-max-paths

Specifies the maximum number of multipaths per prefix or NLRI when the best path is an IBGP learned route. If the ibgp option is configured, this value overrides the max-paths limit. If the best path is an IBGP learned route and this value is set to 1, multipath is disabled.

Values

1 to 64

restrict same-neighbor-as

Specifies that the non-best path must have the same neighbor AS in its AS path as the best path.

restrict exact-as-path-as

Specifies that the non-best path must have the same AS path as the best path.

unequal-cost

Instructs BGP to ignore differences in the next-hop cost only when determining eligible multipaths.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>group>neighbor>add-paths label-ipv4)

[Tree] (config>router>bgp>group>add-paths label-ipv4)

[Tree] (config>router>bgp>add-paths label-ipv4)

Full Context

configure router bgp group neighbor add-paths label-ipv4

configure router bgp group add-paths label-ipv4

configure router bgp add-paths label-ipv4

Description

This command configures the add-paths capability for labeled-unicast IPv4 routes. By default, add-paths is not enabled for labeled-unicast IPv4 routes.

The maximum number of labeled-unicast paths per IPv4 prefix to send is the configured send-limit, which is a mandatory parameter. The capability to receive multiple labeled-unicast paths per prefix from a peer is configurable using the receive keyword, which is optional. If the receive keyword is not included in the command, receive capability is enabled by default.

The no form of this command disables add-paths support for labeled-unicast IPv4 routes, causing sessions established using add-paths for labeled-unicast IPv4 to go down and come back up without the add-paths capability.

Default

no label-ipv4

Parameters

send-limit

Specifies the maximum number of paths per labeled-unicast IPv4 prefix that are allowed to be advertised to add-paths peers. (The actual number of advertised routes may be less.) If the value is none, the router does not negotiate the send capability with respect to label-IPv4 AFI/SAFI. If the value is multipaths, then BGP advertises all the used BGP multipaths for each IPv4 NLRI if the peer has signaled support to receive multiple add paths. If the value is all, all valid and next-hop diverse paths for a prefix are advertised to add-paths capable peers instead of a limited number.

Values

1 to 16, none, multipaths, all

receive

Specifies the router negotiates to receive multiple labeled-unicast routes per IPv4 prefix.

none

Specifies that the router does not negotiate to receive multiple labeled-unicast routes per IPv4 prefix.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>multi-path label-ipv4)

Full Context

configure router bgp multi-path label-ipv4

Description

This command sets ECMP multipath parameters that apply only to the label IPv4 unicast address family. These settings override the values set by the maximum-paths command.

When multipath is enabled, traffic to the destination is load-shared across a set of paths (BGP routes) that the BGP decision process considers equal to the best path. The actual distribution of traffic over the multiple paths may be equal or unequal (that is, based on weights derived from the Link Bandwidth Extended Community).

The no form of this command removes label-IPv4-specific overrides.

Default

no label-ipv4

Parameters

max-paths

Specifies the maximum number of multipaths per prefix/NLRI if ebgp-max-paths or ibgp-max-paths does not apply.

Values

1 to 64

ebgp-max-paths

Specifies the maximum number of multipaths per prefix or NLRI when the best path is an EBGP learned route.

Values

1 to 64

ibgp-max-paths

Specifies the maximum number of multipaths per prefix or NLRI when the best path is an IBGP learned route.

Values

1 to 64

restrict same-neighbor-as

Specifies that the non-best path must have the same neighbor AS in its AS path as the best path.

restrict exact-as-path

Specifies that the non-best path must have the same AS path as the best path.

unequal-cost

Instructs BGP to ignore differences in the next-hop cost only when determining eligible multipaths.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>bgp>multi-path label-ipv6)

Full Context

configure service vprn bgp multi-path label-ipv6

Description

This command sets ECMP multipath parameters that apply only to the label unicast IPv6 address family.

When multipath is enabled, traffic to the destination is load-shared across a set of paths (BGP routes) that the BGP decision process considers equal to the best path. The distribution of traffic over the multiple paths may or may not be equal. The distribution is based on weights derived from the Link Bandwidth Extended Community.

For more information about the criteria a non-best route must meet to qualify as a multipath, see "BGP route installation in the route table” in the 7705 SAR Gen 2 Unicast Routing Protocols Guide.

The no form of this command removes label-IPv6-specific overrides.

Default

no label-ipv6

Parameters

max-paths

Specifies the maximum number of multipaths per prefix or NLRI. Setting this value to 1 disables multipath. This limit only applies if neither the ebgp-max-paths limit nor the ibgp-max-paths limit apply.

Values

1 to 64

ebgp-max-paths

Specifies the maximum number of multipaths per prefix or NLRI when the best path is an EBGP learned route. If the ebgp option is configured, this value overrides the max-paths limit. If the best path is an EBGP learned route and this value is set to 1, multipath is disabled.

Values

1 to 64

ibgp-max-paths

Specifies the maximum number of multipaths per prefix or NLRI when the best path is an IBGP learned route. If the ibgp option is configured, this value overrides the max-paths limit. If the best path is an IBGP learned route and this value is set to 1, multipath is disabled.

Values

1 to 64

restrict same-neighbor-as

Specifies that the non-best path must have the same neighbor AS in its AS path as the best path.

restrict exact-as-path-as

Specifies that the non-best path must have the same AS path as the best path.

unequal-cost

Instructs BGP to ignore differences in the next-hop cost only when determining eligible multipaths.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>group>add-paths label-ipv6)

[Tree] (config>router>bgp>group>neighbor>add-paths label-ipv6)

[Tree] (config>router>bgp>add-paths label-ipv6)

Full Context

configure router bgp group add-paths label-ipv6

configure router bgp group neighbor add-paths label-ipv6

configure router bgp add-paths label-ipv6

Description

This command configures the add-paths capability for labeled-unicast IPv6 routes. By default, add-paths is not enabled for labeled-unicast IPv6 routes.

The maximum number of labeled-unicast paths per IPv6 prefix to send is the configured send-limit, which is a mandatory parameter. The capability to receive multiple labeled-unicast paths per prefix from a peer is configurable using the receive keyword, which is optional. If the receive keyword is not included in the command, receive capability is enabled by default.

The no form of this command disables add-paths support for labeled-unicast IPv6 routes, causing sessions established using add-paths for labeled-unicast IPv6 to go down and come back up without the add-paths capability.

Default

no label-ipv6

Parameters

send-limit

Specifies the maximum number of paths per labeled-unicast IPv6 prefix that are allowed to be advertised to add-paths peers. (The actual number of advertised routes may be less.) If the value is none, the router does not negotiate the send capability with respect to label-IPv6 AFI/SAFI. If the value is multipaths, then BGP advertises all the used BGP multipaths for each IPv6 NLRI if the peer has signaled support to receive multiple add paths. If the value is all, all valid and next-hop diverse paths for a prefix are advertised to add-paths capable peers instead of a limited number.

Values

1 to 16, none, multipaths, all

receive

Specifies that the router negotiates to receive multiple labeled-unicast routes per IPv6 prefix.

none

Specifies that the router does not negotiate to receive multiple labeled-unicast routes per IPv6 prefix.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>multi-path label-ipv6)

Full Context

configure router bgp multi-path label-ipv6

Description

This command sets ECMP multipath parameters that apply only to the label unicast IPv6 address family. These settings override the values set by the maximum-paths command.

When multipath is enabled, traffic to the destination is load-shared across a set of paths (BGP routes) that the BGP decision process considers equal to the best path. The actual distribution of traffic over the multiple paths may be equal or unequal (that is, based on weights derived from the Link Bandwidth Extended Community).

The no form of this command removes label-IPv6-specific overrides.

Default

no label-ipv6

Parameters

max-paths

Specifies the maximum number of multipaths per prefix/NLRI if ebgp-max-paths or ibgp-max-paths does not apply.

Values

1 to 64

ebgp-max-paths

Specifies the maximum number of multipaths per prefix or NLRI when the best path is an EBGP learned route.

Values

1 to 64

ibgp-max-paths

Specifies the maximum number of multipaths per prefix or NLRI when the best path is an IBGP learned route.

Values

1 to 64

restrict same-neighbor-as

Specifies that the non-best path must have the same neighbor AS in its AS path as the best path.

restrict exact-as-path

Specifies that the non-best path must have the same AS path as the best path.

unequal-cost

Instructs BGP to ignore differences in the next-hop cost only when determining eligible multipaths.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>label-allocation label-ipv6)

Full Context

configure router bgp label-allocation label-ipv6

Description

Commands in this context configure advertised label IPv6 programming rules.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>bgp>rib-management label-ipv6)

Full Context

configure service vprn bgp rib-management label-ipv6

Description

Commands in this context configure labeled IPv6 RIB.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>next-hop-res>lbl-routes>use-bgp-routes label-ipv6-explicit-null)

Full Context

configure router bgp next-hop-resolution labeled-routes use-bgp-routes label-ipv6-explicit-null

Description

This command allows a labelled IPv6 route with the explicit-null label to be resolved by other labelled IPv6 routes with the explicit-null label, and also by unlabeled IPv4 routes and unlabeled IPv6 routes that are resolved by static routes, interface routes, or tunnels. Up to four levels of recursive resolution are supported when the top route is a labelled IPv6 route with an explicit-null label.

Regardless of setting, a labelled IPv6 route with a regular label (other than explicit-null) is never resolved by other labelled IPv6 routes.

The no form of this command disables the label-ipv6-explicit-null functionality. When disabled, a labeled IPv6 route cannot be resolved by other labeled IPv6 routes.

Default

no label-ipv6-explicit-null

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls>interface label-map)

Full Context

configure router mpls interface label-map

Description

This command is used on transit routers when a static LSP is defined. The static LSP on the ingress router is initiated using the config router mpls static-lsp lsp-name command. An in-label can be associated with either a pop or a swap action, but not both. If both actions are specified, the last action specified takes effect.

The no form of this command deletes the static LSP configuration associated with the in-label.

Parameters

in-label

Specifies the incoming MPLS label on which to match.

Values

32 to 1023

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn label-mode)

Full Context

configure service vprn label-mode

Description

This command controls the method by which service labels are allocated to routes exported by the VPRN as BGP-VPN routes. The vrf option selects service label per VRF mode while the next-hop option selects service label per next-hop mode.

The no form of this command sets the mode to the default mode of service label per VRF.

Default

no label-mode

Parameters

vrf

Selects service label per VRF mode.

next-hop

Selects service label per next-hop mode.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>bgp label-preference)

[Tree] (config>service>vprn>bgp>group label-preference)

[Tree] (config>service>vprn>bgp>group>neighbor label-preference)

Full Context

configure service vprn bgp label-preference

configure service vprn bgp group label-preference

configure service vprn bgp group neighbor label-preference

Description

This command configures the route preference for routes learned from labeled-unicast peers.

This command can be configured at three levels:

• Global level — applies to all peers

• Group level — applies to all peers in the peer-group

• Neighbor level — applies only to the specified peer

The most specific value is used.

The lower the preference, the higher the chance of the route being the active route.

The no form of this command used at the global level reverts to the default value of 170.

The no form of this command used at the group level reverts to the value defined at the global level.

The no form of this command used at the neighbor level reverts to the value defined at the group level.

Default

no label-preference

Parameters

value

Specifies the route preference value.

Values

1 to 255

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp label-preference)

[Tree] (config>router>bgp>group>neighbor label-preference)

[Tree] (config>router>bgp>group label-preference)

Full Context

configure router bgp label-preference

configure router bgp group neighbor label-preference

configure router bgp group label-preference

Description

This command configures the route preference for routes learned from labeled-unicast peers.

This command can be configured at three levels:

• Global level — applies to all peers

• Group level — applies to all peers in the peer-group

• Neighbor level — applies only to the specified peer

The most specific value is used.

The lower the preference, the higher the chance of the route being the active route.

The no form of this command used at the global level reverts to the default value of 170.

The no form of this command used at the group level reverts to the value defined at the global level.

The no form of this command used at the neighbor level reverts to the value defined at the group level.

Default

no label-preference

Parameters

value

Specifies the route preference value.

Values

1 to 255

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>ttl-propagate label-route-local)

Full Context

configure router ttl-propagate label-route-local

Description

This command configures the TTL propagation for locally generated packets which are forwarded over a BGP label route in the Global Routing Table (GRT) context.

For IPv4 and IPv6 packets forwarded using an RFC 8277 label route in the global routing instance, including 6PE, the all value of the command enables TTL propagation from the IP header into all labels in the transport label stack. The none value reverts to the default mode which disables TTL propagation from the IP header to the labels in the transport label stack. This command does not have a no version.

The TTL of the IP packet is always propagated into the RFC 8277 label itself, and this command only controls the propagation into the transport labels, for example, labels of the RSVP or LDP LSP to which the BGP label route resolves and which are pushed on top of the BGP label.

If the BGP peer advertised the implicit-null label value for the BGP label route, the TTL propagation will not follow the configuration described, but will follow the configuration to which the BGP label route resolves:

RSVP LSP shortcut:

• configure router mpls shortcut-local-ttl-propagate

LDP LSP shortcut:

• configure router ldp shortcut-local-ttl-propagate

This feature does not impact packets forwarded over BGP shortcuts. The ingress LER operates in uniform mode by default and can be changed into pipe mode using the configuration of TTL propagation for RSVP or LDP LSP shortcut listed.

Default

label-route-local none

Parameters

none

Specifies that the TTL of the IP packet is not propagated into the transport label stack.

all

Specifies that the TTL of the IP packet is propagated into all labels of the transport label stack.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>ttl-propagate label-route-transit)

Full Context

configure router ttl-propagate label-route-transit

Description

This command configures the TTL propagation for transit packets which are forwarded over a BGP label route in the Global Routing Table (GRT) context.

For IPv4 and IPv6 packets forwarded using a RFC 8277 label route in the global routing instance, including 6PE, the all value of the command enables TTL propagation from the IP header into all labels in the transport label stack. The none value reverts to the default mode which disables TTL propagation from the IP header to the labels in the transport label stack. This command does not have a no version.

The TTL of the IP packet is always propagated into the RFC 8277 label itself, and this command only controls the propagation into the transport labels, for example, labels of the RSVP or LDP LSP to which the BGP label route resolves and which are pushed on top of the BGP label.

If the BGP peer advertised the implicit-null label value for the BGP label route, the TTL propagation will not follow the configuration described, but will follow the configuration to which the BGP label route resolves.

RSVP LSP shortcut:

• configure router mpls shortcut-transit-ttl-propagate

LDP LSP shortcut:

• configure router ldp shortcut-transit-ttl-propagate

This feature does not impact packets forwarded over BGP shortcuts. The ingress LER operates in uniform mode by default and can be changed into pipe mode using the configuration of TTL propagation for the listed RSVP or LDP LSP shortcut.

Default

label-route-transit none

Parameters

none

Specifies that the TTL of the IP packet is not propagated into the transport label stack.

all

Specifies that the TTL of the IP packet is propagated into all labels of the transport label stack.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls>lsp label-stack-reduction)

[Tree] (config>router>mpls>lsp-template label-stack-reduction)

Full Context

configure router mpls lsp label-stack-reduction

configure router mpls lsp-template label-stack-reduction

Description

This command enables the label stack size reduction for a SR-TE LSP or SR-TE LSP template.

At a high level, the label stack reduction algorithm attempts to replace a segment of a computed SR-TE LSP path with the farthest node SID on that path that results in using ECMP paths with links which still comply to the TE constraints of the LSP path.

The no form of this command returns the command to its default value.

Default

no label-stack-reduction

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>ldp label-withdrawal-delay)

Full Context

configure router ldp label-withdrawal-delay

Description

This command specifies configures the time interval (in s), LDP will delay for the withdrawal of FEC-label binding it distributed to its neighbors when FEC is de-activated. When the timer expires, LDP then sends a label withdrawal for the FEC to all its neighbors. This is applicable only to LDP IPv4 prefix FECs and is not applicable to pseudowires (service FECs).

When there is an upper layer (user of LDP) which depends on LDP control plane for failover detection then label withdrawal delay and tunnel-down-damp-time options must be set to 0.

An example is PW redundancy where the primary PW doesn’t have its own fast failover detection mechanism and the node depends on LDP tunnel down event to activate the standby PW.

Default

no label-withdrawal-delay

Parameters

seconds

Specifies the time that LDP delays the withdrawal of FEC-label binding it distributed to its neighbors when FEC is de-activated.

Values

3 to 120

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>next-hop-res labeled-routes)

Full Context

configure router bgp next-hop-resolution labeled-routes

Description

Commands in this context configure labeled route options for next-hop resolution.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>lag lacp)

Full Context

configure lag lacp

Description

This command enables the LACP protocol. Per the IEEE 802.1ax standard, the Link Aggregation Control Protocol (LACP) provides a standardized means for exchanging information between Partner Systems on a link to allow their Link Aggregation Control instances to reach agreement on the identity of the Link Aggregation Group to which the link belongs, move the link to that Link Aggregation Group, and enable its transmission and reception functions in an orderly manner.

If any of the parameters are omitted, the existing configuration is preserved. The default parameter values are used if a parameter is never explicitly configured.

Default

no lacp

Parameters

mode

Specifies the mode in which LACP will operate.

Values

passive — Starts transmitting LACP packets only after receiving packets.

active — Initiates the transmission of LACP packets.

admin-key

Specifies an administrative key value to identify the channel group on each port configured to use LACP. A random key is assigned by default if a value is not specified when using classic CLI only.

Values

1 to 65535

system-id

Specifies the 48-bit system ID in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff, where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.

Values

1 to 65535

Default

32768

priority

Specifies the system priority.

Values

0 to 65535

Default

32768

Platforms

7705 SAR Gen 2

Context

[Tree] (config>lag lacp-fallback)

Full Context

configure lag lacp-fallback

Description

This command configures the LACP fallback mode. LACP fallback allows one or more designated links of an LACP-controlled LAG to go into forwarding mode if LACP is not yet operational after a configured timeout period. Links capable of forwarding traffic assume the Ethernet and IP characteristics configured for the LAG.

The no form of this command disables LACP fallback.

Default

no lacp-fallback

Parameters

mode

Keyword to specify the LACP fallback mode.

Values

static — Keyword to specify that if LACP is not operational after the timeout period, a single designated LAG member goes into forwarding mode.

individual — The individual mode is not supported.

timeout

Specifies the timeout period in seconds. The LACP link becomes active if no LACP PDUs are received within this timeout period.

Note: Timeout range depends on the configuration of the configure lag lacp-xmit-limit command.

Values

fast: 4 to 3600

slow: 90 to 3600

Default

fast: 4

Platforms

7705 SAR Gen 2

Context

[Tree] (config>lag lacp-mux-control)

Full Context

configure lag lacp-mux-control

Description

This command configures the type of multiplexing machine control to be used in a LAG with LACP in active/passive modes.

The no form of this command disables multiplexing machine control.

Default

lacp-mux-control coupled

Parameters

coupled

Specifies that TX and RX activate together.

independent

Specifies that RX activates independent of TX.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system lacp-system-priority)

Full Context

configure system lacp-system-priority

Description

This command configures the Link Aggregation Control Protocol (LACP) system priority on aggregated Ethernet interfaces. LACP allows the operator to aggregate multiple physical interfaces to form one logical interface.

Default

lacp-system-priority 32768

Parameters

lacp-system-priority

Specifies the LACP system priority.

Values

1 to 65535

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet lacp-tunnel)

Full Context

configure port ethernet lacp-tunnel

Description

This command enables LACP packet tunneling for the Ethernet port. When tunneling is enabled, the port does not process any LACP packets but tunnels them instead. The port cannot be added as a member to a LAG group.

In this context, the lacp-tunnel command is supported for Epipe and VPLS services only.

The no form of this command disables LACP packet tunneling for the Ethernet port.

Default

no lacp-tunnel

Platforms

7705 SAR Gen 2

Context

[Tree] (config>lag lacp-xmit-interval)

Full Context

configure lag lacp-xmit-interval

Description

This command specifies the interval signaled to the peer and tells the peer at which rate it should transmit.

Default

lacp-xmit-interval fast

Parameters

slow

Transmits packets every 30 seconds.

fast

Transmits packets every second.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>lag lacp-xmit-stdby)

Full Context

configure lag lacp-xmit-stdby

Description

This command enables LACP message transmission on standby links.

The no form of this command disables LACP message transmission. This command should be disabled for compatibility when using active/standby groups. This forces a timeout of the standby links by the peer. Use the no form if the peer does not implement the correct behavior regarding the lacp sync bit.

Default

lacp-xmit-stdby

Platforms

7705 SAR Gen 2

Context

[Tree] (config>redundancy>multi-chassis>peer>mc-lag lag)

Full Context

configure redundancy multi-chassis peer mc-lag lag

Description

This command defines a LAG which is forming a redundant-pair for MC-LAG with a LAG configured on the given peer. The same LAG group can be defined only in the scope of 1 peer. In order MC-LAG to become operational, all parameters (lacp-key, system-id, system-priority) must be configured the same on both nodes of the same redundant pair.

The partner system (the system connected to all links forming MC-LAG) will consider all ports using the same lacp-key, system-id, system-priority as the part of the same LAG. In order to achieve this in MC operation, both redundant-pair nodes have to be configured with the same values. In case of the mismatch, MC-LAG is kept in oper-down status.

Note that the correct CLI command to enable MC LAG for a LAG in standby-signaling power-off mode is lag lag-id [remote-lag remote-lag-id]. In the CLI help output, the first three forms are used to enable MC LAG for a LAG in LACP mode. MC LAG is disabled (regardless of the mode) for a given LAG with no lag lag-id.

Parameters

lag-id

The LAG identifier, expressed as an integer. Specifying the lag-id allows the mismatch between lag-id on redundant-pair. If no lag-id is specified it is assumed that neighbor system uses the same lag-id as a part of the specific MC-LAG. If no matching MC-LAG group can be found between neighbor systems, the individual LAGs operates as usual (no MC-LAG operation is established).

Values

1 to 800

admin-key

Specifies a 16 bit key that needs to be configured in the same manner on both sides of the MC-LAG in order for the MC-LAG to come up.

Values

1 to 65535

system-id

Specifies a 6 byte value expressed in the same notation as MAC address.

Values

xx:xx:xx:xx:xx:xx - xx [00 to FF]

remote-lag-id

Specifies the LAG ID on the remote system.

Values

1 to 800

system-priority

Specifies the system priority to be used in the context of the MC-LAG. The partner system will consider all ports using the same lacp-key, system-id, and system-priority as part of the same LAG.

Values

1 to 65535

MAC-Lsb

Configures the last 16 bit of the MAC address to be used for all traffic ingressing the MC-LAG link(s) or if use-lacp-key option is used, it will only copy the value of lacp-key (redundancy multi-chassis mc-lag lag lacp-key admin-key). The command will fail if the value is the same with any of the following configured attributes:

• Source-bmac-lsb assigned to other MC-LAG ports.

• lsb 16 bits value for the source-bmac configured at chassis or BVPLS level

  The first 32 bits will be copied from the source B-MAC of the BVPLS associated with the IVPLS for a specific IVPLS SAP mapped to the MC-LAG. The BVPLS source B-MAC can be provisioned for each BVPLS or can be inherited from the chassis PBB configuration.

Values

1 to 65535 or xx-xx or xx:xx

Platforms

7705 SAR Gen 2

Context

[Tree] (config lag)

Full Context

configure lag

Description

Commands in this context configure Link Aggregation Group (LAG) attributes.

A LAG is used to group multiple ports into one logical link. The aggregation of multiple physical links allows for load sharing and offers seamless redundancy. If one link fails, traffic is redistributed over the remaining links.

There are three possible settings for autonegotiation, as follows:

• "on” or enabled with full port capabilities advertised

• "off” or disabled where there is no autonegotiation advertisements

• "limited” where a single speed/duplex is advertised.

When autonegotiation is enabled on a port, the link attempts to automatically negotiate the link speed and duplex parameters; the configured duplex and speed parameters are ignored.

When autonegotiation is disabled on a port, the port does not attempt to autonegotiate and will only operate at the speed and duplex settings configured for the port.

If the config>port>ethernet autonegotiate limited keyword option is specified, the port will autonegotiate but only advertise the speed and duplex settings configured for the port. Use the limited mode on multi-speed gigabit ports to force gigabit operation while keeping autonegotiation is enabled for compliance with IEEE 801.3.

The system requires autonegotiation to be disabled or limited for ports in a LAG to guarantee a specific port speed.

The no form of this command deletes the LAG from the configuration. A LAG can only be deleted while the LAG is administratively shut down. Any dependencies, such as IP-Interface configurations, must be removed from the configuration before the no lag command is issued.

Parameters

lag-id

Specifies the LAG identifier, expressed as an integer.

The LAG ID ranging from 1 to 64 supports up to 64 LAG members and LAG ID above 64 supports 32 LAG members.

Values

1 to 200

lag-name

Specifies an optional LAG name, up to 27 characters.

In model-driven interfaces, the LAG name is used for configuration references and show commands. A service provider or administrator can use the defined LAG name to identify and manage LAGs within the SR OS platforms.

In the classic CLI interface, the user must assign a LAG ID to create the LAG. The LAG name is optional and, if specified, must always start with "lag-”. If a name is not specified, SR OS automatically assigns a string version of the LAG ID as "lag-<lag-id>”.

Values

lag-<23 chars max>

Platforms

7705 SAR Gen 2

Context

[Tree] (debug lag)

Full Context

debug lag

Description

This command enables debugging for LAG.

Parameters

lag-id

Specifies the link aggregation group ID.

Values

1 to 200

port-id

Specifies the physical port ID.

Values

slot/mda/port

all

Specifies to display all LAG information.

sm

Specifies to display trace LACP state machine.

pkt

Specifies to display trace LACP packets.

cfg

Specifies to display trace LAG configuration.

red

Specifies to display trace LAG high availability.

iom-upd

Specifies to display trace LAG IOM updates.

port-state

Specifies to display trace LAG port state transitions.

timers

Specifies to display trace LAG timers.

sel-logic

Specifies to display trace LACP selection logic.

mc

Specifies to display multi-chassis parameters.

mc-packet

Specifies to display the MC-LAG control packets with valid authentication were received on this system.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>nw-if lag)

Full Context

configure service vprn network-interface lag

Description

This command binds the interface to a Link Aggregation Group (LAG)

The no form of this command removes the LAG id from the configuration.

Parameters

lag-id[:encap-val]

Specifies the LAG ID.

Values

lag-id	1 to 800
encap-val	0 (for null)
	0 to 4094 (for dot1q)

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>system>bgp-evpn>eth-seg lag)

Full Context

configure service system bgp-evpn ethernet-segment lag

Description

This command configures the LAG associated with the ES.

A LAG can be associated with an ES configured with either the single-active or all-active multihoming mode. Additionally, a specified LAG can be associated to only one ES at any time.

The no form of this command removes the LAG association.

Default

no lag

Parameters

lag-id

Specifies the lag-id associated with the ES.

Values

1 to 200

Platforms

7705 SAR Gen 2

Context

[Tree] (config>vrrp>policy>priority-event lag-port-down)

Full Context

configure vrrp policy priority-event lag-port-down

Description

This command creates the context to configure Link Aggregation Group (LAG) priority control events that monitor the operational state of the links in the LAG.

The lag-port-down command configures a priority control event. The event monitors the operational state of each port in the specified LAG. When one or more of the ports enter the operational down state, the event is considered to be set. When all the ports enter the operational up state, the event is considered to be clear. As ports enter the operational up state, any previous set threshold that represents more down ports is considered cleared, while the event is considered to be set.

Multiple unique lag-port-down event nodes can be configured within the priority-event node up to the maximum of 32 events.

The lag-port-down command can reference an arbitrary LAG. The lag-id does have to already exist within the system. The operational state of the lag-port-down event will indicate:

• Set – non-existent

• Set – one port down

• Set – two ports down

• Set – three ports down

• Set – four ports down

• Set – five ports down

• Set – six ports down

• Set – seven ports down

• Set – eight ports down

• Cleared – all ports up

When the lag-id is created, or a port in lag-id becomes operationally up or down, the event operational state must be updated appropriately.

When one or more of the LAG composite ports enters the operationally down state or the lag-id is deleted or does not exist, the event is considered to be set. When an event transitions from clear to set, the set is processed immediately and must be reflected in the associated virtual router instances in-use priority value. As the event transitions from clear to set, a hold-set timer is loaded with the value configured by the events hold-set command. This timer prevents the event from clearing until it expires, damping the effect of event flapping. If the event clears and becomes set again before the hold-set timer expires, the timer is reset to the hold-set value, extending the time before another clear can take effect.

The lag-port-down event is considered to have a tiered event set state. While the priority impact per number of ports down is totally configurable, as more ports go down, the effect on the associated virtual router instances in-use priority is expected to increase (lowering the priority). When each configured threshold is crossed, any higher thresholds are considered further event sets and are processed immediately with the hold-set timer reset to the configured value of the hold-set command. As the thresholds are crossed in the opposite direction (fewer ports down then previously), the priority effect of the event is not processed until the hold-set timer expires. If the number of ports down threshold again increases before the hold-set timer expires, the timer is only reset to the hold-set value if the number of ports down is equal to or greater than the threshold that set the timer.

The event contains number-down nodes that define the priority delta or explicit value to be used based on the number of LAG composite ports that are in the operationally down state. These nodes represent the event set thresholds. Not all port down thresholds must be configured. As the number of down ports increase, the number-down ports-down node that expresses a value equal to or less than the number of down ports describes the delta or explicit priority value to be applied.

The no form of the command deletes the specific LAG monitoring event. The event can be removed at anytime. When the event is removed, the in-use priority of all associated virtual router instances must be reevaluated. The events hold-set timer has no effect on the removal procedure.

Default

no lag-port-down — No LAG priority control events are created.

Parameters

lag-id

The LAG ID that the specific event is to monitor expressed as a decimal integer. The lag-id can only be monitored by a single event in this policy. The LAG may be monitored by multiple VRRP priority control policies. A port within the LAG and the LAG ID itself are considered to be separate entities. A composite port may be monitored with the port-down event while the lag-id the port is in is monitored by a lag-port-down event in the same policy.

Values

1 to 200

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>sap>mld-snooping last-member-query-interval)

[Tree] (config>service>vpls>sap>igmp-snooping last-member-query-interval)

[Tree] (config>service>vpls>mesh-sdp>igmp-snooping last-member-query-interval)

[Tree] (config>service>vpls>spoke-sdp>igmp-snooping last-member-query-interval)

[Tree] (config>service>vpls>spoke-sdp>mld-snooping last-member-query-interval)

[Tree] (config>service>vpls>mesh-sdp>mld-snooping last-member-query-interval)

Full Context

configure service vpls sap mld-snooping last-member-query-interval

configure service vpls sap igmp-snooping last-member-query-interval

configure service vpls mesh-sdp igmp-snooping last-member-query-interval

configure service vpls spoke-sdp igmp-snooping last-member-query-interval

configure service vpls spoke-sdp mld-snooping last-member-query-interval

configure service vpls mesh-sdp mld-snooping last-member-query-interval

Description

This command configures the maximum response time used in group-specific queries sent in response to 'leave' messages, and is also the amount of time between two consecutive group-specific queries. This value may be tuned to modify the leave latency of the network. A reduced value results in reduced time to detect the loss of the last member of a group.

The configured last-member-query-interval is ignored when fast leave is enabled on the SAP or SDP.

The no form of this command reverts to the default value.

Default

last-member-query-interval 10

Parameters

tenths-of-seconds

Specifies the frequency, in tenths of a second, at which query messages are sent.

Values

1 to 50

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>pw-template>igmp-snooping last-member-query-interval)

Full Context

configure service pw-template igmp-snooping last-member-query-interval

Description

This command configures the maximum response time used in group-specific queries sent in response to 'leave’ messages, and is also the amount of time between 2 consecutive group-specific queries. This value may be tuned to modify the leave latency of the network. A reduced value results in reduced time to detect the loss of the last member of a group.

The configured last-member-query-interval is ignored when fast-leave is enabled on the SAP or SDP.

Default

last-member-query-interval 10

Parameters

interval

Specifies the frequency, in tenths of seconds, at which query messages are sent.

Values

1 to 50

Platforms

7705 SAR Gen 2

Context

[Tree] (config>saa>test latency-event)

Full Context

configure saa test latency-event

Description

Specifies that at the termination of an SAA test probe, the calculated latency event value is evaluated against the configured rising and falling latency event thresholds. SAA threshold events are generated as required.

Once the threshold (rising/falling) is crossed, it is disabled from generating additional events until the opposite threshold is crossed. If a falling-threshold is not supplied, the rising- threshold is re-enabled when it falls below the threshold after the initial crossing that generated the event.

The configuration of latency event thresholds is optional.

The no form of this command disables the latency event.

Parameters

rising-threshold threshold

Specifies a rising threshold latency value, in milliseconds. When the test run is completed, the calculated latency value is compared to the configured latency rising threshold. If the test run latency value is greater than the configured rising threshold value then an SAA threshold event is generated. The SAA threshold event is tmnxOamSaaThreshold, logger application OAM, event #2101.

Values

0 to 2147483

Default

0

falling-threshold threshold

Specifies a falling threshold latency value, in milliseconds. When the test run is completed, the calculated latency value is compared to the configured latency falling threshold. If the test run latency value is greater than the configured falling threshold value then an SAA threshold event is generated. The SAA threshold event is tmnxOamSaaThreshold, logger application OAM, event #2101.

Values

0 to 2147483

Default

0

direction

Specifies the direction for OAM ping responses received for an OAM ping test run.

Values

inbound — Monitor the value of jitter calculated for the inbound, one-way, OAM ping responses received for an OAM ping test run.

outbound — Monitor the value of jitter calculated for the outbound, one-way, OAM ping requests sent for an OAM ping test run.

roundtrip — Monitor the value of jitter calculated for the round trip, two-way, OAM ping requests and replies for an OAM ping test run.

Default

roundtrip

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>system>bgp-evpn>ethernet-segment layer-3-neighbor-synchronization)

Full Context

configure service system bgp-evpn ethernet-segment layer-3-neighbor-synchronization

Description

This command configures the Ethernet segment used to synchronize ARP and ND entries across all PEs attached to the same CE that use a single LAG.

The no form of this command disables Layer 3 ARP and ND synchronization across PEs.

Default

no layer-3-neighbor-synchronization

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>security ldap)

Full Context

configure system security ldap

Description

This command configures LDAP authentication parameters for the system.

The no form of this command de-configures the LDAP client from the SR OS.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>security>ldap>server ldap-server)

Full Context

configure system security ldap server ldap-server

Description

This command enables the LDAP server name or description.

The no form of this command disables the LDAP server name.

Parameters

server-name

Specifies the name of the server, up to 32 characters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>bgp-evpn>mpls>auto-bind-tunnel>resolution-filter ldp)

[Tree] (config>service>epipe>bgp-evpn>mpls>auto-bind-tunnel>resolution-filter ldp)

[Tree] (config>service>vprn>bgp-evpn>mpls>auto-bind-tunnel>resolution-filter ldp)

[Tree] (config>service>vprn>bgp-ipvpn>mpls>auto-bind-tunnel>resolution-filter ldp)

Full Context

configure service vpls bgp-evpn mpls auto-bind-tunnel resolution-filter ldp

configure service epipe bgp-evpn mpls auto-bind-tunnel resolution-filter ldp

configure service vprn bgp-evpn mpls auto-bind-tunnel resolution-filter ldp

configure service vprn bgp-ipvpn mpls auto-bind-tunnel resolution-filter ldp

Description

This command enables LDP for the auto-bind tunnel resolution filter.

This command instructs BGP to search for an LDP LSP with a FEC prefix corresponding to the address of the BGP next hop.

The no form of this command removes the configuration.

Default

no ldp

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router ldp)

Full Context

configure router ldp

Description

Commands in this context configure an LDP parameters.

To suspend the LDP protocol, use the shutdown command. Configuration parameters are not affected.

The no form of the command deletes the LDP protocol instance, removing all associated configuration parameters. The LDP instance must first be disabled with the shutdown command before being deleted.

Platforms

7705 SAR Gen 2

Context

[Tree] (debug>router ldp)

Full Context

debug router ldp

Description

Use this command to configure LDP debugging.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>static-route-entry>indirect>tunnel-next-hop>resolution-filter ldp)

Full Context

configure router static-route-entry indirect tunnel-next-hop resolution-filter ldp

Description

This command enables the use of LDP-sourced tunnel entries in the TTM to resolve the associated static route next-hop.

The no form of this command disables the use of LDP-sourced tunnel entries to resolve static route next hops.

Default

no ldp

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>sdp ldp)

Full Context

configure service sdp ldp

Description

This command enables LDP-signaled LSPs on MPLS-encapsulated SDPs.

In MPLS SDP configurations either one or more LSP names can be specified or LDP can be enabled. The SDP ldp and lsp commands are mutually exclusive except if the mixed-lsp-mode option is also enabled. If an LSP is specified on an MPLS SDP, then LDP cannot be enabled on the SDP. To enable LDP on the SDP when an LSP is already specified, the LSP must be removed from the configuration using the no lsp lsp-name command or the mixed-lsp-mode option is also enabled.

Alternatively, if LDP is already enabled on an MPLS SDP, then an LSP cannot be specified on the SDP. To specify an LSP on the SDP, the LDP must be disabled. The LSP must have already been created in the config>router>mpls context with a valid far-end IP address. The above rules are relaxed when the mixed-lsp option is enabled on the SDP.

Default

no ldp (disabled)

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>next-hop-resolution>labeled-routes>transport-tunnel>family>resolution-filter ldp)

[Tree] (config>router>bgp>next-hop-resolution>shortcut-tunn>family>resolution-filter ldp)

Full Context

configure router bgp next-hop-resolution labeled-routes transport-tunnel family resolution-filter ldp

configure router bgp next-hop-resolution shortcut-tunnel family resolution-filter ldp

Description

This command enables LDP tunneling for next-hop resolution and specifies the LDP tunnels in the tunnel table corresponding to /32 IPv4 FECs and /128 IPv6 FECs.

The no form of this command disables LDP tunneling for next-hop resolution.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>auto-bind-tunnel>res-filter ldp)

Full Context

configure service vprn auto-bind-tunnel resolution-filter ldp

Description

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls>lsp-template ldp-over-rsvp)

[Tree] (config>router>mpls>lsp ldp-over-rsvp)

Full Context

configure router mpls lsp-template ldp-over-rsvp

configure router mpls lsp ldp-over-rsvp

Description

This command configures an LSP so that it can be used by the IGP to calculate its SPF tree.

When the ldp-over-rsvp option is also enabled in ISIS or OSPF, the IGP provides LDP with all ECMP IP next-hops and tunnel endpoints that it considers to be the lowest cost path to its destination.

IGP provides only the endpoints which are the closest to the destination in terms of IGP cost for each IP next-hop of a prefix. If this results in more endpoints than the ECMP value configured on the router, it will further prune the endpoints based on the lowest router-id and for the same router-id, it will select lowest interface-index first.

LDP then looks up the tunnel table to select the actual tunnels to the endpoint provided by IGP and further limits the endpoint selection to the ones which are the closest to destination across all the IP next-hops provided by IGP for a prefix. For each remaining endpoint, LDP selects a tunnel in a round-robin fashion until the router ECMP value is reached. For each endpoint, only tunnels with the same lowest metric are candidates. If more than one tunnel qualifies, the selection begins with the lowest tunnel-id.

Default

ldp-over-rsvp include

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>isis ldp-over-rsvp)

Full Context

configure router isis ldp-over-rsvp

Description

This command allows LDP over RSVP processing in IS-IS.

The no form of this command disables LDP over RSVP processing.

Default

no ldp-over-rsvp

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>ospf ldp-over-rsvp)

Full Context

configure router ospf ldp-over-rsvp

Description

This command allows LDP-over-RSVP processing in this OSPF instance.

Default

no ldp-over-rsvp

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router ldp-shortcut)

Full Context

configure router ldp-shortcut

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 corresponds to the LDP shortcut next-hop and has an owner of LDP. The other one 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 forwarding engine 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 without a label.

When ECMP is enabled and multiple equal-cost next-hops exit for the IGP route, the ingress forwarding engine 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

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>static-route-entry>next-hop ldp-sync)

Full Context

configure router static-route-entry next-hop ldp-sync

Description

This command extends the LDP synchronization feature to a static route. When an interface comes back up, it is possible that a preferred static route using the interface as next-hop for a given prefix is enabled before the LDP adjacency to the peer LSR comes up on this interface. In this case, traffic on an SDP that uses the static route for the far-end address would be black-holed until the LDP session comes up and the FECs exchanged.

This option when enabled delays the activation of the static route until the LDP session comes up over the interface and the ldp-sync-timer configured on that interface has expired

Default

no ldp-sync

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>if ldp-sync-timer)

Full Context

configure router interface ldp-sync-timer

Description

This command enables synchronization of an IGP and LDP. When a link is restored after a failure, the IGP sets the link cost to infinity and advertises it. The actual value advertised in OSPF is 0xFFFF (65535). The actual value advertised in IS-IS regular metric is 0x3F (63) and in IS-IS wide-metric is 0xFFFFFE (16777214). This feature is not supported on RIP interfaces.

If an interface belongs to both IS-IS and OSPF, a physical failure will cause both IGPs to advertise an infinite metric and to follow the IGP-LDP synchronization procedures. If only one IGP bounces on this interface or on the system, then only the affected IGP advertises the infinite metric and follows the IGP-LDP synchronization procedures.

Next, an LDP Hello adjacency is brought up with the neighbor. The LDP synchronization timer is started by the IGP when the LDP session to the neighbor is up over the interface. This is to allow time for the label-FEC bindings to be exchanged.

When the LDP synchronization timer expires, the link cost is restored and is readvertised. The IGP will announce a new best next hop and LDP will use it if the label binding for the neighbor’s FEC is available.

If the user changes the cost of an interface, the new value is advertised at the next flooding of link attributes by the IGP. However, if the LDP synchronization timer is still running, the new cost value will only be advertised after the timer expires. The new cost value will also be advertised after the user executes any of the following commands:

• tools>perform>router>isis>ldp-sync-exit

• tools>perform>router>ospf>ldp-sync-exit

• config>router>if>no ldp-sync-timer

• config>router>ospf>disable-ldp-sync

• router>isis>disable-ldp-sync

If the user changes the value of the LDP synchronization timer parameter, the new value will take effect at the next synchronization event. If the timer is still running, it will continue to use the previous value.

If parallel links exist to the same neighbor, then the bindings and services should remain up as long as there is one interface that is up. However, the user-configured LDP synchronization timer still applies on the interface that failed and was restored. In this case, the router will only consider this interface for forwarding after the IGP re-advertises its actual cost value.

The LDP Sync Timer State is not always synchronized across to the standby CPM. Therefore, after an activity switch, the timer state might not be same as it was on the previously active CPM.

If the end-of-lib option is configured, then the system will start the LDP synchronization timer as usual. If the LDP End of LIB Typed Wildcard FEC messages are received for every FEC type negotiated for a given session to an LDP peer for that IGP interface, the ldp-sync-timer is terminated early and the IGP link cost is restored. If the ldp-sync-timer expires before the LDP End of LIB messages are received for every negotiated FEC type, then the system will restore the IGP link cost. The end-of-lib option is disabled by default.

The no form of this command disables IGP-LDP synchronization and deletes the configuration.

Default

no ldp-sync-timer

Parameters

seconds

Specifies the time interval for the IGP-LDP synchronization timer.

Values

1 to 1800

end-of-lib

Specifies that the system should terminate the ldp-sync-timer early if the LDP End of LIB Typed Wildcard FEC messages are received for every FEC type negotiated for a given session to an LDP peer for that IGP interface.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>sap>dhcp6 ldra)

Full Context

configure service vpls sap dhcp6 ldra

Description

This command enables LDRA.

The no form of this command disables LDRA.

Default

no ldra

Platforms

7705 SAR Gen 2

Context

[Tree] (debug>router>isis leak)

Full Context

debug router isis leak

Description

This command enables debugging for IS-IS leaks.

The no form of the command disables debugging.

Parameters

ip-address

When specified, only the specified address is debugged for IS-IS leaks.

Values

ipv4-address:

• a.b.c.d (host bits must be 0)

ipv6-address:

• x:x:x:x:x:x:x:x (eight 16-bit pieces)

• x:x:x:x:x:x:d.d.d.d

• x: [0 to FFFF]H

• d: [0 to 255]D

Platforms

7705 SAR Gen 2

Context

[Tree] (debug>router>ospf leak)

[Tree] (debug>router>ospf3 leak)

Full Context

debug router ospf leak

debug router ospf3 leak

Description

This command enables debugging for OSPF leaks.

Parameters

ip-address

Specifies the IPv4 or IPv6 address to debug OSPF leaks.

Values

ipv4-address:

• a.b.c.d

ipv6-address:

• x:x:x:x:x:x:x:x (eight 16-bit pieces)

• x:x:x:x:x:x:d.d.d.d

• x: [0 to FFFF]H

• d: [0 to 255]D

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>static-route-entry leak-destination)

Full Context

configure router static-route-entry leak-destination

Description

Commands in this context configure a list of VPRNs that receive a leaked copy of the static route.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router leak-export)

Full Context

configure router leak-export

Description

This command associates up to four policies to control the leaking of GRT routes into the associated VPRN.

If a route is evaluated and the action is accepted, that route is subject leaking into an associated VPRN instance, assuming the route is fully resolved and active.

This process creates the pool of routes that can be leaked. Within each VPRN, a corresponding import-grt policy must be configured to import select routes into that specific VPRN instance.

The no form of this command removes all route leaking policy associations and effectively disables the leaking of GRT routes into associated VPRNs.

Parameters

plcy-or-long-expr

Specifies the route policy name, up to 64 characters or a policy logical expression, up to 255 characters.

Values

plcy-or-long-expr: policy-name | long-expr

policy-name: up to 64 characters

long-expr: up to 255 characters

plcy-or-expr

Specifies the route policy name, up to 64 characters or a policy logical expression, up to 64 characters long. A maximum of four policy names or policy logical expressions can be specified in a single statement.

Values

plcy-or-expr: policy-name | expr

policy-name: up to 64 characters

expr: up to 64 characters

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router leak-export-limit)

Full Context

configure router leak-export-limit

Description

This command sets a maximum limit on the number of GRT routes that can be leaked into VPRN instances.

The no form of this command resets the leak-export-limit to its default value of 5.

Default

leak-export-limit 5

Parameters

value

Specifies the maximum number of eligible GRT routes that can be leaked into VPRN instances.

Values

1 to 10000

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>bgp>rib-management>label-ipv6 leak-import)

[Tree] (config>service>vprn>bgp>rib-management>label-ipv4 leak-import)

[Tree] (config>service>vprn>bgp>rib-management>ipv6 leak-import)

[Tree] (config>service>vprn>bgp>rib-management>ipv4 leak-import)

Full Context

configure service vprn bgp rib-management label-ipv6 leak-import

configure service vprn bgp rib-management label-ipv4 leak-import

configure service vprn bgp rib-management ipv6 leak-import

configure service vprn bgp rib-management ipv4 leak-import

Description

This command configures route policies that control the importation of leak-eligible routes from the BGP RIB of another routing instance into the unlabeled-IPv4, unlabeled-IPv6, labeled-IPv4, or labeled-IPv6 RIB of the VPRN instance. To leak a route from one routing instance to another, the origin and destination RIB types must be the same; for example, it is not possible to leak a route from an unlabeled-IPv4 RIB of a VPRN into the labeled-IPv4 RIB of the Base router.

The leak-import command can reference up to 15 objects, where each object is either a policy logical expression or the name of a single policy. The objects are evaluated in the specified order to determine the final action to accept or reject the route.

Only one of the 15 objects referenced by the leak-import command can be a policy logical expression consisting of policy names (enclosed in square brackets) and logical operators (AND, OR, NOT). The first of the 15 objects has a maximum length of 255 characters while the remaining 14 objects have a maximum length of 64 characters each.

When a leak-import policy is not specified, no BGP routes from other routing instances are leaked into the VPRN BGP RIB.

The no form of this command removes the policy association.

Default

no leak-import

Parameters

plcy-or-long-expr

Specifies the route policy name (up to 64 characters) or a policy logical expression (up to 255 characters). Allowed values are any string of characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes.

plcy-or-expr

Specifies the route policy name (up to 64 characters) or a policy logical expression (up to 255 characters). Allowed values are any string of characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>rib-management>label-ipv4 leak-import)

[Tree] (config>router>bgp>rib-management>ipv4 leak-import)

[Tree] (config>router>bgp>rib-management>ipv6 leak-import)

Full Context

configure router bgp rib-management label-ipv4 leak-import

configure router bgp rib-management ipv4 leak-import

configure router bgp rib-management ipv6 leak-import

Description

This command configures the router to specify route policies that control the importation of leak-eligible routes from the BGP RIB of another routing instance into the unlabeled-IPv4, unlabeled-IPv6, or labeled-IPv4 RIB of the Base router. To leak a route from one routing instance to another, the origin and destination RIB types must be the same; for example, it is not possible to leak a route from an unlabeled-IPv4 RIB of a VPRN into the labeled-IPv4 RIB of the Base router.

The leak-import command can reference up to 15 objects, where each object is either a policy logical expression or the name of a single policy. The objects are evaluated in the specified order to determine final action to accept or reject the route.

Only one of the 15 objects referenced by the leak-import command can be a policy logical expression consisting of policy names (enclosed in square brackets) and logical operators (AND, OR, NOT). The first of the 15 objects has a maximum length of 255 characters while the remaining 14 objects have a maximum length of 64 characters each.

When a leak-import policy is not specified, no BGP routes from other routing instances are leaked into the Base router BGP RIB.

The no form of this command removes the policy association.

Default

no leak-import

Parameters

plcy-or-long-expr

Specifies up to 14 route policy names (up to 64 characters long) or a policy logical expression (up to 255 characters long). Allowed values are any string of characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes.

plcy-or-expr

The route policy name (up to 64 characters long) or a policy logical expression (up to 64 characters long). Allowed values are any string of characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>if>vpls>evpn>nd learn-dynamic)

[Tree] (config>service>vprn>if>vpls>evpn>arp learn-dynamic)

[Tree] (config>service>ies>if>vpls>evpn>arp learn-dynamic)

[Tree] (config>service>ies>if>vpls>evpn>nd learn-dynamic)

Full Context

configure service vprn interface vpls evpn nd learn-dynamic

configure service vprn interface vpls evpn arp learn-dynamic

configure service ies interface vpls evpn arp learn-dynamic

configure service ies interface vpls evpn nd learn-dynamic

Description

This command controls whether the ARP or ND frames received on EVPN binds are used to learn dynamic ARP and ND entries in the ARP/ND table.

The no form of the command reverts to the default.

Default

learn-dynamic

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>dhcp>server lease-hold-time)

[Tree] (config>service>vprn>dhcp6>server lease-hold-time)

[Tree] (config>service>vprn>dhcp>server lease-hold-time)

[Tree] (config>router>dhcp6>server lease-hold-time)

Full Context

configure router dhcp local-dhcp-server lease-hold-time

configure service vprn dhcp6 local-dhcp-server lease-hold-time

configure service vprn dhcp local-dhcp-server lease-hold-time

configure router dhcp6 local-dhcp-server lease-hold-time

Description

This command configures the time to remember this lease and is applicable for unsolicited release conditions such as lease timeout if the lease-hold-time-for command is set to the default value no solicited-release and is additionally applicable for normal solicited releases from DHCP clients if the lease-hold-time-for command is set to solicited-release.

The no form of this command reverts to the default.

Default

lease-hold-time sec 0

Parameters

lease-hold-time

Specifies the amount of time to remember the lease.

Values

days	0 to 7305
hours	0 to 23
minutes	0 to 59
seconds	0 to 59

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>dhcp>server lease-hold-time-for)

[Tree] (config>service>vprn>dhcp6>server lease-hold-time-for)

[Tree] (config>router>dhcp6>server lease-hold-time-for)

[Tree] (config>router>dhcp>server lease-hold-time-for)

Full Context

configure service vprn dhcp local-dhcp-server lease-hold-time-for

configure service vprn dhcp6 local-dhcp-server lease-hold-time-for

configure router dhcp6 local-dhcp-server lease-hold-time-for

configure router dhcp local-dhcp-server lease-hold-time-for

Description

Commands in this context configure lease-hold-time-for parameters which define additional types of lease or triggers that cause system to hold up leases.

The no form of this command reverts to the default.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>sap>dhcp lease-populate)

[Tree] (config>service>ies>if>dhcp lease-populate)

[Tree] (config>service>vprn>if>dhcp lease-populate)

Full Context

configure service vpls sap dhcp lease-populate

configure service ies interface dhcp lease-populate

configure service vprn interface dhcp lease-populate

Description

Commands in this context configure IPoE host parameters.

For VPLS, DHCP snooping must be explicitly enabled (using the snoop command) at all points where DHCP messages requiring snooping enter the VPLS instance (both from the DHCP server and from the subscribers). Lease state information is extracted from snooped DHCP ACK messages to populate lease state table entries for the SAP.

The optional nbr-of-leases parameter defines the number lease state table entries allowed.

• for this SAP in case of a VPLS service

• for this interface in case of an IES or VPRN interface

• for each SAP in case of an IES or VPRN group-interface

• for this interface in case of an IES or VPRN retail subscriber-interface

If the nbr-of-leases parameter is omitted, only a single entry is allowed. Once the maximum number of entries has been reached, subsequent lease state entries are not allowed and subsequent DHCP ACK messages are discarded.

The retained lease state information representing dynamic hosts may be used to:

• Populate a SAP based anti-spoof filter table to provide dynamic anti-spoof filtering. If the system is unable to populate the dynamic host information in the anti-spoof filter table on the SAP, the DHCP ACK message must be discarded without adding new lease state entry or updating an existing lease state entry.

• Populate the system’s ARP cache based on the arp-populate configuration. Applicable to IES and VPRN interfaces or group-interfaces.

• Populate managed entries into a VPLS forwarding database. VPLS forwarding database population is an implicit feature that automatically places the dynamic host’s MAC address into the VPLS FDB. When a dynamic host’s MAC address is placed in the lease state table, it will automatically be populated into the VPLS forwarding database associated with the SAP on which the host is learned. The dynamic host MAC address will override any static MAC entries using the same MAC and prevent dynamic learning of the MAC on another interface. Existing static MAC entries with the same MAC address as the dynamic host are marked as inactive but not deleted. If all entries in the lease state table associated with the MAC address are removed, the static MAC may be populated. New static MAC definitions for the VPLS instance may be created while a dynamic host exists associated with the static MAC address.

• Generate dynamic ARP replies if arp-reply-agent is enabled. Applicable to VPLS service SAPs

The no form of this command reverts to the default.

Parameters

nbr-of-leases

Specifies the number of DHCPv4 leases allowed.

l2-header

Indicates a mode of operation where anti-spoof entry associated with the given DHCP state is created based on the src-mac address from the Layer 2 header of the DHCP request message. The Layer 2 header flag is not set by default. This parameter is only applicable for group interfaces.

mac

Specifies that the provisioned ieee-address is used in the anti-spoofing entries for this SAP. The parameter may be changed mid-session. Existing sessions will not be re-programmed unless a tools>perform>subscriber-mgmt>remap-lease-state command is issued for the lease. This parameter is only applicable for group interfaces.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>ipv6>dhcp6-relay lease-populate)

Full Context

configure service ies interface ipv6 dhcp6-relay lease-populate

Description

This command specifies the maximum number of DHCPv6 lease states allocated by the DHCPv6 relay function, allowed on this interface.

Optionally, by specifying route-populate parameter, system could:

• Create routes based on the IA_PD/IA_NA/IA_TA prefix option in relay-reply message.

• Create black hole routes based on OPTION_PD_EXCLUDE in IA_PD in relay-reply message.

These routes could be redistributed into IGP/BGP by using route-policy, following protocol types that could be used in "from protocol”:

• dhcpv6-pd

• dhcpv6-na

• dhcpv6-ta

• dhcpv6-pd-excl

Parameters

nbr-of-leases

Defines the number lease state table entries allowed for this interface. If this parameter is omitted, only a single entry is allowed. Once the maximum number of entries has been reached, subsequent lease state entries are not allowed and subsequent DHCPv6 REPLY messages are discarded.

Values

1 to 8000

route-populate

Specifies the route populate parameter.

Values

pd/na/ta — Create route based on specified option.

exclude — Create blackhole route based on OPTION_PD_EXCLUDE.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>ipv6>dhcp6-relay lease-populate)

Full Context

configure service ies interface ipv6 dhcp6-relay lease-populate

Description

This command specifies the maximum number of DHCPv6 lease states allocated by the DHCPv6 relay function, allowed on this interface.

Optionally, by specifying "route-populate” parameter, system could:

• Create routes based on the IA_PD/IA_NA/IA_TA prefix option in relay-reply message.

• Create black hole routes based on OPTION_PD_EXCLUDE in IA_PD in relay-reply message.

These routes could be redistributed into IGP/BGP by using route-policy, following protocol types that could be used in "from protocol”:

• dhcpv6-pd

• dhcpv6-na

• dhcpv6-ta

• dhcpv6-pd-excl

Parameters

nbr-of-entries

Defines the number lease state table entries allowed for this interface. If this parameter is omitted, only a single entry is allowed. Once the maximum number of entries has been reached, subsequent lease state entries are not allowed and subsequent DHCPv6 ACK messages are discarded.

Values

1 to 8000

route-populate

Specifies the route populate parameter.

Values

pd/na/ta — Create route based on specified option.

exclude — Create blackhole route based on OPTION_PD_EXCLUDE.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>options lease-rebind-time)

[Tree] (config>service>vprn>dhcp>server>pool>options lease-rebind-time)

[Tree] (config>router>dhcp>server>pool>options lease-rebind-time)

Full Context

configure subscriber-mgmt local-user-db ipoe host options lease-rebind-time

configure service vprn dhcp local-dhcp-server pool options lease-rebind-time

configure router dhcp local-dhcp-server pool options lease-rebind-time

Description

This command configures the time the client transitions to a rebinding state for a DHCP client.

The no form of this command removes the time from the configuration.

Parameters

lease-rebind-time

Specifies the lease rebind time.

Values

days:	0 to 3650
hours:	0 to 23
minutes:	0 to 59
seconds	0 to 59

Platforms

7705 SAR Gen 2

Context

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>options lease-renew-time)

[Tree] (config>service>vprn>dhcp>server>pool>options lease-renew-time)

[Tree] (config>router>dhcp>server>pool>options lease-renew-time)

Full Context

configure subscriber-mgmt local-user-db ipoe host options lease-renew-time

configure service vprn dhcp local-dhcp-server pool options lease-renew-time

configure router dhcp local-dhcp-server pool options lease-renew-time

Description

This command configures the time the client transitions to a renew state for a DHCP client.

The no form of this command removes the time from the configuration.

Parameters

lease-renew-time

Specifies the lease renew time.

Values

days:	0 to 3650
hours:	0 to 23
minutes:	0 to 59
seconds	0 to 59

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>dhcp>server>pool>options lease-time)

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>options lease-time)

[Tree] (config>service>vprn>dhcp>server>pool>options lease-time)

Full Context

configure router dhcp local-dhcp-server pool options lease-time

configure subscriber-mgmt local-user-db ipoe host options lease-time

configure service vprn dhcp local-dhcp-server pool options lease-time

Description

This command configures the amount of time that the DHCP server grants to the DHCP client permission to use a specific IP address.

The no form of this command removes the lease time parameters from the configuration.

Parameters

days

Specifies the number of days that the given IP address is valid.

Values

0 to 3650

hours

Specifies the number of hours that the given IP address is valid.

Values

0 to 23

minutes

Specifies the number of minutes that the given IP address is valid.

Values

0 to 59

seconds

Specifies the number of seconds that the given IP address is valid.

Values

0 to 59

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>dhcp>proxy-server lease-time)

[Tree] (config>service>vpls>sap>dhcp>proxy-server lease-time)

[Tree] (config>service>vprn>if>dhcp>proxy lease-time)

Full Context

configure service ies interface dhcp proxy-server lease-time

configure service vpls sap dhcp proxy-server lease-time

configure service vprn interface dhcp proxy-server lease-time

Description

This command defines the length of lease-time that is provided to DHCP clients. By default, the local-proxy-server always makes use of the lease time information provide by either a RADIUS or DHCP server.

The no form of this command disables the use of the lease-time command. The local-proxy-server will use the lease-time offered by either a RADIUS or DHCP server.

Default

lease-time days 7

Parameters

override

Specifies that the local-proxy-server will use the configured lease-time information to provide DHCP clients

days

Specifies the number of days that the given IP address is valid.

Values

0 to 3650

hours

Specifies the number of hours that the given IP address is valid.

Values

0 to 23

minutes

Specifies the number of minutes that the given IP address is valid.

Values

0 to 59

seconds

Specifies the number of seconds that the given IP address is valid.

Values

0 to 59

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>if>autoconfig>dhcp-client lease-time)

[Tree] (config>router>if>autoconfig>dhcp-client lease-time)

[Tree] (config>service>ies>if>autoconfig>dhcp-client lease-time)

Full Context

configure service vprn interface autoconfigure dhcp-client lease-time

configure router interface autoconfigure dhcp-client lease-time

configure service ies interface autoconfigure dhcp-client lease-time

Description

This command configures the lease time that the DHCP client requests from the DHCP server. The DHCP server can override the configured value.

Default

lease-time days 1

Parameters

days

Specifies the lease time, in days.

Values

0 to 3650

hours

Specifies the lease time, in hours.

Values

0 to 23

minutes

Specifies the lease time, in minutes.

Values

0 to 59

seconds

Specifies the lease time, in seconds.

Values

0 to 59

infinite

Keyword to request an infinite lease with no expiry.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls>lsp least-fill)

[Tree] (config>router>mpls>lsp-template least-fill)

Full Context

configure router mpls lsp least-fill

configure router mpls lsp-template least-fill

Description

This command enables the use of the least-fill path selection method for the computation of the path of this LSP.

When MPLS requests the computation of a path for this LSP, CSPF will find all equal cost shortest paths which satisfy the constraints of this path. Then, CSPF identifies the single link in each of these paths which has the least available bandwidth as a percentage of its maximum reservable bandwidth. It then selects the path which has the largest value of this percentage least available bandwidth figure. CSPF identifies the least available bandwidth link in each equal cost path after it has accounted for the bandwidth of the new requested path of this LSP.

CSPF applies the least-fill path selection method to all requests for a path, primary and secondary, of an LSP for which this option is enabled. The bandwidth of the path can be any value, including zero.

CSPF applies the least-fill criterion separately to each preemption priority in the base TE. A higher setup priority path can preemptively lower holding priority paths.

CSPF also applies the least-fill criterion separately to each Diff-Serv TE class if Diff-Serv TE is enabled on this node. A higher setup priority path can preemptively lower holding priority paths within a Class Type.

MPLS will re-signal and move the LSP to the new path in the following cases:

• Initial LSP path signaling.

• Re-try of an LSP path after failure.

• Make-before-break (MBB) due to pending soft preemption of the LSP path.

• MBB due to LSP path configuration change, that is, a user change to bandwidth parameter of primary or secondary path, or a user enabling of fast-reroute option for the LSP.

• MBB of secondary path due to an update to primary path SRLG.

• MBB due to FRR Global Revertive procedures on the primary path.

• Manual re-signaling of an LSP path or of all LSP paths by the user.

During a manual re-signaling of an LSP path, MPLS will always re-signal the path regardless of whether the new path is exactly the same or different than the current path and regardless of whether the metric of the new path is different or not from that of the current path.

During a timer-based re-signaling of an LSP path which has the least-fill option enabled, MPLS will only re-signal the path if the metric of the new path is different than the one of the current path.

The no form of this command deletes a specific node entry in this database.

Default

no least-fill. The path of an LSP is randomly chosen among a set of equal cost paths.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls least-fill-min-thd)

Full Context

configure router mpls least-fill-min-thd

Description

This parameter is used in the least-fill path selection process. When comparing the percentage of least available link bandwidth across the sorted paths, whenever two percentages differ by less than the value configured as the least-fill-min-thresh, CSPF will consider them equal and will apply a random number generator to select the path among these paths

The no form of this command resets this parameter to its default value.

Default

least-fill-min-thd 5

Parameters

percentage

Specifies the least fill minimum threshold value as a percentage.

Values

1 to 100%

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls least-fill-reoptim-thd)

Full Context

configure router mpls least-fill-reoptim-thd

Description

This parameter is used in the least-fill path selection method. During a timer-based re-signaling of an LSP path which has the least-fill option enabled, CSPF will first update the least-available bandwidth figure for the current path of this LSP. It then applies the least-fill path selection method to select a new path for this LSP. If the new computed path has the same cost as the current path, it will compare the least-available bandwidth figures of the two paths and if the difference exceeds the user configured optimization threshold, MPLS will generate a trap to indicate that a better least-fill path is available for this LSP. This trap can be used by an external SNMP based device to trigger a manual re-signaling of the LSP path since the timer-based re-signaling will not re-signal the path in this case. MPLS will generate a path update trap at the first MBB event which results in the re-signaling of the LSP path. This should clear the eligibility status of the path at the SNMP device.

The no form of this command resets this parameter to its default value.

Default

least-fill-reoptim-thd 10

Parameters

percentage

Specifies the least fill reoptimization threshold value as a percentage.

Values

1 to 100%

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>isis>te>application-link-attributes legacy)

Full Context

configure router isis traffic-engineering-options application-link-attributes legacy

Description

This command enables legacy mode of advertising TE attributes.

The no form of this command disables legacy mode, but enables the per-application TE attribute advertisement for RSVP-TE.

Default

legacy

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>ldp legacy-ipv4-lsr-interop)

Full Context

configure router ldp legacy-ipv4-lsr-interop

Description

This command provides for a global LDP knob to allow interoperability with legacy IPv4 LSR implementations which do not comply with the processing of Hello TLVs with the U-bit set. Specifically, this feature disables the following Hello TLVs:

• The Nokia proprietary Interface Info TLV (0x3E05) in the Hello message sent to the peer. This also results in the non-generation of the Nokia proprietary Hello Adjacency Status TLV (0x3E06) since the Interface Info TLV is not sent.

  This is performed in SR OS releases 12 and higher.

• The RFC 7552 standard dual-stack capability TLV (0x701) and the Nokia proprietary Adjacency capability TLV (0x3E07) in SR OS releases 13 and higher.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>error-handling legacy-mode)

[Tree] (config>service>vprn>bgp>error-handling legacy-mode)

Full Context

configure router bgp error-handling legacy-mode

configure service vprn bgp error-handling legacy-mode

Description

The no form of this command configures the BGP instance to ignore the configured update-fault-tolerance commands and apply the new error-handling procedures described in RFC 7606 on all sessions.

Default

no legacy-mode

Platforms

7705 SAR Gen 2

Context

[Tree] (environment>terminal length)

Full Context

environment terminal length

Description

This command sets the number of lines on a screen.

Parameters

lines

Specifies the number of lines for the terminal screen length, expressed as a decimal integer.

Values

1 to 512

Default

24 — terminal dimensions are set to 24 lines long by 80 characters wide

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>management-interface>cli>md-cli>environment>console length)

Full Context

configure system management-interface cli md-cli environment console length

Description

This command configures the set number of lines displayed on the console.

Default

length 24

Parameters

lines

Specifies the number of lines displayed in the console window.

Values

24 to 512

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>serial>rs232>socket>rx>eop length)

Full Context

configure port serial rs232 socket rx eop length

Description

This command configures the number of characters (converted to bytes) received from the serial port that triggers the node to encapsulate the characters into an IP transport packet that can then be sent over an IES or VPRN service.

There are other delimiting parameters within the EOP context. The first condition met signals the EOP.

Default

length 1500

Parameters

bytes

Specifies the number of characters (bytes) to trigger sending an IP transport packet.

Values

1 to 1500

Default

1500

Platforms

7705 SAR-10x, 7705 SAR-Hx, 7705 SAR-Mx

Context

[Tree] (config>test-oam>icmp>ipv6 length-field)

Full Context

configure test-oam icmp ipv6 length-field

Description

This command enables the setting of the length field when building an RFC 4884, Extended ICMP to Support Multi-Part Messages, ICMPv6 Destination Unreachable message or ICMPv6 Time Exceeded message.

The no form of this command disables the length field modification.

Default

no length-field

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos>network>ingress ler-use-dscp)

Full Context

configure qos network ingress ler-use-dscp

Description

This command is used to enable tunnel QoS mapping on all ingress network IP interfaces that the network-qos-policy-id is associated with. The command may be defined at any time after the network QoS policy has been created. Any network IP interfaces currently associated with the policy will immediately start to use the internal IP ToS field of any tunnel terminated IP routed packet received on the interface, ignoring any QoS markings in the tunnel portion of the packet.

This attribute provides the ability to ignore the network ingress QoS mapping of a terminated tunnel containing an IP packet that is to be routed to a Base router or VPRN destination. This is advantageous when the mapping for the tunnel QoS marking does not accurately or completely reflect the required QoS handling for the IP routed packet. When the mechanism is enabled on an ingress network IP interface, the IP interface will ignore the tunnel’s QoS mapping and derive the internal forwarding class and profile based on the precedence or DiffServ Code Point (DSCP) values within the routed IP header ToS field compared to the Network QoS policy defined on the IP interface.

The default state is not to enforce tunnel termination IP routed QoS override within the network QoS policy.

The no form of this command removes tunnel termination IP routed QoS override from the network QoS policy and all ingress network IP interfaces associated with the policy.

Default

no ler-use-dscp

Platforms

7705 SAR Gen 2

Context

[Tree] (config>vrrp>policy>priority-event>route-unknown less-specific)

Full Context

configure vrrp policy priority-event route-unknown less-specific

Description

This command allows a CIDR shortest match hit on a route prefix that contains the IP route prefix associated with the route unknown priority event.

The less-specific command modifies the search parameters for the IP route prefix specified in the route-unknown priority event. Specifying less-specific allows a CIDR shortest match hit on a route prefix that contains the IP route prefix.

The less-specific command eases the RTM lookup criteria when searching for the prefix/mask-length. When the route-unknown priority event sends the prefix to the RTM (as if it was a destination lookup), the result route table prefix (if a result is found) is checked to see if it is an exact match or a less specific match. The less-specific command enables a less specific route table prefix to match the configured prefix. When less-specific is not specified, a less specific route table prefix fails to match the configured prefix. The allow-default optional parameter extends the less-specific match to include the default route (0.0.0.0).

The no form of the command prevents RTM lookup results that are less specific than the route prefix from matching.

Default

no less-specific — The route unknown priority events requires an exact prefix/mask match.

Parameters

allow-default

When the allow-default parameter is specified with the less-specific command, an RTM return of 0.0.0.0 matches the IP prefix. If less-specific is entered without the allow-default parameter, a return of 0.0.0.0 will not match the IP prefix. To disable allow-default, but continue to allow less-specific match operation, only enter the less-specific command (without the allow-default parameter).

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet>egr-scheduler-override level)

Full Context

configure port ethernet egress-scheduler-override level

Description

This command overrides the maximum and CIR rate parameters for a specific priority level on the port or channel’s port scheduler instance. When the level command is executed for a priority level, the corresponding priority level command in the port-scheduler-policy associated with the port is ignored.

The override level command supports the keyword max for the rate and cir parameter. When executing the level override command, at least the rate or cir keywords and associated parameters must be specified for the command to succeed.

The no form of this command removes the local port priority level rate overrides. Once removed, the port priority level will use the port scheduler policies level command for that priority level.

Parameters

priority-level

Identifies which of the eight port priority levels are being overridden.

Values

1 to 8

pir-rate

Overrides the port scheduler policy’s maximum level rate and requires either the max keyword or a rate defined in kilobits per second to follow.

Values

For Ethernet: 1 to 6400000000, max

For SONET-SDH and TDM: 1 to 3200000000, max

cir-rate

Overrides the port scheduler policy’s within-cir level rate and requires either the max keyword or a rate defined in kilobits per second to follow.

Values

For Ethernet: 1 to 6400000000, max

For SONET-SDH and TDM: 1 to 3200000000, max

pir-percent

Specifies the PIR as a percentage.

Values

0.01 to 100.00

cir-percent

Specifies the CIR as a percentage.

Values

0.00 to 100.00

max

removes any existing rate limit imposed by the port scheduler policy for the priority level allowing it to use as much total bandwidth as possible.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>isis>if level)

[Tree] (config>service>vprn>isis level)

[Tree] (config>service>vprn>isis>link-group level)

Full Context

configure service vprn isis interface level

configure service vprn isis level

configure service vprn isis link-group level

Description

This command creates the context to configure IS-IS Level 1 or Level 2 area attributes.

A router can be configured as a Level 1, Level 2, or Level 1/2 system. A Level 1 adjacency can be established if there is at least one area address shared by this router and a neighbor. A Level 2 adjacency cannot be established over this interface.

Level 1/2 adjacency is created if the neighbor is also configured as Level 1/2 router and has at least one area address in common. A Level 2 adjacency is established if there are no common area IDs.

A Level 2 adjacency is established if another router is configured as Level 2 or a Level 1/2 router with interfaces configured as Level 1/2 or Level 2. Level 1 adjacencies are not established over this interface.

To reset global and/or interface level parameters to the default, the following commands must be entered independently:

• level>no hello-authentication-key

• level>no hello-authentication-type

• level>no hello-interval

• level>no hello-multiplier

• level>no metric

• level>no passive

• level>no priority

Default

level 1 or level 2

Parameters

level-number

The IS-IS level number.

Values

1, 2

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>log>syslog level)

Full Context

configure service vprn log syslog level

Description

This command configures the syslog message severity level threshold. All messages with severity level equal to or higher than the threshold are sent to the syslog target host.

Only a single threshold level can be specified. If multiple levels are entered, the last level entered will overwrite the previously entered commands.

Default

level info

Parameters

syslog-level

The threshold severity level name.

Values

emergency, alert, critical, error, warning, notice, info, debug

Router severity level	Numerical Severity (highest to lowest)	Configured Severity	Definition
	0	emergency	system is unusable
3	1	alert	action must be taken immediately
4	2	critical	critical condition
5	3	error	error condition
6	4	warning	warning condition
	5	notice	normal but significant condition
1 cleared 2 indeterminate	6	info	informational messages
	7	debug	debug-level messages

Platforms

7705 SAR Gen 2

Context

[Tree] (config>qos>port-scheduler-policy level)

Full Context

configure qos port-scheduler-policy level

Description

This command configures an explicit within-CIR bandwidth limit and a total bandwidth limit for each port scheduler’s priority level. To understand how to set the level rate and CIR parameters, a basic understanding of the port-level scheduler bandwidth allocation mechanism is required. The port scheduler takes all available bandwidth for the port or channel (after the max-rate and any port egress-rate limits have been accounted for) and offers it to each of the eight priority levels twice.

The first pass is called the within-CIR pass and consists of providing the available port bandwidth to each of the 8 priority levels, starting with level 8 and moving down to level 1. Each level takes the offered load and distributes it to all child members that have a port-parent cir-level equal to the current priority level. (Any child with a cir-weight equal to 0 is skipped in this pass.) Each child may consume bandwidth up to the child’s frame-based within-CIR offered load. The remaining available port bandwidth is then offered to the next lower priority level until level 1 is reached.

The second pass is called the above-CIR pass and consists of providing the remaining available port bandwidth to each of the eight priority levels a second time. Again, each level takes the offered load and distributes it to all child members that have a port-parent level equal to the current priority level. Each child may consume bandwidth up to the remainder of the child’s frame-based offered load (some of the offered load may have been serviced during the within-CIR pass). The remaining available port bandwidth is then offered to the next priority level until level 1 is again reached.

If the port scheduling policy is using the default orphan behavior (orphan-override has not been configured on the policy), the system then takes any remaining port bandwidth and allocates it to the orphan queues and scheduler on priority level 1. In a non-override orphan state, all orphans are attached to priority level 1 using a weight of 0. The zero weight value causes the system to allocate bandwidth equally to all orphans based on each orphan queue or scheduler’s ability to use the bandwidth. If the policy has an orphan-override configured, the orphans are handled based on the override commands parameters in a similar fashion to properly parented queues and schedulers.

The port scheduler priority level command rate keyword is used to optionally limit the total amount of bandwidth that is allocated to a priority level (total for the within-CIR and above-CIR passes). The cir keyword optionally limits the first pass bandwidth allocated to the priority level during the within-CIR pass.

When executing the level command, at least one of the optional keywords, rate or cir, must be specified. If neither keyword is included, the command will fail.

If a previous explicit value for rate or cir exists when the level command is executed, and either rate or cir is omitted, the previous value for the parameter is overwritten by the default value and the previous value is lost.

The configured priority level rate limits may be overridden at the egress port or channel using the egress-scheduler-override level priority-level command. When a scheduler instance has an override defined for a priority level, both the rate and cir values are overridden even when one of them is not explicitly expressed in the override command. For instance, if the cir kilobits per second portion of the override is not expressed, the scheduler instance defaults to not having a CIR rate limit for the priority level even when the port scheduler policy has an explicit CIR limit defined.

The no form of this command returns the level to its default value.

Default

no level priority-level

Parameters

priority-level

Specifies to which priority level the level command pertains. Each of the eight levels is represented by an integer value of 1 to 8, with 8 being the highest priority level.

Values

1 to 8 (8 is the highest priority)

pir-rate

Specifies the total bandwidth limits allocated to priority-level, in kilobits per second.

Values

1 to 6400000000, max

pir-percent

Specifies the percent bandwidth limits allocated to priority-level.

Values

0.01 to 100.00

cir-rate

The cir specified limits the total bandwidth allocated in the within-CIR distribution pass to priority-level. When cir is not specified, all the available port or channel bandwidth may be allocated to the specified priority level during the within-CIR pass.

Values

0 to 6400000000, max

The value given for kilobits per second is expressed in kilobits per second on a base 10 scale as is usual for line rate calculations. If a value of 1 is given, the result is 1000 bits per second (as opposed to a base 2 interpretation that would be 1024 bits per second).

cir-percent

Specifies the percent bandwidth limits allocated to priority-level.

Values

0.00 to 100.00

group name

specifies the existing group that the weighted scheduler group this level maps to, up to 32 characters.

weight

Specifies the weight of the level within this weighted scheduler group.

Values

1 to 100

Default

1

monitor-threshold percent

Specifies the percent of the configured rate. If the offered rate exceeds the configured threshold, a counter monitoring the threshold will be increased.

Values

0 to 100

Platforms

7705 SAR Gen 2

Context

[Tree] (config>log>syslog level)

Full Context

configure log syslog level

Description

This command configures the syslog message severity level threshold. All messages with severity level equal to or higher than the threshold are sent to the syslog target host.

Only a single threshold level can be specified. If multiple levels are entered, the last level entered will overwrite the previously entered commands.

The no form of this command reverts to the default value.

Default

level info

Parameters

value

Specifies the threshold severity level name.

Values

emergency, alert, critical, error, warning, notice, info, debug

Table 2. Level Parameter Value Descriptions

Router severity level	Numerical Severity (highest to lowest)	Configured Severity	Definition
	0	emergency	system is unusable
3	1	alert	action must be taken immediately
4	2	critical	critical condition
5	3	error	error condition
6	4	warning	warning condition
	5	notice	normal but significant condition
1 cleared 2 indeterminate	6	info	informational messages
	7	debug	debug-level messages

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>isis level)

[Tree] (config>router>isis>interface level)

Full Context

configure router isis level

configure router isis interface level

Description

This command creates the context to configure IS-IS Level 1 or Level 2 area attributes.

A router can be configured as a Level 1, Level 2, or Level 1/2 system. A Level 1 adjacency can be established if there is at least one area address shared by this router and a neighbor. A Level 2 adjacency cannot be established over this interface.

Level 1/2 adjacency is created if the neighbor is also configured as Level 1/2 router and has at least one area address in common. A Level 2 adjacency is established if there are no common area IDs.

A Level 2 adjacency is established if another router is configured as Level 2 or a Level 1/2 router with interfaces configured as Level 1/2 or Level 2. Level 1 adjacencies are not established over this interface.

To reset global and/or interface level parameters to the default, the following commands must be entered independently:

— level>no hello-authentication-key
    — level>no hello-authentication-type
    — level>no hello-interval
    — level>no hello-multiplier 
    — level>no metric
    — level>no passive
    — level>no priority 

Default

level 1 or level 2

Parameters

1

Specifies the IS-IS operational characteristics of the interface at level 1.

2

Specifies the IS-IS operational characteristics of the interface at level 2.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>policy-options>policy-statement>entry>from level)

[Tree] (config>router>policy-options>policy-statement>entry>to level)

Full Context

configure router policy-options policy-statement entry from level

configure router policy-options policy-statement entry to level

Description

This command specifies the ISIS route level as a match criterion for the entry.

Default

no level

Parameters

1 | 2

Matches the IS-IS route learned from level 1 or level 2.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>isis>if level-capability)

[Tree] (config>service>vprn>isis level-capability)

Full Context

configure service vprn isis interface level-capability

configure service vprn isis level-capability

Description

This command configures the routing level for an instance of the IS-IS routing process.

An IS-IS router and an IS-IS interface can operate at Level 1, Level 2 or both Level 1 and 2.

Potential Adjacency Capabilities displays configuration combinations and the potential adjacencies that can be formed.

The no form of this command removes the level capability from the configuration.

Default

level-capability level-1/2

Parameters

level-1

Specifies the router/interface can operate at Level 1 only.

level-2

Specifies the router/interface can operate at Level 2 only.

level-1/2

Specifies the router/interface can operate at both Level 1 and Level 2.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>isis>interface level-capability)

[Tree] (config>router>isis level-capability)

Full Context

configure router isis interface level-capability

configure router isis level-capability

Description

This command configures the routing level for an instance of the IS-IS routing process.

An IS-IS router and an IS-IS interface can operate at Level 1, Level 2 or both Level 1 and 2.

Potential Adjacency displays configuration combinations and the potential adjacencies that can be formed.

The no form of this command removes the level capability from the configuration.

Default

level-capability level-1/2

Parameters

level-1

Specifies the router/interface can operate at Level 1only.

level-2

Specifies the router/interface can operate at Level 2 only.

level-1/2

Specifies the router/interface can operate at both Level 1 and Level 2.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>isis>if lfa-policy-map)

Full Context

configure service vprn isis interface lfa-policy-map

Description

This command applies a route next-hop policy template to the IS-IS interface for the VPRN instance.

When a route next-hop policy template is applied to an interface in IS-IS, it is applied in both level 1 and level 2. When a route next-hop policy template is applied to an interface in OSPF, it is applied in all areas. However, the command in an OSPF interface context can only be executed under the area in which the specified interface is primary and then applied in that area and in all other areas where the interface is secondary. If the user attempts to apply it to an area where the interface is secondary, the command fails.

If the user excluded the interface from LFA using the command loopfree-alternate-exclude, the LFA policy, if applied to the interface, has no effect.

Finally, if the user applied a route next-hop policy template to a loopback interface or to the system interface, the command will not be rejected, but it will result in no action being taken.

The no form deletes the mapping of a route next-hop policy template to an OSPF or IS-IS interface.

Parameters

template-name

Specifies the name of the template, up to 32 characters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>isis>if lfa-policy-map)

[Tree] (config>router>ospf3>area>if lfa-policy-map)

[Tree] (config>router>ospf>area>if lfa-policy-map)

[Tree] (config>service>vprn>ospf3>area>if lfa-policy-map)

[Tree] (config>service>vprn>ospf>area>if lfa-policy-map)

Full Context

configure router isis interface lfa-policy-map

configure router ospf3 area interface lfa-policy-map

configure router ospf area interface lfa-policy-map

configure service vprn ospf3 area interface lfa-policy-map

configure service vprn ospf area interface lfa-policy-map

Description

This command applies a route next-hop policy template to an OSPF or IS-IS interface.

When a route next-hop policy template is applied to an interface in IS-IS, it is applied in both level 1 and level 2. When a route next-hop policy template is applied to an interface in OSPF, it is applied in all areas. However, the command in an OSPF interface context can only be executed under the area in which the specified interface is primary and then applied in that area and in all other areas where the interface is secondary. If the user attempts to apply it to an area where the interface is secondary, the command fails.

If the user excluded the interface from LFA using the command loopfree-alternate-exclude, the LFA policy, if applied to the interface, has no effect.

Finally, if the user applied a route next-hop policy template to a loopback interface or to the system interface, the command will not be rejected, but it results in no action being taken.

The no form deletes the mapping of a route next-hop policy template to an OSPF or IS-IS interface.

Default

no lfa-policy-map

Parameters

template-name

Specifies the name of the template, up to 32 characters.

Platforms

7705 SAR Gen 2

Context

[Tree] (admin>system license)

Full Context

admin system license

Description

Enters a context for administrative commands related to licensing.

Platforms

7705 SAR Gen 2

Context

[Tree] (bof license-file)

Full Context

bof license-file

Description

This command configures the license location and file name.

The no form of this command removes the file URL from the configuration.

Parameters

file-url

Specifies the file-url.

Values

file-url	{local-url | remote-url} (up to 180 characters)
local-url	[cflash-id/][file-path]
remote-url	[{ftp://| tftp://} login:pswd@remote-locn/][file-path]
cflash-id	cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>script-control>script-policy lifetime)

Full Context

configure system script-control script-policy lifetime

Description

This command is used to configure the maximum amount of time that a script may run.

Default

lifetime 3600

Parameters

seconds

Specifies the maximum amount of time that a script may run, in seconds.

Values

0 to 21474836

Default

3600 (1 hour)

forever

Specifies to allow a script to run indefinitely.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>ipsec>ike-policy limit-init-exchange)

Full Context

configure ipsec ike-policy limit-init-exchange

Description

This command limits the number of ongoing IKEv2 initial exchanges per tunnel to 1. When the system receives a new IKEv2 IKE_SA_INIT request when there is an ongoing IKEv2 initial exchange from same peer, then system reduces the timeout value of the existing exchange to the specified reduced-max-exchange-timeout. If the reduced-max-exchange-timeout is disabled, then the system does not reduce the timeout value.

The no form of this command reverts to the default value.

Default

limit-init-exchange reduced-max-exchange-timeout 2

Parameters

seconds

Specifies the maximum timeout for the in-progress initial IKE exchange.

Values

2 to 60, disabled

Platforms

7705 SAR-Hx, 7705 SAR-Mx, 7705 SAR-1

Context

[Tree] (config>service>vpls>sap limit-mac-move)

[Tree] (config>service>vpls>spoke-sdp limit-mac-move)

Full Context

configure service vpls sap limit-mac-move

configure service vpls spoke-sdp limit-mac-move

Description

This command indicates whether or not the mac-move agent, when enabled using config>service>vpls>mac-move or config>service>epipe>mac-move, limits the MAC re-learn (move) rate on this SAP.

Default

limit-mac-move blockable

Parameters

blockable

Specifies that the agent monitors the MAC re-learn rate on the SAP, and it blocks it when the re-learn rate is exceeded.

non-blockable

Specifies that this SAP is not blocked, and another blockable SAP is blocked instead.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>pw-template limit-mac-move)

Full Context

configure service pw-template limit-mac-move

Description

This command indicates whether or not the mac-move agent will limit the MAC re-learn (move) rate.

Default

limit-mac-move blockable

Parameters

blockable

The agent will monitor the MAC re-learn rate, and it will block it when the re-learn rate is exceeded.

non-blockable

When specified, a SAP will not be blocked, and another blockable SAP will be blocked instead.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>tdm line-impedance)

Full Context

configure port tdm line-impedance

Description

This command configures the line impedance of a port. Line impedance is set per-port, and ports on the same card can have different values. Before changing the line impedance of a port, the port must be shut down.

Default

120 for E1

Parameters

75

Keyword to set the line impedance to 75 Ω.

100

Keyword to set the line impedance to 100 Ω.

120

Keyword to set the line impedance to 120 Ω.

Platforms

7705 SAR-10x, 7705 SAR-Hx, 7705 SAR-Mx

Context

[Tree] (config>service>ies>if>sap>ipsec-gw>dhcp6 link-address)

[Tree] (config>service>vprn>if>sap>ipsec-gw>dhcp6 link-address)

Full Context

configure service ies interface sap ipsec-gw dhcp6 link-address

configure service vprn interface sap ipsec-gw dhcp6 link-address

Description

This command specifies the link address of the relayed DHCPv6 packets sent by the system.

Default

no link-address

Parameters

ipv6-address

Specifies a global unicast IPv6 address.

Platforms

7705 SAR-Hx, 7705 SAR-Mx, 7705 SAR-1

Context

[Tree] (config>service>vprn>bgp>group link-bandwidth)

[Tree] (config>service>vprn>bgp>group>neighbor link-bandwidth)

Full Context

configure service vprn bgp group link-bandwidth

configure service vprn bgp group neighbor link-bandwidth

Description

This command enables the configuration context for handling the link-bandwidth extended community attached to specific BGP routes.

When all used multipaths of an IP prefix correspond to BGP routes with a link-bandwidth extended community, the datapath is programmed to do weighted ECMP across the BGP next-hops in proportion to the bandwidth values.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>group>neighbor link-bandwidth)

[Tree] (config>router>bgp>group link-bandwidth)

Full Context

configure router bgp group neighbor link-bandwidth

configure router bgp group link-bandwidth

Description

This command enables the configuration context for handling the link-bandwidth extended community attached to specific BGP routes.

When all used multipaths of an IP prefix correspond to BGP routes with a link-bandwidth extended community, the datapath is programmed to do weighted ECMP across the BGP next-hops in proportion to the bandwidth values.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet>efm-oam>peer-rdi-rx link-fault)

Full Context

configure port ethernet efm-oam peer-rdi-rx link-fault

Description

This command configures how the system reacts when it receives a a link fault flag set in the informational PDU from a peer.

Default

link-fault local-port-action out-of-service

Parameters

local-port-action

Keyword that defines whether the local port is affected when a link fault is received from a peer.

log-only

Keyword that prevents the port from being affected when the local peer receives a link fault. The dying gasp is logged but the port remains operational.

out-of-service

Keyword that causes the port to enter a non-operation down state with a port state of link up. The error is logged upon reception of link fault event. The port is not available to service data but it continues to carry Link OAM traffic, ensuring the link is monitored.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>isis link-group)

Full Context

configure service vprn isis link-group

Description

This command configures a link-group for the router or VPRN instance.

The no form of this command removes the specified link-group.

Parameters

link-group-name

Name of the link-group to be added or removed from the router or VPRN service.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>isis link-group)

Full Context

configure router isis link-group

Description

This command specifies the IS-IS link group associated with this particular level of the interface.

Default

no link-group

Parameters

link-group-name

Specifies an IS-IS link group name, up to 32 characters in length, on the system.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>ipv6 link-local-address)

[Tree] (config>service>vprn>if>ipv6 link-local-address)

[Tree] (config>router>if>ipv6 link-local-address)

Full Context

configure service ies interface ipv6 link-local-address

configure service vprn interface ipv6 link-local-address

configure router interface ipv6 link-local-address

Description

This command configures the IPv6 Link Local address that is used as a virtual SRRP IPv6 address by the Master SRRP node. This address is sent in the Router Advertisements initiated by the Master SRRP node. Clients use this address as IPv6 default-gateway. Both SRRP nodes, Master and Backup, must be configured with the same Link Local address.

Only one link-local-address is allowed per interface.

The no form of this command reverts to the default.

Parameters

ipv6-address

Specifies the IPv6 address in the form:

Values

ipv6-address:	x:x:x:x:x:x:x:x
	x:x:x:x:x:x:d.d.d.d
	x - [0..FFFF]H
	d - [0..255]D

dad-disable

Disables Duplicate Address Detection (DAD) and sets the address to preferred, even if there is a duplicated address.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp link-state-export-enable)

Full Context

configure router bgp link-state-export-enable

Description

This command enables the export of link-state information from the BGP-LS address family into the local Traffic Engineering Database (TED).

The no form of this command disables the export of link state information into the TED.

Default

no link-state-export-enable

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp link-state-import-enable)

Full Context

configure router bgp link-state-import-enable

Description

This command enables the import of link-state information into the BGP-LS address family for advertisement to other BGP neighbors.

The no form of this command disables the import of link state information into the BGP-LS address family.

Default

no link-state-import-enable

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls>sap>stp link-type)

[Tree] (config>service>template>vpls-sap-template>stp link-type)

[Tree] (config>service>vpls>spoke-sdp>stp link-type)

Full Context

configure service vpls sap stp link-type

configure service template vpls-sap-template stp link-type

configure service vpls spoke-sdp stp link-type

Description

This command instructs STP on the maximum number of bridges behind this SAP or spoke-SDP. If there is only a single bridge, transitioning to forwarding state will be based on handshaking (fast transitions). If more than two bridges are connected via a shared media, their SAP or spoke-SDPs should all be configured as shared, and timer-based transitions are used.

The no form of this command returns the link type to the default value.

Default

link-type pt-pt

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>pw-template>stp link-type)

Full Context

configure service pw-template stp link-type

Description

This command instructs STP on the maximum number of bridges behind this SAP or spoke SDP. If there is only a single bridge, transitioning to forwarding state will be based on handshaking (fast transitions). If more than two bridges are connected via a shared media, their SAP or spoke SDPs should all be configured as shared, and timer-based transitions are used.

The no form of this command returns the link type to the default value.

Default

link-type pt-pt

Platforms

7705 SAR Gen 2

Context

[Tree] (oam>eth-cfm linktrace)

Full Context

oam eth-cfm linktrace

Description

This command initiates a linktrace test.

Parameters

mac-address

Specifies a unicast MAC address destination.

Values

xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx

remote-mepid mep-id

Specifies the remote MEP ID of the peer within the association. The domain and association information are derived from the source MEP for the session. The Layer 2 IEEE MAC address is resolved from previously learned remote MAC addressing, derived from the reception and processing of the ETH-CC PDU. The local MEP must be administratively enabled.

Values

1 to 8191

mep mep-id

Specifies the local MEP ID.

Values

1 to 8191

md-index

Specifies the MD index.

Values

1 to 4294967295

ma-index

Specifies the MA index.

Values

1 to 4294967295

ttl-value

Specifies the TTL for a returned linktrace.

Values

0 to 255

Default

64

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>netconf listen)

Full Context

configure system netconf listen

Description

Commands in this context configure NETCONF listening parameters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>grpc listening-port)

Full Context

configure system grpc listening-port

Description

This command configures the listening port for the gRPC server.

The no form of this command reverts to the default.

Default

listening-port 57400

Parameters

port

Specifies the port number.

Values

1024 to 49151, 57400

Default

57400

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>security>ssh listening-port)

Full Context

configure system security ssh listening-port

Description

This command configures the default SSH port for SSH connections arriving in VPRN or base routing.

The no form of this command configures the default SSH port to 22.

Default

no listening-port

Parameters

port

Specifies the port number.

Values

1024 to 49151

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>security>telnet listening-port)

Full Context

configure system security telnet listening-port

Description

This command configures the default Telnet port for Telnet connections arriving in VPRN or base routing.

The no form of this command configures the default Telnet port to 23.

Default

no listening-port

Parameters

port

Specifies the port number.

Values

1024 to 49151

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet lldp)

Full Context

configure port ethernet lldp

Description

Commands in this context configure Link Layer Discovery Protocol (LLDP) parameters on the specified port.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet lldp)

Full Context

configure port ethernet lldp

Description

Commands in this context configure Link Layer Discovery Protocol (LLDP) parameters on the specified port.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system lldp)

Full Context

configure system lldp

Description

Commands in this context configure system-wide Link Layer Discovery Protocol parameters.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>lag lldp-member-template)

Full Context

configure lag lldp-member-template

Description

Commands in this context configure the LLDP parameters for member ports.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe>sap>ethernet llf)

Full Context

configure service epipe sap ethernet llf

Description

This command enables LLF on an Ethernet port. This feature provides an end-to-end OAM fault notification for Ethernet VLL service. It brings down the Ethernet port (Ethernet LLF) or sends a SONET/SDH Path AIS (ATM LLF) toward the attached CE when there is a local fault on the pseudowire or service, or a remote fault on the SAP or pseudowire, signaled with label withdrawal or T-LDP status bits. It ceases when the fault disappears.

The Ethernet port must be configured for null encapsulation.

This feature is also supported in Epipes with BGP-EVPN enabled. In this case, upon removal of the EVPN destination, the port is brought operationally down with the LinkLossFwd flag; however, the AD per-EVI route for the SAP is still advertised (the SAP is kept operationally up).

The no form of this command disables LLF on an Ethernet port.

Default

no llf

Platforms

7705 SAR Gen 2

Context

[Tree] (candidate load)

Full Context

candidate load

Description

This command loads a previously saved candidate configuration into the current candidate. The edit point will be set to the end of the loaded configuration lines. The candidate configuration cannot be modified while a load is in progress.

Default

If the candidate is empty then a load without any of the optional parameters (such as overwrite, and so on) will load the file-url into the candidate. If the candidate is not empty then one of the options, such as overwrite, insert, and so on, must be specified.

Parameters

file-url

Specifies the directory and filename to load.

overwrite

Discards the contents of the current candidate and replace it with the contents of the file.

insert

Inserts the contents of the file at the current edit point.

append

Inserts the contents of the file at the end of the current candidate.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>epipe load-balancing)

Full Context

configure service epipe load-balancing

Description

This command enables the load-balancing context to configure interface per-flow load balancing options that will apply to traffic entering this interface and egressing over a LAG/ECMP on system-egress. This is a per interface setting. For load-balancing options that can also be enabled on the system level, the options enabled on the interface level overwrite system level configurations.

Default

not applicable

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>template>vpls-template load-balancing)

Full Context

configure service template vpls-template load-balancing

Description

This command enables the load-balancing context to configure interface per-flow load balancing options that will apply to traffic entering this interface and egressing over a LAG/ECMP on system-egress. This is a per interface setting. For load-balancing options that can also be enabled on the system level, the options enabled on the interface level overwrite system level configurations.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if load-balancing)

Full Context

configure service ies interface load-balancing

Description

This command enables the load-balancing context to configure interface per-flow load balancing options that will apply to traffic entering this interface and egressing over a LAG/ECMP on system-egress. This is a per interface setting. For load balancing options that can also be enabled on the system level, the options enabled on the interface level overwrite system level configurations.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>nw-if load-balancing)

Full Context

configure service vprn network-interface load-balancing

Description

This command enables the load-balancing context to configure interface per-flow load balancing options that will apply to traffic entering this interface and egressing over a LAG/ECMP on system-egress. This is a per interface setting. For load-balancing options that can also be enabled on the system level, the options enabled on the interface level overwrite system level configurations.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>if load-balancing)

Full Context

configure router interface load-balancing

Description

This command enables the load-balancing context to configure interface per-flow load balancing options that will apply to traffic entering this interface and egressing over a LAG/ECMP on system-egress. This is a per interface setting. For load-balancing options that can also be enabled on the system level, the options enabled on the interface level overwrite system level configurations.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system load-balancing)

Full Context

configure system load-balancing

Description

This command enables the load-balancing context to configure the interface per-flow load balancing options that will apply to traffic entering this interface and egressing over a LAG/ECMP on system-egress. This is a per interface setting. For load-balancing options that can also be enabled on the system level, the options enabled on the interface level overwrite system level configurations.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet load-balancing-algorithm)

Full Context

configure port ethernet load-balancing-algorithm

Description

This command specifies the load balancing algorithm to be used on this port.

In the default mode, no load-balancing-algorithm, the port inherits the global settings. The value is not applicable for ports that do not pass any traffic.

The configuration of load-balancing-algorithm at logical port level has three possible values:

• include-l4 — Enables inherits system-wide settings including Layer 4 source and destination port value in hashing algorithm.

• exclude-l4 — Layer 4 source and destination port value will not be included in hashing.

• no load-balancing-algorithm — Inherits system-wide settings.

The hashing algorithm addresses finer spraying granularity where many hosts are connected to the network. To address more efficient traffic distribution between network links (forming a LAG group), a hashing algorithm extension takes into account Layer 4 information (src/dst L4-protocol port). The hashing index can be calculated according to the following algorithm:

If [(TCP or UDP traffic) & enabled]

hash (<TCP/UDP ports>, <IP addresses>)

else if (IP traffic)

hash (<IP addresses>)

else

hash (<MAC addresses>)

endif

This algorithm will be used in all cases where IP information in per-packet hashing is included (refer to "Traffic Load Balancing Options” in the 7705 SAR Gen 2 Interface Configuration Guide). However the Layer 4 information (TCP/UDP ports) will not be used in the following cases:

• fragmented packets

Default

no load-balancing-algorithm

Parameters

option

Specifies the load balancing algorithm to be used on this port.

Values

include-l4 — Specifies that the source and destination ports are used in the hashing algorithm.exclude-l4 — Specifies that the source and destination ports are not used in the hashing algorithm.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>static-route-entry>next-hop load-balancing-weight)

Full Context

configure service vprn static-route-entry next-hop load-balancing-weight

Description

This command configures a weighted ECMP load-balancing weight for a static route next-hop.

If all of the ECMP next-hops of a static route have a configured load-balancing-weight then packets matching the route are sprayed according to the relative weights. In other words, the next-hop interface with the largest load-balancing weight should receive the most forwarded traffic if weighted ECMP is applicable.

The no form of this command disables weighted ECMP for the interface and effectively disables weighted ECMP for the entire static route.

Parameters

value

Specifies the cost metric value.

Values

0 to 4294967295

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>ospf>area>if load-balancing-weight)

[Tree] (config>service>vprn>ospf3>area>if load-balancing-weight)

Full Context

configure service vprn ospf area interface load-balancing-weight

configure service vprn ospf3 area interface load-balancing-weight

Description

This command configures the weighted ECMP load-balancing weight for an IS-IS, OSPF, and OSPF3 interface. If the interface becomes an ECMP next hop for an IPv4 or IPv6 route, and all the other ECMP next hops are interfaces with configured (non-zero) load-balancing weights, then the traffic distribution over the ECMP interfaces is proportional to the weights. This means that the interface with the largest load-balancing weight receives the most forwarded traffic if weighted ECMP is applicable.

The no form of this command disables weighted ECMP for the interface which effectively disables weighted ECMP for any IP prefix that has this interface as a next hop.

Default

no load-balancing-weight

Parameters

weight

Specifies the load balancing weight.

Values

1 to 4294967295

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>isis>if load-balancing-weight)

Full Context

configure service vprn isis interface load-balancing-weight

Description

This command configures the weighted ECMP load-balancing weight for an IS-IS interface of the VPRN. If the interface becomes an ECMP next-hop for IPv4 or IPv6 route and all the other ECMP next-hops are interfaces with configured (non-zero) load-balancing weights, then the traffic distribution over the ECMP interfaces is proportional to the weights. In other words, the interface with the largest load-balancing-weight should receive the most forwarded traffic if weighted ECMP is applicable.

The no form of this command disables weighted ECMP for the interface and, therefore, effectively disables weighted ECMP for any IP prefix that has this interface as a next-hop.

Default

no load-balancing-weight

Parameters

weight

Specifies the load balancing weight.

Values

0 to 4294967295

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>ldp>if-params>if load-balancing-weight)

Full Context

configure router ldp interface-parameters interface load-balancing-weight

Description

This command configures the load balancing weight for the LDP interface. The load balancing weight, normalized to 64, is used for weighted ECMP of LDP labeled packets over direct network IP interfaces.

If the interface becomes an ECMP next hop for an LDP FEC, and all the other ECMP next hops are interfaces with configured (non-zero) load-balancing weights, then the traffic distribution over the ECMP interfaces is proportional to the normalized weight with a granularity of 64.

If one or more of the LDP interfaces in the ECMP set does not have a configured load-balancing weight, then the system falls back to ECMP.

The no form of this command removes the load balancing weight for the LDP interface.

Parameters

weight

Specifies the load balancing weight value.

Values

0 to 4294967295

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>mpls>lsp load-balancing-weight)

Full Context

configure router mpls lsp load-balancing-weight

Description

This command assigns a weight to an MPLS LSP for use in the weighted load-balancing, or weighted ECMP, over MPLS feature.

Parameters

weight

Specifies a 32-bit integer representing the weight of the LSP.

Values

0 to 4294967295

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>static-route-entry>next-hop load-balancing-weight)

Full Context

configure router static-route-entry next-hop load-balancing-weight

Description

This command configures a weighted ECMP load-balancing weight for a static route next-hop.

If all of the ECMP next-hops of a static route have a configured load-balancing-weight then packets matching the route are sprayed according to the relative weights. In other words, the next-hop interface with the largest load-balancing weight should receive the most forwarded traffic if weighted ECMP is applicable.

The no form of this command disables weighted ECMP for the interface and effectively disables weighted ECMP for the entire static route.

Parameters

value

Specifies the load balancing weight value.

Values

0 to 4294967295

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>isis>interface load-balancing-weight)

Full Context

configure router isis interface load-balancing-weight

Description

This command configures the weighted ECMP load-balancing weight for an IS-IS interface. If the interface becomes an ECMP next hop for an IPv4 or IPv6 route, and all the other ECMP next hops are interfaces with configured (non-zero) load-balancing weights, then the traffic distribution over the ECMP interfaces is proportional to the weights. In other words, the interface with the largest load-balancing weight should receive the most forwarded traffic if weighted ECMP is applicable.

The no form of this command disables weighted ECMP for the interface and therefore effectively disables weighted ECMP for any IP prefix that has this interface as a next hop.

Default

no load-balancing-weight

Parameters

value

0 to 4294967295

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>ospf3>area>if load-balancing-weight)

[Tree] (config>router>ospf>area>if load-balancing-weight)

Full Context

configure router ospf3 area interface load-balancing-weight

configure router ospf area interface load-balancing-weight

Description

This command configures the weighted ECMP load-balancing weight for an OSPF or OSPF3 interface. If the interface becomes an ECMP next hop for an IPv4 or IPv6 route, and all the other ECMP next hops are interfaces with configured (non-zero) load-balancing weights, then the traffic distribution over the ECMP interfaces is proportional to the weights. This means that the interface with the largest load-balancing weight receives the most forwarded traffic if weighted ECMP is applicable.

The no form of this command disables weighted ECMP for the interface which effectively disables weighted ECMP for any IP prefix that has this interface as a next hop.

Default

no load-balancing-weight

Parameters

weight

Specifies the load balancing weight.

Values

1 to 4294967295

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>ttl-propagate local)

Full Context

configure service vprn ttl-propagate local

Description

This command overrides the global configuration of the TTL propagation for locally generated packets which are forwarded over a MPLS LSPs in a given VPRN service context.

The global configuration is performed under config>router>ttl-propagate>vprn-local.

The default behavior for a given VPRN instance is to inherit the global configuration for the same command. The user can explicitly set the default behavior by configuring the inherit value

Default

local inherit

Parameters

inherit

Specifies the TTL propagation behavior is inherited from the global configuration under config>router>ttl-propagate>vprn-local.

none

Specifies the TTL of the IP packet is not propagated into the VC label or labels in the transport label stack.

vc-only

Specifies the TTL of the IP packet is propagated into the VC label and not into the labels in the transport label stack.

all

Specifies the TTL of the IP packet is propagated into the VC label and all labels in the transport label stack.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>ipsec>ts-list local)

Full Context

configure ipsec ts-list local

Description

Commands in this context configure local TS-list parameters. The TS-list is the traffic selector of the local system, such as TSr, when the system acts as an IKEv2 responder.

Platforms

7705 SAR-Hx, 7705 SAR-Mx, 7705 SAR-1

Context

[Tree] (config>service>vprn>bgp>group local-address)

[Tree] (config>service>vprn>bgp>group>neighbor local-address)

Full Context

configure service vprn bgp group local-address

configure service vprn bgp group neighbor local-address

Description

Configures the local IP address used by the group or neighbor when communicating with BGP peers.

Outgoing connections use the local-address as the source of the TCP connection when initiating connections with a peer.

When a local address is not specified, the OS uses the system IP address when communicating with IBGP peers and uses the interface address for directly connected EBGP peers. This command is used at the neighbor level to revert to the value defined under the group level.

The no form of this command removes the configured local-address for BGP.

The no form of this command used at the group level reverts to the value defined at the global level.

The no form of this command used at the neighbor level reverts to the value defined at the group level.

Parameters

no local-address

The router ID is used when communicating with IBGP peers and the interface address is used for directly connected EBGP peers.

ip-address

The local address expressed in dotted decimal notation. Allowed values are a valid routable IP address on the router, either an interface or system IP address.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>pcep>pcc local-address)

Full Context

configure router pcep pcc local-address

Description

This command configures the local IPv4 address of the PCEP speaker.

The PCEP protocol operates over TCP using destination TCP port 4189. The PCE client (PCC) always initiates the connection. After the user configures the PCEP local IPv4 address and the peer IPv4 address on the PCC, the latter initiates a TCP connection to the PCE. If both a local IPv4 and a local IPv6 address are configured, the connection uses the local address that is the same family as the peer address. When the connection is established, the PCC and PCE exchange OPEN messages, which initializes the PCEP session and exchanges the session parameters to be negotiated.

By default, the PCC attempts to reach the remote PCE address out of band using the management port. If it cannot, it attempts to reach the remote PCE address in band. The user can change the configuration of the peer to attempt connecting in band only or out of band only. When the session comes up out of band, the management IP address is used as the local address. The local IPv4 address configured by the user is only used for in-band sessions and is otherwise ignored.

The no form of the command removes the configured local address of the PCEP speaker.

Parameters

ip-address

Specifies the IP address of the PCEP speaker to be used for in-band sessions.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>origin-validation>rpki-session local-address)

Full Context

configure router origin-validation rpki-session local-address

Description

This command configures the local address to use for setting up the TCP connection used by an RPKI-Router session. The default local-address is the outgoing interface IPv4 or IPv6 address. The local-address cannot be changed without first shutting down the session.

Default

no local-address

Parameters

ip-address

Specifies an IPv4 address or an IPv6 address.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>group>neighbor local-address)

[Tree] (config>router>bgp>group local-address)

Full Context

configure router bgp group neighbor local-address

configure router bgp group local-address

Description

This command configures the local IP address used by the group or neighbor when communicating with BGP peers.

Outgoing connections use the local-address as the source of the TCP connection when initiating connections with a peer.

When a local address is not specified, the router uses the system IP address when communicating with IBGP peers and uses the interface address for directly connected EBGP peers. This command is used at the neighbor level to revert to the value defined under the group level.

When set to a router interface, the local-address inherits the primary IPv4 or IPv6 address of the router interface depending on whether BGP is configured for IPv4 or IPv6. If the corresponding IPv4 or IPv6 address is not configured on the router interface, the BGP sessions that have this interface set as the local-address are kept down until an interface address is configured on the router interface.

The no form of this command removes the configured local-address for BGP.

The no form of this command used at the group level returns the configuration to the value defined at the global level.

The no form of this command used at the neighbor level returns the configuration to the value defined at the group level.

Default

no local-address

Parameters

ip-address

Specifies the local address expressed in dotted decimal notation. Allowed value is a valid routable IP address on the router, either an interface or system IP address.

Values

ipv4-address:

• a.b.c.d (host bits must be 0)

ipv6-address

Specifies the local address expressed in dotted decimal notation. Allowed value is a valid routable IPv6 address on the router, either an interface or system IPv6 address.

Values

ipv6-address:

• x:x:x:x:x:x:x:x (eight 16-bit pieces)

• x:x:x:x:x:x:d.d.d.d

• x: [0 to FFFF]H

• d: [0 to 255]D

ip-int-name

Specifies the IP interface name whose address the local address will inherit. The interface can be any network interface configured on the system.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>ies>if>sap>ipsec-gw local-address-assignment)

[Tree] (config>service>vprn>if>sap>ipsec-gw local-address-assignment)

Full Context

configure service ies interface sap ipsec-gw local-address-assignment

configure service vprn interface sap ipsec-gw local-address-assignment

Description

Commands in this context configure local address assignments for the IPsec gateway.

Platforms

7705 SAR-Hx, 7705 SAR-Mx, 7705 SAR-1

Context

[Tree] (config>ipsec>client-db>client local-address-assignment)

Full Context

configure ipsec client-db client local-address-assignment

Description

Commands in this context configure the local address assignment information.

Platforms

7705 SAR-Hx, 7705 SAR-Mx, 7705 SAR-1

Context

[Tree] (config>router>pcep>pcc local-address-ipv6)

Full Context

configure router pcep pcc local-address-ipv6

Description

This command configures the local IPv6 address of the PCEP speaker.

The PCEP protocol operates over TCP using destination TCP port 4189. The PCE client (PCC) always initiates the connection. After the user configures the PCEP local IPv6 address and the peer IPv6 address on the PCC, the latter initiates a TCP connection to the PCE. If both a local IPv4 and a local IPv6 address are configured, the connection uses the local address that is the same family as the peer address. When the connection is established, the PCC and PCE exchange OPEN messages, which initializes the PCEP session and exchanges the session parameters to be negotiated.

By default, the PCC attempts to reach the remote PCE address out of band using the management port. If it cannot, it attempts to reach the remote PCE address in-band. The user can change the configuration of the peer to attempt connecting in band only or out of band only. When the session comes up out of band, the management IP address is used as the local address. The local IPv6 address configured by the user is only used for in-band sessions and is otherwise ignored.

The no form of the command removes the configured local address of the PCEP speaker.

Parameters

ipv6-address

Specifies the IP address of the PCEP speaker to be used for in-band sessions.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vpls local-age)

[Tree] (config>service>template>vpls-template local-age)

Full Context

configure service vpls local-age

configure service template vpls-template local-age