e Commands

e-counters

e-counters

Syntax

e-counters [all]

no e-counters

Context

[Tree] (config>subscr-mgmt>acct-plcy>cr>queue e-counters)

[Tree] (config>subscr-mgmt>acct-plcy>cr>ref-queue e-counters)

Full Context

configure subscriber-mgmt radius-accounting-policy custom-record queue e-counters

configure subscriber-mgmt radius-accounting-policy custom-record ref-queue e-counters

Description

Commands in this context configure egress counter parameters for this custom record.

The no form of this command reverts to the default.

Parameters

all

Includes all counters

Platforms

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

e-counters

Syntax

e-counters [all]

no e-counters

Context

[Tree] (config>log>acct-policy>cr>ref-queue e-counters)

[Tree] (config>log>acct-policy>cr>queue e-counters)

[Tree] (config>log>acct-policy>cr>ref-policer e-counters)

[Tree] (config>log>acct-policy>cr>policer e-counters)

Full Context

configure log accounting-policy custom-record ref-queue e-counters

configure log accounting-policy custom-record queue e-counters

configure log accounting-policy custom-record ref-policer e-counters

configure log accounting-policy custom-record policer e-counters

Description

This command configures egress counter parameters for this custom record.

The no form of this command reverts all egress counters to their default value.

Default

e-counters

Parameters

all

Specifies that all egress counters should be included.

Platforms

All

e1

e1

Syntax

e1 [e1-id]

Context

[Tree] (config>port>tdm e1)

Full Context

configure port tdm e1

Description

Commands in this context configure E-1 parameters. E-1 is a basic time division multiplexing scheme used to carry digital circuits. It is also a standard WAN digital communication format designed to operate over copper facilities at a rate of 2.048 Mb/s.

North America uses the T-Carrier system while Europe uses the E-Carrier system of transmission, using multiples of the DS system. Digital signals are carried inside the carrier systems.

The no form of this command disables E-1 capabilities.

Parameters

e1-id

Specifies the E-1 channel being created.

Values

E1: 1 to 21, e1-sonet-sdh-index

Platforms

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

e3

e3

Syntax

[no] e3 [sonet-sdh-index]

Context

[Tree] (config>port>tdm e3)

Full Context

configure port tdm e3

Description

Commands in this context configure E-3 parameters. E-3 lines provide a speed of 44.736 Mb/s and is also frequently used by service providers. E-3 lines carry 16 E-1 signals with a data rate of 34.368 Mb/s.

An E-3 connection typically supports data rates of about 43 Mb/s. An E-3 line actually consists of 672 individual channels, each supporting 64 kb/s. E-3 lines are used mainly by Service Providers to connect to the Internet backbone and for the backbone itself.

Depending on the MDA type, the E-3 parameters must be disabled if clear channel is enabled by default (for example, on the m12-ds3e3 MDA). Clear channel is a channel that uses out-of-band signaling, not in-band signaling, so the channel's entire bit rate is available. Channelization must be explicitly specified. Note that if E-3 nodes are provisioned on the channelized SONET/SDH MDA you must provision the parent STS-1 SONET/STM0 SDH path first.

North America uses the T-Carrier system while Europe uses the E-Carrier system of transmission, using multiples of the DS system. Digital signals are carried inside the carrier systems.

The no form of this command disables E-3 capabilities.

Parameters

sonet-sdh-index

Specifies the components making up the specified SONET/SDH Path. Depending on the type of SONET/SDH port the sonet-sdh-index must specify more path indexes to specify the payload location of the path. The sonet-sdh-index differs for SONET and SDH ports.

Platforms

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

ea-length

ea-length

Syntax

ea-length ea-bits-length

no ea-length

Context

[Tree] (config>service>nat>map-domain>mapping-rule ea-length)

Full Context

configure service nat map-domain mapping-rule ea-length

Description

This command configures the length of EA bits in the MAP rule. The no ea-length statement sets the ea-length to 0.

Default

no ea-length

Parameters

ea-bits-length

Specifies the length of the EA bits.

Values

1 to 48

Platforms

VSR

eapol-destination-address

eapol-destination-address

Syntax

eapol-destination-address mac

no eapol-destination-address

Context

[Tree] (config>port>ethernet>dot1x>macsec>sub-port eapol-destination-address)

Full Context

configure port ethernet dot1x macsec sub-port eapol-destination-address

Description

The EAPoL destination MAC address uses a destination multicast MAC address of 01:80:C2:00:00:03. Some networks cannot tunnel this packet over the network and consume these packets, causing the MKA session to fail. This command can change the destination MAC of the EAPoL to the unicast address of the MACsec peer, and as such, the EAPoL and MKA signaling will be unicasted between two peers.

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

Default

no eapol-destination-address

Parameters

mac

Specifies the desired destination MAC address to be used by the EAPOL MKA packets of this sub-port.

Values

aa:bb:cc:dd:ee:ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers.

Platforms

All

ebgp-default-reject-policy

ebgp-default-reject-policy

Syntax

ebgp-default-reject-policy [import] [export]

no ebgp-default-reject-policy

Context

[Tree] (config>service>vprn>bgp>group ebgp-default-reject-policy)

[Tree] (config>service>vprn>bgp ebgp-default-reject-policy)

[Tree] (config>service>vprn>bgp>group>neighbor ebgp-default-reject-policy)

Full Context

configure service vprn bgp group ebgp-default-reject-policy

configure service vprn bgp ebgp-default-reject-policy

configure service vprn bgp group neighbor ebgp-default-reject-policy

Description

This command configures the default import and export policy behavior for EBGP neighbors.

The no form of this command removes the default import and export policy behavior.

Default

no ebgp-default-reject-policy

Parameters

import

Specifies the default reject import policy for EBGP neighbors.

export

Specifies the default reject export policy for EBGP neighbors.

Platforms

All

ebgp-default-reject-policy

Syntax

ebgp-default-reject-policy [import] [export]

no ebgp-default-reject-policy

Context

[Tree] (config>router>bgp>group ebgp-default-reject-policy)

[Tree] (config>router>bgp ebgp-default-reject-policy)

[Tree] (config>router>bgp>group>neighbor ebgp-default-reject-policy)

Full Context

configure router bgp group ebgp-default-reject-policy

configure router bgp ebgp-default-reject-policy

configure router bgp group neighbor ebgp-default-reject-policy

Description

This command configures the default import and export policy behavior for EBGP neighbors.

The no form of this command removes the default import and export policy behavior.

Default

no ebgp-default-reject-policy

Parameters

import

Specifies the default reject import policy for EBGP neighbors.

export

Specifies the default reject export policy for EBGP neighbors.

Platforms

All

ebgp-ibgp-equal

ebgp-ibgp-equal

Syntax

ebgp-ibgp-equal [ipv4] [ipv6] [label-ipv4] [label-ipv6]

no ebgp-ibgp-equal

Context

[Tree] (config>service>vprn>bgp>best-path-selection ebgp-ibgp-equal)

Full Context

configure service vprn bgp best-path-selection ebgp-ibgp-equal

Description

This command instructs the BGP decision process to ignore the difference between EBGP and IBGP routes in selecting the best path and eligible multipaths (if multipath and ECMP are enabled). The result is a form of EIBGP load-balancing in a multipath scenario.

The operator can apply the behavior selectively to only certain types of routes by specifying one or more address family names in the command.

The no form of this command configures the router in the BGP decision process to prefer an EBGP learned route over an IBGP learned route.

Default

no ebgp-ibgp-equal

Parameters

ipv4

Specifies that the command should be applied to unlabeled unicast IPv4 routes.

ipv6

Specifies that the command should be applied to unlabeled unicast IPv6 routes.

label-ipv4

Specifies that the command should be applied to labeled IPv4 routes.

label-ipv6

Specifies that the command should be applied to labeled IPv6 routes.

Platforms

All

ebgp-ibgp-equal

Syntax

ebgp-ibgp-equal [ipv4] [ipv6] [label-ipv4] [label-ipv6] [vpn-ipv4] [vpn-ipv6]

[evpn]

no ebgp-ibgp-equal

Context

[Tree] (config>router>bgp>best-path-selection ebgp-ibgp-equal)

Full Context

configure router bgp best-path-selection ebgp-ibgp-equal

Description

This command instructs the BGP decision process to ignore the difference between EBGP and IBGP routes in selecting the best path and eligible multipaths (if multipath and ECMP are enabled). The result is a form of EIBGP load balancing in a multipath scenario.

The behavior can be applied selectively to only certain types of routes by specifying one or more address family names in the command. If no families are specified, this command applies to IPv4, IPv6, label-IPv4, label-IPv6, VPN-IPv4, VPN-IPv6, and EVPN routes.

The no form of this command configures the router in the BGP decision process to prefer an EBGP learned route over an IBGP learned route.

Default

no ebgp-ibgp-equal

Parameters

ipv4

Specifies that the command should be applied to unlabeled unicast IPv4 routes.

ipv6

Specifies that the command should be applied to unlabeled unicast IPv6 routes.

label-ipv4

Specifies that the command should be applied to labeled unicast IPv4 routes.

label-ipv6

Specifies that the command should be applied to labeled unicast IPv6 routes.

vpn-ipv4

Specifies that the command should be applied to IPv4 VPN routes.

vpn-ipv6

Specifies that the command should be applied to IPv6 VPN routes.

evpn

Specifies that the command should be applied to EVPN routes.

Platforms

All

ecdsa

ecdsa

Syntax

ecdsa

Context

[Tree] (config>system>security>user>public-keys ecdsa)

Full Context

configure system security user public-keys ecdsa

Description

This command allows the user to enter the context to configure ECDSA public keys.

Platforms

All

ecdsa-key

ecdsa-key

Syntax

ecdsa-key key-id [create]

no ecdsa-key key-id

Context

[Tree] (config>system>security>user>public-keys>ecdsa ecdsa-key)

Full Context

configure system security user public-keys ecdsa ecdsa-key

Description

This command creates an ECDSA public key and associates it with the username. Multiple public keys can be associated with the user. The key ID is used to identify these keys for the user.

Parameters

create

Keyword used to create an ECDSA key. The create keyword requirement can be enabled/disabled in the environment>create context.

key-id

Specifies the key identifier.

Values

1 to 32

Platforms

All

echo

echo

Syntax

echo [text-to-echo] [extra-text-to-echo] [more-text]

Context

[Tree] (echo)

Full Context

echo

Description

This command echoes arguments on the command line. The primary use of this command is to allow messages to be displayed to the screen in files executed with the exec command.

Parameters

text-to-echo

Specifies a text string to be echoed, up to 256 characters.

extra-text-to-echo

Specifies more text to be echoed, up to 256 characters.

more-text

Specifies more text to be echoed, up to 256 characters.

Platforms

All

echo-interval

echo-interval

Syntax

echo-interval seconds

no echo-interval

Context

[Tree] (config>open-flow>of-switch echo-interval)

Full Context

configure open-flow of-switch echo-interval

Description

This command configures the Echo Request interval for monitoring the OpenFlow control channels to the controllers for this OpenFlow switch instance.

The no form of this command restores default value.

Default

echo-interval 10

Parameters

seconds

Specifies an interval, in seconds.

Values

1 to 3600

Platforms

All

echo-multiple

echo-multiple

Syntax

echo-multiple value

no echo-multiple

Context

[Tree] (config>open-flow>of-switch echo-multiple)

Full Context

configure open-flow of-switch echo-multiple

Description

This command configures the number of consecutive Echo Reply messages that must be lost to declare OF control channel down.

The no form of this command restores default value.

Default

echo-multiple 3

Parameters

value

Specifies the threshold value for the number of consecutive Echo Rely messages lost.

Values

3 to 100

Platforms

All

echo-receive

echo-receive

Syntax

echo-receive echo-interval

no echo-receive

Context

[Tree] (config>router>bfd>bfd-template echo-receive)

Full Context

configure router bfd bfd-template echo-receive

Description

This command sets the minimum echo receive interval, in milliseconds, for a session. This is not used by a BFD session for MPLS-TP.

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

Default

echo-receive 100

Parameters

echo-interval

Specifies the echo receive interval.

Values

100 ms to 100,000 ms in 1 ms increments

Default

100

Platforms

All

ecmp

ecmp

Syntax

ecmp max-ecmp-routes

Context

[Tree] (config>service>epipe>bgp-evpn>mpls ecmp)

[Tree] (config>service>vpls>bgp-evpn>mpls ecmp)

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

[Tree] (config>service>epipe>bgp-evpn>vxlan ecmp)

[Tree] (config>service>vpls>bgp-evpn>srv6 ecmp)

[Tree] (config>service>vpls>bgp-evpn>vxlan ecmp)

[Tree] (config>service>epipe>bgp-evpn>srv6 ecmp)

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

Full Context

configure service epipe bgp-evpn mpls ecmp

configure service vpls bgp-evpn mpls ecmp

configure service vpls bgp-evpn mpls auto-bind-tunnel ecmp

configure service epipe bgp-evpn vxlan ecmp

configure service vpls bgp-evpn segment-routing-v6 ecmp

configure service vpls bgp-evpn vxlan ecmp

configure service epipe bgp-evpn segment-routing-v6 ecmp

configure service epipe bgp-evpn mpls auto-bind-tunnel ecmp

Description

When configured in a VPLS service, this command controls the number of paths that are allowed to reach a specified MAC address when that MAC in the FDB is associated to a remote all-active multi-homed ES.

The configuration of two or more ECMP paths to a specified MAC enables the aliasing function described in RFC 7432.

When used in an Epipe service, this command controls the number of paths that are allowed to reach a specified remote Ethernet tag that is associated to an ES destination.

Default

ecmp 1

Parameters

max-ecmp-routes

Specifies the number of paths allowed to the same multi-homed MAC address or Ethernet tag.

Values

1 to 32

Platforms

All

  • configure service epipe bgp-evpn vxlan ecmp
  • configure service vpls bgp-evpn mpls auto-bind-tunnel ecmp
  • configure service vpls bgp-evpn mpls ecmp
  • configure service vpls bgp-evpn vxlan ecmp
  • configure service epipe bgp-evpn mpls ecmp
  • configure service epipe bgp-evpn mpls auto-bind-tunnel ecmp

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

  • configure service epipe bgp-evpn segment-routing-v6 ecmp
  • configure service vpls bgp-evpn segment-routing-v6 ecmp

ecmp

Syntax

ecmp max-ecmp-routes

no ecmp

Context

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

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

Full Context

configure service vprn bgp-ipvpn mpls auto-bind-tunnel ecmp

configure service vprn bgp-evpn mpls auto-bind-tunnel ecmp

Description

This command configures the maximum number of tunnels that may be used as ECMP next-hops for the VPRN. This value overrides any values that are configured using the config>service>vprn>ecmp command.

The no form of this command removes the configured overriding value, and the value configured using the config>service>vprn>ecmp command is used.

Default

ecmp 1

Parameters

max-ecmp-routes

Specifies the maximum number of tunnels that may be used as ECMP next-hops for the VPRN.

Values

1 to 32

Default

1

Platforms

All

ecmp

Syntax

ecmp max-ecmp-routes

no ecmp

Context

[Tree] (config>router ecmp)

Full Context

configure router ecmp

Description

This command enables ECMP and configures the number of routes for path sharing; for example, the value 2 means two equal cost routes will be used for cost sharing.

ECMP can only be used for routes learned with the same preference and same protocol.

When more ECMP routes are available at the best preference than configured in max-ecmp-routes, then the lowest next-hop IP address algorithm is used to select the number of routes configured in max-ecmp-routes.

The no form of this command disables ECMP path sharing. If ECMP is disabled and multiple routes are available at the best preference and equal cost, then the route with the lowest next-hop IP address is used.

Default

no ecmp

Parameters

max-ecmp-routes

Specifies the maximum number of equal cost routes allowed on this routing table instance, expressed as a decimal integer. Setting ECMP max-ecmp-routes to 1 yields the same result as entering no ecmp.

Values

1 to 64

Platforms

All

ecmp

Syntax

ecmp max-ecmp-routes

no ecmp

Context

[Tree] (config>service>vprn ecmp)

Full Context

configure service vprn ecmp

Description

This command enables equal-cost multipath (ECMP) and configures the number of routes for path sharing. For example, the value of 2 means that 2 equal cost routes are used for cost sharing.

ECMP groups form when the system routes to the same destination with equal cost values. Routing table entries can be entered manually (as static routes), or they can be formed when neighbors are discovered and routing table information is exchanged by routing protocols. The system can balance traffic across the groups with equal costs.

ECMP can only be used for routes learned with the same preference and same protocol. See the discussion on preferences in the application6 command.

When more ECMP routes are available at the best preference than configured by the max-ecmp-routes parameter, then the lowest next-hop IP address algorithm is used to select the number of routes configured.

The no form of this command disables ECMP path sharing. If ECMP is disabled and multiple routes are available at the best preference and equal cost, the newly updated route is used.

Default

no ecmp

Parameters

max-ecmp-routes

Specifies the maximum number of routes for path sharing.

Values

1 to 64

Platforms

All

ecmp-opt-threshold

ecmp-opt-threshold

Syntax

ecmp-opt-threshold preference-level

no ecmp-opt-threshold

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle ecmp-opt-threshold)

Full Context

configure mcast-management multicast-info-policy bundle ecmp-opt-threshold

Description

This command defines the preference level threshold where multicast ECMP path management can dynamically optimize channels based on topology or bandwidth events. If the channels preference is equal to or less than the ecmp-opt-threshold, ECMP can move the channel between ECMP paths when bandwidth distribution events happen. Channels with a preference level higher than the threshold are moved during these events.

The default ECMP optimization limit threshold is 7. This means that multicast channels with a preference level of 0 to 7 (all channels) are allowed to move between ECMP paths. The ecmp-opt-threshold command can be used to change the default threshold.

Changing the threshold causes all channels ECMP optimization eligibility to be reevaluated.

The no form of this command restores the default ECMP optimization preference threshold value.

Default

ecmp-opt-threshold 7

Parameters

preference-level

The preference-level parameter is required when specifying the ecmp-opt-threshold. An integer value from 0 to 7 must be specified.

Values

0 to 7

Platforms

All

ecmp-unequal-cost

ecmp-unequal-cost

Syntax

[no] ecmp-unequal-cost

Context

[Tree] (config>service>vprn ecmp-unequal-cost)

Full Context

configure service vprn ecmp-unequal-cost

Description

This command relaxes the constraint that ECMP multipaths must have the same IGP cost to reach the BGP next-hop. When VPN routes for the same IP prefix are imported into a VPRN service, they are eligible to be used as multipaths. The resulting route is programmed as an ECMP IP route.

The BGP best path selection algorithm is the basis for choosing the set of imported VPN routes that can be combined to form an ECMP route. Normally (unless an ignore-nh-metric command is configured), the BGP decision process gives higher preference to VPN routes with a lower next-hop cost if other, more significant criteria, are tied. In these circumstances, a VPN route cannot be an eligible multipath if it does not have the same next-hop cost as the best VPN route. Configuring this command removes this restriction and allows the multipaths to have different (meaning lower) next-hop costs than the best route. This broadens the applicability of multipath and can result in better load balancing in the network.

This command applies only to the following types of routes imported by a VPRN.

  • vpn-ipv4

  • vpn-ipv6

  • mcast-vpn-ipv4

  • mcast-vpn-ipv6

The no form of this command restores the default behavior that requires next-hop costs of multipaths to be equal, unless the next-hop cost is completely removed from the BGP decision process.

Default

ecmp-unequal-cost

Platforms

All

ect-algorithm

ect-algorithm

Syntax

ect-algorithm fid-range fid-range {low-path-id| high-path-id}

Context

[Tree] (config>service>vpls>spb>level ect-algorithm)

Full Context

configure service vpls spb level ect-algorithm

Description

This command configures the ect-algorithm associated with a FID. Names are:

  • low-path-id

  • high-path-id

The algorithm for low-path-id chooses the path with the lowest metric and uses the sum of each Bridge-ID to break-ties (in this case preferring the lowest bridge identifiers).

The algorithm for high-path-id choose the path with the lowest metric and the sum of each Bridge-ID (after each one is modified by the algorithm mask) to break-ties (in this case preferring the highest bridge identifiers).

A Forwarding Identifier (FID) is an abstraction of the IEEE 802.1 SPB Base VID and represents the VLAN (B-VPLS) in IS-IS LSPs. B-VPLS services with the same FID share B-MACs and I-SIDs. (the SAP encapsulation VLAN tag may be set to the same value as the FID or to any other valid VLAN tag). One or more FIDs can be associated with an ECT-algorithm by using the FID range. User B-VPLS services may share the same FID as the control B-VPLS or use independent FIDs where each FID has an assigned ect-algorithm. B-VPLS services with i-vpls services must have an independent FID. B-VPLS services with only PBB Epipes may share FIDs with other B-VPLS services including the control B-VPLS service.

The ect-algorithm is associated with the FID and can only be changed only when there are no VPLS, SAPs or SDP bindings associated with the FID. The FID must be independent from the FID assigned to other services.

Default

ect-algorithm fid-range 1-4095 low-path-id

Parameters

name

low-path-id, high-path-id.

fid-range

Range of Forwarding Identifier values.

Values

1 to 4095

Platforms

All

edge-port

edge-port

Syntax

[no] edge-port

Context

[Tree] (config>service>vpls>sap>stp edge-port)

[Tree] (config>service>template>vpls-sap-template>stp edge-port)

[Tree] (config>service>vpls>spoke-sdp>stp edge-port)

Full Context

configure service vpls sap stp edge-port

configure service template vpls-sap-template stp edge-port

configure service vpls spoke-sdp stp edge-port

Description

This command configures the SAP or SDP as an edge or non-edge port. If auto-edge is enabled for the SAP, this value will be used only as the initial value.

Note:

The function of the edge-port command is similar to the rapid-start command. It tells RSTP that it is on the edge of the network (for example, there are no other bridges connected to that port) and, as a consequence, it can immediately transition to a forwarding state if the port becomes available.

RSTP, however, can detect that the actual situation is different from what edge-port may indicate.

Initially, the value of the SAP or spoke-SDP parameter is set to edge-port. This value will change if:

  • A BPDU is received on that port. This means that after all there is another bridge connected to this port. Then the edge-port becomes disabled.

  • If auto-edge is configured and no BPDU is received within a certain period of time, RSTP concludes that it is on an edge and enables the edge-port.

The no form of this command returns the edge port setting to the default value.

Default

no edge-port

Platforms

All

edge-port

Syntax

[no] edge-port

Context

[Tree] (config>service>pw-template>stp edge-port)

Full Context

configure service pw-template stp edge-port

Description

This command configures the SAP or SDP as an edge or non-edge port. If auto-edge is enabled for the SAP, this value will be used only as the initial value.

Note:

On the 7750 SR and the 7950 XRS, the function of the edge-port command is similar to the rapid-start command. It tells RSTP that it is on the edge of the network (for example, there are no other bridges connected to that port) and, as a consequence, it can immediately transition to a forwarding state if the port becomes available.

RSTP, however, can detect that the actual situation is different from what edge-port may indicate.

Initially, the value of the SAP or spoke SDP parameter is set to edge-port. This value will change if:

  • A BPDU is received on that port. This means that after all there is another bridge connected to this port. Then the edge-port becomes disabled.

  • If auto-edge is configured and no BPDU is received within a certain period of time, RSTP concludes that it is on an edge and enables the edge-port.

The no form of this command returns the edge port setting to the default value.

Default

no edge-port

Platforms

All

edit

edit

Syntax

edit [exclusive]

Context

[Tree] (candidate edit)

Full Context

candidate edit

Description

This command enables the edit-cfg mode where changes can be made to the candidate configuration and sets the edit-point to the end of the candidate. In edit-cfg mode the CLI prompt contains edit-cfg near the root of the prompt. Commands in the candidate CLI branch, except candidate edit, are available only when in edit-cfg mode.

Parameters

exclusive

Allows a user to exclusively create a candidate configuration by blocking other users (and other sessions of the same user) from entering edit-cfg mode. Exclusive edit-cfg mode can only be entered if the candidate configuration is empty and no user is in edit-cfg mode. Once a user is in exclusive edit-cfg mode no other users/sessions are allowed in edit-cfg mode. The user must either commit or discard the exclusive candidate before leaving exclusive edit-cfg mode. If the CLI session times out while a user is in exclusive edit-cfg mode then the contents of the candidate are discarded. The admin disconnect command can be used to force a user to disconnect (and to clear the contents of the candidate) if they have the candidate locked.

Platforms

All

edit-config

edit-config

Syntax

[no] edit-config

Context

[Tree] (configure>system>security>profile>netconf>base-op-authorization edit-config)

Full Context

configure system security profile netconf base-op-authorization edit-config

Description

This command enables the NETCONF edit-config operation.

