l Commands

Context

[Tree] (config>subscr-mgmt>wlan-gw>tunnel-query>type l2)

Full Context

configure subscriber-mgmt wlan-gw tunnel-query type l2

Description

This command enables matching on Layer 2 tunnels.

The no form of this command disables matching on Layer 2 access points, unless no other tunnel type specifier is configured.

Default

no l2

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>wlan-gw>ue-query>state l2)

Full Context

configure subscriber-mgmt wlan-gw ue-query state l2

Description

This command enables matching on UEs in a Layer 2 wholesale state.

The no form of this command disables matching on UEs in a Layer 2 wholesale state, unless all state matching is disabled.

Default

no l2

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vpls>sap>pfcp l2-access-id-alias)

Full Context

configure service vpls sap pfcp l2-access-id-alias

Description

This command defines a Layer 2 access ID alias for the capture SAP. It replaces the default underlying port-based or LAG-based Layer 2 access ID. Different capture SAPs on the same underlying port or LAG can have different Layer 2 access ID aliases.

The no form of the command removes the configuration.

Parameters

string

Specifies the Layer 2 access ID alias, up to 32 characters.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw l2-access-points)

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw l2-access-points)

Full Context

configure service ies subscriber-interface group-interface wlan-gw l2-access-points

configure service vprn subscriber-interface group-interface wlan-gw l2-access-points

Description

Commands in this context configure Layer 2 access points in WLAN gateway group interfaces.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>l2-access-points l2-ap)

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>l2-access-points l2-ap)

Full Context

configure service vprn subscriber-interface group-interface wlan-gw l2-access-points l2-ap

configure service ies subscriber-interface group-interface wlan-gw l2-access-points l2-ap

Description

This command adds a specific SAP where Layer 2 WLAN gateway aggregation is performed. The following SAPs are supported:

• Ethernet

• LAG

• MPLS pseudowire SDPs

This command can be repeated multiple times to create multiple Layer 2 access points.

The no form of this command removes the Layer 2 access point. This is only allowed if the Layer 2 access point SAP is shutdown.

Parameters

sap-id

Specifies SAP to be created.

create

Keyword used to create the Layer 2 WLAN gateway aggregation instance. The create keyword requirement can be enabled/disabled in the environment>create context.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw l2-ap-auto-sub-id-fmt)

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw l2-ap-auto-sub-id-fmt)

Full Context

configure service ies subscriber-interface group-interface wlan-gw l2-ap-auto-sub-id-fmt

configure service vprn subscriber-interface group-interface wlan-gw l2-ap-auto-sub-id-fmt

Description

This command configures the contents of the auto-generated subscriber ID when the ipoe-sub-id-key command is set to include sap-id and the def-sub-id command is configured with use-auto-id. The VLANs must be configured so that the subscriber ID length is not exceeded.

This command can include either the SAP or the SAP + AP delimiting tags.

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

Default

l2-ap-auto-sub-id-fmt include-ap-tags

Parameters

include-ap-tags

Specifies that the SAP + AP delimiting tags is used.

sap-only

Specifies that the SAP only is used.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw l2-ap-encap-type)

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw l2-ap-encap-type)

Full Context

configure service ies subscriber-interface group-interface wlan-gw l2-ap-encap-type

configure service vprn subscriber-interface group-interface wlan-gw l2-ap-encap-type

Description

This parameter specifies the number of AP identifying VLAN tags for an AP. This is the default value that can be overridden per SAP. This value must be at least equal to the number of VLANs configured in the SAP or enabling a SAP will fail.

A SAP VLAN is explicitly configured, for example l2-ap 1/1/1:25. Other VLANs on the same port can still be used in other contexts.

The number of VLAN tags Epiped to the WLAN gateway IOM equals the l2-ap-encap-type minus the encaps of the SAP. Upon receipt of a packet, these VLANs are stored as a Layer 2 tunnel identifier, and are only used in context of WLAN gateway.

The no form of this command sets the default value.

Default

l2-ap-encap-type null

Parameters

null

Both the SAP and the AP are not VLAN-tagged.

dot1q

Either the AP or the SAP uses one VLAN tag.

qinq

Up to two VLAN tags are used by the AP or SAP.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vprn>nat>inside l2-aware)

Full Context

configure service vprn nat inside l2-aware

Description

Commands in this context configure parameters specific to Layer2-Aware NAT.

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>router>nat>inside l2-aware)

Full Context

configure router nat inside l2-aware

Description

Commands in this context configure Layer2-Aware NAT.

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>nat>fwd l2-aware)

Full Context

configure service nat port-forwarding l2-aware

Description

This command creates NAT static port forwards for Layer2-Aware subscribers. The ESM subscriber must be present in the system before this command is executed. The no form of the command deletes NAT static port forwards for Layer2-Aware subscribers.

Parameters

subscriber sub-ident-string

This mandatory parameter specifies the ESM subscriber for which the SPF is to be created; ESM subscriber must be present in the system before the SPF can be created.

ip ip-address

This mandatory parameter specifies the source IPv4/IPv6 address for which SPF will be created.

protocol {tcp | udp}

This mandatory parameter specifies the protocol to use, either TCP or UDP.

port port

This optional parameter specifies a source port.

Values

1 to 65535

outside-ip ipv4-address

This mandatory parameter specifies the outside IPv4 address. If the outside IPv4 address is specified, then all other optional parameters become mandatory.

outside-port port

This optional parameter specifies the outside port.

nat-policy policy-name

If multiple NAT policies are used inside the routing context, then the NAT policy should be specified in the SPF request so the SPF is created in the correct NAT pool. Otherwise, the default NAT policy from the inside routing context will be used.

member member-id

This optional parameter should not be used by the operator. It is used only if the command is replayed via the exec command or at boot-config. The member ID indicates the identifier of the NAT ISA group member associated with this NAT subscriber.

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>dhcp l2-aware-ip-address)

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>dhcp l2-aware-ip-address)

Full Context

configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range dhcp l2-aware-ip-address

configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range dhcp l2-aware-ip-address

Description

This command configures the Layer2-Aware NAT inside IP address to be assigned via DHCP on the WLAN-GW ISA.

If the from-pool parameter is specified instead of an IPv4 address, a unique address is allocated to each UE. The pool used is managed by the dhcpv4-nat pool manager, configured under the same subscriber interface. This option is only available when auth-on-dhcp is also configured.

The no form of this command reverts to the default.

Parameters

ip-address

Specifies the Layer2-Aware NAT inside IP address.

from-pool

Specifies that the Layer2-Aware IP address is allocated from a pool.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>filter>ip-filter>entry>action l2-aware-nat-bypass)

Full Context

configure filter ip-filter entry action l2-aware-nat-bypass

Description

This command enables bypassing NAT for packets pertaining to L2-Aware hosts and matching this entry. This action is only applicable to L2-Aware NAT subscribers and it must be configured together with action forward. Traffic identified in the match condition bypasses L2-Aware NAT. A common use case is to bypass NAT for on-net destinations (within the customer network).

Traffic that is not classified for bypass is automatically diverted to L2-Aware NAT, unless it is explicitly configured in the IP filter to be dropped.

For selective NAT bypass to take effect, in addition to the IP filter configuration, the L2-Aware NAT subscriber must be specifically enabled for selective bypass via the nat-allow-bypass configuration option in the NAT CLI node in the SLA profile.

The no form of this command automatically diverts traffic to L2-Aware NAT, unless it is explicitly configured in the IP filter to be dropped.

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>li>li-source>nat l2-aware-sub)

Full Context

configure li li-source nat l2-aware-sub

Description

This command configures a Layer-2-Aware subscriber source.

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

Parameters

sub-ident-string

Specifies a source name.

Platforms

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>wlan-gw>tunnel-query l2-inner-vlan)

Full Context

configure subscriber-mgmt wlan-gw tunnel-query l2-inner-vlan

Description