The no form of this command disables the operation.

Default

no edit-config

Note:

The operation is enabled by default in the built-in system-generated administrative profile.

Platforms

All

efm

efm

Syntax

efm port-id local-loopback {start | stop}

efm port-id remote-loopback {start | stop}

Context

[Tree] (oam efm)

Full Context

oam efm

Description

This command enables Ethernet in the First Mile (EFM) OAM tests loopback tests on the specified port. The EFM OAM remote loopback OAMPDU is sent to the peering device to trigger remote loopback.

When EFM OAM is disabled or shutdown on a port, the dying gasp flag for the OAMPDU is set for the OAMPDUs sent to the peer. This speeds up the peer loss detection time.

Parameters

port-id

Specifies the port ID.

Note:

On the 7950 XRS, The XMA ID takes the place of the MDA.

port-id

slot/mda/port [.channel]

eth-sat-id

esat-id/slot/port

esat

keyword

id

1 to 20

pxc-id

pxc-id.sub-port

pxc

keyword

id

1 to 64

sub-port

a, b

local-loopback {start | stop}

Specifies whether to start or stop local loopback tests on the specified port.

remote-loopback {start | stop}

Specifies whether to start or stop remote Ethernet in the First Mile (EFM) OAM loopback tests on the specified port. The EFM OAM remote loopback OAMPDU is sent to the peering device to trigger remote loopback.

For EFM OAM tunneling to function properly, EFM OAM tunneling should be configured for VLL services or a VPLS service with two SAPs only.

Platforms

All

efm-oam

efm-oam

Syntax

efm-oam

Context

[Tree] (config>port>ethernet efm-oam)

Full Context

configure port ethernet efm-oam

Description

This command configures EFM-OAM attributes.

Platforms

All

egr-ip-load-balancing

egr-ip-load-balancing

Syntax

egr-ip-load-balancing {source | destination | inner-ip}

no egr-ip-load-balancing

Context

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

Full Context

configure service ies interface load-balancing egr-ip-load-balancing

Description

This command specifies whether to include the source address or destination address or both in the LAG/ECMP hash on IP interfaces. Additionally, when l4-load-balancing is enabled, the command also applies to the inclusion of source/destination port in the hash inputs.

The no form of this command includes both source and destination parameters.

Default

no egr-ip-load-balancing

Parameters

source

Specifies using the source address and, if l4-load balancing is enabled, the source port in the hash, ignore destination address/port.

destination

Specifies using the destination address and, if l4-load balancing is enabled, the destination port in the hash, ignore source address/port.

inner-ip

Specifies using the inner IP header parameters instead of the outer IP header parameters in the LAG/ECMP hash for IPv4 encapsulated traffic.

Platforms

All

egr-ip-load-balancing

Syntax

egr-ip-load-balancing {source | destination | inner-ip}

no egr-ip-load-balancing

Context

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

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

Full Context

configure service vprn interface nw-if load-balancing egr-ip-load-balancing

configure service vprn interface load-balancing egr-ip-load-balancing

Description

This command specifies whether to include the source address or destination address or both in the LAG/ECMP hash on IP interfaces. Additionally, when l4-load-balancing is enabled, the command also applies to the inclusion of source/destination port in the hash inputs.

The no form of this command includes both source and destination parameters.

Default

no egr-ip-load-balancing

Parameters

source

Specifies using the source address and (if l4-load balancing is enabled) source port in the hash, ignore destination address/port.

destination

Specifies using the destination address and (if l4-load balancing is enabled) destination port in the hash, ignore source address/port.

inner-ip

Specifies use of the inner IP header parameters instead of outer IP header parameters in LAG/ECMP hash for IPv4 encapsulated traffic.

Platforms

All

egr-ip-load-balancing

Syntax

egr-ip-load-balancing {source | destination | inner-ip}

no egr-ip-load-balancing

Context

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

Full Context

configure router interface load-balancing egr-ip-load-balancing

Description

This command specifies whether to include source address or destination address or both in LAG/ECMP hash on IP interfaces. Additionally, when l4-load-balancing is enabled the command applies also to inclusion of source/destination port in the hash inputs.

The no form of this command includes both source and destination parameters.

Default

no egr-ip-load-balancing

Parameters

source

Specifies using source address and (if l4-load balancing is enabled) source port in the hash, ignore destination address/port

destination

Specifies using destination address and (if l4-load balancing is enabled) destination port in the hash, ignore source address/port.

inner-ip

Specifies use of the inner IP header parameters instead of outer IP header parameters in LAG/ECMP hash for IPv4 encapsulated traffic.

Platforms

All

egr-percentage-of-rate

egr-percentage-of-rate

Syntax

egr-percentage-of-rate egr-rate-percentage

no egr-percentage-of-rate

Context

[Tree] (config>port>modify-buffer-allocation-rate egr-percentage-of-rate)

Full Context

configure port modify-buffer-allocation-rate egr-percentage-of-rate

Description

The egr-percentage-of-rate command increases or decreases the active bandwidth associated with the egress port that affects the amount of egress buffer space managed by the port. Changing a ports active bandwidth using the egr-percentage-of-rate command is an effective means of artificially lowering the buffers managed by one egress port and giving them to other egress ports on the same MDA.

The egr-percentage-of-rate command accepts a percentage value that increases or decreases the active bandwidth based on the defined percentage. A value of 50% causes the active bandwidth to be reduced by 50%. A value of 150% causes the active bandwidth to be increased by 50%. Values from 1 to 1000 percent are supported.

A value of 100 (the default value) is equivalent to executing the no egr-percentage-of-rate command and restores the egress active rate to the normal value.

The no form of this command removes any artificial increase or decrease of the egress active bandwidth used for egress buffer space allocation to the port. The no egr-percentage-of-rate command sets the egress rate percentage to 100%.

Parameters

egr-rate-percentage

The egr-rate-percentage parameter is required and specifies the percentage value used to modify the current egress active bandwidth of the port. This does not actually change the bandwidth available on the port in any way. The defined egr-rate-percentage parameter is multiplied by the egress active bandwidth of the port. A value of 150 results in an increase of 50% (1.5 x Rate).

Values

1 to 1000

Default

100 (no change to active rate)

Platforms

All

egr-vtep

egr-vtep

Syntax

egr-vtep {ip-address | ipv6-address}

no egr-vtep

Context

[Tree] (config>service>epipe>vxlan egr-vtep)

[Tree] (config>service>vpls>vxlan egr-vtep)

Full Context

configure service epipe vxlan egr-vtep

configure service vpls vxlan egr-vtep

Description

This command configures the static destination VTEP IP used when originating VXLAN packets for the service.

Parameters

ip-address

Specifies the IPv4 address used as the destination VTEP when originating VXLAN packets for the service.

ipv6-address

Specifies the IPv6 address used as the destination VTEP when originating VXLAN packets for the service.

Platforms

All

  • configure service epipe vxlan egr-vtep

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

  • configure service vpls vxlan egr-vtep

egr-weight

egr-weight

Syntax

egr-weight access access-weight network network-weight

no egr-weight

Context

[Tree] (config>port>hybrid-buffer-allocation egr-weight)

Full Context

configure port hybrid-buffer-allocation egr-weight

Description

This command configures the sharing of the egress buffers allocated to a hybrid port among the access and network contexts. By default, it is split equally between network and access.

The no form of this command reverts to the default values for the egress access and network weights.

Parameters

access-weight

Specifies the access weight as an integer.

Values

0 to 100

Default

50

network-weight

Specifies the network weight as an integer.

Values

0 to 100

Default

50

Platforms

All

egress

egress

Syntax

egress

Context

[Tree] (config>subscr-mgmt>ancp>ancp-policy egress)

Full Context

configure subscriber-mgmt ancp ancp-policy egress

Description

Commands in this context configure egress ANCP policy parameters.

Platforms

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

egress

Syntax

egress

Context

[Tree] (config>subscr-mgmt>msap-policy>vpls-only egress)

[Tree] (config>subscr-mgmt>msap-policy>ies-vprn egress)

Full Context

configure subscriber-mgmt msap-policy vpls-only-sap-parameters egress

configure subscriber-mgmt msap-policy ies-vprn-only-sap-parameters egress

Description

Commands in this context configure egress policies for Managed SAPs (MSAPs).

Platforms

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

egress

Syntax

egress

Context

[Tree] (config>service>vprn>if>spoke-sdp egress)

[Tree] (config>service>vprn>red-if>spoke-sdp egress)

Full Context

configure service vprn interface spoke-sdp egress

configure service vprn redundant-interface spoke-sdp egress

Description

This command configures egress SDP parameters.

Platforms

All

  • configure service vprn interface spoke-sdp egress

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

  • configure service vprn redundant-interface spoke-sdp egress

egress

Syntax

egress

Context

[Tree] (config>subscr-mgmt>sla-profile egress)

Full Context

configure subscriber-mgmt sla-profile egress

Description

Commands in this context configure egress parameters for the SLA profile.

Platforms

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

egress

Syntax

egress

Context

[Tree] (config>service>vprn>sub-if>grp-if>sap egress)

[Tree] (config>service>ies>if>sap egress)

[Tree] (config>service>vpls>sap egress)

[Tree] (config>service>ies>sub-if>grp-if>sap egress)

Full Context

configure service vprn subscriber-interface group-interface sap egress

configure service ies interface sap egress

configure service vpls sap egress

configure service ies subscriber-interface group-interface sap egress

Description

Commands in this context configure egress Quality of Service (QoS) policies and filter policies.

If no QoS policy is defined, the system default QoS policy is used for egress processing. If no egress filter is defined, no filtering is performed.

Platforms

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

  • configure service vprn subscriber-interface group-interface sap egress
  • configure service ies subscriber-interface group-interface sap egress

All

  • configure service ies interface sap egress
  • configure service vpls sap egress

egress

Syntax

egress

Context

[Tree] (config>service>vpls>sap egress)

Full Context

configure service vpls sap egress

Description

Commands in this context configure egress filter policies.

If no sap-egress QoS policy is defined, the system default sap-egress QoS policy is used for egress processing. If no egress filter is defined, no filtering is performed.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>service>vpls>mesh-sdp egress)

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

[Tree] (config>service>ies>if>spoke-sdp egress)

[Tree] (config>service>ies>red-if>spoke-sdp egress)

Full Context

configure service vpls mesh-sdp egress

configure service vpls spoke-sdp egress

configure service ies interface spoke-sdp egress

configure service ies redundant-interface spoke-sdp egress

Description

Commands in this context configure egress SDP parameters.

Platforms

All

  • configure service vpls mesh-sdp egress
  • configure service vpls spoke-sdp egress
  • configure service ies interface spoke-sdp egress

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

  • configure service ies redundant-interface spoke-sdp egress

egress

Syntax

egress

Context

[Tree] (config>port>ethernet>access egress)

[Tree] (config>port>ethernet>network egress)

Full Context

configure port ethernet access egress

configure port ethernet network egress

Description

This command configures Ethernet access egress port parameters.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw egress)

Full Context

configure service ies subscriber-interface group-interface wlan-gw egress

Description

Commands in this context configure egress QoS parameters for wlan-gw tunnels.

Platforms

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

egress

Syntax

egress

Context

[Tree] (config>card>mda>network egress)

[Tree] (config>port>access egress)

[Tree] (config>port>network egress)

[Tree] (config>card>mda>access egress)

Full Context

configure card mda network egress

configure port access egress

configure port network egress

configure card mda access egress

Description

Commands in this context configure egress buffer pool parameters which define the percentage of the pool buffers that are used for CBS calculations and specify the slope policy that is configured in the config>qos>slope-policy context.

On the MDA level, network and access egress pools are only allocated on channelized MDAs.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>card>fp egress)

Full Context

configure card fp egress

Description

This command enables access to the egress fp CLI context.

Platforms

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

egress

Syntax

egress

Context

[Tree] (config>port>ethernet egress)

Full Context

configure port ethernet egress

Description

This command configures Ethernet egress port parameters.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>service>sdp>binding>pw-port egress)

Full Context

configure service sdp binding pw-port egress

Description

Commands in this context configure PW port egress side parameters.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>service>epipe>sap egress)

[Tree] (config>service>ipipe>sap egress)

[Tree] (config>service>cpipe>sap egress)

Full Context

configure service epipe sap egress

configure service ipipe sap egress

configure service cpipe sap egress

Description

Commands in this context configure egress SAP parameters.

If no sap-egress QoS policy is defined, the system default sap-egress QoS policy is used for egress processing.

Platforms

All

  • configure service epipe sap egress
  • configure service ipipe sap egress

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

  • configure service cpipe sap egress

egress

Syntax

egress

Context

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

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

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

Full Context

configure service epipe spoke-sdp egress

configure service ipipe spoke-sdp egress

configure service cpipe spoke-sdp egress

Description

This command configures the egress SDP context.

Platforms

All

  • configure service ipipe spoke-sdp egress
  • configure service epipe spoke-sdp egress

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

  • configure service cpipe spoke-sdp egress

egress

Syntax

egress

Context

[Tree] (config>service>epipe>pw-port egress)

Full Context

configure service epipe pw-port egress

Description

Commands in this context configure PW-port egress-side parameters

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>service>template>epipe-sap-template egress)

Full Context

configure service template epipe-sap-template egress

Description

Commands in this context configure egress filter policies.

Platforms

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

egress

Syntax

egress

Context

[Tree] (config>service>ies>aarp-interface>spoke-sdp egress)

Full Context

configure service ies aarp-interface spoke-sdp egress

Description

Commands in this context configure the egress for a spoke SDP.

Platforms

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

egress

Syntax

egress

Context

[Tree] (config>service>ies>if>vpls egress)

Full Context

configure service ies interface vpls egress

Description

The egress node under the vpls binding is used to define the optional sap-egress QoS policy that will be used for reclassifying the egress forwarding class or profile for routed packets associated with the IP interface on the attached VPLS or I-VPLS service context.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>service>vprn>aarp-interface>spoke-sdp egress)

Full Context

configure service vprn aarp-interface spoke-sdp egress

Description

Commands in this context configure the egress for a spoke SDP.

Platforms

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

egress

Syntax

egress

Context

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

Full Context

configure service vprn network-interface egress

Description

Commands in this context configure egress network filter policies for the interface.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>service>vprn>if>sap egress)

Full Context

configure service vprn interface sap egress

Description

Commands in this context configure egress SAP Quality of Service (QoS) policies and filter policies.

If no sap-egress QoS policy is defined, the system default sap-egress QoS policy is used for egress processing. If no egress filter is defined, no filtering is performed.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>service>vprn>if>vpls egress)

Full Context

configure service vprn interface vpls egress

Description

The egress node under the vpls binding is used to define the optional sap-egress QoS policy that will be used for reclassifying the egress forwarding class or profile for routed packets associated with the IP interface on the attached VPLS service context.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>service>vprn>network-interface egress)

Full Context

configure service vprn network-interface egress

Description

Commands in this context configure egress network filter policies for the interface.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>service>vprn>aa-interface>sap egress)

[Tree] (config>service>ies>aa-interface>sap egress)

Full Context

configure service vprn aa-interface sap egress

configure service ies aa-interface sap egress

Description

Commands in this context configure egress parameters.

Platforms

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

egress

Syntax

egress

Context

[Tree] (config>isa>aa-grp>qos egress)

Full Context

configure isa application-assurance-group qos egress

Description

Commands in this context configure IOM port-level Quality of Service for this application assurance group in the egress direction (traffic entering an application assurance engine).

Platforms

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

egress

Syntax

egress

Context

[Tree] (config>service>vprn>video-interface>video-sap egress)

[Tree] (config>service>ies>video-interface>video-sap egress)

Full Context

configure service vprn video-interface video-sap egress

configure service ies video-interface video-sap egress

Description

Commands in this context configure egress parameters for the service’s video SAP.

Platforms

7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

egress

Syntax

egress

Context

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

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

Full Context

configure mirror mirror-dest remote-source spoke-sdp egress

configure mirror mirror-dest spoke-sdp egress

Description

Commands in this context configure spoke SDP egress parameters.

Platforms

All

egress

Syntax

[no] egress

Context

[Tree] (config>mirror>mirror-dest>sap egress)

Full Context

configure mirror mirror-dest sap egress

Description

This command enables access to the context to associate an egress SAP Quality of Service (QoS) policy with a mirror destination SAP.

If no QoS policy is defined, the system default SAP egress QoS policy is used for egress processing.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>qos>network egress)

Full Context

configure qos network egress

Description

This command is used to enter the CLI node that creates or edits egress policy entries that specify the forwarding class queues to be instantiated when this policy is applied to the network port.

The forwarding class and profile state mapping to in- and out-of-profile DiffServ Code Points (DSCPs), dot1p, and MPLS EXP bits mapping for all labeled packets are also defined in this context.

All service packets are aggregated into DiffServ-based egress queues on the network interface. The service packets are transported either with IP GRE encapsulation or over a MPLS LSP. The exception is with the IES service. In this case, the actual customer IP header has the DSCP field mapped.

All out-of-profile service packets are marked with the corresponding out-of-profile DSCP, dot1p, or the EXP bit value at network egress. All the in-profile service ingress packets are marked with the corresponding in-profile DSCP, dot1p, or EXP bit value based on the forwarding class to which they belong. The exceed-profile traffic is marked with the same value as out-of-profile traffic and the inplus-profile traffic is marked with the same value as in-profile traffic.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>qos>queue-group-templates egress)

Full Context

configure qos queue-group-templates egress

Description

Commands in this context configure QoS egress queue groups. Egress queue group templates can be applied to egress Ethernet ports to create an egress queue group.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>router>if egress)

Full Context

configure router interface egress

Description

This command enables access to the context to configure egress network filter policies for the IP interface. If an egress filter is not defined, no filtering is performed.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>service>cust>multi-service-site egress)

Full Context

configure service customer multi-service-site egress

Description

Commands in this context configure the egress node associate an existing scheduler policy name with the customer site. The egress node is an entity to associate commands that complement the association.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>service>pw-template egress)

Full Context

configure service pw-template egress

Description

Commands in this context configure spoke SDP binding egress filter parameters.

Platforms

All

egress

Syntax

egress

Context

[Tree] (config>subscr-mgmt>sub-prof egress)

Full Context

configure subscriber-mgmt sub-profile egress

Description

Commands in this context configure subscriber profile egress setting parameters.

Platforms

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

egress-counter-map

egress-counter-map

Syntax

egress-counter-map policer policer-id traffic-type {unicast | multicast | broadcast} [create]

egress-counter-map queue queue-id traffic-type {unicast | multicast | broadcast} [create]

no egress-counter-map policer policer-id

no egress-counter-map queue queue-id

Context

[Tree] (config>sflow egress-counter-map)

Full Context

configure sflow egress-counter-map

Description

This command configures the egress counter map for sFlow. The map must be configured so sFlow agent understands how to interpret data collected against SAP queues and policers. Multiple queues and policers can be mapped to the same traffic-type using separate line entries.

The no form of this command deletes a SAP policy queue/policer from the map.

Parameters

policer-id

Specifies the policer ID in a SAP egress QoS policy. If the SAP policy does not have a policer with the specified ID, the map entry will be ignored for this SAP.

Values

1 to 8

queue-id

Specifies the queue ID in a SAP egress QoS policy. If the SAP policy does not have a queue with the specified ID, the map entry will be ignored for this SAP.

Values

1 to 8

Platforms

7750 SR, 7750 SR-s, 7950 XRS

egress-engineering

egress-engineering

Syntax

egress-engineering

no egress-engineering

Context

[Tree] (config>router>bgp>group egress-engineering)

[Tree] (config>router>bgp>group>neighbor egress-engineering)

Full Context

configure router bgp group egress-engineering

configure router bgp group neighbor egress-engineering

Description

Commands in this context configure egress engineering on a specific neighbor or all neighbors in a BGP group.

If egress engineering is not configured in the neighbor context, the configuration is inherited from the group context.

The no form of this command removes the egress engineering configuration.

Default

no egress-engineering

Platforms

All

egress-fc

egress-fc

Syntax

egress-fc fc-name

no egress-fc

Context

[Tree] (config>qos>sap-ingress>fc egress-fc)

Full Context

configure qos sap-ingress fc egress-fc

Description

This command configures the forwarding class to be used by the egress QoS processing. It overrides the forwarding class determined by ingress classification but not the QoS Policy Propagation via BGP.

The forwarding class or forwarding subclass can be overridden.

The new egress forwarding class is applicable to both SAP egress and network egress.

Default

no egress-fc

Parameters

fc-name

Specifies the forwarding class name to be used by the egress QoS processing.

Values

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

Platforms

All

egress-ip-filter-entries

egress-ip-filter-entries

Syntax

[no] egress-ip-filter-entries

Context

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl egress-ip-filter-entries)

Full Context

configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ip-filter-entries

Description

Commands in this context configure the egress IP filter parameters.

The no form of this command reverts to the default.

Default

egress-ip-filter-entries

Platforms

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

egress-ipv6-filter-entries

egress-ipv6-filter-entries

Syntax

[no] egress-ipv6-filter-entries

Context

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl egress-ipv6-filter-entries)

Full Context

configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ipv6-filter-entries

Description

Commands in this context configure the egress IPv6 filter parameters.

The no form of this command reverts to the default.

Default

egress-ipv6-filter-entries

Platforms

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

egress-pbr

egress-pbr

Syntax

egress-pbr {default-load-balancing | l4-load-balancing}

no egress-pbr

Context

[Tree] (config>filter>ipv6-filter>entry egress-pbr)

[Tree] (config>filter>ip-filter>entry egress-pbr)

Full Context

configure filter ipv6-filter entry egress-pbr

configure filter ip-filter entry egress-pbr

Description

This command specifies that the configured PBR action is applicable to egress processing. The command should only be enabled in ACL policies used by residential subscribers. Enabling egress-pbr on filters not deployed for residential subscribers is not blocked but may lead to unexpected behavior and should be avoided.

The no form of this command removes the egress-pbr designation of the filter entry's action.

Default

no egress-pbr

Parameters

default-load-balancing

Sets load-balancing to the default (hash based on SA/DA of the packet).

l4-load-balancing

Includes TCP/UDP port (if available) in the hash.

Platforms

All

egress-peer-engineering

egress-peer-engineering

Syntax

egress-peer-engineering

no egress-peer-engineering

Context

[Tree] (config>router>bgp egress-peer-engineering)

Full Context

configure router bgp egress-peer-engineering

Description

Commands in this context configure EPE parameters in BGP.

The no form of this command removes the EPE parameters from the BGP context.

Default

no egress-peer-engineering

Platforms

All

egress-peer-engineering-label-unicast

egress-peer-engineering-label-unicast

Syntax

[no] egress-peer-engineering-label-unicast

Context

[Tree] (config>router>bgp>group egress-peer-engineering-label-unicast)

[Tree] (config>router>bgp>group>neighbor egress-peer-engineering-label-unicast)

Full Context

configure router bgp group egress-peer-engineering-label-unicast

configure router bgp group neighbor egress-peer-engineering-label-unicast

Description

This command enables the generation of a label-unicast route for each /32 or /128 prefix that corresponds to the BGP neighbor or group address in the scope of the command. These routes can be advertised to other routers to recursively resolve unlabeled BGP routes for AS external destinations. They support the Egress Peer Engineering (EPE) use case.

The no form of this command disables the generation of EPE label-unicast routes.

Default

no egress-peer-engineering-label-unicast

Platforms

All

egress-policer

egress-policer

Syntax

egress-policer [policer-name]

no egress-policer

Context

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

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

Full Context

configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range distributed-sub-mgmt egress-policer

configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range distributed-sub-mgmt egress-policer

Description

This command specifies the egress policer applied to all UEs corresponding to default vlan-range (such as, group-interface) or the specified vlan-range. The policer can be created in the config>subscr-mgmt>isa-policer context. The egress policer can be overridden per UE from RADIUS via access-accept or COA.

The no form of this command reverts to the default.

Parameters

policer-name

Specifies the identifier of the distributed-sub-mgmt policer for egress traffic up to 256 characters.

Platforms

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

egress-port-queue-overrides

egress-port-queue-overrides

Syntax

egress-port-queue-overrides

Context

[Tree] (config>port>ethernet>network egress-port-queue-overrides)

Full Context

configure port ethernet network egress-port-queue-overrides

Description

Commands in this context configure Ethernet network egress port queue override parameters.

Platforms

All

egress-rate

egress-rate

Syntax

egress-rate sub-rate

no egress-rate

Context

[Tree] (config>port>ethernet egress-rate)

Full Context

configure port ethernet egress-rate

Description

This command configures the rate of traffic leaving the network. The configured sub-rate uses packet-based accounting. An event log is generated each time the egress rate is modified unless the port is part of a LAG.

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

Default

no egress-rate

Parameters

sub-rate