This command enables matching on a Layer 2 access point with a specified C-VLAN.

The no form of this command disables matching on a C-VLAN.

Default

no l2-inner-vlan

Parameters

q-tag

Specifies the q-tag for the C-VLAN.

Values

0 to 4095

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>cflowd>collector>export-filter>family l2-ip)

Full Context

configure cflowd collector export-filter family l2-ip

Description

This command filters Layer 2 IP flow data from being sent to the associated collector.

The no form of this command removes the filter, allowing Layer 2 IP flow data to be sent to the associated collector.

Default

no l2-ip

Platforms

All

Context

[Tree] (config>subscr-mgmt>wlan-gw>tunnel-query l2-outer-vlan)

Full Context

configure subscriber-mgmt wlan-gw tunnel-query l2-outer-vlan

Description

This command enables matching on a Layer 2 access point with a specified S-VLAN.

The no form of this command disables matching on an S-VLAN.

Default

no l2-outer-vlan

Parameters

q-tag

Specifies the q-tag for the S-VLAN.

Values

0 to 4095

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>nat>firewall-policy l2-outside)

[Tree] (config>service>nat>nat-policy l2-outside)

Full Context

configure service nat firewall-policy l2-outside

configure service nat nat-policy l2-outside

Description

This command configures a NAT policy to be used with a Layer 2 outside service instead of a Layer 3 outside service. This command and the pool command are mutually exclusive.

Default

no l2-outside

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

• configure service nat firewall-policy l2-outside

7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR

• configure service nat nat-policy l2-outside

Context

[Tree] (config>subscr-mgmt>wlan-gw>tunnel-query l2-sap)

Full Context

configure subscriber-mgmt wlan-gw tunnel-query l2-sap

Description

This command enables matching on Layer 2 access points active on the specified SAP.

The no form of this command disables matching on the SAP.

Default

no l2-sap

Parameters

sap-id

Specifies the SAP ID. For details on SAP ID parameter values, refer to section Monitor CLI Commands in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Basic System Configuration Guide.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range l2-service)

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range l2-service)

Full Context

configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range l2-service

configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range l2-service

Description

This command specifies the VPLS service used for L2 wholesale. When such a service is configured no other configuration is allowed under the vlan-range.

The no form of this command removes the L2 wholesale service, this is only allowed if the l2-service node is shut down.

Parameters

service-id

Specifies the VPLS service ID to use for Layer 2 wholesale.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

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

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

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

Full Context

configure service vpls sap l2pt-termination

configure service template vpls-sap-template l2pt-termination

configure service vpls spoke-sdp 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

All

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

All

Context

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host l2tp)

Full Context

configure subscriber-mgmt local-user-db ppp host l2tp

Description

Commands in this context configure L2TP parameters for the host.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>router l2tp)

Full Context

configure router l2tp

Description

Commands in this context configure L2TP parameters. L2TP extends the PPP model by allowing Layer 2 and PPP endpoints to reside on different devices interconnected by a packet-switched network.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (debug>router>l2tp>group>packet l2tp)

[Tree] (debug>router l2tp)

[Tree] (debug>router>l2tp>assignment-id>packet l2tp)

[Tree] (debug>router>l2tp>packet l2tp)

[Tree] (debug>router>l2tp>peer>packet l2tp)

Full Context

debug router l2tp group packet l2tp

debug router l2tp

debug router l2tp assignment-id packet l2tp

debug router l2tp packet l2tp

debug router l2tp peer packet l2tp

Description

This command sets debugging for L2TP packets.

The no form of this command removes the settings of debugging for L2TP packet.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

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

All

Context

[Tree] (debug>service>id>ppp>event l2tp)

Full Context

debug service id ppp event l2tp

Description

This command enables PPP L2TP event debug.

Parameters

terminate-only

Enables debug for local terminated PPP session.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>wlan-gw>tunnel-query>type l2tp)

Full Context

configure subscriber-mgmt wlan-gw tunnel-query type l2tp

Description

This command enables matching on L2TP tunnels.

The no form of this command disables matching on L2TP tunnels, unless no other tunnel type specifier is configured.

Default

no l2tp

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vprn l2tp)

Full Context

configure service vprn l2tp

Description

Commands in this context configure L2TP parameters. L2TP extends the PPP model by allowing Layer 2 and PPP endpoints to reside on different devices interconnected by a packet-switched network.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (debug>oam>build-packet>packet>field-override>header l2tp)

[Tree] (config>test-oam>build-packet>header l2tp)

Full Context

debug oam build-packet packet field-override header l2tp

configure test-oam build-packet header l2tp

Description

This command causes the associated header to be defined as an L2TP header template and enables the context to define the L2TP parameters.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>aaa l2tp-accounting-policy)

Full Context

configure aaa l2tp-accounting-policy

Description

This command configures an L2TP accounting policy.

The no form of this command removes the policy-name from the configuration.

Parameters

policy-name

Specifies a policy name.

create

This keyword is required when first creating the configuration context. Once the context is created, it is possible to navigate into the context without the create keyword.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>sla-profile>session-limits l2tp-lns)

[Tree] (config>subscr-mgmt>sub-profile>session-limits l2tp-lns)

Full Context

configure subscriber-mgmt sla-profile session-limits l2tp-lns

configure subscriber-mgmt sub-profile session-limits l2tp-lns

Description

This command configures the maximum number of L2TP LNS sessions per SLA profile instance or per subscriber.

The no form of this command removes the maximum number of L2TP LNS sessions limit.

Parameters

max-nr-of-sessions

Specifies the maximum number of L2TP LNS sessions.

Values

0 to 131071

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

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

Full Context

configure system load-balancing l2tp-load-balancing

Description

This command enables the inclusion of the L2TPv2 session ID into the load-balancing hash algorithm to induce more variation and better load distribution over available links and next-hops.

The no form of this command disables the inclusion of the session-id.

Platforms

All

Context

[Tree] (config>subscr-mgmt>sub-profile>session-limits l2tp-lts)

[Tree] (config>subscr-mgmt>sla-profile>session-limits l2tp-lts)

Full Context

configure subscriber-mgmt sub-profile session-limits l2tp-lts

configure subscriber-mgmt sla-profile session-limits l2tp-lts

Description

This command configures the maximum number of L2TP LTS sessions per SLA profile instance or per subscriber.

The no form of this command removes the maximum number of L2TP LTS sessions limit.

Parameters

max-nr-of-sessions

Specifies the maximum number of L2TP LTS sessions.

Values

0 to 131071

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>sub-profile>session-limits l2tp-overall)

[Tree] (config>subscr-mgmt>sla-profile>session-limits l2tp-overall)

Full Context

configure subscriber-mgmt sub-profile session-limits l2tp-overall

configure subscriber-mgmt sla-profile session-limits l2tp-overall

Description

This command configures the maximum number of L2TP sessions per SLA profile instance or per subscriber.

The no form of this command removes the maximum number of L2TP sessions limit.

Parameters

max-nr-of-sessions

Specifies the maximum number of L2TP sessions.

Values

0 to 131071

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>redundancy>multi-chassis>peer>sync>track-srrp-instances>track-srrp l2tp-tunnel-id-range)

Full Context

configure redundancy multi-chassis peer sync track-srrp-instances track-srrp l2tp-tunnel-id-range

Description

This command sets the tunnel-id range that is used to allocate a new tunnel-id for a tunnel for which multi-chassis redundancy is configured to this MCS peer.

The no form of this command reverts to the default.

Parameters

start l2tp-tunnel-id

Specifies the start of the range of L2TP tunnel identifiers that can be allocated by L2TP on this system, to be synchronized with Multi Chassis Redundancy Synchronization (MCS).

Values

1 to 16383

end l2tp-tunnel-id

Specifies the end of the range of L2TP tunnel identifiers that can be allocated by L2TP on this system, to be synchronized with Multi Chassis Redundancy Synchronization (MCS).

Values