Specifies the egress rate in kb/s.

Values

1 to 100000000

Platforms

All

egress-rate-modify

egress-rate-modify

Syntax

egress-rate-modify agg-rate-limit

egress-rate-modify scheduler scheduler-name

no egress-rate-modify

Context

[Tree] (config>subscr-mgmt>trk-plcy egress-rate-modify)

Full Context

configure subscriber-mgmt host-tracking-policy egress-rate-modify

Description

This command specifies the egress-rate modification that is to be applied.

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

Parameters

agg-rate-limit

Specifies to use the egress rate limit.

scheduler-name

Specifies the scheduler name up to 32 characters.

Platforms

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

egress-rate-modify

Syntax

egress-rate-modify [agg-rate-limit | scheduler scheduler-name]

no egress-rate-modify

Context

[Tree] (config>subscr-mgmt>igmp-policy egress-rate-modify)

Full Context

configure subscriber-mgmt igmp-policy egress-rate-modify

Description

This command is used to apply HQoS Adjustment to a subscriber. HQoS Adjustment is needed when multicast traffic flow for the subscriber is dissociated from subscriber host queues. Multicast redirection is typical such case although it can be applied in direct IPoE subscriber per-sap replication mode.

The channel bandwidth definition policy is defined in the mcac policy under the config>router>mcac>policy context. The policy is applied under the redirected interface or under the group-interface.

In order for HQoS Adjustment to take effect, sub-mcac-policy must be in a no shutdown mode and applied under the sub-profile even if mcac is not deployed.

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

Parameters

agg-rate-limit

Specifies the aggregate14 rate modification to be applied. The subscriber’s bandwidth is capped via the agg-rate-limit command in the sub-profile or with a Change of Authorization (CoA) request. This bandwidth cap is dynamically adjusted according to the multicast channel definition and channel association with the host via IGMP.

scheduler-name

Specifies the schedule name. The subscriber’s bandwidth is capped via the scheduling-policy in the sub-profile or with a Change of Authorization (CoA) request. HQoS Adjustment will modify the rate of the scheduler defined in the scheduling policy or configured via CoA.

Platforms

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

egress-rate-modify

Syntax

egress-rate-modify agg-rate-limit

egress-rate-modify scheduler scheduler-name

no egress-rate-modify

Context

[Tree] (config>subscr-mgmt>mld-policy egress-rate-modify)

Full Context

configure subscriber-mgmt mld-policy egress-rate-modify

Description

This command configures the egress rate modification.

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

Parameters

agg-rate-limit

Specifies that the maximum total rate for all subscriber egress queues for each subscriber associated with the policy.

scheduler-name

Specifies the scheduler to be applied for egress rate modification.

Platforms

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

egress-rate-modify

Syntax

[no] egress-rate-modify

Context

[Tree] (config>port>ethernet>access>egress>vport egress-rate-modify)

Full Context

configure port ethernet access egress vport egress-rate-modify

Description

This command applies HQoS Adjustment to a Vport. HQoS Adjustment refers to the dynamic adjustment of the rate limit at an QoS enforcement point within a Nokia router when the multicast traffic stream is disjointed from the unicast traffic stream. This QoS enforcement point within the router represents the physical point further down in the access part of the network where the two streams join each other and potentially can cause congestion.

An example would be a PON port which is shared amongst subscriber’s multicast traffic (single copy of each channel) and subscriber’s unicast traffic. The bandwidth control point for this PON port resides in the upstream Nokia BNG node in the form of a Vport. In the case where the multicast delivery method of the BNG utilizes redirection, the multicast traffic in the BNG will flow outside of the subscriber or the Vport context and thus will bypass any bandwidth enforcement in the Nokia router. To correct this, a Vport bandwidth adjustment is necessary in the router that will account for the multicast bandwidth consumption that is bypassing Vport in the router but is present in the PON port whose bandwidth is controlled by Vport.

An estimate of the multicast bandwidth consumption on the PON port can be made at the Vport level based on the IGMP messages sourced from the subscribers behind the PON port. This process is called HQoS Adjustment.

A multicast channel bandwidth is subtracted from or added to the Vport rate limit according to the received IGMP Join/Leave messages and the channel bandwidth definition policy associated with the Vport (indirectly through a group-interface). Since the multicast traffic on the PON port is shared amongst subscribers behind this PON port, only the first IGMP Join or the last IGMP Leave per multicast channel is tracked for the purpose of the Vport bandwidth modification.

The Vport rate that will be affected by this functionality depends on the configuration:

  • In case the agg-rate within the Vport is configured, its value will be modified based on the IGMP activity associated with the subscriber under this Vport.

  • In case the port-scheduler-policy within the Vport is referenced, the max-rate defined in the corresponding port-scheduler-policy will be modified based on the IGMP activity associated with the subscriber under this Vport.

The channel bandwidth definition policy is defined in the mcac policy in the config>router>mcac>policy context. The policy is applied under the group-interface or in case of redirection under the redirected-interface.

The rates in effect can be displayed with the following two commands:

show port 1/1/5 vport name
qos scheduler-hierarchy port port-id vport vport-name

The configuration of a scheduler policy under a Vport, which is only applicable to Ethernet interfaces, is mutually exclusive with the configuration of the egress-rate-modify parameter.

Context: HQoS Adjustment for Vport is disabled.

Platforms

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

egress-scheduler-override

egress-scheduler-override

Syntax

egress-scheduler-override [create]

no egress-scheduler-override

Context

[Tree] (config>port>tdm>e3 egress-scheduler-override)

[Tree] (config>port>tdm>ds3 egress-scheduler-override)

[Tree] (config>port>tdm>e1>channel-group egress-scheduler-override)

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

[Tree] (config>port>tdm>ds1>channel-group egress-scheduler-override)

[Tree] (config>port>sonet-sdh>path egress-scheduler-override)

Full Context

configure port tdm e3 egress-scheduler-override

configure port tdm ds3 egress-scheduler-override

configure port tdm e1 channel-group egress-scheduler-override

configure port ethernet egress-scheduler-override

configure port tdm ds1 channel-group egress-scheduler-override

configure port sonet-sdh path egress-scheduler-override

Description

This command applies egress scheduler overrides. When a port scheduler is associated with an egress port, it is possible to override the following parameters:

  • The max-rate allowed for the scheduler.

  • The maximum rate for each priority level 8 through 1.

  • The CIR associated with each priority level 8 through 1.

See the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide for command syntax and usage for the port-scheduler-policy command.

The no form of this command removes all override parameters from the egress port or channel scheduler context. Once removed, the port scheduler reverts all rate parameters back to the parameters defined on the port-scheduler-policy associated with the port.

Parameters

create

Mandatory while creating an entry.

Platforms

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

  • configure port tdm e1 channel-group egress-scheduler-override
  • configure port tdm e3 egress-scheduler-override
  • configure port tdm ds1 channel-group egress-scheduler-override
  • configure port tdm ds3 egress-scheduler-override

All

  • configure port ethernet egress-scheduler-override

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

  • configure port sonet-sdh path egress-scheduler-override

egress-scheduler-policy

egress-scheduler-policy

Syntax

egress-scheduler-policy port-sched-plcy

no egress-scheduler-policy

Context

[Tree] (config>port-policy egress-scheduler-policy)

Full Context

configure port-policy egress-scheduler-policy

Description

This command references a port scheduler policy that is defined under the config>qos>port-scheduler-policy> hierarchy. Port schedulers are instantiated on carrier IOMs towards all ISAs that are part of the lns-group.

The no form of the command removes the port scheduler policy from the configuration.

Default

no egress-scheduler-policy

Parameters

port-sched-plcy

Specifies the egress scheduler policy, up to 32 characters.

Platforms

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

egress-scheduler-policy

Syntax

egress-scheduler-policy port-scheduler-policy-name

no egress-scheduler-policy

Context

[Tree] (config>port>tdm>e3 egress-scheduler-policy)

[Tree] (config>port>sonet-sdh>path egress-scheduler-policy)

[Tree] (config>port>tdm>ds3 egress-scheduler-policy)

[Tree] (config>port>ethernet egress-scheduler-policy)

[Tree] (config>port>tdm>ds1>channel-group egress-scheduler-policy)

[Tree] (config>port>tdm>e1>channel-group egress-scheduler-policy)

Full Context

configure port tdm e3 egress-scheduler-policy

configure port sonet-sdh path egress-scheduler-policy

configure port tdm ds3 egress-scheduler-policy

configure port ethernet egress-scheduler-policy

configure port tdm ds1 channel-group egress-scheduler-policy

configure port tdm e1 channel-group egress-scheduler-policy

Description

This command enables the provisioning of an existing port-scheduler-policy to a port or channel.

The egress-scheduler-override node allows for the definition of the scheduler overrides for a specific port or channel.

When a port scheduler is active on a port or channel, all queues and intermediate service schedulers on the port are subject to receiving bandwidth from the scheduler. Any policers, queues, or schedulers with port-parent associations are mapped to the appropriate port priority levels based on the port-parent command parameters. Any policers, queues, or schedulers that do not have a port-parent or valid intermediate scheduler parent defined are treated as orphaned and are handled based on the port scheduler policies default or explicit orphan behavior.

The port scheduler maximum rate and priority level rate parameters may be overridden to allow unique values separate from the port-scheduler-policy-name attached to the port or channel. Use the egress-scheduler-override command to specify the port or channel specific scheduling parameters.

The no form of this command removes a port scheduler policy from an egress port or channel. Once the scheduler policy is removed, all orphaned policers, queues, and schedulers revert to a free running state governed only by the local queue or scheduler parameters. This includes any queues or schedulers with a port-parent association.

Parameters

port-scheduler-policy-name

Specifies an existing port-scheduler-policy configured in the config>qos context. The name can be up to 32 characters.

Platforms

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

  • configure port tdm ds1 channel-group egress-scheduler-policy
  • configure port tdm e3 egress-scheduler-policy
  • configure port tdm ds3 egress-scheduler-policy
  • configure port tdm e1 channel-group egress-scheduler-policy

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

  • configure port sonet-sdh path egress-scheduler-policy

All

  • configure port ethernet egress-scheduler-policy

egress-statistics

egress-statistics

Syntax

egress-statistics

Context

[Tree] (config>router>ldp egress-statistics)

Full Context

configure router ldp egress-statistics

Description

Commands in this context enter the LDP FEC prefix for the purpose of enabling egress data path statistics at the ingress LER for this FEC.

Platforms

All

egress-statistics

Syntax

[no] egress-statistics

Context

[Tree] (config>router>mpls>lsp-template egress-statistics)

[Tree] (config>router>mpls>lsp egress-statistics)

Full Context

configure router mpls lsp-template egress-statistics

configure router mpls lsp egress-statistics

Description

This command configures statistics in the egress data path of an originating LSP at a head-end node. The user must execute the no shutdown for this command to effectively enable statistics.

Note:

SR-TE LSP egress statistics are not supported on VSR.

The same set of counters is updated for packets forwarded over any path of the RSVP-TE LSP and over the lifetime of the LSP. In steady state, the counters are updated for packets forwarded over the active path of the LSP. The active path can be the primary path, one of the secondary paths, the FRR detour path, or the FRR bypass path when the head-end node is also the PLR.

For SR-TE LSPs, egress statistics are collected independently for each path (primary, backup standby or not), and are preserved on switchover (except for non-standby).

LSP egress statistics are collected if the head-end node is also the Penultimate-Popping Hop (PHP) node for a single-hop LSP using an implicit null egress label.

RSVP-TE LSP statistics are not collected on a dynamic or a static bypass tunnel itself.

Statistics collection on two labels of the stack is possible. Please refer to config>system>ip>mpls>label-stack-statistics-count.

The no form of this command disables the statistics in the egress data path and removes the accounting policy association from the LSP.

Default

no egress-statistics

Platforms

All

egress-statistics

Syntax

[no] egress-statistics

Context

[Tree] (config>router>mpls>fwd-policies>fwd-policy egress-statistics)

Full Context

configure router mpls forwarding-policies forwarding-policy egress-statistics

Description

This command configures egress statistics in an MPLS forwarding policy.

The no form of this command removes any egress statistics in a forwarding policy.

Default

no egress-statistics

Platforms

All

egress-statistics

Syntax

egress-statistics

Context

[Tree] (config>router>ospf3>segm-rtng egress-statistics)

[Tree] (config>router>isis>segm-rtng egress-statistics)

[Tree] (config>router>ospf>segm-rtng egress-statistics)

Full Context

configure router ospf3 segment-routing egress-statistics

configure router isis segment-routing egress-statistics

configure router ospf segment-routing egress-statistics

Description

Commands in this context configure the egress statistics for IGP SIDs.

Platforms

All

egress-statistics

Syntax

[no] egress-statistics

Context

[Tree] (config>router>segment-routing>sr-policies egress-statistics)

Full Context

configure router segment-routing sr-policies egress-statistics

Description

This command administratively enables the collection of egress traffic statistics for all segment routing policies.

The no form of this command disables egress traffic statistics collection for all segment routing policies.

Default

no egress-statistics

Platforms

All

egress-statistics

Syntax

[no] egress-statistics

Context

[Tree] (config>router>policy-options>policy-statement>default-action egress-statistics)

[Tree] (config>router>policy-options>policy-statement>entry>action egress-statistics)

Full Context

configure router policy-options policy-statement default-action egress-statistics

configure router policy-options policy-statement entry action egress-statistics

Description

This command enables the allocation of statistical indexes to BGP-LU route entries that are programmed on an egress data path.

The no form of this command disables the allocation of statistical indexes to BGP-LU entries.

Default

no egress-statistics

Platforms

All

egress-xpl

egress-xpl

Syntax

egress-xpl

Context

[Tree] (config>card>mda egress-xpl)

Full Context

configure card mda egress-xpl

Description

Commands in this context configure egress-xpl settings used by the fail-on-error feature.

Platforms

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

eibgp-loadbalance

eibgp-loadbalance

Syntax

[no] eibgp-loadbalance

Context

[Tree] (config>service>vprn>bgp eibgp-loadbalance)

Full Context

configure service vprn bgp eibgp-loadbalance

Description

This command enables eiBGP load sharing so routes with both MP-BGP and IPv4 next-hops can be used simultaneously.

In order for this command to be effective, the ecmp and multipath commands for the associated VPRN instance must also be configured to allow for multiple routes to the same destination.

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

Default

no eibgp-loadbalance

Platforms

All

elevation-mask-angle

elevation-mask-angle

Syntax

elevation-mask-angle degrees

Context

[Tree] (config>port>gnss elevation-mask-angle)

Full Context

configure port gnss elevation-mask-angle

Description

This command configures the elevation mask angle, which provides a method of filtering satellites used by the system. This command is supported on platforms that have one or more embedded GNSS receivers.

Satellites with low elevation may provide degraded accuracy because of the long signal path through the atmosphere. Signals from satellites below the configured minimum satellite elevation are not used.

Note:

Nokia recommends not to configure an elevation mask angle below 10°.

Default

10

Parameters

degrees

Specifies the elevation mask angle in degrees from the horizon.

Values

0 to 89

Platforms

7750 SR-1-24D, 7750 SR-1-46S, 7750 SR-1-48D, 7750 SR-1-92S, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-1se, 7750 SR-2se

elmi

elmi

Syntax

elmi

Context

[Tree] (config>port>ethernet elmi)

Full Context

configure port ethernet elmi

Description

This command configures Ethernet Local Management Interface (E-LMI) parameters for the Ethernet port. E-LMI is only supported on Ethernet access ports with Dot1q encapsulation type.

Platforms

All

embed-filter

embed-filter

Syntax

embed-filter ip-filter-id [offset offset] [{active | inactive}]

no embed-filter ip-filter-id

embed-filter ipv6-filter-id [offset offset] [{active | inactive}]

no embed-filter ipv6-filter-id

embed-filter flowspec [group group-id] [router {router-instance | service-name vprn-service-name}] [offset offset] [{active | inactive}]

no embed-filter flowspec [group group-id]

embed-filter open-flow ofs-name [{system | service {service-id | service-name} | sap sap-id}] [ offset offset] [{active | inactive}]

no embed-filter open-flow ofs-name [{system | service {service-id | service-name} | sap sap-id}]

Context

[Tree] (config>filter>ip-filter embed-filter)

[Tree] (config>filter>ipv6-filter embed-filter)

Full Context

configure filter ip-filter embed-filter

configure filter ipv6-filter embed-filter

Description

This command embeds a previously defined IPv4, IPv6, or MAC embedded filter policy or Hybrid OpenFlow switch instance into this exclusive, template, or system filter policy at the specified offset value. Rules derived from the BGP FlowSpec can also be embedded into template filter policies only.

The embed-filter open-flow ofs-name form of this command enables OpenFlow (OF) in GRT either by embedding the specified OpenFlow switch (OFS) instance with switch-defined-cookie disabled, or by embedding rules with sros-cookie:type "grt-cookie”, value 0, from the specified OFS instance with switch-defined-cookie enabled. The embedding filter can only be deployed in GRT context or be unassigned.

The embed-filter open-flow ofs-name system form of this command enables OF in system filters by embedding rules with sros-cookie:type "system-cookie”, value 0, from the specified OFS instance with switch-defined-cookie enabled. The embedding filter can only be of scope system.

The embed-filter open-flow ofs-name service {service-id | service-name} form of this command enables OF in VPRN/VPLS filters by embedding rules with sros-cookie:type "service-cookie”, value service-id, from the specified OFS instance with switch-defined-cookie enabled—per service rules. The embedding filter can only be deployed in the specified VPRN/VPLS service. A single VPLS service can only support OF rules per SAP or per service.

The embed-filter open-flow ofs-name sap sap-id form of this command enables OF in VPLS SAP filters by embedding rules with sros-cookie:type "service-cookie”, value service-id and flow match conditions specifying the sap-id from the specified OFS instance with switch-defined-cookie enabled—per SAP OF rules. The embedding filter must be of type exclusive and can only be deployed on the specified SAP in the context of the specified VPLS service. A single VPLS service can only support OF rules per SAP or per service.

The no embed-filter open-flow ofs-name form of this command removes the OF embedding for the GRT context.

The embed-filter flowspec form of this command enables the embedding of rules derived from BGP FlowSpec routes into the filter policy that is being configured. The optional group parameter specifies that only FlowSpec routes tagged with an interface-set extended community containing this group ID should be selected for embedding. The optional router parameter specifies the routing instance source of the BGP FlowSpec routes; if the parameter is not specified, the routing instance is derived automatically from the context in which the filter policy is applied.

The no embed-filter flowspec form of this command removes the FlowSpec filter embedding from this filter policy.

The no embed-filter filter-id form of this command removes the embedding from this filter policy.

See the description of embedded filter policies in this guide for further operational details.

Parameters

ip-filter-id

Specifies a previously defined IPv4 policy for embedding in this filter.

ipv6-filter-id

Specifies a previously defined IPv6 policy for embedding in this filter.

offset

Specifies that an embedded filter entry X will have an entry X + offset in the embedding filter.

Values

0 to 2097151

Default

0

active

Specifies that embedded filter entries are to be included in this embedding filter policy and activated on applicable line cards—default if no keyword is specified and omitted from info command output (but not info detail), or when saving the configuration.

inactive

Specifies that no embedded filter policy entries are to be included in this embedding filter policy. The embedding is configured but will not do anything.

flowspec

This keyword indicates that rules derived from BGP FlowSpec routes should be embedded into (or removed from, in case of the no form) the filter.

group-id

Specifies that only FlowSpec routes with an interface-set extended community with this value of group-id should be selected for embedding.

Values

0 to 16383

router-instance

Specifies a router instance.

vprn-service-name

Specifies the VPRN service name used for embedding FlowSpec rules.

open-flow

Indicates that rules derived from OpenFlow should be embedded into (or removed from, in case of the no form) the filter.

ofs-name

Specifies the name of the currently configured Hybrid OpenFlow Switch (OFS) instance.

Not including the system, service or sap parameters will specify OF in a GRT instance context by default. This allows embedding of OF rules into filters deployed in GRT instances from OFS with switch-defined-cookie disabled, or embedding rules from OFS with switch-defined-cookie enabled, when the FlowTable cookie encodes sros-cookie:type "grt-cookie”.

system

Used for OF control of system filters. Allows embedding of OF rules into system filters from OFS with switch-defined-cookie enabled. Only the rules with cookie value encoding "system-cookie” are embedded.

service-id

Specifies an existing VPRN or VPLS service ID that the embedding filter can be used for.

service-name — Specifies an existing VPRN or VPLS service name that the embedding filter can be used for.

Values

1 to 2147483647

service-name

Specifies an existing VPRN or VPLS service name up to 64 characters that the embedding filter can be used for.

sap-id

Used for OF control of VPLS services when a PortID and VLAN ID match is required. Allows embedding of OF rules with a PortID and VLAN ID match into exclusive VPLS SAP filters. Only the rules with cookie value encoding the VPLS service, and flow table match encoding the specified SAP, are embedded into the filter. The embedding filter can only be deployed in the context of the specified SAP.

sap-id — Specifies an existing SAP that the embedding filter can be used for.

Platforms

All

embedded-rp

embedded-rp

Syntax

embedded-rp

Context

[Tree] (config>service>vprn>pim>rp>ipv6 embedded-rp)

Full Context

configure service vprn pim rp ipv6 embedded-rp

Description

This command enables context to configure IPv6 embedded RP parameters.

Platforms

All

embedded-rp

Syntax

[no] embedded-rp

Context

[Tree] (config>router>pim>rp>ipv6 embedded-rp)

Full Context

configure router pim rp ipv6 embedded-rp

Description

Commands in this context configure embedded RP parameters.

Embedded RP is required to support IPv6 inter-domain multicast because there is no MSDP equivalent in IPv6.

The detailed protocol specification is defined in RFC 3956, Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address. This RFC describes a multicast address allocation policy in which the address of the RP is encoded in the IPv6 multicast group address, and specifies a PIM-SM group-to-RP mapping to use the encoding, leveraging, and extending unicast-prefix-based addressing. This mechanism not only provides a simple solution for IPv6 inter-domain ASM but can be used as a simple solution for IPv6 intra-domain ASM with scoped multicast addresses as well. It can also be used as an automatic RP discovery mechanism in those deployment scenarios that would have previously used the Bootstrap Router protocol (BSR).

The no form of this command disables embedded RP.

Platforms

All

emulated-server

emulated-server

Syntax

emulated-server ip-address

no emulated-server

Context

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

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

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

[Tree] (config>service>vprn>sub-if>ipv6>dhcp6>proxy emulated-server)

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

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

[Tree] (config>service>vprn>sub-if>grp-if>ipv6>dhcp6>proxy-server emulated-server)

[Tree] (config>service>vprn>if>dhcp>proxy-server emulated-server)

Full Context

configure service ies interface dhcp proxy-server emulated-server

configure service vpls sap dhcp proxy-server emulated-server

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

configure service vprn subscriber-interface ipv6 dhcp6 proxy emulated-server

configure service vprn subscriber-interface group-interface dhcp proxy-server emulated-server

configure service ies subscriber-interface group-interface dhcp proxy-server emulated-server

configure service vprn subscriber-interface group-interface ipv6 dhcp6 proxy-server emulated-server

configure service vprn interface dhcp proxy-server emulated-server

Description

This command configures the IP address which is used as the DHCP server address in the context of the SAP. Typically, the configured address should be in the context of the subnet represented by the service.

The no form of this command reverts to the default setting. The local proxy server will not become operational without the emulated-server address being specified.

The no form of this command reverts to the default.

Parameters

ip-address

Specifies the emulated server’s IP address. This address must be unique within the subnet and specified in dotted decimal notation. Allowed values are IP addresses in the range 1.0.0.0 – 223.255.255.255 (with support of /31 subnets).

Platforms

All

  • configure service vpls sap dhcp proxy-server emulated-server
  • configure service ies interface dhcp proxy-server emulated-server
  • configure service vprn interface dhcp proxy-server emulated-server

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

  • configure service vprn subscriber-interface group-interface ipv6 dhcp6 proxy-server emulated-server
  • configure service vprn subscriber-interface group-interface dhcp proxy-server emulated-server
  • configure service ies subscriber-interface group-interface dhcp proxy-server emulated-server
  • configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp proxy-server emulated-server

enable-admin

enable-admin

Syntax

enable-admin

Context

[Tree] (enable-admin)

Full Context

enable-admin

Description

See the description for the admin-password command. If the admin-password is configured in the config>system>security>password context, then any user can enter a special administrative mode by entering the enable-admin command.

enable-admin is in the default profile. By default, all users are given access to this command.

Once the enable-admin command is entered, the user is prompted for a password. If the password matches, the user is given unrestricted access to all the commands.

The minimum length of the password is determined by the minimum-length command. The complexity requirements for the password are determined by the complexity command.

The following shows a password configuration example:

A:ALA-1>config>system>security# info
----------------------------------------------
...
            password
                aging 365
                minimum-length 8
                attempts 5 time 5 lockout 20
                admin-password "rUYUz9XMo6I" hash
            exit
...
----------------------------------------------
A:ALA-1>config>system>security#

There are two ways to verify that a user is in the enable-admin mode:

  • show users — administrator can know which users are in this mode

  • Enter the enable-admin command again at the root prompt and an error message will be returned.

*A:node-1# show users
===============================================================================
User                             Type      Login time           Idle time
  Session ID   From
===============================================================================
                                 Console         --             3d 10:16:12 --
  6            --
admin                            SSHv2     12OCT2018 20:44:15   0d 00:00:00 A-
 #83           192.168.0.10
admin                            SSHv2     12OCT2018 21:09:25   0d 00:05:10 --
  84           192.168.0.10
-------------------------------------------------------------------------------
Number of users: 2
'#' indicates the current active session
'A' indicates user is in admin mode
===============================================================================
*A:node-1# enable-admin
MINOR: CLI Already in admin mode.
*A:node-1#

Platforms

All

enable-admin-control

enable-admin-control

Syntax

enable-admin-control

Context

[Tree] (config>system>security>password enable-admin-control)

Full Context

configure system security password enable-admin-control

Description

Enable the user to become a system administrator.

Note:

This command applies to users on RADIUS, TACACS, and LDAP.

Platforms

All

enable-asm-mdt

enable-asm-mdt

Syntax

[no] enable-asm-mdt

Context

[Tree] (config>service>vprn>mvpn>pt>selective enable-asm-mdt)

Full Context

configure service vprn mvpn provider-tunnel selective enable-asm-mdt

Description

This command enables Data MDT with PIM-ASM mode on the receiver PE node. PIM-ASM or PIM-SSM operation mode is derived based on the locally configured SSM range on the node.

If asm-mode is disabled using this command, then PIM-SSM mode is enabled for all groups, independent of the configured SSM range on the node.

Platforms

All

enable-bfd-leaf

enable-bfd-leaf

Syntax

[no] enable-bfd-leaf

Context

[Tree] (config>service>vprn>mvpn>pt>inclusive>rsvp enable-bfd-leaf)

Full Context

configure service vprn mvpn provider-tunnel inclusive rsvp enable-bfd-leaf

Description

This command enables unidirectional multi-point BFD session on a receiver (leaf) PE node for upstream fast failure detection over RSVP-TE P2MP LSP.

Platforms

All

enable-bfd-leaf

Syntax

[no] enable-bfd-leaf

Context

[Tree] (configure>service>vprn>mvpn>provider-tunnel>inclusive>p2mp-sr enable-bfd-leaf)

Full Context

configure service vprn mvpn provider-tunnel inclusive p2mp-sr enable-bfd-leaf

Description

This command enables unidirectional multipoint BFD sessions on a receiver (leaf) PE node for upstream fast failure detection over P2MP SR tree LSP.

The no form of this command disables unidirectional multipoint BFD sessions.

Default

no enable-bfd-leaf

Platforms

All

enable-bfd-root

enable-bfd-root

Syntax

enable-bfd-root transmit-interval [multiplier multiplier]

no enable-bfd-root

Context

[Tree] (config>service>vprn>mvpn>pt>inclusive>rsvp enable-bfd-root)

Full Context

configure service vprn mvpn provider-tunnel inclusive rsvp enable-bfd-root

Description

This command enables unidirectional multi-point BFD session on a sender (Root) PE node for upstream fast failure detection over RSVP-TE P2MP LSP.

Parameters

transmit-interval

Sets the transmit interval, in milliseconds.

Values

10 to 100000

Default

100

multiplier

Sets the multiplier for the BFD session.

Values

3 to 20

Default

3

Platforms

All

enable-bfd-root

Syntax

enable-bfd-root transmit-interval [multiplier multiplier]

no enable-bfd-root

Context

[Tree] (configure>service>vprn>mvpn>pt>inclusive>p2mp-sr enable-bfd-root)

Full Context

configure service vprn mvpn provider-tunnel inclusive p2mp-sr enable-bfd-root

Description

This command enables a unidirectional multi-point BFD session on a sender (Root) PE node for upstream fast failure detection over P2MP SR tree LSP. The node uses the multiplier and the transmit interval parameters to calculate the detection time, which is the period of time without receiving BFD packets after which the session failure is determined.

Default

no enable-bfd-root

Parameters

transmit-interval

Sets the transmit interval, in milliseconds.

Values

10 to 100000

Default

300

multiplier

Sets the multiplier for the transmit interval of the BFD session.

Values

3 to 20

Default

3

Platforms

All

enable-bgp-vpn-backup

enable-bgp-vpn-backup

Syntax

enable-bgp-vpn-backup [ipv4] [ ipv6]

no enable-bgp-vpn-backup

Context

[Tree] (config>service>vprn enable-bgp-vpn-backup)

Full Context

configure service vprn enable-bgp-vpn-backup

Description

This command allows BGP-VPN routes imported into the VPRN to be used as backup paths for IPv4 or IPv6 BGP-learned prefixes.

Parameters

ipv4

Allows BGP-VPN routes to be used as backup paths for IPv4 prefixes.

ipv6

Allows BGP-VPN routes to be used as backup paths for IPv6 prefixes.

Platforms

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

enable-console-access

enable-console-access

Syntax

[no] enable-console-access

Context

[Tree] (config>system>satellite>eth-sat enable-console-access)

Full Context

configure system satellite eth-sat enable-console-access

Description

This command enables access to a satellite console interface for additional debugging purposes.

When configured through the 7750 SR, 7450 ESS, and 7950 XRS host CLI, the 7210 SAS console port is enabled to perform the debug function. Console commands are limited to specific show commands and no configuration or operational changes can be made using the 7210 console.

The no form of this command disables satellite console interface access.

Default

no enable-console-access

Platforms

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

enable-dscp-prec-remarking

enable-dscp-prec-remarking

Syntax

[no] enable-dscp-prec-remarking

Context

[Tree] (config>qos>sap-egress>policer enable-dscp-prec-remarking)

Full Context

configure qos sap-egress policer enable-dscp-prec-remarking

Description

This command enables DSCP/precedence remarking based on the profile state of a packet being forwarded by a SAP or subscriber egress policer. The DSCP/precedence can be remarked to a value independent of, or separately based on, the packet's profile, if the packet has an exceed, in-profile, or out-of-profile state.

Default

no enable-dscp-prec-remarking

Platforms

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

enable-dynamic-services-config

enable-dynamic-services-config

Syntax

[no] enable-dynamic-services-config

Context

[Tree] (enable-dynamic-services-config)

Full Context

enable-dynamic-services-config

Description

Note:

See also the description for the dynsvc-password command.

If the dynsvc-password is configured in the config>system>security>password context, then any user can enter a special dynamic services configuration mode by entering the enable-dynamic-services-config command.

The enable-dynamic-services-config command is not in the default profile. To give access to this command, the user must belong to the administrative profile or a new profile should be created.

Once the enable-dynamic-services-config command is entered, the user is prompted for a password. If the password matches, the user is given access to the dynamic services configuration. Access to static configuration is in this case prohibited.

To verify that a user is in the enable-dynamic-services-config mode, use the show users command. Users in the enable-dynamic-services-config mode lists the letter "D” next to the user’s CLI session.

The no form of this command disables the dynamic services configuration mode for this user.

Platforms

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

enable-exceed-pir

enable-exceed-pir

Syntax

[no] enable-exceed-pir

Context

[Tree] (config>qos>sap-egress>policer enable-exceed-pir)

Full Context

configure qos sap-egress policer enable-exceed-pir

Description

This command enables the forwarding of packets with an exceed-profile state and traffic exceeding the PIR for a SAP egress or a network egress queue group (configured in the egress queue group template) policer. This traffic is forwarded as exceed-profile instead of being dropped. This parameter is not supported when policers-hqos-manageable is configured in the SAP egress QoS policy.

Default

no enable-exceed-pir

Platforms

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

enable-exceed-pir

Syntax

[no] enable-exceed-pir

Context

[Tree] (cfg>qos>qgrps>egr>qgrp>policer enable-exceed-pir)

Full Context

configure qos queue-group-templates egress queue-group policer enable-exceed-pir

Description

This command enables the forwarding of traffic exceeding the PIR for a SAP egress or a network egress queue group (configured in the egress queue group template) policer. This traffic is forwarded as exceed-profile instead of being dropped.

Default

no enable-exceed-pir

Platforms

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

enable-fc-collection

enable-fc-collection

Syntax

[no] enable-fc-collection

Context

[Tree] (config>oam-pm>session>ethernet>lmm enable-fc-collection)

Full Context

configure oam-pm session ethernet lmm enable-fc-collection

Description

This command enables the ETH-LMM test within the OAM-PM session to collect per-FC counters. This command must be used in combination with the collect-lmm-fc-stats command for the entity over which the source MEP is defined. The config>oam-pm>session>ethernet>priority value must match the numerical value that represents the FC name (7 = NC, 6 = H1, 5 = EF, 4 = H2, 3 = L1, 2 = AF, 1 = L2, 0 = BE).

The OAM-PM infrastructure does not validate that the proper counting mode has been configured on the entity that is linked to the source MEP, and does not validate that the FC and priority have been configured. The show>eth-cfm>collect-lmm-fc-stats command may be used to display the entities and the FCs on those entities that have established individual FC counters.

Sessions that launch from the same source MEP must use the same counting model; either collect-lmm-fc-stats for individual counters for the defined FCs, or collect-lmm-stats for a single all-encompassing counter.

Individual OAM-PM sessions must be configured if multiple Ethernet LMM tests are required for different FCs. Cross-session validation occurs to ensure that a source MEP does not include multiple tests that are using the same priority.

The no form of this command removes all previously defined FCs and stops counting for those FCs.

Platforms

All

enable-graceful-shutdown

enable-graceful-shutdown

Syntax

[no] enable-graceful-shutdown

Context

[Tree] (config>system>login-control>telnet enable-graceful-shutdown)

Full Context

configure system login-control telnet enable-graceful-shutdown

Description

This command enables graceful shutdown of telnet sessions.

The no form of this command disables graceful shutdown of telnet sessions.

Platforms

All

enable-grt

enable-grt

Syntax

[no] enable-grt

Context

[Tree] (config>service>vprn>grt-lookup enable-grt)

Full Context

configure service vprn grt-lookup enable-grt

Description

This command enables the functions required for looking up routes in the Global Route Table (GRT) when the lookup in the local VRF fails. If this command is enabled without the use of a static-route option (as subcommand to this parent), a lookup in the local VRF is preferred over the GRT. When the local VRF returns no route table lookup matches, the result from the GRT is preferred.

The no form of this command disables the lookup in the GRT when the lookup in the local VRF fails.

Default

no enable-grt

Platforms

All

enable-icmp-vse

enable-icmp-vse

Syntax

[no] enable-icmp-vse

Context

[Tree] (config>system enable-icmp-vse)

Full Context

configure system enable-icmp-vse

Description

This command enables vendor specific extensions to ICMP.

Default

no enable-icmp-vse

Platforms

All

enable-ingress-stats

enable-ingress-stats

Syntax

[no] enable-ingress-stats

Context

[Tree] (config>service>vprn>sub-if>grp-if enable-ingress-stats)

[Tree] (config>service>ies>if enable-ingress-stats)

[Tree] (config>router>if enable-ingress-stats)

[Tree] (config>service>ies>sub-if>grp-if enable-ingress-stats)

[Tree] (config>service>vprn>if enable-ingress-stats)

[Tree] (config>service>vprn>nw-if enable-ingress-stats)

Full Context

configure service vprn subscriber-interface group-interface enable-ingress-stats

configure service ies interface enable-ingress-stats

configure router interface enable-ingress-stats

configure service ies subscriber-interface group-interface enable-ingress-stats

configure service vprn interface enable-ingress-stats

configure service vprn network-interface enable-ingress-stats

Description

This command enables the collection of ingress interface IP stats. This command is only applicable to IP statistics, and not to uRPF statistics.

If enabled, then the following statistics are collected:

  • IPv4 offered packets

  • IPv4 offered octets

  • IPv6 offered packets

  • IPv6 offered octets

Note:

Octet statistics for IPv4 and IPv6 bytes at IP interfaces include the Layer 2 frame overhead.

Default

no enable-ingress-stats

Platforms

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

  • configure service ies subscriber-interface group-interface enable-ingress-stats
  • configure service vprn subscriber-interface group-interface enable-ingress-stats

All

  • configure service vprn network-interface enable-ingress-stats
  • configure service vprn interface enable-ingress-stats
  • configure router interface enable-ingress-stats
  • configure service ies interface enable-ingress-stats

enable-inter-as-vpn

enable-inter-as-vpn

Syntax

[no] enable-inter-as-vpn

Context

[Tree] (config>router>bgp enable-inter-as-vpn)

Full Context

configure router bgp enable-inter-as-vpn

Description

This command specifies whether VPNs can exchange routes across autonomous system boundaries, providing model B connectivity.

The no form of this command disallows ASBRs to advertise VPRN routes to their peers in other autonomous systems.

Default

no enable-inter-as-vpn

Platforms

All

enable-mac-accounting

enable-mac-accounting

Syntax

[no] enable-mac-accounting

Context

[Tree] (config>service>ies>if enable-mac-accounting)

Full Context

configure service ies interface enable-mac-accounting

Description

This command enables MAC accounting functionality on this interface.

The no form of this command disables MAC accounting functionality on this interface.

Platforms

All

enable-mac-accounting

Syntax

[no] enable-mac-accounting

Context

[Tree] (config>service>vprn>if enable-mac-accounting)

Full Context

configure service vprn interface enable-mac-accounting

Description

This command enables MAC accounting functionality on this interface.

The no form of this command disables MAC accounting functionality on this interface.

Platforms

All

enable-mac-accounting

Syntax

[no] enable-mac-accounting

Context

[Tree] (config>router>if enable-mac-accounting)

Full Context

configure router interface enable-mac-accounting

Description

This command enables MAC Accounting functionality for the interface.

Default

no enable-mac-accounting

Platforms

All

enable-mdt-spt

enable-mdt-spt

Syntax

[no] enable-mdt-spt

Context

[Tree] (config>router>pim enable-mdt-spt)

Full Context

configure router pim enable-mdt-spt

Description

This command enables SPT switchover for default MDT. On enable, PIM instance resets all MDTs and re-initiate setup.

The no form of this command disables SPT switchover for default MDT. On disable, PIM instance resets all MDTs and re-initiate setup.

Default

no enable-mdt-spt

Platforms

All

enable-notification

enable-notification

Syntax

enable-notification

no enable-notification

Context

[Tree] (config>service>vprn>bgp>group>neighbor>graceful-restart enable-notification)

[Tree] (config>service>vprn>bgp>group>graceful-restart enable-notification)

[Tree] (config>service>vprn>bgp>graceful-restart enable-notification)

Full Context

configure service vprn bgp group neighbor graceful-restart enable-notification

configure service vprn bgp group graceful-restart enable-notification

configure service vprn bgp graceful-restart enable-notification

Description

When this command is present, the graceful restart capability sent by this router indicates support for NOTIFICATION messages. If the peer also supports this capability then the session can be restarted gracefully (while preserving forwarding) if either peer sends a NOTIFICATION message due to some type of event or error.

Default

no enable-notification

Platforms

All

enable-notification

Syntax

enable-notification

no enable-notification

Context

[Tree] (config>router>bgp>graceful-restart enable-notification)

[Tree] (config>router>bgp>group>neighbor>graceful-restart enable-notification)

[Tree] (config>router>bgp>group>graceful-restart enable-notification)

Full Context

configure router bgp graceful-restart enable-notification

configure router bgp group neighbor graceful-restart enable-notification

configure router bgp group graceful-restart enable-notification

Description

When this command is present, the graceful restart capability sent by this router indicates support for NOTIFICATION messages. If the peer also supports this capability, then the session can be restarted gracefully (while preserving forwarding) if either peer needs to send a NOTIFICATION message due to some type of event or error.

Default

no enable-notification

Platforms

All

enable-origin-validation

enable-origin-validation

Syntax

enable-origin-validation [ipv4] [ipv6] [ label-ipv4]

no enable-origin-validation

Context

[Tree] (config>service>vprn>bgp>group enable-origin-validation)

[Tree] (config>service>vprn>bgp>group>neighbor enable-origin-validation)

Full Context

configure service vprn bgp group enable-origin-validation

configure service vprn bgp group neighbor enable-origin-validation

Description

When this command is added to the configuration of a group or neighbor, it causes every inbound IPv4, IPv6, and label-IPv4 route from that peer to be marked with one of the following origin validation states:

  • Valid (0)

  • Not-Found (1)

  • Invalid (2)

By default (when no family parameter is present in the command) or when all the family options are specified, all unicast IPv4 (AFI1/SAFI1), label-IPv4 (AFI1/SAFI4), and unicast IPv6 (AFI2/SAFI1) routes are evaluated to determine their origin validation states. When only a subset of the family options are present, then only the corresponding address family routes are evaluated.

This command applies to all types of VPRN BGP peers, generally, it should only be applied to EBGP peers and groups that contain only EBGP peers.

The no form of this command disables the inspection of received routes from the peer to determine origin validation state.

Default

no enable-origin-validation

Parameters

ipv4

Enables origin validation processing for unlabeled unicast IPv4 routes.

ipv6

Enables origin validation processing for unlabeled unicast IPv6 routes.

label-ipv4

Enables origin validation processing for labeled IPv4 routes.

Platforms

All

enable-origin-validation

Syntax

enable-origin-validation [ipv4] [ipv6] [ label-ipv4] [label-ipv6]

no enable-origin-validation

Context

[Tree] (config>router>bgp>group>neighbor enable-origin-validation)

[Tree] (config>router>bgp>group enable-origin-validation)

Full Context

configure router bgp group neighbor enable-origin-validation

configure router bgp group enable-origin-validation

Description

When the enable-origin-validation command is added to the configuration of a group or neighbor, it causes every inbound IPv4 or IPv6 route from that peer to be marked with one of the following origin validation states:

  • Valid (0)

  • Not-Found (1)

  • Invalid (2)

By default (when neither the ipv4 or ipv6 option is present in the command) or when both the ipv4 and ipv6 options are specified, all unicast IPv4 (AFI1/SAFI1), label-IPv4 (AFI1/SAFI4), unicast IPv6 (AFI2/SAFI1), and label-IPv6 (AFI2/SAFI4) routes are evaluated to determine their origin validation states. When only the ipv4 or ipv6 option is present, only the corresponding address family routes (unlabeled and labeled) are evaluated.

The enable-origin-validation command applies to all types of BGP peers, but as a general rule, it should only be applied to EBGP peers and groups that contain only EBGP peers.

Default

no enable-origin-validation

Parameters

ipv4

Enables origin validation processing for unlabeled unicast IPv4 routes.

ipv6

Enables origin validation processing for unlabeled unicast IPv6 routes.

label-ipv4

Enables origin validation processing for labeled IPv4 routes.

label-ipv6

Enables origin validation processing for labeled IPv6 routes.

Platforms

All

enable-peer-tracking

enable-peer-tracking

Syntax

[no] enable-peer-tracking

Context

[Tree] (config>service>vprn>bgp enable-peer-tracking)

[Tree] (config>service>vprn>bgp>group enable-peer-tracking)

[Tree] (config>service>vprn>bgp>group>neighbor enable-peer-tracking)

Full Context

configure service vprn bgp enable-peer-tracking

configure service vprn bgp group enable-peer-tracking

configure service vprn bgp group neighbor enable-peer-tracking

Description

This command enables BGP peer tracking.

Default

no enable-peer-tracking

Platforms

All

enable-peer-tracking

Syntax

[no] enable-peer-tracking

Context

[Tree] (config>router>bgp>group enable-peer-tracking)

[Tree] (config>router>bgp enable-peer-tracking)

[Tree] (config>router>bgp>group>neighbor enable-peer-tracking)

Full Context

configure router bgp group enable-peer-tracking

configure router bgp enable-peer-tracking

configure router bgp group neighbor enable-peer-tracking

Description

This command enables BGP peer tracking. BGP peer tracking allows a BGP peer to be dropped immediately if the route used to resolve the BGP peer address is removed from the IP routing table and there is no alternative available. The BGP peer will not wait for the holdtimer to expire; therefore, the BGP re-convergence process is accelerated.

The no form of this command disables peer tracking.

Default

no enable-peer-tracking

Platforms

All

enable-rr-vpn-forwarding

enable-rr-vpn-forwarding

Syntax

[no] enable-rr-vpn-forwarding

Context

[Tree] (config>router>bgp enable-rr-vpn-forwarding)

Full Context

configure router bgp enable-rr-vpn-forwarding

Description

When this command is configured all received VPN-IP routes, regardless of route target, are imported into the dummy VRF, where the BGP next-hops are resolved. The label-route-transport-tunnel under config>router>bgp>next-hop-resolution determines what types of tunnels are eligible to resolve the next-hops. If a received VPN-IP route from IBGP peer X is resolved and selected as best so that it can be re-advertised to an IBGP peer Y, and the BGP next-hop is modified towards peer Y (by using the next-hop-self command in Y’s group or neighbor context or by using a next-hop action in an export policy applied to Y) then BGP allocates a new VPRN service label value for the route, signals that new label value to Y and programs the IOM to do the corresponding label swap operation. The supported combinations of X and Y are outlined below:

  • from X (client) to Y (client)

  • from X (client) to Y (non-client)

  • from X (non-client) to Y (client)

The no form of this command causes the re-advertisement of a VPN-IP route between one IBGP peer and another IBGP peer does not cause a new VPRN service label value to be signaled and programmed even if the BGP next-hop is changed through group/neighbor configuration or policy.

Nokia recommends leaving this command disabled for scaling and convergence reasons.

Default

no enable-rr-vpn-forwarding

Platforms

All

enable-subconfed-vpn-forwarding

enable-subconfed-vpn-forwarding

Syntax

[no] enable-subconfed-vpn-forwarding

Context

[Tree] (config>router>bgp enable-subconfed-vpn-forwarding)

Full Context

configure router bgp enable-subconfed-vpn-forwarding

Description

This command configures BGP to keep VPN-IPv4 and VPN-IPv6 routes within a subconfederation and allow a next-hop-self command to create label swap forwarding entries.

When this is enabled, the base router BGP instance retains all received VPN-IPv4 and VPN-IPv6 routes, even those with route targets not matching any VRF import policy of any locally configured VPRN. In addition, when this leaf is enabled and base router BGP is configured to apply a next-hop-self command to a peer of any type (EBGP, IBGP, or confed-EBGP), the VPN-IPv4 and VPN-IPv6 routes are advertised to the peer with a new BGP label and next-hop, and a label-swap forwarding entry is programmed.The preceding behaviors are applied when the enable-inter-as-vpn or the enable-rr-vpn-forwarding commands, both under the configure router bgp context, are also enabled in the same BGP instance and regardless of whether the base router has a confederation configuration.

The no form of this command disables subconfederation VPN forwarding.

Default

no enable-subconfed-vpn-forwarding

Platforms

All

enable-tech

enable-tech

Syntax

[no] enable-tech

Context

[Tree] (admin enable-tech)

Full Context

admin enable-tech

Description

This command enables the shell and kernel commands.

Note:

This command should only be used with authorized direction of Nokia support.

Platforms

All

enable-triggered-hosts

enable-triggered-hosts

Syntax

[no] enable-triggered-hosts

Context

[Tree] (config>service>ies>sub-if>grp-if>wpp enable-triggered-hosts)

[Tree] (config>service>vprn>sub-if>grp-if>wpp enable-triggered-hosts)

Full Context

configure service ies subscriber-interface group-interface wpp enable-triggered-hosts

configure service vprn subscriber-interface group-interface wpp enable-triggered-hosts

Description

This command enables system to auto creates ESM hosts upon successful WPP authentication. The default host must be configured under SAP on the subscriber SAP to redirect unauthenticated client traffic to the web portal.

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

encap

encap

Syntax

encap

Context

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

Full Context

configure mirror mirror-dest encap

Description

Commands in this context configure encapsulation options for the mirrored traffic. Note that the use of encap is mutually exclusive with SAP or spoke SDP options in the same mirror destination. Only one type of encapsulation can be specified for a single mirror destination. Slicing and encap are mutually exclusive in the same mirror-dest context.

Platforms

All

encap-defined-qos

encap-defined-qos

Syntax

encap-defined-qos

Context

[Tree] (config>service>vpls>sap>egress encap-defined-qos)

Full Context

configure service vpls sap egress encap-defined-qos

Description