1 to 16383

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>router>l2tp l2tpv3)

[Tree] (config>service>vprn>l2tp>group>tunnel l2tpv3)

[Tree] (config>router>l2tp>group>tunnel l2tpv3)

[Tree] (config>service>vprn>l2tp>group l2tpv3)

[Tree] (config>router>l2tp>group l2tpv3)

[Tree] (config>service>vprn>l2tp l2tpv3)

Full Context

configure router l2tp l2tpv3

configure service vprn l2tp group tunnel l2tpv3

configure router l2tp group tunnel l2tpv3

configure service vprn l2tp group l2tpv3

configure router l2tp group l2tpv3

configure service vprn l2tp l2tpv3

Description

Commands in this context configure L2TPv3 parameters.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>epipe>spoke-sdp>ingress l2tpv3)

[Tree] (config>service>epipe>spoke-sdp>egress l2tpv3)

Full Context

configure service epipe spoke-sdp ingress l2tpv3

configure service epipe spoke-sdp egress l2tpv3

Description

Commands in this context configure L2TPv3 spoke SDPs for Epipe services.

Platforms

All

Context

[Tree] (config>mirror>mirror-dest>spoke-sdp>ingress l2tpv3)

[Tree] (config>mirror>mirror-dest>spoke-sdp>egress l2tpv3)

[Tree] (config>mirror>mirror-dest>remote-src>spoke-sdp>ingress l2tpv3)

Full Context

configure mirror mirror-dest spoke-sdp ingress l2tpv3

configure mirror mirror-dest spoke-sdp egress l2tpv3

configure mirror mirror-dest remote-source spoke-sdp ingress l2tpv3

Description

Commands in this context configure an RX/TX cookie for L2TPv3 egress spoke SDP or for the remote-source ingress spoke SDP.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

• configure mirror mirror-dest spoke-sdp ingress l2tpv3

All

• configure mirror mirror-dest spoke-sdp egress l2tpv3
• configure mirror mirror-dest remote-source spoke-sdp ingress l2tpv3

Context

[Tree] (config>service>vpls>sap l2tpv3-session)

[Tree] (config>service>epipe>sap l2tpv3-session)

Full Context

configure service vpls sap l2tpv3-session

configure service epipe sap l2tpv3-session

Description

This command creates the configuration context to define the L2TPv3 tunnel parameters.

The no form of this command deletes the L2TPv3 configuration context.

Parameters

create

This keyword is mandatory while creating a L2TPv3 session.

Platforms

All

Context

[Tree] (config>subscr-mgmt>wlan-gw>tunnel-query>ue-state l2w)

Full Context

configure subscriber-mgmt wlan-gw tunnel-query ue-state l2w

Description

This command enables matching on tunnels with L2W UEs.

The no form of this command disables matching on L2W UEs, unless UE state matching is disabled altogether.

Default

no l2w

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

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

All

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 7450 ESS, 7750 SR, 7950 XRS, and VSR Interface Configuration Guide). However, the Layer 4 information (TCP/UDP ports) will not be used for fragmented packets.

Default

no l4-load-balancing

Platforms

All

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 maskrespectively.

Values

1 to 65535 (decimal)

Default

65535 (exact match)

Platforms

All

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

All

Context

[Tree] (config>test-oam>build-packet>header>mpls label)

[Tree] (debug>oam>build-packet>packet>field-override>header>mpls label)

Full Context

configure test-oam build-packet header mpls label

debug oam build-packet packet field-override header mpls label

Description

This command defines the MPLS value to be used in the MPLS header.

The no form of this command removes the label value.

Default

label 0

Parameters

label

Specifies the MPLS label to be used in the MPLS header.

Values

0 to 1048575

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (debug>router>rib-api label)

Full Context

debug router rib-api label

Description

This command enables debugging for the specified RIB-API label.

Parameters

label

Specifies the label of the specified RIB-API entry.

Values

32 to 1048575

Platforms

All

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

All

Context

[Tree] (conf>router>segment-routing>srv6>loc>static-function label-block)

Full Context

configure router segment-routing segment-routing-v6 locator static-function label-block

Description

This command configures a reserved label block name to be used in the termination of services on the SRv6 FPE.

Static values of the service SID function are mapped to label values drawn from this reserved label block. A static function value of 1 maps to the first label in this label block and so on.

Dynamic values of service SID function are mapped to label values drawn from the dynamic label range.

An End or End.X function does not map to a label value.

The no form of this command removes the label block name from the configuration.

Default

no label-block

Parameters

name

Specifies a reserved label block name, up to 64 characters.

Platforms

7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR

Context

[Tree] (config>router>segment-routing>srv6>locator label-block)

Full Context

configure router segment-routing segment-routing-v6 locator label-block

Description

This command configures a reserved label block name for the termination of services on the SRv6 FPE.

When an operator configures this block, the router maps both static and dynamic values of the service SID functions to label values drawn from the reserved label block. This reserved block and the block defined under static-function are mutually exclusive. The configuration of this block does not constrain the configuration of a particular function length.

An End or End.X function does not map to a label value.

The no form of this command removes the label block name from the configuration.

Default

no label-block

Parameters

name

Specifies a reserved label block name, up to 64 characters.

Platforms

7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR

Context

[Tree] (conf>router>sr>srv6>ms>block label-block)

Full Context

configure router segment-routing segment-routing-v6 micro-segment block label-block

Description

This command associates a pre-configured reserved label block with the micro-SID block.

The no form of this command disassociates the reserved label block.

Default

no label-block

Parameters

name

Specifies a reserved label block name, up to 64 characters.

Platforms

7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR

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 7450 ESS 7750 SR 7950 XRS VSR Unicast Routing Protocols User 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

All

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.

Values

1 to 16, none, multipaths

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

All

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

All

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 7450 ESS 7750 SR 7950 XRS VSR Unicast Routing Protocols User 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

All

Context

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

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

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

Full Context

configure router bgp group neighbor add-paths label-ipv6

configure router bgp group 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.

Values

1 to 16, none, multipaths

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

All

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

All

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

All

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

All

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

All

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

All

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

All

Context

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

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

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

Full Context

configure service vprn bgp group label-preference

configure service vprn bgp group neighbor label-preference

configure service vprn bgp 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

All

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

All

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

All

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

All

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

All

Context

[Tree] (config>system>ip>mpls label-stack-statistics-count)

Full Context

configure system ip mpls label-stack-statistics-count

Description

This command enables the system to collect traffic statistics on the specified number of labels of the MPLS label stack.

The no form of this command disables the collecting of traffic statistics.

Default

label-stack-statistics-count 1

Parameters

label-stack-statistics-count

Specifies the number of labels on which the system can collect statistics.

Values

1, 2

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

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 of 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

All

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

All

Context

[Tree] (config>subscr-mgmt>sub-profile>host-limits lac-overall)

[Tree] (config>subscr-mgmt>sla-profile>host-limits lac-overall)

Full Context

configure subscriber-mgmt sub-profile host-limits lac-overall

configure subscriber-mgmt sla-profile host-limits lac-overall

Description

This command configures the maximum number of L2TP LAC hosts per SLA profile instance or per subscriber.

The no form of this command removes the maximum number of L2TP LAC hosts limit.

Parameters

max-nr-of-hosts

Specifies the maximum number of L2TP LAC hosts.

Note:

The operational maximum value may be smaller due to equipped hardware dependencies.

Values

0 to 131071

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

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

All

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

All

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

All

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

All

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

All

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

All

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

All

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 800

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

All

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 800

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

All

Context

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

Full Context

configure service system bgp-evpn ethernet-segment lag

Description

This command configures a LAG ID associated with the Ethernet-Segment. When the Ethernet-Segment is configured as all-active, then only a lag or PW port can be associated with the Ethernet-Segment. When the Ethernet-Segment is configured as single-active, then a lag, port or sdp can be associated to the Ethernet-Segment. In either case, only one of the four objects can be configured in the Ethernet-Segment. A specified lag can be part of only one Ethernet-Segment.