This command creates a new QoS sub-context in B-VPLS SAP egress context. The user can define encapsulation groups, referred to as encap-group, based on the ISID value in the packet’s encapsulation and assign a QoS policy and a scheduler policy or aggregate rate limit to the group.

Platforms

All

encap-group

encap-group

Syntax

encap-group group-name [type group-type] [qos-per-member] [create]

no encap-group group-name

Context

[Tree] (config>service>vpls>sap>egress>encap-defined-qos encap-group)

Full Context

configure service vpls sap egress encap-defined-qos encap-group

Description

This command defines an encapsulation group which consists of a group of ISID values. All packets forwarded on the egress of a B-VPLS SAP which payload header matches one of the ISID value in the encap-group will use the same QoS policy instance and scheduler policy or aggregate rate limit instance.

The user adds or removes members to the encap-group one at a time or as a range of contiguous values using the member command. However, when the qos-per-member option is enabled, members must be added or removed one at a time. These members are also referred to as ISID contexts.

The user can configure one or more encap-groups in the egress context of the same B-SAP, therefore defining different ISID values and applying each a different SAP egress QoS policy, and optionally a different scheduler policy/agg-rate. ISID values are unique within the context of a B-SAP. The same ISID value cannot be re-used in another encap-group under the same B-SAP but can be re-used in an encap-group under a different B-SAP. Finally, if the user adds to an encap-group an ISID value which is already a member of this encap-group, the command causes no effect. The same if the user attempts to remove an ISID value which is not a member of this encap-group.

Once a group is created, the user will assign a SAP egress QoS policy, and optionally a scheduler policy or aggregate rate limit, using the following commands:

config>service>vpls>sap>egress>encap-defined-qos>encap-group>qos sap-egress-policy-id

config>service>vpls>sap>egress>encap-defined-qos>encap-group>scheduler-policy scheduler-policy-name

config>service>vpls>sap>egress>encap-defined-qos>encap-group>agg-rate kilobits-per-second

A SAP egress QoS policy must first be assigned to the created encap group before the user can add members to this group. Conversely, the user cannot perform the no qos command until all members are deleted from the encap-group.

An explicit or the default SAP egress QoS policy continues to be applied to the entire B-SAP but this will serve to create the set of egress queues which are used to store and forward a packet which does not match any of the defined ISID values in any of the encap-groups for this SAP.

Only the queue definition and fc-to-queue mapping from the encap-group SAP egress QoS policy is applied to the ISID members. All other parameters configurable in a SAP egress QoS policy must be inherited from egress QoS policy applied to the B-SAP.

Furthermore, any other CLI option configured in the egress context of the B-SAP continues to apply to packets matching a member of any encap-group defined in this B-SAP.

The keyword qos-per-member allows the user to specify that a separate queue set instance and scheduler/agg-rate instance will be created for each ISID value in the encap-group. By default, shared instances will be created for the entire encap-group.

When the B-SAP is configured on a LAG port, the ISID queue instances defined by all the encap-groups applied to the egress context of the SAP will be replicated on each member link of the LAG. The set of scheduler/agg-rate instances will be replicated per link or per IOM or XMA depending if the adapt-qos option is set to link/port-fair mode or distribute mode. This is the same behavior as that applied to the entire B-SAP in the current implementation.

The no form of this command deletes the encap-group.

Parameters

group-name

Specifies the name of the encap-group and can be up to 32 ASCII characters in length

type

Specifies the type of the encapsulation ID used by this encap-group

Values

isid

qos-per-member

Specifies that a separate queue set instance and scheduler/agg-rate instance will be created for each ISID value in the encap-group

Platforms

All

encap-match

encap-match

Syntax

encap-match {all-encap | double-tag encap-value | single-tag encap-value | untagged}

no encap-match

Context

[Tree] (config>port>ethernet>dot1x>macsec>sub-port encap-match)

Full Context

configure port ethernet dot1x macsec sub-port encap-match

Description

This command defines the sub-set of traffic on this port affected by this MACsec sub-port.

In order to establish an end-to-end communication between the remote MACsec peers encrypting VLAN-tagged traffic, the MKA packets have to be able to travel over the network following the same path as the encrypted traffic. MKA packets are generated with specific tags depending on the traffic match criteria configured, as shown in MKA Packet Generation .

The no form of this command removes all traffic sub-set definitions from the MACsec sub-port.

Table 1. MKA Packet Generation

Configuration

Config Example (<s-tag>.<c-tag>)

MKA Packet Generation

Traffic pattern match/behavior

PORT all-encap

Config>port>ethernet>dot1x>macsec

Sub-port 10

encap-match all-encap

ca-name 10

untagged MKA packet

Matches all traffic on the port, including untagged, single-tag, double-tag.

This is the Release 15.0 default behavior.

Untagged

Config>port>ethernet>dot1x>macsec

Sub-port 1

encap-match untagged

ca-name 2

untagged MKA packet

Matches only untagged traffic on the port

802.1Q single S-TAG (specific S-TAG)

Config>port>ethernet>dot1x>macsec

Sub-port 2

encap-match dot1q 1

ca-name 3

MKA packet generated with S-TAG=1

Matches only single-tag traffic on port with tag ID of 1

802.1Q single S-TAG (any S-TAG)

Config>port>ethernet>dot1x>macsec

Sub-port 3

encap-match dot1q *

ca-name 4

untagged MKA packet

Matches any single-tag traffic on port

802.1ad double tag (both tag have specific TAGs)

Config>port>ethernet>dot1x>macsec

Sub-port 4

encap-match qinq 1.1

ca-name 5

MKA packet generated with S-tag=1 and C-TAG=1

Matches only double-tag traffic on port with service tag of 1 and customer tag of 1

802.1ad double tag (specific S-TAG, any C-TAG)

Config>port>ethernet>dot1x>macsec

Sub-port 6

encap-match qinq 1.*

ca-name 7

MKA packet generated with S-TAG=1

Matches only double-tag traffic on port with service tag of 1 and customer tag of any

802.1ad double tag (any S-TAG, any C-TAG

Config>port>ethernet>dot1x>macsec

Sub-port 7

encap-match double-tag *.*

ca-name 8

untagged MKA packet

Matches any double-tag traffic on port

Default

encap-match all-encap

Parameters

all-encap

Specifies that all traffic patterns are matched including untagged, single-tag or double-tag, and all will be encrypted.

untagged

Specifies that only untagged traffic are matched and encrypted.

single-tag

Specifies that only dot1q traffic are matched. Either all single tag traffic can be matched, by using *, or a specific dot1q tag can be matched.

double-tag

Specifies that only qinq traffic are matched. The service tag can be specifically matched or a wild card match (*.*) can be used.

encap-value

Specifies the type and value of the packet encapsulation to match for this MACsec sub-port.

Type

Parameter

all-encap

untagged

dot1q

[*| s] (s = 0..4094)

qinq

[*.*| s.*| s.c] (s and c = 0..4094)

where:

  • S = service tag

  • C = customer tag

Platforms

All

encap-offset

encap-offset

Syntax

encap-offset [type type]

no encap-offset

Context

[Tree] (config>subscr-mgmt>sub-profile>egress encap-offset)

Full Context

configure subscriber-mgmt sub-profile egress encap-offset

Description

This command enables the adjustment of the queue and subscriber aggregate rate based on the last mile Ethernet or ATM encapsulation.

The data path computes the adjusted frame size real-time for each serviced packet from a queue by adding the actual packet size to the fixed offset provided by CPM for this queue and variable AAL5 padding.

When this command is enabled, the fixed packet offset is derived from the encapsulation type value signaled in the Access-loop-encapsulation sub-TLV in the Vendor-Specific PPPoE Tags or DHCP Relay Options as per RFC 4679. If the user specifies an encapsulation type with the command, this value is used as the default value for all hosts of this subscriber until a host session signaled a valid value. The signaled value is applied to this host only and the remaining hosts of this subscriber continue to use the user entered default type value if configured, or no offset is applied. However, hosts of the same subscriber using the same SLA profile and which are on the same SAP will share the same instance of FC queues. In this case, the last valid encapsulation value signaled by a host of that same instance of the SAP egress QoS policy will override any previous signaled or configured value.

If the user manually applied a constant byte offset to each packet serviced by the queue by configuring the packet-byte-offset, it will have no effect on the net offset computed for the packet. This net offset is stored in the subscriber host table.

The procedures for handling signaling changes or configuration changes affecting the subscriber profile are as follows:

The avg-frame-size parameter in the subscriber profile is ignored.

If the user specifies an encapsulation type with the command, this value is used as the default value for all hosts of this subscriber until a host session signaled a valid value. The signaled value is applied to this host and other hosts of the same subscriber sharing the same SLA profile and which are on the same SAP. The remaining hosts of this subscriber continue to use the user entered default type value if configured, or no offset is applied.

If the user enables/disables the encap-offset option, or changes the parameter value of the encap-offset option, CPM immediately triggers a re-evaluation of subscribers hosts using the corresponding subscriber profile and an update the IOM with the new fixed offset value.

If a subscriber has a static host or an ARP host, the subscriber host continues to use the user-configured default encapsulation type value or the last valid encapsulation value signaled in the PPPoE tags or DHCP relay options by other hosts of the same subscriber which use the same SLA profile instance. If none was signaled or configured, then no rate adjustment is applied.

When the encap-offset option is configured in the subscriber profile, the subscriber host queue rates, that is, CLI and operational PIR and CIR as well as queue bucket updates, the queue statistics, that is, forwarded, dropped, and HQoS offered counters use the last-mile frame-over-the-wire format. The scheduler policy CLI and operational rates also use LM-FoW format. The port scheduler max-rate and the priority level rates and weights, if a Weighted Scheduler Group is used, are always entered in CLI and interpreted as local port frame-over-the-wire rates. The same is true for an agg-rate-limit applied to a Vport. Finally the subscriber agg-rate-limit is entered in CLI as last-mile frame-over-the-wire rate. The system maintains a running average frame expansion ratio for each queue to convert queue rates between these two formats.

The no form of this command reverts to the default.

Parameters

type

The name of the default encapsulation used for all host queues of a subscriber in the absence of a valid value signaled in the PPPoE tags.

Values

pppoa-llc, pppoa-null, pppoeoa-llc, pppoeoa-llc-fcs, pppoeoa-llc-tagged, pppoeoa-llc-tagged-fcs, pppoeoa-null, pppoeoa-null-fcs, pppoeoa-null-tagged, pppoeoa-null-tagged-fcs, ipoa-llc, ipoa-null, ipoeoa-llc, ipoeoa-llc-fcs, ipoeoa-llc-tagged, ipoeoa-llc-tagged-fcs, ipoeoa-null, ipoeoa-null-fcs, ipoeoa-null-tagged, ipoeoa-null-tagged-fcs, pppoe, pppoe-tagged, ipoe, ipoe-tagged

Platforms

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

encap-offset

Syntax

encap-offset [type encap-type]

no encap-offset

Context

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>access-loop-encapsulation encap-offset)

Full Context

configure subscriber-mgmt local-user-db ppp host access-loop-encapsulation encap-offset

Description

This command is applicable within the LAC/LNS context. It provides the last mile link encapsulation information that is needed for proper (shaping) rate calculations and interleaving delay in the last mile.

The encapsulation value will be taken from the following sources in the order of priority:

  • Statically provisioned value in local user database (LUDB).

  • RADIUS

  • PPPoE tags on LAC or ICRQ message (RFC 5515) on LNS

In case that the encapsulation information is not provided by any of the existing means (LUDB, RADIUS, AVP signaling, PPPoE Tags), then by default pppoea-null encapsulation will be in effect.

The following values are supported encapsulation values on LNS in the 7750 SR.

encap-type:

pppoa-llc

LLC (NLPID) PPPoA encapsulation.

pppoa-null

VC-MUX PPPoA encapsulation.

pppoeoa-llc

LLC/SNAP based bridged Ethernet PPPoEoA encapsulation without FCS.

pppoeoa-llc-fcs

LLC/SNAP based bridged Ethernet PPPoEoA encapsulation with FCS.

pppoeoa-null

VC-MUX PPPoEoA encapsulation without FCS.

pppoeoa-null-fcs

VC-MUX PPPoEoA encapsulation with FCS.

pppoe

PPPoE encapsulation.

pppoe-tagged

Tagged PPPoE Encapsulation.

The values are not supported encapsulation values on LNS in the 7750 SR.

pppoeoa-llc-tagged

pppoeoa-llc-tagged-fcs

pppoeoa-null-tagged

pppoeoa-null-tagged-fcs

ipoa-llc

ipoa-null

ipoeeoa-llc

ipoeoa-llc-fcs

ipoeoa-llc-tagged

ipoeoa-llc-tagged-fcs

ipoeoa-null

ipoeoa-null-fcs

ipoeoa-null-tagged

ipoeoa-null-tagged-fcs

ipoe

ipoe-tagged

Default

no encap-offset

Platforms

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

encap-tag-range

encap-tag-range

Syntax

encap-tag-range start-tag start-tag end-tag end-tag

no encap-tag-range

Context

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>host-ident encap-tag-range)

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>host-ident encap-tag-range)

Full Context

configure subscriber-mgmt local-user-db ipoe host host-identification encap-tag-range

configure subscriber-mgmt local-user-db ppp host host-identification encap-tag-range

Description

This command specifies a range of encapsulation tags as the host identifications. The encapsulation tag is dot1q or qinq on Ethernet port.

For dot1q, the start/end-tag is single number, range from 0-4094; for QinQ, the start/end-tag format is x.y, x or y could be "*”, which means ignore inner or outer tag.

Note:

This command is only used when encap-tag-range is configured as one of the match-list parameters.

The no form of this command removes the encapsulation tag range from the configuration.

Parameters

start-tag start-tag

Specifies the value of the start label in the range of SAPs allowed on this host.

Values

start-tag

dot1q

qtag1

qinq

(qtag1.qtag2 | qtag1.* | *.qtag2)

end-tag end-tag

Specifies the value of the end label in the range of SAPs allowed on this host.

Values

end-tag

dot1q

qtag1

qinq

(qtag1.qtag2 | qtag1.* | *.qtag2)

Platforms

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

encap-tag-separate-range

encap-tag-separate-range

Syntax

encap-tag-separate-range outer outer-encap-range inner inner-encap-range

no encap-tag-separate-range

Context

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>host-ident encap-tag-separate-range)

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>host-ident encap-tag-separate-range)

Full Context

configure subscriber-mgmt local-user-db ppp host host-identification encap-tag-separate-range

configure subscriber-mgmt local-user-db ipoe host host-identification encap-tag-separate-range

Description

This command specifies a range of encapsulation tags as the host identifications.

Note:

This command is only used when encap-tag-separate-range is configured as one of the match-list parameters.

The no form of this command removes the range of encapsulation tags from the configuration.

Default

no encap-tag-separate-range

Parameters

outer-encap-range

Specifies the value of the outer encapsulation tag range.

Values

start-qtag - end-qtag

start-qtag: 0 to 4094

end-qtag: 0 to 4094

inner-encap-range

Specifies the value of the inner encapsulation tag range.

Values

start-qtag - end-qtag

start-qtag: 0 to 4094

end-qtag: 0 to 4094

Platforms

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

encap-type

encap-type

Syntax

encap-type {default | null | dot1q | qinq}

no encap-type

Context

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

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

Full Context

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

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

Description

If different from default, this command overrides the value specified by l2-ap-encap-type on wlan-gw level. See the description of l2-ap-encap-type for more detail. This value can only be changed while the l2-ap is shut down.

The no form of this command sets the default value.

Default

encap-type default

Parameters

default

Specifies to use the value specified by l2-ap-encap-type.

null

Specifies to use both the SAP and the AP are not VLAN-tagged.

dot1q

Specifies to use 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

encap-type

Syntax

encap-type {dot1q | null | qinq}

no encap-type

Context

[Tree] (config>port>ethernet encap-type)

Full Context

configure port ethernet encap-type

Description

This command configures the encapsulation method used to distinguish customer traffic on an Ethernet access port, or different VLANs on a network port.

The no form of this command restores the default.

Default

encap-type null

Parameters

dot1q

Ingress frames carry 802.1Q tags where each tag signifies a different service.

null

Ingress frames will not use any tags to delineate a service. As a result, only one service can be configured on a port with a null encapsulation type.

qinq

Specifies QinQ encapsulation.

Platforms

All

encap-type

Syntax

encap-type {cem}

Context

[Tree] (config>port>tdm>e1>channel-group encap-type)

[Tree] (config>port>tdm>ds3 encap-type)

[Tree] (config>port>tdm>e3 encap-type)

[Tree] (config>port>tdm>ds1>channel-group encap-type)

Full Context

configure port tdm e1 channel-group encap-type

configure port tdm ds3 encap-type

configure port tdm e3 encap-type

configure port tdm ds1 channel-group encap-type

Description

This command configures the encapsulation method used to on the specified port, path, or channel. This parameter can be set on both access and network ports.

The no form of this command restores the default.

Default

encap-type bcp-null

Parameters

cem

Specifies that on circuit emulation MDAs, only the cem encap-type is supported. All other values are blocked with an appropriate warning. The cem encap-type is not supported on other MDAs and are blocked with an appropriate warning.

Platforms

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

encap-type

Syntax

encap-type {dot1q | null | qinq}

no encap-type

Context

[Tree] (config>lag encap-type)

Full Context

configure lag encap-type

Description

This command configures the encapsulation method used to distinguish customer traffic on a LAG. The encapsulation type is configurable on a LAG port. The LAG port and the port member encapsulation types must match when adding a port member.

If the encapsulation type of the LAG port is changed, the encapsulation type on all the port members will also change. The encapsulation type can be changed on the LAG port only if there is no interface associated with it. If the MTU is set to a non-default value, it will be reset to the default value when the encap type is changed.

The no form of this command restores the default.

Default

encap-type null — All traffic on the port belongs to a single service or VLAN.

Parameters

dot1q

Ingress frames carry 802.1Q tags where each tag signifies a different service.

null

Ingress frames will not use any tags to delineate a service. As a result, only one service can be configured on a port with a null encapsulation type.

qinq

Specifies QinQ encapsulation.

Platforms

All

encap-type

Syntax

encap-type {dot1q| qinq}

no encap-type

Context

[Tree] (config>eth-tunnel>ethernet encap-type)

Full Context

configure eth-tunnel ethernet encap-type

Description

This command configures the encapsulation method used to distinguish customer traffic on a LAG. The encapsulation type is configurable on a LAG port. The LAG port and the port member encapsulation types must match when adding a port member.

If the encapsulation type of the LAG port is changed, the encapsulation type on all the port members will also change. The encapsulation type can be changed on the LAG port only if there is no interface associated with it. If the MTU is set to a non-default value, it will be reset to the default value when the encap type is changed.

The no form of this command reverts to the default.

Default

encap-type dot1q

Parameters

dot1q

Specifies that frames carry 802.1Q tags where each tag signifies a different service.

qinq

Specifies the qinq encapsulation method.

Platforms

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

encap-type

Syntax

encap-type {dot1q | qinq}

no encap-type

Context

[Tree] (config>pw-port encap-type)

Full Context

configure pw-port encap-type

Description

This command configures the encapsulation type on a PW port. Customer Ethernet frames can be single-tagged or double-tagged, and this command determines the number of tags that the SR OS will check (and strip) on PW-SAP ingress and insert on PW-SAP egress.

The no form of this command removes the configuration.

Parameters

dot1q

Specifies that the encapsulation type is dot1q; used when the customer's Ethernet frame is single-tagged.

qinq

Specifies that the encapsulation type is qinq; used when the customer's Ethernet frame is double-tagged.

Default

dot1q

Platforms

All

encapsulated-ip-mtu

encapsulated-ip-mtu

Syntax

encapsulated-ip-mtu bytes

no encapsulated-ip-mtu

Context

[Tree] (config>ipsec>tnl-temp encapsulated-ip-mtu)

[Tree] (config>router>if>ipsec>ipsec-tunnel encapsulated-ip-mtu)

[Tree] (config>service>ies>if>ipsec>ipsec-tunnel encapsulated-ip-mtu)

[Tree] (config>service>ies>if>sap>ip-tunnel encapsulated-ip-mtu)

[Tree] (config>service>vprn>if>sap>ip-tunnel encapsulated-ip-mtu)

[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel encapsulated-ip-mtu)

[Tree] (config>service>vprn>if>sap>ipsec-tun encapsulated-ip-mtu)

Full Context

configure ipsec tunnel-template encapsulated-ip-mtu

configure router interface ipsec ipsec-tunnel encapsulated-ip-mtu

configure service ies interface ipsec ipsec-tunnel encapsulated-ip-mtu

configure service ies interface sap ip-tunnel encapsulated-ip-mtu

configure service vprn interface sap ip-tunnel encapsulated-ip-mtu

configure service vprn interface ipsec ipsec-tunnel encapsulated-ip-mtu

configure service vprn interface sap ipsec-tunnel encapsulated-ip-mtu

Description

This command specifies the maximum size of encapsulated tunnel packet for the ipsec-tunnel, ip-tunnel, or the dynamic tunnels terminated on the ipsec-gw. If the encapsulated IPv4 or IPv6 tunnel packet exceeds the encapsulated-ip-mtu, then the system fragments the packet against the encapsulated-ip-mtu.

The no form of this command reverts to the default.

Default

no encapsulated-ip-mtu

Parameters

bytes

Specifies the maximum size in bytes.

Values

512 to 9000

Platforms

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

  • configure ipsec tunnel-template encapsulated-ip-mtu
  • configure service ies interface sap ip-tunnel encapsulated-ip-mtu
  • configure service vprn interface sap ip-tunnel encapsulated-ip-mtu
  • configure service vprn interface sap ipsec-tunnel encapsulated-ip-mtu

VSR

  • configure service vprn interface ipsec ipsec-tunnel encapsulated-ip-mtu
  • configure service ies interface ipsec ipsec-tunnel encapsulated-ip-mtu
  • configure router interface ipsec ipsec-tunnel encapsulated-ip-mtu

encapsulated-ip-mtu

Syntax

encapsulated-ip-mtu octets

no encapsulated-ip-mtu

Context

[Tree] (config>service>vprn>sap>ip-tunnel encapsulated-ip-mtu)

Full Context

configure service vprn sap ip-tunnel encapsulated-ip-mtu

Description

This command configures the tunnel encapsulated IP MTU.

The no form of this command reverts to the default.

Parameters

octets

Specifies the tunnel encapsulated IP MTU in octets.

encode

encode

Syntax

encode type type key key

encode type type key hash-key hash

encode type type key hash2-key hash2

encode type type key custom-key custom

encode type type cert-profile cert-profile-name

no encode

Context

[Tree] (config>app-assure>group>http-enrich>field encode)

Full Context

configure application-assurance group http-enrich field encode

Description

This command configures the encoding applied to the HTTP header enrichment field.

The no form of this command removes the encoding.

Default

no encode

Parameters

type

Specifies whether the parameters are hashed with MD5, encrypted with RC4 or AES using the configured key, or if certificate-based encryption is used with RSA.

Values

md5, rc4, certificate, cert-base64, rc4md5-base64, aes128, aes256, aes128cbc, aes256cbc

key

Specifies the key string, 64 characters maximum.

hash-key

Specifies the first hashed key.

hash-key2

Specifies the second hashed key.

hash

Specifies that the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.

hash2

Specifies that the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.

custom

Specifies the custom encryption to management interface.

cert-profile-name

Specifies the name of the certificate profile to use. This profile must have already been created using the certificate-profile command.

Platforms

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

encoding

encoding

Syntax

encoding encoding

no encoding

Context

[Tree] (config>system>telemetry>persistent-subscriptions>subscription encoding)

Full Context

configure system telemetry persistent-subscriptions subscription encoding

Description

This command configures the encoding type that is used for telemetry notifications in accordance with the definitions in the gNMI OpenConfig standard.

Default

encoding json

Parameters

encoding

Specifies the encoding type.

Values

json, bytes, proto

Platforms

All

encrypt

encrypt

Syntax

encrypt {on | off}

Context

[Tree] (bof encrypt)

Full Context

bof encrypt

Description

This command enables and disables encryption of the BOF using AES256 and SHA256.

When the BOF is encrypted on the compact flash, it is still reachable using the BOF interactive menu during node startup, and fields can be modified using the BOF interactive menu.

Default

encrypt off

Parameters

on

Enables BOF encryption

off

Disables BOF encryption

Platforms

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

encryption-key

encryption-key

Syntax

encryption-key key [hash | hash2 | custom]

no encryption-key

Context

[Tree] (bof encryption-key)

Full Context

bof encryption-key

Description

This command creates a key to be used by AES256 and SHA256 for configuration file encryption and hashing. This key is used for all configuration files (primary, secondary, and tertiary).

After creating or deleting a key, use the admin save command to save the configuration file with the current encryption key state.

The no form of this command deletes the encryption key.

Default

no encryption-key

Parameters

key

Specifies the encryption key.

If the hash, hash2, or custom parameter is not configured, the key is entered in plaintext and the key length must be between 8 and 32 characters. A plaintext key cannot contain embedded nulls or end with " hash”, " hash2”, or " custom”.

If the hash, hash2, or custom parameter is configured, the key is hashed and the key length must be between 1 and 64 characters.

hash

Keyword to specify that the key is entered in an encrypted form.

hash2

Keyword to specify that the key is entered in a more complex encrypted form. The hash2 encryption scheme is node-specific and the key cannot be transferred between nodes.

custom

Keyword to specify that the key uses custom encryption.

Platforms

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

encryption-key

Syntax

encryption-key key [hash | hash2 | custom]

no encryption-key

Context

[Tree] (config>log encryption-key)

Full Context

configure log encryption-key

Description

This command specifies the encryption key used by AES-256-CTR for log file encryption. The encryption key is used for all local log files on the system.

The no form of this command deletes the encryption key.

Default

no encryption-key

Parameters

key

Specifies the encryption key.

If the hash, hash2, or custom parameter is not configured, the key is entered in plaintext and the key length must be between 8 and 32 characters. A plaintext key cannot contain embedded nulls or end with " hash”, " hash2”, or " custom”.

If the hash, hash2, or custom parameter is configured, the key is hashed and the key length must be between 1 and 64 characters.

hash

Keyword to specify that the key is entered in an encrypted form.

hash2

Keyword to specify that the key is entered in a more complex encrypted form. The hash2 encryption scheme is node-specific and the key cannot be transferred between nodes.

custom

Keyword to specify that the key uses custom encryption.

Platforms

All

encryption-keygroup

encryption-keygroup

Syntax

encryption-keygroup keygroup-id direction direction

no encryption-keygroup direction direction

Context

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>group-encryption encryption-keygroup)

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>group-encryption encryption-keygroup)

Full Context

configure service ies subscriber-interface group-interface wlan-gw group-encryption encryption-keygroup

configure service vprn subscriber-interface group-interface wlan-gw group-encryption encryption-keygroup

Description

This command binds an encryption key-group to a WLAN-GW soft-GRE group interface. When configured in the inbound direction, received packets must be encrypted using one of the valid security-associations configured for the key-group. When configured in the outbound direction, L2oMPLSoGRE packets egressing the node use the "active-outbound-sa” associated with the key-group configured.

The no form of this command removes the encryption keygroup from the inbound or outbound group interface.

Parameters

keygroup-id

Specifies the ID number or name of the keygroup.

Values

1 to 127, keygroup-name up to 64 characters

direction

Applies the keygroup to the inbound or outbound direction of a service.

Values

inbound | outbound

Platforms

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

encryption-keygroup

Syntax

encryption-keygroup keygroup-id direction {inbound | outbound}

no encryption-keygroup direction {inbound | outbound}

Context

[Tree] (config>router>if>group-encryption encryption-keygroup)

Full Context

configure router interface group-encryption encryption-keygroup

Description

This command is used to bind a key group to a router interface for inbound or outbound packet processing. When configured in the outbound direction, packets egressing the router use the active-outbound-sa associated with the configured key group. When configured in the inbound direction, received packets must be encrypted using one of the valid security associations configured for the key group.

The no form of this command removes the key group from the router interface in the specified direction.

Default

no encryption-keygroup direction inbound

no encryption-keygroup direction outbound

Parameters

keygroup-id

The ID number of the key group being configured.

Values

1 to 127, keygroup-name (64 characters maximum)

inbound

Binds the key group in the inbound direction.

outbound

Binds the key group in the outbound direction.

Platforms

VSR

encryption-keygroup

Syntax

encryption-keygroup keygroup-id [create]

no encryption-keygroup keygroup-id

Context

[Tree] (config>grp-encryp encryption-keygroup)

Full Context

configure group-encryption encryption-keygroup

Description

This command is used to create a key group. Once the key group is created, use the command to enter the key group context or delete a key group.

The no form of the command removes the key group. Before using the no form, the key group association must be deleted from all services that are using this key group.

Parameters

keygroup-id

The number or name of the key group being referenced.

Values

1 to 15, or keygroup-name (up to 64 characters)

create

Creates a key group.

Platforms

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

encryption-keygroup

Syntax

encryption-keygroup keygroup-id direction {inbound | outbound}

no encryption-keygroup direction {inbound | outbound}

Context

[Tree] (config>service>sdp encryption-keygroup)

[Tree] (config>service>vprn encryption-keygroup)

[Tree] (config>service>pw-template encryption-keygroup)

Full Context

configure service sdp encryption-keygroup

configure service vprn encryption-keygroup

configure service pw-template encryption-keygroup

Description

This command is used to bind a key group to an SDP, VPRN service, or PW template for inbound or outbound packet processing. When configured in the outbound direction, packets egressing the node use the active-outbound-sa associated with the key group configured. When configured in the inbound direction, received packets must be encrypted using one of the valid security associations configured for the key group. Services using the SDP will be encrypted.

The encryption (enabled or disabled) configured on an SDP used to terminate a Layer 3 spoke SDP of a VPRN always overrides any VPRN-level configuration for encryption.

Encryption is enabled after the outbound direction is configured.

For PW template changes, the following tools command must be executed after the configuration changes are made: tools>perform>service>eval-pw-template>allow-service-impact. This command applies the changes to services that use the PW template.

The no form of the command removes the key group from the SDP or service in the specified direction (inbound or outbound).

Parameters

keygroup-id

Specifies the number of the key group being configured.

Values

1 to 15 or keygroup-name (up to 64 characters)

direction {inbound | outbound}

Specifies the direction of the service that the key group will be bound to.

Platforms

VSR

encryption-offset

encryption-offset

Syntax

encryption-offset encryption-offset

no encryption-offset

Context

[Tree] (config>macsec>connectivity-association encryption-offset)

Full Context

configure macsec connectivity-association encryption-offset

Description

This command specifies the offset of the encryption in MACsec packet.

The encryption-offset is distributed by MKA (Key-server) to all parties.

It is signaled via MACsec capabilities. There are four basic settings for this. MACsec Basic Settings breaks down the settings.

Table 2. MACsec Basic Settings

Setting

Description

0

MACsec is not implemented

1

Integrity without confidentiality

2

The following are supported:

  • Integrity without confidentiality

  • Integrity and confidentiality with a confidentiality offset of 0

3

The following are supported:

  • Integrity without confidentiality

  • Integrity and confidentiality with a confidentiality offset of 0, 30, or 50

Note:

  1. SR OS supports setting (3) Integrity without confidentiality and Integrity and confidentiality with a confidentiality offset of 0, 30, or 50.

The no form of this command rejects all arriving traffic whether MACsec is secured or not.

Default

encryption-offset 0

Parameters

encryption-offset

Specifies the encryption.

Values

0 — encrypt the entire payload

30 — leave the IPv4 header in clear

50 — leave the IPv6 header in clear

Platforms

All

end

end

Syntax

end end-week end-day end-month hours-minutes

Context

[Tree] (config>system>time>dst-zone end)

Full Context

configure system time dst-zone end

Description

This command configures start of summer time settings.

Default

end first sunday january 00:00

Parameters

end-week

Specifies the starting week of the month when the summer time ends.

Values

first, second, third, fourth, last

Default

first

end-day

Specifies the starting day of the week when the summer time ends.

Values

sunday, monday, tuesday, wednesday, thursday, friday, saturday

Default

sunday

end-month

Specifies the starting month of the year when the summer time takes effect.

Values

january, february, march, april, may, june, july, august, september, october, november, december

Default

january

hours-minutes

Specifies the time at which the summer time ends, in hh:mm format.

Values

hours: 00 to 23

minutes: 00 to 59

Default

00:00

Platforms

All

end

Syntax

[no] end function-value

Context

[Tree] (config>router>segment-routing>srv6>inst>loc>func end)

Full Context

configure router segment-routing segment-routing-v6 base-routing-instance locator function end

Description

Commands in this context configure the value and attributes of SRv6 End SID function of a locator. The End SID function encodes the basic behavior of a prefix or a node SID.

The End SID function for each SRH mode must be statically allocated. The value is not automatically allocated by default.

The no form of this command removes the specified End function.

Parameters

function-value

Specifies an SRv6 End SID function value. Up to eight values can be configured per locator. Statically allocated functions of all SID types in a locator have their value upper range limited by parameter locator function-length static-function max-entries.

Values

1 to 1048575

Platforms

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

end-dt2m

end-dt2m

Syntax

end-dt2m [function-value]

no end-dt2m

Context

[Tree] (config>service>vpls>srv6>locator>function end-dt2m)

Full Context

configure service vpls segment-routing-v6 locator function end-dt2m

Description

This command configures the SRv6 End.DT2M behavior and function value that is associated to the SRv6 instance in the service. This means that decapsulation and table lookup for IPv6 prefixes occurs in the VPLS service.

The no form of this command removes the function behavior and value from the configuration.

Default

no end-dt2m

Parameters

function-value

Specifies the optional static function value that is associated to the function behavior. Statically allocated functions of all SID types in a locator have their value upper range limited by parameter locator function-length static-function max-entries. If not configured, the system allocates a value dynamically. Auto-allocated service function values have an upper range limited by the maximum service function length of 20-bits that is used in the datapath lookup for service functions.

Values

1 to 1048575

Platforms

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

end-dt2u

end-dt2u

Syntax

end-dt2u [function-value]

no end-dt2u

Context

[Tree] (config>service>vpls>srv6>locator>function end-dt2u)

Full Context

configure service vpls segment-routing-v6 locator function end-dt2u

Description

This command configures the SRv6 End.DT2U behavior and function value that is associated to the SRv6 instance in the service. This means that decapsulation and table lookup for IPv6 prefixes occurs in the VPLS service.

The no form of this command removes the function behavior and value from the configuration.

Default

no end-dt2m

Parameters

function-value

Specifies the optional static function value that is associated to the function behavior. Statically allocated functions of all SID types in a locator have their value upper range limited by parameter locator function-length static-function max-entries. If not configured, the system allocates a value dynamically. Auto-allocated service function values have an upper range limited by the maximum service function length of 20-bits that is used in the datapath lookup for service functions.

Values

1 to 1048575

Platforms

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

end-dt4

end-dt4

Syntax

end-dt4 [function-value]

no end-dt4

Context

[Tree] (config>service>vprn>srv6>locator>function end-dt4)

Full Context

configure service vprn segment-routing-v6 locator function end-dt4

Description

This command configures the SRv6 End.DT4 behavior and function value that is associated to the SRv6 instance in the service. This implies decapsulation and table lookup for IPv4 prefixes in the VPRN.

The no form of this command removes the function behavior and value from the configuration.

Default

no end-dt4

Parameters

function-value

Specifies the optional static function value that is associated to the function behavior. Statically allocated functions of all SID types in a locator have their value upper range limited by parameter locator function-length static-function max-entries. If not configured, the system allocates a value dynamically. Auto-allocated service function values have an upper range limited by the maximum service function length of 20 bits that is used in the datapath lookup for service functions.

Values

1 to 1048575

Platforms

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

end-dt4

Syntax

end-dt4 [function-value]

no end-dt4

Context

[Tree] (config>router>segment-routing>srv6>inst>loc>func end-dt4)

Full Context

configure router segment-routing segment-routing-v6 base-routing-instance locator function end-dt4

Description

This command configures the SRv6 End.DT4 behavior and function value associated with the base routing instance. This implies decapsulation and table lookup for IPv4 prefixes in the base routing table. These prefixes can be static routes or routes advertised in BGP.

The no form of this command removes the function behavior and value from the configuration.

Default

no end-dt4

Parameters

function-value

Specifies the SRv6 End.DT4 function value. Statically allocated functions of all SID types in a locator have their value upper range limited by parameter locator function-length static-function max-entries. Auto-allocated service function values have an upper range limited by the maximum service function length of 20-bits that is used in the datapath lookup for service functions.

Values

1 to 1048575

Platforms

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

end-dt46

end-dt46

Syntax

end-dt46 [function-value]

no end-dt46

Context

[Tree] (config>service>vprn>srv6>locator>function end-dt46)

Full Context

configure service vprn segment-routing-v6 locator function end-dt46

Description

This command configures the SRv6 End.DT46 behavior and function value that is associated to the SRv6 instance in the service. This means that decapsulation and table lookup for IPv4 and IPv6 prefixes occurs in the VPRN service.

The no form of this command removes the function behavior and value from the configuration.

Default

no end-dt46

Parameters

function-value

Specifies the optional static function value that is associated to the function behavior. Statically allocated functions of all SID types in a locator have their value upper range limited by parameter locator function-length static-function max-entries. If not configured, the system allocates a value dynamically. Auto-allocated service function values have an upper range limited by the maximum service function length of 20-bits that is used in the datapath lookup for service functions.

Values

1 to 1048575

Platforms

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

end-dt46

Syntax

end-dt46 [function-value]

no end-dt46

Context

[Tree] (config>router>segment-routing>srv6>inst>loc>func end-dt46)

Full Context

configure router segment-routing segment-routing-v6 base-routing-instance locator function end-dt46

Description

This command configured the SRv6 End.DT46 function behavior and value associated with the base routing instance. This implies decapsulation and table lookup for IPv4 and IPv6 prefixes in the base routing table. These prefixes can be static routes or routes advertised in BGP.

The no form of this command removes the function behavior and value from the configuration.

Default

no end-dt46

Parameters

function-value

Specifies the SRv6 End.DT46 function value. Statically allocated functions of all SID types in a locator have their value upper range limited by parameter locator function-length static-function max-entries. Auto-allocated service function values have an upper range limited by the maximum service function length of 20-bits that is used in the datapath lookup for service functions.

Values

1 to 1048575

Platforms

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

end-dt6

end-dt6

Syntax

end-dt6 [function-value]

no end-dt6

Context

[Tree] (config>service>vprn>srv6>locator>function end-dt6)

Full Context

configure service vprn segment-routing-v6 locator function end-dt6

Description

This command configures the SRv6 End.DT6 behavior and function value that is associated to the SRv6 instance in the service. This means that decapsulation and table lookup for IPv6 prefixes occurs in the VPRN service.

The no form of this command removes the function behavior and value from the configuration.

Default

no end-dt6

Parameters

function-value

Specifies the optional static function value that is associated to the function behavior. Statically allocated functions of all SID types in a locator have their value upper range limited by parameter locator function-length static-function max-entries. If not configured, the system allocates a value dynamically. Auto-allocated service function values have an upper range limited by the maximum service function length of 20-bits that is used in the datapath lookup for service functions.

Values

1 to 1048575

Platforms

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

end-dt6

Syntax

[no] end-dt6

end-dt6 [function-value]

Context

[Tree] (config>router>segment-routing>srv6>inst>loc>func end-dt6)

Full Context

configure router segment-routing segment-routing-v6 base-routing-instance locator function end-dt6

Description

This command configures the SRv6 End.DT6 function behavior and value associated with the base routing instance. This means that decapsulation and table lookup for IPv6 prefixes occurs in the base routing table. These prefixes can be static routes or routes advertised in BGP.

The no form of this command removes the function behavior and value from the configuration.

Default

no end-dt6

Parameters

function-value

Specifies the SRv6 End.DT6 function value. Statically allocated functions of all SID types in a locator have their value upper range limited by parameter locator function-length static-function max-entries. Auto-allocated service function values have an upper range limited by the maximum service function length of 20-bits that is used in the datapath lookup for service functions.

Values

1 to 1048575

Platforms

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

end-dx2

end-dx2

Syntax

end-dx2 [function-value]

no end-dx2

Context

[Tree] (config>service>epipe>srv6>locator>function end-dx2)

Full Context

configure service epipe segment-routing-v6 locator function end-dx2

Description

This command configures the SRv6 End.DX2 behavior and function value that is associated with the SRv6 instance in the service, which means that decapsulation and cross-connect to the egress SAP occurs in the Epipe service.

The no form of this command removes the function behavior and value from the configuration.

Default

no end-dx2

Parameters

function-value

Specifies the optional static function value that is associated with the function behavior. Statically allocated functions of all SID types in a locator have their upper range limited by the config>router>segment-routing>srv6>loc>static-function max-entries. If not configured, the system allocates a value dynamically. Auto-allocated service function values have an upper range limited by the maximum service function length of 20 bits that is used in the datapath lookup for service functions.

Values

1 to 1048575

Platforms

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

end-marker-count

end-marker-count

Syntax

end-marker-count packets

no end-marker-count

Context

[Tree] (config>subscr-mgmt>gtp>peer-profile end-marker-count)

Full Context

configure subscriber-mgmt gtp peer-profile end-marker-count

Description

This command specifies the number of end marker packets that are sent when it is certain no more packets will be sent over the corresponding GTP-U tunnel, such as after a completed mobility event.

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

Default

end-marker-count 1

Parameters

packets

Specifies the number of end marker packets to send.

Values

0 to 5

Platforms

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

end-of-data

end-of-data

Syntax

[no] end-of-data

Context

[Tree] (debug>router>rpki-session>packet end-of-data)

Full Context

debug router rpki-session packet end-of-data

Description

This command enables debugging for end of data RPKI packets.

The no form of this command disables debugging for end of data RPKI packets.

Platforms

All

end-station-only

end-station-only

Syntax

[no] end-station-only

Context

[Tree] (config>service>vpls>mrp>mmrp end-station-only)

Full Context

configure service vpls mrp mmrp end-station-only

Description

This command configures the end-station-only. This option prevents MMRP messages from being generated or processed. It is useful in case all the MMRP entries for the B-VPLS are static.

Platforms

All

end-time

end-time

Syntax

end-time [date | day-name] time

no end-time

Context

[Tree] (config>system>cron>sched end-time)

Full Context

configure system cron schedule end-time

Description

This command is used concurrently with type periodic or calendar. Using the type of periodic, end-time determines at which interval the schedule will end. Using the type of calendar, end-time determines on which date the schedule will end.

When no end-time is specified, the schedule runs forever.

Default

no end-time

Parameters

date

Specifies the date to schedule a command.

Values

YYYY:MM:DD in year:month:day number format

day-name

Specifies the day of the week to schedule a command.

Values

sunday, monday, tuesday, wednesday, thursday, friday, saturday

time

Specifies the time of day to schedule a command.

Values

hh:mm

Platforms

All

end-time

Syntax

end-time date hours-minutes [UTC]

end-time {now | forever}

no end-time

Context

[Tree] (config>system>security>keychain>direction>uni>receive>entry end-time)

Full Context

configure system security keychain direction uni receive entry end-time

Description

This command specifies the calendar date and time after which the key specified by the authentication key is no longer eligible to sign or authenticate the protocol stream.

Default

end-time forever

Parameters

date

Specifies the calendar date after which the key specified by the authentication key is no longer eligible to sign or authenticate the protocol stream in the YYYY/MM/DD format. When no year is specified the system assumes the current year.

hours-minutes

Specifies the time after which the key specified by the authentication key is no longer eligible to sign or authenticate the protocol stream in the hh:mm[:ss] format. Seconds are optional, and if not included, assumed to be 0.

UTC

Indicates that time is given with reference to Coordinated Universal Time in the input.

now

Specifies a time equal to the current system time.

forever

Specifies that the key is always active.

Platforms

All

end-x

end-x

Syntax

[no] end-x function-value

Context

[Tree] (config>router>segment-routing>srv6>inst>loc>func end-x)

Full Context

configure router segment-routing segment-routing-v6 base-routing-instance locator function end-x

Description

Commands in this context configure the attributes of the End.X SID function associated with a P2P interface. The End.X SID function encodes the behavior of an adjacency SID.

A static function value can be configured for each combination of SRH mode and protection type.

For a given interface, the static function value associated with the same combination of protection type and SRH mode overrides any corresponding automatically allocated function value (end-x-auto-allocate command configuration).

If more than one value is configured for an interface and combination of SRH mode and protection type, they are all advertised in IS-IS.

When used in remote TI-LFA repair tunnel programming, IS-IS uses rules to select one End.X value from the multiple values received in IS-IS link advertisements.

Values assigned to loopback and system interfaces are not advertised in IS-IS.

End.X SID functions for adjacencies over broadcast interfaces are always automatically allocated based on the configuration of the end-x-auto-allocate command.

The no form of this command removes the function value from the configuration.

Parameters

function-value

Specifies the SRv6 End.X function. Statically allocated functions of all SID types in a locator have their value upper range limited by parameter locator function-length static-function max-entries.

Values

1 to 1048575

Platforms

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

end-x-auto-allocate

end-x-auto-allocate

Syntax

[no] end-x-auto-allocate srh-mode srh-mode protection protection

Context

[Tree] (config>router>segment-routing>srv6>inst>loc>func end-x-auto-allocate)

Full Context

configure router segment-routing segment-routing-v6 base-routing-instance locator function end-x-auto-allocate

Description

This command adds an list entry for the automatic allocation of the End.X SID function for all adjacencies over all network interfaces on the router (P2P and broadcast interfaces). Auto-allocated End.X SID function values have a range up to the maximum value of parameter function-length in a locator configuration.

A list entry is a combination of the protection type and the SRH mode. Any combinations in addition to the maximum number of entries supported by this command must be allocated statically for each P2P interface. The maximum number of entries in this list is two.

When no list entries are configured, no End.X function values are automatically allocated by default for a locator.

Note:

Any change to this list causes a re-allocation of new function values to all interfaces on the router that results in flooding them to the network and triggers a new SPF in all routers.

The no form of this command removes a list entry.

Parameters

srh-mode

Specifies the SRH mode for the SID.

Values

psp — Penultimate Segment Pop of the SRH

usp — Ultimate Segment Pop of the SRH

protection

Specifies if the adjacency SID is protected.

Values

protected, unprotected

Platforms

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

endpoint

endpoint

Syntax

endpoint ip ip-address

endpoint mac ieee-address

endpoint system-ip

endpoint system-mac

no endpoint

Context

[Tree] (config>subscr-mgmt>ppp-policy>mlppp endpoint)

[Tree] (config>router>l2tp>group>mlppp endpoint)

[Tree] (config>router>l2tp>group>tunnel>mlppp endpoint)

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

[Tree] (config>service>vprn>l2tp>group>mlppp endpoint)

Full Context

configure subscriber-mgmt ppp-policy mlppp endpoint

configure router l2tp group mlppp endpoint

configure router l2tp group tunnel mlppp endpoint

configure service vprn l2tp group tunnel mlppp endpoint

configure service vprn l2tp group mlppp endpoint

Description

When configured under the l2tp hierarchy, this command is applicable to LNS.

Within the ppp-policy, this command is applicable only to LAC.

The endpoint, according to RFC 1990, represents the system transmitting the packet. It is used during MLPPPoX negotiation phase to distinguish this peer from all others.

In the case that the client rejects the endpoint option during LCP negotiation, the LAC and the LNS must be able to negotiate the LCP session without the endpoint option.

The no form of this command disables sending endpoint option in LCP negotiation.

Parameters

ip-address

Specifies the IPv4 address (class 2).

system-ip

Specifies to use the system IPv4 address (class 2).

ieee-address

Specifies the MAC address of the interface (class 3).

system-mac

Specifies to use the MAC address of the system (class 3).

Platforms

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

endpoint

Syntax

endpoint endpoint-name [create]

no endpoint endpoint-name

Context

[Tree] (config>service>epipe endpoint)

[Tree] (config>service>ipipe endpoint)

[Tree] (config>service>cpipe endpoint)

Full Context

configure service epipe endpoint

configure service ipipe endpoint

configure service cpipe endpoint

Description

This command configures a service endpoint.

Parameters

endpoint-name

Specifies an endpoint name.

Platforms

All

  • configure service ipipe endpoint
  • configure service epipe endpoint

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

  • configure service cpipe endpoint

endpoint

Syntax

endpoint endpoint-name [create]

no endpoint

Context

[Tree] (config>service>vpls endpoint)

Full Context

configure service vpls endpoint

Description

This command configures a service endpoint.

Parameters

endpoint-name

Specifies an endpoint name up to 32 characters in length

create

This keyword is mandatory while creating a service endpoint

Platforms

All

endpoint

Syntax

endpoint ip-address

no endpoint

Context

[Tree] (config>router>mpls>fwd-policies>fwd-policy endpoint)

Full Context

configure router mpls forwarding-policies forwarding-policy endpoint

Description

This command configures the endpoint address for an MPLS forwarding policy.

The policy allows the user to forward unlabeled packets over a set of user-defined direct (with option to push a label stack) or indirect next hops. Routes are bound to an endpoint policy when their next hop matches the endpoint address of the policy.

The no form of the command removes the endpoint from the MPLS forwarding policy.