Default

no lag

Parameters

lag-id

Specifies the lag-id associated with the Ethernet-Segment.

Values

1 to 800

Platforms

All

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

All

Context

[Tree] (config>eth-tunnel lag-emulation)

Full Context

configure eth-tunnel lag-emulation

Description

Commands in this context configure eth-tunnel loadsharing parameters.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config service vprn sub-if grp-if sap lag-link-map-profile)

[Tree] (config subscr-mgmt msap-policy lag-link-map-profile)

Full Context

configure service vprn subscriber-interface group-interface sap lag-link-map-profile

configure subscriber-mgmt msap-policy lag-link-map-profile

Description

This command assigns a pre-configured lag link map profile to a SAP or network interface configured on a LAG or a PW port that exists on a LAG. Once assigned or de-assigned, the SAP or network interface egress traffic is re-hashed over LAG as required by the new configuration.

The no form of this command reverts the SAP/network interface to use per-flow, service or link hash as configured for the service/LAG.

Parameters

link-map-profile-id

Defines a unique LAG link map profile on which the LAG the SAP/network interface exist.

Default

1 to 64

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config service ipipe sap lag-link-map-profile)

[Tree] (config service epipe sap lag-link-map-profile)

Full Context

configure service ipipe sap lag-link-map-profile

configure service epipe sap lag-link-map-profile

Description

This command assigns a pre-configured lag link map profile to a SAP/network interface configured on a LAG or a PW port that exists on a LAG. Once assigned/de-assigned, the SAP’s/network interface’s egress traffic will be re-hashed over LAG as required by the new configuration.

The no form of this command reverts the SAP/network interface to use per-flow, service or link hash as configured for the service/LAG.

Default

no lag-link-map-profile

Parameters

link-map-profile-id

An integer from 1 to 64 that defines a unique lag link map profile on the LAG the SAP/network interface exists on.

Platforms

All

Context

[Tree] (config service vpls sap lag-link-map-profile)

Full Context

configure service vpls sap lag-link-map-profile

Description

This command assigns a pre-configured lag link map profile to a SAP/network interface configured on a LAG or a PW port that exists on a LAG. Once assigned/unassigned, the SAP/network interface egress traffic will be re-hashed over LAG as required by the new configuration.

The no form of this command reverts the SAP/network interface to use per-flow, service or link hash as configured for the service/LAG.

Default

no lag-link-map-profile

Parameters

link-map-profile-id

An integer from 1 to 64 that defines a unique lag link map profile on which the LAG the SAP/network interface exist.

Platforms

All

Context

[Tree] (config service ies if sap lag-link-map-profile)

[Tree] (config service ies sub-if grp-if sap lag-link-map-profile)

Full Context

configure service ies interface sap lag-link-map-profile

configure service ies subscriber-interface group-interface sap lag-link-map-profile

Description

This command assigns a pre-configured lag link map profile to a SAP/network interface configured on a LAG or a PW port that exists on a LAG. Once assigned/de-assigned, the SAP/network interface egress traffic will be re-hashed over LAG as required by the new configuration.

The no form of this command reverts the SAP/network interface to use per-flow, service or link hash as configured for the service/LAG.

Default

no lag-link-map-profile

Parameters

lag-link-map-profile-id

An integer from 1 to 64 that defines a unique lag link map profile on which the LAG the SAP/network interface exist.

Platforms

All

• configure service ies interface sap lag-link-map-profile

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

• configure service ies subscriber-interface group-interface sap lag-link-map-profile

Context

[Tree] (config service vprn if sap lag-link-map-profile)

Full Context

configure service vprn interface sap lag-link-map-profile

Description

This command assigns a pre-configured LAG link map profile to a SAP or network interface configured on a LAG or a PW port that exists on a LAG. Once assigned, the SAP or network interface egress traffic will be re-hashed over LAG as required by the new configuration.

The no form of this command reverts the SAP or network interface to use per-flow, service or link hash as configured for the service or LAG.

Default

no lag-link-map-profile

Parameters

link-map-profile-id

An integer from 1 to 64 that defines a unique LAG link map profile on which the LAG the SAP or network interface exist.

Platforms

All

Context

[Tree] (config router if lag-link-map-profile)

Full Context

configure router interface lag-link-map-profile

Description

This command assigns a preconfigured lag link map profile to a SAP/network interface configured on a LAG or a PW port that exists on a LAG. Once assigned/unassigned, the SAP/network interface egress traffic will be re-hashed over LAG as required by the new configuration.

The no form of this command reverts the SAP/network interface to use per-flow, service or link hash as configured for the service/LAG.

Default

no lag-link-map-profile

Parameters

link-map-profile-id

An integer from 1 to 32 that defines a unique lag link map profile on which the LAG the SAP/network interface exist.

Platforms

All

Context

[Tree] (config>subscr-mgmt>sub-profile>egress lag-per-link-hash)

Full Context

configure subscriber-mgmt sub-profile egress lag-per-link-hash

Description

This command configures weight and class to be used on LAG egress when the LAG uses weighted per-link-hash by subscribers with the profile assigned. Subscribers using profile with lag-per-link-hash default configuration, inherit weight and class from the SAP configuration (1 and 1 respectively if none configured under SAP).

The no form of this command restores default configuration.

Parameters

class

Specifies the class to be used to select a LAG link.

Values

1, 2, 3

Default

1

weight

Specifies the weight to be associated with this SAP when selecting a LAG link.

Values

1 to 1024

Default

1

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>ipipe>sap lag-per-link-hash)

[Tree] (config>service>vpls>sap lag-per-link-hash)

[Tree] (config>service>epipe>sap lag-per-link-hash)

Full Context

configure service ipipe sap lag-per-link-hash

configure service vpls sap lag-per-link-hash

configure service epipe sap lag-per-link-hash

Description

This command configures weight and class to this SAP to be used on LAG egress when the LAG uses weighted per-link-hash.

The no form of this command restores default configuration.

Default

no lag-per-link-hash (equivalent to weight 1 class 1)

Platforms

All

Context

[Tree] (config>service>ies>if>sap lag-per-link-hash)

[Tree] (config>service>ies>sub-if>grp-if>sap lag-per-link-hash)

Full Context

configure service ies interface sap lag-per-link-hash

configure service ies subscriber-interface group-interface sap lag-per-link-hash

Description

This command configures weight and class to this SAP to be used on LAG egress when the LAG uses weighted per-link-hash.

The no form of this command restores default configuration.

Default

no lag-per-link-hash (equivalent to weight 1 class 1)

Parameters

class

Specifies the class.

Values

1, 2, 3

weight

Specifies the weight.

Values

1 to 1024

Platforms

All

• configure service ies interface sap lag-per-link-hash

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

• configure service ies subscriber-interface group-interface sap lag-per-link-hash

Context

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

[Tree] (config>service>vprn>if>sap lag-per-link-hash)

Full Context

configure service vprn network-interface lag-per-link-hash

configure service vprn interface sap lag-per-link-hash

Description

This command configures weight and class to this SAP to be used on LAG egress when the LAG uses weighted per-link-hash.

The no form of this command restores the default configuration.

Default

no lag-per-link-hash (equivalent to weight 1 class 1)

Platforms

All

Context

[Tree] (config>router>if lag-per-link-hash)

Full Context

configure router interface lag-per-link-hash

Description

This command configures weight and class to this interface to be used on LAG egress when the LAG uses weighted per-link-hash.

The no form of this command restores the default configuration (weight 1 class 1).

Default

no lag-per-link-hash

Parameters

class

Specifies the class.

Values

1, 2, 3

weight

Specifies the weight.

Values

1 to 1024

Platforms

All

Context

[Tree] (config>router>mcac>policy>bundle>mc-constraints lag-port-down)

Full Context

configure router mcac policy bundle mc-constraints lag-port-down