Parameters

ip-address

Specifies the destination IPv4 or IPv6 address.

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..FFFF]H

d - [0..255]D

Platforms

All

endpoint

Syntax

endpoint endpoint-name [create]

no endpoint endpoint-name

Context

[Tree] (config>mirror>mirror-dest endpoint)

[Tree] (config>mirror>mirror-dest>sdp endpoint)

[Tree] (config>mirror>mirror-dest>sap endpoint)

Full Context

configure mirror mirror-dest endpoint

configure mirror mirror-dest sdp endpoint

configure mirror mirror-dest sap endpoint

Description

This command configures a service end point. A mirror service supports two implicit endpoints managed internally by the system. The following applies to endpoint configurations.

Up to two named endpoints may be created per service mirror or LI service. The endpoint name is locally significant to the service mirror or LI service.

  • Objects (SAPs or SDPs) may be created on the service mirror or LI with the following limitations:

    • two implicit endpoint objects (without explicit endpoints defined)

    • one implicit and multiple explicit object with the same endpoint name

    • multiple explicit objects each with one of two explicit endpoint names

  • All objects become associated implicitly or indirectly with the implicit endpoints 'x' and 'y'.

  • Objects may be created without an explicit endpoint defined.

  • Objects may be created with an explicit endpoint defined.

  • Objects without an explicit endpoint may have an explicit endpoint defined without deleting the object.

  • Objects with an explicit endpoint defined may be dynamically moved to another explicit endpoint or may have the explicit endpoint removed.

Creating an object without an explicit endpoint:

  • If an object on a mirror or LI service has no explicit endpoint name associated, the system attempts to associate the object with implicit endpoint 'x' or 'y'.

  • The implicit endpoint cannot have an existing object association.

  • If both 'x' and 'y' are available, 'x' is selected.

  • If an 'x' or 'y' association cannot be created, the object cannot be created.

Creating an object with an explicit endpoint name:

  • The endpoint name must exist on the mirror or LI service.

  • If this is the first object associated with the endpoint name:

    • the object is associated with either implicit endpoint 'x' or 'y'

    • the implicit endpoint cannot have an existing object associated

    • if both 'x' and 'y' are available, 'x' is selected

    • if 'x' or 'y' is not available, the object cannot be created

    • the implicit endpoint is now associated with the named endpoint

    • f this is not the first object associated with the endpoint name:

    • the object is associated with the named endpoint's implicit association

Changing an object’s implicit endpoint to an explicit endpoint name

  • If the explicit endpoint name is associated with an implicit endpoint, the object is moved to that implicit endpoint

  • If the object is the first to be associated with the explicit endpoint name:

    • the object is associated with either implicit endpoint 'x' or 'y'

    • the implicit endpoint cannot have an existing object associated (except this one)

    • if both 'x' and 'y' are available, 'x' is selected

    • if 'x' or 'y' is not available, the object cannot be moved to the explicit endpoint

    • if moved, the implicit endpoint is now associated with the named endpoint

Changing an object’s explicit endpoint to another explicit endpoint name

  • If the new explicit endpoint name is associated with an implicit endpoint, the object is moved to that implicit endpoint

  • If the object is the first to be associated with the new explicit endpoint name:

    • the object is associated with either implicit endpoint 'x' or 'y'

    • the implicit endpoint cannot have an existing object associated (except this one)

    • if both 'x' and 'y' are available, 'x' is selected

    • if 'x' or 'y' is not available, the object cannot be moved to the new endpoint

    • if moved, the implicit endpoint is now associated with the named endpoint

An explicitly named endpoint can have a maximum of one SAP and one ICB. Once a SAP is added to the endpoint, only one more object of type ICB sdp is allowed. The ICB sdp cannot be added to the endpoint if the SAP is not part of a MC-LAG instance. Conversely, a SAP which is not part of a MC-LAG instance cannot be added to an endpoint which already has an ICB sdp.

An explicitly named endpoint which does not have a SAP object can have a maximum of four SDPs which can include any of the following: a single primary SDP, one or many secondary SDPs with precedence, and a single ICB SDP.

The user can only add a SAP configured on a MC-LAG instance to this endpoint. Conversely, the user will not be able to change the mirror service type away from mirror service without first deleting the MC-LAG SAP.

The no form of this command removes the association of a SAP or an SDP with an explicit endpoint name. When removing an objects explicit endpoint association:

  • The system attempts to associate the object with implicit endpoint 'x' or 'y'.

  • The implicit endpoint cannot have an existing object association (except this one).

  • If both 'x' and 'y' are available, 'x' is selected.

  • If an 'x' or 'y' association cannot be created, the explicit endpoint cannot be removed.

Parameters

endpoint-name

Specifies the endpoint name.

create

Mandatory keyword to create this entry.

Platforms

All

endpoint

Syntax

endpoint ip-address

no endpoint

Context

[Tree] (conf>router>segment-routing>sr-policies>policy endpoint)

Full Context

configure router segment-routing sr-policies static-policy endpoint

Description

This command associates an IPv4 or IPv6 endpoint address with a statically-defined segment routing policy. This association is mandatory when enabling an SR segment-routing policy.

The endpoint address 0.0.0.0 is a special value that matches all BGP next-hops. To use it, the BGP route must have a color-extended community with the color-only bits set to '01' or '10'.

The no form of this command removes the endpoint association.

Default

no endpoint

Parameters

ip-address

Specifies the endpoint IP address to be associated with the statically-defined segment-routing policy.

Values

ipv4-address:

a.b.c.d

ipv6-address:

x:x:x:x:x:x:x:x

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

x:

[0 to FFFF]H

d:

[0 to 255]D

Platforms

All

endpoint

Syntax

endpoint ip-address

no endpoint

Context

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

Full Context

configure router policy-options policy-statement entry from endpoint

Description

This command configures an SR Policy endpoint address as a route policy match criterion. This match criterion is only used in import policies.

The no form of this command removes the endpoint IP match criterion from the configuration.

Parameters

ip-address

Specifies the IPv4 or IPv6 address.

Values

ipv4-address:

  • a.b.c.d

ipv6-address:

  • x:x:x:x:x:x:x:x [-interface]

  • x:x:x:x:x:x:d.d.d.d [-interface]

  • x: [0 to FFFF]H

  • d: [0 to 255]D

Platforms

All

endstation-vid-group

endstation-vid-group

Syntax

endstation-vid-group id vlan-id startvid-endvid

no endstation-vid-group id

Context

[Tree] (config>service>vpls>mrp>mvrp endstation-vid-group)

Full Context

configure service vpls mrp mvrp endstation-vid-group

Description

This command specifies the range of VLAN IDs that are controlled by MVRP on the port associated with the parent SAP. When the command is present under a certain SAP, the MVRP will treat the associated virtual port as an end-station.

MVRP endstation behavior means that configuration of a new data SAP with the outer tag in the configured endstation-vid-group will generate down that virtual port a MVRP declaration for the new [outer] VLAN attribute. Also registration received for the VLAN attribute in the range will be accepted but not propagated in the rest of MVRP context.

VPLS-groups are not allowed under the associated Management VPLS (M-VPLS) when the endstation is configured under one SAP. VPLS-groups can be supported in the chassis using a different M-VPLS.

The no form of this command removes the specified group id.

Default

no endstation-vid-group

Parameters

id

Specifies the range index

Values

1 to 4094

startvid-endvid

Specifies the range of VLANs to be controlled by MVRP

Values

1 to 4094

Platforms

All

enforce-diffserv-lsp-fc

enforce-diffserv-lsp-fc

Syntax

[no] enforce-diffserv-lsp-fc

Context

[Tree] (config>service>sdp>class-forwarding enforce-diffserv-lsp-fc)

Full Context

configure service sdp class-forwarding enforce-diffserv-lsp-fc

Description

This command enables checking by RSVP that a Forwarding Class (FC) mapping to an LSP under the SDP configuration is compatible with the Diff-Serv Class Type (CT) configuration for this LSP.

When the user enables this option, the service manager inquires with RSVP if the FC is supported by the LSP. RSVP checks if the FC maps to the CT of the LSP, for example, the default class-type value or the class-type value entered at the LSP configuration level.

If RSVP did not validate the FC, then the service manager will return an error and the check has failed. In this case, packets matching this FC will be forwarded over the default LSP. Any addition of an LSP to an SDP that will not satisfy the FC check will also be rejected.

The service manager does not validate the default-lsp FC-to-CT mapping. Whether or not the FC is validated, the default-lsp will always end up being used in this case.

RSVP will not allow the user to change the CT of the LSP until no SDP with class-based forwarding enabled and the enforce-diffserv-lsp-fc option enabled is using this LSP. All other SDPs using this LSP are not concerned by this rule.

The SDP will continue to enforce the mapping of a single LSP per FC. However, when enforce-diffserv-lsp-fc enabled, RSVP will also enforce the use of a single CT per FC as per the user configured mapping in RSVP.

If class-forwarding is enabled but enforce-diffserv-lsp-fc is disabled, forwarding of the service packets will continue to be based on the user entered mapping of FC to LSP name without further validation as per the existing implementation. The CT of the LSP does not matter in this case.

If class-forwarding is not enabled on the SDP, forwarding of the service packets will continue to be based on the ECMP/LAG hash routine. The CT of the LSP does not matter in this case.

The no form of this command reverts to the default value which is to use the user entered mapping of FC to LSP name.

Default

no enforce-diffserv-lsp-fc

Platforms

All

enforce-first-as

enforce-first-as

Syntax

enforce-first-as

Context

[Tree] (config>service>vprn>bgp>group>neighbor enforce-first-as)

[Tree] (config>service>vprn>bgp>group enforce-first-as)

[Tree] (config>service>vprn>bgp enforce-first-as)

Full Context

configure service vprn bgp group neighbor enforce-first-as

configure service vprn bgp group enforce-first-as

configure service vprn bgp enforce-first-as

Description

When this command is configured so that it applies to an EBGP session, all routes (belonging to all address families) that are received from the EBGP peer are checked to ensure that the most recent autonomous system number (ASN) in the AS_PATH attribute of each route matches the configured peer-as of the session; if it does not match, then either the session is reset (if update-fault-tolerance is not enabled) or the session is left up but the route is treated as withdrawn (if update-fault-tolerance is enabled).

Enabling or disabling this command on a session that is already up does not flap the session. When enforce-first-as is enabled, previously received routes are not checked for compliance with the rule. Enforcement applies only to routes received after the command is enabled and stops when the command is disabled.

Platforms

All

enforce-first-as

Syntax

enforce-first-as

Context

[Tree] (config>router>bgp>group>neighbor enforce-first-as)

[Tree] (config>router>bgp>group enforce-first-as)

[Tree] (config>router>bgp enforce-first-as)

Full Context

configure router bgp group neighbor enforce-first-as

configure router bgp group enforce-first-as

configure router bgp enforce-first-as

Description

When this command is configured so that it applies to an EBGP session, all routes (belonging to all address families) that are received from the EBGP peer are checked to ensure that the most recent autonomous system number (ASN) in the AS_PATH attribute of each route matches the configured peer-as of the session; if it does not match, then either the session is reset (if update-fault-tolerance is not enabled) or the session is left up but the route is treated as withdrawn (if update-fault-tolerance is enabled).

Enabling or disabling this command on a session that is already up does not flap the session. When enforce-first-as is enabled, previously received routes are not checked for compliance with the rule. Enforcement applies only to routes received after the command is enabled and stops when the command is disabled.

Platforms

All

enforce-strict-tunnel-tagging

enforce-strict-tunnel-tagging

Syntax

[no] enforce-strict-tunnel-tagging

Context

[Tree] (config>service>vprn>bgp-evpn>mpls>auto-bind-tunnel enforce-strict-tunnel-tagging)

[Tree] (config>service>vpls>bgp-evpn>mpls>auto-bind-tunnel enforce-strict-tunnel-tagging)

[Tree] (config>service>epipe>bgp-evpn>mpls>auto-bind-tunnel enforce-strict-tunnel-tagging)

Full Context

configure service vprn bgp-evpn mpls auto-bind-tunnel enforce-strict-tunnel-tagging

configure service vpls bgp-evpn mpls auto-bind-tunnel enforce-strict-tunnel-tagging

configure service epipe bgp-evpn mpls auto-bind-tunnel enforce-strict-tunnel-tagging

Description

This command forces the system to only consider LSPs marked with an admin tag for next hop resolution. Untagged LSPs are not considered.

The no form of this command reverts to default value. While tagged RSVP and SR-TE LSPs are considered first, the system can fall back to using untagged LSPs of other types and does not exclude them depending on the auto-bind-tunnel configuration.

Default

no enforce-strict-tunnel-tagging

Platforms

All

enforce-strict-tunnel-tagging

Syntax

[no] enforce-strict-tunnel-tagging

Context

[Tree] (config>router>bgp>next-hop-resolution>labeled-routes>transport-tunnel>family enforce-strict-tunnel-tagging)

[Tree] (config>router>bgp>next-hop-resolution>shortcut-tunn>family enforce-strict-tunnel-tagging)

Full Context

configure router bgp next-hop-resolution labeled-routes transport-tunnel family enforce-strict-tunnel-tagging

configure router bgp next-hop-resolution shortcut-tunnel family enforce-strict-tunnel-tagging

Description

This command forces the system to only consider LSPs marked with an admin-tag for next-hop resolution. Untagged LSPs are not be considered.

The no form of this command reverts to the default behavior. While tagged RSVP and SR-TE LSPs will be considered first, the system can fall back to using tagged LSPs that are not explicitly excluded by a route admin tag policy and untagged LSPs of other types and not exclude them.

Default

no enforce-strict-tunnel-tagging

Platforms

All

enforce-test-session-start-time

enforce-test-session-start-time

Syntax

[no] enforce-test-session-start-time

Context

[Tree] (config>test-oam>twamp>server enforce-test-session-start-time)

Full Context

configure test-oam twamp server enforce-test-session-start-time

Description

This command configures the router to check the signalled test-session start time against the server time and discard TWAMP test packets that arrive before the negotiated test-session start time.

The no form of this command configures the router to process all TWAMP test packets without checking the test-session start time against the server time.

Default

enforce-test-session-start-time

Platforms

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

enforce-unique-if-index

enforce-unique-if-index

Syntax

[no] enforce-unique-if-index

Context

[Tree] (config>system>ip enforce-unique-if-index)

Full Context

configure system ip enforce-unique-if-index

Description

This command enables the options to force the creation of IP interface indexes so that they are globally unique across all routing contexts. In addition, the command ensures that any interface created using SNMP also has a system-wide unique IP interface index.

If this command is issued but the system has previously existing interface indexes that conflict, the command will be rejected until all the conflicts are removed. Pre-existing persistency tables should also be removed before enabling this system option.

The no form of the command disables this option and returns the system to the default behavior.

Default

no enforce-unique-if-index

Platforms

All

enforcement

enforcement

Syntax

enforcement {static policer-name | dynamic {mon-policer-name | local-mon-bypass}}

Context

[Tree] (config>sys>security>dist-cpu-protection>policy>protocol enforcement)

Full Context

configure system security dist-cpu-protection policy protocol enforcement

Description

This command configures the enforcement method for the protocol.

Default

enforcement dynamic local-mon-bypass

Parameters

static

Specifies that the protocol is always enforced using a static-policer. Multiple protocols can reference the same static-policer. Packets of protocols that are statically enforced bypass any local monitors.

policer name

Specifies which static-policer to use.

dynamic

Specifies that a specific enforcement policer for this protocol for this SAP/object is instantiated when the associated local-monitoring-policer is determined to be in a nonconforming state (at the end of a minimum monitoring time of 60 seconds to reduce thrashing).

mon-policer-name

Specifies which local-monitoring-policer to use.

local-mon-bypass

This parameter is used to not include packets from this protocol in the local monitoring function, and when the local-monitor "trips”, do not instantiate a dynamic enforcement policer for this protocol.

Platforms

All

engineID

engineID

Syntax

[no] engineID engine-id

Context

[Tree] (config>system>snmp engineID)

Full Context

configure system snmp engineID

Description

This command sets the SNMP engine ID that uniquely identifies the SNMPv3 node.If unconfigured, the system uses an engine ID based on the information from the system backplane.If the SNMP engine ID is changed, the current configuration must be saved and a reboot must be executed. Otherwise, the previously configured SNMP communities and logger trap-target notify communities will not be valid for the new engine ID.

Note:

Changing the SNMP engine ID invalidates all SNMPv3 MD5 and SHA security digest keys, which may render the node unmanageable.

When replacing a chassis, configure the new router to use the same engine ID as the previous router. This preserves SNMPv3 security keys and allows management stations to use their existing authentication keys for the new router.

Ensure that the engine ID of each router is unique. A management domain can only maintain one instance of a specific engine ID.

The no form of the command configures the router to use the default value.

Parameters

engine-id

Specifies an identifier from 10 to 64 hexadecimal digits (5 to 32 octet number), uniquely identifying this SNMPv3 node. This string is used to access this node from a remote host with SNMPv3.

Platforms

All

enhanced-distribution

enhanced-distribution

Syntax

[no] enhanced-distribution

Context

[Tree] (config>cflowd enhanced-distribution)

Full Context

configure cflowd enhanced-distribution

Description

This command enables the inclusion of the ingress port ID into the hash algorithm used to distribute cflowd sample traffic to cflowd processes running on the 7950 XRS CPM. By including this new attribute, cflowd may see better distribution of flows across processing tasks if there is a limited number of IP interfaces on which sampling is performed, but those interfaces use LAGs with a large number of port members.

By enabling this option, the same flow may be captured multiple times if packets are received on multiple ingress ports.

This command is only applicable to cflowd running on a 7950 XRS platform.

The no form of this command removes the command from the configuration and disables the inclusion of the ingress port ID in the cflowd hash algorithm.

Default

no enhanced-distribution

Platforms

7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS

enqueue-on-pir-zero

enqueue-on-pir-zero

Syntax

[no] enqueue-on-pir-zero

Context

[Tree] (config>qos>adv-config-policy>child-control>bandwidth-distribution enqueue-on-pir-zero)

Full Context

configure qos adv-config-policy child-control bandwidth-distribution enqueue-on-pir-zero

Description

This command is used to enable queuing of new packets when H-QoS determines that a queue should stop forwarding (operational PIR set to zero). The default behavior is to allow the queue to continue to use the previously determined operational PIR and set the queue’s MBS (Maximum Burst Size) to zero. This prevents new packets from being admitted to the queue until the PIR zero case terminates. The new behavior when enqueue-on-pir-zero is enabled is to set the operational PIR to zero and leave the queue’s MBS set to the normal value.

This command overrides the limit-pir-zero-drain command.

The no form of this command reverts to default behavior.

Platforms

All

enroll

enroll

Syntax

enroll est-profile name key key-filename output output-cert-filename [hash-alg hash algorithm] subject-dn subject-dn [domain-name domain-names] [ip-addr ip-address | ipv6-address] [validate-cert-chain] [force]

Context

[Tree] (admin>certificate>est enroll)

Full Context

admin certificate est enroll

Description

This command enrolls a new certificate with Certificate Authority (CA) by the EST protocol specified with the est-profile name parameter with a imported private key specified by the key key-filename parameter.

The est-profile name specifies the authentication between the system and EST server.

The hash-alg hash-algorithm, subject-dn subject-dn, domain-name domain-names, and ip-addr ip-address parameters are used to generate the Certificate Signing Request (CSR) in the EST request message. The domain-name domain-names and ip-addr ip-address parameters are used as subject alternative names.

If validate-cert-chain is specified, the system validates the certificate’s chain of result certificate before importing it. The "certificate chain” is the chain of all the certificates from the result certificate to the issuing CA. The "result certificate” is the new certificate returned by EST server.

The result certificate is imported and saved with the filename specified by the output output-cert-filename. If force is specified, the system overwrites the existing file with same name as the output-cert-filename.

Parameters

name

Specifies EST profile name, up to 32 characters

key-filename

Specifies the filename of a key, up to 95 characters

output-cert-filename

Specifies the output certificate filename, up to 200 characters

hash-algorithm

Specifies the hash algorithm used in a certificate request.

Values

sha1, sha224, sha256, sha384, sha512

subject-dn

Specifies the distinguish name, up to 256 characters, used as the subject in a certificate request, including:

  • C-Country

  • ST-State

  • O-Organization name

  • OU-Organization Unit name

  • CN-common name

This parameter is formatted as a text string including any of the preceding attributes. The attribute and its value is linked by using "=”, and ",” is used to separate different attributes.

For example: C=US,ST=CA,O=ALU,CN=SR12

Values

attr1=val1,attr2=val2

where: attrN={C | ST | O | OU | CN}, up to 256 characters

domain-names

Specifies domain names, up to 512 characters, separated by commas

ip-address

Specifies an IPv4 or IPv6 address string, up to 64 characters

validate-cert-chain

Specifies that the system validates the certificate’s chain of result certificate before importing it

force

Specifies that the system overwrites the existing file with same output-cert-filename

Platforms

All

enter

enter

Syntax

[no] enter

Context

[Tree] (config>system>management-interface>cli>md-cli>environment>command-completion enter)

Full Context

configure system management-interface cli md-cli environment command-completion enter

Description

This command enables completion on the enter character.

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

Default

enter

Platforms

All

entropy-label

entropy-label

Syntax

[no] entropy-label

Context

[Tree] (config>service>vpls>mesh-sdp entropy-label)

[Tree] (config>service>epipe>bgp-evpn>mpls entropy-label)

[Tree] (config>service>vpls>bgp-evpn>mpls entropy-label)

[Tree] (config>service>epipe>spoke-sdp entropy-label)

[Tree] (config>service>pw-template entropy-label)

[Tree] (config>service>ipipe>spoke-sdp entropy-label)

[Tree] (config>service>vpls>spoke-sdp entropy-label)

Full Context

configure service vpls mesh-sdp entropy-label

configure service epipe bgp-evpn mpls entropy-label

configure service vpls bgp-evpn mpls entropy-label

configure service epipe spoke-sdp entropy-label

configure service pw-template entropy-label

configure service ipipe spoke-sdp entropy-label

configure service vpls spoke-sdp entropy-label

Description

This command enables or disables the use of entropy labels for spoke SDPs.

If entropy-label is configured, the entropy label and ELI are inserted in packets for which at least one LSP in the stack for the far-end of the tunnel used by the service has advertised entropy-label-capability. If the tunnel is RSVP type, entropy-label can also be controlled under the config>router>mpls or config>router>mpls>lsp contexts.

The entropy label and hash label features are mutually exclusive. The entropy label cannot be configured on a spoke SDP or service where the hash label feature has already been configured.

Default

no entropy-label

Platforms

All

entropy-label

Syntax

[no] entropy-label

Context

[Tree] (config>service>ies>if>spoke-sdp entropy-label)

Full Context

configure service ies interface spoke-sdp entropy-label

Description

This command enables the use of entropy labels on a spoke-SDP bound to an IES interface.

If entropy-label is configured, the entropy label and ELI are inserted in packets for which at least one LSP in the stack for the far-end of the tunnel used by the service has advertised entropy-label-capability. If the tunnel is RSVP, entropy-label can also be controlled under the config>router>mpls or config>router>mpls>lsp contexts.

The entropy label and hash label features are mutually exclusive. The entropy label cannot be configured on a spoke-sdp or service where the hash label feature has already been configured.

Default

no entropy-label

Platforms

All

entropy-label

Syntax

[no] entropy-label

Context

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

[Tree] (config>service>vprn>if>spoke-sdp entropy-label)

Full Context

configure service vprn entropy-label

configure service vprn interface spoke-sdp entropy-label

Description

This command enables or disables the use of entropy labels for spoke SDPs on a VPRN.

If entropy-label is configured, the entropy label and ELI are inserted in packets for which at least one LSP in the stack for the far-end of the tunnel used by the service has advertised entropy-label-capability. If the tunnel is RSVP type, entropy-label can also be controlled under the config>router>mpls or config>router>mpls>lsp contexts.

The entropy label and the hash label features are mutually exclusive. The entropy label cannot be configured on a spoke SDP or service where the hash label feature has already been configured.

Default

no entropy-label

Platforms

All

entropy-label

Syntax

entropy-label

[no] entropy-label

Context

[Tree] (config>service>sdp>binding>pw-port entropy-label)

Full Context

configure service sdp binding pw-port entropy-label

Description

This command enables entropy label insertion on the PW port.

If this command is configured, the entropy label and ELI are inserted in packets for which at least one LSP in the stack for the far-end of the tunnel used by the service has advertised entropy label capability.

  • If the tunnel is of type RSVP or SR-TE, the entropy-label must be enabled under the config>router>mpls or config>router>mpls>lsp contexts.

  • If the tunnel is of type SR-ISIS, SR-OSPF or SR-TE, the override-tunnel-elc command must be configured under the config>router>isis or config>router>ospf contexts.

  • If the tunnel is LDP, the entropy-level capability is configured under the configure>router>ldp context.