Description

This command configures the bandwidth available both at the interface and bundle level when a specific number of ports in a LAG group fail.

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

Parameters

lag-id

Specifies the LAG ID. When the number of ports available in the LAG link is reduced by the number of ports configured in this context then the level-id specified here must be applied.

number-lag-port-down

If the number of ports available in the LAG is reduced by the number of ports configured in this command here then bandwidth allowed for bundle and/or interface will be as per the levels configured in this context.

Values

1 to 64 (for 64-link LAG) 1 to 32 (for other LAGs)

level-id

Specifies the amount of bandwidth available within a given bundle for MC traffic for a specified level.

Values

1 to 8

Platforms

All

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-setvalue 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 800 (apply to the 7750 SR and 7950 XRS)

1 to 200 (apply to the 7450 ESS)

Platforms

All

Context

[Tree] (config>router>pim lag-usage-optimization)

Full Context

configure router pim lag-usage-optimization

Description

This command enables the router’s usage of the LAG so traffic for a given multicast stream destined to an IP interface using the LAG is sent only to the forwarding complex that owns the LAG link on which it will actually be forwarded.

Changing the value causes the PIM protocol to be restarted.

If this optimization is disabled, the traffic is sent to all forwarding complexes that own at least one link in the LAG.

The no form of this command causes the traffic to be sent to all the forwarding complexes that own at least one link in the LAG.

Default

no lag-usage-optimization

Platforms

All

Context

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>vrgw lanext)

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>vrgw lanext)

Full Context

configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range vrgw lanext

configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range vrgw lanext

Description

Commands in this context configure HLE parameters.

The no form of this command disables the vRGW parameters enabled in this context.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>router>vrgw lanext)

Full Context

configure router vrgw lanext

Description

Commands in this context configure HLE parameters.

The no form of this command disables the context.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>vrgw lanext)

Full Context

configure subscriber-mgmt vrgw lanext

Description

Commands in this context configure subscriber management vRGW home HLE parameters.

The no form of this command disables the context.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>acct-plcy>include lanext-bridge-id)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute lanext-bridge-id

Description

This command enables the system to include the HLE service’s bridge ID (Alc-Bridge-Id) in RADIUS accounting packets.

The no form of this command excludes the HLE service’s bridge ID (Alc-Bridge-Id) from RADIUS accounting packets.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>acct-plcy>include lanext-device-type)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute lanext-device-type

Description

This command enables the system to include the HLE host’s device type (Alc-HLE-Device-Type) in RADIUS accounting packets.

The no form of this command excludes the HLE host’s device type (Alc-HLE-Device-Type) from RADIUS accounting packets.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>acct-plcy>include lanext-route-distinguisher)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute lanext-route-distinguisher

Description

This command enables the system to include the HLE service’s EVPN route distinguisher (Alc-RD) in RADIUS accounting packets.

The no form of this command excludes the HLE service’s EVPN route distinguisher (Alc-RD) from RADIUS accounting packets.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>acct-plcy>include lanext-route-target)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute lanext-route-target

Description

This command enables the system to include the HLE service’s EVPN route target (Alc-RT) in RADIUS accounting packets.

The no form of this command excludes the HLE service’s EVPN route target (Alc-RT) from RADIUS accounting packets.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>acct-plcy>include lanext-vni)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute lanext-vni

Description

This command enables the system to include the HLE service’s EVPN VXLAN VNI (Alc-Vxlan-VNI) in RADIUS accounting packets.

The no form of this command excludes the HLE service’s EVPN VXLAN VNI (Alc-Vxlan-VNI) from RADIUS accounting packets.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

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

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

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

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

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

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

Full Context

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

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

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

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

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

configure service vpls spoke-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

All

Context

[Tree] (config>subscr-mgmt>msap-policy>vpls-only>igmp-snp last-member-query-interval)

Full Context

configure subscriber-mgmt msap-policy vpls-only-sap-parameters 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 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 interval is ignored when fast-leave is enabled on the SAP or SDP.

The no form of this command reverts to the default.

Default

last-member-query-interval 10

Parameters

seconds

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

Values

1 to 50

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

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

All

Context

[Tree] (config>test-oam>link-meas>template last-reported-delay-hold)

Full Context

configure test-oam link-measurement measurement-template last-reported-delay-hold

Description

This command configures the timer that specifies the wait time before the last reported delay measurement is flushed after a link measurement test enters the operationally down state. The aging timer delays the flushing of the last reported delay metric to the routing engine.

This timer starts a countdown to zero when an administrative function causes the operational state of the test on that specific interface to transition from up to down. If the timer expires before the operational state transitions to up, the previously reported value is flushed. The Delay Measurement Last Reported indicates "Cleared”. The timestamp indicates the time of the clear event. The Triggered By indicates "Expired”. If the administrative state recovers to operationally up before the expiration of the timer, the previous reported value is not flushed.

The aging timer does not apply to failure conditions that do not affect the administrative state of the interface, for example interface failure or routing changes.

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

Default

last-reported-delay-hold 86400

Parameters

seconds

Specifies the delay measurement retention time, in seconds, after the interface on which it was collected is administratively disabled. If the configured value is reached, the last reported measurement is cleared.

A configured value of 0 indicates that the previous reported value is cleared without additional wait time.

Values

0 to 86400

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

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

All

Context

[Tree] (config>subscr-mgmt>shcv-policy layer-3)

Full Context

configure subscriber-mgmt shcv-policy layer-3

Description

Commands in this context configure SHCV behavior parameters for IES and VPRN services.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>mirror>mirror-dest>encap layer-3-encap)

Full Context

configure mirror mirror-dest encap layer-3-encap

Description

This command specifies the format of the routable encapsulation to add to each copied packet. Layer 3 encapsulation takes precedence over Ethernet encapsulation configuration in an LI source. No changes are allowed to the Layer 3 encapsulation once a gateway is configured.

The no form of this command removes the routable encapsulation.

Default

no layer-3-encap

Parameters

ip-udp-shim

Specifies that the type of Layer 3 encapsulation is an IPv4 header, UDP header, and LI shim header added to the mirrored packets.

ip-gre

Specifies that the type of Layer 3 encapsulation is an IPv4 header and GRE header added to the mirrored packets. This encapsulation type is only supported with mirror-type ip-only.

ip-udp-shim-sampled

Specifies that the type of Layer 3 encapsulation is an IPv4 header, UDP header, and a mirror shim header added to the mirrored packets providing direction, mirror type, filter action, interface type, and interface value.

create

Creates a Layer 3 encapsulation.

Platforms

All

Context

[Tree] (config>li>mirror-dest-template layer-3-encap)

Full Context

configure li mirror-dest-template layer-3-encap

Description

This command specifies the format of the routable encapsulation to add to each copied packet. Layer 3 encapsulation takes precedence over Ethernet encapsulation configuration in an LI source. No changes are allowed to the Layer 3 encapsulation after a gateway is configured.

The no form of this command disables Layer 3 encapsulation.

Parameters

ip-udp-shim

Specifies that the type of Layer 3 encapsulation is an IPv4 header, UDP header, and LI-Shim.

ip-gre

Specifies that the type of Layer 3 encapsulation is an IPv4 GRE.

Platforms

All

Context

[Tree] (config>service>vpls>load-balancing lbl-eth-or-ip-l4-teid)

[Tree] (config>service>epipe>load-balancing lbl-eth-or-ip-l4-teid)

Full Context

configure service vpls load-balancing lbl-eth-or-ip-l4-teid

configure service epipe load-balancing lbl-eth-or-ip-l4-teid

Description

This command enables hashing of MPLS Ethernet and MPLS IP packets received on the Epipe and VPLS service SAP using the MPLS labels, the inner IP addresses, the port numbers, and the GTP TEID field, if read by the system. This capability is supported on FP4- and FP5-based line cards.

The no form of this command disables hashing.

Default

no lbl-eth-or-ip-l4-teid

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep lbm-svc-act-responder)

[Tree] (config>service>epipe>sap>eth-cfm>mep lbm-svc-act-responder)

Full Context

configure service epipe spoke-sdp eth-cfm mep lbm-svc-act-responder

configure service epipe sap eth-cfm mep lbm-svc-act-responder

Description

This command enables the MEP to process service activation streams encapsulated in ETH-CFM LBM frames that are directed to the MEP. The MEP will be allocated additional resources to rapidly respond to a high-speed stream of LBM messages.

A MEP created with this option will not validate any TLVs, will not validate the ETH-LBM MAC Address, and will not increment or compute any loopback statistics. Statistical computation and reporting is the responsibility of the test head-end. The ETH-CFM level of the high speed ETH-LBM stream must match the level of a MEP configured with this command. The high-speed stream must not target an ETH-CFM level that is not explicitly configured with this option. MEPs act as boundaries for lower levels, below the configured MEP level values. Those boundary levels do not inherit this function.

When the service activation test is complete, the MEP may be returned to standard processing by removing this command. If there is available bandwidth, the MEP will respond to other ETH-CFM PDUs, such as ETH-DMM marker packets, using standard processing.

The interaction between this command and the tools perform service id service-id loopback eth command must be carefully considered. It is recommended that either the lbm-svc-act-responder or the tools perform service id service-id loopback eth command be used at any given time within a service. If both commands must be configured, and the target reflection point is the MAC Swap Loopback function, the inbound stream of data must not include ETH-CFM traffic that is equal to or lower than the domain level of any configured MEP which would otherwise extract and process the ETH-CFM message. If the reflection target is a MEP configured with the lbm-svc-act-responder option, the mode (ingress or egress) of the SAP or SDP specified with this tools command and the MEP direction (up or down) must match when the functions are enabled on the same reflection point, and the domain level of the inbound ETH-LBM must be the same as that of the MEP configured with the lbm-svc-act-responder option. At no time should the two functions be conflicting with each other along the path of the stream. This conflict would lead to unpredictable and possibly destabilizing situations.

The no form of this command reverts to MEP LBM standard processing.

Default

no lbm-svc-act-responder

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep lbm-svc-act-responder)

[Tree] (config>service>vpls>sap>eth-cfm>mep lbm-svc-act-responder)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep lbm-svc-act-responder)

Full Context

configure service vpls spoke-sdp eth-cfm mep lbm-svc-act-responder

configure service vpls sap eth-cfm mep lbm-svc-act-responder

configure service vpls mesh-sdp eth-cfm mep lbm-svc-act-responder

Description

This command enables the MEP to process service activation streams encapsulated in ETH-CFM LBM frames that are directed to the MEP. The MEP will be allocated additional resources to rapidly respond to a high-speed stream of LBM messages. A MEP created with this option will not validate any TLVs, will not validate the ETH-LBM MAC Address, and will not increment or compute any loopback statistics. Statistical computation and reporting is the responsibility of the test head-end. The ETH-CFM level of the high speed ETH-LBM stream must match the level of a MEP configured with this command. It must not target any lower ETH-CFM level the MEP will terminate. When the service activation test is complete, the MEP may be returned to standard processing by removing this command. If there is available bandwidth, the MEP will respond to other ETH-CFM PDUs, such as ETH-DMM marker packets, using standard processing.

The interaction between this command and the tools perform service id service-id loopback eth command must be carefully considered. It is recommended that either the lbm-svc-act-responder or the tools perform service id service-id loopback eth command be used at any given time within a service. If both commands must be configured, and the target reflection point is the MAC Swap Loopback function, the inbound stream of data must not include ETH-CFM traffic that is equal to or lower than the domain level of any configured MEP which would otherwise extract and process the ETH-CFM message. If the reflection target is a MEP configured with the lbm-svc-act-responder option, the mode (ingress or egress) of the SAP or SDP specified with this tools command and the MEP direction (up or down) must match when the functions are enabled on the same reflection point, and the domain level of the inbound ETH-LBM must be the same as that of the MEP configured with the lbm-svc-act-responder option. At no time should the two functions be conflicting with each other along the path of the stream. This conflict would lead to unpredictable and possibly destabilizing situations.

The no form of this command reverts to MEP LBM standard processing.

Default

no lbm-svc-act-responder

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>router>if>eth-cfm>mep lbm-svc-act-responder)

Full Context

configure router interface eth-cfm mep lbm-svc-act-responder

Description

This command enables the MEP to process service activation streams encapsulated in ETH-CFM LBM frames that are directed to the MEP. The MEP will be allocated additional resources to rapidly respond to a high-speed stream of LBM messages. A MEP created with this option will not validate any TLVs, will not validate the ETH-LBM MAC Address, and will not increment or compute any loopback statistics. Statistical computation and reporting is the responsibility of the test head-end. The ETH-CFM level of the high speed ETH-LBM stream must match the level of a MEP configured with this command. It must not target any lower ETH-CFM level the MEP will terminate. When the service activation test is complete, the MEP may be returned to standard processing by removing this command. If there is available bandwidth, the MEP will respond to other ETH-CFM PDUs, such as ETH-DMM marker packets, using standard processing.

The interaction between this command and the tools perform service id service-id loopback eth command must be carefully considered. It is recommended that either the lbm-svc-act-responder or the tools perform service id service-id loopback eth command be used at any given time within a service. If both commands must be configured, and the target reflection point is the MAC Swap Loopback function, the inbound stream of data must not include ETH-CFM traffic that is equal to or lower than the domain level of any configured MEP which would otherwise extract and process the ETH-CFM message. If the reflection target is a MEP configured with the lbm-svc-act-responder option, the mode (ingress or egress) of the SAP or SDP specified with this tools command and the MEP direction (up or down) must match when the functions are enabled on the same reflection point, and the domain level of the inbound ETH-LBM must be the same as that of the MEP configured with the lbm-svc-act-responder option. At no time should the two functions be conflicting with each other along the path of the stream. This conflict would lead to unpredictable and possibly destabilizing situations.

The no form of this command reverts to MEP LBM standard processing.

Default

no lbm-svc-act-responder

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS

Context

[Tree] (config>port>tdm lbo)

Full Context

configure port tdm lbo

Description

This command applies only to a DS-1 port configured with a 'long' buildout (see the buildout command). Specify the number of decibels the transmission signal decreases over the line.

For 'short' buildout the following values are valid:

lboNotApplicable — Not applicable

For 'long' buildout the following values are valid:

The default for 'short' build out is 'NotApplicable' while the default for 'long' buildout is 'lbo0dB'.

Platforms

7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e

Context

[Tree] (config>service>vprn>l2tp>group>ppp lcp-force-ack-accm)

[Tree] (config>router>l2tp>group>ppp lcp-force-ack-accm)

[Tree] (config>router>l2tp>group>tunnel>ppp lcp-force-ack-accm)

[Tree] (config>service>vprn>l2tp>group>tunnel>ppp lcp-force-ack-accm)

Full Context

configure service vprn l2tp group ppp lcp-force-ack-accm

configure router l2tp group ppp lcp-force-ack-accm

configure router l2tp group tunnel ppp lcp-force-ack-accm

configure service vprn l2tp group tunnel ppp lcp-force-ack-accm

Description

This command enables the LCP Asynchronous Control Character Map (ACCM) configuration option. When enabled, the LCP ACCM configuration option is acknowledged during LCP negotiation between the LNS and the PPP client. The option is then ignored and no ACCM mapping is done.

By default, an L2TP tunnel inherits the configuration from the L2TP group CLI context.

The no form of this command disables the LCP ACCM configuration option.

Parameters

always

Specifies to acknowledge the LCP ACCM configuration option, but not to perform ACCM mapping. This option overrides the group level configuration.

never

Specifies to reject the LCP ACCM configuration option. This option overrides the group level configuration.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>ppp-policy lcp-ignore-identifier)