The entropy label is only applicable to PW ports bound to a static port, and not to ports using an FPE.

The no form of this command disables the entropy label insertion on the PW port.

Default

no entropy-label

Platforms

All

entropy-label

Syntax

entropy-label {rsvp-te | sr-te} {force-disable | enable}

Context

[Tree] (config>router>mpls entropy-label)

Full Context

configure router mpls entropy-label

Description

This command configures the use of entropy labels for MPLS.

The entropy label (EL) and entropy label indicator (ELI) require the insertion of two additional labels in the label stack. In some cases, this may result in an unsupported label stack depth or large changes in the label stack depth during the lifetime of an LSP (for example, due to switching from a primary path with ELC enabled to a secondary path for which the far end has not signaled ELC).

This command provides control at the head end of an RSVP LSP or SR-TE LSP as to whether an EL is inserted on an LSP by ignoring the ELC signaled from the far-end LER, and to control how the additional label stack depth is accounted for.

By default, regardless of the value set for entropy label capability at the egress node, the ingress LER considers the EL and ELI in the label stack while sending the information to the TTM and NHLFE. The application using the LSP does not insert an EL and ELI in the label stack unless the far-end signals ELC and the application is configured to insert an entropy label.

When entropy-label is set to force-disable, the ingress LER does not consider EL and ELC in the label stack when sending the information to the TTM and NHLFE. Therefore, the system marks the TTM and NHLFE as ELC not supported, and applications do not insert an EL or ELI.

The entropy-label command value changes at either the MPLS level or the LSP level. The new operational value does not take effect until the LSP is re-signaled. A shutdown and no shutdown of the LSP is required to enable the new value.

The user can use the clear command or bounce MPLS itself (shutdown/no shutdown) to force the new value to take effect for a large numbers of LSPs.

Default

entropy-label rsvp-te enable

Parameters

rsvp-te

Applies the entropy-label command to RSVP LSPs.

sr-te

Applies the entropy-label command applies to SR-TE LSPs.

force-disable

Specifies that the ingress LER will not consider the EL and ELI in the label stack while sending the information to the TTM and NHLFE. The system marks the TTM and NHLFE as ELC not supported, and applications do not insert an EL or ELI in the label stack.

enable

Specifies that the ingress LER will consider what is signaled from the egress node for ELC for marking the NHLFE, while the TTM is always marked. Although applications only insert the entropy label if the far end signals ELC, the additional two labels of the EL and ELI are always accounted for.

Platforms

All

entropy-label

Syntax

entropy-label {force-disable | enable | inherit}

Context

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

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

Full Context

configure router mpls lsp-template entropy-label

configure router mpls lsp entropy-label

Description

This command configures the use of entropy labels for an LSP.

The entropy label (EL) and entropy label indicator (ELI) require the insertion of two additional labels in the label stack. In some cases, this may result in an unsupported label stack depth or large changes in the label stack depth during the lifetime of an LSP (for example, due to switching from a primary path with ELC enabled to a secondary path for which the far end has not signaled ELC).

This command provides control at the head end of an RSVP LSP or SR-TE LSP over whether an entropy label is inserted on an LSP by overriding the ELC signaled from the far-end LER, and control over how the additional label stack depth is accounted for.

By default, the value of entropy-label is inherited from the MPLS level. The command under the LSP context provides a means to override the default MPLS behavior on a per-LSP basis. For auto-LSPs, it can only be configured in LSP templates of type one-hope-p2p and mesh-p2p.

Under the LSP context, when the value of entropy-label is set to enable, the ingress LER will take into consideration what is signaled from the egress node for ELC when marking the NHLFE as entropy-label-capable. Since the value of entropy-label is set to enable at the LSP level, the system will always mark it in the TTM as entropy-label-capable regardless of the signaled value, in order to ensure that the potential additional label stack depth is accounted for. In this scenario, the TTM and NHLFE can be out of synchronization based on what is configured at the egress node. That is, the application will always account for the entropy label and ELI in the label stack without taking into consideration the signaled value of ELC.

When entropy-label is set to force-disable, the ingress LER will not consider EL and ELI in the label stack while sending the information to the TTM and NHLFE, regardless of what the far end signals. Therefore, the system will mark the TTM and NHLFE as ELC not supported, and applications will not insert an EL or ELI.

When the value of entropy-label changes at either the MPLS level or the LSP level, the new operational value will not take effect until the LSP is re-signaled. A shutdown and no shutdown of the LSP is required to enable the new value.

The user can use the clear command or bounce MPLS itself (shutdown and no shutdown) to force the new value to take effect for a large numbers of LSPs.

Default

entropy-label inherit

Parameters

force-disable

Indicates that the ingress LER will not consider the entropy label and ELI in the label stack while sending the information to the TTM and NHLFE. The system will mark the TTM and NHLFE as ELC not supported, and applications will not insert an EL or ELI in the label stack.

enable

Indicates that the ingress LER will take into consideration what is signaled from the egress node for ELC for marking the NHLFE, while the TTM is always marked. Therefore, although applications will only insert the entropy label if the far end signals ELC, the additional two labels of the entropy label EL and ELI are always accounted for.

inherit

Indicates that the value of entropy-label is inherited from the setting in the MPLS context.

Platforms

All

entropy-label

Syntax

[no] entropy-label

Context

[Tree] (config>router entropy-label)

Full Context

configure router entropy-label

Description

If entropy-label is configured, the Entropy label and Entropy Label Indicator is inserted on packets for which at least one LSP in the stack for the far-end of the LDP or RSVP tunnel used by an IGP or BGP shortcut has advertised entropy-label-capability. If the tunnel is of type RSVP, then entropy-label must also have been enabled under config>router>mpls or config>router>mpls>lsp.

This configuration will result in other traffic that is forwarded over an LDP or RSVP LSP for which this router is the LER, and for which there is no explicit service endpoint on this router, to have the EL/ELI enabled, subject to the LSP far-end advertising entropy-label-capability. An example of such traffic includes packets arriving on a stitched LDP LSP forwarded over an RSVP LSP.

Default

no entropy-label

Platforms

All

entropy-label

Syntax

entropy-label

Context

[Tree] (config>router>isis entropy-label)

[Tree] (config>router>ospf entropy-label)

Full Context

configure router isis entropy-label

configure router ospf entropy-label

Description

Commands in this context configure entropy label capabilities for the routing protocol.

Platforms

All

entropy-label

Syntax

entropy-label {force-disable | enable}

no entropy-label

Context

[Tree] (config>router>isis>segm-rtng entropy-label)

[Tree] (config>router>ospf>segm-rtng entropy-label)

Full Context

configure router isis segment-routing entropy-label

configure router ospf segment-routing entropy-label

Description

This command instructs the system to ignore any received IGP advertisements of entropy label capability relating to remote nodes in the network. It also prevents a user from configuring override-tunnel-elc for the IGP instance.

The no version of this command enables the processing of any received IGP advertisements of entropy label capability.

Default

entropy-label enable

Parameters

force-disable

Forces the system to ignore any received entropy label capability signaled in the IGP.

enable

Enables the system to process any received entropy label capability signaled in the IGP.

Platforms

All

entropy-label-capability

entropy-label-capability

Syntax

[no] entropy-label-capability

Context

[Tree] (config>router>ldp entropy-label-capability)

[Tree] (config>router>rsvp entropy-label-capability)

Full Context

configure router ldp entropy-label-capability

configure router rsvp entropy-label-capability

Description

This command enables or disables ELC for RSV.

If entropy-label-capability is configured, then the system will signal (using the procedures specified in RFC 6790) that it is capable of receiving and processing the entropy label and ELI on incoming packets of RSVP and LDP LSPs.

If no entropy-label-capability is configured, then the system will not signal ELC. If an ELI is exposed on a packet where the tunnel label is popped at the termination of that LSP, and an entropy label is not configured, then the packet will be dropped.

Default

no entropy-label-capability

Platforms

All

entry

entry

Syntax

entry entry-id [create]

no entry entry-id

Context

[Tree] (config>filter>dhcp-filter entry)

[Tree] (config>filter>dhcp6-filter entry)

Full Context

configure filter dhcp-filter entry

configure filter dhcp6-filter entry

Description

This command configures DHCP filter entries.

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

Parameters

entry-id

Specifies the entry ID.

Values

1 to 65535

create

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

Platforms

All

entry

Syntax

entry id [create]

no entry id

Context

[Tree] (config>subscr-mgmt>isa-svc-chain>vas-filter entry)

Full Context

configure subscriber-mgmt isa-service-chaining vas-filter entry

Description

This command configures an entry in the VAS filter.

The no form of this command removes the entry ID from the configuration.

Parameters

id

Specified an entry in the VAS filter.

Values

0 to 4294967295

create

Keyword used to create the entry ID instance. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

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

entry

Syntax

entry key ancp-string customer customer-id multi-service-site customer-site-name ancp-policy policy-name

entry key ancp-string sap sap-id ancp-policy policy-name

no entry key ancp-string customer customer-id multi-service-site customer-site-name

no entry key ancp-string sap sap-id

Context

[Tree] (config>subscr-mgmt>ancp>static-map entry)

Full Context

configure subscriber-mgmt ancp ancp-static-map entry

Description

This command configures an ANCP name. When ANCP is configured to provide rate adaptation without the use of enhanced subscriber management, this command will define how to map an ANCP key (usually the circuit-id of the DSLAM port) to either a SAP and a scheduler name (when a Multi-Service Site (MSS) is not used) or a customer, site and scheduler name when MSS is used.

Different ANCP names may be used with the same SAPs or customer ID/MSS combinations to allow schedulers within the policy to be mapped to the ANCP names. An ANCP string and SAP combination may reference only one ancp-policy. An ANCP string and customer and site-name combination may reference a single ancp-policy.

The no form of this command reverts to the default.

Parameters

ancp-string

Specifies the ASCII representation of the DSLAM circuit-id name, up to 63 characters.

customer-id

Specifies the associated existing customer ID.

Values

1 to 2147483647

customer-site-name

Specifies the associated customer’s configured MSS name, up to 32 characters.

policy-name

Specifies an existing ANCP policy name, up to 32 characters.

sap-id

Specifies the physical port identifier portion of the SAP definition.

Platforms

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

entry

Syntax

entry entry-id [create]

no entry entry-id

Context

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>ingr-ipv6 entry)

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>egr-ip entry)

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>ingr-ip entry)

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>egr-ipv6 entry)

Full Context

configure subscriber-mgmt category-map category exhausted-credit-service-level ingress-ipv6-filter-entries entry

configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ip-filter-entries entry

configure subscriber-mgmt category-map category exhausted-credit-service-level ingress-ip-filter-entries entry

configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ipv6-filter-entries entry

Description

This command configures the IP filter entry.

The no form of this command reverts to the default.

Parameters

entry-id

Specifies the entry ID.

Values

1 to 65535

create

Keyword used to create an entry. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

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

entry

Syntax

entry key sub-ident-string [sub-profile sub-profile-name] [alias sub-alias-string] [sla-profile sla-profile-name] [app-profile app-profile-name]

no entry key sub-ident-string

Context

[Tree] (config>subscr-mgmt>explicit-sub-map entry)

Full Context

configure subscriber-mgmt explicit-subscriber-map entry

Description

This command configures a subscriber identification string.

The no form of this command reverts to the default.

Parameters

sub-ident-string

Specifies the profile string, up to 32 characters.

sub-profile-name

Specifies an existing subscriber profile name, up to 32 characters.

sub-alias-string

Specifies an alias for the subscriber identification string, up to 64 characters.

sla-profile-name

Specifies an existing SLA profile, up to 32 characters.

app-profile-name

Specifies an app profile name up to 256 characters.

Platforms

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

entry

Syntax

entry key app-profile-string app-profile app-profile-name

no entry key app-profile-string

Context

[Tree] (config>subscr-mgmt>sub-ident-pol>app-profile-map entry)

Full Context

configure subscriber-mgmt sub-ident-policy app-profile-map entry

Description

This command configures an application profile string.

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

Parameters

app-profile-string

Specifies the application profile string up to 16 characters.

app-profile-name

Specifies the application profile name up to 32 characters.

Platforms

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

entry

Syntax

entry key sla-profile-string sla-profile sla-profile-name

no entry key sla-profile-string

Context

[Tree] (config>subscr-mgmt>sub-prof>sla-profile-map entry)

[Tree] (config>subscr-mgmt>sub-ident-pol>sla-profile-map entry)

Full Context

configure subscriber-mgmt sub-profile sla-profile-map entry

configure subscriber-mgmt sub-ident-policy sla-profile-map entry

Description

This command configures an SLA profile string. Each subscriber identification string can be provisioned into a subscriber mapping table providing an explicit mapping of the string to a specific subscriber profile. This allows certain subscribers to be directly mapped to the appropriate subscriber profile in the event that the default mappings are not desired for the subscriber.

An explicit mapping of a subscriber identification string to a subscriber profile cannot be defined with the subscriber profile name default. It is possible for the subscriber identification string to be entered in the mapping table without a defined subscriber profile which can result in the explicitly defined subscriber to be associated with the subscriber profile named default.

Explicitly mapping a subscriber identification string to a subscriber profile will cause an existing active subscriber associated with the string to be reassigned to the newly mapped subscriber profile. An explicit mapping overrides all default subscriber profile definitions.

Attempting to delete a subscriber profile that is currently defined as in an explicit subscriber identification string mapping will fail.

The system will fail the removal attempt of an explicit subscriber identification string mapping to a subscriber profile definition when an active subscriber is using the mapping and cannot be reassigned to a defined default non-provisioned subscriber profile.

The no form of this command reverts to the default.

Parameters

sla-profile-string

Identifies the SLA profile string, up to 32 characters.

sla-profile-name

Identifies the SLA profile name, up to 32 characters.

Platforms

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

entry

Syntax

entry key sub-profile-string sub-profile sub-profile-name

no entry key sub-profile-string

Context

[Tree] (config>subscr-mgmt>sub-ident-pol>sub-profile-map entry)

Full Context

configure subscriber-mgmt sub-ident-policy sub-profile-map entry

Description

This command configures a subscriber profile string.

The no form of this command reverts to the default.

Parameters

sub-profile-string

Specifies the subscriber profile string, up to 32 characters.

sub-profile-name

Specifies the subscriber profile name, up to 32 characters.

Platforms

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

entry

Syntax

[no] entry direction direction type type id id

Context

[Tree] (config>subscr-mgmt>accu-stats-policy entry)

Full Context

configure subscriber-mgmt accu-stats-policy entry

Description

This command defines the direction of the policer or queue to the stored and accumulated policy.

The no form of this command removes the entry.

Parameters

direction

Specifies the direction of the queue or policer.

Values

egress, ingress

type

Specifies whether the entry is for a queue or policer.

Values

queue, policer

id

Specifies the queue or policer ID.

Values

1 to 63

Platforms

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

entry

Syntax

entry entry-id [create]

no entry entry-id

Context

[Tree] (config>subscr-mgmt>isa-filter>ipv6 entry)

[Tree] (config>subscr-mgmt>isa-filter entry)

Full Context

configure subscriber-mgmt isa-filter ipv6 entry

configure subscriber-mgmt isa-filter entry

Description

This command creates a new entry for this filter. When processing a packet, entries are matched in order, starting with the lowest entry-id. A maximum of 128 IPv4 and 128 IPv6 DSM filter entries are allowed.

The no form of this command removes the specified entry from the ISA filter.

Parameters

entry-id

Specifies the numeric identifier for the filter entry.

Platforms

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

entry

Syntax

entry [entry] [prefix-string prefix-string] [accounting-server-policy policy-name] [authentication-server-policy policy-name] [suffix-string suffix-string]

no entry [entry]

Context

[Tree] (config>router>radius-proxy>server>attribute-matching entry)

[Tree] (config>service>vprn>radius-proxy>server>attribute-matching entry)

Full Context

configure router radius-proxy server attribute-matching entry

configure service vprn radius-proxy server attribute-matching entry

Description

This command matches the specified prefix or suffix string with the selected accounting server policy or authentication server policy.

Parameters

entry

Specifies an entry ID.

Values

1 to 32

prefix-string

Specifies the prefix string for matching up to 128 characters. If the suffix-string is also used, the combined length cannot exceed 126 characters.

suffix-string

Specifies the suffix string for matching up to 126 characters. If the prefix-string is also used, the combined length cannot exceed 126 characters.

policy-name

Specifies the RADIUS accounting or authentication policy up to 32 characters.

Platforms

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

entry

Syntax

entry entry-id [create]

no entry entry-id

Context

[Tree] (config>service>mrp>mrp-policy entry)

Full Context

configure service mrp mrp-policy entry

Description

This command creates or edits an mrp-policy entry. Multiple entries can be created using unique entry-id numbers within the policy. The implementation exits the policy on the first match found and executes the actions in accordance with the accompanying action command. For this reason, entries must be sequenced correctly from most to least explicit. An entry may not have any match criteria defined (in which case, everything matches) but must have at least the keyword action for it to be considered complete. Entries without the action keyword will be considered incomplete and therefore will be rendered inactive.

The no form of this command removes the specified entry from the mrp-policy. Entries removed from the mrp-policy are immediately removed from all services where the policy is applied.

Parameters

entry-id

An entry-id uniquely identifies a match criteria and the corresponding action. It is recommended that multiple entries be given entry-ids in staggered increments. This allows users to insert a new entry in an existing policy without requiring renumbering of all the existing entries.

Values

1 to 65535

create

Keyword; required when first creating the configuration context. When the context is created, one can navigate into the context without the create keyword.

Platforms

All

entry

Syntax

entry range-entry-id [create]

no entry range-entry-id

Context

[Tree] (config>service>vpls>isid-policy entry)

Full Context

configure service vpls isid-policy entry

Description

This command creates or edits an ISID policy entry. Multiple entries can be created using unique entry-id numbers within the ISID policy.

entry-id — Specifies an entry-id uniquely identifies a ISID range and the corresponding actions. This allows users to insert a new entry in an existing policy without requiring renumbering of all the existing entries.

The following rules govern the usage of multiple entry statements:

  • overlapping values are allowed:

    • isid from 301 to 310

    • isid from 305 to 315

    • isid 316

  • the minimum and maximum values from overlapping ranges are considered and displayed. The above entries will be equivalent with "isid from 301 to 316” statement.

  • there is no consistency check with the content of ISID statements from other entries. The entries will be evaluated in the order of their IDs and the first match will cause the implementation to execute the associated action for that entry.

no isid - removes all the previous statements under one entry.

no isid value | from value to higher-value - removes a specific ISID value or range. Must match a previously used positive statement: for example, if the command "isid 16 to 100” was used using "no isid 16 to 50”, it will not work but "no isid 16 to 100 will be successful.

Values 1 to 65535

Default

no entry

Parameters

range-entry-id

Specifies the ID of the ISID policy to be created or edited

Values

1 to 8191

create

Required when first creating the configuration context. Once the context is created, one can navigate into the context without the create keyword.

Platforms

All

entry

Syntax

entry entry-id [name entry-name]

no entry entry-id

Context

[Tree] (config>service>vprn>log>filter entry)

Full Context

configure service vprn log filter entry

Description

This command is used to create or edit an event filter entry. Multiple entries may be created using unique entry-id values. The SR OS implementation exits the filter on the first match found and executes the action in accordance with the action command.

Comparisons are performed in an ascending entry ID order. When entries are created, they should be arranged sequentially from the most explicit entry to the least explicit. Matching ceases when a packet matches an entry. The entry action is performed on the packet, either drop or forward. To be considered a match, the packet must meet all the conditions defined in the entry.

An entry may not have any match criteria defined (in which case, everything matches) but must have at least the keyword action for it to be considered complete. Entries without the action keyword will be considered incomplete and are rendered inactive.

By default, no filter entries are defined. Entries must be explicitly configured.

The no form of this command removes the specified entry from the event filter. Entries removed from the event filter are immediately removed from all log-id’s where the filter is applied.

Default

No event filter entries are defined. An entry must be explicitly configured.

Parameters

entry-id

The entry ID uniquely identifies a set of match criteria corresponding action within a filter. Entry ID values should be configured in staggered increments so you can insert a new entry in an existing policy without renumbering the existing entries.

Values

1 to 999

name entry-name

Configures an optional entry name for the event filter, up to 64 characters, that can be used to refer to the entry after it is created.

Platforms

All

entry

Syntax

entry entry-id [create]

no entry entry-id

Context

[Tree] (config>app-assure>group>policy>app-filter entry)

Full Context

configure application-assurance group policy app-filter entry

Description

This command creates an application filter entry.

App filter entries are an ordered list, the lowest numerical entry that matches the flow defines the application for that flow.

An application filter entry or entries configures match attributes of an application.

The no form of this command deletes the specified application filter entry.

Parameters

entry-id

Specifies an integer that identifies an app-filter entry.

Values

1 to 65535

create

Keyword used to create the entry.

Platforms

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

entry

Syntax

entry entry-id [create]

no entry entry-id

Context

[Tree] (config>app-assure>group>policy>aqp entry)

Full Context

configure application-assurance group policy app-qos-policy entry

Description

This command creates an application QoS policy entry. A flow that matches multiple Application QoS policies (AQP) entries will have multiple AQP entries actions applied. When a conflict occurs for two or more actions, the action from the AQP entry with the lowest numerical value takes precedence.

The no form of this command deletes the specified application QoS policy entry.

Parameters

entry-id

An integer identifying the AQP entry.

Values

1 to 65535

create

Mandatory keyword creates the entry. The create keyword requirement can be enabled/disabled in the environment>create context.

Platforms

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

entry

Syntax

entry entry-id [create]

no entry entry-id

Context

[Tree] (config>app-assure>group>sess-fltr entry)

Full Context

configure application-assurance group session-filter entry

Description

This command configures a particular Application-Assurance session filter match entry. Every session filter can have zero or more session filter match entries. An application filter entry or entries configures match attributes of an application.

The no form of this command deletes the specified entry.

Parameters

entry-id

Specifies an integer that identifies the entry.

Values

1 to 65535

create

Keyword used to create the entry.

Platforms

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

entry

Syntax

entry entry-id direction direction [create]

no entry entry-id direction direction

Context

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>msg entry)

Full Context

configure application-assurance group statistics threshold-crossing-alert gtp-filter message-type entry

Description

This command configures a TCA for the counter capturing hits for the specified GTP filter entry. A GTP filter entry TCA can be created for traffic generated from the subscriber side of AA (from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating a default action TCA.

Parameters

entry-id

Specifies the GTP filter message-type entry identifier.

Values

1 to 255

direction

Specifies the traffic direction.

Values

from-sub, to-sub

create

Keyword used to create the TCA.

Platforms

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

entry

Syntax

entry entry-id direction direction [create]

no entry entry-id direction direction

Context

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>msg-gtpv2 entry)

Full Context

configure application-assurance group statistics threshold-crossing-alert gtp-filter message-type-gtpv2 entry

Description

This command configures a TCA for the counter capturing hits for the specified GTPv2 message type filter entry. A GTP filter entry TCA can be created for traffic generated from the subscriber side of AA (from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating an entry TCA.

Parameters

entry-id

Specifies the GTP filter message-type-gtpv2 entry identifier.

Values

516 to 770

direction

Specifies the traffic direction.

Values

from-sub, to-sub

create

Keyword used to create the TCA.

Platforms

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

entry

Syntax

entry entry-id direction direction [create]

no entry entry-id direction direction

Context

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>imsi-apn entry)

Full Context

configure application-assurance group statistics threshold-crossing-alert gtp-filter imsi-apn entry

Description

This command configures a TCA for the counter capturing hits for the specified IMSI-APN filter entry. A GTP IMSI-APN filter entry TCA can be created for traffic generated from the subscriber side of AA (from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating an entry TCA.

Parameters

entry-id

Specifies the identifier for the IMSI-APN filter entry.

Values

1031 to 2030

direction

Specifies the traffic direction.

Values

from-sub, to-sub

create

Keyword used to create the TCA.

entry

Syntax

entry entry-id direction direction [create]

no entry entry-id direction direction

Context

[Tree] (config>app-assure>group>statistics>tca>sctp-fltr>ppid entry)

Full Context

configure application-assurance group statistics threshold-crossing-alert sctp-filter ppid entry

Description

This command configures a TCA for the counter capturing hits for the specified SCTP filter PPID entry. An SCTP filter entry TCA can be created for traffic generated from the subscriber side of AA (from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating a TCA.

Parameters

entry-id

Specifies the SCTP filter PPID entry identifier.

Values

1 to 255

direction

Specifies the traffic direction.

Values

from-sub, to-sub