Full Context

configure subscriber-mgmt ppp-policy lcp-ignore-identifier

Description

This command instructs BNG to ignore identifier values in Link Control Protocol (LCP) Echo Reply packets and keep the PPP session up.

The no form of this command instructs BNG not to ignore the identifier values, in which case, incorrect messages are discarded and the PPP session terminates because of echo timeout.

Default

lcp-ignore-identifier

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>service>vprn>l2tp>group>ppp lcp-ignore-magic-numbers)

[Tree] (config>router>l2tp>group>tunnel>ppp lcp-ignore-magic-numbers)

[Tree] (config>router>l2tp>group>ppp lcp-ignore-magic-numbers)

[Tree] (config>service>vprn>l2tp>group>tunnel>ppp lcp-ignore-magic-numbers)

Full Context

configure service vprn l2tp group ppp lcp-ignore-magic-numbers

configure router l2tp group tunnel ppp lcp-ignore-magic-numbers

configure router l2tp group ppp lcp-ignore-magic-numbers

configure service vprn l2tp group tunnel ppp lcp-ignore-magic-numbers

Description

This command configures checking the magic number field in LCP Echo-Request and LCP Echo-Reply messages.

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

Default

no lcp-ignore-magic-numbers

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>ppp-policy lcp-ignore-magic-numbers)

Full Context

configure subscriber-mgmt ppp-policy lcp-ignore-magic-numbers

Description

This command enables the PPP session to stay established when an LCP peer magic number mismatch is detected.

By default, the PPP session is terminated when an LCP peer magic number mismatch is detected.

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

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

All

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

All

Context

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

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

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

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

Full Context

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

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

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

configure service epipe bgp-evpn 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

All

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

All

Context

[Tree] (debug>router ldp)

Full Context

debug router ldp

Description

Use this command to configure LDP debugging.

Platforms

All

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

All

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

All

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

All

Context

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

Full Context

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

Description

Platforms

All

Context

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

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

Full Context

configure router mpls lsp ldp-over-rsvp

configure router mpls lsp-template 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

All

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

All

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

All

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

All

Context

[Tree] (config>service>vprn>static-route-entry>indirect ldp-sync)

Full Context

configure service vprn static-route-entry indirect 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

All

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

All

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

All

Context

[Tree] (oam ldp-treetrace)

Full Context

oam ldp-treetrace

Description

This command allows the user to perform a single run of the LDP ECMP OAM tree trace to discover all ECMP paths of an LDP FEC.

Parameters

ip-prefix/mask

Specifies the address prefix and subnet mask of the target BGP IPv4 label route.

Values

ip-prefix: a.b.c.dmask, the value must be 32

downstream-map-tlv {dsmap | ddmap}

Specifies which format of the downstream mapping TLV to use in the LSP trace packet. The DSMAP TLV is the original format in RFC 4379 (obsoleted by RFC 8029). The DDMAP is the new enhanced format specified in RFC 6424 and RFC 8029.

Default

Inherited from global configuration of downstream mapping TLV in option mpls-echo-request-downstream-map {dsmap | ddmap}.

fc-name

Specifies the FC and profile parameters are used to indicate the forwarding class and profile of the MPLS echo request packet.

When an MPLS echo request packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the specified FC and profile parameter values. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface.

When the MPLS echo request packet is received on the responding node, The FC and profile parameter values are dictated by the LSP-EXP mappings of the incoming interface.

When an MPLS echo reply packet is generated in CPM and is forwarded to the outgoing interface, the packet is queued in the egress network queue corresponding to the FC and profile parameter values determined by the classification of the echo request packet, which is being replied to, at the incoming interface. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface. The ToS byte is not modified. ldp-treetrace Request Packet and Behavior summarizes this behavior.

Table 2. ldp-treetrace Request Packet and Behavior

CPM (sender node)	Echo request packet: packet {tos=1, fc1, profile1} fc1 and profile1 are as entered by user in OAM command or default values tos1 as per mapping of {fc1, profile1} to IP precedence in network egress QoS policy of outgoing interface
Outgoing interface (sender node)	Echo request packet: pkt queued as {fc1, profile1} ToS field=tos1 not remarked EXP=exp1, as per mapping of {fc1, profile1} to EXP in network egress QoS policy of outgoing interface
Incoming interface (responder node)	Echo request packet: packet {tos1, exp1} exp1 mapped to {fc2, profile2} as per classification in network QoS policy of incoming interface
CPM (responder node)	Echo reply packet: packet {tos=1, fc2, profile2}
Outgoing interface (responder node)	Echo reply packet: pkt queued as {fc2, profile2} ToS filed= tos1 not remarked (reply inband or out-of-band) EXP=exp2, if reply is inband, remarked as per mapping of {fc2, profile2} to EXP in network egress QoS policy of outgoing interface
Incoming interface (sender node)	Echo reply packet: packet {tos1, exp2} exp2 mapped to {fc1, profile1} as per classification in network QoS policy of incoming interface

Values

be, l2, af, l1, h2, ef, h1, nc

Default

be

profile {in | out}

Specifies the profile state of the MPLS echo request packet.

Values

in, out

Default

out

max-paths

Specifies the maximum number of paths for a ldp-treetrace test, expressed as a decimal integer.

Values

1 to 255

Default

128

ttl-value

Specifies the maximum TTL value in the MPLS label for the LSP trace test, expressed as a decimal integer.

Values

1 to 255

Default

30

retry-count

Specifies the maximum number of consecutive MPLS echo requests, expressed as a decimal integer that do not receive a reply before the trace operation fails for a given TTL.

Values

1 to 255

Default

5

timeout

Specifies the time, in seconds, used to override the default time out value and is the amount of time that the router waits for a message reply after sending the message request. Upon the expiration of the message time out, the requesting router assumes that the message response is not received. Any response received after the request times out is silently discarded.

Values

1 to 60

Default

3

Platforms

All

Output

The following output is an example of treetrace prefix information.

*A:Dut-A# oam ldp-treetrace prefix 10.20.1.6/32 

ldp-treetrace for Prefix 10.20.1.6/32:

         127.0.0.1, ttl =   3 dst =      127.1.0.255 rc = EgressRtr status = Done
    Hops:         127.0.0.1         127.0.0.1

         127.0.0.1, ttl =   3 dst =      127.2.0.255 rc = EgressRtr status = Done
    Hops:         127.0.0.1         127.0.0.1

ldp-treetrace discovery state: Done
ldp-treetrace discovery status: ' OK '
Total number of discovered paths: 2
Total number of failed traces: 0

Context

[Tree] (config>test-oam ldp-treetrace)

Full Context

configure test-oam ldp-treetrace

Description

This command creates the context to configure the LDP ECMP OAM tree trace which consists of an LDP ECMP path discovery and an LDP ECMP path probing features.

The no form of this command deletes the configuration for the LDP ECMP OAM tree discovery and path probing under this context.

Platforms

All

Output

The following is an example LDP treetrace information.

*A:Dut-B# oam ldp-treetrace prefix 10.20.1.5/32 

ldp-treetrace for Prefix 10.20.1.5/32:

       10.10.131.2, ttl =   2 dst =      127.1.0.253 rc = EgressRtr status = Done
    Hops:          11.1.0.2

       10.10.132.2, ttl =   2 dst =      127.1.0.255 rc = EgressRtr status = Done
    Hops:          11.1.0.2

       10.10.131.2, ttl =   2 dst =      127.2.0.255 rc = EgressRtr status = Done
    Hops:          11.2.0.2

       10.10.132.2, ttl =   2 dst =      127.2.0.253 rc = EgressRtr status = Done
    Hops:          11.2.0.2

ldp-treetrace discovery state: Done
ldp-treetrace discovery status: ' OK '
Total number of discovered paths: 4
Total number of failed traces: 0

*A:Dut-A# oam ldp-treetrace prefix 10.20.1.6/32 downstream-map-tlv dsmap 

ldp-treetrace for Prefix 10.20.1.6/32:

         127.0.0.1, ttl =   3 dst =      127.1.0.255 rc = EgressRtr status = Done
    Hops:         127.0.0.1         127.0.0.1

         127.0.0.1, ttl =   3 dst =      127.2.0.255 rc = EgressRtr status = Done
    Hops:         127.0.0.1         127.0.0.1

ldp-treetrace discovery state: Done
ldp-treetrace discovery status: ' OK '
Total number of discovered paths: 2
Total number of failed traces: 0

Context

[Tree] (debug>oam ldp-treetrace)

Full Context

debug oam ldp-treetrace

Description

This command enables debugging for OAM LDP treetrace.

The no form of this command disables the debugging.

Platforms

All

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

All

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

All

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

All

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

All

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

All

Context

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

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

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

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

Full Context

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

configure service vprn bgp rib-management ipv4 leak-import

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

configure service vprn bgp rib-management ipv6 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 (#, $, spaces, and so on), 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 (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

Platforms

All

Context

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

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

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

Full Context

configure router bgp rib-management ipv6 leak-import

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

configure router bgp rib-management ipv4 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 (#, $, spaces, and so on), 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 (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

Platforms

All

Context

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw learn-ap-mac)

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw learn-ap-mac)

Full Context

configure service ies subscriber-interface group-interface wlan-gw learn-ap-mac

configure service vprn subscriber-interface group-interface wlan-gw learn-ap-mac

Description

This command enables the sending of ARP or ND packets on the WLAN-GW GRE tunnel for certain events. The target IP address in the ARP/ND packet is the endpoint IP address of the AP. The ARP/ND response from the AP should contain the AP MAC, which subsequently can be reported in a called-station-id message. When enabled, a message will be sent for following events:

• CPM: Mobility to an AP for which the AP-MAC is not yet known

• CPM: RS-triggered authentication on an AP for which the AP-MAC is not yet known

• ISA: Any mobility event

• ISA: Any authentication where the AP-MAC is not yet known (for example, from a RADIUS proxy cache or a DHCP circuit-id). If the optional keyword delay-auth is configured, then the authentication will be delayed until the ARP/ND is answered or timed out, after which the AP-MAC can be included in the authentication.

This configuration is ignored for L2-AP and L2TPv3 access.

Parameters

delay-auth

Specifies that authentication will be delayed until the ARP/ND is answered or timed out, after which the AP-MAC can be included in the authentication.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

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

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

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

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

Full Context

configure service vprn interface vpls evpn arp learn-dynamic

configure service ies interface vpls evpn nd learn-dynamic

configure service vprn interface vpls evpn nd learn-dynamic

configure service ies interface vpls evpn arp 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

All

Context

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw learn-l2tp-cookie)

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw learn-l2tp-cookie)

Full Context

configure service ies subscriber-interface group-interface wlan-gw learn-l2tp-cookie

configure service vprn subscriber-interface group-interface wlan-gw learn-l2tp-cookie

Description

This command specifies when this system will learn the cookie from L2TP tunnels terminating on this interface. Learning the cookie means that the value of the octets 3-8 of the cookie is interpreted as an access point’s MAC address, and used as such, for example in the Called-Station-Id attribute of RADIUS Interim-Update messages.

Parameters

if-match

Specifies that the cookie is interpreted only if the value of the first two octets of the cookie is equal to the value of the object tmnxWlanGwSoftGreIfL2tpCookie.

cookie hex string

Specifies the value used to compare the first two bytes of the cookie. This parameter is only valid if if-match is configured.

Values

0x0000 to 0xFFFF...(4 hex nibbles)

never

Specifies that the cookie value will always be ignored.

always

Always learn the AP-MAC from the cookie, regardless of the value of the first two bytes.

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

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

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

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

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

Full Context

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

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

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

configure service vprn 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

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

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

[Tree] (config>router>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)

Full Context

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

configure router 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

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

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>msap-policy>vpls-only>dhcp lease-populate)

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

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

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

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

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

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

Full Context

configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp lease-populate

configure service vprn subscriber-interface group-interface dhcp lease-populate

configure service ies subscriber-interface group-interface dhcp lease-populate

configure service vprn interface dhcp lease-populate

configure service vpls sap dhcp lease-populate

configure service vprn subscriber-interface dhcp lease-populate

configure service ies 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

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

• configure service vprn subscriber-interface group-interface dhcp lease-populate
• configure service ies subscriber-interface group-interface dhcp lease-populate
• configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp lease-populate
• configure service vprn subscriber-interface dhcp lease-populate

All

• configure service ies interface dhcp lease-populate
• configure service vpls sap dhcp lease-populate
• configure service vprn interface dhcp lease-populate

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

All

Context

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

Full Context

configure service ies interface ipv6 dhcp-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.

Context

[Tree] (config>service>ies>sub-if>wlan-gw>pool-manager>dhcp6-client lease-query)

[Tree] (config>service>vprn>sub-if>wlan-gw>pool-manager>dhcp6-client lease-query)

Full Context

configure service ies subscriber-interface wlan-gw pool-manager dhcpv6-client lease-query

configure service vprn subscriber-interface wlan-gw pool-manager dhcpv6-client lease-query

Description

This command enables lease-query. If this is specified the dhcp6-client will retrieve any existing addresses when becoming active. The lease-query is performed for all of the configured servers

The no form of this command disables lease-query.

Parameters

Max nbr of retries

Specifies the maximum number of retries before the lease query assumes no existing subnets were allocated.

Values

0 to 10

Platforms

7750 SR, 7750 SR-e, 7750 SR-s, VSR

Context

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

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

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

Full Context

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

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

configure service vprn 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

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

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

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

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

Full Context

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

configure subscriber-mgmt local-user-db ipoe host 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

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

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

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

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

Full Context

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

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

configure router 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

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

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

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

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

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

[Tree] (config>subscr-mgmt>msap-policy>vpls-only>dhcp>proxy lease-time)

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

Full Context

configure service ies interface dhcp proxy-server lease-time

configure service ies subscriber-interface group-interface dhcp proxy-server lease-time

configure service vprn interface dhcp proxy-server lease-time

configure service vprn subscriber-interface group-interface dhcp proxy-server lease-time

configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp proxy-server lease-time

configure service vpls sap 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

All

• 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

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

• configure service ies subscriber-interface group-interface dhcp proxy-server lease-time
• configure service vprn subscriber-interface group-interface dhcp proxy-server lease-time
• configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp proxy-server lease-time

Context

[Tree] (config>service>ies>sub-if>grp-if>wpp lease-time)

[Tree] (config>service>vprn>sub-if>grp-if>wpp lease-time)

Full Context

configure service ies subscriber-interface group-interface wpp lease-time

configure service vprn subscriber-interface group-interface wpp lease-time

Description

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

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

Parameters

lease-time

Specifies the lease time.

Values

days days	0 to 3650
hrs hours	0 to 23
min minutes	0 to 59
sec seconds	0 to 59

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

[Tree] (config>subscr-mgmt>vrgw>brg>brg-profile>dhcp-pool lease-time)

Full Context

configure subscriber-mgmt vrgw brg brg-profile dhcp-pool lease-time

Description

This command configures the lease time, in seconds, to be used when allocating addresses from the pool. This time value should always be longer than the renew/rebind time.

The no form of this command reverts to the default.

Default

lease-time hrs 6

Parameters

seconds

Specifies the lease time in seconds.

Values

300 to 315446399

days

Specifies the lease time in days.

Values

1 to 3650

hrs

Specifies the lease time in hours.

Values

1 to 23

min

Specifies the lease time in minutes.

Values

1 to 59

sec

Specifies the lease time in seconds.

Values

1 to 59

Platforms

7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR

Context

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

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

Full Context

configure router mpls lsp-template least-fill

configure router mpls lsp 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

All

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

All

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