r Commands

radius

radius

Syntax

radius type direction {ingress | egress} script script

no radius type direction {ingress | egress}

Context

[Tree] (config>python>py-policy radius)

Full Context

configure python python-policy radius

Description

This command specifies the Python script for the specified RADIUS packet type in the specified direction.

Multiple radius command configurations are allowed in the same Python policy.

The no form of this command reverts to the default.

Parameters

type

Specifies the message type of the event.

Values

access-request, access-accept, access-reject, accounting-request, accounting-response, access-challenge, disconnect-request, change-of-authorization-request

direction {ingress | egress}

Specifies whether the event is incoming or outgoing.

script

Specifies the name of the Python script, up to 32 characters, that is used to handle the specified message.

Platforms

All

radius

Syntax

[no] radius

Context

[Tree] (debug>router radius)

Full Context

debug router radius

Description

This command enables the debug router RADIUS context.

Platforms

All

radius

Syntax

radius [create]

no radius

Context

[Tree] (config>service>vprn>aaa>remote-servers radius)

Full Context

configure service vprn aaa remote-servers radius

Description

This command creates the context to configure RADIUS authentication on the VPRN.

Implement redundancy by configuring multiple server addresses for each VPRN.

The no form of this command removes the RADIUS configuration.

Parameters

create

Keyword used to create the RADIUS context.

Platforms

All

radius

Syntax

radius

Context

[Tree] (config>app-assure>group>transit-ip-policy radius)

Full Context

configure application-assurance group transit-ip-policy radius

Description

This command enables dynamic RADIUS-based management of transit aa-subs for the transit-ip-policy. This is mutually exclusive to other types management of transit subs for a specific transit-ip-policy.

Platforms

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

radius

Syntax

radius

Context

[Tree] (config>li radius)

Full Context

configure li radius

Description

This command configures RADIUS for Lawful Intercept.

Platforms

All

radius

Syntax

radius [detail] [hex]

no radius

Context

[Tree] (debug radius)

Full Context

debug radius

Description

This command enables debugging for RADIUS connections.

The no form of the command disables the debug output.

Parameters

detail

Displays detailed output.

hex

Displays the packet dump in hex format.

Platforms

All

radius

Syntax

[no] radius

Context

[Tree] (config>system>security radius)

Full Context

configure system security radius

Description

This command creates the context to configure RADIUS authentication on the router.

Implement redundancy by configuring multiple server addresses for each router.

The no form of this command removes the RADIUS configuration.

Platforms

All

radius-accounting

radius-accounting

Syntax

radius-accounting

Context

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

Full Context

configure subscriber-mgmt sub-profile radius-accounting

Description

Commands in this context configure RADIUS accounting subscriber profile parameters.

Platforms

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

radius-accounting-policy

radius-accounting-policy

Syntax

radius-accounting-policy policy-name

no radius-accounting-policy

Context

[Tree] (config>router>l2tp radius-accounting-policy)

[Tree] (config>service>vprn>l2tp radius-accounting-policy)

[Tree] (config>service>vprn>l2tp>group>tunnel radius-accounting-policy)

[Tree] (config>service>vprn>l2tp>group radius-accounting-policy)

[Tree] (config>service>vprn>if>sap>ipsec-gw radius-accounting-policy)

[Tree] (config>service>ies>if>sap>ipsec-gw radius-accounting-policy)

[Tree] (config>router>l2tp>group>tunnel radius-accounting-policy)

[Tree] (config>router>l2tp>group radius-accounting-policy)

Full Context

configure router l2tp radius-accounting-policy

configure service vprn l2tp radius-accounting-policy

configure service vprn l2tp group tunnel radius-accounting-policy

configure service vprn l2tp group radius-accounting-policy

configure service vprn interface sap ipsec-gw radius-accounting-policy

configure service ies interface sap ipsec-gw radius-accounting-policy

configure router l2tp group tunnel radius-accounting-policy

configure router l2tp group radius-accounting-policy

Description

This command configures the RADIUS accounting policy.

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

Default

no radius-accounting-policy

Parameters

policy-name

Specifies the policy name, up to 32 characters.

Platforms

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

  • configure router l2tp group tunnel radius-accounting-policy
  • configure service vprn l2tp radius-accounting-policy
  • configure service vprn l2tp group tunnel radius-accounting-policy
  • configure router l2tp group radius-accounting-policy
  • configure router l2tp radius-accounting-policy
  • configure service vprn l2tp group radius-accounting-policy

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

  • configure service ies interface sap ipsec-gw radius-accounting-policy
  • configure service vprn interface sap ipsec-gw radius-accounting-policy

radius-accounting-policy

Syntax

radius-accounting-policy name [create]

no radius-accounting-policy

Context

[Tree] (config>subscr-mgmt radius-accounting-policy)

Full Context

configure subscriber-mgmt radius-accounting-policy

Description

This command specifies a subscriber RADIUS based accounting policy.

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

Parameters

name

The name of the policy. The string is case-sensitive and limited to 32 ASCII 7-bit printable characters with no spaces.

create

Keyword used to create a RADIUS accounting policy instance. The create keyword requirement can be enabled/disabled in the environment>create context.

Platforms

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

radius-accounting-policy

Syntax

radius-accounting-policy nat-accounting-policy

no radius-accounting-policy

Context

[Tree] (config>isa>wlan-gw-group>nat radius-accounting-policy)

Full Context

configure isa wlan-gw-group nat radius-accounting-policy

Description

This command configures the RADIUS accounting policy to use for each MDA in this ISA group.

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

Parameters

nat-accounting-policy

Specifies the RADIUS accounting policy up to 32 characters.

Platforms

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

radius-accounting-policy

Syntax

radius-accounting-policy rad-acct-plcy-name

no radius-accounting-policy

Context

[Tree] (config>app-assure>group>statistics>aa-sub radius-accounting-policy)

Full Context

configure application-assurance group statistics aa-sub radius-accounting-policy

Description

This command specifies an existing subscriber RADIUS based accounting policy to use for AA. RADIUS Accounting policies are configured in the config>app-assure>radius-accounting-policy context.

Default

no radius-accounting-policy

Parameters

rad-acct-plcy-name

Specifies the name of the policy. The string is case sensitive and limited to 32 ASCII 7-bit printable characters with no spaces.

Platforms

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

radius-accounting-policy

Syntax

radius-accounting-policy rad-acct-plcy-name [create]

no radius-accounting-policy rad-acct-plcy-name

Context

[Tree] (config>app-assure radius-accounting-policy)

Full Context

configure application-assurance radius-accounting-policy

Description

This command specifies an existing subscriber RADIUS-based accounting policy to use for AA. RADIUS accounting policies are configured in the config>app-assure>radius-accounting-policy context.

Default

no radius-accounting-policy

Parameters

rad-acct-plcy-name

Specifies the policy name. The string is case sensitive and limited to 32 ASCII 7-bit printable characters with no spaces.

create

Keyword used to create the policy.

Platforms

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

radius-accounting-policy

Syntax

radius-accounting-policy name [create]

no radius-accounting-policy name

Context

[Tree] (config>ipsec radius-accounting-policy)

Full Context

configure ipsec radius-accounting-policy

Description

This command specifies an existing RADIUS accounting policy to use to collect accounting statistics on this subscriber profile by RADIUS. This command is used independently of the collect-stats command.

Parameters

name

Specifies an existing RADIUS based accounting policy.

Platforms

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

radius-accounting-policy

Syntax

radius-accounting-policy nat-accounting-policy

no radius-accounting-policy

Context

[Tree] (config>isa>nat-group radius-accounting-policy)

Full Context

configure isa nat-group radius-accounting-policy

Description

This command specifies the RADIUS accounting policy to use for each MDA in this ISA group.

The no form of the command removes the policy ID from the configuration.

Default

no radius-accounting-policy

Parameters

nat-accounting-policy

Reference to the nat-accounting-policy which defines:

Source IP addresses that are assigned to BB-ISA cards.

Parameters related to RADIUS server itself.

List of RADIUS attributes that are included in accounting messages.

Platforms

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

radius-accounting-server

radius-accounting-server

Syntax

radius-accounting-server

Context

[Tree] (config>aaa>l2tp-acct-plcy>include-radius-attribute radius-accounting-server)

Full Context

configure aaa l2tp-accounting-policy include-radius-attribute radius-accounting-server

Description

Commands in this context configure RADIUS accounting server attributes under a specific session authentication policy.

Platforms

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

radius-accounting-server

Syntax

radius-accounting-server

Context

[Tree] (config>app-assure>rad-acct-plcy radius-accounting-server)

[Tree] (config>aaa>l2tp-acct-plcy radius-accounting-server)

Full Context

configure application-assurance radius-accounting-policy radius-accounting-server

configure aaa l2tp-accounting-policy radius-accounting-server

Description

This command creates the context for defining RADIUS accounting server attributes under a specific session authentication policy.

Platforms

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

  • configure application-assurance radius-accounting-policy radius-accounting-server

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

  • configure aaa l2tp-accounting-policy radius-accounting-server

radius-attr

radius-attr

Syntax

radius-attr type attribute-type [extended-type attribute-ext-type] [transaction]

radius-attr type attribute-type [transaction] {address | hex | integer | string} value attribute-value

radius-attr vendor vendor-id type attribute-type [extended-type attribute-ext-type] [transaction] [encoding encoding-type]

radius-attr vendor vendor-id type attribute-type [extended-type attribute-ext-type] [transaction] [encoding encoding-type] {address | hex | integer | string} value attribute-value

no radius-attr type attribute-type [extended-type attribute-ext-type]

no radius-attr type attribute-type [extended-type attribute-ext-type] {address | hex | integer | string} value attribute-value

no radius-attr vendor vendor-id type attribute-type [extended-type attribute-ext-type]

no radius-attr vendor vendor-id type attribute-type [extended-type attribute-ext-type] {address | hex | integer | string} [value] attribute-value

Context

[Tree] (debug>router>radius radius-attr)

Full Context

debug router radius radius-attr

Description

This command specifies the RADIUS attribute filter of command debug router radius.

Parameters

attribute-type

Specifies the RADIUS attribute type.

Values

1 to 255

attribute-ext-type

Specifies the RADIUS attribute extended type (RFC 6929).

Values

1 to 255

address

Specifies the value is a IPv4 or IPv6 address/prefix/subnet.

string

Specifies the value is a ASCII string.

integer

Specifies the value is a integer.

hex

Specifies the value is a binary string in hex format, such as "\0xAB01FE”.

attribute-value

Specifies the value of the RADIUS attribute.

Values

address

<ipv4-address> | <ipv6-address> | <ipv6-prefix/prefix-length>

ipv4-address

a.b.c.d

ipv6-address

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

ipv6-prefix

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

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

x - [0 to FFFF]H

d - [0 to 255]D

ipv6-prefix-length [0 to 128]

hex

[0x0 to 0xFFFFFFFF (up to 506 hex nibbles)]

integer

[0 to 4294967295]

string

ascii-string (up to 253 characters)

transaction

Specifies that the system outputs both request and response packets in the same session even if the response packet does not include the filter attribute.

vendor-id

Specifies the vendor ID for the vendor specific attribute.

Values

0 to 16777215

encoding-type

Specifies the size of the vendor-type and vendor-length in bytes. It is a two digitals string: "xy”, x is the size of vendor-type, range from 1 to 4; y is the size of vendor-length, range from 0 to 2; it is "11” by default.

Values

type-size:1 to 4, length-size: 0 to 2

Platforms

All

radius-auth-policy

radius-auth-policy

Syntax

radius-auth-policy radius-authentication-policy-name

no radius-auth-policy

Context

[Tree] (config>subscr-mgmt>gtp>apn-policy>apn radius-auth-policy)

Full Context

configure subscriber-mgmt gtp apn-policy apn radius-auth-policy

Description

This command configures the RADIUS authentication policy with which the GTP connection is authenticated.

The no form of this command removes the authentication policy. Only new session setups are affected.

Default

no radius-auth-policy

Parameters

radius-authentication-policy-name

Specifies the name of the authentication policy to be used, up to 32 characters.

Platforms

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

radius-authentication

radius-authentication

Syntax

radius-authentication

Context

[Tree] (config>subscr-mgmt>vrgw>brg>brg-profile radius-authentication)

Full Context

configure subscriber-mgmt vrgw brg brg-profile radius-authentication

Description

Commands in this context configure parameters related to RADIUS authentication performed for the BRG.

Platforms

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

radius-authentication-policy

radius-authentication-policy

Syntax

radius-authentication-policy name

no radius-authentication-policy

Context

[Tree] (config>service>vprn>if>sap>ipsec-gw radius-authentication-policy)

[Tree] (config>service>ies>if>sap>ipsec-gw radius-authentication-policy)

Full Context

configure service vprn interface sap ipsec-gw radius-authentication-policy

configure service ies interface sap ipsec-gw radius-authentication-policy

Description

This command configures the policy used for the IKEv2 remote-access tunnels terminated on the IPsec gateway. The radius-authentication-policy is defined under config>ipsec context.

Parameters

name

Specifies the name of an existing RADIUS authentication policy.

Platforms

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

radius-authentication-policy

Syntax

radius-authentication-policy name [create]

no radius-authentication-policy name

Context

[Tree] (config>ipsec radius-authentication-policy)

Full Context

configure ipsec radius-authentication-policy

Description

This command specifies the RADIUS authentication policy associated with this IPsec gateway.

Parameters

name

Specifies an existing RADIUS authentication policy.

Platforms

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

radius-authentication-server

radius-authentication-server

Syntax

radius-authentication-server

Context

[Tree] (config>subscr-mgmt>auth-plcy radius-authentication-server)

Full Context

configure subscriber-mgmt authentication-policy radius-authentication-server

Description

Commands in this context define RADIUS authentication server attributes under a specific session authentication policy.

Platforms

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

radius-coa-port

radius-coa-port

Syntax

radius-coa-port {port-number}

no radius-coa-port

Context

[Tree] (config>aaa radius-coa-port)

Full Context

configure aaa radius-coa-port

Description

This command configures the system-wide UDP port number that RADIUS is listening on for CoA and Disconnect messages.

The no form of this command reverts to the default.

Default

radius-coa-port 3799

Parameters

port-number

Specifies the UDP port number for RADIUS CoA and disconnect messages.

Values

1647, 1700, 1812, 3799

Platforms

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

radius-plcy

radius-plcy

Syntax

radius-plcy name

no radius-plcy

Context

[Tree] (config>port>ethernet>dot1x radius-plcy)

Full Context

configure port ethernet dot1x radius-plcy

Description

This command references the RADIUS policy to be used for 802.1x authentication. An 802.1x RADIUS policy must be configured (config>system>security>dot1x) before it is associated to a port. If the RADIUS policy ID does not exist, an error is returned. Only one 802.1x RADIUS policy can be associated with a port at a time.

The no form of this command removes the RADIUS policy association.

Default

no radius-plcy

Parameters

name

Specifies an existing 802.1x RADIUS policy name, up to 32 characters.

Platforms

All

radius-plcy

Syntax

radius-plcy name [create]

Context

[Tree] (config>system>security>dot1x radius-plcy)

Full Context

configure system security dot1x radius-plcy

Description

This command creates the context to configure RADIUS server parameters for 802.1x network access control on the router.

Note:

The RADIUS server configured under the config>system>security>dot1x>radius-plcy context authenticates clients who get access to the data plane of the router as opposed to the RADIUS server configured under the config>system>radius context which authenticates CLI login users who get access to the management plane of the router.

The no form of this command removes the RADIUS server configuration for 802.1x.

Platforms

All

radius-proxy

radius-proxy

Syntax

radius-proxy

Context

[Tree] (config>router radius-proxy)

[Tree] (config>service>vprn radius-proxy)

Full Context

configure router radius-proxy

configure service vprn radius-proxy

Description

This command context to configure RADIUS proxy parameters.

Platforms

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

radius-proxy-cache

radius-proxy-cache

Syntax

radius-proxy-cache router router-instance server server-name

no radius-proxy-cache

Context

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>ranges>range>track-mobility radius-proxy-cache)

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw>ranges>range>track-mobility radius-proxy-cache)

Full Context

configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range track-mobility radius-proxy-cache

configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range track-mobility radius-proxy-cache

Description

This command specifies the RADIUS-proxy server to allow subscribers created via data-triggered authentication to create an entry. This RADIUS proxy cache entry allows efficient handling of UE mobility.

Parameters

router-instance

Specifies the router instance.

Values

router-name

Base

service-id

1 to 2147483647

server-name

Specifies the server name up to 32 characters.

Platforms

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

radius-proxy-server

radius-proxy-server

Syntax

[no] radius-proxy-server router router-instance name server-name

Context

[Tree] (config>subscr-mgmt>vrgw>brg>brg-profile radius-proxy-server)

Full Context

configure subscriber-mgmt vrgw brg brg-profile radius-proxy-server

Description

This command enables BRG processing on the specified RADIUS proxy server. Whenever an Access-Accept message is received with the attribute Alc-BRG-Id present, this triggers the creation of a BRG. The BRG uses the brg-profile specified in the Access-Accept message or fall back to this BRG profile. When the specified radius-proxy-server has a cache enabled, no cache entries are created for a transaction identified as BRG. A RADIUS proxy server can only be listed in one BRG profile.

This command can be executed multiple times.

The no form of this command removes BRG processing for the specified radius-proxy server.

Parameters

router-instance

Specifies the ID of the VRF where the proxy server is located.

server-name

Specifies the name of the RADIUS proxy server.

Platforms

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

radius-proxy-server

Syntax

radius-proxy-server router router-instance name server-name

no radius-proxy-server

Context

[Tree] (config>router>nat>inside>subscriber-identification radius-proxy-server)

[Tree] (config>service>vprn>nat>inside>subscriber-identification radius-proxy-server)

Full Context

configure router nat inside subscriber-identification radius-proxy-server

configure service vprn nat inside subscriber-identification radius-proxy-server

Description

This command configures RADIUS proxy server parameters. This is a reference to a RADIUS accounting proxy server in Subscriber Aware Large Scale NAT44 application. RADIUS accounting proxy server will cache attributes related to a BNG subscriber as they are received in standard accounting messages (RFC 2866). Radius accounting proxy server can be configured in any routing instance within 7750 SR.

Parameters

router router-instance

Specifies the routing instance in which the RADIUS accounting proxy is configured.

name server-name

Specifies the name reference to the RADIUS accounting proxy server that is instantiated in 7750 SR.

Platforms

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

radius-script-policy

radius-script-policy

Syntax

radius-script-policy policy-name [create]

no radius-script-policy policy-name

Context

[Tree] (config>aaa radius-script-policy)

Full Context

configure aaa radius-script-policy

Description

This command configures a RADIUS script policy.

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

Parameters

policy-name

Configures Python scripts to modify RADIUS messages.

create

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

Platforms

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

radius-server

radius-server

Syntax

radius-server

Context

[Tree] (config>router radius-server)

[Tree] (config>service>vprn radius-server)

Full Context

configure router radius-server

configure service vprn radius-server

Description

Commands in this context configure the RADIUS server under router or VPRN service.

Platforms

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

radius-server-policy

radius-server-policy

Syntax

radius-server-policy policy-name

no radius-server-policy

Context

[Tree] (config>aaa>l2tp-acct-plcy radius-server-policy)

Full Context

configure aaa l2tp-accounting-policy radius-server-policy

Description

This command references an existing radius-server-policy (available under the config>aaa context) for use in subscriber management authentication and accounting.

When configured in an authentication-policy, following CLI commands are ignored in the policy to avoid conflicts:

  • all commands in the radius-authentication-server context

  • accept-authorization-change

  • coa-script-policy

  • accept-script-policy

  • request-script-policy

When configured in a radius-accounting-policy, following CLI commands are ignored in the policy to avoid conflicts:

  • all commands in the radius-accounting-server context

  • acct-request-script-policy

The no form of this command removes the radius-server-policy reference from the configuration.

Default

no radius-server-policy

Parameters

policy-name

Specifies the RADIUS server policy.

Platforms

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

radius-server-policy

Syntax

radius-server-policy policy-name [create]

no radius-server-policy policy-name

Context

[Tree] (config>aaa radius-server-policy)

Full Context

configure aaa radius-server-policy

Description

This command creates a radius-server-policy.

A RADIUS server policy can be used in

  • radius-proxy, for application like EAP authentication for WIFI access

  • authentication policy, for Enhanced Subscriber Management authentication

  • RADIUS accounting policy, for Enhanced Subscriber Management accounting

  • dynamic data service RADIUS accounting

  • AAA route downloader

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

Parameters

policy-name

Specifies the name of the radius-server-policy up to 32 characters.

create

Keyword used to create a radius-server-policy name. The create keyword requirement can be enabled/disabled in the environment>create context.

Platforms

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

radius-server-policy

Syntax

radius-server-policy radius-server-policy-name

no radius-server-policy

Context

[Tree] (config>subscr-mgmt>acct-plcy radius-server-policy)

[Tree] (config>subscr-mgmt>auth-plcy radius-server-policy)

Full Context

configure subscriber-mgmt radius-accounting-policy radius-server-policy

configure subscriber-mgmt authentication-policy radius-server-policy

Description

This command references an existing radius-server-policy (available under the config>aaa context) for use in subscriber management authentication and accounting.

When configured in an authentication-policy, following CLI commands are ignored in the policy to avoid conflicts:

  • all commands in the radius-authentication-server context

  • accept-authorization-change

  • coa-script-policy

  • accept-script-policy

  • request-script-policy

When configured in a radius-accounting-policy, following CLI commands are ignored in the policy to avoid conflicts:

  • all commands in the radius-accounting-server context

  • acct-request-script-policy

The no form of this command removes the radius-server-policy reference from the configuration

Parameters

radius-server-policy-name

Specifies the RADIUS server policy.

Platforms

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

radius-server-policy

Syntax

radius-server-policy policy-name

no radius-server-policy

Context

[Tree] (config>aaa>route-downloader radius-server-policy)

Full Context

configure aaa route-downloader radius-server-policy

Description

This command references an existing radius-server-policy (available under the config>aaa context). The server (or servers) referenced by the policy is used as the targets for the access-request message.

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

Parameters

policy-name

Specifies the RADIUS server policy.

Platforms

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

radius-server-policy

Syntax

radius-server-policy policy-name

no radius-server-policy

Context

[Tree] (config>subscr-mgmt>vrgw>brg>brg-profile>radius-authentication radius-server-policy)

Full Context

configure subscriber-mgmt vrgw brg brg-profile radius-authentication radius-server-policy

Description

This command is used if the BRG must be authenticated to the controller/PCMP by the vRGW. This is required if the BRG does not perform RADIUS authentication via the proxy server. The vRGW originates a valid Access Request using the BRG ID as the username.

The no form of this command removes the radius-server-policy from the configuration. Setup of an unauthenticated BRG fails.

Parameters

policy-name

Specifies the RADIUS server policy, up to 32 characters, to be applied to this subscriber authentication policy.

Platforms

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

radius-server-policy

Syntax

radius-server-policy radius-server-policy-name

no radius-server-policy

Context

[Tree] (config>ipsec>rad-acct-plcy radius-server-policy)

[Tree] (config>ipsec>rad-auth-plcy radius-server-policy)

Full Context

configure ipsec radius-accounting-policy radius-server-policy

configure ipsec radius-authentication-policy radius-server-policy

Description

This command references an existing radius-server-policy (available under the config>aaa context) for use in subscriber management authentication and accounting.

When configured in an authentication-policy, following CLI commands are ignored in the policy to avoid conflicts:

  • all commands in the radius-authentication-server context

  • accept-authorization-change

  • coa-script-policy

  • accept-script-policy

  • request-script-policy

When configured in a radius-accounting-policy, following CLI commands are ignored in the policy to avoid conflicts:

  • all commands in the radius-accounting-server context

  • acct-request-script-policy

The no form of this command removes the radius-server-policy reference from the configuration.

Default

no radius-server-policy

Parameters

radius-server-policy-name

Specifies the RADIUS server policy.

Platforms

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

radius-server-policy

Syntax

radius-server-policy policy-name

no radius-server-policy

Context

[Tree] (config>subscr-mgmt>vrgw>brg>brg-profile radius-server-policy)

Full Context

configure subscriber-mgmt vrgw brg brg-profile radius-server-policy

Description

This command allows the vRGW to authenticate on the BRG's behalf. This is required if the BRG does not perform authentication itself using the radius proxy. The vRGW originates a valid Access Request using the BRG ID as a username.

The no form of this command removes the RADIUS server policy from the configuration. Setting up of an unauthenticated BRG will now fail.

Default

no radius-server-policy

Parameters

policy-name

Specifies the RADIUS server policy, up to 32 characters, to apply in this subscriber authentication policy.

Platforms

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

radius-server-policy

Syntax

radius-server-policy policy-name

radius-server-policy auth policy-name-auth

radius-server-policy acct policy-name-acct

radius-server-policy auth policy-name-auth acct policy-name-acct

no radius-server-policy

Context

[Tree] (config>port>ethernet>dot1x radius-server-policy)

Full Context

configure port ethernet dot1x radius-server-policy

Description

This command configures the RADIUS policy with IPv4/IPv6 in base routing and VPRN. The current RADIUS policy can be found under the configure>aaa>radius-server-policy context.

The RADIUS servers for the policy are configured under configure>router>radius-server or configure>service>vprn>radius-server context.

The RADIUS policy is assigned under dot1x using the radius-server-policy command. When the RADIUS policy is configured, both authorization and accounting are performed via the same server.

The no form of this command allows authorization and accounting via different servers.

Default

no radius-server-policy

Parameters

policy-name

Specifies the RADIUS server policy, up to 32 characters.

The policy is configured under configure>aaa>radius-server-policy. When the policy name is configured, both authorization and accounting are done via this server.

policy-name-auth

Specifies the AAA RADIUS server policy for dot1x authorization only; up to 32 characters.

The policy is configured under configure>aaa>radius-server-policy. The policy name authorization is used if the user needs a different server for authorization.

policy-name-acct

Specifies the AAA RADIUS server policy for dot1x accounting only; up to 32 characters.

The policy is configured under configure>aaa>radius-server-policy. The policy name accounting is used if the user needs a different server for accounting.

Platforms

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

radius-session-timeout

radius-session-timeout

Syntax

radius-session-timeout {backwards-compatible | ignore | absolute}

no radius-session-timeout

Context

[Tree] (config>service>ies>sub-if>grp-if>ipoe-session radius-session-timeout)

[Tree] (config>service>vprn>sub-if>grp-if>ipoe-session radius-session-timeout)

Full Context

configure service ies subscriber-interface group-interface ipoe-session radius-session-timeout

configure service vprn subscriber-interface group-interface ipoe-session radius-session-timeout

Description

This command specifies how to interpret the session-timeout coming from a RADIUS VSA in an Access-Accept or CoA message.

The value of this command can only be changed on wlan-gw group interfaces.

The no form of this command to resets the default behavior.

Default

radius-session-timeout absolute (backward compatible on wlan-gw group interfaces)

Parameters

backwards-compatible

Specifies that the VSA is interpreted as an IPv4 lease time if the Alc-Lease-Time attribute is not present and an absolute timeout otherwise. The VSA is treated the same as for non-ipoe session DHCP hosts.

ignore

Specifies that the VSA meaning is irrelevant for IPoE session and should be ignored.

absolute

Specifies that the VSA would be treated as a timeout starting from the moment the IPoE session is set up.

Platforms

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

radius-user-name

radius-user-name

Syntax

[no] radius-user-name

Context

[Tree] (config>subscr-mgmt>diam-appl-plcy>gy>include-avp radius-user-name)

Full Context

configure subscriber-mgmt diameter-application-policy gy include-avp radius-user-name

Description

This command includes the RADIUS user name AVP in the Diameter Gy messages.

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

Platforms

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

rai

rai

Syntax

[no] rai

Context

[Tree] (config>subscr-mgmt>diam-appl-plcy>gx>include-avp rai)

Full Context

configure subscriber-mgmt diameter-application-policy gx include-avp rai

Description

This command enables the inclusion of the RAI AVP as signaled in the incoming GTP setup message.

The no form of this command disables the inclusion of the AVP.

Platforms

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

range

range

Syntax

range start-entry queue-id count count

no range

Context

[Tree] (config>qos>sap-egress>dynamic-queue range)

Full Context

configure qos sap-egress dynamic-queue range

Description

This command configures the range of IDs from which the system allocates dynamic queues. You cannot use the same IDs for static queues within the same policy.

Default

no range

Parameters

queue-id

Specifies the ID of the queue for the start entry of the range.

Values

2 to 8

count

Specifies the count for the range.

Values

1 to 7

Platforms

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

range

Syntax

range encap-range sync-tag sync-tag

no range encap-range

Context

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

Full Context

configure redundancy multi-chassis peer sync port range

Description

This command configures a range of encapsulation values.

Parameters

encap-range

Specifies a range of encapsulation values on a port to be synchronized with a multi-chassis peer.

Values

Dot1Q

start-tag-end-tag

start-tag

0 to 4094

end-tag

0 to 4094

QinQ

qtag1.start-qtag2-qtag1.end-qtag2-start-qtag1.*-end-qtag1.*

qtag1

1 to 4094

start-qtag1

1 to 4094

en-qtag1

1 to 4094

start-qtag2

0 to 4094

end-qtag2

0 to 4094

sync-tag

Specifies a synchronization tag up to 32 characters to be used while synchronizing this encapsulation value range with the multi-chassis peer.

Platforms

All

range

Syntax

range vc-id-range [sync-tag sync-tag]

no range vc-id-range

Context

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

Full Context

configure redundancy multi-chassis peer sync sdp range

Description

This command specifies a range of VC IDs for manually configured spoke SDPs to be synchronized with the multi-chassis peer and a synchronization tag to be used while synchronizing each range with the multi-chassis peer. The range command and the configuration of a synchronization tag on the parent sdp command are mutually exclusive.

To synchronize a single spoke SDP, the start-vc-id should be the same as the end-vc-id. If the configured end-vc-id is lower than the start-vc-id, the range command fails.

The synchronization tag can be changed by entering the same command with a different synchronization tag. Changing the synchronization tag removes all states relating to the previous synchronization tag for the SDP and a new synchronization tag state is created.

Multiple range commands can be configured, however, overlapping ranges for the same SDP (sdp-id) are not permitted.

The synchronization of PIM snooping is only supported for manually configured spoke SDPs but is not supported for spoke SDPs configured within an endpoint. See PIM Snooping for IPv4 Synchronization for service support.

The synchronization of the PIM snooping state is not supported on any of the following when used with the configured sdp-id:

  • mesh SDPs

  • spoke SDPs in non-VPLS services

  • BGP-AD/BGP-VPLS (FEC 129) spoke SDPs

  • spoke SDPs configured in endpoints

  • pseudowire SAPs

  • ESM-over-MPLS pseudowires

Non-existent spoke SDPs may be specified. If these spoke SDPs are created at a later time, then all states on the spoke SDPs are synchronized according to the synchronization tag and the synchronization protocols enabled. The sync-tag can be changed by entering the same command with a different sync-tag value. If the synchronization tag is changed, then all states for the previous sync-tag are removed for the SDP configured in the command and the state is then built for the new synchronization tag.

Parameters

vc-id-range

Specifies a non-overlapping range of VC IDs for the spoke SDPs of the SDP to be synchronized with the multi-chassis peer.

Values

start-vc-id-end-vc-id

start-vc-id: 1 to 4294967295

end-vc-id: 1 to 4294967295

sync-tag

Specifies a synchronization tag, up to 32 characters, to be used when synchronizing with the multi-chassis peer.

Platforms

All

range

Syntax

[no] range vlan-range

Context

[Tree] (config>redundancy>mc>peer>mcr>ring>path-b range)

[Tree] (config>redundancy>mc>peer>mcr>ring>path-excl range)

Full Context

configure redundancy multi-chassis peer mc-ring ring path-b range

configure redundancy multi-chassis peer mc-ring ring path-excl range

Description

This command configures a Layer 2 MC-Ring path-b or path-excl VLAN range.

By default, all customer VLANs participating in an L2 MC-Ring are on path-a. For load balancing purposes, a range of customer VLANs can be configured to use path-b which is set up in the opposite direction than path-a.The range of VLANs that are not participating in L2 MC-Ring are configured using the path-excl command.

Parameters

vlan-range

Specifies the VLAN range.

Values

[0 to 4094] - [0 to 4094]

[0 to 4094] - *

* - *

Platforms

All

range

Syntax

[no] range vlan-range

Context

[Tree] (config>service>vpls>sap>managed-vlan-list range)

Full Context

configure service vpls sap managed-vlan-list range

Description

This command configures a range of VLANs on an access port that are to be managed by an existing management VPLS.

This command is only valid when the VPLS in which it is entered was created as a management VPLS, and when the SAP in which it was entered was created on an Ethernet port with encapsulation type of dot1q or qinq, or on a SONET/SDH port with encapsulation type of bcp-dot1q.

To modify the range of VLANs, first the new range should be entered and afterwards the old range removed.

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

Parameters

vlan-range

Specifies the VLAN start value and VLAN end value. The end-vlan must be greater than start-vlan. The format is <start-vlan>-<end-vlan>.

Values

start-vlan: 1 to 4094

end-vlan: 1 to 4094

Platforms

All

range

Syntax

range start [value] end [value]

range default

no range start [value] end [value]

Context

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

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

Full Context

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

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

Description

This command creates a VLAN range or enters the context of the specified VLAN ranges for configuration applicable to that range of VLANs.

Parameters

start

Specifies the start of the VLAN range.

Values

0 to 4096

Default

200

end

Specifies the end of VLAN range.

Values

0 to 4096

Default

400

default

Specifies to use defaults for the interface.

Platforms

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

range

Syntax

range isid [to isid]

no range

Context

[Tree] (config>service>vpls>isid-policy>entry range)

Full Context

configure service vpls isid-policy entry range

Description

This command specifies an ISID or a Range of ISIDs in a B-VPLS. One range is allowed per entry.

Default

no range

Parameters

isid

Specifies the ISID value in 24 bits. When singular, ISID identifies a particular ISID to be used for matching

Values

0 to 16777215

to isid

Identifies upper value in a range of ISIDs to be used as matching criteria

Platforms

All

range

Syntax

range range-id isid isid-value [to isid-value] [create]

no range range-id

Context

[Tree] (config>service>vpls>sap>static-isid range)

[Tree] (config>service>vpls>spoke-sdp>static-isid range)

Full Context

configure service vpls sap static-isid range

configure service vpls spoke-sdp static-isid range

Description

This command identifies a set of ISIDs for I-VPLS services that are external to SPBM. These ISIDs are advertised as supported locally on this node unless an altered by an isid-policy. This allows communication from I-VPLS services external to SPBM through this node. The SAP may be a regular SAP or MC-LAG SAP. The spoke-SDP may be an active/standby spoke. When used with MC-LAG or active/stand-by PWs the conditional static-mac must be configured. ISIDs declared this way become part of the ISID multicast and consume MFIBs. Multiple SPBM static-isid ranges are allowed under a SAP/spoke-SDP.

The static-isids are associated with a remote B-MAC that must be declared as a static-mac for unicast traffic. ISIDs are advertised as if they were attached to the local B-MAC. Only remote I-VPLS ISIDs need to be defined. In the MFIB, the group MACs are then associated with the active SAP or spoke-SDP. An ISID policy may be defined to suppress the advertisement of an ISID if the ISID is primary used for unicast services. The following rules govern the usage of multiple ISID 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.

The no form of this command removes all the previous statements under one interface

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 316 to 400” was used using "no isid 316 to 350” will not work but "no isid 316 to 400 will be successful.

Parameters

range-id

Sets context for specified entry ID for the static-isids

Values

1— 8191

isid-value

Configures the ISID or the start of an ISID range. Specifies the ISID value in 24 bits. When just one present identifies a particular ISID to be used for matching.

Values

0 to 16777215

to isid

Identifies upper value in a range of ISIDs to be used as matching criteria

Values

0 to 16777215

create

This keyword is mandatory when creating a range instance.

Platforms

All

range

Syntax

range start-entry policer-id count count

no range

Context

[Tree] (config>qos>sap-egress>dyn-policer range)

[Tree] (config>qos>sap-ingress>dyn-policer range)

Full Context

configure qos sap-egress dynamic-policer range

configure qos sap-ingress dynamic-policer range

Description

This command defines the range of ids for dynamic policers that are created using a Gx interface.

The no form of this command disables creation of dynamic policers using a Gx interface, resulting in a Gx rule instantiation failure, which is the default.

Default

no range

Parameters

start-entry policer-id

Specifies the lowest entry in the range.

Values

1 to 63

count count

Specifies the number of entries in the range.

Values

1 to 63

Platforms

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

rapid-psc-timer

rapid-psc-timer

Syntax

rapid-psc-timer interval

no rapid-psc-timer

Context

[Tree] (config>router>mpls>mpls-tp>protection-template rapid-psc-timer)

Full Context

configure router mpls mpls-tp protection-template rapid-psc-timer

Description

This command configures the rapid timer value to be used for protection switching coordination (PSC) packets for MPLS-TP linear protection (RFC 6378).

Default

rapid-psc-timer 10

Parameters

interval

Specifies the rapid timer interval in milliseconds.

Values

[10, 100, 1000]

Platforms

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

rapid-retransmit-time

rapid-retransmit-time

Syntax

rapid-retransmit-time hundred-milliseconds

no rapid-retransmit-time

Context

[Tree] (config>router>rsvp rapid-retransmit-time)

Full Context

configure router rsvp rapid-retransmit-time

Description

This command defines the value of the Rapid Retransmission Interval. It is used in the re-transmission mechanism to handle unacknowledged message_id objects and is based on an exponential back-off timer.

Re-transmission interval of a RSVP message with the same message_id = 2 * rapid-retransmit-time interval of time.

The node stops re-transmission of unacknowledged RSVP messages:

  • If the updated back-off interval exceeds the value of the regular refresh interval.

  • If the number of re-transmissions reaches the value of the rapid-retry-limit parameter, whichever comes first.

The Rapid Retransmission Interval must be smaller than the regular refresh interval configured in config>router>rsvp>refresh-time.

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

Default

rapid-retransmit-time 5

Parameters

hundred-milliseconds

Specifies the rapid retransmission interval, in hundred-milliseconds (for example, enter "6” for a 600 millisecond retransmit time).

Values

1 to 100, in units of 100 ms.

Platforms

All

rapid-retry-limit

rapid-retry-limit

Syntax

rapid-retry-limit number

no rapid-retry-limit

Context

[Tree] (config>router>rsvp rapid-retry-limit)

Full Context

configure router rsvp rapid-retry-limit

Description

This command defines the value of the Rapid Retry Limit. This is used in the retransmission mechanism based on an exponential backoff timer in order to handle unacknowledged message_id objects. The RSVP message with the same message_id is retransmitted every 2 * rapid-retransmit-time interval of time. The node stops retransmission of unacknowledged RSVP messages whenever the updated backoff interval exceeds the value of the regular refresh interval or the number of retransmissions reaches the value of the rapid-retry-limit parameter, whichever comes first.

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

Default

rapid-retry-limit 3

Parameters

number

Specifies the value of the Rapid Retry Limit.

Values

1 to 6, integer values

Platforms

All

rapid-update

rapid-update

Syntax

rapid-update [l2-vpn] [mvpn-ipv4] [mvpn-ipv6] [mdt-safi] [evpn] [label-ipv4] [label-ipv6] [vpn-ipv4] [vpn-ipv6] [mcast-vpn-ipv4] [mcast-vpn-ipv6]

no rapid-update

Context

[Tree] (config>router>bgp rapid-update)

Full Context

configure router bgp rapid-update

Description

This command enables and disables BGP rapid update for specified address families.

If rapid update is enabled for a set of address families, and a route belonging to a family in that set is received by the router and chosen for propagation to certain BGP peers, the remaining time on the MRAI timer of these peers is ignored and the route is transmitted immediately, along with all other pending routes for these peers (including routes of address families not specified in the rapid-update command).

The rapid-update command overrides the peer-level min-route-advertisement (config>router>bgp min-route-advertisement, config>router>bgp>group min-route-advertisement, config>router>bgp>group>neighbor min-route-advertisement) time and applies the minimum setting (0 seconds) to routes belonging to specified address families; routes of other address families continue to be advertised according to the session-level MRAI setting.

The no form of this command disables rapid update for all address families.

Default

no rapid-update

Parameters

l2-vpn

Specifies the BGP rapid update for the 12-byte Virtual Switch Instance identifier (VSI-ID) value consisting of the 8-byte route distinguisher (RD) followed by a 4-byte value.

mvpn-ipv4

Specifies BGP rapid update for the mvpn-ipv4 address family. The mvpn-pv4 address is a variable size value consisting of the 1-byte route type, 1-byte length and variable size that is route type specific. Route type defines encoding for the route type specific field. Length indicates the length in octets of the route type specific field.

mdt-safi

Specifies BGP rapid update for the mdt-safi address family. The address is a 16-byte value consisting of 12-byte route distinguisher (RD) followed by a 4-byte group address.

mvpn-ipv6

Specifies BGP rapid update for the mvpn-ipv6 address family.

evpn

Specifies BGP rapid update for the evpn address family by including or removing EVPN routes from the set of routes that can trigger rapid update.

label-ipv4

Includes or removes label-ipv4 routes from the set of routes that can trigger rapid update.

label-ipv6

Includes or removes label-ipv6 routes from the set of routes that can trigger rapid update.

vpn-ipv4

Includes or removes vpn-ipv4 routes from the set of routes that can trigger rapid update.

vpn-ipv6

Includes or removes vpn-ipv6 routes from the set of routes that can trigger rapid update.

mcast-vpn-ipv4

Includes or removes mcast-vpn-ipv4 routes from the set of routes that can trigger rapid update.

mcast-vpn-ipv6

Includes or removes mcast-vpn-ipv6 routes from the set of routes that can trigger rapid update.

Platforms

All

rapid-withdrawal

rapid-withdrawal

Syntax

[no] rapid-withdrawal

Context

[Tree] (config>service>vprn>bgp rapid-withdrawal)

Full Context

configure service vprn bgp rapid-withdrawal

Description

This command disables the delay (Minimum Route Advertisement) on sending BGP withdrawals. Normal route withdrawals may be delayed up to the minimum route advertisement to allow for efficient packing of BGP updates.

The no form of this command removes this command from the configuration and returns withdrawal processing to the normal behavior.

Default

no rapid-withdrawal

Platforms

All

rapid-withdrawal

Syntax

[no] rapid-withdrawal

Context

[Tree] (config>router>bgp rapid-withdrawal)

Full Context

configure router bgp rapid-withdrawal

Description

This command disables the delay (Minimum Route Advertisement) on sending BGP withdrawals. Normal route withdrawals may be delayed up to the minimum route advertisement to allow for efficient packing of BGP updates.

The no form of this command removes this command from the configuration and returns withdrawal processing to the normal behavior.

Default

no rapid-withdrawal

Platforms

All

rat-type

rat-type

Syntax

rat-type {utran | geran | wlan | gan | hspa | eutran | virtual | id}

no rat-type

Context

[Tree] (config>subscr-mgmt>gtp>peer-profile rat-type)

Full Context

configure subscriber-mgmt gtp peer-profile rat-type

Description

This command configures the default Radio Access Type (RAT) signaled during GTP setup. RAT is the underlying physical connection method for a radio-based communication network. This can be overridden by RADIUS.

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

Default

rat-type wlan

Parameters

utran

Specifies the signaled RAT type is UTRAN (1).

geran

Specifies the signaled RAT type is GERAN (2).

wlan

Specifies the signaled RAT type is WLAN (3).

gan

Specifies the signaled RAT type is GAN (4).

hspa

Specifies the signaled RAT type is HSPA Evolution (5).

eutran

Specifies the signaled RAT type is EUTRAN (6).

virtual

Specifies the signaled RAT type is virtual (7).

id

Specifies the numeric RAT type value.

Values

0 to 255

Platforms

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

rat-type

Syntax

[no] rat-type

Context

[Tree] (config>subscr-mgmt>auth-plcy>include-radius-attribute rat-type)

Full Context

configure subscriber-mgmt authentication-policy include-radius-attribute rat-type

Description

This command enables the inclusion of the Radio Access Type in AAA protocols as signaled in the incoming GTP setup message.

The no form of this command disables the inclusion of the attribute.

Platforms

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

rat-type

Syntax

[no] rat-type

Context

[Tree] (config>subscr-mgmt>diam-appl-plcy>nasreq>include-avp rat-type)

[Tree] (config>subscr-mgmt>diam-appl-plcy>gx>include-avp rat-type)

Full Context

configure subscriber-mgmt diameter-application-policy nasreq include-avp rat-type

configure subscriber-mgmt diameter-application-policy gx include-avp rat-type

Description

This command includes the RAT type.

The no form of this command reverts to the default.

Platforms

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

  • configure subscriber-mgmt diameter-application-policy nasreq include-avp rat-type

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

  • configure subscriber-mgmt diameter-application-policy gx include-avp rat-type

rate

rate

Syntax

rate rate

no rate

Context

[Tree] (config>subscr-mgmt>sla-prof>egress>qos>hs-wrr-grp rate)

Full Context

configure subscriber-mgmt sla-profile egress qos hs-wrr-group rate

Description

This command configures the rate (PIR) override for the WRR group.

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

Parameters

rate

Specifies the PIR expressed as a percentage of line rate in kb/s.

Values

1 to 2000000000, max

Platforms

7750 SR-7/12/12e

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>subscr-mgmt>sla-prof>egress>qos>queue rate)

Full Context

configure subscriber-mgmt sla-profile egress qos queue rate

Description

This command defines the administrative Peak Information Rate (PIR) and the administrative Committed Information Rate (CIR) parameters for the queue. The PIR defines the maximum rate that the queue can transmit packets out an egress interface (for SAP egress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth.

The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. In-profile then out-of-profile packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse. To be properly handled throughout the network, the packets must be marked accordingly for profiling at each hop.

The CIR can be used by the queue’s parent command’s cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.

The rate command can be executed at any time, altering the PIR and CIR rates for all queues created through the association of the SAP egress QoS policy with the queue-id.

The no form of this command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).

Parameters

pir-rate

Defines the administrative PIR rate, in kb/s, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. Fractional values are not allowed and must be given as a positive integer.

The actual PIR rate is dependent on the queues adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

1 to 2000000000, max

Default

max

cir-rate

Defines the administrative CIR rate, kb/s, for the queue. The cir parameter overrides the default administrative CIR used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed. Fractional values are not allowed and must be given as a positive integer.

Values

0 to 2000000000, max

Default

0

Platforms

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

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>subscr-mgmt>sla-prof>ingress>qos>queue rate)

Full Context

configure subscriber-mgmt sla-profile ingress qos queue rate

Description

This command defines the administrative Peak Information Rate (PIR) and the administrative Committed Information Rate (CIR) parameters for the queue. The PIR defines the maximum rate that the queue can transmit packets through the switch fabric (for SAP ingress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth.

The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. For SAP ingress, the CIR also defines the rate that packets are considered in-profile by the system. In-profile then out-of-profile packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse. To be properly handled throughout the network, the packets must be marked accordingly for profiling at each hop.

The CIR can be used by the queue’s parent command’s cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.

The rate command can be executed at any time, altering the PIR and CIR rates for all queues created through the association of the SAP ingress or SAP egress QoS policy with the queue-id.

The no form of this command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).

Parameters

pir-rate

Defines the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed.

Fractional values are not allowed and must be given as a positive integer.

The actual PIR rate is dependent on the queues adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

1 to 2000000000, max

Default

max

cir-rate

Specifies the cir parameter used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed.

Fractional values are not allowed and must be given as a positive integer.

Values

0 to 2000000000, max

Default

0

Platforms

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

rate

Syntax

rate {max | rate} [cir {max | rate}]

Context

[Tree] (config>subscr-mgmt>sla-prof>egress>qos>policer rate)

[Tree] (config>subscr-mgmt>sla-prof>ingress>qos>policer rate)

Full Context

configure subscriber-mgmt sla-profile egress qos policer rate

configure subscriber-mgmt sla-profile ingress qos policer rate

Description

This command is used to configure the policer’s metering and optional profiling rates. The metering rate is used by the system to configure the policer’s PIR leaky bucket’s decrement rate while the profiling rate configures the policer’s CIR leaky bucket’s decrement rate. The decrement function empties the bucket while packets applied to the bucket attempt to fill it based on each packets size. If the bucket fills faster than how much is decremented per packet, the bucket’s depth eventually reaches it's exceed (CIR) or violate (PIR) threshold. The cbs, mbs, and high-prio-only commands are used to configure the policer’s PIR and CIR thresholds.

If a packet arrives at the policer while the bucket’s depth is less than the threshold associated with the packet, the packet is considered to be conforming to the bucket’s rate. If the bucket depth is equal to or greater than the threshold, the packet is considered to be in the exception state. For the CIR bucket, the exception state is exceeding the CIR rate while the PIR bucket's exception state is violating the PIR bucket rate. If the packet is violating the PIR, the packet is marked red and is discarded. If the packet is not red, it may be green or yellow based on the conforming or exceeding state from the CIR bucket.

When a packet is red neither the PIR or CIR bucket depths are incremented by the packets size. When the packet is yellow the PIR bucket is incremented by the packet size, but the CIR bucket is not. When the packet is green, both the PIR and CIR buckets are incremented by the packet size. This ensures that conforming packets impact the bucket depth while exceeding or violating packets do not.

The policer’s adaptation-rule command settings are used by the system to convert the specified rates into hardware timers and decrement values for the policer’s buckets.

By default, the policer’s metering rate is max and the profiling rate is 0 kb/s (all packets out-of-profile).

The rate settings defined for the policer in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied.

The no form of this command restores the default metering and profiling rate to a policer.

Parameters

{max | rate}

Specifies the packet byte offset. Specifying the keyword max or an explicit rate (in kilobits per second) parameter directly following the rate command is required and identifies the policer’s metering rate for the PIR leaky bucket. When the policer is first created, the metering rate defaults to max. The kilobits per second value must be expressed as an integer and defines the rate in kilobits per second. The integer value is multiplied by 1,000 to derive the actual rate in bits per second. When max is specified, the maximum policer rate used is equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the PIR used is equivalent to max.

Values

max or 1 to 2000000000

cir {max | rate}

Specifies the packet byte offset. The optional cir keyword is used to override the default CIR rate of the policer. Specifying the keyword max or an explicit rate (in kilobits per second) parameter directly following the cir keyword is required and identifies the policer’s profiling rate for the CIR leaky bucket. When the policer is first created, the profiling rate defaults to 0 kb/s. The kilobits per second value must be expressed as an integer and defines the rate in kilobits per second. The integer value is multiplied by 1,000 to derive the actual rate in bits per second. When max is specified, the maximum policer rate used is equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the CIR used is equivalent to max.

Values

max or 0 to 2000000000

Platforms

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

rate

Syntax

rate kilobits-per-second

no rate

Context

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

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

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

Full Context

configure service vprn subscriber-interface group-interface sap egress agg-rate rate

configure service ies interface sap egress agg-rate rate

configure service ies subscriber-interface group-interface sap egress agg-rate rate

Description

This command defines the enforced aggregate rate for all queues associated with the agg-rate context. A rate must be specified for the agg-rate context to be considered to be active on the context’s object (SAP, subscriber, Vport, and so on).

The no form of this command removes an explicit rate value from the aggregate rate therefore returning it to its default value.

Parameters

kilobits-per-second

Specifies the rate limit for the SAP, in kilobits per second.

Values

1 to 6400000000, max

Platforms

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

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

All

  • configure service ies interface sap egress agg-rate rate

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>service>ies>if>sap>ingress>queue-override>queue rate)

[Tree] (config>service>ies>if>sap>egress>queue-override>queue rate)

[Tree] (config>service>vpls>sap>egress>queue-override>queue rate)

[Tree] (config>service>vpls>sap>ingress>queue-override>queue rate)

Full Context

configure service ies interface sap ingress queue-override queue rate

configure service ies interface sap egress queue-override queue rate

configure service vpls sap egress queue-override queue rate

configure service vpls sap ingress queue-override queue rate

Description

This command overrides specific attributes of the specified queue’s Peak Information Rate (PIR) and the Committed Information Rate (CIR) parameters.

The PIR defines the maximum rate that the queue can transmit packets out an egress interface (for SAP egress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth.

The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. In-profile, then out-of-profile, packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse. To be properly handled throughout the network, the packets must be marked accordingly for profiling at each hop.

The CIR can be used by the queue’s parent commands cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.

The rate command can be executed at any time, altering the PIR and CIR rates for all queues created through the association of the SAP egress QoS policy with the queue-id.

The no form of this command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).

Default

rate max cir 0

Parameters

pir-rate

Defines the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed.

Fractional values are not allowed and must be configured as a positive integer.

The actual PIR rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

1 to 6400000000, max

Default

max

cir-rate

Overrides the default administrative CIR used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed.

Fractional values are not allowed and must be configured as a positive integer.

Values

0 to 6400000000, max

Default

0

Platforms

All

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>service>vpls>sap>egress>sched-override>scheduler rate)

Full Context

configure service vpls sap egress scheduler-override scheduler rate

Description

This command overrides specific attributes of the specified scheduler rate. The rate command defines the maximum bandwidth that the scheduler can offer its policers, child queues or schedulers. The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent scheduler. If the scheduler has no parent, the maximum rate is assumed to be the amount available to the scheduler. When a parent is associated with the scheduler, the CIR parameter provides the amount of bandwidth to be considered during the parent scheduler’s 'within CIR’ distribution phase.

The actual operating rate of the scheduler is limited by bandwidth constraints other than its maximum rate. The scheduler’s parent scheduler may not have the available bandwidth to meet the scheduler’s needs or the bandwidth available to the parent scheduler could be allocated to other child schedulers or child queues on the parent based on higher priority. The children of the scheduler may not need the maximum rate available to the scheduler because of insufficient offered load or limits to their own maximum rates.

When a scheduler is defined without specifying a rate, the default rate is max. If the scheduler is a root scheduler (no parent defined), the default maximum rate must be changed to an explicit value. Without this explicit value, the scheduler assumes that an infinite amount of bandwidth is available and allow all child queues and schedulers to operate at their maximum rates.

The no form of this command returns the scheduler's PIR and CIR parameters to the value configured in the applied scheduler policy.

Default

rate max cir sum

Parameters

pir-rate

Specifies the PIR rates. The pir parameter accepts a step multiplier value that specifies the multiplier used to determine the PIR rate at which the queue operates. A value of 0 to 100000000 or the keyword max is accepted. Any other value results in an error without modifying the current PIR rate.

To calculate the actual PIR rate, the rate described by the queue’s rate is multiplied by the pir-rate.

The SAP ingress context for PIR is independent of the defined forwarding class (fc) for the queue. The default pir and definable range is identical for each class. The PIR in effect for a queue defines the maximum rate at which the queue is allowed to forward packets in a given second, shaping the queue’s output.

The PIR parameter for SAP ingress queues do not have a negate (no) function. To return the queue’s PIR rate to the default value, that value must be specified as the PIR value.

Values

1 to 6400000000, max

Default

max

cir-rate

Specifies the CIR rate. The cir parameter accepts a step-multiplier value that specifies the multiplier used to determine the CIR rate at which the queue operate. A value of 0 to 250 or the keyword max is accepted. Any other value results in an error without modifying the current CIR rate.

To calculate the actual CIR rate, the rate described by the rate pir pir-rate is multiplied by the cir-rate. If the cir is set to max, then the CIR rate is set to infinity.

The context for CIR is dependent on the defined forwarding class (fc) for the queue. The default CIR and definable range is different for each class. The CIR in effect for a policer or queue defines both its profile (in or out) marking level as well as the relative importance compared to other queues for scheduling purposes during congestion periods.

Values

0 to 6400000000, max, sum

Default

sum

Platforms

All

rate

Syntax

rate rate [cir cir-rate]

no rate

Context

[Tree] (config>subscr-mgmt>isa-policer rate)

Full Context

configure subscriber-mgmt isa-policer rate

Description

This command specifies at which rate the policer drains packets. The cir value is only supported on dual-bucket-bandwidth policers. If rate max is configured, no actual rate limitations are applied.

The no form of this command reverts to the default.

Parameters

rate

Specifies the rate in kb/s.

Values

1 to 100000000, max

Default

max

cir-rate

Specifies the CIR rate in kb/s.

Values

1 to 100000000, max

Default

max

Platforms

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

rate

Syntax

rate {max | rate}

no rate

Context

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

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>egress>agg-rate rate)

Full Context

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

configure service vprn subscriber-interface group-interface wlan-gw egress agg-rate rate

Description

This command defines the enforced aggregate rate for all queues associated with the agg-rate context. A rate must be specified for the agg-rate context to be considered to be active on the context’s object (SAP, subscriber, Vport, and so on).

The no form of this command reverts to the default.

rate

Syntax

rate {rate | max} [cir {max | rate}]

no rate

Context

[Tree] (config>card>fp>ingress>access>qgrp>policer-over>plcr rate)

[Tree] (config>card>fp>ingress>network>qgrp>policer-over>plcr rate)

Full Context

configure card fp ingress access queue-group policer-override policer rate

configure card fp ingress network queue-group policer-override policer rate

Description

This command configures the policer’s metering and optional profiling rates. The metering rate is used by the system to configure the policer’s PIR leaky bucket’s decrement rate while the profiling rate configures the policer’s CIR leaky bucket’s decrement rate. The decrement function empties the bucket while packets applied to the bucket attempt to fill it based on its packet size. If the bucket fills faster than how much is decremented per packet, the bucket’s depth eventually reaches it's exceeded (CIR) or violate (PIR) threshold. The cbs, mbs, and high-prio-only commands are used to configure the policer’s PIR and CIR thresholds.

If a packet arrives at the policer while the bucket’s depth is less than the threshold associated with the packet, the packet is considered to be conforming to the bucket’s rate. If the bucket depth is equal to or greater than the threshold, the packet is considered to be in the exception state. For the CIR bucket, the exception state is exceeding the CIR rate while the PIR bucket's exception state is violating the PIR bucket rate. If the packet is violating the PIR, the packet is marked red and will be discarded. If the packet is not red, it may be green or yellow based on the conforming or exceeding state from the CIR bucket.

When a packet is red neither the PIR nor the CIR bucket depths are incremented by the packets size. When the packet is yellow the PIR bucket is incremented by the packet size, but the CIR bucket is not. When the packet is green, both the PIR and CIR buckets are incremented by the packet size. This ensures that conforming packets impact the bucket depth while exceeding or violating packets do not.

The policer’s adaptation-rule command settings are used by the system to convert the specified rates into hardware timers and decrement values for the policer’s buckets.

By default, the policer’s metering rate is max and the profiling rate is 0 kb/s (all packets out-of-profile).

The rate settings defined for the policer in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied.

The no form of this command reverts to the default metering and profiling rate of a policer.

Parameters

{rate | max}

Specifying the keyword max or an explicit rate parameter directly following the rate command is required and identifies the policer’s metering rate for the PIR leaky bucket. When the policer is first created, the metering rate defaults to max. The kilobits-per-second value must be expressed as an integer and defines the rate in kilobits-per-second. The integer value is multiplied by 1,000 to derive the actual rate in bits-per-second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the PIR used is equivalent to max.

Values

max or 1 to 2000000000

cir {max | rate}

The optional cir keyword is used to override the default CIR rate of the policer. Specifying the keyword max or an explicit rate parameter directly following the cir keyword is required and identifies the policer’s profiling rate for the CIR leaky bucket. When the policer is first created, the profiling rate defaults to 0 kb/s. The kilobits-per-second value must be expressed as an integer and defines the rate in kilobits-per-second. The integer value is multiplied by 1,000 to derive the actual rate in bits-per-second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the CIR used is equivalent to max.

Values

max or 0 to 2000000000

Platforms

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

rate

Syntax

rate kilobits-per-second

no rate

Context

[Tree] (config>port>ethernet>access>egr>qgrp>agg-rate rate)

[Tree] (config>port>ethernet>network>egr>qgrp>agg-rate rate)

Full Context

configure port ethernet access egress queue-group agg-rate rate

configure port ethernet network egress queue-group agg-rate rate

Description

This command defines the enforced aggregate rate for all queues associated with the agg-rate context. A rate must be specified for the agg-rate context to be considered to be active on the context’s object.

The no form of this command removes an explicit rate value from the aggregate rate returning it to its default value.

Parameters

kilobits-per-second

Specifies the rate limit for the queue group, in kilobits per second.

Values

1 to 3200000000, max

Platforms

All

rate

Syntax

rate kilobits-per-second

no rate

Context

[Tree] (config>port>ethernet>access>egr>vport>agg-rate rate)

Full Context

configure port ethernet access egress vport agg-rate rate

Description

This command defines the enforced aggregate rate for all queues associated with the agg-rate context. A rate must be specified for the agg-rate context to be considered to be active on the context’s object.

The no form of this command removes an explicit rate value from the aggregate rate returning it to its default value.

Parameters

kilobits-per-second

Specifies the rate limit for the Vport, in kilobits per second.

Values

1 to 6400000000, max

Platforms

All

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>port>ethernet>network>egr>qover>q rate)

[Tree] (config>port>ethernet>access>ing>qgrp>qover>q rate)

[Tree] (config>port>ethernet>access>egr>qgrp>qover>q rate)

Full Context

configure port ethernet network egress queue-overrides queue rate

configure port ethernet access ingress queue-group queue-overrides queue rate

configure port ethernet access egress queue-group queue-overrides queue rate

Description

This command specifies the administrative Peak Information Rate (PIR) and the administrative Committed Information Rate (CIR) parameters for the queue. The PIR defines the maximum rate that the queue can transmit packets out an egress interface (for SAP egress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth.

The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. In-profile then out-of-profile packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse. To be properly handled throughout the network, the packets must be marked accordingly for profiling at each hop.

The CIR can be used by the queue’s parent commands cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.

The rate command can be executed at any time, altering the PIR and CIR rates for all queues created through the association of the SAP egress QoS policy with the queue-id.

This command is ignored for egress HSQ queue group queues which are attached to an HS WRR group within an associated HS attachment policy. In this case, the configuration of the rate is performed under the hs-wrr-group within the egress queue group template.

The no form of this command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).

Default

rate max cir 0 - The max default specifies the amount of bandwidth in kilobits per second (thousand bits per second). The max value is mutually exclusive to the pir-rate value.

Parameters

pir-rate

Defines the administrative PIR rate, in kilobits per second, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. Fractional values are not allowed and must be given as a positive integer.

The actual PIR rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

1 to 200000000, max

Default

max

cir-rate

The cir parameter overrides the default administrative CIR used by the queue, in kilobits per second. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed. Fractional values are not allowed and must be given as a positive integer.

Values

0 to 200000000, max

Default

0

Platforms

All

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>port>ethernet>access>ing>qgrp>sched-override>scheduler rate)

[Tree] (config>port>ethernet>access>egr>qgrp>sched-override>scheduler rate)

Full Context

configure port ethernet access ingress queue-group scheduler-override scheduler rate

configure port ethernet access egress queue-group scheduler-override scheduler rate

Description

This command can be used to override specific attributes of the specified scheduler rate. The rate command defines the maximum bandwidth that the scheduler can offer its child queues or schedulers. The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent scheduler. If the scheduler has no parent, the maximum rate is assumed to be the amount available to the scheduler. When a parent is associated with the scheduler, the CIR parameter provides the amount of bandwidth to be considered during the parent scheduler's 'within CIR' distribution phase.

The actual operating rate of the scheduler is limited by bandwidth constraints other than its maximum rate. The scheduler's parent scheduler may not have the available bandwidth to meet the scheduler's needs or the bandwidth available to the parent scheduler could be allocated to other child schedulers or child queues on the parent based on higher priority. The children of the scheduler may not need the maximum rate available to the scheduler because of insufficient offered load or limits to their own maximum rates.

When a scheduler is defined without specifying a rate, the default rate is max. If the scheduler is a root scheduler (no parent defined), the default maximum rate must be changed to an explicit value. Without this explicit value, the scheduler assumes that an infinite amount of bandwidth is available and allow all child policers, queues, and schedulers to operate at their maximum rates.

The no form of this command returns the scheduler's PIR and CIR parameters to the value configured in the applied scheduler policy.

Parameters

pir-rate

Specifies the PIR rate, in kilobits per second. Any other value results in an error without modifying the current PIR rate.

Values

1 to 6400000000, max

cir-rate

Specifies the CIR rate, in kilobits per second. If the CIR is set to max, then the CIR rate is set to infinity. The sum keyword specifies that the CIR be used as the summed CIR values of the children schedulers, policers, or queues.

Values

0 to 6400000000, sum, max

Platforms

All

rate

Syntax

rate rate

no rate

Context

[Tree] (config>port>ethernet>egress>hs-sec-shaper>agg rate)

[Tree] (config>port>ethernet>egress>hs-sec-shaper>class rate)

Full Context

configure port ethernet egress hs-secondary-shaper aggregate rate

configure port ethernet egress hs-secondary-shaper class rate

Description

This command specifies the rate allowed for the HS secondary shaper's aggregate rate and per-class rates.

The no form of this command reverts to the default.

Default

rate max

Parameters

rate

Specifies the maximum rate in kilobits per second. When the max keyword follows the rate keyword, the bandwidth limitation is removed from the aggregate or class. The max keyword is mutually exclusive to the rate parameter. Either max or a rate value must follow the rate keyword.

Values

1 to 100000000, max

Platforms

7750 SR-7/12/12e

rate

Syntax

rate kilobits-per-second

no rate

Context

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

[Tree] (config>service>ipipe>sap>egress>agg-rate rate)

[Tree] (config>service>cpipe>sap>egress>agg-rate rate)

Full Context

configure service epipe sap egress agg-rate rate

configure service ipipe sap egress agg-rate rate

configure service cpipe sap egress agg-rate rate

Description

This command defines the enforced aggregate rate for all queues associated with the agg-rate context. A rate must be specified for the agg-rate context to be considered to be active on the context’s object (SAP, subscriber, Vport, and so on).

The no form of this command removes an explicit rate value from the aggregate rate returning it to its default value.

Parameters

kilobits-per-second

The enforced aggregate rate for all queues associated with the agg-rate context, in kilobits per second.

Values

1 to 6400000000, max

Platforms

All

  • configure service ipipe sap egress agg-rate rate
  • configure service epipe sap egress agg-rate rate

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

  • configure service cpipe sap egress agg-rate rate

rate

Syntax

rate {rate | max} [cir {rate | max}]

Context

[Tree] (config>service>epipe>sap>ingress>policer-over>plcr rate)

[Tree] (config>service>cpipe>sap>egress>policer-over>plcr rate)

[Tree] (config>service>epipe>sap>egress>policer-over>plcr rate)

[Tree] (config>service>ipipe>sap>ingress>policer-over>plcr rate)

[Tree] (config>service>cpipe>sap>ingress>policer-over>plcr rate)

[Tree] (config>service>ipipe>sap>egress>policer-over>plcr rate)

Full Context

configure service epipe sap ingress policer-override policer rate

configure service cpipe sap egress policer-override policer rate

configure service epipe sap egress policer-override policer rate

configure service ipipe sap ingress policer-override policer rate

configure service cpipe sap ingress policer-override policer rate

configure service ipipe sap egress policer-override policer rate

Description

This command within the SAP ingress and egress policer-overrides contexts is used to override the sap-ingress and sap-egress QoS policy configured rate parameters for the specified policer-id.

The no rate command is used to restore the policy defined metering and profiling rate to a policer.

Parameters

rate rate

Specifies the policer instance metering rate for the PIR leaky bucket, in kilobits per second. The integer value is multiplied by 1000 to derive the actual rate in bits per second.

Values

1 to 6400000000

cir rate

Specifies the overriding value for the policy-derived profiling rate of the policer, in kilobits per second. The integer value is multiplied by 1000 to derive the actual rate in bits per second.

Values

0 to 6400000000

max

Uses the maximum policer rate, equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the PIR or CIR used is equivalent to max.

Platforms

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

  • configure service ipipe sap egress policer-override policer rate
  • configure service epipe sap ingress policer-override policer rate
  • configure service ipipe sap ingress policer-override policer rate
  • configure service epipe sap egress policer-override policer rate

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

  • configure service cpipe sap egress policer-override policer rate
  • configure service cpipe sap ingress policer-override policer rate

rate

Syntax

rate rate

no rate

Context

[Tree] (config>service>epipe>sap>egress>queue-override>hs-wrr-group rate)

[Tree] (config>service>ipipe>sap>egress>queue-override>hs-wrr-group rate)

Full Context

configure service epipe sap egress queue-override hs-wrr-group rate

configure service ipipe sap egress queue-override hs-wrr-group rate

Description

This command overrides the scheduling rate applied to the HS WRR group in kb/s. A rate can be specified in kb/s or the keyword max can be used to remove the bandwidth limitation on the HS WRR group. The override rate type must match the corresponding rate type within the applied QoS policy.

The no form of this command removes the rate override value from the configuration.

Parameters

rate

Specifies the scheduling rate of the HS WRR group in kb/s.

Values

1 to 2000000000, max

Platforms

7750 SR-7/12/12e

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>service>epipe>sap>egress>queue-override>queue rate)

[Tree] (config>service>ipipe>sap>ingress>queue-override>queue rate)

[Tree] (config>service>epipe>sap>ingress>queue-override>queue rate)

[Tree] (config>service>cpipe>sap>ingress>queue-override>queue rate)

[Tree] (config>service>ipipe>sap>egress>queue-override>queue rate)

[Tree] (config>service>cpipe>sap>egress>queue-override>queue rate)

Full Context

configure service epipe sap egress queue-override queue rate

configure service ipipe sap ingress queue-override queue rate

configure service epipe sap ingress queue-override queue rate

configure service cpipe sap ingress queue-override queue rate

configure service ipipe sap egress queue-override queue rate

configure service cpipe sap egress queue-override queue rate

Description

This command can be used to override specific attributes of the specified queue’s Peak Information Rate (PIR) and the Committed Information Rate (CIR) parameters.

The PIR defines the maximum rate that the queue can transmit packets out an egress interface (for SAP egress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth.

The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. In-profile and then out-of-profile packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse. To be properly handled throughout the network, the packets must be marked accordingly for profiling at each hop.

The CIR can be used by the queue’s parent commands cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.

The rate command can be executed at any time, altering the PIR and CIR rates for all queues created through the association of the SAP egress QoS policy with the queue-id.

This command is ignored for egress HSQ queue group queues which are attached to an HS WRR group within an associated HS attachment policy. In this case, the configuration of the rate is performed under the hs-wrr-group within the SAP egress QoS policy.

The no form of this command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).

Default

rate max cir 0

Parameters

pir-rate

Defines the administrative PIR rate, in kilobits per second, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed.

Fractional values are not allowed and must be given as a positive integer.

The actual PIR rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

1 to 6400000000, max

Default

max

cir-rate

The cir parameter overrides the default administrative CIR used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed.

Fractional values are not allowed and must be given as a positive integer. The sum keyword specifies that the CIR be used as the summed CIR values of the children schedulers, policers, or queues.

Values

0 to 6400000000, max, sum

Default

0

Platforms

All

  • configure service ipipe sap egress queue-override queue rate
  • configure service epipe sap egress queue-override queue rate
  • configure service epipe sap ingress queue-override queue rate
  • configure service ipipe sap ingress queue-override queue rate

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

  • configure service cpipe sap egress queue-override queue rate
  • configure service cpipe sap ingress queue-override queue rate

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>service>cpipe>sap>ingress>sched-override>scheduler rate)

[Tree] (config>service>ipipe>sap>egress>sched-override>scheduler rate)

[Tree] (config>service>cpipe>sap>egress>sched-override>scheduler rate)

[Tree] (config>service>epipe>sap>ingress>sched-override>scheduler rate)

[Tree] (config>service>ipipe>sap>ingress>sched-override>scheduler rate)

[Tree] (config>service>epipe>sap>egress>sched-override>scheduler rate)

Full Context

configure service cpipe sap ingress scheduler-override scheduler rate

configure service ipipe sap egress scheduler-override scheduler rate

configure service cpipe sap egress scheduler-override scheduler rate

configure service epipe sap ingress scheduler-override scheduler rate

configure service ipipe sap ingress scheduler-override scheduler rate

configure service epipe sap egress scheduler-override scheduler rate

Description

This command can be used to override specific attributes of the specified scheduler rate. The rate command defines the maximum bandwidth that the scheduler can offer its child policers, queues or schedulers. The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent scheduler. If the scheduler has no parent, the maximum rate is assumed to be the amount available to the scheduler. When a parent is associated with the scheduler, the CIR parameter provides the amount of bandwidth to be considered during the parent scheduler’s 'within CIR’ distribution phase.

The actual operating rate of the scheduler is limited by bandwidth constraints other than its maximum rate. The scheduler’s parent scheduler may not have the available bandwidth to meet the scheduler’s needs or the bandwidth available to the parent scheduler could be allocated to other child schedulers or child policers or queues on the parent based on higher priority. The children of the scheduler may not need the maximum rate available to the scheduler due to insufficient offered load or limits to their own maximum rates.

When a scheduler is defined without specifying a rate, the default rate is max. If the scheduler is a root scheduler (no parent defined), the default maximum rate must be changed to an explicit value. Without this explicit value, the scheduler will assume that an infinite amount of bandwidth is available and allow all child policers, queues, and schedulers to operate at their maximum rates.

The no form of this command returns the scheduler’s PIR and CIR parameters to the values configured in the applied scheduler policy.

Parameters

pir-rate

The pir parameter accepts the max keyword or a value in kilobits per second. Any other value will result in an error without modifying the current PIR rate.

Values

1 to 6400000000, max

cir cir-rate

The cir parameter accepts a value in kilobits per second or the max keyword. Any other value will result in an error without modifying the current CIR rate.

If the cir parameter is set to max, then the CIR rate is set to infinity but bounded by the PIR rate.

The sum keyword specifies that the CIR will be used as the summed CIR values of the children schedulers, policers, or queues.

Values

0 to 6400000000, max, sum

Platforms

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

  • configure service cpipe sap egress scheduler-override scheduler rate
  • configure service cpipe sap ingress scheduler-override scheduler rate

All

  • configure service ipipe sap egress scheduler-override scheduler rate
  • configure service epipe sap ingress scheduler-override scheduler rate
  • configure service epipe sap egress scheduler-override scheduler rate
  • configure service ipipe sap ingress scheduler-override scheduler rate

rate

Syntax

rate kilobits-per-second

no rate

Context

[Tree] (config>service>template>vpls-sap-template>egress>agg-rate rate)

[Tree] (config>service>vpls>sap>egress>agg-rate rate)

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

Full Context

configure service template vpls-sap-template egress agg-rate rate

configure service vpls sap egress agg-rate rate

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

Description

This command defines the enforced aggregate rate for all queues associated with the agg-rate context. A rate must be specified for the agg-rate context to be considered active on the context’s object (SAP, subscriber, Vport, and so on.).

The no form of this command removes an explicit rate value from the aggregate rate returning it to its default value.

Parameters

kilobits-per-second

The enforced aggregate rate for all queues associated with the agg-rate context, in kilobits per second.

Values

1 to 6400000000, max

Platforms

All

rate

Syntax

rate {rate | max} [cir {max | rate}]

Context

[Tree] (config>service>vpls>sap>ingress>policer-override>plcr rate)

[Tree] (config>service>vpls>sap>egress>policer-override>plcr rate)

Full Context

configure service vpls sap ingress policer-override policer rate

configure service vpls sap egress policer-override policer rate

Description

This command within the SAP ingress and egress policer-overrides contexts is used to override the sap-ingress and sap-egress QoS policy configured rate parameters for the specified policer-id.

The no form of this command removes the rate override so that the rate configured for the policer in the applied SAP egress QoS policy is used.

Parameters

{rate | max}

Specifying the keyword max or an explicit kilobits per second parameter directly following the rate override command is required and identifies the policer instance’s metering rate for the PIR leaky bucket. The kilobits per second value must be expressed as an integer and defines the rate in kilobits per second. The integer value is multiplied by 1,000 to derive the actual rate in bits per second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the PIR used is equivalent to max.

Values

1 to 6400000000, max

cir {max | rate}

The optional cir keyword is used to override the policy derived profiling rate of the policer. Specifying the keyword max or an explicit kilobits per second parameter directly following the cir keyword is required. The kilobits per second value must be expressed as an integer and defines the rate in kilobits per second. The integer value is multiplied by 1,000 to derive the actual rate in bits per second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the CIR used is equivalent to max.

Values

0 to 6400000000, max

Platforms

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

rate

Syntax

rate rate

no rate

Context

[Tree] (config>service>vpls>sap>egress>queue-override>hs-wrr-group rate)

Full Context

configure service vpls sap egress queue-override hs-wrr-group rate

Description

This command overrides the scheduling rate applied to the HS WRR group in kb/s. Alternatively, the keyword max can be specified which removes the bandwidth limitation on the HS WRR group. The override rate type must match the corresponding rate type within the applied QoS policy.

The no form of this command removes the rate override value from the configuration.

Parameters

rate

Specifies the scheduling rate of the HS WRR group in kb/s.

Values

1 to 2000000000, max

Platforms

7750 SR-7/12/12e

rate

Syntax

rate {rate | max} [cir {max | rate}]

Context

[Tree] (config>service>ies>if>sap>ingress>policer-override>plcr rate)

[Tree] (config>service>ies>if>sap>egress>policer-override>plcr rate)

Full Context

configure service ies interface sap ingress policer-override policer rate

configure service ies interface sap egress policer-override policer rate

Description

This command within the SAP ingress and egress policer-overrides contexts is used to override the sap-ingress and sap-egress QoS policy configured rate parameters for the specified policer-id.

The no form of the command removes the rate override so that the rate configured for the policer in the applied SAP egress QoS policy is used.

Parameters

{rate | max}

Specifying the keyword max or an explicit kilobits per second parameter directly following the rate override command is required and identifies the policer instance’s metering rate for the PIR leaky bucket. The kilobits per second value must be expressed as an integer and defines the rate in kilobits per second. The integer value is multiplied by 1,000 to derive the actual rate in bits per second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the PIR used is equivalent to max.

Values

1 to 6400000000, max

cir {max | rate}

The optional cir keyword is used to override the policy derived profiling rate of the policer. Specifying the keyword max or an explicit kilobits per second parameter directly following the cir keyword is required. The kilobits per second value must be expressed as an integer and defines the rate in kilobits per second. The integer value is multiplied by 1,000 to derive the actual rate in bits per second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the CIR used is equivalent to max.

Values

0 to 6400000000, max

Platforms

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

rate

Syntax

rate rate

no rate

Context

[Tree] (config>service>ies>if>sap>egress>queue-override>hs-wrr-group rate)

Full Context

configure service ies interface sap egress queue-override hs-wrr-group rate

Description

This command overrides the scheduling rate applied to the HS WRR group in Kb/s. Alternatively, the keyword max can be specified which removes the bandwidth limitation on the HS WRR group. The override rate type must match the corresponding rate type within the applied QoS policy.

The no form of this command removes the rate override value from the configuration.

Parameters

rate

Specifies the scheduling rate of the HS WRR group in Kb/s.

Values

1 to 2000000000, max

Platforms

7750 SR-7/12/12e

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>service>ies>if>sap>egress>sched-override>scheduler rate)

[Tree] (config>service>ies>if>sap>ingress>sched-override>scheduler rate)

Full Context

configure service ies interface sap egress scheduler-override scheduler rate

configure service ies interface sap ingress scheduler-override scheduler rate

Description

This command can be used to override specific attributes of the specified scheduler rate. The rate command defines the maximum bandwidth that the scheduler can offer its child queues or schedulers. The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent scheduler. If the scheduler has no parent, the maximum rate is assumed to be the amount available to the scheduler. When a parent is associated with the scheduler, the CIR parameter provides the amount of bandwidth to be considered during the parent scheduler’s 'within CIR’ distribution phase.

The actual operating rate of the scheduler is limited by bandwidth constraints other than its maximum rate. The scheduler’s parent scheduler may not have the available bandwidth to meet the scheduler’s needs or the bandwidth available to the parent scheduler could be allocated to other child schedulers or child queues on the parent based on higher priority. The children of the scheduler may not need the maximum rate available to the scheduler due to insufficient offered load or limits to their own maximum rates.

When a scheduler is defined without specifying a rate, the default rate is max. If the scheduler is a root scheduler (no parent defined), the default maximum rate must be changed to an explicit value. Without this explicit value, the scheduler will assume that an infinite amount of bandwidth is available and allow all child queues and schedulers to operate at their maximum rates.

The no form of this command returns the scheduler's PIR and CIR parameters to the value configured in the applied scheduler policy.

Parameters

pir-rate

The pir parameter accepts a value in kilobits per second, or the keyword max. Any other value will result in an error without modifying the current PIR rate.

Values

1 to 6400000000, max

cir-rate

This parameter accepts a step-multiplier value that specifies the multiplier used to determine the CIR rate at which the queue will operate. A value in kilobits per second or the keywords max or sum is accepted. Any other value will result in an error without modifying the current CIR rate.

If the cir is set to max, then the CIR rate is set to infinity but is restricted by the PIR rate.

The sum keyword specifies that the CIR be used as the summed CIR values of the children schedulers, policers, or queues.

For egress>sched-override>scheduler and ingress>sched-override>scheduler:

Values

0 to 6400000000, max, sum

Platforms

All

rate

Syntax

rate kilobits-per-second

no rate

Context

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

Full Context

configure service vprn interface sap egress agg-rate rate

Description

This command defines the enforced aggregate rate for all queues associated with the agg-rate context. A rate must be specified for the agg-rate context to be considered to be active on the context’s object.

The no form of this command removes an explicit rate value from the aggregate rate returning it to its default value.

Parameters

kilobits-per-second

Specifies the rate limit for the SAP, in kilobits per second.

Values

1 to 6400000000, max

Platforms

All

rate

Syntax

rate {rate | max} [cir {max | rate}]

Context

[Tree] (config>service>vprn>if>sap>egress>policer-override>plcr rate)

[Tree] (config>service>vprn>if>sap>ingress>policer-override>plcr rate)

Full Context

configure service vprn interface sap egress policer-override policer rate

configure service vprn interface sap ingress policer-override policer rate

Description

This command within the SAP ingress and egress policer-overrides contexts is used to override the sap-ingress and sap-egress QoS policy configured rate parameters for the specified policer-id.

The no form of this command restores the policy defined metering and profiling rate to a policer.

Parameters

{rate | max}

Specifying the keyword max or an explicit kilobits per second parameter directly following the rate override command is required and identifies the policer instance’s metering rate for the PIR leaky bucket. The kilobits per second value must be expressed as an integer and defines the rate in kilobits per second. The integer value is multiplied by 1,000 to derive the actual rate in bits per second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the PIR used is equivalent to max.

Values

1 to 6400000000, max

cir {max | rate}

The optional cir keyword is used to override the policy derived profiling rate of the policer. Specifying the keyword max or an explicit kilobits per second parameter directly following the cir keyword is required. The kilobits per second value must be expressed as an integer and defines the rate in kilobits per second. The integer value is multiplied by 1,000 to derive the actual rate in bits per second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the CIR used is equivalent to max.

Values

0 to 6400000000, max

Platforms

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

rate

Syntax

rate rate

no rate

Context

[Tree] (config>service>vprn>if>sap>egress>queue-override>hs-wrr-group rate)

Full Context

configure service vprn interface sap egress queue-override hs-wrr-group rate

Description

This command overrides the scheduling rate applied to the HS WRR group in Kb/s. Alternatively, the keyword max can be specified which removes the bandwidth limitation on the HS WRR group. The override rate type must match the corresponding rate type within the applied QoS policy.

The no form of this command removes the rate override value from the configuration.

Parameters

rate

Specifies the scheduling rate of the HS WRR group in Kb/s.

Values

1 to 2000000000, max

Platforms

7750 SR-7/12/12e

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>service>vprn>if>sap>ingress>queue-override>queue rate)

[Tree] (config>service>vprn>if>sap>egress>queue-override>queue rate)

Full Context

configure service vprn interface sap ingress queue-override queue rate

configure service vprn interface sap egress queue-override queue rate

Description

This command can be used to override specific attributes of the specified queue’s Peak Information Rate (PIR) and the Committed Information Rate (CIR) parameters. The PIR defines the maximum rate that the queue can transmit packets out an egress interface (for SAP egress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth.

The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. In-profile packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse. To be properly handled throughout the network, the packets must be marked accordingly for profiling at each hop.

The CIR can be used by the queue’s parent commands cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.

The rate command can be executed at any time, altering the PIR and CIR rates for all queues created through the association of the SAP egress QoS policy with the queue-id.

This command is ignored for egress HSQ queue group queues which are attached to an HS WRR group within an associated HS attachment policy. In this case, the configuration of the rate is performed under the hs-wrr-group within the SAP egress QoS policy.

The no form of this command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).

Default

rate max cir 0

Parameters

pir-rate

Defines the administrative PIR rate, in kb/s, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed.

Fractional values are not allowed and must be given as a positive integer.

The actual PIR rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

1 to 6400000000, max

Default

max

cir-rate

Defines the administrative CIR rate, in kb/s, for the queue. The cir parameter overrides the default administrative CIR used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed.

Fractional values are not allowed and must be given as a positive integer.

Values

0 to 6400000000, max

Default

0

Platforms

All

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>service>vprn>if>sap>ingress>sched-override>scheduler rate)

[Tree] (config>service>vprn>if>sap>egress>sched-override>scheduler rate)

Full Context

configure service vprn interface sap ingress scheduler-override scheduler rate

configure service vprn interface sap egress scheduler-override scheduler rate

Description

This command can be used to override specific attributes of the specified scheduler rate. The rate command defines the maximum bandwidth that the scheduler can offer its child queues or schedulers. The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent scheduler. If the scheduler has no parent, the maximum rate is assumed to be the amount available to the scheduler. When a parent is associated with the scheduler, the CIR parameter provides the amount of bandwidth to be considered during the parent scheduler’s 'within CIR’ distribution phase.

The actual operating rate of the scheduler is limited by bandwidth constraints other than its maximum rate. The scheduler’s parent scheduler may not have the available bandwidth to meet the scheduler’s needs or the bandwidth available to the parent scheduler could be allocated to other child schedulers or child policers and queues on the parent based on higher priority. The children of the scheduler may not need the maximum rate available to the scheduler due to insufficient offered load or limits to their own maximum rates.

When a scheduler is defined without specifying a rate, the default rate is max. If the scheduler is a root scheduler (no parent defined), the default maximum rate must be changed to an explicit value. Without this explicit value, the scheduler will assume that an infinite amount of bandwidth is available and allow all child queues and schedulers to operate at their maximum rates.

The no form of this command returns the scheduler's PIR and CIR parameters to the value configured in the applied scheduler policy.

Parameters

pir-rate

Specifies the PIR rate for the scheduler. The pir parameter accepts a value in kb/s, or the max keyword. Any other value will result in an error without modifying the current PIR rate.

Values

1 to 6400000000, max

cir-rate

Specifies the CIR rate for the scheduler. The cir parameter accepts a value in kb/s, or the max or sum keywords. Any other value will result in an error without modifying the current CIR rate.

If the cir is set to max, then the CIR rate is set to infinity, but is limited by the pir-rate.

If the cir is set to sum, then the CIR rate is set to the summed CIR values of the children schedulers, policers, or queues.

Values

0 to 6400000000, max, sum

Platforms

All

rate

Syntax

rate sample-rate

no rate

Context

[Tree] (config>app-assure>group>cflowd>volume rate)

Full Context

configure application-assurance group cflowd volume rate

Description

This command configures the sampling rate of packets for the cflowd export of application assurance volume statistics.

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

Parameters

sample-rate

Specifies the rate at which to sample packets for the cflowd export of application assurance volume statistics.

Values

1 to 10000

Platforms

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

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>app-assure>group>policer rate)

[Tree] (config>app-assure>group>tod-override rate)

Full Context

configure application-assurance group policer rate

configure application-assurance group policer tod-override rate

Description

This command configures the administrative PIR and CIR for bandwidth policers and flow setup rate limits for flow policers. The actual rate sustained by the flow can be limited by other policers that may be applied to that flow’s traffic. This command does not apply to flow-count-limit policers.

The cir option is applicable only to dual-bucket bandwidth policers. It is recommended to configure flow setup rate subscriber-level policer for AA subscribers to ensure fair usage of flow resources between AA subscribers.

The no form of this command resets the values to defaults.

Default

rate max cir 0

Parameters

pir-rate

Specifies an integer for the PIR rate in kb/s for bandwidth policers.

Values

1 to 100000000, max or flows/sec

cir-rate

Specifies an integer for the CIR rate in kb/s.

Values

0 to 100000000, max

Platforms

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

rate

Syntax

rate sample-rate

no rate

Context

[Tree] (debug>app-assure>group>port-recorder rate)

[Tree] (debug>app-assure>group>http-host-recorder rate)

Full Context

debug application-assurance group port-recorder rate

debug application-assurance group http-host-recorder rate

Description

This command configures the sampling rate for the recorded http host, a sampling rate of 10 will sample one out of 10 http-host.

Parameters

sample-rate

Specifies the sample rate.

Values

1 to 10000

Default

100

Platforms

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

Output

The following output is an example of a configuration with http-host entries ending with ".com” as a result of the expression filter configuration. It will not record any other HTTP host values since the default-filter-action set to no-record. The http-host entries analyzed by the recorder in the first place are http-host-app-filter-candidates.

Output Example
7750# show debug                                             
debug
    application-assurance
        group 1:1
            http-host-recorder
                filter
                    default-filter-action no-record
                    expression 1 http-host eq "*.com$" record
                    record http-host-app-filter-candidates
                exit
                rate 100
                no shutdown
            exit
        exit
    exit
exit

rate

Syntax

rate rate

no rate

Context

[Tree] (config>qos>plcr-ctrl-plcy>tier>arbiter rate)

Full Context

configure qos policer-control-policy tier arbiter rate

Description

This command is used to define the maximum bandwidth an instance of the arbiter can receive from its parent tier 1 arbiter or the root arbiter. The arbiter instance enforces this limit by calculating the bandwidth each of its child policers should receive relative to their offered loads, parenting parameters, and individual rate limits, and using that derived rate as a child PIR decrement rate override. The override will not exceed the child policer’s administrative rate limit and the aggregate of all the child PIR decrement rates will not exceed the specified arbiter rate limit.

The arbiter’s policy defined rate value may be overridden at the SAP or sub-profile where the policer-control-policy is applied. Specifying an override prevents the arbiter from being removed from the policer control policy until the override is removed.

The no form of this command is used to remove a rate limit from the arbiter at the policer control policy level. The policy level rate limit for the arbiter will return to the default value of max. The no rate command has no effect on instances of the arbiter where a rate limit override has been defined.

Default

rate max

Parameters

rate

Enter an integer representing the rate limit in kilobits per second.

Values

1 to 6400000000, max

max

When max is specified, the arbiter does not enforce a rate limit on its child policers or arbiters other than the individual rate limits enforced at the child level.

Platforms

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

rate

Syntax

rate {max | pir-rate} [cir {max | cir-rate}]

Context

[Tree] (config>qos>sap-ingress>policer rate)

[Tree] (config>qos>sap-egress>policer rate)

Full Context

configure qos sap-ingress policer rate

configure qos sap-egress policer rate

Description

This command is used to configure the policer’s metering and optional profiling rates. The metering rate is used by the system to configure the policer’s PIR leaky bucket’s decrement rate while the profiling rate configures the policer’s CIR leaky bucket’s decrement rate. The decrement function empties the bucket while packets applied to the bucket attempt to fill it based on each packet’s size. If the bucket fills faster than how much is decremented per packet, the bucket’s depth eventually reaches its exceed (CIR) or violate (PIR) threshold. The cbs, mbs, and high-prio-only commands are used to configure the policer’s PIR and CIR thresholds.

If a packet arrives at the policer while the bucket’s depth is less than the threshold associated with the packet, the packet is considered to be conforming to the bucket’s rate. If the bucket depth is equal to or greater than the threshold, the packet is considered to be in the exception state. For the CIR bucket, the exception state is exceeding the CIR rate while the PIR bucket's exception state is violating the PIR bucket rate. If the packet is violating the PIR, the packet is marked red and will be discarded. If the packet is not red, it may be green or yellow, based on the conforming or exceeding state from the CIR bucket.

When a packet is red, neither the PIR nor CIR bucket depths are incremented by the packets size. When the packet is yellow, the PIR bucket is incremented by the packet size, but the CIR bucket is not. When the packet is green, both the PIR and CIR buckets are incremented by the packet size. This ensures that conforming packets impact the bucket depth while exceeding or violating packets do not.

The policer’s adaptation-rule command settings are used by the system to convert the specified rates into hardware timers and decrement values for the policer’s buckets.

By default, the policer’s metering rate is max and the profiling rate is 0 kb/s (all packets out-of-profile).

The rate settings defined for the policer in the QoS policy may be overridden on an sla-profile or SAP where the policy is applied.

The no form of this command is used to restore the default metering and profiling rate to a policer.

Parameters

{max | pir-rate}

Specifying the keyword max or an explicit pir-rate parameter directly following the rate command is required and identifies the policer’s metering rate for the PIR leaky bucket. When the policer is first created, the metering rate defaults to max. The pir-rate value must be expressed as an integer and defines the rate in kilobits-per-second. The integer value is multiplied by 1,000 to derive the actual rate in bits-per-second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the PIR used is equivalent to max.

Values

1 to 6400000000, max

cir {max | cir-rate}

The optional cir keyword is used to override the default CIR rate of the policer. Specifying the keyword max or an explicit cir-rate parameter directly following the cir keyword is required and identifies the policer’s profiling rate for the CIR leaky bucket. When the policer is first created, the profiling rate defaults to 0 kb/s. The cir-rate value must be expressed as an integer and defines the rate in kilobits-per-second. The integer value is multiplied by 1,000 to derive the actual rate in bits-per-second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the CIR used is equivalent to max.

Values

0 to 6400000000, max

Platforms

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

rate

Syntax

rate pir-rate [cir cir-rate] [fir fir-rate]

rate pir-rate police

no rate

Context

[Tree] (config>qos>sap-ingress>queue rate)

Full Context

configure qos sap-ingress queue rate

Description

This command defines the administrative Peak Information Rate (PIR), the administrative Committed Information Rate (CIR), and the administrative Fair Information Rate (FIR) parameters for the queue.

The PIR defines the maximum rate that the queue can transmit packets through the switch fabric (for SAP ingress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth.

The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. For SAP ingress, the CIR also defines the rate that packets are considered in-profile by the system, unless cir-non-profiling is configured. In-profile, then out-of-profile, packets are preferentially queued by the system at egress and at subsequent next-hop nodes where the packet can traverse. To be properly handled throughout the network, the packets must be marked accordingly for profiling at each hop.

The CIR can be used by the queue’s parent commands cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.

The FIR defines an additional rate at which the system prioritizes the queue over other queues competing for the same bandwidth above that used by the CIR.

The rate command can be executed at any time, altering the PIR, CIR, and FIR for all queues created through the association of the SAP ingress QoS policy with the queue-id.

The no form of this command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0, 0).

Default

rate max cir 0 fir 0

Parameters

pir-rate

Defines the administrative PIR, in kilobits per second, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed.

Fractional values are not allowed and the value must be given as a positive integer.

The actual PIR is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

1 to 6400000000, max

Default

max

cir-rate

The cir parameter overrides the default administrative CIR, in kilobits per second, used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed.

Fractional values are not allowed and the value must be given as a positive integer. The actual CIR used is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

0 to 6400000000, max

Default

0

fir-rate

The fir parameter overrides the default administrative FIR, in kilobits per second, used by the queue. When the rate command is executed, an FIR setting is optional. When the rate command has not been executed or the fir parameter is not explicitly specified, the default FIR (0) is assumed.

Fractional values are not allowed and the value must be given as a positive integer. The actual FIR used is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

FIR is only supported on FP4 hardware and is ignored when the related policy is applied to FP2- or FP3-based hardware.

Values

0 to 6400000000, max

Default

0

police

Specifies that traffic feeding into the queue instance above the specified PIR rate will be dropped. When the police keyword is defined, only the PIR rate may be overridden.

Platforms

All

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>qos>sap-egress>queue rate)

Full Context

configure qos sap-egress queue rate

Description

This command defines the administrative Peak Information Rate (PIR) and the administrative Committed Information Rate (CIR) parameters for the queue. The PIR defines the maximum rate that the queue can transmit packets out an egress interface (for SAP egress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth.

The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. In-profile packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse. To be properly handled as in- or out-of-profile throughout the network, the packets must be marked accordingly for profiling at each hop.

The CIR can be used by the queue’s parent commands cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.

The rate command can be executed at any time, altering the PIR and CIR rates for all queues created through the association of the SAP egress QoS policy with the queue-id.

When configured on an egress HSQ queue group queue, the cir keyword is ignored.

This command is ignored for egress HSQ queue group queues which are attached to an HS WRR group within an associated HS attachment policy. In this case, the configuration of the rate is performed under the hs-wrr-group within the SAP egress QoS policy.

The no form of this command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).

Default

rate max cir 0

Parameters

pir-rate

Defines the administrative PIR rate, in kilobits per second, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed.

Fractional values are not allowed and must be given as a positive integer.

The actual PIR rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

1 to 6400000000, max

Default

max

cir-rate

The cir parameter overrides the default administrative CIR, in kilobits per second, used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed.

Fractional values are not allowed and must be given as a positive integer.

Values

0 to 6400000000, max

Default

0

Platforms

All

rate

Syntax

rate percent

no rate

Context

[Tree] (config>qos>network-queue>hs-wrr-group rate)

Full Context

configure qos network-queue hs-wrr-group rate

Description

This command specifies the scheduling rate applied to the HS WRR group as a percentage of the port rate, which includes both the egress-rate and HS scheduler policy max-rate, if configured.

The no form of the command reverts to the default.

Default

rate 100

Parameters

percent

Specifies the scheduling rate of the HS WRR group as a percentage.

Values

1 to 100

Platforms

7750 SR-7/12/12e

rate

Syntax

rate rate

no rate

Context

[Tree] (config>qos>sap-egress>hs-wrr-group rate)

Full Context

configure qos sap-egress hs-wrr-group rate

Description

This command specifies the scheduling rate applied to the HS WRR group in kb/s. Alternatively, the keyword max can be specified, which removes the bandwidth limitation on the HS WRR group. The rate and percent-rate commands are mutually exclusive.

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

Default

rate max

Parameters

rate

Specifies the scheduling rate of the HS WRR group in kb/s.

Values

1 to 2000000000, max

Platforms

7750 SR-7/12/12e

rate

Syntax

rate rate

no rate

Context

[Tree] (config>qos>qgrps>egr>qgrp>hs-wrr-group rate)

Full Context

configure qos queue-group-templates egress queue-group hs-wrr-group rate

Description

This command specifies the scheduling rate applied to the HS WRR group in kb/s. Alternatively, the keyword max can be specified, which removes the bandwidth limitation on the HS WRR group. The rate and percent-rate commands are mutually exclusive.

The no form of the command reverts to the rate max.

Default

rate max

Parameters

rate

Specifies the scheduling rates of the HS WRR group in kb/s.

Values

1 to 2000000000, max

Platforms

7750 SR-7/12/12e

rate

Syntax

rate percent [cir percent] [fir percent]

no rate

Context

[Tree] (config>qos>network-queue>queue rate)

Full Context

configure qos network-queue queue rate

Description

This command defines the administrative Peak Information Rate (PIR), the administrative Committed Information Rate (CIR), and the administrative Fair Information Rate (FIR) parameters for the queue.

The PIR defines the percentage that the queue can transmit packets through the switch fabric (for ingress queues) or out of an egress port (for egress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available bandwidth.

The CIR defines the percentage at which the system prioritizes the queue over other queues competing for the same bandwidth.

The CIR can be used by the queue’s port-parent commands cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent port scheduler.

The FIR defines an additional percentage at which the system prioritizes the queue over other queues competing for the same bandwidth above that used by the CIR percentage.

The rate command can be executed at any time, altering the PIR, CIR, and FIR for all queues created through the association of the network queue policy with the queue-id.

When configured on an egress HSQ queue group queue, the cir keyword is ignored.

This command is ignored for egress HSQ queue group queues which are attached to an HS WRR group within an associated HS attachment policy. In this case, the configuration of the rate is performed under the hs-wrr-group within the network queue policy.

The no form of the command returns all queues created with the queue-id by association with the network queue policy to the default PIR, CIR, and FIR parameters.

Default

rate 100 cir 0 fir 0

Parameters

percent

Defines the percentage of the sum of the capacities of network and hybrid ports on that FP (taking into account any ingress-rate configuration) or egress port speed for the rate allowed for the queue. When the rate command is executed, a valid percent (PIR setting) must be explicitly defined. When the rate command has not been executed, the default PIR of 100 is assumed. Fractional values are not allowed, and the value must be given as a positive integer.

The actual PIR used is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

1 to 100

Default

100

cir percent

Defines the percentage of the sum of the capacities of network and hybrid ports on that FP (taking into account any ingress-rate configuration) or egress port speed for the CIR allowed for the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed. Fractional values are not allowed, and the value must be given as a positive integer. The actual CIR used is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

0 to 100

Default

0

fir percent

Defines the percentage of the sum of the capacities of network and hybrid ports on that FP (taking into account any ingress-rate configuration) or egress port speed for the FIR allowed for the queue. When the rate command is executed, a FIR setting is optional. When the rate command has not been executed or the fir parameter is not explicitly specified, the default FIR (0) is assumed. Fractional values are not allowed, and the value must be given as a positive integer. The actual FIR used is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned. FIR is only supported on FP4 hardware and is ignored when the related policy is applied to FP2- or FP3-based hardware.

Values

0 to 100

Default

0

Platforms

All

rate

Syntax

rate {max | pir-rate} [cir {max | cir-rate}]

no rate

Context

[Tree] (config>qos>qgrps>ing>qgrp>policer rate)

[Tree] (config>qos>qgrps>egr>qgrp>policer rate)

Full Context

configure qos queue-group-templates ingress queue-group policer rate

configure qos queue-group-templates egress queue-group policer rate

Description

This command is used to configure the policer’s metering and optional profiling rates. The metering rate is used by the system to configure the policer’s PIR leaky bucket’s decrement rate while the profiling rate configures the policer’s CIR leaky bucket’s decrement rate. The decrement function empties the bucket while packets applied to the bucket attempt to fill it based on each packet’s size. If the bucket fills faster than how much is decremented per packet, the bucket’s depth eventually reaches its exceed (CIR) or violate (PIR) threshold. The cbs, mbs, and high-prio-only commands are used to configure the policer’s PIR and CIR thresholds.

If a packet arrives at the policer while the bucket’s depth is less than the threshold associated with the packet, the packet is considered to be conforming to the bucket’s rate. If the bucket depth is equal to or greater than the threshold, the packet is considered to be in the exception state. For the CIR bucket, the exception state is exceeding the CIR rate while the PIR bucket's exception state is violating the PIR bucket rate. If the packet is violating the PIR, the packet is marked red and will be discarded. If the packet is not red, it may be green or yellow, based on the conforming or exceeding state from the CIR bucket.

When a packet is red, neither the PIR nor CIR bucket depths are incremented by the packets size. When the packet is yellow, the PIR bucket is incremented by the packet size, but the CIR bucket is not. When the packet is green, both the PIR and CIR buckets are incremented by the packet size. This ensures that conforming packets impact the bucket depth while exceeding or violating packets do not.

The policer’s adaptation-rule command settings are used by the system to convert the specified rates into hardware timers and decrement values for the policer’s buckets.

By default, the policer’s metering rate is max and the profiling rate is 0 kb/s (all packets out-of-profile).

The no form of this command is used to restore the default metering and profiling rate to a policer.

Parameters

{max | pir-rate}

Specifying the keyword max or an explicit pir-rate parameter directly following the rate command is required and identifies the policer’s metering rate for the PIR leaky bucket. When the policer is first created, the metering rate defaults to max. The pir-rate value must be expressed as an integer and defines the rate in kilobits-per-second. The integer value is multiplied by 1,000 to derive the actual rate in bits-per-second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the PIR used is equivalent to max.

Values

max, 1 to 2000000000

cir {max | cir-rate}

The optional cir keyword is used to override the default CIR rate of the policer. Specifying the keyword max or an explicit cir-rate parameter directly following the cir keyword is required and identifies the policer’s profiling rate for the CIR leaky bucket. When the policer is first created, the profiling rate defaults to 0 kb/s. The cir-rate value must be expressed as an integer and defines the rate in kilobits-per-second. The integer value is multiplied by 1,000 to derive the actual rate in bits-per-second. When max is specified, the maximum policer rate used will be equal to the maximum capacity of the card on which the policer is configured. If the policer rate is set to a value larger than the maximum rate possible for the card, then the CIR used is equivalent to max.

Values

max, 0 to 2000000000

Platforms

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

rate

Syntax

rate pir-rate [cir cir-rate] [fir fir-rate]

rate pir-rate police

no rate

Context

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

Full Context

configure qos queue-group-templates ingress queue-group queue rate

Description

This command defines the administrative Peak Information Rate (PIR), the administrative Committed Information Rate (CIR), and the administrative Fair Information Rate (FIR) parameters for the queue. The PIR defines the maximum rate that the queue can transmit packets through the switch fabric (for SAP ingress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth.

The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. For SAP ingress, the CIR also defines the rate that packets are considered in-profile by the system, unless cir-non-profiling is configured. In-profile, then out-of-profile, packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse. To be properly handled throughout the network, the packets must be marked accordingly for profiling at each hop.

The CIR can be used by the queue’s parent commands cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.

The FIR defines an additional rate at which the system prioritizes the queue over other queues competing for the same bandwidth above that used by the CIR.

The rate command can be executed at any time, altering the PIR, CIR, and FIR for all queues created through the association of the ingress queue group template with the queue-id.

The no form of this command returns all queues created with the queue-id by association with the QoS policy to the default PIR, CIR, and FIR parameters (max, 0, 0).

Default

rate max cir 0 fir 0

Parameters

pir-rate

Defines the administrative PIR, in kilobits, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. Fractional values are not allowed and the value must be given as a positive integer.

The actual PIR is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

1 to 2000000000 kb/s, max

Default

max

cir-rate

The cir parameter overrides the default administrative CIR used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed. Fractional values are not allowed and the value must be given as a positive integer. The actual CIR used is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

1 to 2000000000 kb/s, max

Default

0

fir-rate

The fir parameter overrides the default administrative FIR used by the queue. When the rate command is executed, an FIR setting is optional. When the rate command has not been executed or the fir parameter is not explicitly specified, the default FIR (0) is assumed.

Fractional values are not allowed and the value must be given as a positive integer. The actual FIR used is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

FIR is only supported on FP4 hardware and is ignored when the related policy is applied to FP2- or FP3-based hardware.

Values

1 to 2000000000 kb/s, max

Default

0

police

Specifies that traffic feeding into the queue instance above the specified rate is dropped.

Platforms

All

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

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

Full Context

configure qos queue-group-templates egress queue-group queue rate

Description

This command defines the administrative PIR and the administrative CIR parameters for the queue. The PIR defines the maximum rate that the queue can transmit packets out an egress port. Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by oversubscription factors or available egress bandwidth.

The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth. In-profile packets are preferentially queued by the system at egress and at subsequent next hop nodes where the packet can traverse. To be properly handled as in- or out-of-profile throughout the network, the packets must be marked accordingly for profiling at each hop.

The CIR can be used by the queue’s parent commands cir-level and cir-weight parameters to define the amount of bandwidth considered to be committed for the child queue during bandwidth allocation by the parent scheduler.

The rate command can be executed at any time, altering the PIR and CIR for all queues created through the association of the egress queue group template with the queue-id.

When configured on an egress HSQ queue group queue, the cir keyword is ignored.

This command is ignored for egress HSQ queue group queues which are attached to an HS WRR group within an associated HS attachment policy. In this case, the configuration of the rate is performed under the hs-wrr-group within the SAP egress QoS policy.

The no form of this command returns all queues created with the queue-id by association with the QoS policy to the default PIR and CIR parameters (max, 0).

Default

rate max cir 0

Parameters

pir-rate

Defines the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed.

Fractional values are not allowed and must be given as a positive integer.

The actual PIR rate is dependent on the queue’s adaptation-rule parameters and the actual hardware where the queue is provisioned.

Values

1 to 200000000 kb/s, max

Default

max

cir-rate

The cir parameter overrides the default administrative CIR used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed.

Fractional values are not allowed and must be given as a positive integer.

Values

0 to 200000000 kb/s, max

Default

0

Platforms

All

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>qos>scheduler-policy>tier>scheduler rate)

Full Context

configure qos scheduler-policy tier scheduler rate

Description

The rate command defines the maximum bandwidth that the scheduler can offer its child queues or schedulers. The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent scheduler. If the scheduler has no parent, the maximum rate is assumed to be the amount available to the scheduler. When a parent is associated with the scheduler, the CIR parameter provides the amount of bandwidth to be considered during the parent scheduler’s within-CIR distribution phase.

The actual operating rate of the scheduler is limited by bandwidth constraints other than its maximum rate. The scheduler’s parent scheduler may not have the available bandwidth to meet the scheduler’s needs or the bandwidth available to the parent scheduler could be allocated to other child schedulers or child queues on the parent based on higher priority. The children of the scheduler may not need the maximum rate available to the scheduler due to insufficient offered load or limits to their own maximum rates.

When a scheduler is defined without specifying a rate, the default rate is max. If the scheduler is a root scheduler (no parent defined), the default maximum rate must be changed to an explicit value. Without this explicit value, the scheduler will assume that an infinite amount of bandwidth is available and allow all child queues and schedulers to operate at their maximum rates.

The no form of this command returns the scheduler's PIR and CIR parameters to the value configured in the applied scheduler policy.

Parameters

pir pir

Specifies the PIR rate of the scheduler in kb/s or it can be set to the maximum using the max keyword.

Values

1 to 6400000000, max

Default

max

cir cir

Specifies the CIR rate of the scheduler in kb/s or it can be set to the maximum using the max keyword. The sum keyword can also be used, which sets the CIR to the sum of child CIR values.

Values

0 to 6400000000, max, sum

Default

sum

Platforms

All

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

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

Full Context

configure qos port-scheduler-policy group rate

Description

This command specifies the total bandwidth and the within-CIR bandwidth allocated to a weighted scheduler group.

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

Parameters

pir-rate

Specifies PIR rates, in kilobits per second.

Values

1 to 6400000000, max

cir cir-rate

Specifies CIR rates, in kilobits per second.

Values

0 to 6400000000, max

Platforms

All

rate

Syntax

rate percent [cir percent] [fir percent]

no rate

Context

[Tree] (config>qos>shared-queue>queue rate)

Full Context

configure qos shared-queue queue rate

Description

This command defines the administrative PIR, the administrative CIR, and the administrative FIR parameters for the queue.

The PIR defines the percentage that the queue can transmit packets through the switch fabric (for ingress queues). Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by over-subscription factors or available bandwidth.

The CIR defines the percentage at which the system prioritizes the queue over other queues competing for the same bandwidth.

The rate command can be executed at any time, altering the PIR, CIR, and FIR for the queue created with the queue-id.

Parameters

percent

Defines the percentage of the FP ingress capacity for the max rate allowed for the queue. When the rate command is executed, a valid percent (PIR) setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. Fractional values are not allowed and the value must be given as a positive integer.

Values

1 to 100, max

Default

100

cir percent

Defines the percentage of the FP ingress capacity for the CIR allowed for the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed. Fractional values are not allowed and the value must be given as a positive integer.

Values

0 to 100, max

Default

0

fir percent

Defines the percentage of the FP ingress capacity for the FIR allowed for the queue. When the rate command is executed, a FIR setting is optional. When the rate command has not been executed or the fir parameter is not explicitly specified, the default FIR (0) is assumed. Fractional values are not allowed and the value must be given as a positive integer. FIR is only supported on FP4 hardware and is ignored when the related policy is applied to FP2- or FP3-based hardware.

Values

0 to 100

Default

0

Platforms

All

rate

Syntax

rate sample-rate

no rate

Context

[Tree] (config>cflowd rate)

Full Context

configure cflowd rate

Description

This command specifies the rate (N) at which traffic is sampled and sent for flow analysis. A packet is sampled every N packets; for example, when sample-rate is configured as 1, then all packets are sent to the cache. When sample-rate is configured as 100, then every 100th packet is sent to the cache.

The no form of this command resets the sample rate to the default value.

Default

rate 1000

Parameters

sample-rate

Specifies the rate at which traffic is sampled.

Values

1 to 10000

Platforms

All

rate

Syntax

rate kilobits-per-second

no rate

Context

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

Full Context

configure service customer multi-service-site egress agg-rate rate

Description

This command defines the enforced aggregate rate for all queues associated with the agg-rate context. A rate must be specified for the agg-rate context to be considered to be active on the context’s object.

The no form of the command reverts to the default.

Parameters

kilobits-per-second

Specifies the rate limit for the multi-service site, in kilobits per second.

Values

1 to 6400000000, max

Platforms

All

rate

Syntax

rate pir-rate [cir cir-rate]

no rate

Context

[Tree] (config>service>cust>multi-service-site>ingress>sched-override>scheduler rate)

[Tree] (config>service>cust>multi-service-site>egress>sched-override>scheduler rate)

Full Context

configure service customer multi-service-site ingress scheduler-override scheduler rate

configure service customer multi-service-site egress scheduler-override scheduler rate

Description

This command overrides specific attributes of the specified scheduler rate.

The rate command defines the maximum bandwidth that the scheduler can offer its child policers, queues or schedulers. The maximum rate is limited to the amount of bandwidth the scheduler can receive from its parent scheduler. If the scheduler has no parent, the maximum rate is assumed to be the amount available to the scheduler. When a parent is associated with the scheduler, the CIR parameter provides the scheduler’s amount of bandwidth to be considered during the parent schedulers 'within CIR’ distribution phase.

The actual operating rate of the scheduler is limited by bandwidth constraints other than its maximum rate. The scheduler’s parent scheduler may not have the available bandwidth to meet the scheduler’s needs or the bandwidth available to the parent scheduler could be allocated to other child schedulers or child policers or queues on the parent based on higher priority. The children of the scheduler may not need the maximum rate available to the scheduler due to insufficient offered load or limits to their own maximum rates.

When a scheduler is defined without specifying a rate, the default rate is max. If the scheduler is a root scheduler (no parent defined), the default maximum rate must be changed to an explicit value. Without this explicit value, the scheduler will assume that an infinite amount of bandwidth is available and allow all child queues and schedulers to operate at their maximum rates.

The no form of this command returns the scheduler’s to the PIR and CIR parameters to the value configured in the applied scheduler policy.

Parameters

pir-rate

Specifies the PIR rate.

Values

1 to 6400000000, max

Default

max

cir-rate

Specifies the CIR rate.

If the cir-rate is set to max, then the CIR rate is set to infinity. The sum keyword specifies that the CIR be used as the summed CIR values of the children schedulers, policers or queues.

Values

0 to 6400000000, max, sum

Default

sum

Platforms

All

rate

Syntax

rate rate [cir cir]

no rate

Context

[Tree] (config>system>security>cpm-queue>queue rate)

Full Context

configure system security cpm-queue queue rate

Description

This command specifies the maximum bandwidth that will be made available to the queue in kilobits per second (kb/s).

Parameters

rate

Specifies the administrative Peak Information Rate (PIR) for the queue.

cir

Specifies the amount of bandwidth committed to the queue.

Platforms

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

rate

Syntax

rate kbps {kilobits-per-second | max} [mbs size] [bytes | kilobytes]

rate packets {ppi | max} within seconds [initial-delay packets]

no rate

Context

[Tree] (config>sys>security>dist-cpu-protection>policy>local-monitoring-policer rate)

[Tree] (config>sys>security>dist-cpu-protection>policy>protocol>dynamic-parameters rate)

Full Context

configure system security dist-cpu-protection policy local-monitoring-policer rate

configure system security dist-cpu-protection policy protocol dynamic-parameters rate

Description

This command configures the rate and burst tolerance for the policer in either a packet rate or a bit rate.

The actual hardware may not be able to perfectly rate limit to the exact configured parameters. In this case, the configured parameters will be adapted to the closest supported rate. The actual (operational) parameters can be seen in CLI, for example, show service id 33 sap 1/1/3:33 dist-cpu-protection detail.

If the kilobits-per-second parameter value is configured as max, then the policer is effectively disabled (always conforming).

If the size parameter value is configured as 0, then all packets are considered as nonconforming.

Default

rate packets max within 1 initial-delay 0

Parameters

packets | kbps

specifies that the rate is either in units of packets per interval or in units of kilobits per second. The packets option would typically be used for lower rates (for example, for per-subscriber DHCP rate limiting) while the kbps option would typically be used for higher rates (for example, per-interface BGP rate limiting).

ppi

Specifies packets per interval.

Values

0 to 255, max

max = disable the policer (always conforming)

packets 0 = all packets considered nonconforming

seconds

Specifies the length of the ppi rate measurement interval.

Values

1 to 32767

packets

Specifies the number of packets allowed (even at line rate) in an initial burst (or a burst after the policer bucket has drained to zero) in addition to the normal ppi. This would typically be set to a value that is equal to the number of received packets in several full handshakes/negotiations of the particular protocol.

Values

0 to 255

kilobits-per-second

Specifies the kilobits per second.

Values

1 to 20000000, max

size

Specifies the tolerance for the kbps rate.

Values

0 to 4194304

Default

10

bytes | kilobytes

Specifies that the units of the mbs size parameter are either in bytes or kilobytes.

Platforms

All

rate

Syntax

rate kbps {kilobits-per-second | max} [mbs size] [bytes | kilobytes]

rate packets {ppi | max} within seconds [initial-delay packets]

no rate

Context

[Tree] (config>sys>security>dist-cpu-protection>policy>static-policer rate)

Full Context

configure system security dist-cpu-protection policy static-policer rate

Description

This command configures the rate and burst tolerance for the policer in either a packet rate or a bit rate.

The actual hardware may not be able to perfectly rate limit to the exact configured parameters. In this case, the configured parameters will be adapted to the closest supported rate. The actual (operational) parameters can be seen in CLI, for example, show service id 33 sap 1/1/3:33 dist-cpu-protection detail.

If the kilobits-per-second parameter value is configured as max, then the policer is effectively disabled (always conforming).

If the size parameter is configured as 0, then all packets are considered as nonconforming.

Default

rate packets max within 1 initial-delay 0

Parameters

packets | kbps

specifies that the rate is either in units of packets per interval or in units of kilobits per second. The packets option would typically be used for lower rates (for example, for per-subscriber DHCP rate limiting) while the kbps option would typically be used for higher rates (for example, per-interface BGP rate limiting).

ppi

Specifies packets per interval.

Values

0 to 8000, max

max = disable the policer (always conforming)

packets 0 = all packets considered nonconforming

seconds

Specifies the length of the ppi rate measurement interval.

Values

1 to 32767

packets

Specifies the number of packets allowed (even at line rate) in an initial burst (or a burst after the policer bucket has drained to zero) in addition to the normal ppi. This would typically be set to a value that is equal to the number of received packets in several full handshakes/negotiations of the particular protocol.

Values

0 to 255

kilobits-per-second

Specifies the kilobits per second.

Values

1 to 20000000, max

size

Specifies the tolerance for the kbps rate.

Values

0 to 4194304

Default

10

bytes | kilobytes

Specifies that the units of the mbs size parameter are either in bytes or kilobytes.

Platforms

All

rate

Syntax

rate cir cir-rate-in-kbps [pir pir-rate-in-kbps]

no rate

Context

[Tree] (config>test-oam>sath>svc-test>svc-stream rate)

Full Context

configure test-oam service-activation-testhead service-test service-stream rate

Description

This command configures the CIR that must be validated for a specific stream. If configured, the PIR value must be greater than or equal to the CIR value.

The service activation testhead generates traffic up to the specified rate based on the test-types command, as follows.

  • For type cir, traffic is generated at a rate up to the configured CIR.

  • For type cir-pir, traffic is generated at a rate up to the configured PIR.

  • For type policing, traffic is generated at a rate up to 125% of the configured PIR.

  • For type performance, traffic is generated at a rate up to the configured PIR.

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

Default

no rate

Parameters

cir-rate-in-kbps

Specifies the CIR rate, in kb/s, which overrides the default CIR value. The configured value must be a positive integer; fractional values are not allowed. If the rate command is not executed, or the CIR parameter is not explicitly specified, the default CIR value applies.

Values

1 to 400,000,000

pir-rate-in-kbps

Specifies the PIR rate, in kb/s, which overrides the default administrative PIR value. The configured value must be a positive integer; fractional values are not allowed. If the rate command is not executed or the PIR parameter is not explicitly specified, the default PIR value applies.

Values

1 to 400,000,000

Platforms

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

rate-adjustment

rate-adjustment

Syntax

rate-adjustment adjusted-percent

no rate-adjustment

Context

[Tree] (config>subscr-mgmt>ancp>policy>ingress rate-adjustment)

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

Full Context

configure subscriber-mgmt ancp ancp-policy ingress rate-adjustment

configure subscriber-mgmt ancp ancp-policy egress rate-adjustment

Description

This command configures a rate adjustment for the scheduler. The rate-adjustment command should be used when the rate returned by the DSLAM is calculated with different encapsulation than the 7450 ESS or 7750 SR. The node will adjust the rate by the percent specified as:

DSLAM_RATE*adjust-rate/100 — rate-reduction.

The no form of this command reverts to the default.

Parameters

adjusted-percent

Specifies a rate adjustment for the scheduler.

Values

1 to 200

Default

100

Platforms

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

rate-calc-min-int

rate-calc-min-int

Syntax

rate-calc-min-int [fast-queue percent-of-default] [slow-queue percent-of-default]

no rate-calc-min-int

Context

[Tree] (config>card>virt-sched-adj rate-calc-min-int)

Full Context

configure card virtual-scheduler-adjustment rate-calc-min-int

Description

This command overrides the default minimum time that must elapse before a policer or queue’s offered rate may be recalculated. A minimum time between offered rate calculations is enforced to both prevent inaccurate estimation of the offered rate and excessive input to the virtual scheduler process.

In order to smooth out rapidly fluctuating offered rates, the system averages the measured offered rate with a window of previously measured offered traffic statistics and knowledge of the time between the samples.

The window size is defined by the "rate calculation minimum interval” with offered traffic statistics being read at most four times within the window. Any previous measured offered statistics within the window are used in the averaging function. Note that if there are large numbers of samples required, for example when a large number of queues are running HQoS, then it may be that a time greater than the "rate calculation minimum interval” passes before another sample of the offered statistics can be taken for a queue. In this case, in order to calculate an offered rate, HQoS will always use two samples, the current and the previous. In this case, using a smaller rate-calc-min-int will have no effect on the responsiveness of HQoS to queue rate changes.

The system separates policers and queues into fast and slow categories and maintains a separate "rate calculation minimum interval” for each type. The default for each type are as follows:

Slow Queue: 1.0 seconds

Fast Queue: 0.25 seconds

The actual minimum rate calculation interval may be increased or decreased by using the fast-queue and/or slow-queue keywords (which are also applicable for policers managed by HQoS) followed by a percent value which is applied to the default interval. The default slow-queue threshold rate is 1 Mb/s. Once a policer or queue is categorized as slow, its rate must rise to 1.5 Mb/s before being categorized as a fast policer or queue. The categorization threshold may be modified by using the slow-queue-threshold command.

The no form of this command restores the default fast queue and slow queue minimum rate calculation interval.

Default

no rate-calc-min-int

Parameters

percent-of-default

Specifies that the fast-queue percent-of-default parameter is optional and is used to modify the default minimum rate calculation time for "fast” queues. Defining 100.00 percent is equivalent to removing the override (restoring the default) on the fast queue minimum rate calculation time.

Values

0.01% to 1000.00%

Default

100.00%

percent-of-default

Specifies that the slow-queue percent-of-default parameter is optional and is used to modify the default minimum rate calculation time for "slow” queues. Defining 100.00 percent is equivalent to removing the override (restoring the default) on the slow queue minimum rate calculation time.

Values

0.01% to 1000.00%

Default

100.00%

Platforms

All

rate-down

rate-down

Syntax

rate-down rate

no rate-down

Context

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

Full Context

configure subscriber-mgmt local-user-db ppp host access-loop-encapsulation rate-down

Description

This command is applicable to LAC and LNS. It provides the last mile link rate in the downstream direction that is needed for proper shaping and calculating the interleaving delay.

The rate information in the last mile 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) /ICCN message (TX Connect Seed) on LNS.

Default

no rate-down

Parameters

rate

Specifies the last mile link downstream rate in the access loop

Values

1 to 100000 kb/s

Platforms

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

rate-limit

rate-limit

Syntax

rate-limit packets-per-second

no rate-limit

Context

[Tree] (config>service>nat>syslog>syslog-export-policy rate-limit)

Full Context

configure service nat syslog syslog-export-policy rate-limit

Description

This command configures the maximum rate limit at which syslog messages are sent. Once the rate limit is exceeded, NAT flow logs will be buffered. Overload condition is characterized by exhaustion of this buffer space. This condition can occur due to imposed rate limit or the software speed limit. Once the buffer space is exhausted, new flow creation will be denied, and the teardown of the existing flows will be delayed until the buffer space becomes available.

The no form of the command removes the maximum rate limit from the configuration.

Parameters

packets-per-second

Specifies the packet rate limit in seconds.

Values

10 to 2147483647

Platforms

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

rate-limit

Syntax

rate-limit value [kbps | pps] [mbs mbs-value]

rate-limit value [kbps | pps] extracted-traffic

rate-limit value [kbps | pps] packet-length {lt | gt | eq} packet-length-value

rate-limit value [kbps | pps] packet-length range packet-length-value packet-length-value

rate-limit value [kbps | pps] pattern expression expression mask mask offset-type offset-type offset-value offset-value

rate-limit value [kbps | pps] ttl {lt | gt | eq} ttl-value

rate-limit value [kbps | pps] ttl range ttl-value ttl-value

Context

[Tree] (config>filter>ip-filter>entry>action rate-limit)

Full Context

configure filter ip-filter entry action rate-limit

Description

This command configures the rate-limit value for traffic matching this filter entry. Rate-limit policers are configured with MBS equals CBS equals 10 ms of the rate and high-prio-only equals 0.

Traffic can also be rate limited based on extracted-traffic, packet-length, ttl, or a pattern of conditional match criteria.

Packets that match the filter entry match criteria, but do not match the conditional match criteria value, are implicitly forwarded with no further match in the following filter entries.

For pattern match:

  • the expression is left-aligned for the odd number bytes, for example, the expression 0xABC is programmed 0x0ABC in the line card

  • the 'data' offset requires protocol UDP or TCP to be selected in the filter entry match criteria.

Parameters

value

Specifies the rate-limit value in kb/s (default) or packets per second (pps). A rate of 0 results in all traffic being dropped. A rate of max results in all traffic being forwarded.

Values

0 to 2000000000 kb/s, max

0 to 100000000 pps, max

mbs-value

Specifies the maximum burst size in bytes. This parameter can only be specified when the rate-limit value unit is kbps.

Values

0 to 268435456

extracted-traffic

Specifies rate-limit packets both extracted to the CPM and matching the filter entry match criteria.

packet-length

Specifies rate-limit packets matching both the filter entry match criteria and the packet-length value defined in the rate-limit action statement. Packets matching the filter entry match criteria and not matching the packet-length value, as defined in the rate-limit action statement, are implicitly forwarded with no further match in the following filter entries.

Values

lt — Specifies "less than”. The lt parameter cannot be used with the lowest possible numerical value for the parameter.

gt — Specifies "greater than”. The gt parameter cannot be used with the highest possible numerical value for the parameter.

eq — Specifies "equal to”.

packet-length-value

Specifies the packet length value for the rate limit action.

Values

0 to 65535

range

Specifies an inclusive range. When range is used, the start of the range (the first value entered) must be smaller than the end of the range (the second value entered).

expression

Specifies the hexadecimal pattern to match; up to eight bytes.

Values

0x0000000000000001 to 0xffffffffffffffff

mask

Specifies the mask for the pattern expression, up to eight bytes.

Values

0x0000000000000001 to 0xffffffffffffffff

offset-type

Specifies the starting point reference for the offset-value of this pattern.

Values

layer-3, layer-4, data, dns-qtype

offset-value

Specifies the offset value for the pattern expression. Dns-qtype supports offset value of 0.

Values

0 to 255

ttl-value

Specifies rate-limit packets matching both the filter entry match criteria and the TTL value defined in the rate-limit action statement. Packets matching the filter entry match criteria and not matching the TTL value, as defined in the rate-limit action statement, are implicitly forwarded with no further match in the following filter entries.

Values

0 to 255

Platforms

All

rate-limit

Syntax

rate-limit value

Context

[Tree] (config>filter>mac-filter>entry>action rate-limit)

Full Context

configure filter mac-filter entry action rate-limit

Description

This command sets the rate limit for the traffic matching both the filter entry match criteria and the packet-length-value defined in the rate-limit action statement.

Packets matching the filter entry match criteria and not matching the packet-length-value defined in the rate-limit action statement are implicitly forwarded with no further match in subsequent filter entries.

Rate limit packets matching both the filter entry match criteria and the ttl-value are defined in the action rate-limit statement.

Packets matching the filter entry match criteria and not matching the ttl-value defined in the rate-limit action statement are implicitly forwarded with no further match in the following filter entries.

Parameters

value

Specifies the rate-limit value in kb/s. A rate of 0 results in all traffic being dropped. A rate of max results in all traffic being forwarded.

Values

0 to 2000000000 kb/s | max

Platforms

All

rate-limit

Syntax

rate-limit value [kbps | pps] [mbs mbs-value]

rate-limit value [kbps | pps] extracted-traffic

rate-limit value [kbps | pps] hop-limit {lt | gt | eq} hop-limit-value

rate-limit value [kbps | pps] hop-limit range hop-limit-value hop-limit-value

rate-limit value [kbps | pps] pattern expression expression mask mask offset-type offset-type offset-value offset-value

rate-limit value [kbps | pps] payload-length {lt | gt | eq} payload-length-value

rate-limit value [kbps | pps] payload-length range payload-length-value payload-length-value

Context

[Tree] (config>filter>ipv6-filter>entry>action rate-limit)

Full Context

configure filter ipv6-filter entry action rate-limit

Description

This command configures the rate-limit value for traffic matching this filter entry.

Traffic can also be rate-limited based on extracted-traffic, payload-length, hop-limit, or a pattern of conditional match criteria.

Packets that match the filter entry match criteria, but do not match the conditional match criteria value, are implicitly forwarded with no further match in the following filter entries.

For pattern match:

  • the expression is left-aligned for the odd number bytes, for example, the expression 0xABC is programmed 0x0ABC in the line card.

  • the 'data' offset requires protocol UDP or TCP to be selected in the filter entry match criteria.

Parameters

value

Specifies the rate-limit value in kb/s (default) or packets per second (pps). A rate of 0 results in all traffic being dropped. A rate of max results in all traffic being forwarded.

Values

0 to 2000000000 kb/s, max

0 to 100000000 pps, max

mbs-value

Specifies the maximum burst size in bytes. This parameter can only be specified when the rate-limit value unit is kbps.

Values

0 to 268435456

extracted-traffic

Specifies packets extracted to the CPM.

hop-limit

Specifies the hop limit value for the rate limit action.

Values

lt — Specifies "less than”. The lt parameter cannot be used with the lowest possible numerical value for the parameter.

gt — Specifies "greater than”. The gt parameter cannot be used with the highest possible numerical value for the parameter.

eq — Specifies "equal to”.

hop-limit-value

Specifies the hop limit value for the rate limit action.

Values

0 to 255

range

Specifies an inclusive range. When the range parameter is used, the start of the range (the first value entered) must be smaller than the end of the range (the second value entered).

expression

Specifies the hexadecimal pattern to match; up to eight bytes.

Values

0x0000000000000001 to 0xffffffffffffffff

mask

Specifies the mask for the pattern expression, up to eight bytes.

Values

0x0000000000000001 to 0xffffffffffffffff

offset-type

Specifies the starting point reference for the offset-value of this pattern.

Values

layer-3, layer-4, data, dns-qtype

offset-value

Specifies the offset value for the pattern expression. Dns-qtype supports offset value of 0.

Values

0 to 255

payload-length

Specifies rate-limit packets matching both the filter entry match criteria and the payload-length-value defined in the rate-limit action statement. Packets matching the filter entry match criteria and not matching the payload-length-value, as defined in the rate-limit action statement, are implicitly forwarded with no further match in the following filter entries.

Values

lt — Specifies "less than”. The lt parameter cannot be used with the lowest possible numerical value for the parameter.

gt — Specifies "greater than”. The gt parameter cannot be used with the highest possible numerical value for the parameter.

eq — Specifies "equal to”.

payload-length-value

Specifies the payload length value for the rate limit action.

Values

0 to 65535

Platforms

All

rate-modify

rate-modify

Syntax

rate-modify scheduler scheduler-name

rate-modify agg-rate-limit

no rate-modify

Context

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

[Tree] (config>subscr-mgmt>ancp>policy>ingress rate-modify)

Full Context

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

configure subscriber-mgmt ancp ancp-policy ingress rate-modify

Description

This command configures rate modify scheduler parameters.

The no form of this command removes the scheduler name 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 a scheduler name, up to 32 characters.

Platforms

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

rate-monitor

rate-monitor

Syntax

rate-monitor kilobit-per-second [alarm]

no rate-monitor

Context

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

[Tree] (config>subscr-mgmt>ancp>policy>ingress rate-monitor)

Full Context

configure subscriber-mgmt ancp ancp-policy egress rate-monitor

configure subscriber-mgmt ancp ancp-policy ingress rate-monitor

Description

This command configures the rate monitor level.

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

Parameters

kilobit-per-second

Specifies the rate below which the system generates an event.

Values

0 to 4294967295

alarm

When the monitored rate is below the configured value the system generates an alarm (trap) to the management system. The trap includes the rate as well as the ANCP policy name and the ANCP string.

Platforms

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

rate-percentage

rate-percentage

Syntax

rate-percentage rate-percentage

no rate-percentage

Context

[Tree] (config>app-assure>group>policer rate-percentage)

Full Context

configure application-assurance group policer rate-percentage

Description

This command indirectly configures the rate used by Access-Network-Location (ANL) policers. Because ANL total bandwidth is dynamically measured and estimated by AA, this command allows the operator to configure the ratio of that measured bandwidth to be used by the ANL policer as the policer rate.

The no form of this command resets the values to defaults.

Default

no rate-percentage

Parameters

rate-percentage

Specifies an integer value that specifies a percentage that is applied against the ANL estimate maximum bandwidth to produce the actual rate that is used by the policer when ANL congestion occurs.

Values

0 to 200 (0: means drop all traffic)

Default

0

Platforms

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

rate-percentage-stage2

rate-percentage-stage2

Syntax

rate-percentage-stage2 rate-percentage

no rate-percentage-stage2

Context

[Tree] (config>app-assure>group>policer rate-percentage-stage2)

Full Context

configure application-assurance group policer rate-percentage-stage2

Description

This command indirectly configures the rate used by Access-Network-Location (ANL) policers. Because ANL stage2 total bandwidth is dynamically measured and estimated by AA, this command allows the operator to configure the ratio of that measured bandwidth to be used by the ANL stage2 policer as the policer rate.

The no form of this command reverts to the default.

Parameters

rate-percentage

Specifies an integer value that specifies a percentage that is applied to the ANL estimated maximum bandwidth to produce the actual rate that is used by the policer when ANL stage2 congestion occurs. A value of 0 means that all traffic is dropped.

Values

0 to 200

Default

0

Platforms

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

rate-reduction

rate-reduction

Syntax

rate-reduction kilobit-per-second

no rate-reduction

Context

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

[Tree] (config>subscr-mgmt>ancp>policy>ingress rate-reduction)

Full Context

configure subscriber-mgmt ancp ancp-policy egress rate-reduction

configure subscriber-mgmt ancp ancp-policy ingress rate-reduction

Description

This command defines a constant rate reduction to the rate specified by the DSLAM. The rate-reduction command should be used if the node should adjust the rate to a value that is offset (for example by a fixed multicast dedicated bandwidth) compared to the total available on the DSLAM.

When set, the rate is:

DSLAM_RATE*adjust-rate/100 — rate-reduction

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

Parameters

kilobits-per-second

Specifies the rate reduction to be applied for this subscriber.

Values

0 to 4294967295

Platforms

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

rate-thresholds

rate-thresholds

Syntax

rate-thresholds high high-percentage low low-percentage

no rate-thresholds

Context

[Tree] (config>subscr-mgmt>sla-profile>egress>bonding-selection rate-thresholds)

Full Context

configure subscriber-mgmt sla-profile egress bonding-selection rate-thresholds

Description

This command configures the rate thresholds that are required before decreasing or increasing the preferred link’s weight with the specified change percentage.

The low threshold value must be lower than the high threshold value.

The no form of this command reverts to the default.

Default

rate-thresholds high 90 low 80

Parameters

high-percentage

Specifies the high threshold, as a percentage of the reference rate.

Values

56 to 99

low-percentage

Specifies the low threshold, as a percentage of the reference rate.

Values

55 to 98

Platforms

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

rating-group

rating-group

Syntax

rating-group rating-group-id

no rating-group

Context

[Tree] (config>subscr-mgmt>cat-map>category rating-group)

Full Context

configure subscriber-mgmt category-map category rating-group

Description

This command configures the rating group applicable for this category.

The no form of this command reverts to the default.

Parameters

rating-group-id

Specifies the rating group applicable for this category.

Values

0 to 4294967295

Platforms

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

raw

raw

Syntax

[no] raw

Context

[Tree] (config>cflowd>collector>aggregation raw)

Full Context

configure cflowd collector aggregation raw

Description

This command configures raw (unaggregated) flow data to be sent in Version 5.

The no form of this command removes this type of aggregation from the collector configuration.

Platforms

All

rd

rd

Syntax

rd file-url rf

rd file-url [force]

Context

[Tree] (file rd)

Full Context

file rd

Description

If the directory is empty, the rd command is used to remove it. The force option executes the command without prompting the user to confirm the action.

If the directory contains files and/or subdirectories, the rf parameter must be used to remove the directory.

Example:

A:nE1>file cf1:\ # rd test 
Are you sure (y/n)? y 
Deleting directory cf1:\test ..MINOR: CLI Cannot delete cf1:\test.
A:nE1>file cf1:\ # rd test force 
Deleting directory cf1:\test .MINOR: CLI Cannot delete cf1:\test.


A:nE1>file cf1:\ # rd testbase rf 
Deleting all subdirectories and files in specified directory. y/n ?y 
Deleting directory cf1:\testbase\testbase1 ..OK
Deleting directory cf1:\test .OK

Parameters

file-url

Specifies the directory to be removed.

Values

local-url

[cflash-id/][file-path] up to 200 characters, including cflash-id directory length up to 99 each

remote-url

[{ftp:// | tftp://}login:pswd@remote-locn/][file-path]

up to 247 characters

directory length up to 99 characters each

remote-locn

[hostname | ipv4-address | [ipv6-address]]

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

interface - up to 32 characters, for link local addresses 255

cflash-id

cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

rf

Forces a recursive delete.

force

Forces an immediate deletion of the specified directory. The rd file-url force command executes the command without displaying a user prompt message.

Platforms

All

rd-entry

rd-entry

Syntax

rd-entry rd

no rd-entry rd

Context

[Tree] (config>router>policy-options>route-distinguisher-list rd-entry)

Full Context

configure router policy-options route-distinguisher-list rd-entry

Description

This command creates a route distinguisher (RD) entry in the RD list, containing an IPv4 address or ASN and the assigned number.

The no form of the command deletes the RD entry from the list.

Parameters

rd
Specifies a route distinguisher matching an entry in one of the following formats:
  • a.b.c.d/m:* – RD in IPv4 format with a wildcard character (such as 10.0.0.0/16:*)
  • a.b.c.d/m:n – RD in IPv4 format with a specific number (such as 10.0.0.2/32:535)
  • asn:* – RD in ASN format with a wildcard character (such as 65000:*)
  • asn:n – RD in ASN format with a specific number (such as 65000:535)

See the "Route distinguishers" section of the 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 3 Services Guide: IES and VPRN for information about Type values.

Platforms

All

rdi-alarms

rdi-alarms

Syntax

rdi-alarms [suppress | circuit]

Context

[Tree] (config>port>aps rdi-alarms)

Full Context

configure port aps rdi-alarms

Description

This command configures how RDI alarms (line, path, section) are generated on physical circuits of an APS ports. The command configuration changes are supported only for switching-mode set to uni_1plus1. The configuration can be changed only when no working and protecting circuit has been added. Options:

  • circuit–RDI alarms are H/W-generated independently on each working and protect circuit based on RX failure of that circuit regardless of APS line status.

  • suppress–RDI H/W generation on working and protect circuits is suppressed. No alarms are generated on RX failure of that circuit.

Default

rdi-alarms circuit

Platforms

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

rdnss-lifetime

rdnss-lifetime

Syntax

rdnss-lifetime seconds

rdnss-lifetime infinite

no rdnss-lifetime

Context

[Tree] (config>service>ies>sub-if>ipv6>rtr-adv rdnss-lifetime)

[Tree] (config>subscr-mgmt>rtr-adv-plcy>dns-opt rdnss-lifetime)

[Tree] (config>service>ies>sub-if>grp-if>ipv6 rdnss-lifetime)

[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv rdnss-lifetime)

[Tree] (config>service>vprn>sub-if>grp-if>ipv6 rdnss-lifetime)

Full Context

configure service ies subscriber-interface ipv6 rtr-adv rdnss-lifetime

configure subscriber-mgmt router-advertisement-policy dns-options rdnss-lifetime

configure service ies subscriber-interface group-interface ipv6 rdnss-lifetime

configure service vprn subscriber-interface ipv6 rtr-adv rdnss-lifetime

configure service vprn subscriber-interface group-interface ipv6 rdnss-lifetime

Description

This command configures the maximum time that the RDNSS address may be used for name resolution.

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

Default

rdnss-lifetime 3600

Parameters

seconds

Specifies the time, in seconds, that the RDNSS address is valid for this route.

Values

900 to 3600

infinite

Specifies that the RDNSS address can be used permanently.

Platforms

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

rdnss-lifetime

Syntax

rdnss-lifetime seconds

rdnss-lifetime infinite

no rdnss-lifetime

Context

[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-adv>dns-opt rdnss-lifetime)

[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv>dns-opt rdnss-lifetime)

[Tree] (config>service>vprn>sub-if>grp-if>ipv6>rtr-adv>dns-opt rdnss-lifetime)

[Tree] (config>service>ies>sub-if>ipv6>rtr-adv>dns-opt rdnss-lifetime)

Full Context

configure service ies subscriber-interface group-interface ipv6 router-advertisements dns-options rdnss-lifetime

configure service vprn subscriber-interface ipv6 router-advertisements dns-options rdnss-lifetime

configure service vprn subscriber-interface group-interface ipv6 router-advertisements dns-options rdnss-lifetime

configure service ies subscriber-interface ipv6 router-advertisements dns-options rdnss-lifetime

Description

This command configures the maximum time that the RDNSS address may be used for name resolution.

The no form of this command reverts to the default.

Default

rdnss-lifetime 3600

Parameters

seconds

Specifies the time, in seconds, that the RDNSS address is valid for this route.

Values

900 to 3600

infinite

The RDNSS address can be used permanently.

Platforms

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

rdnss-lifetime

Syntax

rdnss-lifetime {seconds | infinite}

no rdnss-lifetime

Context

[Tree] (config>service>vprn>router-advert>dns-options rdnss-lifetime)

[Tree] (config>service>vprn>router-advert>if>dns-options rdnss-lifetime)

Full Context

configure service vprn router-advertisement dns-options rdnss-lifetime

configure service vprn router-advertisement interface dns-options rdnss-lifetime

Description

This command specifies the maximum time that the RDNSS address may be used for name resolution by the client. The RDNSS Lifetime must be no more than twice MaxRtrAdvLifetime with a maximum of 3600 seconds.

Default

rdnss-lifetime infinite

Parameters

infinite

Specifies an infinite RDNSS lifetime.

seconds

Specifies the time in seconds.

Values

4to 3600

Platforms

All

rdnss-lifetime

Syntax

rdnss-lifetime seconds

rdnss-lifetime infinite

no rdnss-lifetime

Context

[Tree] (config>router>router-advert>dns-opt rdnss-lifetime)

[Tree] (config>router>router-advert>if>dns-opt rdnss-lifetime)

Full Context

configure router router-advertisement dns-options rdnss-lifetime

configure router router-advertisement interface dns-options rdnss-lifetime

Description

This command specifies the maximum time that the RDNSS address may be used for name resolution by the client.

Default

rdnss-lifetime infinite

Parameters

seconds

Specifies the time in seconds.

Values

4 to 3600

infinite

Specifies an infinite RDNSS lifetime.

Platforms

All

re-auth-period

re-auth-period

Syntax

re-auth-period seconds

no re-auth-period

Context

[Tree] (config>port>ethernet>dot1x re-auth-period)

Full Context

configure port ethernet dot1x re-auth-period

Description

This command configures the period after which re-authentication is performed. This value is only relevant if re-authentication is enabled.

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

Default

re-auth-period 3600

Parameters

seconds

Specifies the re-authentication delay period in seconds.

Values

1 to 9000

Platforms

All

re-authentication

re-authentication

Syntax

[no] re-authentication

Context

[Tree] (config>subscr-mgmt>auth-policy re-authentication)

Full Context

configure subscriber-mgmt authentication-policy re-authentication

Description

This command enables authentication process at every DHCP address lease renewal s only if RADIUS did not reply any special attributes (for example, authentication only, no authorization).

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

Platforms

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

re-authentication

Syntax

[no] re-authentication

Context

[Tree] (config>port>ethernet>dot1x re-authentication)

Full Context

configure port ethernet dot1x re-authentication

Description

This command enables/disables periodic 802.1x re-authentication.

When re-authentication is enabled, the router re-authenticates clients on the port every re-auth-period.

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

Default

no re-authentication

Platforms

All

re-establish-session

re-establish-session

Syntax

re-establish-session padr

no re-establish-session

Context

[Tree] (config>subscr-mgmt>ppp-policy re-establish-session)

Full Context

configure subscriber-mgmt ppp-policy re-establish-session

Description

This command enables host to reconnect and override existing session.

If disabled and a subscriber abruptly terminates a PPP sessions without sending a PADT to the BNG, the BNG denies any reconnect attempts until the stale PPP session has expired. With this, enabled re-establish-session eliminates the waiting period by allowing immediate PPP reconnection attempts.

The no form of this command reverts to the default.

Parameters

padr

Specifies that the existing session will be deleted upon reception of the PPPoE Active Discovery Request (PADR).

Platforms

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

reachable-time

reachable-time

Syntax

reachable-time milli-seconds

no reachable-time

Context

[Tree] (config>subscr-mgmt>rtr-adv-plcy reachable-time)

Full Context

configure subscriber-mgmt router-advertisement-policy reachable-time

Description

This command configures the reachable time for advertisements.

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

Default

reachable-time 0

Parameters

milli-seconds

Specifies the time, in milliseconds, for the reachable time.

Values

0 to 3600000

Platforms

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

reachable-time

Syntax

reachable-time milli-seconds

no reachable-time

Context

[Tree] (config>service>vprn>router-advert>if reachable-time)

[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv reachable-time)

[Tree] (config>service>ies>sub-if>ipv6>rtr-adv reachable-time)

[Tree] (config>service>vprn>sub-if>grp-if>ipv6>rtr-adv reachable-time)

[Tree] (config>router>router-advert>if reachable-time)

[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-adv reachable-time)

Full Context

configure service vprn router-advertisement interface reachable-time

configure service vprn subscriber-interface ipv6 router-advertisements reachable-time

configure service ies subscriber-interface ipv6 router-advertisements reachable-time

configure service vprn subscriber-interface group-interface ipv6 router-advertisements reachable-time

configure router router-advertisement interface reachable-time

configure service ies subscriber-interface group-interface ipv6 router-advertisements reachable-time

Description

This command configures how long this router should be considered reachable by other nodes on the link after receiving a reachability confirmation.

The configured value is placed in the reachable time field in router advertisement messages sent from this interface.

The no form of this command reverts to the default.

Default

reachable-time 0

Parameters

milli-seconds

Specifies the reachable time, in seconds, for advertisements from this interface.

Values

0 to 3600000

Platforms

All

  • configure service vprn router-advertisement interface reachable-time
  • configure router router-advertisement interface reachable-time

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

  • configure service ies subscriber-interface group-interface ipv6 router-advertisements reachable-time
  • configure service vprn subscriber-interface ipv6 router-advertisements reachable-time
  • configure service ies subscriber-interface ipv6 router-advertisements reachable-time
  • configure service vprn subscriber-interface group-interface ipv6 router-advertisements reachable-time

reachable-time

Syntax

reachable-time seconds

no reachable-time

Context

[Tree] (config>service>vprn>if>ipv6 reachable-time)

[Tree] (config>service>vprn>ipv6 reachable-time)

Full Context

configure service vprn interface ipv6 reachable-time

configure service vprn ipv6 reachable-time

Description

This command configures how long this router should be considered reachable by other nodes on the link after receiving a reachability confirmation.

Default

no reachable-time

Parameters

seconds

Specifies the length of time, in seconds the router should be considered reachable.

Values

30 to 3600

Platforms

All

reachable-time

Syntax

reachable-time milliseconds

no reachable-time

Context

[Tree] (config>service>ies>sub-if>grp-if>ipv6>router-ad reachable-time)

Full Context

configure service ies subscriber-interface group-interface ipv6 router-ad reachable-time

Description

This command configures how long this router should be considered reachable by other nodes on the link after receiving a reachability confirmation.

Parameters

milliseconds

Specifies the length of time the router should be considered reachable for default router selection.

Values

0 to 3600000

reachable-time

Syntax

reachable-time seconds

no reachable-time

Context

[Tree] (config>router>ipv6 reachable-time)

Full Context

configure router ipv6 reachable-time

Description

This command configures the neighbor reachability detection timer.

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

Default

reachable-time 30

Parameters

seconds

Specifies the length of time the router should be considered reachable.

Values

30 to 3600

Platforms

All

reachable-time

Syntax

reachable-time seconds

no reachable-time

Context

[Tree] (config>router>if>ipv6 reachable-time)

Full Context

configure router interface ipv6 reachable-time

Description

This command configures the neighbor reachability detection timer.

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

Default

no reachable-time

Parameters

seconds

Specifies the length of time the router should be considered reachable.

Values

30 to 3600

Platforms

All

reactivation-failure-threshold

reactivation-failure-threshold

Syntax

reactivation-failure-threshold number

no reactivation-failure-threshold

Context

[Tree] (config>test-oam>icmp>ping-template reactivation-failure-threshold)

Full Context

configure test-oam icmp ping-template reactivation-failure-threshold

Description

This command configures the number of consecutive failures, without previous successes, that must occur transmitting at the reactivation-interval (recovering phase) level before changing to the standard interval and subsequently waiting for the first success.

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

Default

reactivation-failure-threshold 4

Parameters

number

Specifies the number of consecutive failures without previous successes.

Values

1 to 10

Platforms

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

reactivation-interval

reactivation-interval

Syntax

reactivation-interval seconds

no reactivation-interval

Context

[Tree] (config>test-oam>icmp>ping-template reactivation-interval)

Full Context

configure test-oam icmp ping-template reactivation-interval

Description

This command configures the packet transmit interval used when the IP interface is operationally down because of a ping template failure and the previous ICMP echo request successfully received a response, recovering phase.

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

Default

reactivation-interval 1

Parameters

seconds

Specifies the packet transmit interval used when IP interface is operational down

Values

1 to 60

Platforms

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

reactivation-threshold

reactivation-threshold

Syntax

reactivation-threshold number

no reactivation-threshold

Context

[Tree] (config>test-oam>icmp>ping-template reactivation-threshold)

Full Context

configure test-oam icmp ping-template reactivation-threshold

Description

This command configures the count, when reached, that causes the transition of the IP interface from operationally down to operationally up because of a ping template failure. This is used in the recovering phase.

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

Default

reactivation-threshold 3

Parameters

number

Specifies a count that causes the transition of the IP interface from operationally up to operationally down because of ping-template failure.

Values

1 to 10

Platforms

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

reactivation-timeout

reactivation-timeout

Syntax

reactivation-timeout seconds

no reactivation-timeout

Context

[Tree] (config>test-oam>icmp>ping-template reactivation-timeout)

Full Context

configure test-oam icmp ping-template reactivation-timeout

Description

This command configures the time that the function waits before declaring the packet as lost. This is the timer used to time out the reactivation-interval transmitted packets. The reactivation-timeout value can be equal to or lower than the reactivation-interval value but not higher.

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

Default

reactivation-timeout 1

Parameters

seconds

Specifies the wait time, in seconds, before declaring the packet is lost.

Values

1 to 60

Platforms

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

read-algorithm

read-algorithm

Syntax

read-algorithm {hash | hash2 | custom| all-hash}

no read-algorithm

Context

[Tree] (config>system>security>management-interface>classic-cli read-algorithm)

Full Context

configure system security management-interface classic-cli read-algorithm

Description

This command specifies how encrypted configuration secrets are interpreted, and which encryption types are accepted, when secrets are input into the system or read from a configuration file (for example at system bootup time).

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

Default

read-algorithm all-hash

Parameters

hash

Specifies hash. Use this option to transport a phrase between modules and nodes. In this case the write-algorithm should be hash as well.

hash2

Specifies hash2 which is module-specific.

custom

Specifies the custom encryption to management interface.

all-hash

Specifies that the system accepts hash or hash2.

Platforms

All

reassemble

reassemble

Syntax

reassemble

Context

[Tree] (config>filter>ip-filter>entry>action reassemble)

Full Context

configure filter ip-filter entry action reassemble

Description

This command sets the filter entry action to reassemble.

Platforms

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

reassembly

reassembly

Syntax

reassembly [wait-msecs]

no reassembly

Context

[Tree] (config>service>ies>if>sap>ip-tunnel reassembly)

[Tree] (config>service>vprn>if>sap>ip-tunnel reassembly)

Full Context

configure service ies interface sap ip-tunnel reassembly

configure service vprn interface sap ip-tunnel reassembly

Description

This command configures the maximum number of seconds to wait to receive all fragments of a particular IPsec or GRE packet for reassembly.

The no form of this commands removes the wait time from the configuration.

Default

no reassembly

Parameters

wait-msecs

Specifies the reassembly wait time in 100 increments.

Values

1 to 5000 ms

Platforms

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

reassembly

Syntax

reassembly [wait-msecs]

no reassembly

Context

[Tree] (config>service>ies>if>sap>gre-tunnel reassembly)

[Tree] (config>isa>tunnel-group reassembly)

[Tree] (config>service>vprn>if>sap>gre-tunnel reassembly)

Full Context

configure service ies interface sap gre-tunnel reassembly

configure isa tunnel-group reassembly

configure service vprn interface sap gre-tunnel reassembly

Description

This command configures IP packet reassembly for IPsec and GRE tunnels supported by an MS-ISA. The reassembly command at the tunnel-group level configures IP packet reassembly for all IPsec and GRE tunnels associated with the tunnel-group. The reassembly command at the GRE tunnel level configures IP packet reassembly for that one specific GRE tunnel, overriding the tunnel-group configuration.

The no form of this command disables IP packet reassembly.

Default

no reassembly (tunnel-group level)

reassembly (gre-tunnel level)

Parameters

wait

Specifies the maximum number of milliseconds that the ISA tunnel application will wait to receive all fragments of a particular IPsec or GRE packet. If one or more fragments are still missing when this limit is reached the partially reassembled datagram is discarded and an ICMP time exceeded message is sent to the source host (if allowed by the ICMP configuration of the sending interface). Internally, the configured value is rounded up to the nearest multiple of 100 ms.

Values

1 to 5000

Default

2000 (tunnel-group level)

Platforms

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

reassembly

Syntax

[no] reassembly

Context

[Tree] (config>router>nat>inside>dual-stack-lit>address reassembly)

Full Context

configure router nat inside dual-stack-lit address reassembly

Description

This command enables reassembly of fragmented frames for DS-Lite. Reassembly is enabled in the upstream direction per AFTR address.

The no form of the command disables the reassembly.

reassembly-group

reassembly-group

Syntax

reassembly-group nat-group-id [to-base-network]

no reassembly-group

Context

[Tree] (config>service>vprn reassembly-group)

[Tree] (config>router reassembly-group)

Full Context

configure service vprn reassembly-group

configure router reassembly-group

Description

This command associates a reassembly-group consisting of multiple ISAs with the routing context in which the application requiring reassembly service resides.

Default

no reassembly-group

Parameters

nat-group-id

Specifies the NAT group ID; the NAT group contains up to 10 active ISAs.

Values

1 to 4

to-base-network

Enables the reassembly context to use network interfaces in the base routing context.

Platforms

All

reassembly-timeout

reassembly-timeout

Syntax

reassembly-timeout {timeout}

no reassembly-timeout

Context

[Tree] (config>service>vprn>l2tp>group>tunnel>mlppp reassembly-timeout)

[Tree] (config>service>vprn>l2tp>group>mlppp reassembly-timeout)

[Tree] (config>router>l2tp>group>tunnel>mlppp reassembly-timeout)

[Tree] (config>router>l2tp>group>mlppp reassembly-timeout)

Full Context

configure service vprn l2tp group tunnel mlppp reassembly-timeout

configure service vprn l2tp group mlppp reassembly-timeout

configure router l2tp group tunnel mlppp reassembly-timeout

configure router l2tp group mlppp reassembly-timeout

Description

This command is applicable only to LNS. It determines the time during which the LNS keeps fragments of the same packet in the buffer before it discards them. The assumption is that if the fragments do not arrive within certain time, the chance is that they were lost somewhere in the network. In this case the partial packet cannot be reassembled and all fragments that has arrived up to this point and are stored in the buffer IS discarded to free up the buffer. Otherwise, a condition arises in which partial packets are held in the buffer until the buffer is exhausted.

The configuration under the tunnel hierarchy overrides the configuration under the group hierarchy.

The no form of this command reverts to the default.

Default

reassembly-timeout 1000

Parameters

timeout

Specifies the reassembly timeout value.

Values

100, 1000 milliseconds

Platforms

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

rebind-timer

rebind-timer

Syntax

rebind-timer [days days] [hrs hours] [min minutes] [sec seconds]

no rebind-timer

Context

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

[Tree] (config>router>dhcp6>server>pool>prefix rebind-timer)

[Tree] (config>router>dhcp6>server>defaults rebind-timer)

[Tree] (config>service>vprn>dhcp6>server>pool>prefix rebind-timer)

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>ipv6-lease-times rebind-timer)

[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6>proxy-server rebind-timer)

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>ipv6-lease-times rebind-timer)

[Tree] (config>service>vprn>dhcp6>defaults rebind-timer)

Full Context

configure service vprn subscriber-interface group-interface ipv6 dhcp6 proxy-server rebind-timer

configure router dhcp6 local-dhcp-server pool prefix rebind-timer

configure router dhcp6 local-dhcp-server defaults rebind-timer

configure service vprn dhcp6 local-dhcp-server pool prefix rebind-timer

configure subscriber-mgmt local-user-db ipoe host ipv6-lease-times rebind-timer

configure service ies subscriber-interface group-interface ipv6 dhcp6 proxy-server rebind-timer

configure subscriber-mgmt local-user-db ppp host ipv6-lease-times rebind-timer

configure service vprn dhcp6 defaults rebind-timer

Description

This command configures the lease rebind timer (T2) via LUDB.

The T2 time is the time at which the client contacts any available addressing authority to extend the lifetimes of DHCPv6 leases. T2 is a time duration relative to the current time expressed in units of seconds.

The IP addressing authority controls the time at which the client contacts the addressing authority to extend the lifetimes on assigned addresses/prefixes through the T1 and T2 parameters assigned to an IA. At time T1 for an IA, the client initiates a Renew/Reply message exchange to extend the lifetimes on any addresses in the IA. The client includes an IA option with all addresses/prefixes currently assigned to the IA in its Renew message. Recommended values for T1 and T2 are .5 and .8 times the shortest preferred lifetime of the addresses/prefixes in the IA that the addressing authority is willing to extend, respectively.

The configured rebind timer should always be longer than or equal to the renew timer.

The T1 and T2 are carried in the IPv6 address option that is within the IA.

The no form of this command reverts to the default.

Default

rebind-timer min 48

Parameters

rebind-timer

Specifies the preferred lifetime.

Values

days days

0 to 14

hrs hours

0 to 23

min minutes

0 to 59

sec seconds

0 to 9

Platforms

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 rebind-timer
  • configure service ies subscriber-interface group-interface ipv6 dhcp6 proxy-server rebind-timer
  • configure router dhcp6 local-dhcp-server pool prefix rebind-timer
  • configure subscriber-mgmt local-user-db ipoe host ipv6-lease-times rebind-timer
  • configure subscriber-mgmt local-user-db ppp host ipv6-lease-times rebind-timer
  • configure service vprn dhcp6 local-dhcp-server pool prefix rebind-timer

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

  • configure router dhcp6 local-dhcp-server defaults rebind-timer

reboot

reboot

Syntax

reboot [active | standby | upgrade] [now]

Context

[Tree] (admin reboot)

Full Context

admin reboot

Description

This command reboots the router or one CPM and can also be used to force an upgrade of the system boot ROMs.

If no options are specified, the user is prompted to confirm the reboot operation. Answering yes (y) will result in both CPMs and all IOMs rebooting.

ALA-1>admin# reboot
Are you sure you want to reboot (y/n)?

Parameters

active

Reboots the active CPM.

Default

active

standby

Reboots the standby CPM.

Default

active

upgrade

Forces card firmware to be upgraded during chassis reboot. This option should only be used if it has been indicated as required in the Release Notes or by Nokia technical support. Normally, the SR-series router OS automatically performs firmware upgrades on CPMs and XCM/IOM cards without the need for the upgrade keyword.

When the upgrade keyword is specified, a chassis flag is set for the BOOT Loader (boot.ldr) and on the subsequent boot of the OS on the chassis, firmware images on CPMs, XCMs, and IOMs will be upgraded automatically.

Firmware on CPMs, XCMs, or IOMs that are installed in a running chassis will be upgraded automatically. For example, if a card is inserted as the result of a hot swap, and the card has a firmware version that is no longer compatible with the SR OS image running on the chassis, then the firmware on the card will be automatically upgraded before the card is brought online.

If the card firmware is upgraded, a chassis cardUpgraded (event 2032) log event is generated. The corresponding SNMP trap for this log event is tmnxEqCardFirmwareUpgraded.

During any firmware upgrade, automatic or manual, it is imperative that during the upgrade procedure:

  • Power must not be switched off or interrupted.

  • The system must not be reset.

  • No cards are inserted or removed.

Any of the above conditions may render cards inoperable requiring a return of the card for resolution.

The time required to upgrade the firmware on the cards in the chassis depends on the number of cards to be upgraded. The progress of a firmware upgrade can be monitored at the console.

now

Forces a reboot of the router immediately without an interactive confirmation.

Platforms

All

reboot

Syntax

reboot [now] upgrade

Context

[Tree] (admin>satellite>eth-sat reboot)

Full Context

admin satellite eth-sat reboot

Description

The command initiates an administrative reboot of the specified Ethernet-satellite chassis.

Parameters

now

Causes the satellite to reboot immediately without further prompts or interactive confirmation.

upgrade

Causes the satellite to update its firmware image during chassis reboot.

Platforms

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

receive

receive

Syntax

[no] receive

Context

[Tree] (config>port>ethernet>eth-cfm>mep>eth-bn receive)

Full Context

configure port ethernet eth-cfm mep eth-bn receive

Description

This command enables the reception and processing of eth-bn messages and the retrieval and processing of the current bandwidth field for inclusion in dynamic egress rate adjustments.

The received rate is an Layer 2 rate, and is expected to be in Mb/s. If this rate is a link rate (including preamble, start frame delimiter, and inter-frame gap), this would require the use of network egress queue groups (configured in the configure qos queue-group-templates egress queue-group "qg1" queue 1 packet-byte-offset add 20). The packet-byte-offset is not supported for default network queues.

Default

no receive

Platforms

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

receive

Syntax

receive {both | none | version-1 | version-2}

no receive

Context

[Tree] (config>service>vprn>rip receive)

[Tree] (config>service>vprn>ripng>group>neighbor receive)

[Tree] (config>service>vprn>rip>group receive)

[Tree] (config>service>vprn>ripng>group receive)

[Tree] (config>service>vprn>ripng receive)

[Tree] (config>service>vprn>rip>group>neighbor receive)

Full Context

configure service vprn rip receive

configure service vprn ripng group neighbor receive

configure service vprn rip group receive

configure service vprn ripng group receive

configure service vprn ripng receive

configure service vprn rip group neighbor receive

Description

This command configures the type(s) of RIP updates that will be accepted and processed.

If both or version-2 is specified, the RIP instance listens for and accepts packets sent to the broadcast and multicast (224.0.0.9) addresses.

If version-1 is specified, the router only listens for and accepts packets sent to the broadcast address.

This control can be issued at the global, group or interface level. The default behavior accepts and processes both RIPv1 and RIPv2 messages.

The no form of this command resets the type of messages accepted to both.

Default

no receive

Parameters

both

Accept RIP updates in either Version 1 or Version 2 format.

none

Do not accept and RIP updates.

version-1

Router should only accept RIP updates in Version 1 format.

version-2

Router should only accept RIP updates in Version 2 format.

Platforms

All

receive

Syntax

receive

Context

[Tree] (config>system>security>keychain>direction>uni receive)

Full Context

configure system security keychain direction uni receive

Description

This command enables the receive nodal context. Entries defined under this context are used to authenticate TCP segments that are being received by the router.

Platforms

All

receive

Syntax

receive option-number

no receive

Context

[Tree] (config>system>security>keychain>tcp-option-number receive)

Full Context

configure system security keychain tcp-option-number receive

Description

This command configures the TCP option number accepted in TCP packets received.

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

Default

receive 254

Parameters

option-number

Specifies an enumerated integer that indicates the TCP option number to be used in the TCP header.

Values

253, 254, 253&254, tcp-ao

Platforms

All

receive

Syntax

receive {both | none | version-1 | version-2}

no receive

Context

[Tree] (config>router>rip>group>neighbor receive)

[Tree] (config>router>ripng>group receive)

[Tree] (config>router>ripng>group>neighbor receive)

[Tree] (config>router>rip>group receive)

[Tree] (config>router>ripng receive)

[Tree] (config>router>rip receive)

Full Context

configure router rip group neighbor receive

configure router ripng group receive

configure router ripng group neighbor receive

configure router rip group receive

configure router ripng receive

configure router rip receive

Description

This command configures the types of RIP updates that will be accepted and processed.

If both or version-2 is specified, the RIP instance listens for and accepts packets sent to the broadcast and multicast (224.0.0.9) addresses.

If version-1 is specified, the router only listens for and accept packets sent to the broadcast address.

This control can be issued at the global, group or interface level. The default behavior is to accept and process both RIPv1 and RIPv2 messages.

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

Default

receive both – in the config>router>rip context

receive version-1 – in the config>router>ripng context

Parameters

both

Specifies that RIP updates in either version 1 or version 2 format will be accepted.

none

Specifies that RIP updates will not be accepted.

version-1

Specifies that RIP updates in version 1 format only will be accepted.

version-2

Specifies that RIP updates in version 2 format only will be accepted.

Platforms

All

receive-interval

receive-interval

Syntax

receive-interval receive-interval

no receive-interval

Context

[Tree] (config>lag>bfd>family receive-interval)

Full Context

configure lag bfd family receive-interval

Description

This command specifies the receive timer used for micro-BFD session over the associated LAG links.

The no form of this command removes the receive timer from the configuration.

Default

receive-interval 100

Parameters

receive-interval

Specifies the interval value, in milliseconds.

Values

10 to 100000

Default

100 for CPM3 or later, 1000 for all others

Platforms

All

receive-interval

Syntax

receive-interval receive-interval

no receive-interval

Context

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

Full Context

configure router bfd bfd-template receive-interval

Description

This command specifies the receive timer used for BFD packets. If the template is used for a BFD session on an MPLS-TP LSP, then this timer is used for CC packets.

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

Default

receive-interval 100

Parameters

receive-interval

Specifies the receive interval. The minimum interval that can be configured is hardware dependent.

Values

10 ms to 100,000 ms in 1 ms intervals

Default

10 ms for CPM3 or higher; 1 second for other hardware

Platforms

All

receive-interval

Syntax

receive-interval receive-interval

no receive-interval

Context

[Tree] (config>router>lsp-bfd>tail-end receive-interval)

Full Context

configure router lsp-bfd tail-end receive-interval

Description

This command configures the LSP BFD minimum receive interval for the tail end of LSP BFD sessions.

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

Default

receive-interval 1000

Parameters

receive-interval

Specifies the receive interval, in milliseconds.

Values

100 to 1000

Default

1000

Platforms

All

receive-msdp-msg-rate

receive-msdp-msg-rate

Syntax

receive-msdp-msg-rate number interval seconds [threshold number]

no receive-msdp-msg-rate

Context

[Tree] (config>service>vprn>msdp receive-msdp-msg-rate)

[Tree] (config>service>vprn>msdp>group receive-msdp-msg-rate)

[Tree] (config>service>vprn>msdp>group>peer receive-msdp-msg-rate)

[Tree] (config>service>vprn>msdp>peer receive-msdp-msg-rate)

Full Context

configure service vprn msdp receive-msdp-msg-rate

configure service vprn msdp group receive-msdp-msg-rate

configure service vprn msdp group peer receive-msdp-msg-rate

configure service vprn msdp peer receive-msdp-msg-rate

Description

This command limits the number of Multicast Source Discovery Protocol (MSDP) messages that are read from the TCP session. It is possible that an MSDP/ RP router may receive a large number of MSDP protocol message packets in a particular source active message.

After the number of MSDP packets (including source active messages) defined in the threshold have been processed, the rate of all other MSDP packets is rate limited by no longer accepting messages from the TCP session until the time (seconds) has elapsed.

The no form of this command reverts this active-source limit to default operation.

Default

no receive-msdp-msg-rate

Parameters

number

Defines the number of MSDP messages (including source active messages) that are read from the TCP session per the number of seconds.

Values

10 to 10000

Default

0

interval seconds

Defines the time that, together with the number parameter, defines the number of MSDP messages (including source active messages) that are read from the TCP session within the configured number of seconds.

Values

1 to 600

Default

0

threshold number

The number of MSDP messages can be processed before the MSDP message rate limiting function described above is activated; this is particularly of use during at system startup and initialization.

Values

1 to 1000000

Default

0

Platforms

All

receive-msdp-msg-rate

Syntax

receive-msg-rate number interval seconds [threshold number]

no receive-msg-rate

Context

[Tree] (config>router>msdp>group>peer receive-msdp-msg-rate)

[Tree] (config>router>msdp>peer receive-msdp-msg-rate)

[Tree] (config>router>msdp>group receive-msdp-msg-rate)

[Tree] (config>router>msdp receive-msdp-msg-rate)

Full Context

configure router msdp group peer receive-msdp-msg-rate

configure router msdp peer receive-msdp-msg-rate

configure router msdp group receive-msdp-msg-rate

configure router msdp receive-msdp-msg-rate

Description

This command limits the number of Multicast Source Discovery Protocol (MSDP) messages that are read from the TCP session. It is possible that an MSDP/ RP router may receive a large number of MSDP protocol message packets in a particular source active message.

After the number of MSDP packets (including source active messages) defined in the threshold have been processed, the rate of all other MSDP packets is rate limited by no longer accepting messages from the TCP session until the time (seconds) has elapsed.

The no form of this command sets no limit on the number of MSDP and source active limit messages that will be accepted.

Default

no receive-msdp-msg-rate

Parameters

number

Specifies the number of MSDP messages (including source active messages) that are read from the TCP session per the number of seconds.

Values

10 to 10000

Default

0

seconds

Specifies the time that, together with the number parameter, defines the number of MSDP messages (including source active messages) that are read from the TCP session within the configured number of seconds.

Values

1 to 600

Default

0

number

Specifies the number of MSDP messages can be processed before the MSDP message rate limiting function described above is activated; this is particularly of use during at system startup and initialization.

Values

1 to 1000000

Default

0

Platforms

All

receive-window-size

receive-window-size

Syntax

receive-window-size window-size

no receive-window-size

Context

[Tree] (config>service>vprn>l2tp>group receive-window-size)

[Tree] (config>router>l2tp>group receive-window-size)

[Tree] (config>service>vprn>l2tp receive-window-size)

[Tree] (config>router>l2tp>group>tunnel receive-window-size)

[Tree] (config>service>vprn>l2tp>group>tunnel receive-window-size)

[Tree] (config>router>l2tp receive-window-size)

Full Context

configure service vprn l2tp group receive-window-size

configure router l2tp group receive-window-size

configure service vprn l2tp receive-window-size

configure router l2tp group tunnel receive-window-size

configure service vprn l2tp group tunnel receive-window-size

configure router l2tp receive-window-size

Description

This command configures the L2TP receive window size.

Default

receive-window-size 64

Parameters

window-size

Specifies the window size.

Values

4 to 1024

Platforms

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

receiver

receiver

Syntax

receiver receiver-name [create]

no receiver

Context

[Tree] (config>sflow receiver)

Full Context

configure sflow receiver

Description

This command creates an sFlow receiver context or enters existing sFlow receiver context for the sFlow agent.

The no form of this command deletes an existing sFlow receiver context.

Parameters

receiver-names

String of up to 127 characters.

Platforms

7750 SR, 7750 SR-s, 7950 XRS

reclassify-using-qos

reclassify-using-qos

Syntax

reclassify-using-qos policy-id

no reclassify-using-qos

Context

[Tree] (config>service>ies>if>vpls>egress reclassify-using-qos)

Full Context

configure service ies interface vpls egress reclassify-using-qos

Description

The reclassify-using-qos command is used to specify a sap-egress QoS policy that will be used to reclassify the forwarding class and profile of egress routed packets on the VPLS or I-VPLS service. When routed packets associated with the IP interface egress a VPLS SAP, the reclassification rules within the sap-egress QoS policy applied to the SAP are always ignored (even when reclassify-using-qos is not defined).

Any queues or policers defined within the specified QoS policy are ignored and are not created on the VPLS egress SAPs. Instead, the routed packets continue to use the forwarding class mappings, queues and policers from the sap-egress QoS policy applied to the egress VPLS SAP.

While the specified sap-egress policy ID is applied to an IP interface it cannot be deleted from the system.

The no form of this command removes the sap-egress QoS policy used for reclassification from the egress IP interface. When removed, IP routed packets will not be reclassified on the egress SAPs of the VPLS service attached to the IP interface.

Parameters

policy-id

Specifies the SAP egress QoS policy ID. This parameter is required when executing the reclassify-using-qos command. The specified SAP egress QoS ID must exist within the system or the command fails.

Platforms

All

reclassify-using-qos

Syntax

reclassify-using-qos policy-id

no reclassify-using-qos

Context

[Tree] (config>service>vprn>if>vpls>egress reclassify-using-qos)

Full Context

configure service vprn interface vpls egress reclassify-using-qos

Description

This command specifies a SAP egress QoS policy that is used to reclassify the forwarding class and profile of egress routed packets on the VPLS service. When routed packets associated with the IP interface egress a VPLS SAP, the reclassification rules within the sap-egress QoS policy applied to the SAP are always ignored (even when reclassify-using-qos is not defined).

Any queues or policers defined within the specified QoS policy are ignored and are not created on the VPLS egress SAPs. Instead, the routed packets continue to use the forwarding class mappings, queues and policers from the SAP egress QoS policy applied to the egress VPLS SAP.

While the specified SAP egress policy ID is applied to an IP interface it cannot be deleted from the system.

The no form of this command removes the SAP egress QoS policy used for reclassification from the egress IP interface. When removed, IP routed packets is not reclassified on the egress SAPs of the VPLS service attached to the IP interface.

Parameters

policy-id

Specifies the SAP egress QoS policy ID This parameter is required when executing the reclassify-using-qos command. The specified SAP egress QoS ID must exist within the system or the command fails.

Platforms

All

reconnect-timeout

reconnect-timeout

Syntax

reconnect-timeout reconnect-timeout

reconnect-timeout infinite

no reconnect-timeout

Context

[Tree] (config>service>vprn>l2tp>group reconnect-timeout)

[Tree] (config>router>l2tp>eth-tunnel reconnect-timeout)

[Tree] (config>service>vprn>l2tp reconnect-timeout)

[Tree] (config>router>l2tp>group>eth-tunnel reconnect-timeout)

Full Context

configure service vprn l2tp group reconnect-timeout

configure router l2tp eth-tunnel reconnect-timeout

configure service vprn l2tp reconnect-timeout

configure router l2tp group eth-tunnel reconnect-timeout

Description

This command configures the number of seconds that the Ethernet tunnel client of L2TPv3 waits before attempting to re-establish a new session after a session setup fails or a session closes.

The no form of this command returns reconnect-timeout to an infinite timeout value, meaning that reconnection is not attempted by the local client.

Default

no reconnect-timeout (infinite timeout)

Parameters

reconnect-timeout

Specifies the number of seconds before a session reconnection is attempted after a previous session or session setup fails.

Values

10 to 3600

Platforms

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

reconnect-timeout

Syntax

reconnect-timeout reconnect-timeout

no reconnect-timeout

Context

[Tree] (config>service>vprn>l2tp>eth-tunnel reconnect-timeout)

Full Context

configure service vprn l2tp eth-tunnel reconnect-timeout

Description

This command configures the number of seconds that the Ethernet tunnel client of L2TPv3 waits before attempting to re-establish a new session after a session setup fails or a session closes.

The no form of this command returns reconnect-timeout to an infinite timeout value, meaning that reconnection is not attempted by the local client.

Default

no reconnect-timeout (infinite timeout)

Parameters

reconnect-timeout

Specifies the timeout value for the next session setup retry.

Values

10 to 3600

Platforms

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

reconnect-timeout

Syntax

reconnect-timeout reconnect-timeout

reconnect-timeout infinite

no reconnect-timeout

Context

[Tree] (config>service>vprn>l2tp>group>eth-tunnel reconnect-timeout)

Full Context

configure service vprn l2tp group eth-tunnel reconnect-timeout

Description

This command configures the number of seconds that the Ethernet tunnel client of L2TPv3 waits before attempting to re-establish a new session after a session setup fails or a session closes.

The no form of this command returns reconnect-timeout to an infinite timeout value, meaning that reconnection is not attempted by the local client.

Default

no reconnect-timeout (infinite timeout)

Parameters

reconnect-timeout

Specifies the timeout value for the next session setup retry.

Values

10 to 3600

infinite

Specifies the timeout value for the next session setup retry.

Platforms

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

record

record

Syntax

[no] record

Context

[Tree] (config>router>mpls>lsp>primary record)

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

[Tree] (config>router>mpls>lsp>secondary record)

[Tree] (config>router>mpls>lsp>primary-p2mp-instance record)

Full Context

configure router mpls lsp primary record

configure router mpls lsp-template record

configure router mpls lsp secondary record

configure router mpls lsp primary-p2mp-instance record

Description

This command enables recording of all the hops that an LSP path traverses. Enabling record increases the size of the PATH and RESV refresh messages for the LSP since this information is carried end-to-end along the path of the LSP. The increase in control traffic per LSP may impact scalability.

The config>router>mpls>lsp>primary-p2mp-instance>record command is not supported on the 7450 ESS.

The no form of this command disables the recording of all the hops for the given LSP. There are no restrictions as to when the no command can be used. The no form of this command also disables the record-label command.

Default

record

Platforms

All

record

Syntax

record

Context

[Tree] (debug>app-assure>group>traffic-capture record)

Full Context

debug application-assurance group traffic-capture record

Description

This command configures traffic recording options.

Platforms

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

record

Syntax

record {all-hosts | http-host-app-filter-candidates}

Context

[Tree] (debug>app-assure>group>http-host>filter record)

Full Context

debug application-assurance group http-host-recorder filter record

Description

This command configures which http-host are selected for the http-host-recorder. It is either any http-host values going through the AA ISA or the http-host corresponding to flows not matching a string based app-filter.

For the feature to work it is required to configure at least one app-filter to catch the HTTP protocol signature.

Parameters

all-hosts | http-host-app-filter-candidates

Specifies which hosts the recorder will record

Values

all-hosts, http-host-app-filter-candidates

Default

http-host-app-filter-candidates

Platforms

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

record

Syntax

[no] record record-name

Context

[Tree] (config>log>accounting-policy record)

Full Context

configure log accounting-policy record

Description

This command adds the accounting record type to the accounting policy that is forwarded to the configured accounting file. A record name can only be used in one accounting policy. To obtain a list of all record types that can be configured, use the show log accounting-records command.

Note:

aa, video, and subscriber records are not applicable to the 7950 XRS.

To configure an accounting policy for access ports, select a service record (for example, service-ingress-octets). To change the record name to another service record, enter the record command with the new record name and it replaces the old record name.

When configuring an accounting policy for network ports, select a network record. To change the record name to another network record, enter the record command with the new record name and it replaces the old record name.

If the change required modifies the record from network to service or from service to network, then the old record name must be removed using the no form of this command.

Only one record can be configured in a single accounting policy. For example, if an accounting-policy is configured with an access-egress-octets record, to change it to a service-ingress-octets record, use the no record command under the accounting-policy to remove the old record first, and then enter the service-ingress-octets record.

Note:

Collecting excessive statistics can adversely affect the CPU utilization and take up large amounts of storage space.

The no form of this command removes the record type from the policy.

Default

no record

Parameters

record-name

Specifies the accounting record name.

Platforms

All

record

Syntax

record record-name

no record

Context

[Tree] (config>log>acct-policy record)

Full Context

configure log accounting-policy record

Description

This command enables the collection of rate statistics on egress of SR-MPLS and SRv6 policies.

The no form of this command removes the accounting record type to be forwarded to the configured accounting file

Platforms

All

record-label

record-label

Syntax

[no] record-label

Context

[Tree] (config>router>mpls>lsp>primary record-label)

[Tree] (config>router>mpls>lsp>secondary record-label)

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

Full Context

configure router mpls lsp primary record-label

configure router mpls lsp secondary record-label

configure router mpls lsp-template record-label

Description

This command enables recording of all the labels at each node that an LSP path traverses. Enabling the record-label command will also enable the record command if it is not already enabled.

The no form of this command disables the recording of the hops that an LSP path traverses.

Default

record-label

Platforms

All

record-stats

record-stats

Syntax

record-stats {delay | loss | delay-and-loss}

no record-stats

Context

[Tree] (config>oam-pm>session>ip>twamp-light record-stats)

Full Context

configure oam-pm session ip twamp-light record-stats

Description

This option provides the ability to determine which statistics are recorded. The TWAMP-Light PDU can report on both delay and loss using a single packet. The operator may choose which statistics they would like to report. Only delay recording is on by default. All other metrics are ignored. In order to change what is being recorded and reported, the TWAMP-Light session must be shutdown. This is required because the single packet approach means the base statistics are shared between the various datasets. Issuing a no shutdown command clears previous all non-volatile memory for the session and allocate new memory blocks. All the parameters under this context are mutually exclusive.

The no version of the command restores the default "delay” only.

Default

record-stats delay

Parameters

delay

Specifies report on delay using a single packet..

loss

Specifies to report on loss using a single packet..

delay-and-loss

Specifies to report on both delay and loss using a single packet.

Platforms

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

recovery

recovery

Syntax

[no] recovery

Context

[Tree] (debug>router>l2tp>tunnel>event recovery)

[Tree] (debug>router>l2tp>group>event recovery)

[Tree] (debug>router>l2tp>event recovery)

[Tree] (debug>router>l2tp>peer>event recovery)

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

Full Context

debug router l2tp tunnel event recovery

debug router l2tp group event recovery

debug router l2tp event recovery

debug router l2tp peer event recovery

debug router l2tp assignment-id event recovery

Description

This command configures L2TP LAC state recovery event debugging.

Platforms

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

recovery-failed

recovery-failed

Syntax

[no] recovery-failed

Context

[Tree] (debug>router>l2tp>event recovery-failed)

[Tree] (debug>router>l2tp>assignment-id>event recovery-failed)

[Tree] (debug>router>l2tp>tunnel>event recovery-failed)

[Tree] (debug>router>l2tp>peer>event recovery-failed)

[Tree] (debug>router>l2tp>group>event recovery-failed)

Full Context

debug router l2tp event recovery-failed

debug router l2tp assignment-id event recovery-failed

debug router l2tp tunnel event recovery-failed

debug router l2tp peer event recovery-failed

debug router l2tp group event recovery-failed

Description

This command configures L2TP LAC state recovery failed event debugging.

Platforms

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

recovery-max-session-lifetime

recovery-max-session-lifetime

Syntax

recovery-max-session-lifetime minutes

no recovery-max-session-lifetime

Context

[Tree] (config>router>l2tp>failover recovery-max-session-lifetime)

[Tree] (config>service>vprn>l2tp>failover recovery-max-session-lifetime)

Full Context

configure router l2tp failover recovery-max-session-lifetime

configure service vprn l2tp failover recovery-max-session-lifetime

Description

This command configures the sub-set of sessions that this system attempts to synchronize in the Session State Synchronization phase as described in RFC 4951, Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP).

The no form of this command reverts to the default.

Default

recovery-max-session-lifetime 2

Parameters

minutes

Specifies the sub-set of sessions to recover.

Values

2 to 4294967295

Platforms

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

recovery-method

recovery-method

Syntax

recovery-method method

no recovery-method

Context

[Tree] (config>service>vprn>l2tp>failover recovery-method)

[Tree] (config>router>l2tp>group>tunnel>failover recovery-method)

[Tree] (config>service>vprn>l2tp>group>failover recovery-method)

[Tree] (config>router>l2tp>failover recovery-method)

[Tree] (config>service>vprn>l2tp>group>tunnel>failover recovery-method)

[Tree] (config>router>l2tp>group>failover recovery-method)

Full Context

configure service vprn l2tp failover recovery-method

configure router l2tp group tunnel failover recovery-method

configure service vprn l2tp group failover recovery-method

configure router l2tp failover recovery-method

configure service vprn l2tp group tunnel failover recovery-method

configure router l2tp group failover recovery-method

Description

This command sets the recovery method to be used for newly created tunnels.

The no form of this command reverts to the default.

Default

recovery-method mcs on config>router>l2tp>failover and config>service>vprn>l2tp>failover

recovery-method default on config>router>l2tp>group>failover

recovery-method default on config>router>l2tp>group>tunnel>failover

recovery-method default on config>service>vprn>l2tp>group>failover

recovery-method default on config>service>vprn>l2tp>group>tunnel>failover

Parameters

method

Describes how a pair of redundant LAC peers recover tunnel and session state (sequence numbers, for example) immediately after a failover.

Note:

While failover is enabled, the tunnels and sessions proper are always kept synchronized between the redundant pair, regardless of the recovery method for the sequence numbers when a failover really occurs.

Values

mcs — Specifies that the stateful information is recovered from the failover peer directly, using Multi-Chassis Redundancy Synchronization (MCS).

recovery-tunnel — Specifies that the stateful information is recovered as described in RFC 4951, Fail Over Extensions for Layer 2 Tunneling Protocol (L2TP). This method uses a recovery tunnel to the L2TP peer to pass the stateful information.

default — Specifies that the actual value must be derived from another object of the same type with a wider scope. Takes the value of the next higher level (not available in config>router>l2tp>failover and config>service>vprn>l2tp>failover).

Platforms

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

recovery-time

recovery-time

Syntax

recovery-time seconds

no recovery-time

Context

[Tree] (config>router>l2tp>group>tunnel>failover recovery-time)

[Tree] (config>service>vprn>l2tp>group>tunnel>failover recovery-time)

[Tree] (config>service>vprn>l2tp>failover recovery-time)

[Tree] (config>router>l2tp>failover recovery-time)

[Tree] (config>service>vprn>l2tp>group>failover recovery-time)

[Tree] (config>router>l2tp>group>failover recovery-time)

Full Context

configure router l2tp group tunnel failover recovery-time

configure service vprn l2tp group tunnel failover recovery-time

configure service vprn l2tp failover recovery-time

configure router l2tp failover recovery-time

configure service vprn l2tp group failover recovery-time

configure router l2tp group failover recovery-time

Description

This command sets the recovery time to be negotiated via RFC 4951. It represents the extra time this L2TP peer (LAC or LNS) needs to recover all its tunnels.

The no form of this command reverts to the default.

Default

recovery-time 0 on config>router>l2tp>failover and config>service>vprn>l2tp>failover

Parameters

seconds

Specifies the period, expressed in seconds, an endpoint asks its peer to wait before assuming the recovery process has failed.

Values

0 to 900

Platforms

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

recovery-timer

recovery-timer

Syntax

[no] recovery-timer

Context

[Tree] (config>service>ipipe>eth-legacy-fault-notification recovery-timer)

Full Context

configure service ipipe eth-legacy-fault-notification recovery-timer

Description

Note: This command is no longer supported and will be removed in a future release.

Platforms

All

red

red

Syntax

red [detail]

no red

Context

[Tree] (debug>service>id>pim-snooping red)

Full Context

debug service id pim-snooping red

Description

This command enables or disables debugging for PIM messages sent to the standby CPM.

Parameters

detail

Displays detailed debugging information

Platforms

All

red

Syntax

[no] red [detail]

Context

[Tree] (debug>router>pim red)

Full Context

debug router pim red

Description

This command enables debugging for PIM redundancy messages to the standby CPM.

The no form of this command disables debugging for PIM redundancy messages to the standby CPM.

Parameters

detail

Displays detailed redundancy information.

Platforms

All

red

Syntax

red [detail]

no red

Context

[Tree] (debug>router>pcep>pcc red)

[Tree] (debug>router>pcep>pcc>conn red)

Full Context

debug router pcep pcc red

debug router pcep pcc connection red

Description

This command enables debugging for PCC or connection redundancy events.

The no form of this command disables debugging.

Parameters

detail

Keyword used to specify detailed information about PCC or connection redundancy events.

Platforms

All

red

Syntax

red [detail]

no red

Context

[Tree] (debug>router>pcep>pce>conn red)

[Tree] (debug>router>pcep>pce red)

Full Context

debug router pcep pce connection red

debug router pcep pce red

Description

This command enables debugging for PCE or connection redundancy events.

The no form of this command disables debugging.

Parameters

detail

Keyword used to specify detailed information about PCE or connection redundancy events.

Platforms

VSR-NRC

red-alarm-threshold

red-alarm-threshold

Syntax

red-alarm-threshold percentage

no red-alarm-threshold

Context

[Tree] (config>port>access>ingress>pool red-alarm-threshold)

[Tree] (config>port>network>egress>pool red-alarm-threshold)

[Tree] (config>port>access>egress>pool red-alarm-threshold)

Full Context

configure port access ingress pool red-alarm-threshold

configure port network egress pool red-alarm-threshold

configure port access egress pool red-alarm-threshold

Description

This command configures the threshold for the red alarm on the over-subscription allowed.

Users can selectively enable amber or red alarm thresholds. But if both are enabled (non-zero), the amber alarm threshold cannot be more than the red alarm threshold.

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

Default

no red-alarm-threshold

Parameters

percentage

Specifies the red alarm threshold.

Values

1 to 1000

Platforms

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

red-alarm-threshold

Syntax

red-alarm-threshold percentage

no red-alarm-threshold

Context

[Tree] (config>card>fp>ingress>network>pool red-alarm-threshold)

Full Context

configure card fp ingress network pool red-alarm-threshold

Description

This command configures the threshold for the red alarm on the over-subscription allowed.

Users can selectively enable amber or red alarm thresholds. But if both are enabled (non-zero) then the red alarm threshold must be greater than the amber alarm threshold.

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

Default

no amber-alarm-threshold

Parameters

percentage

Specifies the red alarm threshold.

Values

1 to 1000

Platforms

All

red-source-list

red-source-list

Syntax

red-source-list

Context

[Tree] (config>service>vprn>mvpn red-source-list)

Full Context

configure service vprn mvpn red-source-list

Description

This command enables context to configure list of redundant source prefixes for preferred source selection.

Platforms

All

redelegation-timer

redelegation-timer

Syntax

redelegation-timer seconds

no redelegation-timer

Context

[Tree] (config>router>pcep>pcc redelegation-timer)

Full Context

configure router pcep pcc redelegation-timer

Description

This command configures the redelegation timer for PCE-initiated LSPs.

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

Default

redelegation-timer 90

Parameters

seconds

Specifies the number of seconds before the redelegation timer expires.

Values

1 to 3600

Platforms

All

redirect-https

redirect-https

Syntax

redirect-https

no redirect-https

Context

[Tree] (config>app-assure>group>http-redirect redirect-https)

Full Context

configure application-assurance group http-redirect redirect-https

Description

This command configures the http-redirect policy to redirect HTTPS sessions to the configured redirect-url.

The no form of this command removes the redirect-https.

Platforms

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

redirect-policy

redirect-policy

Syntax

redirect-policy redirect-policy-name [create]

no redirect-policy redirect-policy-name

Context

[Tree] (config>filter redirect-policy)

Full Context

configure filter redirect-policy

Description

This command, creates a configuration context for the specified redirect policy.

The no form of the command removes the redirect policy from the filter configuration only if the policy is not referenced in a filter and the filter is not in use (applied to a service or network interface).

Parameters

redirect-policy-name

Specifies the redirect policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. There is no limit to the number of redirect policies that can be configured.

create

This keyword is required to create the configuration context. Once it is created, the context can be enabled with or without the create keyword.

Platforms

All

redirect-policy

Syntax

redirect-policy redirect-policy-name destination ip-address

no redirect-policy redirect-policy-name [destination ip-address]

Context

[Tree] (config>filter>redirect-policy-binding redirect-policy)

Full Context

configure filter redirect-policy-binding redirect-policy

Description

This command adds the destination (specified by its IP address) of a redirect-policy (specified by its name) to the binding. An error is thrown if either the destination does not exist for the specified redirect-policy or if the redirect-policy does not exist.

The no form of the command removes from the binding from all the destinations of the specified redirect-policy, or only the specified destination.

Parameters

redirect-policy-name

Specifies the name of the redirect-policy (up to 32 characters) as the destination that is to be added to the binding.

ip-address

The IP address of the destination. This can be an 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 to FFFF]H

d: [0 to 255]D

Platforms

All

redirect-policy-binding

redirect-policy-binding

Syntax

redirect-policy-binding name [create]

no redirect-policy-binding name

Context

[Tree] (config>filter redirect-policy-binding)

Full Context

configure filter redirect-policy-binding

Description

This command creates a redirect-policy binding (specified by its name) in case it does not exist and, enters the context associated with it. When a redirect-policy binding is created, no destination is associated to this binding by default and the binding operator is set to AND.

The no form of this command deletes the redirect-policy binding and all the associated configuration information.

Parameters

name

Specifies the name of the binding. Possible values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotations.

create

This keyword is required to create the binding if it does not exist. This has no effect when used with an existing binding.

Platforms

All

redirect-url

redirect-url

Syntax

redirect-url redirect-url

no redirect-hurl

Context

[Tree] (config>app-assure>group>http-redirect redirect-url)

Full Context

configure application-assurance group http-redirect redirect-url

Description

This command configures the http redirect URL which is the URL (page) that the user is redirected to when an HTTP redirect takes effect.

The operator can select the URL arguments to include in the redirect-url using either a specific template-id or by configuring the redirect-url using any of the supported macro substitution keywords. Only ESM and ESM-MAC sub types support $MAC, $SAP, $CID, and $RID macro substitution.

The no form of this command removes the redirect-url field from the configuration.

Parameters

redirect-url

Specifies the URL of the landing page

Values

macro substitutions:

$CATID

The category ID.

$CATNAME

The category name of the URL.

$URL

The Request-URI in the HTTP GET Request received.

$SUB

A string that represents the subscriber ID.

$IP

A string that represents the IP address of the subscriber host.

$RTRID

A string that represents the router ID.

$URLPRM

The HTTP URL parameter associated with the subscriber.

$MAC

A string that represents the MAC address of the subscriber host.

$SAP

A string that represents a SAP ID.

$CID

A string that represents the circuit-id or interface-id of the subscriber host (hexadecimal format).

$RID

A string that represents the remote-id of the subscriber host (hexadecimal format).

Platforms

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

redirect-vprn

redirect-vprn

Syntax

redirect-vprn

Context

[Tree] (config>router>dns redirect-vprn)

Full Context

configure router dns redirect-vprn

Description

This command configures the DNS resolution to be resolved via VPRN. If configured, all packet URL resolution is done through a DNS server that is reachable in a VPRN. This includes packets in the global routing table.

Default

redirect-vprn

Platforms

All

redirection

redirection

Syntax

redirection level

no redirection

Context

[Tree] (config>system>file-trans-prof redirection)

Full Context

configure system file-transmission-profile redirection

Description

This command enables system to accept HTTP redirection response, along with the max level of redirection. The virtual router may send a new request to another server if the requested resources are not available (temporarily available to another server).

Default

no redirection

Parameters

level

Specifies the maximum level of redirection of the file transmission profile max level of HTTP redirection.

Values

1 to 8

Platforms

All

redirection-policy

redirection-policy

Syntax

redirection-policy policy-name

no redirection-policy

Context

[Tree] (config>subscr-mgmt>igmp-policy redirection-policy)

Full Context

configure subscriber-mgmt igmp-policy redirection-policy

Description

This command will apply multicast redirection action to the subscriber. The redirection action along with the redirected interface (and possibly service id) is defined in the referenced policy-name. IGMP messages is redirected to an alternate interface if that alternate interface has IGMP enabled. The alternate interface does not have to have any multicast groups registered via IGMP. Currently all IGMP messages are redirected and there is no ability to selectively redirect IGMP messages based on match conditions (multicast-group address, source IP address, and so on). Multicast redirection is supported between VPRN services and also between interfaces within the Global Routing Context. Multicast Redirection is not supported between the VPRN services and the Global Routing Table (GRT).

IGMP state is maintained per subscriber host and per redirected interface. Traffic is however forwarded only on the redirected interface.

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

Parameters

policy-name

Specifies the redirection policy to be applied to this host IGMP policy up to 32 characters. This is a policy defined in the config>router>policy-option>policy-statement context.

Platforms

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

redirection-policy

Syntax

redirection-policy policy-name

no redirection-policy

Context

[Tree] (config>subscr-mgmt>mld-policy redirection-policy)

Full Context

configure subscriber-mgmt mld-policy redirection-policy

Description

This command applies multicast redirection action to the subscriber. The redirection action along with the redirected interface (and possibly service id) is defined in the referenced policy-name. MLD messages is redirected to an alternate interface if that alternate interface has MLD enabled. The alternate interface does not have to have any multicast groups registered via MLD. Currently all MLD messages are redirected and there is no ability to selectively redirect MLD messages based on match conditions (multicast-group address, source IP address, and so on). Multicast redirection is supported between VPRN services and also between interfaces within the Global Routing Context. Multicast Redirection is not supported between the VPRN services and the Global Routing Table (GRT).

MLD state is maintained per subscriber host and per redirected interface. Traffic is however forwarded only on the redirected interface.

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

Parameters

policy-name

Specifies a redirection policy name up to 32 characters. This is a regular policy defined under the configure>router>policy-option>policy-statement context.

Platforms

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

redirects

redirects

Syntax

redirects [number seconds]

no redirects

Context

[Tree] (config>service>ies>if>icmp redirects)

[Tree] (config>service>ies>sub-if>grp-if>icmp redirects)

[Tree] (config>service>ies>if>ipv6>icmp6 redirects)

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

[Tree] (config>service>vprn>if>icmp redirects)

[Tree] (config>service>vprn>if>ipv6>icmp6 redirects)

[Tree] (config>service>vprn>if redirects)

Full Context

configure service ies interface icmp redirects

configure service ies subscriber-interface group-interface icmp redirects

configure service ies interface ipv6 icmp6 redirects

configure service vprn network-interface icmp redirects

configure service vprn interface icmp redirects

configure service vprn interface ipv6 icmp6 redirects

configure service vprn interface redirects

Description

This command configures the rate for Internet Control Message Protocol (ICMP) redirect messages issued on the router interface.

When routes are not optimal on this router and another router on the same subnetwork has a better route, the router can issue an ICMP redirect to alert the sending node that a better route is available.

The redirects command enables the generation of ICMP redirects on the router interface. The rate at which ICMP redirects is issued can be controlled with the optional number and seconds parameters by indicating the maximum number of redirect messages that can be issued on the interface for a given time interval.

The no form of this command disables the generation of ICMP redirects on the router interface.

Default

redirects 100 10

Parameters

number

Specifies the maximum number of ICMP redirect messages to send. This parameter must be specified with the second parameter.

Values

10 to 1000

seconds

Specifies the time frame in seconds used to limit the number of ICMP redirect messages that can be issued.

Values

1 to 60

Platforms

All

  • configure service ies interface ipv6 icmp6 redirects
  • configure service vprn network-interface icmp redirects
  • configure service vprn interface ipv6 icmp6 redirects
  • configure service vprn interface icmp redirects
  • configure service vprn interface redirects
  • configure service ies interface icmp redirects

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

  • configure service ies subscriber-interface group-interface icmp redirects

redirects

Syntax

redirects [number number] [seconds seconds]

no redirects

Context

[Tree] (config>subscr-mgmt>git>ipv4>icmp redirects)

Full Context

configure subscriber-mgmt group-interface-template ipv4 icmp redirects

Description

This command configures the ICMPv4 redirect messages that are generated when routes are not optimal on the router and the node needs to be alerted that another router on the same subnetwork has a better route available.

When disabled, ICMPv4 redirects are not generated.

The no form of this command disables generation of redirect messages.

Default

redirects number 100 seconds 10

Parameters

number

Specifies the number of ICMPv4 redirects that are issued in the time frame specified by the seconds parameter.

Values

10 to 1000

Default

100

seconds

Specifies the time, in seconds, that is used to limit the number of ICMPv4 redirects issued.

Values

1 to 60

Default

10

Platforms

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

redirects

Syntax

redirects [number seconds]

no redirects

Context

[Tree] (config>router>if>icmp redirects)

Full Context

configure router interface icmp redirects

Description

This command enables and configures the rate for ICMP redirect messages issued on the router interface.

When routes are not optimal on this router, and another router on the same subnetwork has a better route, the router can issue an ICMP redirect to alert the sending node that a better route is available.

The redirects command enables the generation of ICMP redirects on the router interface. The rate at which ICMP redirects are issued can be controlled with the optional number and time parameters by indicating the maximum number of redirect messages that can be issued on the interface for a given time interval.

By default, generation of ICMP redirect messages is enabled at a maximum rate of 100 per 10 second time interval.

The no form of this command disables the generation of ICMP redirects on the router interface.

Default

redirects 100 10 — Maximum of 100 redirect messages in 10 seconds.

Parameters

number

The maximum number of ICMP redirect messages to send, expressed as a decimal integer. This parameter must be specified with the time parameter.

Values

10 to 1000

seconds

The time frame, in seconds, used to limit the number of ICMP redirect messages that can be issued, expressed as a decimal integer.

Values

1 to 60

Platforms

All

redirects

Syntax

redirects [number seconds]

no redirects

Context

[Tree] (config>router>if>ipv6>icmp6 redirects)

Full Context

configure router interface ipv6 icmp6 redirects

Description

This command configures the rate for ICMPv6 redirect messages. When configured, ICMPv6 redirects are generated when routes are not optimal on the router and another router on the same subnetwork has a better route to alert that node that a better route is available.

The no form of this command disables ICMPv6 redirects.

Default

redirects 100 10 (when IPv6 is enabled on the interface)

Parameters

number

Limits the number of redirects issued per the time frame specified in seconds parameter.

Values

10 to 1000

seconds

Determines the time frame, in seconds, that is used to limit the number of redirects issued per time frame.

Values

1 to 60

Platforms

All

redistribute-delay

redistribute-delay

Syntax

redistribute-delay redistribute-delay

no redistribute-delay

Context

[Tree] (config>router>ospf3>timers redistribute-delay)

[Tree] (config>router>ospf>timers redistribute-delay)

Full Context

configure router ospf3 timers redistribute-delay

configure router ospf timers redistribute-delay

Description

This command sets the internal OSPF hold down timer for external routes being redistributed into OSPF.

Shorting this delay can speed up the advertisement of external routes into OSPF but can result in additional OSPF messages if that source route is not yet stable.

The no form of this command resets the timer value back to the default value.

Note:

The timer granularity is 10 ms if the value is less than 500 ms, and 100 ms if the value is greater than or equal to 500 ms. Timer values are rounded down to the nearest granularity, for example a configured value of 550 ms is internally rounded down to 500 ms.

Default

redistribute-delay 1000

Parameters

redistribute-delay

Specifies the OSPF redistribution hold down time in milliseconds for external routes being advertised into OSPF.

Values

0 to 1000

Platforms

All

redistribute-external

redistribute-external

Syntax

[no] redistribute-external

Context

[Tree] (config>service>vprn>ospf>area>nssa redistribute-external)

[Tree] (config>service>vprn>ospf3>area>nssa redistribute-external)

Full Context

configure service vprn ospf area nssa redistribute-external

configure service vprn ospf3 area nssa redistribute-external

Description

This command enables the redistribution of external routes into the Not So Stubby Area (NSSA) or an NSSA area border router (ABR) that is exporting the routes into non-NSSA areas.

NSSA or Not So Stubby Areas are similar to stub areas in that no external routes are imported into the area from other OSPF areas. The major difference between a stub area and an NSSA is that the NSSA has the capability to flood external routes that it learns (providing it is an ASBR) throughout its area and via an ABR to the entire OSPF domain.

The no form of this command disables the default behavior to automatically redistribute external routes into the NSSA area from the NSSA ABR.

Default

redistribute-external — External routes are redistributed into the NSSA.

Platforms

All

redistribute-external

Syntax

[no] redistribute-external

Context

[Tree] (config>router>ospf>area>nssa redistribute-external)

[Tree] (config>router>ospf3>area>nssa redistribute-external)

Full Context

configure router ospf area nssa redistribute-external

configure router ospf3 area nssa redistribute-external

Description

This command enables the redistribution of external routes into the Not So Stubby Area (NSSA) or an NSSA area border router (ABR) that is exporting the routes into non-NSSA areas.

NSSA or Not So Stubby Areas are similar to stub areas in that no external routes are imported into the area from other OSPF or OSPF3 areas. The major difference between a stub area and an NSSA is that the NSSA has the capability to flood external routes that it learns (providing it is an ASBR) throughout its area and via an Area Border Router to the entire OSPF or OSPF3 domain.

The no form of this command disables the default behavior to automatically redistribute external routes into the NSSA area from the NSSA ABR.

Default

redistribute-external

Platforms

All

redo

redo

Syntax

redo [count]

Context

[Tree] (candidate redo)

Full Context

candidate redo

Description

This command reapplies the changes to the candidate that were removed using a previous undo. All undo or redo history is lost when the operator exits edit-cfg mode.

A redo command is blocked if another user has made changes in the same CLI branches that would be impacted during the redo.

Parameters

count

Specifies the number of previous changes to reapply.

Values

1 to 50

Default

1

Platforms

All

reduced-prompt

reduced-prompt

Syntax

reduced-prompt [no-of-nodes-in-prompt]

no reduced-prompt

Context

[Tree] (environment reduced-prompt)

Full Context

environment reduced-prompt

Description

This command configures the maximum number of higher CLI context levels to display in the CLI prompt for the current CLI session. This command is useful when configuring features that are several node levels deep, causing the CLI prompt to become too long. By default, the CLI prompt displays the system name and the complete context in the CLI.

The number of nodes specified indicates the number of higher-level contexts that can be displayed in the prompt. For example, if reduced prompt is set to 2, the two highest contexts from the present working context are displayed by name with the hidden (reduced) contexts compressed into a ellipsis ("…”).

A:ALA-1>environment# reduced-prompt 2
A:ALA-1>config>router# interface to-103
A:ALA-1>...router>if#

The setting is not saved in the configuration. It must be reset for each CLI session or stored in an exec script file.

The no form of the command reverts to the default.

Default

no reduced-prompt

Parameters

no-of-nodes-in-prompt

Specifies the maximum number of higher-level nodes displayed by name in the prompt, expressed as a decimal integer.

Values

0 to 15

Default

2

Platforms

All

redundancy

redundancy

Syntax

redundancy

Context

[Tree] (config redundancy)

Full Context

configure redundancy

Description

This command allows the user to perform redundancy operations.

Associated commands include the following in the admin>redundancy context:

  • force-switchover - Forces a switchover to the standby CPM card.

  • now - Switch to standby CPM.

    Switching to the standby displays the following message.

    WARNING: Configuration and/or Boot options may have changed since the last save.

    Are you sure you want to switchover (y/n)?

  • synchronize - Synchronizes the secondary CPM.

Platforms

All

redundancy

Syntax

redundancy

Context

[Tree] (admin redundancy)

Full Context

admin redundancy

Description

Commands in this context allow the user to perform redundancy operations.

Platforms

All

redundancy

Syntax

redundancy

Context

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

Full Context

configure service ies subscriber-interface wlan-gw redundancy

Description

Commands in this context configure WLAN-GW redundancy-related parameters.

Platforms

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

redundancy

Syntax

redundancy

Context

[Tree] (config>service>vprn>nat>inside redundancy)

[Tree] (config>router>nat>inside redundancy)

[Tree] (config>service>vprn>nat>outside>pool redundancy)

Full Context

configure service vprn nat inside redundancy

configure router nat inside redundancy

configure service vprn nat outside pool redundancy

Description

Commands in this context configure redundancy parameters.

Platforms

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

redundancy

Syntax

redundancy {active-active | active-standby | l2aware-bypass}

no redundancy

Context

[Tree] (config>isa>nat-group redundancy)

Full Context

configure isa nat-group redundancy

Description

This command configures intra-chassis redundancy mode for the NAT group.

Default

redundancy active-standby

Parameters

active-active

Specifies the mode in which all MS-ISAs in a NAT group are active. If one or two MS-ISAs in the system fail, the remaining active MS-ISA accepts the load from the failed MS-ISAs.

active-standby

Specifies the mode in which one or more MS-ISAs in the NAT group are in standby mode. While in standby mode, MS-ISAs do not process traffic. Traffic is diverted to the standby MS-ISA only when the active MS-ISA fails, at which point the standby becomes active.

l2-aware-bypass

Specifies that when an ISA MDA fails, NAT reroutes its traffic based on the regular destination address lookup. This resiliency mode is applicable only to L2-Aware NAT. When the MS-ISA fails, its traffic is routed via regular routing (destination-based lookup). The assumption is that traffic is sent to an external NAT device that serves as a backup NAT device.

Platforms

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

redundancy

Syntax

redundancy

Context

[Tree] (config>router>nat>outside>pool redundancy)

Full Context

configure router nat outside pool redundancy

Description

Commands in this context configure NAT pool redundancy parameters.

Platforms

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

redundancy

Syntax

redundancy

Context

[Tree] (config>eth-cfm redundancy)

Full Context

configure eth-cfm redundancy

Description

Commands in this context configure the ETH-CFM redundancy parameters.

Platforms

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

redundant-interface

redundant-interface

Syntax

redundant-interface red-ip-int-name

no redundant-interface

Context

[Tree] (config>service>vprn>sub-if>grp-if redundant-interface)

[Tree] (config>service>ies>sub-if>grp-if redundant-interface)

Full Context

configure service vprn subscriber-interface group-interface redundant-interface

configure service ies subscriber-interface group-interface redundant-interface

Description

This command configures a redundant interface used for dual homing.

Parameters

red-ip-int-name

Specifies the redundant IP interface name.

Platforms

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

redundant-interface

Syntax

redundant-interface ip-int-name [create]

no redundant-interface ip-int-name

Context

[Tree] (config>service>ies redundant-interface)

[Tree] (config>service>vprn redundant-interface)

Full Context

configure service ies redundant-interface

configure service vprn redundant-interface

Description

This command configures a redundant interface.

Parameters

ip-int-name

Specifies the name of the IP interface. Interface names can be from 1 to 32 alphanumeric characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

create

Keyword used to create a redundant interface.

Platforms

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

redundant-interface

Syntax

redundant-interface service service-id name interface-name

no redundant-interface

Context

[Tree] (config>subscr-mgmt>up-resiliency>fsg-template redundant-interface)

Full Context

configure subscriber-mgmt up-resiliency fate-sharing-group-template redundant-interface

Description

This command configures downstream traffic shunting from a standby BNG-UP to an active BNG-UP. Downstream traffic that is received for standby sessions is sent over the redundant interface to the active BNG-UP. This requires the configuration of the multi-chassis-shunt-id command in the service that receives the session traffic.

The noform of the command removes the configuration.

Parameters

service-id

Specifies the name of the VPRN or IES service that contains the redundant interface, up to 64 characters. This can be different from the service where session traffic is terminated.

interface-name

Specifies the redundant interface name, up to 32 characters. It must exist within the configured service-id.

Platforms

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

redundant-mcast-capacity

redundant-mcast-capacity

Syntax

redundant-mcast-capacity primary-percentage secondary secondary-percentage

no redundant-mcast-capacity

Context

[Tree] (config>mcast-mgmt>chassis-level>plane-capacity redundant-mcast-capacity)

Full Context

configure mcast-management chassis-level per-mcast-plane-capacity redundant-mcast-capacity

Description

This command configures the primary and secondary multicast plane capacities used when the full complement of possible switch fabrics in the system are up. The rates are defined as a percentage of the total multicast plane capacity which is configured using the total-capacity command.

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

Default

redundant-mcast-capacity 87.50 secondary 87.50

Parameters

primary-percentage

Specifies the percentage of the total multicast plane capacity to be used for primary multicast planes.

Values

0.01 to 100

secondary-percentage

Specifies the percentage of the total multicast plane capacity to be used for secondary multicast planes.

Values

0.01 to 100

Platforms

7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR

redundant-multicast

redundant-multicast

Syntax

[no] redundant-multicast

Context

[Tree] (config>router>igmp>if redundant-multicast)

Full Context

configure router igmp interface redundant-multicast

Description

This command configures the interface as a member of a redundant pair for multicast traffic.

The no form of the command removes the configuration.

Platforms

All

ref-aa-specific-counter

ref-aa-specific-counter

Syntax

ref-aa-specific-counter any

no ref-aa-specific-counter

Context

[Tree] (config>log>acct-policy>cr ref-aa-specific-counter)

Full Context

configure log accounting-policy custom-record ref-aa-specific-counter

Description

This command enables the use of significant-change so only those aa-specific records which have changed in the last accounting interval are written.

The no form of this command disables the use of significant-change so all aa-specific records are written whether or not they have changed within the last accounting interval.

Parameters

any

Indicates that a record is collected as long as any field records activity when non-zero significant-change value is configured.

Platforms

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

ref-order

ref-order

Syntax

ref-order first second [third [fourth][fifth]]]

no ref-order

Context

[Tree] (config>system>sync-if-timing ref-order)

Full Context

configure system sync-if-timing ref-order

Description

The synchronous equipment timing subsystem can lock to different timing reference inputs, those specified in the ref1, ref2, bits, synce, and ptp command configuration. This command organizes the priority order of the timing references.

If a reference source is disabled, then the clock from the next reference source as defined by ref-order is used. If all reference sources are disabled, then clocking is derived from a local oscillator.

If a sync-if-timing reference is linked to a source port that is operationally down, the port is no longer qualified as a valid reference.

For 7450 ESS and 7750 SR systems with two CPM modules, the system distinguishes between the BITS inputs on the active and standby CPMs. The active CPM will use its BITS input port providing that port is qualified. If the local port is not qualified, then the active CPM will use the BITS input port from the standby CPM as the next priority reference. For example, the normal ref-order of bits ref1 ref2 will actually be bits (active CPM), followed by bits (standby CPM), followed by ref1, followed by ref2.

For 7950 XRS systems with two CPMs and two CCMs, the system distinguishes between the BITS inputs on the CCMs associated with the active and standby CPMs. The active CPM will use the BITS input port on the associated CCM, provided that the port is qualified. If the local port is not qualified, then the active CPM will use the BITS input port from the CCM associated with the standby CPM as the next priority reference. For example, the normal ref-order of bits ref1 ref2 will actually be bits (active CCM), followed by bits (standby CCM), followed by ref1, followed by ref2.

The no form of the command resets the reference order to the default values.

The SyncE/1588 port of the CPM or CCM can be used as a frequency input reference. It shares internal resources with the BITS input ports and so only one can be used at a time. The BITS port shall have priority, if BITS input is enabled, then the SyncE port cannot be enabled.

Similar to the BITS input ports, when the synce reference is enabled and in the ref-order, the system distinguishes between the synce inputs on the active and standby CPM/CCMs. The active CPM/CCM uses its synce input port if that port is qualified. If the local port is not qualified, the active CPM uses the synce input port from the standby CPM/CCM as the next priority reference. For example, the ref-order of synce ref1 ref2 will actually be synce (active CPM/CCM), followed by synce (standby CPM/CCM), followed by ref1, followed by ref2.

Default

bits synce ref1 ref2 ptp (7750 SR-7/12/12e with CPM-5, 7950 XRS-20/20e, SR-7s/14s, and 7450 ESS-7/12)

bits ref1 ref2 ptp (7750 SR-a4/8, SR-1e/2e/3e, SR-1, SR-1s/2s)

Parameters

first

Specifies the first timing reference to use in the reference order sequence.

Values

bits, synce, ref1, ref2, ptp

second

Specifies the second timing reference to use in the reference order sequence.

Values

bits, synce, ref1, ref2, ptp

third

Specifies the third timing reference to use in the reference order sequence.

Values

bits, synce, ref1, ref2, ptp

fourth

Specifies the fourth timing reference to use in the reference order sequence.

Values

bits, synce, ref1, ref2, ptp

fifth

Specifies the fifth timing reference to use in the reference order sequence.

Values

bits, synce, ref1, ref2, ptp

Platforms

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

ref-policer

ref-policer

Syntax

ref-policer policer-id

ref-policer all

no ref-policer

Context

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

Full Context

configure log accounting-policy custom-record ref-policer

Description

This command creates a policer context to configure reference policer counters for significant change only reporting. The custom record is only generated when the change in the sum of all queue and policer reference counters equals or exceeds the configured (non-zero) significant change value.

The no form of this command deletes all policer reference counters.

Default

no ref-policer

Parameters

policer-id

Specifies the policer for which reference counters are configured and to which significant-change is applied.

Values

1 to 63

all

Applies the significant-change to the specified counters for all policers.

Platforms

All

ref-queue

ref-queue

Syntax

ref-queue queue-id

ref-queue all

no ref-queue

Context

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

Full Context

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

Description

This command configures a reference queue.

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

Parameters

queue-id

Specifies the reference queue ID.

Values

1 to 32

all

Includes all reference queue IDs.

Platforms

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

ref-queue

Syntax

ref-queue queue-id

ref-queue all

no ref-queue

Context

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

Full Context

configure log accounting-policy custom-record ref-queue

Description

This command creates a queue context to configure reference queue counters for significant change only reporting. The custom record is only generated when the change in the sum of all queue and policer reference counters equals or exceeds the configured (non-zero) significant change value.

The no form of this command deletes all queue reference counters.

Default

no ref-queue

Parameters

queue-id

Specifies the queue for which reference counters are configured and to which the significant-change is applied.

Values

1 to 32

all

Applies the significant-change to the specified counters for all queues.

Platforms

All

ref1

ref1

Syntax

ref1

Context

[Tree] (config>system>sync-if-timing ref1)

Full Context

configure system sync-if-timing ref1

Description

Commands in this context configure parameters for the first timing reference.

The restrictions on the location for the source port or source bits for ref1 and ref2 are listed in Ref1 and Ref2 Timing References.

Platforms

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

ref1

Syntax

ref1

Context

[Tree] (conf>sys>sat>eth-sat>sync-if-timing ref1)

Full Context

configure system satellite eth-sat sync-if-timing ref1

Description

Commands in this context configure parameters for the first timing reference used in the ethernet satellite.

The source ports for ref1 can be either uplinks or client ports.

Platforms

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

ref2

ref2

Syntax

ref2

Context

[Tree] (config>system>sync-if-timing ref2)

Full Context

configure system sync-if-timing ref2

Description

Commands in this context configure parameters for the second timing reference. There are restrictions on the source-port and source-bits locations for ref2 based on the platform. The restrictions on the location for the source-port or source-bits for ref1 and ref2 are listed in Revertive, non-Revertive Timing Reference Switching Operation.

Platforms

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

ref2

Syntax

ref2

Context

[Tree] (conf>sys>sat>eth-sat>sync-if-timing ref2)

Full Context

configure system satellite eth-sat sync-if-timing ref2

Description

Commands in this context configure parameters for the second timing reference used in the ethernet satellite.

The source ports for ref2 can be either uplinks or client ports.

Platforms

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

reference-bandwidth

reference-bandwidth

Syntax

reference-bandwidth bandwidth-in-kbps

reference-bandwidth [zbps Zetta-bps] [ebps Exa-bps] [pbps Peta-bps] [tbps Tera-bps] [gbps Giga-bps] [mbps Mega-bps] [kbps Kilo-bps]

no reference-bandwidth

Context

[Tree] (config>service>vprn>isis reference-bandwidth)

Full Context

configure service vprn isis reference-bandwidth

Description

This command configures the reference bandwidth that provides the basis of bandwidth relative costing.

In order to calculate the lowest cost to reach a specific destination, each configured level on each interface must have a cost. If the reference bandwidth is defined, then the cost is calculated using the following formula:

cost = reference – bandwidth  bandwidth

If the reference bandwidth is configured as 10 Gigabits (10,000,000,000), a 100 M/bps interface has a default metric of 100. In order for metrics in excess of 63 to be configured, wide metrics must be deployed. (See wide-metrics-only in the config>router>isis context.)

If the reference bandwidth is not configured, all interfaces have a default metric of 10.

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

Default

no reference-bandwidth — No reference bandwidth is defined. All interfaces have a metric of 10.

Parameters

Zetta-bps

Specifies the reference bandwidth in zettabits per second, expressed as a decimal integer.

Values

1 to 18

Exa-bps

Specifies the reference bandwidth in exabits per second, expressed as a decimal integer.

Values

1 to 999

Peta-bps

Specifies the reference bandwidth in petabits per second, expressed as a decimal integer.

Values

1 to 999

bandwidth-in-kbps

Specifies the reference bandwidth in kilobits per second, expressed as a decimal integer.

Values

1 to 18446744073709551615

Tera-bps

Specifies the reference bandwidth in terabits per second, expressed as a decimal integer.

Values

1 to 999

Giga-bps

Specifies the reference bandwidth in gigabits per second, expressed as a decimal integer.

Values

1 to 999

Mega-bps

Specifies the reference bandwidth in megabits per second, expressed as a decimal integer.

Values

1 to 999

Kilo-bps

Specifies the reference bandwidth in kilobits per second, expressed as a decimal integer.

Values

1 to 999

Platforms

All

reference-bandwidth

Syntax

reference-bandwidth bandwidth-inkbps

reference-bandwidth [zbps Zetta-bps] [ebps Exa-bps] [pbps Peta-bps] [tbps Tera-bps] [gbps Giga-bps] [mbps Mega-bps] [kbps Kilo-bps]

no reference-bandwidth

Context

[Tree] (config>service>vprn>ospf3 reference-bandwidth)

[Tree] (config>service>vprn>ospf reference-bandwidth)

Full Context

configure service vprn ospf3 reference-bandwidth

configure service vprn ospf reference-bandwidth

Description

This command configures the reference bandwidth in kilobits per second (kb/s) that provides the reference for the default costing of interfaces based on their underlying link speed.

The default interface cost is calculated as follows:

cost = reference–bandwidth  bandwidth

The default reference-bandwidth is 100,000,000 kb/s or 100 Gb/s, so the default auto-cost metrics for various link speeds are as follows:

  • 10 Mb/s link default cost of 10000

  • 100 Mb/s link default cost of 1000

  • 1 Gb/s link default cost of 100

  • 10 Gb/s link default cost of 10

  • 40 Gb/s link default cost of 2

  • 100 Gb/s link default cost of 1

  • 400 Gb/s link default cost of 1

Note:

The default reference-bandwidth value must be manually configured to a higher value if interface speeds are greater than 100 Gb/s, and metrics based on link speed are used. When the default reference-bandwidth value is used, a metric of 1 is set on all interface speeds ≥ 100 Gb/s. For example, 100 GE, 100 GE LAG, 400 GE, and 400 GE LAG interfaces will all have a metric of 1.

If the reference bandwidth is configured as 10 Gb (reference-bandwidth 10000000000), a 100 Mb/s interface has a default metric of 100.

When a very large reference bandwidth value is configured, a metric calculation may result in a value higher than the supported protocol cost value. If this occurs, OSPF automatically reverts to the maximum configurable cost metric.

The reference-bandwidth command assigns a default cost to the interface based on the interface speed. To override this default cost on a particular interface, use the metric metric command configured in the config>router>ospf>area>if ip-int-name context.

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

Default

reference-bandwidth 100000000

Parameters

bandwidth-in-kbps

Specifies the reference bandwidth in kilobits per second expressed as a decimal integer.

Values

1 to 4000000000

tbps Tera-bps

Specifies the reference bandwidth in terabits per second expressed as a decimal integer.

Values

1 to 4

gbps Giga-bps

Specifies the reference bandwidth in gigabits per second expressed as a decimal integer.

Values

1 to 999

mbps Mega-bps

Specifies the reference bandwidth in megabits per second expressed as a decimal integer.

Values

1 to 999

kbps Kilo-bps

Specifies the reference bandwidth in kilobits per second expressed as a decimal integer.

Values

1 to 999

Platforms

All

reference-bandwidth

Syntax

reference-bandwidth bandwidth-in-kbps

reference-bandwidth [zbps Zetta-bps] [ebps Exa-bps] [pbps Peta-bps] [tbps Tera-bps] [gbps Giga-bps] [mbps Mega-bps] [kbps Kilo-bps]

no reference-bandwidth

Context

[Tree] (config>router>isis reference-bandwidth)

Full Context

configure router isis reference-bandwidth

Description

This command configures the reference bandwidth that provides the basis of bandwidth relative costing.

To calculate the lowest cost to reach a specific destination, each configured level on each interface must have a cost. If the reference bandwidth is defined, then the cost is calculated using the following formula:

cost = reference-bandwidth  bandwidth

If the reference bandwidth is configured as 10 Gb (reference-bandwidth 10000000000), a 100 Mb/s interface has a default metric of 100. To configure metrics in excess of 63, wide metrics must be deployed (see wide-metrics-only in the config>router>isis context).

When a large reference-bandwidth value is configured, a metric calculation may result in a value higher than the supported protocol cost value. If this occurs, IS-IS automatically reverts to the maximum configurable cost metric.

If the reference bandwidth is not configured, then all interfaces have a default metric of 10.

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

Default

no reference-bandwidth

Parameters

bandwidth-in-kbps

Specifies the reference bandwidth in kilobits per second, expressed as a decimal integer.

Values

1 to 18446744073709551615

Zetta-bps

Specifies the reference bandwidth in zettabits per second, expressed as a decimal integer.

Values

1 to 18

Exa-bps

Specifies the reference bandwidth in exabits per second, expressed as a decimal integer.

Values

1 to 999

Peta-bps

Specifies the reference bandwidth in petabits per second, expressed as a decimal integer.

Values

1 to 999

Tera-bps

Specifies the reference bandwidth in terabits per second, expressed as a decimal integer.

Values

1 to 999

Giga-bps

Specifies the reference bandwidth in gigabits per second, expressed as a decimal integer.

Values

1 to 999

Mega-bps

Specifies the reference bandwidth in megabits per second, expressed as a decimal integer.

Values

1 to 999

Kilo-bps

Specifies the reference bandwidth in kilobits per second, expressed as a decimal integer.

Values

1 to 999

Platforms

All

reference-bandwidth

Syntax

reference-bandwidth bandwidth-in-kbps

reference-bandwidth [zbps Zetta-bps] [ebps Exa-bps] [pbps Peta-bps] [tbps Tera-bps] [gbps Giga-bps] [mbps Mega-bps] [kbps Kilo-bps]

no reference-bandwidth

Context

[Tree] (config>router>ospf3 reference-bandwidth)

[Tree] (config>router>ospf reference-bandwidth)

Full Context

configure router ospf3 reference-bandwidth

configure router ospf reference-bandwidth

Description

This command configures the reference bandwidth in kilobits per second (kb/s) that provides the reference for the default costing of interfaces based on their underlying link speed.

The default interface cost is calculated as follows:

cost = reference-bandwidth  bandwidth

The default reference-bandwidth is 100,000,000 kb/s or 100 Gb/s, the default auto-cost metrics for various link speeds are as follows:

  • 10 Mb/s link default cost of 10000

  • 100 Mb/s link default cost of 1000

  • 1 Gb/s link default cost of 100

  • 10 Gb/s link default cost of 10

  • 100 Gb/s link default cost of 1

  • 400 Gb/s link default cost of 1

Note:

The default reference-bandwidth must be manually configured to a higher value if interface speeds are greater than 100 Gb/s, and metrics based on link speed are used. When the default reference-bandwidth is used, a metric of 1 is set on all interface speeds ≥ 100 Gb/s. For example, 100 GE, 100 GE LAG, 400 GE, and 400 GE LAG interfaces will all have a metric of 1.

If the reference bandwidth is configured as 10 Gb (reference-bandwidth 10000000000), a 100 Mb/s interface has a default metric of 100.

When a very large reference bandwidth value is configured, a metric calculation may result in a value higher than the supported protocol cost value. If this occurs, OSPF automatically reverts to the maximum configurable cost metric.

The reference-bandwidth command assigns a default cost to the interface based on the interface speed. To override this default cost on a particular interface, use the metric metric command configured in the config>router>ospf>area>interface ip-int-name context.

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

Default

reference-bandwidth 100000000

Parameters

bandwidth-in-kbps

Specifies the reference bandwidth in kilobits per second, expressed as a decimal integer.

Values

1 to 18446744073709551615

Zetta-bps

Specifies the reference bandwidth in zettabits per second, expressed as a decimal integer.

Values

1 to 18

Exa-bps

Specifies the reference bandwidth in exabits per second, expressed as a decimal integer.

Values

1 to 999

Peta-bps

Specifies the reference bandwidth in petabits per second, expressed as a decimal integer.

Values

1 to 999

Tera-bps

Specifies the reference bandwidth in terabits per second, expressed as a decimal integer.

Values

1 to 999

Giga-bps

Specifies the reference bandwidth in gigabits per second, expressed as a decimal integer.

Values

1 to 999

Mega-bps

Specifies the reference bandwidth in megabits per second, expressed as a decimal integer.

Values

1 to 999

Kilo-bps

Specifies the reference bandwidth in kilobits per second, expressed as a decimal integer.

Values

1 to 999

Platforms

All

reflect-pad

reflect-pad

Syntax

[no] reflect-pad

Context

[Tree] (config>oam-pm>session>mpls>dm reflect-pad)

Full Context

configure oam-pm session mpls dm reflect-pad

Description

This command enables copying the padding in each MPLS-DM query to the response.

When padding is included in the DM frame the option exists to reflect the padding back in the direction of the source or remove the padding. The removal of the pad-tlv is good practice when using unidirectional tunnels such as RSVP.

This command uses the mandatory TLV type 0, instructing the responder to include the pad TLV from the response. The no form of this command uses the optional TVL type 128, instructing the responder to remove the pad TLV from the response.

The no form of this command disables copying the padding in each MPLS-DM query to the response.

Platforms

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

reflector

reflector

Syntax

reflector [udp-port udp-port-number] [create]

no reflector

Context

[Tree] (config>service>vprn>twamp-light reflector)

[Tree] (config>router>twamp-light reflector)

Full Context

configure service vprn twamp-light reflector

configure router twamp-light reflector

Description

This command configures a TWAMP Light session reflector parameters and to enable TWAMP Light functionality with the no shutdown command. The udp-port keyword and value must be specified with the create keyword. An error message is generated if the specific UDP port is unavailable.

Parameters

udp-port-number

Specifies the UDP port number. A strictly enforced restricted range has been introduced. The TWAMP Light session reflector must be brought in line with this new restriction prior upgrading or rebooting from any previous release if there is an active TWAMP Light session reflector configured. Failure to do so prevents an ISSU operation from proceeding and fails to activate any reflector outside of the enforced range.

Note that in the Two-Way Active Measurement Protocol Light (TWAMP Light) section for a complete description. This parameter is required and specifies the destination udp-port that the session reflector uses to listen for TWAMP Light packets. The session controller launching the TWAMP Light packets must be configured with the same destination UDP port as part of the TWAMP Light test. The IES service uses the destination UDP port that is configured under the router context. Only one UDP port can be configured per unique context.

Values

862, 64364 to 64373

Platforms

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

reflector

Syntax

[no] reflector reflector-name

Context

[Tree] (config>bfd>seamless-bfd reflector)

Full Context

configure bfd seamless-bfd reflector

Description

This command specifies the seamless BFD reflector.

The no form of this command removes the context.

Parameters

reflector-name

Specifies the reflector name, up to 32 characters.

Platforms

All

refresh-reduction

refresh-reduction

Syntax

[no] refresh-reduction

Context

[Tree] (config>router>rsvp>interface refresh-reduction)

Full Context

configure router rsvp interface refresh-reduction

Description

This command enables the use of the RSVP overhead refresh reduction capabilities on this RSVP interface.

When this option is enabled, a node will enable support for three capabilities. It will accept bundles RSVP messages from its peer over this interface, it will attempt to perform reliable RSVP message delivery to its peer, and will use summary refresh messages to refresh path and resv states. The reliable message delivery must be explicitly enabled by the user after refresh reduction is enabled. The other two capabilities are enabled immediately.

A bundle message is intended to reduce overall message handling load. A bundle message consists of a bundle header followed by one or more bundle sub-messages. A sub-message can be any regular RSVP message except another bundle message. A node will only process received bundled RSVP messages but will not generate them.

When reliable message delivery is supported by both the node and its peer over the RSVP interface, an RSVP message is sent with a message_id object. A message_id object can be added to any RSVP message when sent individually or as a sub-message of a bundled message.

if the sender sets the ack_desired flag in the message_id object, the receiver acknowledges the receipt of the RSVP message by piggy-backing a message_ack object to the next RSVP message it sends to its peer. Alternatively, an ACK message can also be used to send the message_ack object. In both cases, one or many message_ack objects could be included in the same message.

The router supports the sending of separate ACK messages only but is capable of processing received message_ack objects piggy-backed to hop-by-hop RSVP messages, such as path and resv.

The router sets the ack_desired flag only in non-refresh RSVP messages and in refresh messages which contain new state information.

A retransmission mechanism based on an exponential backoff timer is supported in order to handle unacknowledged message_id objects. The RSVP message with the same message_id is retransmitted every 2 * rapid-retransmit-time interval of time. The rapid-retransmit-time is referred to as the rapid retransmission interval as it must be smaller than the regular refresh interval configured in the config>router>rsvp>refresh-time context. There is also a maximum number of retransmissions of an unacknowledged RSVP message rapid-retry-limit. The node will stop retransmission of unacknowledged RSVP messages whenever the updated backoff interval exceeds the value of the regular refresh interval or the number of retransmissions reaches the value of the rapid-retry-limit parameter, whichever comes first. These two parameters are configurable globally on a system in the config>router>rsvp context.

Refresh summary consists of sending a summary refresh message containing a message_id list object. The fields of this object are populated each with the value of the message_identifier field in the message_id object of a previously sent individual path or resv message. The summary refresh message is sent every refresh regular interval as configured by the user using the refresh-time command in the config>router>rsvp context. The receiver checks each message_id object against the saved path and resv states. If a match is found, the state is updated as if a regular path or resv refresh message was received from the peer. If a specific message_identifier field does not match, then the node sends a message_id_nack object to the originator of the message.

The above capabilities are referred to collectively as "refresh overhead reduction extensions”. When the refresh-reduction is enabled on an RSVP interface, the node indicates this to its peer by setting a "refresh-reduction-capable” bit in the flags field of the common RSVP header. If both peers of an RSVP interface set this bit, all the above three capabilities can be used. Furthermore, the node monitors the settings of this bit in received RSVP messages from the peer on the interface. As soon as this bit is cleared, the router stops sending summary refresh messages. If a peer did not set the "refresh-reduction-capable” bit, a node does not attempt to send summary refresh messages.

However, if the peer did not set the "refresh-reduction-capable” bit, a node, with refresh reduction enabled and reliable message delivery enabled, will still attempt to perform reliable message delivery with this peer. If the peer does not support the message_id object, it returns an error message "unknown object class”. In this case, the node retransmits the RSVP message without the message_id object and reverts to using this method for future messages destined to this peer. The RSVP Overhead Refresh Reduction is supported with both RSVP P2P LSP path and the S2L path of an RSVP P2MP LSP instance over the same RSVP instance.

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

Default

no refresh-reduction

Platforms

All

refresh-reduction-over-bypass

refresh-reduction-over-bypass

Syntax

refresh-reduction-over-bypass [enable | disable]

Context

[Tree] (config>router>rsvp refresh-reduction-over-bypass)

Full Context

configure router rsvp refresh-reduction-over-bypass

Description

This command enables the refresh reduction capabilities over all bypass tunnels originating on this PLR node or terminating on this Merge Point (MP) node.

By default, this is disabled. Since a bypass tunnel may merge with the primary LSP path in a node downstream of the next-hop, there is no direct interface between the PLR and the MP node and it is possible the latter will not accept summary refresh messages received over the bypass.

When disabled, the node as a PLR or MP will not set the "Refresh-Reduction-Capable” bit on RSVP messages pertaining to LSP paths tunneled over the bypass. It will also not send Message-ID in RSVP messages. This effectively disables summary refresh.

Default

refresh-reduction-over-bypass disable

Platforms

All

refresh-time

refresh-time

Syntax

refresh-time seconds

no refresh-time

Context

[Tree] (config>router>rsvp refresh-time)

Full Context

configure router rsvp refresh-time

Description

The refresh-time controls the interval (in s), between the successive Path and Resv refresh messages. RSVP declares the session down after it misses keep-multiplier number consecutive refresh messages.

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

Default

refresh-time 30

Parameters

seconds

The refresh time in s.

Values

1 to 65535

Platforms

All

refresh-time

Syntax

refresh-time seconds hold-time seconds

no refresh-time

Context

[Tree] (config>router>origin-validation>rpki-session refresh-time)

Full Context

configure router origin-validation rpki-session refresh-time

Description

This command is used to configure the refresh-time and hold-time intervals that are used for liveness detection of the RPKI-Router session. The refresh-time defaults to 300 seconds and is reset whenever a Reset Query PDU or Serial Query PDU is sent to the cache server. When the timer expires, a new Serial Query PDU is sent with the last known serial number.

The hold-time specifies the length of time in seconds that the session is to be considered UP without any indication that the cache server is alive and reachable. The timer defaults to 600 seconds and must be at least 2x the refresh-time (otherwise the CLI command is not accepted). Reception of any PDU from the cache server resets the hold timer. When the hold-time expires, the session is considered to be DOWN and the stale timer is started.

Default

no refresh-time

Parameters

seconds

Specifies a time in seconds.

Values

30 to 32767

seconds

Specifies a time in seconds.

Values

60 to 65535

Platforms

All

refresh-timer

refresh-timer

Syntax

refresh-timer value

no refresh-timer

Context

[Tree] (config>service>cpipe>spoke-sdp>control-channel-status refresh-timer)

[Tree] (config>service>vpls>spoke-sdp>control-channel-status refresh-timer)

[Tree] (config>service>epipe>spoke-sdp>control-channel-status refresh-timer)

Full Context

configure service cpipe spoke-sdp control-channel-status refresh-timer

configure service vpls spoke-sdp control-channel-status refresh-timer

configure service epipe spoke-sdp control-channel-status refresh-timer

Description

This command configures the refresh timer for control channel status signaling packets. By default, no refresh packets are sent.

Default

no refresh-timer

Parameters

value

Specifies the refresh timer value, in seconds.

Values

10 to 65535

Default

0 (off)

Platforms

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

  • configure service cpipe spoke-sdp control-channel-status refresh-timer

All

  • configure service vpls spoke-sdp control-channel-status refresh-timer
  • configure service epipe spoke-sdp control-channel-status refresh-timer

refresh-timer

Syntax

refresh-timer value

no refresh-timer

Context

[Tree] (config>service>ies>if>spoke-sdp>control-channel-status refresh-timer)

Full Context

configure service ies interface spoke-sdp control-channel-status refresh-timer

Description

This command configures the refresh timer for control channel status signaling packets. By default, no refresh packets are sent.

Default

no refresh-timer

Parameters

value

Specifies the refresh timer value.

Values

10 to 65535 seconds

Default

0 (off)

Platforms

All

refresh-timer

Syntax

refresh-timer value

no refresh-timer

Context

[Tree] (config>service>vprn>if>spoke-sdp>control-channel-status refresh-timer)

[Tree] (config>service>vprn>red-if>spoke-sdp>control-channel-status refresh-timer)

Full Context

configure service vprn interface spoke-sdp control-channel-status refresh-timer

configure service vprn redundant-interface spoke-sdp control-channel-status refresh-timer

Description

This command configures the refresh timer for control channel status signaling packets. By default, no refresh packets are sent.

Default

no refresh-timer

Parameters

value

Specifies the refresh timer value.

Values

10 to 65535 seconds

Default

0 (off)

Platforms

All

  • configure service vprn interface spoke-sdp control-channel-status refresh-timer

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

  • configure service vprn redundant-interface spoke-sdp control-channel-status refresh-timer

refresh-timer

Syntax

refresh-timer seconds

no refresh-timer

Context

[Tree] (config>mirror>mirror-dest>spoke-sdp>control-channel-status refresh-timer)

[Tree] (config>mirror>mirror-dest>remote-src>spoke-sdp>control-channel-status refresh-timer)

Full Context

configure mirror mirror-dest spoke-sdp control-channel-status refresh-timer

configure mirror mirror-dest remote-source spoke-sdp control-channel-status refresh-timer

Description

This command configures the refresh timer for control channel status signaling packets. By default, no refresh packets are sent.

Parameters

seconds

Specifies the refresh timer value.

Values

10 to 65535

Platforms

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

register

register

Syntax

register [group grp-ip-address] [source ip-address] [detail]

no register

Context

[Tree] (debug>router>pim register)

Full Context

debug router pim register

Description

This command enables debugging for PIM register mechanism.

The no form of this command disables debugging for PIM register mechanism.

Parameters

grp-ip-address

Debugs information associated with the specified PIM register.

Values

multicast group address (ipv4, ipv6)

ip-address

Debugs information associated with the specified PIM register.

Values

source address (ipv4, ipv6)

detail

Debugs detailed register information.

Platforms

All

register-message

register-message

Syntax

[no] register-message {ip-address | ipv6-address}

Context

[Tree] (config>router>pim>src-address register-message)

[Tree] (config>service>vprn>pim>src-address register-message)

Full Context

configure router pim source-address register-message

configure service vprn pim source-address register-message

Description

This command configures the source IP address for PIM register messages. The IP address can be set to any unicast address, regardless of whether it resides on the node. Ensure that the specified IP address is configured on the router as a loopback or interface IP address.

The no form of this command removes the IP address. By default, when no IP address is specified for the PIM instance, the source IP address for register messages is selected by choosing the smallest IP address from available interfaces on the node.

Parameters

ip-address | ipv6-address

Specifies the source IPv4 or IPv6 address, up to 64 characters.

Platforms

All

registrant-sm

registrant-sm

Syntax

[no] registrant-sm

Context

[Tree] (debug>service>id>mrp registrant-sm)

Full Context

debug service id mrp registrant-sm

Description

This command enables debugging of the registrant state machine.

The no form of this command disables debugging of the registrant state machine.

Platforms

All

reinit-delay

reinit-delay

Syntax

reinit-delay time

no reinit-delay

Context

[Tree] (config>system>lldp reinit-delay)

Full Context

configure system lldp reinit-delay

Description

This command configures the time before re-initializing LLDP on a port.

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

Default

no reinit-delay

Parameters

time

Specifies the time, in seconds, before re-initializing LLDP on a port.

Values

1 to 10

Default

2

Platforms

All

reject-disabled-ncp

reject-disabled-ncp

Syntax

[no] reject-disabled-ncp

Context

[Tree] (config>service>vprn>l2tp>group>tunnel>ppp reject-disabled-ncp)

[Tree] (config>service>vprn>l2tp>group>ppp reject-disabled-ncp)

[Tree] (config>router>l2tp>group>ppp reject-disabled-ncp)

[Tree] (config>router>l2tp>group>tunnel>ppp reject-disabled-ncp)

Full Context

configure service vprn l2tp group tunnel ppp reject-disabled-ncp

configure service vprn l2tp group ppp reject-disabled-ncp

configure router l2tp group ppp reject-disabled-ncp

configure router l2tp group tunnel ppp reject-disabled-ncp

Description

This command forces an LCP Protocol Reject when receiving an IPv6CP Configure Request message whenIPv6 is not configured.

By default, an IPv6CP Configure Request message is silently ignored when IPv6 is not configured.

Platforms

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

reject-disabled-ncp

Syntax

[no] reject-disabled-ncp

Context

[Tree] (config>subscr-mgmt>ppp-policy reject-disabled-ncp)

Full Context

configure subscriber-mgmt ppp-policy reject-disabled-ncp

Description

This command forces an LCP Protocol Reject when receiving an IPv6CP Configure Request message while IPv6 is not configured or when receiving an IPv4CP Configure Request message and no local IPv4 address is assigned.

By default, an IPv4CP/IPv6CP Configure Request message is silently ignored when IPv4/IPv6 is not configured.

Platforms

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

relative

relative

Syntax

relative percent

no relative

Context

[Tree] (config>test-oam>link-meas>template>asw>thr relative)

[Tree] (config>test-oam>link-meas>template>sw>thr relative)

Full Context

configure test-oam link-measurement measurement-template aggregate-sample-window threshold relative

configure test-oam link-measurement measurement-template sample-window threshold relative

Description

This command configures the percentage value of change, positive or negative, compared to the previously reported measurement. If this percentage value is reached in either direction, the new value is conveyed to the routing engine for further handling and stored as the delay measurement last reported. If the percentage value is not configured, this threshold is disabled.

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

Default

relative 0

Parameters

percent

Specifies the percentage of change.

A value of 0 (zero) indicates no relative thresholding is performed when considering report to the routing engine.

Values

0 to 100

Platforms

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

relay

relay

Syntax

[no] relay

Context

[Tree] (config>service>vprn>sub-if>ipv6>dhcp6 relay)

[Tree] (config>service>vprn>sub-if>grp-if>ipv6>dhcp6 relay)

[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6 relay)

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

Full Context

configure service vprn subscriber-interface ipv6 dhcp6 relay

configure service vprn subscriber-interface group-interface ipv6 dhcp6 relay

configure service ies subscriber-interface group-interface ipv6 dhcp6 relay

configure service ies subscriber-interface ipv6 dhcp6 relay

Description

Commands in this context configure DHCPv6 relay parameters for this interface.

Platforms

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

relay-plain-bootp

relay-plain-bootp

Syntax

[no] relay-plain-bootp

Context

[Tree] (config>service>vprn>if>dhcp relay-plain-bootp)

[Tree] (config>service>ies>if>dhcp relay-plain-bootp)

Full Context

configure service vprn interface dhcp relay-plain-bootp

configure service ies interface dhcp relay-plain-bootp

Description

This command enables the relaying of plain BOOTP packets.

The no form of this command disables the relaying of plain BOOTP packets.

Platforms

All

relay-plain-bootp

Syntax

[no] relay-plain-bootp

Context

[Tree] (config>router>if>dhcp relay-plain-bootp)

Full Context

configure router interface dhcp relay-plain-bootp

Description

This command enables the relaying of plain BOOTP packets.

The no form of this command disables the relaying of plain BOOTP packets.

Default

no relay-plain-bootp

Platforms

All

relay-proxy

relay-proxy

Syntax

relay-proxy [release-update-src-ip] [siaddr-override ip-address]

no relay-proxy

Context

[Tree] (config>service>vprn>sub-if>dhcp relay-proxy)

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

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

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

[Tree] (config>service>ies>sub-if>dhcp relay-proxy)

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

Full Context

configure service vprn subscriber-interface dhcp relay-proxy

configure service vprn subscriber-interface group-interface dhcp relay-proxy

configure service vprn interface dhcp relay-proxy

configure service ies subscriber-interface group-interface dhcp relay-proxy

configure service ies subscriber-interface dhcp relay-proxy

configure service ies interface dhcp relay-proxy

Description

This command enables the DHCPv4 relay proxy function on the interface. The command has no effect when no dhcp servers are configured (DHCPv4 relay not configured). By default, unicast DHCPv4 release messages are forwarded transparently.

A relay proxy enhances the relay such that it also relays unicast client DHCPv4 REQUEST messages (lease renewals).

  • In the upstream direction, update the source IP address and add the gateway IP address (gi-address) field before sending the message to the intended DHCP server (the message is not broadcasted to all configured DHCP servers.

  • In the downstream direction, remove the gi-address and update the destination IP address to the address of the yiaddr (your IP address) field.

The optional release-update-src-ip parameter updates the source IP address of a DHCP RELEASE message with the address used for relayed DHCPv4 messages.

The optional siaddr-override ip-address parameter enables DHCP server IP address hiding towards the client. This parameter requires that lease-populate is enabled on the interface. The DHCP server ip address is required for the address hiding function and is stored in the lease state record. The client interacts with the relay proxy as if it is the DHCP server. In all DHCP messages to the client, the value of following header fields and DHCP options containing the DHCP server IP address is replaced with the configured <ip-address>:

  • the "source IP address” field in the IP DHCPv4 packet header

  • the "siaddr” field in the DHCPv4 header if not equal to zero in the message received from the server

  • the Server Identification option (DHCPv4 option 54) if present in the original server message

  • the source IP address field in the IP packet header

DHCP OFFER selection during initial binding is done in the relay-proxy. Only the first DHCP OFFER message is forwarded to the client. Subsequent DHCP OFFER messages from different servers are silently dropped.

Parameters

release-update-src-ip

Updates the source IP address of a DHCP RELEASE message with the address used for relayed DHCPv4 messages.

ip-address

Enables DHCPv4 server address hiding towards the DHCPv4 client and activates DHCPv4 OFFER selection in case multiple DHCP servers are configured. The ip-address can be any local address in the same routing instance. If DHCP relay lease-split is enabled, siaddr-override ip-address has priority over the emulated-server ip-address configured in the proxy-server and is used as the source IP address.

Platforms

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

  • configure service ies subscriber-interface group-interface dhcp relay-proxy
  • configure service vprn subscriber-interface dhcp relay-proxy
  • configure service ies subscriber-interface dhcp relay-proxy
  • configure service vprn subscriber-interface group-interface dhcp relay-proxy

All

  • configure service vprn interface dhcp relay-proxy
  • configure service ies interface dhcp relay-proxy

relay-unsolicited-cfg-attribute

relay-unsolicited-cfg-attribute

Syntax

relay-unsolicited-cfg-attribute

Context

[Tree] (config>ipsec>ike-policy relay-unsolicited-cfg-attribute)

Full Context

configure ipsec ike-policy relay-unsolicited-cfg-attribute

Description

This command enters relay unsolicited configuration attributes context. With this configuration, the configured attributes returned from source (such as a RADIUS server) will be returned to IKEv2 remote-access tunnel client regardless if the client has requested it in the CFG_REQUEST payload.

Platforms

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

release-reason

release-reason

Syntax

[no] release-reason

Context

[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes release-reason)

Full Context

configure aaa isa-radius-policy acct-include-attributes release-reason

Description

This command enables the inclusion of the release reason attributes.

The no form of the command excludes release reason attributes.

Default

no release-reason

Platforms

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

release-timeout

release-timeout

Syntax

release-timeout seconds

no release-timeout

Context

[Tree] (config>subscr-mgmt>pfcp-association release-timeout)

Full Context

configure subscriber-mgmt pfcp-association release-timeout

Description

This command configures the time to wait to clean up the PFCP association after administratively disabling it and requesting a shutdown to the BNG CPF. If the BNG CPF does not gracefully remove the PFCP association before the timer expires, the full association and all related sessions are forcefully removed.

The no form of this command reverts to the default.

Default

release-timeout 3600

Parameters

seconds

Specifies the wait time, in seconds, for cleanup of the PFCP association.

Values

30 to 3600

Note:

The PFCP protocol encoding does not allow the full range of configured values. The system automatically rounds up the configured value to the nearest value allowed by the protocol. For more information about the protocol encoding, see 3GPP TS 29.244 8.2.78.1.

Platforms

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

reliable-delivery

reliable-delivery

Syntax

[no] reliable-delivery

Context

[Tree] (config>router>rsvp>if>refresh-reduction reliable-delivery)

Full Context

configure router rsvp interface refresh-reduction reliable-delivery

Description

This command enables reliable delivery of RSVP messages over the RSVP interface. When refresh-reduction is enabled on an interface and reliable-delivery is disabled, the router will send a message_id and not set ACK desired in the RSVP messages over the interface. The router does not expect an ACK and but will accept it if received. The node will also accept message ID and reply with an ACK when requested. In this case, if the neighbor set the "refresh-reduction-capable” bit in the flags field of the common RSVP header, the node will enter summary refresh for a specific message_id it sent regardless if it received an ACK or not to this message from the neighbor.

Finally, when 'reliable-delivery’ option is enabled on any interface, RSVP message pacing is disabled on all RSVP interfaces of the system, for example, the user cannot enable the msg-pacing option in the config>router>rsvp context, and error message is returned in CLI. Conversely, when the msg-pacing option is enabled, the user cannot enable the reliable delivery option on any interface on this system. An error message is also generated in CLI after such an attempt.

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

Default

no reliable-delivery

Platforms

All

reload

reload

Syntax

reload type {cert | key | cert-key-pair} filename protocol protocol [key-file filename]

Context

[Tree] (admin>certificate reload)

Full Context

admin certificate reload

Description

This command reloads imported certificate or key file or both at the same time. This command is typically used to update certificate or key file without shutting down ipsec-tunnel/ipsec-gw/cert-profile/ca-profile. Note that type cert and type key is deprecated in a future release. Use type cert-key-pair instead. Instead of type cert use type key instead.

  • If the new file exists and valid, then for each tunnel using it:

    • If the key matches the certificate, then the new file is downloaded to the MS-ISA to be used the next time. Tunnels currently up are not affected.

    • If the key does not match the certificate:

      • If cert and key configuration is used instead of cert-profile then the tunnel is brought down.

      • If cert-profile is used, then cert-profile is brought down. The next authentication fails while the established tunnels are not affected.

If the new file does not exists or somehow invalid (bad format, does not contain right extension, and so on), then this command will abort.

In the case of type cert-key-pair, if the new file does not exist or is invalid or cert and key do not match, then this command aborts with an error message.

Parameters

type

Specifies what item will be reloaded.

cert

Specifies that a certificate cache will be reloaded.

key

Specifies that a key cache will be reloaded.

cert-key-pair

Specifies that a paired certificate and key cache will be reloaded.

filename

Up to 95 characters.

protocol

Specifies which protocol the certificate will be reloaded for.

Values

ipsec, tls

Platforms

All

rem-router-id

rem-router-id

Syntax

rem-router-id ip-addr

no rem-router-id

Context

[Tree] (config>service>vprn>l2tp>group>l2tpv3 rem-router-id)

Full Context

configure service vprn l2tp group l2tpv3 rem-router-id

Description

This command configures the IP address that should be used within the Remote Router-ID AVP.

The no form of this command removes the configured IP address.

Default

no rem-router-id

Parameters

ip-addr

Specifies an IP address to be used within the Remote Router-ID AVP.

Platforms

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

remark

remark

Syntax

remark

Context

[Tree] (config>app-assure>group>policy>aqp>entry>action remark)

Full Context

configure application-assurance group policy app-qos-policy entry action remark

Description

This command configures remark action on flows matching this AQP entry.

Platforms

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

remark

Syntax

remark dscp dscp-name

Context

[Tree] (config>filter>ip-filter>entry>action>extended-action remark)

[Tree] (config>filter>ipv6-filter>entry>action>extended-action remark)

[Tree] (config>filter>ipv6-filter>entry>action remark)

[Tree] (config>filter>ip-filter>entry>action remark)

Full Context

configure filter ip-filter entry action extended-action remark

configure filter ipv6-filter entry action extended-action remark

configure filter ipv6-filter entry action remark

configure filter ip-filter entry action remark

Description

This command enables and configures the remarking of the DiffServ Code Points of packets matching the criteria of the IPv4/IPv6 filter policy entry, in conjunction with a PBR action. Packets are remarked regardless of QoS-based in-profile or out-of-profile classification. QoS-based DSCP remarking is overridden. If the status of the PBR target is tracked and it is down, the extended action will not be executed; otherwise, the extended action will be performed.

Parameters

dscp-name

Specifies the DSCP value to write.

Values

be, ef, cp1, cp2, cp3, cp4, cp5, cp6, cp7, cp9, cs1, cs2, cs3, cs4, cs5, nc1, nc2, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cp11, cp13, cp15, cp17, cp19, cp21, cp23, cp25, cp27, cp29, cp31, cp33, cp35, cp37, cp39, cp41, cp42, cp43, cp44, cp45, cp47, cp49, cp50, cp51, cp52, cp53, cp54, cp55, cp57, cp58, cp59, cp60, cp61, cp62, cp63

Platforms

All

remarking

remarking

Syntax

remarking [force]

no remarking

Context

[Tree] (config>qos>network>egress remarking)

Full Context

configure qos network egress remarking

Description

This command remarks both customer traffic and egress network IP interface traffic; VPRN customer traffic is not remarked. The remarking is based on the forwarding class to DSCP and LSP EXP bit mapping defined under the egress node of the network QoS policy.

Normally, packets that ingress on network ports have either the DSCP or, for MPLS packets, LSP EXP bit set by an upstream router. The packets are placed in the appropriate forwarding class based on the DSCP-to-forwarding class mapping or the LSP EXP-to-forwarding class mapping. The DSCP or LSP EXP bits of such packets are not altered as the packets egress this router, unless remarking is enabled.

Remarking can be required if this router is connected to a different DiffServ domain where the DSCP-to-forwarding class mapping is different.

Normally, no remarking is necessary when all router devices are in the same DiffServ domain.

The network QoS policy supports an egress flag that forces remarking of packets that were received on trusted IES and network IP interfaces. This provides the capability of remarking without regard to the ingress state of the IP interface on which a packet was received. The effect of the egress network remark trusted state on each type of ingress IP interface and trust state is listed in Ingress IP Interface Type and Trust State Effect on Egress Network Remarking.

The remark trusted state has no effect on packets received on an ingress VPRN IP interface.

Table 1. Ingress IP Interface Type and Trust State Effect on Egress Network Remarking

Ingress IP Interface Type and Trust State

Egress Network IP Interface Trust Remark Disabled (Default)

Egress Network IP Interface Trust Remark Enabled

IES Non-Trusted (Default)

Egress Remarked

Egress Remarked

IES Trusted

Egress Not Remarked

Egress Remarked

VPRN Non-Trusted

Egress Remarked

Egress Remarked

VPRN Trusted (Default)

Egress Not Remarked

Egress Not Remarked

Network Non-Trusted

Egress Remarked

Egress Remarked

Network Trusted (Default)

Egress Not Remarked

Egress Remarked

The no form of this command resets the configuration to the default behavior.

Default

no remarking — Remarking disabled in the Network QoS policy.

Parameters

force

Specifies that all IP routed traffic egressing the associated network interface will have its EXP, DSCP, P-bit, and DE bit setting remarked as defined in the associated QoS policy. Only bit fields configured in the QoS policy will be remarked; all others will be left untouched or set based on the default if the fields were not present at ingress.

Platforms

All

remote

remote

Syntax

remote

Context

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

Full Context

configure ipsec ts-list remote

Description

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

Platforms

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

remote-address

remote-address

Syntax

remote-address ip-address

no remote-address

Context

[Tree] (config>subscr-mgmt>wlan-gw>tunnel-query remote-address)

Full Context

configure subscriber-mgmt wlan-gw tunnel-query remote-address

Description

This command enables matching only on the tunnel that uses the specified source IP address.

The no form of this command disables matching on a tunnel’s source IP address.

Default

no remote-address

Parameters

ip-address

Specifies the IPv4 or IPv6 remote 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 to FFFF]H

d: [0 to 255]D

Platforms

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

remote-age

remote-age

Syntax

remote-age aging-timer

no remote-age [aging-timer]

Context

[Tree] (config>service>vpls remote-age)

[Tree] (config>service>template>vpls-template remote-age)

Full Context

configure service vpls remote-age

configure service template vpls-template remote-age

Description

This command specifies the aging time for remotely learned MAC addresses in the forwarding database (FDB) for the Virtual Private LAN Service (VPLS) instance.

In a VPLS service, MAC addresses are associated with a Service Access Point (SAP) or with a Service Distribution Point (SDP). MACs associated with a SAP are classified as local MACs, and MACs associated with an SDP are remote MACs.

Like in a Layer 2 switch, learned MACs can be aged out if no packets are sourced from the MAC address for a period of time (the aging time). In each VPLS service instance, there are independent aging timers for local learned MAC and remote learned MAC entries in the FDB. The remote-age timer specifies the aging time for remote learned MAC addresses. To reduce the amount of signaling required between switches configure this timer larger than the local-age timer.

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

Default

remote-age 900

Parameters

seconds

Specifies the aging time for remote MACs expressed in seconds

Values

60 to 86400

Platforms

All

remote-attachment-circuit

remote-attachment-circuit

Syntax

remote-attachment-circuit ac-name [endpoint endpoint-name] [create]

no remote-attachment-circuit ac-name

Context

[Tree] (config>service>epipe>bgp-evpn remote-attachment-circuit)

Full Context

configure service epipe bgp-evpn remote-attachment-circuit

Description

This command configures the remote attachment circuit.

The no form of this command disables the context.

Default

no remote-attachment-circuit

Parameters

ac-name

Specifies the name of the remote attachment circuit, up to 32 characters.

endpoint-name

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

create

Keyword used to create the remote AC.

Platforms

All

remote-ecid

remote-ecid

Syntax

remote-ecid emulated circuit identifier

no remote-ecid

Context

[Tree] (config>service>epipe>sap>cem remote-ecid)

Full Context

configure service epipe sap cem remote-ecid

Description

This command defines the Emulated Circuit Identifiers (ECID) to be used for the remote (destination) end of the circuit emulation service.

Parameters

emulated circuit identifier

Specifies the value to be used as the remote (destination) ECID for the circuit emulation service. Upon CES packet reception, the ECID in the packet will be compared to the configured local-ecid value. These must match for the packet payload to be used for the TDM circuit. The remote-ecid value is inserted into the MEF-8 CES packet to be transmitted.

Values

0 to 1048575

Platforms

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

remote-gateway-address

remote-gateway-address

Syntax

remote-gateway-address [ip-address | ipv6-address]

no remote-gateway-address

Context

[Tree] (config>router>if>ipsec>ipsec-tunnel remote-gateway-address)

Full Context

configure router interface ipsec ipsec-tunnel remote-gateway-address

Description

This command configures the remote IPsec tunnel endpoint address.

Parameters

ip-address

Specifies a remote unicast IPv4 address, up to 64 characters.

ipv6-address

Specifies a remote unicast global unicast IPv6 address, up to 64 characters.

Platforms

VSR

remote-id

remote-id

Syntax

remote-id hex hex-string

remote-id string ascii-string

no remote-id

Context

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>host-ident remote-id)

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>host-ident remote-id)

Full Context

configure subscriber-mgmt local-user-db ipoe host host-identification remote-id

configure subscriber-mgmt local-user-db ppp host host-identification remote-id

Description

This command specifies the remote ID to match for a host lookup. When the LUDB is accessed using a DHCPv4 server, the SAP-ID is matched against DHCP option 82.

Note:

This command is used only when remote-id is configured as one of the match-list parameters.

The no form of this command removes the remote ID from the configuration.

Parameters

hex-string

Specifies the hexadecimal format for the remote ID.

Values

0x0 to 0xFFFFFFFF (maximum 254 hex nibbles)

ascii-string

Specifies the string format for the remote ID, up to 255 characters.

Platforms

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

remote-id

Syntax

remote-id mac

remote-id string ASCII string

no remote-id

Context

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>ali remote-id)

Full Context

configure subscriber-mgmt local-user-db ppp host access-loop-information remote-id

Description

This command specifies a remote-id for PPPoE hosts. A remote-id received in PPPoE tags has precedence over the LUDB specified remote ID.

The no form of this command reverts to the default.

Parameters

mac

Specifies MAC address of the PPPoE session as the remote ID.

ASCII string

Specifies the circuit ID as a string, up to 63 characters.

Platforms

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

remote-id

Syntax

remote-id

remote-id mac

remote-id string [string]

no remote-id

Context

[Tree] (config>service>vprn>if>ipv6>dhcp6>option remote-id)

[Tree] (config>service>vprn>sub-if>grp-if>ipv6>dhcp6>option remote-id)

[Tree] (config>service>ies>if>ipv6>dhcp6>option remote-id)

Full Context

configure service vprn interface ipv6 dhcp6-relay option remote-id

configure service vprn subscriber-interface group-interface ipv6 dhcp6 option remote-id

configure service ies interface ipv6 dhcp6-relay option remote-id

Description

This command enables the sending of remote ID option in the DHCPv6 relay packet.

The client DHCP Unique Identifier (DUID) is used as the remote ID.

The no form of this command disables the sending of remote ID option in the DHCPv6 relay packet.

Platforms

All

  • configure service vprn interface ipv6 dhcp6-relay option remote-id
  • configure service ies interface ipv6 dhcp6-relay option remote-id

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

  • configure service vprn subscriber-interface group-interface ipv6 dhcp6 option remote-id

remote-id

Syntax

remote-id

remote-id hex [hex-string]

remote-id {mac | string string}

no remote-id

Context

[Tree] (config>service>vprn>sub-if>grp-if>dhcp>option remote-id)

[Tree] (config>service>vprn>if>dhcp>option remote-id)

[Tree] (config>service>vpls>sap>dhcp>option remote-id)

[Tree] (config>service>ies>sub-if>grp-if>dhcp>option remote-id)

[Tree] (config>subscr-mgmt>msap-policy>vpls-only>dhcp>option remote-id)

[Tree] (config>service>ies>if>dhcp>option remote-id)

Full Context

configure service vprn subscriber-interface group-interface dhcp option remote-id

configure service vprn interface dhcp option remote-id

configure service vpls sap dhcp option remote-id

configure service ies subscriber-interface group-interface dhcp option remote-id

configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp option remote-id

configure service ies interface dhcp option remote-id

Description

This command specifies what information goes into the remote-id sub-option in the DHCP relay packet.

If disabled, the remote-id sub-option of the DHCP packet is left empty. When the command is configured without any parameters, it equals to the remote-id mac option.

The no form of this command reverts to the default.

Parameters

string

Specifies the remote-id, up to 32 characters.

hex-string

Specifies the hex value of this option.

Values

0x0 to 0xFFFFFFFF...(up to 64 hex nibbles)

mac

Specifies that the MAC address of the remote end is encoded in the sub-option.

Platforms

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

  • configure service vprn subscriber-interface group-interface dhcp option remote-id
  • configure service ies subscriber-interface group-interface dhcp option remote-id
  • configure subscriber-mgmt msap-policy vpls-only-sap-parameters dhcp option remote-id

All

  • configure service vprn interface dhcp option remote-id
  • configure service vpls sap dhcp option remote-id
  • configure service ies interface dhcp option remote-id

remote-id

Syntax

[no] remote-id

Context

[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute remote-id)

[Tree] (config>subscr-mgmt>auth-policy>include-radius-attribute remote-id)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute remote-id

configure subscriber-mgmt authentication-policy include-radius-attribute remote-id

Description

This command enables the generation of the Broad Band Forum Agent-Remote-Id VSA in RADIUS request messages.

The no form of this command disables the generation of the Broad Band Forum Agent-Remote-Id VSA.

Platforms

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

remote-id

Syntax

[no] remote-id

Context

[Tree] (config>subscr-mgmt>diam-appl-plcy>nasreq>include-avp remote-id)

Full Context

configure subscriber-mgmt diameter-application-policy nasreq include-avp remote-id

Description

This command enables the generation of the Broad Band Forum Agent-Remote-Id Vendor Specific AVP in Diameter NASREQ AAR messages.

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

remote-id

Syntax

[no] remote-id remote-id

Context

[Tree] (debug>service>id>ppp remote-id)

Full Context

debug service id ppp remote-id

Description

This command enable PPP debug for the specified remote-id.

Multiple remote-id filters can be specified in the same debug command.

Parameters

remote-id

Specifies the remote-id in PADI.

Platforms

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

remote-id

Syntax

[no] remote-id

Context

[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes remote-id)

[Tree] (config>aaa>isa-radius-plcy>auth-include-attributes remote-id)

Full Context

configure aaa isa-radius-policy acct-include-attributes remote-id

configure aaa isa-radius-policy auth-include-attributes remote-id

Description

This command enables the sending of remote ID option. The client DHCP Unique Identifier (DUID) is used as the remote ID.

The no form of the command disables the sending of remote ID option relay packet.

Default

no remote-id

Platforms

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

remote-id

Syntax

remote-id [{mac | string string}]

no remote-id

Context

[Tree] (config>router>if>dhcp>option remote-id)

Full Context

configure router interface dhcp option remote-id

Description

When enabled, the router sends the MAC address of the remote end (typically the DHCP client) in the remote-id suboption of the DHCP packet. This command identifies the host at the other end of the circuit. If disabled, the remote-id suboption of the DHCP packet will be left empty.

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

Default

no remote-id

Parameters

mac

This keyword specifies the MAC address of the remote end is encoded in the suboption.

string

Specifies the remote ID.

Platforms

All

remote-id

Syntax

remote-id mac

remote-id string <string>

no remote-id

Context

[Tree] (config>service>vpls>sap>dhcp6>ldra>options remote-id)

Full Context

configure service vpls sap dhcp6 ldra options remote-id

Description

This command configures the information for the remote ID suboption in the DHCP6 LDRA.

The no form of this command reverts to the default.

Default

no remote-id

Parameters

mac

Sets the enterprise number field of the Relay Agent remote ID to 6527 and configures the DHCPv6 client source MAC address as six hexadecimal numbers.

string

Sets the enterprise number field of the Relay-Agent remote ID to 6527 and configures the ASCII-encoded string using up to 32 characters.

Platforms

All

remote-ip

remote-ip

Syntax

remote-ip ip-address

no remote-ip

Context

[Tree] (config>service>ies>if>sap>ip-tunnel remote-ip)

Full Context

configure service ies interface sap ip-tunnel remote-ip

Description

This command configures the primary destination IPv4 or IPv6 address to use for an IP tunnel. This configuration applies to the outer IP header of the encapsulated packets. The source address, remote-ip address and backup-remote-ip address of a tunnel must all belong to the same address family (IPv4 or IPv6). When the remote-ip address contains an IPv6 address it must be a global unicast address.

Default

no remote-ip

Parameters

ip-address

An IPv4 address or an IPv6 address.

Platforms

All

remote-ip

Syntax

remote-ip ip-address

no remote-ip

Context

[Tree] (config>service>vprn>if>sap>ip-tunnel remote-ip)

Full Context

configure service vprn interface sap ip-tunnel remote-ip

Description

This command sets the primary destination IPv4 address of GRE encapsulated packets associated with a particular GRE tunnel. If this address is reachable in the delivery service (there is a route) then this is the destination IPv4 address of GRE encapsulated packets sent by the delivery service.

The no form of this command deletes the destination address from the GRE tunnel configuration.

Parameters

ip-address

Specifies the destination IPv4 address of the GRE tunnel.

Values

1.0.0.0 to 223.255.255.255

Platforms

All

remote-ip

Syntax

remote-ip {ip-prefix/prefix-length | ip-prefix netmask | any}

Context

[Tree] (config>router>ipsec>sec-plcy>entry remote-ip)

[Tree] (config>service>vprn>ipsec>sec-plcy>entry remote-ip)

Full Context

configure router ipsec security-policy entry remote-ip

configure service vprn ipsec security-policy entry remote-ip

Description

This command configures the remote (from the tunnel) IP prefix/mask for the policy parameter entry.

Only one entry is necessary to describe a potential flow. The local-ip and remote-ip commands can be defined only once. The system evaluates:

  • the local IP as the source IP when traffic is examined in the direction of the flows from private to public and as the destination IP when traffic flows from public to private

  • the remote IP as the source IP when traffic flows public to private and as the destination IP when traffic flows from private to public

Parameters

ip-prefix

Specifies the destination address of the aggregate route in dotted decimal notation.

Values

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

prefix-length 1 to 32

netmask

Specifies the subnet mask in dotted decimal notation.

any

keyword to specify that it can be any address.

Platforms

VSR

  • configure router ipsec security-policy entry remote-ip

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

  • configure service vprn ipsec security-policy entry remote-ip

remote-ip-address

remote-ip-address

Syntax

remote-ip-address ip-address

no remote-ip-address

Context

[Tree] (config>lag>bfd>family remote-ip-address)

Full Context

configure lag bfd family remote-ip-address

Description

This command specifies the IPv4 or IPv6 address of the BFD destination.

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

Default

no remote-ip-address

Parameters

ip-address

Specifies the IP 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 to FFFF]H

d: [0 to 255]D

Platforms

All

remote-ip-range-start

remote-ip-range-start

Syntax

remote-ip-range-start ip-address

no remote-ip-range-start

Context

[Tree] (config>isa>nat-group>inter-chassis-redundancy remote-ip-range-start)

Full Context

configure isa nat-group inter-chassis-redundancy remote-ip-range-start

Description

This command configures the first IPv4 address that is assigned to a first member ISA on the remote node. The remaining member ISAs on the remote node are assigned the consecutive IP addresses starting from the first IP address. These IP addresses are used to communicate between the ISAs on redundant nodes for the purpose of flow synchronization. Traffic from the first local IP address (member ISA), is sent to the first IP address from the remote IP range.

The no form of this command removes the ip-address from the configuration.

Default

no remote-ip-range-start

Parameters

ip-address

Specifies the first IPv4 address, in the a.b.c.d format, from the range assigned to the first member ISA on the remote node.

Platforms

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

remote-lfa

remote-lfa

Syntax

remote-lfa [max-pq-cost value]

no remote-lfa

Context

[Tree] (config>router>isis>loopfree-alternates remote-lfa)

Full Context

configure router isis loopfree-alternates remote-lfa

Description

This command enables the use of the Remote LFA algorithm in the LFA SPF calculation for this ISIS instance.

The no form of this command disables the use of the Remote LFA algorithm in the LFA SPF calculation for this ISIS instance.

Default

no remote-lfa

Parameters

value

Specifies the integer used to limit the search of candidate P and Q nodes in the remote LFA by setting the maximum IGP cost from the router performing the remote LFA calculation to the candidate P or Q node.

Values

0 to 4294967295

Default

4261412864

Platforms

All

remote-lfa

Syntax

remote-lfa [max-pq-cost value]

no remote-lfa

Context

[Tree] (config>router>ospf3>loopfree-alternates remote-lfa)

[Tree] (config>router>ospf>loopfree-alternates remote-lfa)

Full Context

configure router ospf3 loopfree-alternates remote-lfa

configure router ospf loopfree-alternates remote-lfa

Description

This command enables the use of the Remote LFA algorithm in the LFA SPF calculation in this OSPF or OSPF3 instance.

The no form of this command disables the use of the Remote LFA algorithm in the LFA SPF calculation in this OSPF or OSPF3 instance.

Default

no remote-lfa

Parameters

max-pq-cost value

Specifies the integer used to limit the search of candidate P and Q nodes in the remote LFA by setting the maximum IGP cost from the router performing the remote LFA calculation to the candidate P or Q node.

Values

0 to 4294967295

Default

4261412864

Platforms

All

remote-loop-respond

remote-loop-respond

Syntax

[no] remote-loop-respond

Context

[Tree] (config>port>tdm>ds1 remote-loop-respond)

Full Context

configure port tdm ds1 remote-loop-respond

Description

When enabled, the channel responds to requests for remote loopbacks.

Default

no remote-loop-respond — The port will not respond.

Platforms

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

remote-mac

remote-mac

Syntax

remote-mac ieee-address

no remote-mac

Context

[Tree] (config>service>epipe>sap>cem remote-mac)

Full Context

configure service epipe sap cem remote-mac

Description

This command defines the destination IEEE MAC address to be used to reach the remote end of the circuit emulation service.

Default

remote-mac 00:00:00:00:00:00

Parameters

ieee-address

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

Platforms

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

remote-management

remote-management

Syntax

remote-management

Context

[Tree] (config>system>management-interface remote-management)

Full Context

configure system management-interface remote-management

Description

Commands in this context configure the SR OS node to use the remote management service. Configuring remote management enables the SR OS node to report itself to a remote manager service running on a remote server, so that it is included in the dynamic list of available nodes. The manager service streamlines the management of multiple SR OS nodes running different SR OS versions using the same client application providing a similar shell to the MD-CLI.

Platforms

All

remote-management

Syntax

remote-management

no remote-management

remote-management manager [manager-name]

no remote-management manager [manager-name]

Context

[Tree] (debug>system>management-interface remote-management)

Full Context

debug system management-interface remote-management

Description

This command configures the management interface to debug the remote-management managers.

The no form of this command removes the configuration.

Parameters

manager manager-name

Specifies the name of the manager, up to 64 characters. If the parameter is not specified, all configured managers are debugged.

Platforms

All

remote-max-checkpoints

remote-max-checkpoints

Syntax

remote-max-checkpoints [number-of-files]

no remote-max-checkpoints

Context

[Tree] (config>system>rollback remote-max-checkpoints)

Full Context

configure system rollback remote-max-checkpoints

Description

This command configures the maximum number of rollback checkpoint files when the rollback-location is remote (for example, ftp).

Default

no remote-max-checkpoints

Parameters

number of files

Specifies the maximum rollback files saved at a remote location.

Values

1 to 200

Platforms

All

remote-mepid

remote-mepid

Syntax

remote-mepid mep-id remote-mac {unicast-da | default}

no remote-mepid mep-id

Context

[Tree] (config>eth-cfm>domain>assoc remote-mepid)

Full Context

configure eth-cfm domain association remote-mepid

Description

This command configures the remote MEP ID. Optionally, the operator may configure a unicast MAC address associated with the remote MEP. This unicast value replaces the default Layer 2 class 1 multicast address that is typically associated with ETH-CC packets.

Note:

This command is not supported with sub second CCM intervals. The unicast-da parameter may only be configured when a single remote MEP exists in the association.

The no form of this command removes the peer information.

Parameters

mep-id

Specifies the peer MEP ID.

Values

1 to 8191

unicast-da

Specifies the unicast MAC destination address.

Values

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

default — Removes the remote MAC unicast address and reverts back to class 1 multicast address.

Platforms

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

remote-mepid

Syntax

remote-mepid mep-id

no remote-mepid

Context

[Tree] (config>oam-pm>session>ethernet remote-mepid)

Full Context

configure oam-pm session ethernet remote-mepid

Description

This command specifies the remote MEP ID as an alternative to the static dest-mac ieee-address. When the remote-mepid option is configured as an alternative to the dest-mac, the domain and association information of the source mep within the session is used to check for a locally-stored unicast MAC address for the peer. The local MEP must be administratively enabled. Peer MEP MAC addresses are learned and maintained by the ETH-CC protocol.

The no form of this command removes this session parameter.

Parameters

mep-id

Specifies the remote MEP ID of the peer within the association.

Values

1 to 8191

Platforms

All

remote-name

remote-name

Syntax

remote-name host-name

no remote-name

Context

[Tree] (config>router>l2tp>group>tunnel remote-name)

[Tree] (config>service>vprn>l2tp>group>tunnel remote-name)

Full Context

configure router l2tp group tunnel remote-name

configure service vprn l2tp group tunnel remote-name

Description

This command configures a string to be compared to the host name used by the tunnel peer during the authentication phase of tunnel establishment.

Default

no remote-name

Parameters

host-name

Specifies a remote host name for the tunnel, up to 64 characters.

Platforms

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

remote-proxy-arp

remote-proxy-arp

Syntax

[no] remote-proxy-arp

Context

[Tree] (config>service>ies>sub-if>grp-if remote-proxy-arp)

[Tree] (config>service>vprn>nw-if remote-proxy-arp)

[Tree] (config>service>ies>if remote-proxy-arp)

[Tree] (config>service>vprn>sub-if>grp-if remote-proxy-arp)

[Tree] (config>service>vprn>if remote-proxy-arp)

Full Context

configure service ies subscriber-interface group-interface remote-proxy-arp

configure service vprn nw-if remote-proxy-arp

configure service ies interface remote-proxy-arp

configure service vprn subscriber-interface group-interface remote-proxy-arp

configure service vprn interface remote-proxy-arp

Description

This command enables remote proxy ARP on the interface.

Remote proxy ARP is similar to proxy ARP. It allows the router to answer an ARP request on an interface for a subnet that is not provisioned on that interface. This allows the router to forward to the other subnet on behalf of the requester. To distinguish remote proxy ARP from local proxy ARP, local proxy ARP performs a similar function but only when the requested IP is on the receiving interface.

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

  • configure service ies subscriber-interface group-interface remote-proxy-arp
  • configure service vprn subscriber-interface group-interface remote-proxy-arp

All

  • configure service vprn interface remote-proxy-arp
  • configure service ies interface remote-proxy-arp

remote-proxy-arp

Syntax

[no] remote-proxy-arp

Context

[Tree] (config>subscr-mgmt>git>ipv4 remote-proxy-arp)

Full Context

configure subscriber-mgmt group-interface-template ipv4 remote-proxy-arp

Description

This command enables remote proxy ARP on the interface.

Remote proxy ARP is similar to proxy ARP. It allows the router to answer an ARP request on an interface for a subnet that is not provisioned on that interface. This allows the router to forward to the other subnet on behalf of the requester. To distinguish remote proxy ARP from local proxy ARP, local proxy ARP performs a similar function but only when the requested IP address is on the receiving interface.

The no form of this command disables remote proxy ARP on the interface.

Default

no remote-proxy-arp

Platforms

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

remote-proxy-arp

Syntax

[no] remote-proxy-arp

Context

[Tree] (config>router>if remote-proxy-arp)

Full Context

configure router interface remote-proxy-arp

Description

This command enables remote proxy ARP on the interface.

Default

no remote-proxy-arp

Platforms

All

remote-servers

remote-servers

Syntax

remote-servers

Context

[Tree] (config>service>vprn>aaa remote-servers)

Full Context

configure service vprn aaa remote-servers

Description

Commands in this context configure AAA remote servers on the VPRN.

Platforms

All

remote-source

remote-source

Syntax

[no] remote-source

Context

[Tree] (config>mirror>mirror-dest remote-source)

Full Context

configure mirror mirror-dest remote-source

Description

This command is used on a destination router in a remote mirroring solution. The mirroring (packet copy) is performed on the source router and sent via an SDP to the destination router. Remote mirroring requires remote source configuration on the destination router.

Remote mirroring allows a destination router to terminate SDPs from multiple remote source routers. This allows consolidation of packet sniffers or analyzers at a single or small set of points in a network (for example, a sniffer or analyze farm, or lawful interception gateway).

A remote-source entry must be configured on the destination router for each source router from which mirrored traffic is being sent via SDPs.

A mirror destination service that is configured for a destination router must not be configured as for a source router.

The emote source configuration is not applicable when routable LI encapsulation is being used on the mirror source router. The remote source configuration is only used when a source router is sending mirrored traffic to a destination router via SDPs.

Two types of remote-source entries can be configured:

  • far end

  • spoke SDP

Certain remote source types are applicable with certain SDP types. For descriptions of the command usage in the mirror-dest context, see the far-end and spoke-sdp commands.

The no form of this command removes all remote-source entries.

Platforms

All

remote-v6-ip

remote-v6-ip

Syntax

remote-v6-ip any

remote-v6-ip ipv6-prefix/prefix-length

no remote-v6-ip

Context

[Tree] (config>router>ipsec>sec-plcy>entry remote-v6-ip)

[Tree] (config>service>vprn>ipsec>sec-plcy>entry remote-v6-ip)

Full Context

configure router ipsec security-policy entry remote-v6-ip

configure service vprn ipsec security-policy entry remote-v6-ip

Description

This command specifies the remote v6 prefix for the security-policy entry.

Parameters

ipv6-prefix/prefix-length

Specifies the local v6 prefix and length.

Values

ipv6-address/prefix: ipv6-address

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

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

x [0 to FFFF]H

d [0 to 255]D

host bits must be 0

:: not allowed

prefix-length [1 to 28]

any

A keyword to specify that any address can be used.

Platforms

VSR

  • configure router ipsec security-policy entry remote-v6-ip

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

  • configure service vprn ipsec security-policy entry remote-v6-ip

remote-ve-name

remote-ve-name

Syntax

[no] remote-ve-name name

Context

[Tree] (config>service>epipe>bgp-vpws remote-ve-name)

Full Context

configure service epipe bgp-vpws remote-ve-name

Description

This command creates or edits a remote-ve-name. A single remote-ve-name can be created per BGP VPWS instance if the service is single-homed or uses a single pseudowire to connect to a pair of dual-homed systems. When the service requires active/standby pseudowires to be created to remote dual-homed systems then two remote-ve-names must be configured.

This context defines the remote PE to which a pseudowire will be signaled.

remote-ve-name commands can be added even if bgp-vpws is not shutdown.

The no form of this command removes the configured remote-ve-name from the bgp vpws node. It can be used when the BGP VPWS status is either shutdown or "no shutdown”.

Parameters

name

Specifies a site name up to 32 characters in length.

Platforms

All

remove

remove

Syntax

[no] remove

Context

[Tree] (config>service>vprn>bgp>attribute-set remove)

Full Context

configure service vprn bgp attribute-set remove

Description

This command configures BGP to ignore and silently discard ATTR_SETs in BGP routes received from PE-CE peers of the VPRN. The discarded ATTR_SETs do not affect BGP best-path selection in the VPRN, and they do not appear in the VPN-IP routes that result from the VRF export of the BGP routes. Nokia recommends enabling this command in most deployments.

The no form of this command configures BGP to ignore ATTR_SETs in BGP routes received from PE-CE peers of the VPRN without discarding them. This allows the ATTR_SETs to propagate between CE devices connected to the VPRN and to other PE devices when the BGP routes are exported as VPN-IP routes.

Note: If the configuration of this command is changed, ROUTE_REFRESH messages are sent to all PE-CE peers of the VPRN.

Default

no remove

Platforms

All

remove-oldest

remove-oldest

Syntax

[no] remove-oldest

Context

[Tree] (config>subscr-mgmt>sla-profile>host-limits remove-oldest)

Full Context

configure subscriber-mgmt sla-profile host-limits remove-oldest

Description

This command removes the oldest subscriber host when the host limit is reached.

The no form of this command maintains the oldest subscriber host when the host limit is reached.

Platforms

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

remove-private

remove-private

Syntax

[no] remove-private

Context

[Tree] (config>subscr-mgmt>bgp-prng-plcy remove-private)

Full Context

configure subscriber-mgmt bgp-peering-policy remove-private

Description

This command allows private AS numbers to be removed from the AS path before advertising them to BGP peers.

The OS software recognizes the set of AS numbers that are defined by IANA as private. These are AS numbers in the range 64512 through 65535, inclusive.

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

Private AS numbers are included in the AS path attribute.

Platforms

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

remove-private

Syntax

remove-private [limited] [skip-peer-as] [replace]

no remove-private

Context

[Tree] (config>service>vprn>bgp>group>neighbor remove-private)

[Tree] (config>service>vprn>bgp remove-private)

[Tree] (config>service>vprn>bgp>group remove-private)

Full Context

configure service vprn bgp group neighbor remove-private

configure service vprn bgp remove-private

configure service vprn bgp group remove-private

Description

When this command is configured private AS numbers are removed or replaced when they are found inside the AS path of BGP routes advertised to peers within the scope of the command.

The set of AS numbers that are defined by IANA as private are in the range of 64512 to 65534, and 4200000000 to 4294967294, inclusive. In SR OS, this command also removes ASN 65535 and ASN 4294967295, which are reserved values.

The no form of this command (at the BGP instance level) implements the default behavior, private AS numbers are allowed without restriction or modification in routes advertised to peers.

Default

no remove-private

Parameters

limited

This keyword instructs BGP to process private ASNs only up to the first public ASN encountered. Private ASNs beyond that first public AS will not be stripped or replaced.

skip-peer-as

This keyword instructs BGP to not strip or replace a private ASN from the AS-Path if that ASN is the same as the BGP peer AS number.

replace

When this keyword is configured, private ASNs are not stripped. Each occurrence is replaced by the ASN of the advertising BGP router (the ASN the router advertised to its peer in its OPEN message). When the replace keyword is not configured, private ASNs are stripped, subject to influence by the other keyword options. This generally results in a shortening of AS_PATH length.

Platforms

All

remove-private

Syntax

remove-private [limited] [skip-peer-as] [replace]

no remove-private

Context

[Tree] (config>router>bgp remove-private)

[Tree] (config>router>bgp>group remove-private)

[Tree] (config>router>bgp>group>neighbor remove-private)

Full Context

configure router bgp remove-private

configure router bgp group remove-private

configure router bgp group neighbor remove-private

Description

When this command is configured private AS numbers are removed or replaced when they are found inside the AS path of BGP routes advertised to peers within the scope of the command.

The set of AS numbers that are defined by IANA as private are in the range of 64512 to 65534, and 4200000000 to 4294967294, inclusive. In SR OS, this command also removes ASN 65535 and ASN 4294967295, which are reserved values.

The no form of this command (at the BGP instance level) implements the default behavior, private AS numbers are allowed without restriction or modification in routes advertised to peers.

Default

no remove-private

Parameters

limited

This keyword instructs BGP to process private ASNs only up to the first public ASN encountered. Private ASNs beyond that first public AS will not be stripped or replaced.

skip-peer-as

This keyword instructs BGP to not strip or replace a private ASN from the AS-Path if that ASN is the same as the BGP peer AS number.

replace

When this keyword is configured, private ASNs are not stripped. Each occurrence is replaced by the ASN of the advertising BGP router (the ASN the router advertised to its peer in its OPEN message). When the replace keyword is not configured, private ASNs are stripped, subject to influence by the other keyword options. This generally results in a shortening of AS_PATH length.

Platforms

All

renew

renew

Syntax

renew est-profile name cert cert-filename key key-filename [hash-alg hash-algorithm] output output-cert-filename [validate-cert-chain] [force]

Context

[Tree] (admin>certificate>est renew)

Full Context

admin certificate est renew

Description

This command renews an imported certificate (specified by the cert cert-filename) with a Certificate Authority (CA) using the EST protocol specified by the est-profile name, with an imported private key specified the key parameter. The key can be either the key of the certificate to be renewed or a new key.

The authentication between system and EST server is specified by the est-profile.

The hash-alg hash-alorithm parameter is used to generate the CSR (Certificate Signing Request) in the EST request message.

Parameters

name

Specifies EST profile name, up to 32 characters

cert-filename

Specifies the certificate file name, up to 95 characters

key-filename

Specifies the file name of a key, up to 95 characters

hash-algorithm

Specifies the hash algorithm to be used in a certificate request.

Values

sha1, sha224, sha256, sha384, sha512

output-cert-filename

Specifies the output cert file name, up to 200 characters

validate-cert-chain

Specifies that the the system validates the certificate chain of the result certificate before importing it

force

Specifies the system to overwrite the existing file with same output output-cert-filename

Platforms

All

renew-timer

renew-timer

Syntax

renew-timer [days days] [hrs hours] [min minutes] [sec seconds]

no renew-timer

Context

[Tree] (config>service>ies>sub-if>grp-if>ipv6>dhcp6>proxy-server renew-timer)

[Tree] (config>service>vprn>dhcp6>server>pool>prefix renew-timer)

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>ipv6-lease-times renew-timer)

[Tree] (config>router>dhcp6>server>pool>prefix renew-timer)

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host>ipv6-lease-times renew-timer)

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

Full Context

configure service ies subscriber-interface group-interface ipv6 dhcp6 proxy-server renew-timer

configure service vprn dhcp6 local-dhcp-server pool prefix renew-timer

configure subscriber-mgmt local-user-db ipoe host ipv6-lease-times renew-timer

configure router dhcp6 local-dhcp-server pool prefix renew-timer

configure subscriber-mgmt local-user-db ppp host ipv6-lease-times renew-timer

configure service vprn subscriber-interface group-interface ipv6 dhcp6 proxy-server renew-timer

Description

This command configures the lease renew time (T1) via LUDB.

The T1 is the time at which the client contacts the addressing authority to extend the lifetimes of the DHCPv6 leases (addresses or prefixes). T1 is a time duration relative to the current time expressed in units of seconds.

The IP addressing authority controls the time at which the client contacts the addressing authority to extend the lifetimes on assigned addresses through the T1 and T2 parameters assigned to an IA. At time T1 for an IA, the client initiates a Renew/Reply message exchange to extend the lifetimes on any addresses in the IA. The client includes an IA option with all addresses currently assigned to the IA in its Renew message. Recommended values for T1 and T2 are .5 and .8 times the shortest preferred lifetime of the addresses in the IA that the addressing authority is willing to extend, respectively.

The configured renew timer should always be smaller than or equal to the rebind timer.

The T1 and T2 are carried in the IPv6 address option that is within the IA.

The no form of this command reverts to the default.

Default

renew-timer min 30

Parameters

renew-timer

Specifies the preferred lifetime.

Values

days days

0 to 7

hrs hours

0 to 23

min minutes

0 to 59

sec seconds

0 to 59

Platforms

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

renew-timer

Syntax

renew-timer [days days] [hrs hours] [min minutes] [sec seconds]

no renew-timer

Context

[Tree] (config>router>dhcp6>server>defaults renew-timer)

Full Context

configure router dhcp6 local-dhcp-server defaults renew-timer

Description

This command configures the default renew timer.

The no form of this command reverts to the default.

Default

renew-timer min 30

Parameters

renew-timer

Specifies the timer after which the lease is renewed.

Values

days:

0 to 7

hours:

0 to 23

minutes:

0 to 59

seconds

0 to 59

Platforms

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

renotify

renotify

Syntax

renotify value

no renotify

Context

[Tree] (config>service>vpls>mac-notification renotify)

Full Context

configure service vpls mac-notification renotify

Description

This command controls the periodic interval at which sets of MAC notification messages are sent. At each expiration of the renotify timer, a new burst of notification messages is sent, specifically <count> frames at <interval> deci-seconds.

Default

no renotify

Parameters

value

Specifies the time interval between re-notification, in seconds

Values

240 to 840

Platforms

All

renum

renum

Syntax

renum src-entry-id to dst-entry-id

Context

[Tree] (config>service>mrp>mrp-policy renum)

Full Context

configure service mrp mrp-policy renum

Description

This command renumbers existing MRP policy entries to properly sequence policy entries. This may be required in some cases since the implementation exits when the first match is found and executes the actions according to the accompanying action command. This requires that entries be sequenced correctly from most to least explicit.

Parameters

src-entry-id

Specifies the entry number of an existing entry.

Values

1 to 65535

new-entry-id

Specifies the new entry number to be assigned to the old entry. If the new entry exists, an error message is generated.

Values

1 to 65535

Platforms

All

renum

Syntax

renum old-entry-id new-entry-id

Context

[Tree] (config>qos>sap-ingress>ip-criteria renum)

[Tree] (config>qos>sap-egress>ipv6-criteria renum)

[Tree] (config>qos>sap-ingress>mac-criteria renum)

[Tree] (config>qos>sap-ingress>ipv6-criteria renum)

[Tree] (config>qos>sap-egress>ip-criteria renum)

Full Context

configure qos sap-ingress ip-criteria renum

configure qos sap-egress ipv6-criteria renum

configure qos sap-ingress mac-criteria renum

configure qos sap-ingress ipv6-criteria renum

configure qos sap-egress ip-criteria renum

Description

This command renumbers existing QoS policy criteria entries to properly sequence policy entries.

This can be required in some cases since the router exits when the first match is found and executes the actions in accordance with the accompanying action command. This requires that entries be sequenced correctly from most to least explicit.

Parameters

old-entry-id

Enter the entry number of an existing entry.

Values

1 to 65535

new-entry-id

Enter the new entry number to be assigned to the old entry.

Values

1 to 65535

Platforms

All

renum

Syntax

renum old-entry-number new-entry-number

Context

[Tree] (config>qos>network>egress>ip-criteria renum)

[Tree] (config>qos>network>ingress>ip-criteria renum)

[Tree] (config>qos>network>ingress>ipv6-criteria renum)

[Tree] (config>qos>network>egress>ipv6-criteria renum)

Full Context

configure qos network egress ip-criteria renum

configure qos network ingress ip-criteria renum

configure qos network ingress ipv6-criteria renum

configure qos network egress ipv6-criteria renum

Description

This command renumbers existing QoS policy criteria entries to properly sequence policy entries.

This can be required in some cases since the router exits when the first match is found and executes the actions in accordance with the accompanying action command. This requires that entries be sequenced correctly from most to least explicit.

Parameters

old-entry-number

Enter the entry number of an existing entry.

Values

1 to 65535

new-entry-number

Enter the new entry number to be assigned to the old entry.

Values

1 to 65535

Platforms

All

renum

Syntax

renum old-entry-id new-entry-id

Context

[Tree] (config>filter>mac-filter renum)

[Tree] (config>filter>ip-exception renum)

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

[Tree] (config>filter>ipv6-exception renum)

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

Full Context

configure filter mac-filter renum

configure filter ip-exception renum

configure filter ip-filter renum

configure filter ipv6-exception renum

configure filter ipv6-filter renum

Description

This command renumbers existing MAC, IPv4/IPv6, IP exception filter, or IPv6 exception filter entries to properly sequence filter entries.

This may be required in some cases since the OS exits when the first match is found and executes the actions according to the accompanying action command. This requires that entries be sequenced correctly from most to least explicit.

Parameters

old-entry-id

Specifies the entry number of an existing entry, as a decimal integer.

Values

1 to 2097151

new-entry-id

Specifies the new entry-number to be assigned to the old entry, as a decimal integer.

Values

1 to 2097151

Platforms

All

  • configure filter ipv6-filter renum
  • configure filter ip-filter renum
  • configure filter mac-filter renum

VSR

  • configure filter ipv6-exception renum
  • configure filter ip-exception renum

renum

Syntax

renum old-entry-number new-entry-number

Context

[Tree] (config>system>security>mgmt-access-filter>ipv6-filter renum)

[Tree] (config>system>security>mgmt-access-filter>ip-filter renum)

[Tree] (config>system>security>mgmt-access-filter>mac-filter renum)

Full Context

configure system security management-access-filter ipv6-filter renum

configure system security management-access-filter ip-filter renum

configure system security management-access-filter mac-filter renum

Description

This command renumbers existing management access filter entries for an IP(v4), IPv6, or MAC filter to re-sequence filter entries.

The exits on the first match found and executes the actions in accordance with the accompanying action command. This may require some entries to be re-numbered differently from most to least explicit.

Parameters

old-entry-number

Specifies the entry number of the existing entry.

Values

1 to 9999

new-entry-number

Specifies the new entry number that will replace the old entry number.

Values

1 to 9999

Platforms

All

renum

Syntax

renum old-entry-id new-entry-id

Context

[Tree] (config>sys>sec>cpm>ip-filter renum)

[Tree] (config>sys>sec>cpm>ipv6-filter renum)

[Tree] (config>sys>sec>cpm>mac-filter renum)

Full Context

configure system security cpm-filter ip-filter renum

configure system security cpm-filter ipv6-filter renum

configure system security cpm-filter mac-filter renum

Description

This command renumbers existing IP(IPv4), IPv6, or MAC filter entries to re-sequence filter entries.

This may be required in some cases since the OS exits when the first match is found and execute the actions according to the accompanying action command. This requires that entries be sequenced correctly from most to least explicit.

Parameters

old-entry-id

Specifies the entry number of an existing entry.

Values

1 to 6144 for ip-filter and ipv6-filter

1 to 2048 for mac-filter

new-entry-id

Specifies the new entry number to be assigned to the old entry.

Values

1 to 6144 for ip-filter and ipv6-filter

1 to 2048 for mac-filter

Platforms

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

renum

Syntax

renum old-entry-number new-entry-number

Context

[Tree] (config>system>security>profile renum)

Full Context

configure system security profile renum

Description

This command renumbers profile entries to re-sequence the entries.

Since the OS exits when the first match is found and executes the actions according to accompanying action command, re-numbering is useful to rearrange the entries from most explicit to least explicit.

Parameters

old-entry-number

Enter the entry number of an existing entry.

Values

1 to 9999

new-entry-number

Enter the new entry number.

Values

1 to 9999

Platforms

All

renumber

renumber

Syntax

renumber from entry-id to entry-id

Context

[Tree] (config>router>policy-options>policy-statement renumber)

Full Context

configure router policy-options policy-statement renumber

Description

This command allows the operator to renumber the existing entry ID to a new entry ID. When performing the renumbering action, the two entry IDs must be different. The existing (from) entry-id must exist. The new (to) entry-id must not exist.

Renumbering is not saved in the configuration because it is a performing action.

Parameters

from entry-id

Specifies the existing entry ID to be renumbered.

Values

1 to 4294967295

to entry-id

Specifies the new entry ID to be assigned.

Values

1 to 4294967295

Platforms

All

reorder-audio

reorder-audio

Syntax

reorder-audio time

no reorder-audio

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>video reorder-audio)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>video reorder-audio)

Full Context

configure mcast-management multicast-info-policy bundle video reorder-audio

configure mcast-management multicast-info-policy bundle channel video reorder-audio

Description

This command configures the time, in milliseconds, by which the audio packets are reordered in the ad stream.

Configuring this parameter depends on what is configured on the A Server and the GOP sizes of the network stream. Typically, this configuration should match the A Server configuration.

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

Default

no reorder-audio

Parameters

time

Specifies the audio reorder time, in milliseconds.

Values

100 to 1000

Platforms

7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

repair

repair

Syntax

repair [cflash-id]

Context

[Tree] (file repair)

Full Context

file repair

Description

This command checks a compact flash device for errors and repairs any errors found.

Parameters

cflash-id

Specifies the compact flash slot ID to be shut down or enabled. When a specific cflash-id is specified, then that drive is shut down. If no flash-id is specified, the drive referred to by the current working directory is assumed. If a slot number is not specified, then the active CSM is assumed.

Values

cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

Default

the current compact flash device.

Platforms

All

repeat

repeat

Syntax

repeat padding

Context

[Tree] (config>test-oam>sath>svc-test>svc-stream>frm-payl>patt repeat)

Full Context

configure test-oam service-activation-testhead service-test service-stream frame-payload data-pattern repeat

Description

This command configures the data pattern padding bytes for the frames launched for the service stream.

The specified data pattern value is repeated as many times as required to fill the remaining length of the payload for the highest level of the specified PDU. If only the Ethernet and ETH-CFM information is added, the data pattern is included in the data TLV of the ETH-CFM frame.

Default

repeat 0

Parameters

padding

Specifies the data pattern to populate the payload data.

Values

0 to 4294967295

Platforms

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

repeated-characters

repeated-characters

Syntax

repeated-characters count

no repeated-characters

Context

[Tree] (config>system>security>password>complexity-rules repeated-characters)

Full Context

configure system security password complexity-rules repeated-characters

Description

The number of times a characters can be repeated consecutively.

The no form of this command resets to default.

Default

no repeated-characters

Parameters

count

Specifies the minimum count of consecutively repeated characters.

Values

2 to 8

Platforms

All

replace

replace

Syntax

replace [line]

Context

[Tree] (candidate replace)

Full Context

candidate replace

Description

This command displays the specified line (a single line only) and allows it to be changed.

Parameters

line

Indicates which line to replace starting at the point indicated by the following options.

Values

line, offset, first, edit-point, last

line

absolute line number

offset

relative line number to current edit point. Prefixed with '+' or '-'

first

keyword - first line

edit-point

keyword - current edit point

last

keyword - last line that is not 'exit'

Platforms

All

replace-result-code

replace-result-code

Syntax

replace-result-code code [code]

no replace-result-code

Context

[Tree] (config>service>vprn>l2tp replace-result-code)

[Tree] (config>router>l2tp replace-result-code)

Full Context

configure service vprn l2tp replace-result-code

configure router l2tp replace-result-code

Description

This command replaces CDN Result-Code 4, 5 and 6 on LNS with the Result Code 2. This is needed for interoperability with some implementation of LAC which only takes action based on CDN Result-Code 2 while ignoring CDN Result-Code 4, 5 and 6.

Default

no replace-result-code

Parameters

code

Specifies the L2TP Result codes that need to be replaced. Up to three codes can be specified.

Values

cdn-tmp-no-facilities — CDN Result-Code 4 on LNS are replaced with the result code 2 before it is sent to LAC.

cdn-prem-no-facilities — CDN Result-Code 5 on LNS are replaced with the result code 2 before it is sent to LAC.

cdn-inv-dest — CDN Result-Code 6 on LNS are replaced with the result code 2 before it is sent to LAC.

Platforms

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

replay-protection

replay-protection

Syntax

[no] replay-protection

Context

[Tree] (config>macsec>connectivity-association replay-protection)

Full Context

configure macsec connectivity-association replay-protection

Description

Specifies the size of the replay protection window.

This command must be configured to force packet discard when it has detected a packet that is not within the replay-window-size.

When replay protection is enabled, the sequence of the ID number of the received packets are checked. If the packet arrives out of sequence and the difference between the packet numbers exceeds the replay window size, the packet is counted by the receiving port and then discarded. For example, if the replay protection window size is set to five and a packet assigned the ID of 1006 arrives on the receiving link immediately after the packet assigned the ID of 1000, the packet that is assigned the ID of 1006 is counted and discarded because it falls outside the parameters of the replay window size.

Replay protection is especially useful for fighting man-in-the-middle attacks. A packet that is replayed by a man-in-the-middle attacker on the Ethernet link will arrive on the receiving link out of sequence, so replay protection helps ensure the replayed packet is dropped instead of forwarded through the network.

Replay protection should not be enabled in cases where packets are expected to arrive out of order.

Default

no replay-protection

Platforms

All

replay-window

replay-window

Syntax

replay-window replay-window-size

no replay-window

Context

[Tree] (config>service>ies>if>ipsec>ipsec-tunnel replay-window)

[Tree] (config>ipsec>tnl-temp replay-window)

[Tree] (config>service>vprn>if>sap>ipsec-tunnel replay-window)

[Tree] (config>ipsec>trans-mode-prof replay-window)

[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel replay-window)

Full Context

configure service ies interface ipsec ipsec-tunnel replay-window

configure ipsec tunnel-template replay-window

configure service vprn interface sap ipsec-tunnel replay-window

configure ipsec ipsec-transport-mode-profile replay-window

configure service vprn interface ipsec ipsec-tunnel replay-window

Description

This command specifies the size of the anti-replay window. The anti-replay window protocol further secures IPsec against an entity that can inject a recorded message in a message stream from a source to a destination computer on the Internet.

Default

no replay-window

Parameters

replay-window-size

Specifies the size of the SA anti-replay window.

Values

32, 64, 128, 256, 512

Platforms

VSR

  • configure service ies interface ipsec ipsec-tunnel replay-window
  • configure service vprn interface ipsec ipsec-tunnel replay-window

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

  • configure ipsec tunnel-template replay-window
  • configure ipsec ipsec-transport-mode-profile replay-window
  • configure service vprn interface sap ipsec-tunnel replay-window

replay-window-size

replay-window-size

Syntax

replay-window-size number-of-packets

no replay-window-size

Context

[Tree] (config>macsec>connectivity-association replay-window-size)

Full Context

configure macsec connectivity-association replay-window-size

Description

This command specifies the size of the replay protection window.

This command must be configured to enable replay protection. When replay protection is enabled, the sequence of the ID number of received packets are checked. If the packet arrives out of sequence and the difference between the packet numbers exceeds the replay protection window size, the packet is dropped by the receiving port. For example, if the replay protection window size is set to five and a packet assigned the ID of 1006 arrives on the receiving link immediately after the packet assigned the ID of 1000, the packet that is assigned the ID of 1006 is dropped because it falls outside the parameters of the replay protection window.

Replay protection is especially useful for fighting man-in-the-middle attacks. A packet that is replayed by a man-in-the-middle attacker on the Ethernet link will arrive on the receiving link out of sequence, so replay protection helps ensure the replayed packet is dropped instead of forwarded through the network.

Replay protection should not be enabled in cases where packets are expected to arrive out of order.

When the number-of-packets variable is set to 0, all packets that arrive out-of-order are dropped.

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

Default

replay-window-size 0

Parameters

number-of-packets

Specifies the window for which the packets can arrive out of order.

Values

0 to 4294967294

Platforms

All

replication-segment

replication-segment

Syntax

[no] replication-segment policy-name

Context

[Tree] (config>router>p2mp-sr-tree replication-segment)

Full Context

configure router p2mp-sr-tree replication-segment

Description

This command creates a P2MP SR tree replication segment entry for the P2MP LSP.

The no form of this command deletes the replication segment entry.

Parameters

policy-name

Specifies the P2MP policy name, up to 32 characters, associated with the forwarding instructions contained in the replication segment.

Platforms

All

replication-sid

replication-sid

Syntax

replication-sid label [label]

no replication-sid

Context

[Tree] (config>router>p2mp-sr-tree>replication-segment>next-hop-id replication-sid)

Full Context

configure router p2mp-sr-tree replication-segment next-hop-id replication-sid

Description

This command configures the replication SID or a SID list for the next hop of the P2MP SR tree replication segment.

When a SID list is configured, the replication SID is at the bottom of the stack and the unicast node or the adjacency SID is at the top of the stack. The SID at the top of the stack must be configured first in the list and the replication SID at the bottom of the list must be configured last in the list.

The no form of this command removes the replication SID.

Parameters

label

Specifies the label of the replication SID; up to a maximum of 11 labels.

Values

3, 16 to 1048575, 4294967295

Platforms

All

replication-threshold

replication-threshold

Syntax

replication-threshold seconds

no replication-threshold

Context

[Tree] (config>isa>nat-group>inter-chassis-redundancy replication-threshold)

Full Context

configure isa nat-group inter-chassis-redundancy replication-threshold

Description

This command configures the minimum duration of the flow that needs to be met before it is synchronized to the standby node. This way, flow synchronization and statefulness in a multi-chassis environment are limited only to long-lived flows.

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

Default

replication-threshold 20

Parameters

seconds

Specifies the minimum flow existence time before it is synchronized.

Values

0 to 300

Platforms

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

reply-on-padt

reply-on-padt

Syntax

[no] reply-on-padt

Context

[Tree] (config>subscr-mgmt>ppp-policy reply-on-padt)

Full Context

configure subscriber-mgmt ppp-policy reply-on-padt

Description

This command enables replying to PPPoE Active Discovery Terminate (PADT) packets. Some of the PPPoE clients expect reply on PADT message before the context of the session is cleared up. To support such client, a command enabling reply to PADT is provided.

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

report-alarm

report-alarm

Syntax

[no] report-alarm [ais] [los] [ oof] [rai] [looped]

Context

[Tree] (config>port>tdm>e3 report-alarm)

[Tree] (config>port>tdm>ds3 report-alarm)

Full Context

configure port tdm e3 report-alarm

configure port tdm ds3 report-alarm

Description

This command enables logging of DS-3 and E-3 alarms for a DS-3/E-3 port or channel.

The no form of this command disables logging of the specified alarms.

Parameters

ais

Reports alarm indication signal errors. When configured, ais alarms are not raised and cleared.

Default

ais alarms are issued

los

Reports loss of signal errors. When configured, los traps are not raised and cleared.

Default

los traps are issued

oof

Reports out-of-frame errors. When configured, oof alarms are not raised and cleared.

Default

oof alarms are not issued

rai

Reports resource availability indicator events. When configured, rai events are not raised and cleared.

Default

rai alarms are not issued

looped

Reports looped packets errors.

Default

looped alarms are not issued

Platforms

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

report-alarm

Syntax

[no] report-alarm [signal-fail] [remote] [ local] [no-frame-lock] [ high-ber] [no-block-lock] [ no-am-lock] [duplicate-lane]

Context

[Tree] (config>port>ethernet report-alarm)

Full Context

configure port ethernet report-alarm

Description

This command specifies when and if to generate alarms and alarm clear notifications for this port.

Note:

For some DWDM transceivers, if the configure port dwdm coherent rx-los-reaction squelch command is disabled the signal-fail and no-am-lock alarm conditions are not reported when the media side of the transceiver has an RX LOS condition.

Parameters

signal-fail

Reports an Ethernet signal lost alarm.

remote

Reports remote faults.

local

Reports local faults.

no-frame-lock

Reports a 'not locked on the Ethernet framing sequence' alarm.

high-ber

Reports High Bit Error Rate.

no-block-lock

Reports 40G/100G PCS Lanes Not Block Locked.

no-am-lock

Reports 40G/100G PCS Alignment Marker Loss of Lock.

duplicate-lane

Reports 40G/100G PCS Duplicate Lane Marker.

Platforms

All

report-alarm

Syntax

[no] report-alarm [loc] [lais] [ lrdi] [ss1f] [lb2er-sd] [lb2er-sf] [slof] [ slos] [lrei]

Context

[Tree] (config>port>sonet-sdh report-alarm)

Full Context

configure port sonet-sdh report-alarm

Description

This command enables logging of SONET (SDH) line and section alarms for a SONET-SDH port. Only line and section alarms can be configured in the SONET/SDH context, for path alarms see the sonet-sdh>path context.

The no form of this command disables logging of the specified alarms.

This command is supported on TDM satellites.

Parameters

loc

Reports a loss of clock which causes the operational state of the port to be shut down.

Default

loc alarms are issued

lais

Reports line alarm indication signal errors. When configured, lais alarms are raised and cleared.

Default

lais alarms are not issued

lrdi

Reports line remote defect indication errors. LRDI's are caused by remote LOF, LOC, LOS. When configured, lrdi alarms are raised and cleared.

Default

lrdi alarms are issued

ss1f

Reports section synchronization failure which is detected when the S1 byte is not consistent for 8 consecutive frames. When configured, ss1f alarms are raised and cleared.

Default

ss1f alarms are not issued

lb2er-sd

Reports line signal degradation BER (bit interleaved parity) errors. Use the threshold command to set the error rate(s) that when crossed determine signal degradation and signal failure. When configured, lb2er-sd alarms are raised and cleared.

Default

lb2er-sd alarms are not issued

lb2er-sf

Reports line signal failure BER errors. Use the threshold command to set the error rate(s) that when crossed determine signal degradation and signal failure. When configured, lb2er-sf alarms are raised and cleared.

Default

lb2er-sf alarms are issued

slof

Reports section loss of frame errors. When configured, slof alarms are raised and cleared.

Default

slof alarms are issued

slos

Reports a section loss of signal error on the transmit side. When configured, slos alarms are raised and cleared.

Default

slos alarms are issued

lrei

Reports a line error condition raised by the remote as a result of b1 errors received from this node. When configured, lrei traps are raised but not cleared.

Default

lrei traps are not issued

Platforms

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

report-alarm

Syntax

[no] report-alarm {pais | plop | prdi | pplm | prei}

Context

[Tree] (config>port>sonet-sdh>path report-alarm)

Full Context

configure port sonet-sdh path report-alarm

Description

This command enables logging of SONET (SDH) path alarms for a SONET-SDH port. Only path alarms can be configured in the channel context.

The no form of this command disables logging of the specified alarms.

Parameters

pais

Reports path alarm indication signal errors. When configured, pais alarms are raised and cleared.

Default

pais alarms are not issued

plop

Reports path loss of pointer (per tributary) errors. When configured, plop traps are raised but not cleared.

Default

plop traps are issued

prdi

Reports path remote defect indication errors. When configured, prdi alarms are raised and cleared.

Default

prdi alarms are not issued

pplm

Reports a path payload mismatch, as a result the channel will be brought down. When configured, pplm traps are raised but not cleared.

Default

pplm traps are issued

prei

Reports a path error condition raised by the remote as a result of b3 errors received from this node. When configured, prei traps are raised but not cleared.

Default

prei traps are not issued

Platforms

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

report-alarm

Syntax

[no] report-alarm [ais] [los] [ oof] [rai] [looped] [ber-sd] [ber-sf]

Context

[Tree] (config>port>tdm>e1 report-alarm)

[Tree] (config>port>tdm>ds1 report-alarm)

Full Context

configure port tdm e1 report-alarm

configure port tdm ds1 report-alarm

Description

This command enables logging of DS-1/DS-3 or E-1/E-3 alarms for DS-1/DS-3 or E-1/E-3 ports or channels.

The no form of this command disables logging of the specified alarms.

Parameters

ais

Reports alarm indication signal errors. When configured, ais alarms are not raised and cleared.

Default

ais alarms are issued

los

Reports loss of signal errors. When configured, los traps are not raised and cleared.

Default

los traps are issued.

oof

Reports out-of-frame errors. When configured, oof alarms are not raised and cleared.

Default

oof alarms are not issued.

rai

Reports resource availability indicator events. When configured, rai events are not raised and cleared.

Default

rai alarms are not issued

looped

Reports looped packets errors.

looped alarms are not issuedlof

Reports loss of frame errors. When configured, lof traps are not raised and cleared.

Default

lof traps are issued

ber-sd

Specifies the BER that specifies signal degradation.

ber-sf

Specifies the BER that specifies signal failure.

Platforms

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

report-alarm

Syntax

[no] report-alarm [stray] [malformed] [pktloss] [overrun] [underrun] [rpktloss] [rfault] [rrdi]

Context

[Tree] (config>service>cpipe>sap>cem report-alarm)

[Tree] (config>service>epipe>sap>cem report-alarm)

Full Context

configure service cpipe sap cem report-alarm

configure service epipe sap cem report-alarm

Description

This command indicates the type of CEM SAP alarm.

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

Default

On: stray, malformed, pktloss and overrun

Off: rpktloss, rfault, rrdi

Parameters

stray

Reports the reception of packets not destined for this CES circuit.

malformed

Reports the reception of packet not properly formatted as CES packets.

pktloss

Reports the lack of reception of CES packets.

overrun

Reports the reception of too many CES packets resulting in a overrun of the receive jitter buffer.

underrun

Reports the reception of too few CES packets resulting in a overrun of the receive jitter buffer.

rpktloss

Reports that the remote peer is currently in packet loss status.

rfault

Reports that the remote TDM interface is currently not in service.

rrdi

Reports that the remote TDM interface is currently in RDI status.

Platforms

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

  • configure service cpipe sap cem report-alarm

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

  • configure service epipe sap cem report-alarm

report-alarm

Syntax

report-alarm severity {tnc | qos | poa}

no report-alarm

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>video>analyzer>alarms report-alarm)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>video>analyzer>alarms report-alarm)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>source-override>video>analyzer>alarms report-alarm)

Full Context

configure mcast-management multicast-info-policy bundle channel video analyzer alarms report-alarm

configure mcast-management multicast-info-policy bundle video analyzer alarms report-alarm

configure mcast-management multicast-info-policy bundle channel source-override video analyzer alarms report-alarm

Description

This command configures the type of alarm to monitor and raise through SNMP. The severity of alarms increases from TNC, to QoS, and then to POA. For example, if QoS alarms are configured, the analyzer only raises alarms and events related to QoS. The analyzer may raise alarms for POA events if they occur, but alarms for TNC are not sent.

Default

no report-alarm

Parameters

severity

Keyword to configure the type of alarm.

tnc

Specifies to monitor and raise alarms for TNC events.

qos

Specifies to monitor and raise alarms for QoS events.

poa

Specifies to monitor and raise alarms for POA events.

Platforms

7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

report-alarms

report-alarms

Syntax

[no] report-alarms [modflt] [mod] [ netrx] [nettx] [hosttx]

Context

[Tree] (config>port>dwdm>coherent report-alarms)

Full Context

configure port dwdm coherent report-alarms

Description

This command configures the alarms that will be reported for the coherent module.

Default

modflt mod netrx nettx hosttx

Parameters

modflt

Reports module fault alarm.

mod

Reports module alarm.

netrx

Reports network (optical side) receive alarm.

nettx

Reports network (optical side) transmit alarm.

hosttx

Reports host (electrical side) transmit alarm.

Platforms

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

report-alarms

Syntax

[no] report-alarms [loc] [los] [ lof] [lom] [otu-ais] [otu-ber-sf] [otu-ber-sd] [otu-bdi] [otu-tim] [ otu-iae] [otu-biae] [ fec-sf] [fec-sd] [ fec-fail] [ fec-uncorr] [odu-ais] [ odu-oci] [odu-lck] [ odu-bdi] [ odu-tim] [opu-plm]

Context

[Tree] (config>port>otu report-alarms)

Full Context

configure port otu report-alarms

Description

This command enables OTU alarms. Specify specific alarms to add to the list of reported alarms.

The no form of this command disables OTU alarm reporting.

Default

loc, los, lof, lom, otu-ber-sf, otu-bdi, fec-sf

Parameters

alarms

Refer to Alarm Descriptions for alarm descriptions.

Table 2. Alarm Descriptions

Alarm

Description

loc

Loss of clock.

lof

Loss of OTU framing.

lom

Loss of Multi-frame.

los

Loss of signal transitions on the data.

otu-ais

OTU Alarm Indication Signal (all 1s, overwrites all OTU overhead, even framing bytes).

otu-ber-sf

SM Signal Fail (based on BPI8).

otu-ber-sd

SM Signal Degrade (based on BPI8).

otu-bdi

SM Backward defect indication.

otu-tim

SM Trace Id Mismatch.

otu-iae

SM Incoming Alignment Error.

otu-biae

SM Backward Incoming Alignment Error.

fec-sf

Signal Fail (based on FEC corrected bits).

fec-sd

Signal Degrade (based on FEC corrected bits).

fec-fail

FEC Mode mismatch (EFEC-GFEC) or High Uncorrectable rate (>10E-2).

fec-uncorr

One or More Uncorrectable FEC errors.

odu-ais

ODU Alarm Indication Signal.

odu-oci

ODU Open connection Indication.

odu-lck

ODU Locked.

odu-bdi

PM Backward Defect indication.

odu-tim

PM Trace Id Mismatch.

opu-plm

OPU PSI Payload Type Mismatch.

Platforms

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

report-ip-address-event

report-ip-address-event

Syntax

[no] report-ip-address-event

Context

[Tree] (config>subscr-mgmt>diam-appl-plcy>gx report-ip-address-event)

Full Context

configure subscriber-mgmt diameter-application-policy gx report-ip-address-event

Description

This command enables triggered CCR-u messages based on IP address allocation or de-allocation for the subscriber host.

If the requests for both IP address families (IPv4 and IPv6) arrive at approximately the same time, a single CCR-i is sent containing the IP addresses from both address families, IPv4 and IPv6 (NA, PD, or SLAAC). When the requests for IP addresses are not nearly simultaneous, the CCR-i contains only the IP address that was allocated first (the one that triggered the session creation). The request for the second IP address family, depending on configuration, triggers an additional CCR-u that will carry the IP address allocation update to the PCRF along with the UE_IP_ADDRESS_ALLOCATE (18) event. The CCR-u content mirrors the content of the CCR-i with the exception of already allocated IP address(es).

When this command is disabled, IP address-triggered CCR-u messages are not sent.

The no form of this command disables the command.

Default

report-ip-address-event

Platforms

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

report-local-routes

report-local-routes

Syntax

[no] report-local-routes

Context

[Tree] (config>bmp>station report-local-routes)

Full Context

configure bmp station report-local-routes

Description

This command enables local route reporting to the BMP monitoring station.

The no form of this command disables the local route reporting.

Platforms

All

report-path-constraints

report-path-constraints

Syntax

report-path-constraints

no report-path-constraints

Context

[Tree] (config>router>pcep>pcc report-path-constraints)

Full Context

configure router pcep pcc report-path-constraints

Description

This command enables the inclusion of LSP path constraints in the PCE report messages sent from the PCC to a PCE.

In order for the PCE to know about the original constraints for an LSP which is delegated, but for which there is no prior state in its LSP database, such as if no PCReq message was sent for the same PLSP-ID, the following proprietary behavior is observed:

  • PCC appends a duplicate of each of the LSPA, METRIC, and BANDWIDTH objects in the PCRpt message. The only difference between two objects of the same type is that the P-flag is set in the common header of the duplicate object to indicate that it is a mandatory object for processing by PCE.

  • The value of the metric or bandwidth in the duplicate object contains the original constraint value, while the first object contains the operational value. This is applicable to hop metrics in the METRIC and BANDWIDTH objects only. The SR OS PCC does not support configuring a boundary on the path computation IGP or TE metrics.

  • The path computation on the PCE must use the first set of objects when updating a path if the PCRpt contained a single set. If the PCRpt contained a duplicate set, PCE path computation must use the constraints in the duplicate set.

The no form of the command disables the above behavior in case of interoperability issues with third-party PCE implementations.

Default

report-path-constraints

Platforms

All

report-rate

report-rate

Syntax

report-rate agg-rate-limit

report-rate scheduler scheduler-name

report-rate pppoe-actual-rate

report-rate policer policer-id

report-rate rfc5515-actual-rate

no report-rate

Context

[Tree] (config>subscr-mgmt>sla-prof>ingress report-rate)

[Tree] (config>subscr-mgmt>sla-prof>egress report-rate)

Full Context

configure subscriber-mgmt sla-profile ingress report-rate

configure subscriber-mgmt sla-profile egress report-rate

Description

This command configures the source for Tx and Rx connect speeds in AVP 38 (Rx Connect Speed) and AVP 24 (Tx Connect Speed) of an L2TP session established on a LAC.

The no form of this command reverts to the default.

Parameters

agg-rate-limit

Specifies that the rate (egress only) is taken from:

  1. the agg-rate RADIUS override (RADIUS VSA "Alc-Subscriber-QoS-Override” in a RADIUS Access-Accept message) if present

  2. the configured agg-rate-limit in the config>subscr-mgmt>sub-prof>egr context

  3. fall back to the default (no report-rate)

scheduler-name

Specifies the rate taken from the scheduler scheduler-name up to 32 characters. If the scheduler scheduler-name is not present in the scheduler-policy configured in the config>subscr-mgmt>sub-prof>egr context, fall back to the default (no report-rate).

pppoe-actual-rate

Specifies rates taken from the DSL Line characteristics PPPoE tags (Actual Data Rate Upstream/Downstream) if present; otherwise fall back to the default (no report-rate).

policer-id

Specifies the rate taken from the policer with the specified ID.

Values

1 to 63

rfc5515-actual-rate

Puts the same value as the transmitted Actual-Data-Rate-Upstream AVP in the Rx-Connect-Speed AVP, and the same value as the transmitted Actual-Data-Rate-Downstream AVP in the Tx-Connect-Speed AVP

Platforms

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

report-src-ip

report-src-ip

Syntax

report-src-ip ip-address

no report-src-ip

Context

[Tree] (config>service>vpls>igmp-snooping report-src-ip)

Full Context

configure service vpls igmp-snooping report-src-ip

Description

This command configures the source IPv4 address used when generating IGMP reports. According the IGMPv3 standard, a zero source address is allowed in sending IGMP reports. However, for interoperability with some multicast routers, the source IP address of IGMP group reports can be configured using this command.

Default

report-src-ip 0.0.0.0

Parameters

ip-address

Specifies the source IPv4 address in transmitted IGMP reports.

Values

a.b.c.d

Platforms

All

report-src-ip

Syntax

report-src-ip ipv6-address

no report-src-ip

Context

[Tree] (config>service>vpls>mld-snooping report-src-ip)

Full Context

configure service vpls mld-snooping report-src-ip

Description

This command configures the source IPv6 address used when generating MLD reports. A zero source address is allowed in sending MLD reports. However, for interoperability with some multicast routers, the source IP address of MLD reports can be configured using this command.

Default

report-src-ip 0:0:0:0:0:0:0:0

Parameters

ipv6-address

Specifies the source IPv6 address in transmitted MLD reports.

Values

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

Platforms

All

report-wlan-location

report-wlan-location

Syntax

[no] report-wlan-location

Context

[Tree] (config>subscr-mgmt>gtp>peer-profile report-wlan-location)

Full Context

configure subscriber-mgmt gtp peer-profile report-wlan-location

Description

This command enables reporting the WLAN location or cellular location of the UE in the signaling interface (S2a or Gn) between the WLAN GW and the mobile gateway (PGW or GGSN).

The no form of this command disables location reporting.

Default

no report-wlan-location

Platforms

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

reporting

reporting

Syntax

[no] reporting

Context

[Tree] (config>subscr-mgmt>diam-appl-plcy>gy>efh>interim-c reporting)

Full Context

configure subscriber-mgmt diameter-application-policy gy extended-failure-handling interim-credit reporting

Description

This command enables reporting of the used interim credit for each rating group when a new Diameter Gy session is successfully established with the Online Charging Server (OCS). When enabled, the used interim credit report includes:

  • the unreported used credit assigned via the initial Diameter Gy session when Extended Failure Handling (EFH) became active

  • the used interim credits during EFH

  • the used credits assigned via the new established Diameter Gy session

The no form of this command disables interim credit reporting. Only credit assigned via the new established Diameter Gy session is reported.

Platforms

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

reporting

Syntax

[no] reporting

Context

[Tree] (config>test-oam>link-meas>template reporting)

Full Context

configure test-oam link-measurement measurement-template reporting

Description

This command specifies whether values that reach a configured threshold are reported to the routing engine. Reaching a configured sample-window or aggregate-sample-window indicates a value of interest.

When this command is disabled, values reaching thresholds are not reported to the routing engine. In both enabled and disabled cases, the sample-window and aggregate-sample-window information and computed values are stored on the node until overwriting occurs.

Default

reporting

Platforms

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

request

request

Syntax

request seconds

Context

[Tree] (config>li>x-interfaces>x3>timeouts request)

[Tree] (config>li>x-interfaces>x2>timeouts request)

Full Context

configure li x-interfaces x3 timeouts request

configure li x-interfaces x2 timeouts request

Description

This command configures the X2 and X3 keep-alive timeout.

Parameters

seconds

Specifies the maximum time to wait for a LIC reply to a request. The system retries up to three more times, and if no reply is received, the system initiates a connection release and logs the failure event.

Values

5 to 30

Default

5

Platforms

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

request-format

request-format

Syntax

request-format

Context

[Tree] (config>system>security>tacplus request-format)

[Tree] (config>service>vprn>aaa>rmt-srv>tacplus request-format)

Full Context

configure system security tacplus request-format

configure service vprn aaa remote-servers tacplus request-format

Description

Commands in this context configure access operations that are sent to the TACACS+ server during authorization.

Platforms

All

request-script-policy

request-script-policy

Syntax

request-script-policy script-policy

no request-script-policy

Context

[Tree] (config>aaa>radius-srv-plcy request-script-policy)

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

Full Context

configure aaa radius-server-policy request-script-policy

configure aaa l2tp-accounting-policy request-script-policy

Description

This command configures a RADIUS script policy to modify Access-Request.

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

Parameters

script-policy

Specifies the name of the Python script used to modify Access-Request messages.

Platforms

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

request-script-policy

Syntax

request-script-policy policy-name

no request-script-policy

Context

[Tree] (config>subscr-mgmt>auth-plcy request-script-policy)

Full Context

configure subscriber-mgmt authentication-policy request-script-policy

Description

This command configures the RADIUS script policy used to change the RADIUS attributes of the outgoing Access-Request messages.

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

Parameters

policy-name

Specifies the name of the Python script to modify Access-Request messages.

Platforms

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

request-timer

request-timer

Syntax

request-timer timer1 retry-timer timer2 timeout-multiplier multiplier

no request-timer

Context

[Tree] (config>service>vpls>spoke-sdp>control-channel-status request-timer)

[Tree] (config>service>epipe>spoke-sdp>control-channel-status request-timer)

[Tree] (config>service>cpipe>spoke-sdp>control-channel-status request-timer)

Full Context

configure service vpls spoke-sdp control-channel-status request-timer

configure service epipe spoke-sdp control-channel-status request-timer

configure service cpipe spoke-sdp control-channel-status request-timer

Description

This command configures the control channel status request mechanism. When it is configured, control channel status request procedures are used. These augment the procedures for control channel status messaging from RFC 6478. This command cannot be used with a non-zero refresh-timer value.

Parameters

timer1

Specifies the interval, in seconds, at which pseudowire status messages, including a reliable delivery TLV with the "request” bit set, are sent.

Values

10 to 65535

timer2

specifies the timeout interval, in seconds, if no response to a pseudowire status request is received. This parameter must be configured. A value of zero (0) disables retries.

Values

0, 3 to 60

multiplier

If a requesting node does not receive a valid response to a pseudowire status request within a number of seconds equal to the retry timer multiplied by this multiplier, then it will assume the pseudowire is down. This parameter is optional.

Values

3 to 20

Platforms

All

  • configure service vpls spoke-sdp control-channel-status request-timer
  • configure service epipe spoke-sdp control-channel-status request-timer

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

  • configure service cpipe spoke-sdp control-channel-status request-timer

request-timer

Syntax

request-timer request-timer-secs retry-timer retry-timer-secs timeout-multiplier multiplier

no request-timer

Context

[Tree] (config>service>vpls>spoke-sdp>control-channel-status request-timer)

Full Context

configure service vpls spoke-sdp control-channel-status request-timer

Description

This command configures the control channel status request mechanism. When it is configured, control channel status request procedures are used. These augment the procedures for control channel status messaging from RFC 6478, Pseudowire Status for Static Pseudowires. This command cannot be used with a non-zero refresh-timer value.

Parameters

request-timer-secs

Specifies the interval, in seconds, at which pseudowire status messages, including a reliable delivery TLV with the "request” bit set, are sent.

Values

10 to 65535

retry-timer-secs

specifies the timeout interval, in seconds, if no response to a pseudowire status request is received. This parameter must be configured. A value of zero (0) disables retries.

Values

0, 3 to 60

multiplier

If a requesting node does not receive a valid response to a pseudowire status request within a number of seconds equal to the retry timer multiplied by this multiplier, then it will assume the pseudowire is down. This parameter is optional.

Values

3 to 20

Platforms

All

request-timer

Syntax

request-timer timer1 retry-timer timer2 timeout-multiplier multiplier

no request-timer

Context

[Tree] (config>service>ies>if>spoke-sdp>control-channel-status request-timer)

Full Context

configure service ies interface spoke-sdp control-channel-status request-timer

Description

This command configures the control channel status request mechanism. When it is configured, control channel status request procedures are used. These augment the procedures for control channel status messaging from RFC 6478. This command is mutually exclusive with a non-zero refresh-timer value.

Parameters

timer1

Specifies the interval at which pseudowire status messages, including a reliable delivery TLV, with the "request” bit set, are sent.

Values

10 to 65535 seconds

retry-timer timer2

Specifies the timeout interval if no response to a pseudowire status request is received. This parameter must be configured. A value of zero (0) disables retries.

Values

0, 3 to 60 seconds

timeout-multiplier multiplier

If a requesting node does not receive a valid response to a pseudowire status request within this multiplier times the retry timer, then it will assume the pseudowire is down. This parameter is optional.

Values

3 to 20 seconds

Platforms

All

request-timer

Syntax

request-timer request-timer-secs retry-timer retry-timer-secs timeout-multiplier multiplier

no request-timer

Context

[Tree] (config>service>vprn>red-if>spoke-sdp>control-channel-status request-timer)

[Tree] (config>service>vprn>if>spoke-sdp>control-channel-status request-timer)

Full Context

configure service vprn redundant-interface spoke-sdp control-channel-status request-timer

configure service vprn interface spoke-sdp control-channel-status request-timer

Description

This command configures the control channel status request mechanism. When it is configured, control channel status request procedures are used. These augment the procedures for control channel status messaging from RFC 6478. This command is mutually exclusive with a non-zero refresh-timer value.

Parameters

request-timer-secs

Specifies the interval, in seconds, at which pseudowire status messages, including a reliable delivery TLV, with the "request” bit set, are sent.

Values

10 to 65535

retry-timer retry-timer-secs

Specifies the timeout interval, in seconds, if no response to a pseudowire status request is received. This parameter must be configured. A value of zero (0) disables retries.

Values

0, 3 to 60

timeout-multiplier multiplier

Specifies the multiplier, in seconds. If a requesting node does not receive a valid response to a pseudowire status request within this multiplier times the retry timer, then it assume the pseudowire is down. This parameter is optional.

Values

3 to 15

Platforms

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

  • configure service vprn redundant-interface spoke-sdp control-channel-status request-timer

All

  • configure service vprn interface spoke-sdp control-channel-status request-timer

request-timer

Syntax

request-timer request-timer-secs retry-timer retry-timer-secs timeout-multiplier multiplier

no request-timer

Context

[Tree] (config>mirror>mirror-dest>spoke-sdp>control-channel-status request-timer)

[Tree] (config>mirror>mirror-dest>remote-src>spoke-sdp>control-channel-status request-timer)

Full Context

configure mirror mirror-dest spoke-sdp control-channel-status request-timer

configure mirror mirror-dest remote-source spoke-sdp control-channel-status request-timer

Description

This command configures the control channel status request mechanism. When it is configured, control channel status request procedures are used. These augment the procedures for control channel status messaging from RFC 6478. This command is mutually exclusive with a non-zero refresh-timer value.

Parameters

request-timer-secs

Specifies the interval, in seconds, at which pseudowire status messages, including a reliable delivery TLV, with the "request” bit set, are sent.

Values

10 to 65535

retry-timer-secs

Specifies the timeout interval, in seconds, if no response to a pseudowire status request is received. This parameter must be configured. A value of zero (0) disables retries.

Values

3 to 60

multiplier

Specifies the multiplier, in seconds, that if a requesting node does not receive a valid response to a pseudowire status request within this multiplier times the retry timer, then it will assume the pseudowire is down. This parameter is optional.

Values

3 to 15

Platforms

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

requests

requests

Syntax

[no] requests [neighbor ip-int-name | ip-address]

Context

[Tree] (debug>router>rip requests)

Full Context

debug router rip requests

Description

This command enables debugging for RIP requests.

Parameters

ip-int-name | ip-address

Debugs the RIP requests sent on the neighbor IP address or interface.

Platforms

All

requests

Syntax

[no] requests [neighbor ip-int-name | ipv6-address]

Context

[Tree] (debug>router>ripng requests)

Full Context

debug router ripng requests

Description

This command enables debugging for RIP requests.

Parameters

ip-int-name| ipv6-address

Debugs the RIP requests sent on the neighbor IP address or interface.

Platforms

All

required

required

Syntax

required [lowercase count] [uppercase count] [numeric count] [special-character count]

no required

Context

[Tree] (config>system>security>password>complexity-rules required)

Full Context

configure system security password complexity-rules required

Description

Force the minimum number of different character classes required.

The no form of this command resets to default.

Default

required lowercase 0 uppercase 0 numeric 0 special-character 0

Parameters

count

Specifies the minimum count of characters classes.

Values

0 to 10

Platforms

All

rescue-location

rescue-location

Syntax

rescue-location file-url

no rescue-location

Context

[Tree] (config>system>rollback rescue-location)

Full Context

configure system rollback rescue-location

Description

The location and filename of the rescue configuration is configurable to be local (on compact flash) or remote. The suffix .rc will be automatically appended to the filename when a rescue configuration file is saved. Trivial FTP (TFTP) is not supported for remote locations.

Default

no rescue location

Parameters

file-url

Specifies the URL or filename.

Values

local-url | remote-url

local-url

[cflash-id/][file-path] up to 200 characters, including cflash-id directory length of up to 99 characters each

remote-url

[{ftp://}login:pswd@ remote-locn/][file-path] up to 255 characters, directory length of up to 99 characters each

remote-locn

[hostname | ipv4-address | ipv6-address]

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

interface - 32 chars max, for link local addresses

cflash-id

cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

rescue filename

suffixed with .rc during the rescue file creation

Platforms

All

reserved

reserved

Syntax

reserved num-sessions

no reserved

Context

[Tree] (config>isa>nat-group>session-limits reserved)

Full Context

configure isa nat-group session-limits reserved

Description

This command configures the number of sessions per block that are reserved for prioritized sessions.

Default

no reserved

Parameters

num-sessions

Specifies the number of sessions reserved for prioritized sessions.

Values

0 to 6291456

Platforms

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

reserved

Syntax

reserved num-sessions

no reserved

Context

[Tree] (config>service>nat>up-nat-policy>session-limits reserved)

[Tree] (config>service>nat>firewall-policy>session-limits reserved)

[Tree] (config>service>nat>nat-policy>session-limits reserved)

Full Context

configure service nat up-nat-policy session-limits reserved

configure service nat firewall-policy session-limits reserved

configure service nat nat-policy session-limits reserved

Description

This command configures the number of sessions per block that will be reserved for prioritized sessions.

Default

no reserved

Parameters

num-sessions

Specifies the number of sessions reserved for prioritized sessions.

Values

0 to 65534

Platforms

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

  • configure service nat nat-policy session-limits reserved
  • configure service nat up-nat-policy session-limits reserved

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

  • configure service nat firewall-policy session-limits reserved

reserved

Syntax

reserved num-ports

no reserved

Context

[Tree] (config>service>nat>nat-policy>port-limits reserved)

[Tree] (config>service>nat>up-nat-policy>port-limits reserved)

Full Context

configure service nat nat-policy port-limits reserved

configure service nat up-nat-policy port-limits reserved

Description

This command configures the number of ports per block that will be reserved for prioritized sessions.

Default

no reserved

Parameters

num-ports

Specifies the number of ports to reserve for prioritized sessions.

Values

1 to 65534

Platforms

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

reserved-label-block

reserved-label-block

Syntax

[no] reserved-label-block name

Context

[Tree] (config>router>mpls-labels reserved-label-block)

Full Context

configure router mpls-labels reserved-label-block

Description

Commands in this context configure a block of labels from the dynamic range to be locally assigned for specific applications, such as Segment Routing adjacency SIDs. The reserved label block is not advertised by the IGP.

The no form of this command removes a reserved label block.

Parameters

name

Specifies the name of the reserved label block, up to 64 characters

Platforms

All

reserved-label-block

Syntax

reserved-label-block name

no reserved-label-block

Context

[Tree] (config>router>rib-api>mpls reserved-label-block)

Full Context

configure router rib-api mpls reserved-label-block

Description

This command specifies the reserved label block for use in all label-FIB entries programmed using the RIB-API gRPC service. The named reserved label block must already have been configured under config>router>mpls>mpls-labels.

The no form of this command removes the assignment of the reserved label block, causing all existing label-FIB entry programming, using the RIB-API gRPC service, to become invalid and unusable.

Default

no reserved-label-block

Parameters

name

Specifies the name of the reserved label block up to 64 characters in length.

Platforms

All

reserved-label-block

Syntax

reserved-label-block name

no reserved-label-block

Context

[Tree] (config>router>mpls>fwd-policies reserved-label-block)

Full Context

configure router mpls forwarding-policies reserved-label-block

Description

This command specifies the reserved label block to use for all MPLS forwarding policies. The named reserved label block must already have been configured under config>router>mpls-labels.

The no form of the command removes the assignment of the reserved label block.

Parameters

name

Specifies the name of the reserved label block, up to 64 characters.

Platforms

All

reserved-label-block

Syntax

reserved-label-block name

no reserved-label-block

Context

[Tree] (config>router>segment-routing>sr-policies reserved-label-block)

Full Context

configure router segment-routing sr-policies reserved-label-block

Description

This command associates a reserved label block with segment routing policies. The name must already exist. Reserved label blocks are configured under the config>router>mpls-labels hierarchy.

A locally-targeted segment routing policy (statically configured or BGP signaled) cannot be activated if its binding SID (BSID) is not an available label between the start-label and end-label of the referenced reserved label block.

The no form of this command removes any association of segment routing policies with a reserved label block.

Default

no reserved-label-block

Parameters

name

Specifies the name of a reserved-label-block that has already been configured, up to 64 characters.

Platforms

All

reserved-label-block

Syntax

[no] reserved-label-block name

Context

[Tree] (config>anysec reserved-label-block)

Full Context

configure anysec reserved-label-block

Description

This command assigns the label block that is reserved for ANYsec encryption SID under the configure router mpls-labels context. Without this reserved block, ANYsec cannot assign any encryption SIDs. The encryption SID uniquely identifies the encrypting node within a network and avoids double encryption scenarios. The encryption SID can be assigned per encryption group. However, all encryption groups can have the same encryption SID.

To save label space, Nokia recommends limiting the number of encryption SIDs within a network.

The no form of this command removes a reserved label block.

Parameters

name

Specifies the name of the reserved label block.

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

reserved-lbl-block

reserved-lbl-block

Syntax

reserved-lbl-block reserved-lbl-block

no reserved-lbl-block

Context

[Tree] (config>router>p2mp-sr-tree reserved-lbl-block)

Full Context

configure router p2mp-sr-tree reserved-lbl-block

Description

This command configures the reserved label block name for the P2MP SR tree. Before configuring for the P2MP SR tree, the reserved label block name must be configured on the root node of the P2MP policy in the config>router>mpls-labels context.

The no form of this command removes the reserved label block name for the P2MP SR tree.

Default

no reserved-lbl-block

Parameters

reserved-lbl-block

Specifies the value of the reserved label block name, up to 64 characters.

Platforms

All

reserved-non-shaper-queues

reserved-non-shaper-queues

Syntax

reserved-non-shaper-queues range

Context

[Tree] (config>qos>fp-resource-policy>aggregate-shapers reserved-non-shaper-queues)

Full Context

configure qos fp-resource-policy aggregate-shapers reserved-non-shaper-queues

Description

This command configures the number of egress queues which will not be used by hardware aggregate shapers.

Parameters

range

Specifies the number of queues which will not be used by hardware aggregate shapers

Values

2048 to 262144

Default

8192

Platforms

7750 SR-1, 7750 SR-s

reset-on-recoverable-error

reset-on-recoverable-error

Syntax

[no] reset-on-recoverable-error

Context

[Tree] (config>card reset-on-recoverable-error)

Full Context

configure card reset-on-recoverable-error

Description

This command configures the behavior of the card when a fatal memory parity error is detected on a Q-chip of the card. If reset-on-recoverable-error is enabled, the card is reset, regardless of the setting of the fail-on-error parameter.

The no form of this command specifies that the recovery action is taken instead of resetting the card.

Default

no reset-on-recoverable-error

Platforms

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

reset-on-recoverable-error

Syntax

[no] reset-on-recoverable-error

Context

[Tree] (config>card>mda reset-on-recoverable-error)

Full Context

configure card mda reset-on-recoverable-error

Description

This command configures the behavior of the MDA when a fatal memory parity error is detected on a Q-chip of the MDA. If reset-on-recoverable-error is enabled, the MDA is reset, regardless of the setting of the fail-on-error parameter.

The no form of this command specifies that the recovery action is taken instead of resetting the MDA.

Default

no reset-on-recoverable-error

Platforms

7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 7950 XRS

reset-on-recoverable-error

Syntax

[no] reset-on-recoverable-error

Context

[Tree] (config>card>xiom reset-on-recoverable-error)

Full Context

configure card xiom reset-on-recoverable-error

Description

This command configures the behavior of the XIOM when a fatal memory parity error is detected on a Q-chip of the XIOM. If reset-on-recoverable-error is enabled, the XIOM is reset, regardless of the setting of the fail-on-error parameter.

The no form of this command specifies that the recovery action is taken instead of resetting the XIOM.

Default

no reset-on-recoverable-error

Platforms

7750 SR-1s, 7750 SR-2s, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s

reset-policy-exclusive

reset-policy-exclusive

Syntax

reset-policy-exclusive

Context

[Tree] (admin reset-policy-exclusive)

Full Context

admin reset-policy-exclusive

Description

This command allows an authorized administrator to reset the exclusive policy editing lock. This will reset the lock flag and end the policy editing session in progress, discarding any policy edits.

Platforms

All

reset-query

reset-query

Syntax

[no] reset-query

Context

[Tree] (debug>router>rpki-session>packet reset-query)

Full Context

debug router rpki-session packet reset-query

Description

This command enables debugging for reset query RPKI packets.

The no form of this command disables debugging for reset query RPKI packets.

Platforms

All

reset-unknown-tcp

reset-unknown-tcp

Syntax

[no] reset-unknown-tcp

Context

[Tree] (config>service>nat>nat-policy reset-unknown-tcp)

[Tree] (config>service>nat>up-nat-policy reset-unknown-tcp)

Full Context

configure service nat nat-policy reset-unknown-tcp

configure service nat up-nat-policy reset-unknown-tcp

Description

This command enables the system to drop a TCP packet and generate a TCP reset, when a TCP packet without the SYN flag set is received by the NAT inside for an unknown flow.

The no form of this command disables sending the reset, but the packet is still dropped.

Default

no reset-unknown-tcp

Platforms

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

resignal-on-igp-event

resignal-on-igp-event

Syntax

[no] resignal-on-igp-event

Context

[Tree] (config>router>mpls>sr-te-resignal resignal-on-igp-event)

Full Context

configure router mpls sr-te-resignal resignal-on-igp-event

Description

This command introduces the ad-hoc resignaling of all SR-TE LSPs at the receipt of one or more IGP link down events in TE-DB. Once the re-optimization is triggered, the behavior is exactly the same as the timer based resignal or the delay option of the manual based resignal. MPLS forces the expiry of the resignal timer and asks TE-DB to re-evaluate the active paths of all SR-TE LSPs. The re-evaluation consists of updating the total IGP or TE metric of the current path, checking the validity of the hops and labels, and computing a new CSPF for each SR-TE LSP. MPLS programs the new path only if the total metric of the new computed path is different than the updated metric of the current path, or if one or more hops or labels of the current path are invalid. Otherwise, the current path is considered to be one of the most optimal ECMP paths and is not updated in data path.

Platforms

All

resignal-on-igp-overload

resignal-on-igp-overload

Syntax

[no] resignal-on-igp-overload

Context

[Tree] (config>router>mpls resignal-on-igp-overload)

Full Context

configure router mpls resignal-on-igp-overload

Description

This command enables the resignaling of all RSVP-TE LSPs at the receipt of the IS-IS overload bit in the TE-DB.

Once the re-optimization is triggered, the behavior is the same as the timer-based resignal or the delay option of the manual-based resignal. MPLS forces the expiry of the resignal timer and requests the TE-DB to compute a new CSPF for each RSVP-TE LSP active path.

This re-optimization effectively causes the immediate move of transit RSVP-TE LSP paths away from the IS-IS node in overload.

By default, MPLS re-optimizes, using the MBB procedure, the transit paths away from the node in an IS-IS overload state only at the time a manual or timer-based resignal is performed for the LSP paths. MPLS does not act immediately on the receipt of the IS-IS overload bit.

Note:

This command and the retry-on-overload command are mutually exclusive.

The no form of this command results in the MPLS not acting immediately to the request of the IS-IS overload bit.

Default

no resignal-on-overload

Platforms

All

resignal-on-igp-overload

Syntax

[no] resignal-on-igp-overload

Context

[Tree] (config>router>mpls>sr-te-resignal resignal-on-igp-overload)

Full Context

configure router mpls sr-te-resignal resignal-on-igp-overload

Description

This command enables the ad-hoc re-optimzation of the CSPF paths of all SR-TE LSPs when IS-IS receives an IS-IS overload bit advertisement from a remote router.

When this command is enabled on the router and an IGP overload bit is set in a Layer 1 or Layer 2 IS-IS LSP received from a remote router, MPLS performs an ad-hoc re-optimization of all the paths of all the SR-TE LSPs that have paths computed by the local CSPF. For each SR-TE LSP current path that transits the router in overload, the CSPF looks for a new path that avoids the router. For each SR-TE LSP current path that terminates on the router in overload, the CSPF checks if a better path exists. In both cases, if a new path is not found the system maintains the current path when operationally up.

The ad-hoc re-optimization triggers the timer-based re-optimization by forcing the resignal timer to expire. Therefore, the user must use the following command to configure the resignal timer for the SR-TE application.
configure router mpls sr-te-resignal resignal-timer

The no form of this command configures MPLS to not act immediately on an IS-IS overload bit from a remote router. MPLS will act on it at the next timer-based or manual re-optimization of the SR-TE LSPs.

Default

no resignal-on-igp-overload

Platforms

All

resignal-timer

resignal-timer

Syntax

resignal-timer minutes

no resignal-timer

Context

[Tree] (config>router>mpls resignal-timer)

Full Context

configure router mpls resignal-timer

Description

This command specifies the value for the LSP resignal timer. The resignal timer is the time, in minutes, the software waits before attempting to resignal the LSPs.

When the resignal timer expires, if the new computed path for an LSP has a better metric than the current recorded hop list, an attempt is made to resignal that LSP using the make-before-break mechanism. If the attempt to resignal an LSP fails, the LSP continues to use the existing path and a resignal will be attempted the next time the timer expires.

The no form of this command disables timer-based LSP resignaling.

Default

no resignal-timer

Parameters

minutes

Specifies the time the software waits before attempting to resignal the LSPs.

Values

30 to 10080

Platforms

All

resignal-timer

Syntax

resignal-timer minutes

no resignal-timer

Context

[Tree] (config>router>mpls>sr-te-resignal resignal-timer)

Full Context

configure router mpls sr-te-resignal resignal-timer

Description

This command specifies the value for the SR-TE LSP resignal timer when the path computation method is set to the local CSPF or the PCE.

The resignal timer is the time, in minutes, MPLS waits before attempting to re-optimize all paths of all SR-TE LSPs. The re-optimization is performed by the local CSPF or the PCE, depending on the value of the parameter path-computation-method.

When local CSPF is used and the resignal timer expires, MPLS provides the current path of the SR-TE LSP and TE-DB updates the total IGP or TE metric of the current path and checks the validity of the hops and labels. CSPF then computes a new path for each SR-TE LSP. MPLS programs the new path only if the total metric of the new computed path is different than the updated metric of the current path, or if one or more hops or labels of the current path are invalid. Otherwise, the current path is considered to be one of the most optimal ECMP paths and is not updated in data path.

The no form of this command disables timer-based LSP resignaling.

Default

no resignal-timer

Parameters

minutes

Specifies the time, in minutes, the software waits before attempting to resignal the SR-TE LSPs.

Values

30 to 10080

Platforms

All

resolution

resolution

Syntax

resolution {route-table | tunnel-table | fallback-tunnel-to-route-table}

Context

[Tree] (config>service>vprn>bgp-ipvpn>srv6 resolution)

[Tree] (config>router>bgp>srv6>family resolution)

[Tree] (config>service>vprn>bgp-evpn>srv6 resolution)

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

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

Full Context

configure service vprn bgp-ipvpn segment-routing-v6 resolution

configure router bgp segment-routing-v6 family resolution

configure service vprn bgp-evpn segment-routing-v6 resolution

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

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

Description

This command configures the resolution option for routes in the specified family.

The no form of the command reverts to the default.

Default

resolution route-table

Parameters

route-table

Keyword that specifies to resolve the route to the shortest-path SRv6 tunnel. If no such shortest-path tunnel is found, the resolution fails.

tunnel-table

Keyword that specifies to resolve the route directly to a tunnel in TTMv6. The system tries to find an SRv6 policy with a matching color and endpoint for BGP routes received with an SRv6 TLV and containing an SRv6 service SID in the IPv6 tunnel table. If none is found, the resolution fails.

fallback-tunnel-to-route-table

Keyword that specifies to first try resolving the route to a tunnel in the IPv6 tunnel table. If none is found in the IPv6 tunnel table, fall back to the shortest-path SRv6 resolution. If no such shortest-path tunnel is found in RTM, the resolution fails.

Platforms

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

resolution

Syntax

resolution {disabled | any | filter}

Context

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

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

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

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

Full Context

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

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

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

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

Description

This command configures the resolution mode in the automatic binding of a BGP-EVPN or BGP-IPVPN MPLS service to tunnels to MP-BGP peers.

Default

resolution disabled

Parameters

any

Enables the binding to any supported tunnel type in a BGP-EVPN or BGP-IPVPN MPLS context following TTM preference.

disabled

Disables the automatic binding of a BGP-EVPN or BGP-IPVPN MPLS service to tunnels to MP-BGP peers.

filter

Enables the binding to the subset of tunnel types configured the resolution-filter context.

Platforms

All

resolution

Syntax

resolution {any | disabled | filter}

Context

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

Full Context

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

Description

This command determines the resolution mode for the associated static route to a tunnel next hop.

Default

resolution any

Parameters

any

Allows the associated static route to be resolved to any active entry in the TTM, following the TTM preference order.

disabled

Disables the resolution of the associated static route to any active entry in the TTM. As a result, the static route can only be resolved via IP RTM resolution of the static route's next hop.

filter

Allows the associated static route to be resolved to active tunnels in the TTM using the resolution-filter restrictions.

Platforms

All

resolution

Syntax

resolution {any | filter | disabled}

Context

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

Full Context

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

Description

This command configures the resolution mode in the resolution of BGP label routes using tunnels to BGP peers.

Parameters

any

Enables the binding to any supported tunnel type in the BGP label route context following TTM preference.

filter

Enables the binding to the subset of tunnel types configured under resolution-filter.

disabled

Disables the resolution of BGP label routes using tunnels to BGP peers.

Platforms

All

resolution

Syntax

resolution {any | filter | disabled}

Context

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

Full Context

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

Description

This command configures the resolution mode in the resolution of BGP prefixes using tunnels to BGP peers.

Parameters

any

Enables the binding to any supported tunnel type in BGP shortcut context following TTM preference.

filter

Enables the binding to the subset of tunnel types configured under resolution-filter.

disabled

Disables the resolution of BGP prefixes using tunnels to BGP peers.

Platforms

All

resolution

Syntax

resolution {any | disabled | filter | match-family-ip}

Context

[Tree] (config>router>isis>igp-shortcut>tunnel-next-hop>family resolution)

Full Context

configure router isis igp-shortcut tunnel-next-hop family resolution

Description

This command configures resolution mode in the resolution of the IP prefix or SR tunnel family using IGP shortcuts.

Parameters

any

Enables the binding to any supported tunnel type following TTM preference.

disabled

Disables the resolution of the IP prefix or SR tunnel family using IGP shortcuts.

filter

Enables the binding to the subset of tunnel types configured under resolution-filter.

match-family-ip

Enables the resolution of the SR tunnel family to match that of the corresponding IP prefix family.

Platforms

All

resolution

Syntax

resolution {any | disabled | filter | match-family-ip}

Context

[Tree] (config>router>ospf>igp-shortcut>tunnel-next-hop>family resolution)

Full Context

configure router ospf igp-shortcut tunnel-next-hop family resolution

Description

This command configures resolution mode in the resolution of the IP prefix or SR tunnel family using IGP shortcuts.

Parameters

any

Enables the binding to any supported tunnel type following TTM preference.

disabled

Disables the resolution of the IP prefix or SR tunnel family using IGP shortcuts.

filter

Enables the binding to the subset of tunnel types configured under resolution-filter.

match-family-ip

Enables the resolution of the SR tunnel family to match that of the corresponding IP prefix family.

Platforms

All

resolution

Syntax

resolution {any | disabled | filter}

Context

[Tree] (config>router>ospf3>igp-shortcut>tunnel-next-hop>family resolution)

Full Context

configure router ospf3 igp-shortcut tunnel-next-hop family resolution

Description

This command configures resolution mode in the resolution of the IPv6 prefix using IGP shortcuts.

Parameters

any

Enables the binding to any supported tunnel type following TTM preference.

disabled

Disables the resolution of the IPv6 prefix using IGP shortcuts.

filter

Enables the binding to the subset of tunnel types configured under resolution-filter.

Platforms

All

resolution

Syntax

resolution {any | disabled | filter}

Context

[Tree] (config>service>vprn>auto-bind-tunnel resolution)

Full Context

configure service vprn auto-bind-tunnel resolution

Description

This command configures the resolution method for tunnel selection.

Default

resolution any

Parameters

any

Allows the associated static route to be resolved to any active entry in the TTM, following the TTM preference order.

disabled

Disables the associated static route to be resolved to any active entry in the TTM. As a result, the static route can only be resolved via IP RTM resolution of the static route's nexthop.

filter

Allows the associated static route to be resolved to active tunnels in the TTM using the resolution-filter restrictions.

Platforms

All

resolution

Syntax

resolution

Context

[Tree] (config>service>vprn>auto-bind-tunnel resolution)

Full Context

configure service vprn auto-bind-tunnel resolution

Description

Note: This command is no longer supported and will be removed in a future release.

Platforms

All

resolution-filter

resolution-filter

Syntax

resolution-filter

Context

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

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

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

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

Full Context

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

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

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

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

Description

Commands in this context configure the subset of tunnel types that can be used in the resolution of BGP-EVPN or BGP-IPVPN routes within the automatic binding of BGP-EVPN or BGP-IPVPN MPLS service to tunnels to MP-BGP peers.

The following tunnel types are supported in a BGP-EVPN or BGP-IPVPN MPLS context: BGP, LDP, RIB-API, RSVP, SR-ISIS, SR-OSPF, SR-policy, SR-TE, UDP, and MPLS forwarding policy.

The user must set resolution to filter to activate the list of tunnel-types configured under resolution-filter.

Note:

UDP tunnels are created through import policies with action create-udp-tunnel.

Platforms

All

resolution-filter

Syntax

resolution-filter

Context

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

Full Context

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

Description

This command creates the context to configure the tunnel next-hop resolution options.

If one or more tunnel filter criteria are specified, the static route nexthop is resolved to an available tunnel from one of those LSP types. The tunnel type is selected based on the TTM preference.

Platforms

All

resolution-filter

Syntax

resolution-filter

Context

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

Full Context

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

Description

Commands in this context set resolution filter types.

Platforms

All

resolution-filter

Syntax

resolution-filter [bgp] [ldp] [rsvp] [sr-isis] [sr-ospf] [sr-policy] [sr-te]

Context

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

Full Context

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

Description

This command configures the subset of tunnel types that can be used to resolve BGP unlabeled routes.

Parameters

bgp

Selects the BGP label route tunnel type.

ldp

Selects the LDP tunnel type.

rsvp

Selects the RSVP-TE tunnel type.

sr-isis

Selects the SR tunnel type programmed by an IS-IS instance in TTM.

sr-ospf

Selects the SR tunnel type programmed by an OSPF instance in TTM.

sr-policy

Selects the SR tunnel type programmed by an SR policy instance in TTM.

sr-te

Selects the SR tunnel type programmed by a TE instance in TTM.

Platforms

All

resolution-filter

Syntax

resolution-filter

Context

[Tree] (config>router>isis>igp-shortcut>tunnel-next-hop>family resolution-filter)

Full Context

configure router isis igp-shortcut tunnel-next-hop family resolution-filter

Description

Commands in this context configure the subset of tunnel types which can be used in the resolution of the IP prefix or SR tunnel family using IGP shortcuts.

Parameters

rsvp

Selects the RSVP-TE tunnel type.

sr-te

Selects the SR-TE tunnel type.

Platforms

All

resolution-filter

Syntax

resolution-filter

Context

[Tree] (config>router>ospf3>igp-shortcut>tunnel-next-hop>family resolution-filter)

[Tree] (config>router>ospf>igp-shortcut>tunnel-next-hop>family resolution-filter)

Full Context

configure router ospf3 igp-shortcut tunnel-next-hop family resolution-filter

configure router ospf igp-shortcut tunnel-next-hop family resolution-filter

Description

Commands in this context configure the subset of tunnel types that can be used in the resolution of the IP prefix or SR tunnel family using IGP shortcuts.

Platforms

All

resolution-filter

Syntax

resolution-filter

Context

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

Full Context

configure service vprn auto-bind-tunnel resolution-filter

Description

Note: This command is no longer supported and will be removed in a future release.

Platforms

All

resolve

resolve

Syntax

resolve minutes

Context

[Tree] (config>service>vpls>proxy-arp>dynamic resolve)

[Tree] (config>service>vpls>proxy-nd>dynamic resolve)

Full Context

configure service vpls proxy-arp dynamic resolve

configure service vpls proxy-nd dynamic resolve

Description

This command configures the frequency at which a resolve message is sent. The resolve message is an ARP-request or NS message flooded to all the non-EVPN endpoints in the service irrespective of the current status of the unknown-arp-request-flood-evpn or unknown-ns-flood-evpn commands.

Default

resolve 5

Parameters

minutes

Specifies the frequency in minutes at which the resolve message is issued.

Values

1 to 60

Default

5

Platforms

All

resolve-root-using

resolve-root-using

Syntax

resolve-root-using {ucast-rtm | mcast-rtm}

Context

[Tree] (config>router>ldp resolve-root-using)

Full Context

configure router ldp resolve-root-using

Description

By default, MLDP resolves the FEC using the unicast RTM. When this command is set to mcast-rtm, MLDP will resolve the FEC using the multicast route table. The multicast route table does not include any IGP shortcuts, unlike the unicast RTM. MLDP cannot resolve a FEC using an IGP shortcut, so if IGP shortcuts are used for unicast, enable multicast MLDP lookups.

If this command is set to mcast-rtm:

  • For FEC resolution using IGP, static or local, the ROOT in this FEC is resolved using the multicast RTM.

  • A FEC being resolved using BGP is recursive, so the FEC next-hop (ASBR/ABR) is resolved using the multicast RTM first and, if this fails, it is resolved using the unicast RTM. This next-hop needs to be recursively resolved again using IGP/Static-Route or Local, this second resolution (recursive resolution) uses the multicast RTM only.

  • In all cases, MLDP uses the unicast RTM to resolve the FEC and will not resolve the FEC if its next hop is resolved using an IGP shortcut.

Default

resolve-root-using ucast-rtm

Platforms

All

resolve-static

resolve-static

Syntax

[no] resolve-static

Context

[Tree] (config>router>policy-options>policy-statement>default-action resolve-static)

[Tree] (config>router>policy-options>policy-statement>entry>action resolve-static)

Full Context

configure router policy-options policy-statement default-action resolve-static

configure router policy-options policy-statement entry action resolve-static

Description

This command has an affect only in BGP route-table-import policies and applies only to BGP IPv4 and IPv6 routes created by importing static routes with indirect next-hops. When such a route matches a policy entry with this action, the BGP next-hop is the resolved next-hop of the static route.

The no form of this command reverts to the default behavior, which copies the indirect next-hop of the static route into the BGP next-hop without resolving it further.

Default

no resolve-static

Platforms

All

resolve-v6-prefix-over-shortcut

resolve-v6-prefix-over-shortcut

Syntax

[no] resolve-v6-prefix-over-shortcut

Context

[Tree] (config>router>ldp>targ-session resolve-v6-prefix-over-shortcut)

Full Context

configure router ldp targeted-session resolve-v6-prefix-over-shortcut

Description

This command allows an IPv6 prefix FEC to be resolved over an IGP shortcut.

The no form of this command disables the resolution.

Platforms

All

responder-url

responder-url

Syntax

responder-url url-string

no responder-url

Context

[Tree] (config>system>security>pki>ca-profile>ocsp responder-url)

Full Context

configure system security pki ca-profile ocsp responder-url

Description

This command specifies HTTP URL of the OCSP responder for the CA, this URL will only be used if there is no OCSP responder defined in the AIA extension of the certificate to be verified.

Default

no responder-url

Parameters

url-string

Specifies the HTTP URL of the OCSP responder

Platforms

All

response-signing-cert

response-signing-cert

Syntax

response-signing-cert filename

no response-signing-cert

Context

[Tree] (config>system>security>pki>ca-profile>cmp2 response-signing-cert)

Full Context

configure system security pki ca-profile cmp2 response-signing-cert

Description

This command specifies a imported certificate that is used to verify the CMP response message if they are protected by signature. If this command is not configured, then CA’s certificate will be used.

Default

no response-signing-cert

Parameters

filename

Specifies the filename of the imported certificate.

restart-backoff

restart-backoff

Syntax

restart-backoff initial-time seconds max-time seconds

no restart-backoff

Context

[Tree] (config>subscr-mgmt>pppoe-client-policy restart-backoff)

Full Context

configure subscriber-mgmt pppoe-client-policy restart-backoff

Description

This command configures backoff timer parameters that determine how often and how long the system will attempt to restart a PPPoE client after a failure. When a client first fails, the system immediately tries to re-establish connectivity. If this attempt is also unsuccessful, the system initiates a backoff timer and waits until it expires before attempting to restart the client again, to avoid flooding the BNG. The initial duration of the backoff timer is configured with the initial-time parameter. With each subsequent failure, the backoff timer is doubled until the configured max-time is reached.

The no form of this command reverts to the default.

Default

restart-backoff initial-time 30 max-time 600

Parameters

initial-time seconds

Specifies the initial backoff time to wait before attempting a client restart.

Values

10 to 3600

max-time seconds

Specifies the maximum time to attempt client restarts.

Values

10 to 3600

Platforms

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

restart-time

restart-time

Syntax

restart-time seconds

no restart-time

Context

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

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

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

Full Context

configure service vprn bgp graceful-restart restart-time

configure service vprn bgp group graceful-restart restart-time

configure service vprn bgp group neighbor graceful-restart restart-time

Description

This command sets the value of the restart-time that is advertised in the router’s graceful-restart capability. If this command is not configured, the default is 300.

Default

no restart-time

Parameters

seconds

Specifies the restart-time that is advertised in the router’s graceful-restart capability.

Values

0 to 4095 seconds

Default

300

Platforms

All

restart-time

Syntax

restart-time seconds

no restart-time

Context

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

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

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

Full Context

configure router bgp group neighbor graceful-restart restart-time

configure router bgp group graceful-restart restart-time

configure router bgp graceful-restart restart-time

Description

This command sets the value of the restart-time that is advertised in the router’s graceful-restart capability. If this command is not configured, the default is 300.

Default

no restart time

Parameters

seconds

Specifies the restart-time that is advertised in the router’s graceful-restart capability.

Values

0 to 4095 seconds

Default

config>router>bgp>graceful-restart: 120 seconds

config>router>bgp>group>graceful-restart: 300 seconds

config>router>bgp>group>neighbor>graceful-restart: 300 seconds

Platforms

All

restore-disconnected

restore-disconnected

Syntax

[no] restore-disconnected

Context

[Tree] (config>service>ies>sub-if>grp-if>wpp restore-disconnected)

[Tree] (config>service>vprn>sub-if>grp-if>wpp restore-disconnected)

Full Context

configure service ies subscriber-interface group-interface wpp restore-disconnected

configure service vprn subscriber-interface group-interface wpp restore-disconnected

Description

This command specifies that the initial profiles must be restored after a DHCP host has disconnected. The behavior that system will restore the initial-sla-profile, initial-sub-profile, or initial-app-profile when hosts disconnects instead of removing them.

The no form of this command specifies that the initial profiles will not be restored after a DHCP host has disconnected.

Default

restore-disconnected

Platforms

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

restore-disconnected

Syntax

restore-disconnected {restore | no-restore}

no restore-disconnected

Context

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host>wpp restore-disconnected)

Full Context

configure subscriber-mgmt local-user-db ipoe host wpp restore-disconnected

Description

This command specifies the behavior that system will restore the initial-sla-profile, initial-sub-profile, or initial-app-profile when hosts disconnects instead of removing them.

The no form of this command reverts to the default.

Parameters

restore

Specifies that the initial profiles must be restored after a DHCP host has disconnected.

no-restore

Specifies that the initial profiles will not be restored after a DHCP host has disconnected.

Platforms

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

restrict-protected-src

restrict-protected-src

Syntax

restrict-protected-src discard-frame

restrict-protected-src [alarm-only]

no restrict-protected-src

Context

[Tree] (config>service>vpls>sap restrict-protected-src)

[Tree] (config>service>pw-template restrict-protected-src)

[Tree] (config>service>vpls>spoke-sdp restrict-protected-src)

[Tree] (config>service>vpls>split-horizon-group restrict-protected-src)

[Tree] (config>service>vpls>mesh-sdp restrict-protected-src)

[Tree] (config>service>vpls>endpoint restrict-protected-src)

[Tree] (config>service>pw-template>split-horizon-group restrict-protected-src)

Full Context

configure service vpls sap restrict-protected-src

configure service pw-template restrict-protected-src

configure service vpls spoke-sdp restrict-protected-src

configure service vpls split-horizon-group restrict-protected-src

configure service vpls mesh-sdp restrict-protected-src

configure service vpls endpoint restrict-protected-src

configure service pw-template split-horizon-group restrict-protected-src

Description

This command indicates how the agent will handle relearn requests for protected MAC addresses, either manually added using the mac-protect command or automatically added using the auto-learn-mac-protect command. While enabled all packets entering the configured SAP, spoke SDP, mesh SDP, or any SAP that is part of the configured split horizon group (SHG) is verified not to contain a protected source MAC address. If the packet is found to contain such an address, the action taken depends on the parameter specified on the restrict-protected-src command, namely:

  • No parameter — The packet is discarded, an alarm is generated and the SAP, spoke SDP or mesh SDP is set operationally down. The SAP, spoke SDP or mesh SDP must be shut down and enabled (no shutdown) for this state to be cleared.

  • alarm-only — The packet is forwarded, an alarm is generated but the source MAC is not learned on the SAP, spoke SDP or mesh SDP.

  • discard-frame — The packet is discarded and an alarm generated. The frequency of alarm generation is fixed to be at most one alarm per MAC address per FP per 10 minutes in a given VPLS service. This parameter is only applicable to automatically protected MAC addresses.

When the restrict-protected-src is enabled on an SHG the action only applies to the associated SAPs (no action is taken by default for spoke SDPs in the SHG) and is displayed in the SAP show output as the oper state unless it is overridden by the configuration of restrict-protected-src on the SAP itself. To enable this function for spoke SDPs within a SHG, the restrict-protected-src must be enabled explicitly under the spoke SDP. If required, restrict-protected-src can also be enabled explicitly under specific SAPs within the SHG.

When this command is applied or removed, with either the alarm-only or discard-frame parameters, the MAC addresses are cleared from the related object.

The use of restrict-protected-src discard-frame is mutually exclusive with the configuration of manually protected MAC addresses within a given VPLS.

The alarm-only parameter is not supported on the 7750 SR-a, 7750 SR-1e/2e/3e, 7950 XRS, 7750 SR-1,or 7750 SR-1s/2s/7s/14s platforms.

The no form of the command reverts to the default.

Default

no restrict-protected-src

Parameters

alarm-only

Specifies that the packet is forwarded, an alarm is generated but the source MAC is not learned on the SAP, spoke SDP, or mesh SDP.

Default

no alarm-only

discard-frame

Specifies that the packet is discarded and an alarm generated. The frequency of alarm generation is fixed to be at most one alarm per MAC address per FP per 10 minutes within a given VPLS service.

Default

no discard-frame

Platforms

All

restrict-protected-src

Syntax

restrict-protected-src discard-frame

no restrict-protected-src

Context

[Tree] (config>service>vpls>pbb>backbone-vpls restrict-protected-src)

Full Context

configure service vpls pbb backbone-vpls restrict-protected-src

Description

This command indicates how the agent handles relearn requests for protected MAC addresses, either manually added using the mac-protect command or automatically added using the auto-learn-mac-protect command. While enabled, all packets entering the configured SAP, spoke SDP, mesh SDP, or any SAP that is part of the configured split horizon group (SHG) is verified not to contain a protected source MAC address. If the packet is found to contain such an address, the action taken depends on the parameter specified on the restrict-protected-src command, namely:

  • No parameter — The packet is discarded, an alarm is generated and the SAP, spoke SDP or mesh SDP will be set as operationally down. The SAP, spoke SDP or mesh SDP must be shutdown and enabled (no shutdown) for this state to be cleared.

  • discard-frame — The packet is discarded and an alarm generated. The frequency of alarm generation is fixed to be at most one alarm per MAC address per FP per 10 minutes in a specified VPLS service. This parameter is only applicable to automatically protected MAC addresses.

When the restrict-protected-src is enabled on an SHG, the action only applies to the associated SAPs (no action is taken by default for spoke-SDPs in the SHG) and is displayed in the SAP show output as the oper state unless it is overridden by the configuration of restrict-protected-src on the SAP itself. To enable this function for spoke SDPs within a SHG, the restrict-protected-src must be enabled explicitly under the spoke SDP. If required, restrict-protected-src can also be enabled explicitly under specific SAPs within the SHG.

When this command is applied or removed, with the discard-frame parameter, the MAC addresses are cleared from the related object.

The use of restrict-protected-src discard-frame is mutually exclusive with the configuration of manually protected MAC addresses within a specified VPLS.

Default

no restrict-protected-src

Parameters

discard-frame

Specifies that the packet is discarded and an alarm generated. The frequency of alarm generation is fixed to be at most one alarm per MAC address per FP per 10 minutes within a specified VPLS service

Platforms

All

restrict-protected-src

Syntax

restrict-protected-src discard-frame

no restrict-protected-src

Context

[Tree] (config>service>vpls>vxlan restrict-protected-src)

[Tree] (config>service>vpls>bgp-evpn>srv6 restrict-protected-src)

Full Context

configure service vpls vxlan restrict-protected-src

configure service vpls bgp-evpn segment-routing-v6 restrict-protected-src

Description

This command enables protected source MAC restrictions.

Platforms

All

  • configure service vpls vxlan restrict-protected-src

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

  • configure service vpls bgp-evpn segment-routing-v6 restrict-protected-src

restrict-unprotected-dst

restrict-unprotected-dst

Syntax

restrict-unprotected-dst

no restrict-unprotected-dst

Context

[Tree] (config>service>vpls restrict-unprotected-dst)

[Tree] (config>service>vpls>split-horizon-group restrict-unprotected-dst)

[Tree] (config>service>vpls>sap restrict-unprotected-dst)

[Tree] (config>service>pw-template>split-horizon-group restrict-unprotected-dst)

Full Context

configure service vpls restrict-unprotected-dst

configure service vpls split-horizon-group restrict-unprotected-dst

configure service vpls sap restrict-unprotected-dst

configure service pw-template split-horizon-group restrict-unprotected-dst

Description

This command indicates how the system will forward packets destined for an unprotected MAC address, either manually added using the mac-protect command or automatically added using the auto-learn-mac-protect command. While enabled all packets entering the configured SAP or SAPs within a split horizon group (but not spoke or mesh-SDPs) will be verified to contain a protected destination MAC address. If the packet is found to contain a non-protected destination MAC, it will be discarded. Detecting a non-protected destination MAC on the SAP will not cause the SAP to be placed in the operationally down state. No alarms are generated.

If the destination MAC address is unknown, even if the packet is entering a restricted SAP, with restrict-unprotected-dst enabled, it will be flooded.

Default

no restrict-unprotected-dst

Platforms

All

restricted-to-home

restricted-to-home

Syntax

[no] restricted-to-home

Context

[Tree] (config>system>security>user-template restricted-to-home)

[Tree] (config>system>security>user restricted-to-home)

Full Context

configure system security user-template restricted-to-home

configure system security user restricted-to-home

Description

This command denies the user from accessing files outside of their home directory. Files can be accessed locally by CLI file commands and output modifiers such as > (file redirect), or remotely via FTP and SCP.

When enabled, the system denies all configuration save operations (such as admin save) via any management interface (such as CLI and NETCONF) unless save-when-restricted is enabled.

When restricted-to-home is configured, file access is denied unless the home-directory is configured and the directory is created by an administrator.

The no form of this command permits the user to access all files on the system.

Default

no restricted-to-home

Platforms

All

results

results

Syntax

results file-url

no results

Context

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

Full Context

configure system script-control script-policy results

Description

This command is used to specify the location where the system writes the output of an event script’s execution.

The no form of the command removes the file location from the configuration. Scripts will not execute if there is no result location defined.

Default

no results

Parameters

file-url

Specifies the location to send CLI output from script runs. The file-url is a location, directory, and filename prefix to which a data and timestamp suffix is added when the results files are created during a script run, as follows:

file-url_YYYYMMDD-hhmmss.uuuuuu.out

where:

YYYYMMDD — date

hhmmss — hours, minutes, and seconds

uuuuuu — microseconds (padded to 6 characters with leading zeros)

Values

local-url | remote-url

local-url — [cflash-id/] [file-path] 167 chars max, including cflash-idfile-path 166 chars max

remote url — [{ftp:// | tftp://}login:password@remote-location/][file-path] 255 characters max directory length 99 characters max each

remote-location — [hostname | ipv4-address | ipv6-address]

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 interface — 32 characters max, for link local addresses

cflash-id — cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

Platforms

All

resv

resv

Syntax

resv [detail]

no resv

Context

[Tree] (debug>router>rsvp>event resv)

Full Context

debug router rsvp event resv

Description

This command debugs RSVP reservation events.

The no form of the command disables the debugging.

Parameters

detail

Displays detailed information about RSVP reservation events.

Platforms

All

resv

Syntax

resv [detail]

no resv

Context

[Tree] (debug>router>rsvp>packet resv)

Full Context

debug router rsvp packet resv

Description

This command enables debugging for RSVP resv packets.

The no form of the command disables the debugging.

Parameters

detail

Displays detailed information about RSVP Resv events.

Platforms

All

resv-cbs

resv-cbs

Syntax

resv-cbs percent-or-default amber-alarm-action step percent max percent

resv-cbs percent-or-default

no resv-cbs

Context

[Tree] (config>port>access>egress>pool resv-cbs)

[Tree] (config>port>network>egress>pool resv-cbs)

[Tree] (config>port>access>ingress>pool resv-cbs)

[Tree] (config>port>access>egress>channel>pool resv-cbs)

Full Context

configure port access egress pool resv-cbs

configure port network egress pool resv-cbs

configure port access ingress pool resv-cbs

configure port access egress channel pool resv-cbs

Description

This command defines the percentage or specifies the sum of the pool buffers that are used as a guideline for CBS calculations for access and network ingress and egress queues. Two actions are accomplished by this command:

  • A reference point is established to compare the currently assigned (provisioned) total CBS with the amount the buffer pool considers to be reserved. Based on the percentage of the pool reserved that has been provisioned, the over provisioning factor can be calculated.

  • The size of the shared portion of the buffer pool is indirectly established. The shared size is important to the calculation of the instantaneous-shared-buffer-utilization and the average-shared-buffer-utilization variables used in Random Early Detection (RED) per packet slope plotting.

It is important to note that this command does not actually set aside buffers within the buffer pool for CBS reservation. The CBS value per queue only determines the point at which enqueuing packets are subject to a RED slope. Oversubscription of CBS could result in a queue operating within its CBS size and still not able to enqueue a packet due to unavailable buffers. The resv-cbs parameter can be changed at any time.

If the total pool size is 10 Mb and the resv-cbs set to 5, the 'reserved size’ is 500 kb.

The no form of this command clears all the adaptive configurations. There cannot be any adaptive sizing enabled for default resv-cbs.

Default

resv-cbs 30

Parameters

percent-or-default

Specifies the pool buffer size percentage.

Values

0 to 100, default

amber-alarm-action step percent

Specifies the percentage step-size for the reserved CBS size of the pool. When using the default value, the adaptive CBS sizing is disabled. To enable adaptive CBS sizing, step percent must be set to non-default value along with the max parameter. When reserved CBS is default adaptive CBS sizing cannot be enabled. The reserved CBS (Committed Burst Size) defines the amount of buffer space within the pool that is not considered shared.

Values

1 to 100

Default

0

max percent

Specifies the maximum percentage for the reserved CBS size of the pool. When using the default value, the adaptive CBS sizing is disabled. To enable adaptive CBS sizing, max value must be set to non-default value along with the step percent. When reserved CBS is default adaptive CBS sizing cannot be enabled. The reserved CBS (Committed Burst Size) defines the amount of buffer space within the pool that is not considered shared. Max reserved CBS must not be more than the reserved CBS.

Values

1 to 100

Default

0

Platforms

All

resv-cbs

Syntax

resv-cbs min percentage max percentage

no resv-cbs

Context

[Tree] (config>card>fp>egress>wred-queue-control resv-cbs)

Full Context

configure card fp egress wred-queue-control resv-cbs

Description

This command defines the amount of buffers within the WRED mega-pool that will be set aside for WRED queues operating within their configured CBS thresholds. Note that the min percentage and max percentage parameters must be set to the same value. The forwarding plane protects against WRED queue buffer starvation by setting aside a portion of the buffers within the WRED mega-pool. The WRED queue CBS threshold defines when a WRED queue requests buffers from reserved portion of the WRED mega-pool and when it starts requesting buffers from the shared portion of the mega-pool. With proper oversubscription provisioning, this prevents a seldom active queue from being denied a buffer from the mega-pool when the shared portion of the mega-pool is congested.

The WRED mega-slope reserve CBS size is controlled in the same manner as the overall sizing of the WRED mega-pool. A min and max parameter is provided to scope the range that the reserved portion based on percentages of the WRED mega-pool current size.

The no form of this command immediately restores the default min and max percentage values for sizing the WRED mega-pool CBS reserve.

Default

resv-cbs min 25.00 max 25.00

Parameters

min percentage

Specifies that the required keyword defines the minimum percentage of the WRED mega-pool buffers that will be applied to the CBS reserve. The value given for percentage must be less than or equal to the value given for the max percentage. Percentages are defined with an accuracy of hundredths of a percent in the nn.nn format (15.65 = 15.65%).

Values

0.00 to 99.99

Default

25.00

max percentage

Specifies that the required keyword defines the maximum percentage of the WRED mega-pool buffers that may be applied to the CBS reserve. The value given for percentage must be greater than or equal to the value given for the min percentage. Percentages are defined with an accuracy of hundredths of a percent in the nn.nn format (15.65 = 15.65%).

Values

0.01 to 99.99

Default

25.00

Platforms

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

resv-cbs

Syntax

resv-cbs percent-or-default

resv-cbs percent-or-default amber-alarm-action step percent max percent

no resv-cbs

Context

[Tree] (config>card>fp>ingress>network>pool resv-cbs)

Full Context

configure card fp ingress network pool resv-cbs

Description

This command defines the percentage or specifies the sum of the pool buffers that are used as a guideline for CBS calculations for access and network ingress and egress queues. Two actions are accomplished by this command:

  • A reference point is established to compare the currently assigned (provisioned) total CBS with the amount the buffer pool considers to be reserved. Based on the percentage of the pool reserved that has been provisioned, the over provisioning factor can be calculated.

  • The size of the shared portion of the buffer pool is indirectly established. The shared size is important to the calculation of the instantaneous-shared-buffer-utilization and the average-shared-buffer-utilization variables used in Random Early Detection (RED) per packet slope plotting.

It is important to note that this command does not actually set aside buffers within the buffer pool for CBS reservation. The CBS value per queue only determines the point at which enqueuing packets are subject to a RED slope. Oversubscription of CBS could result in a queue operating within its CBS size and still not able to enqueue a packet due to unavailable buffers. The resv-cbs parameter can be changed at any time.

If the total pool size is 10 Mb and the resv-cbs set to 5, the 'reserved size’ is 500 kb.

The no form of this command clears all the adaptive configurations. There cannot be any adaptive sizing enabled for default resv-cbs.

Default

resv-cbs 30

Parameters

percent-or-default

Specifies the pool buffer size percentage.

Values

0 to 100, default

amber-alarm-action step percent

Specifies the percentage step-size for the reserved CBS size of the pool. When using the default value, the adaptive CBS sizing is disabled. To enable adaptive CBS sizing, step percent must be set to non-default value along with the max parameter. When reserved CBS is default adaptive CBS sizing cannot be enabled. The reserved CBS defines the amount of buffer space within the pool that is not considered shared.

Values

1 to 100

Default

0

max percent

Specifies the maximum percentage for the reserved CBS size of the pool. When using the default value, the adaptive CBS sizing is disabled. To enable adaptive CBS sizing, max value must be set to non-default value along with the step percent. When reserved CBS is default adaptive CBS sizing cannot be enabled. The reserved CBS defines the amount of buffer space within the pool that is not considered shared. Max reserved CBS must not be more than the reserved CBS.

Values

1 to 100

Default

0

Platforms

All

resv-cbs

Syntax

resv-cbs percent-or-default

no resv-cbs

Context

[Tree] (config>isa>aa-grp>qos>egress>to-subscriber>pool resv-cbs)

[Tree] (config>isa>aa-grp>qos>egress>from-subscriber>pool resv-cbs)

Full Context

configure isa application-assurance-group qos egress to-subscriber pool resv-cbs

configure isa application-assurance-group qos egress from-subscriber pool resv-cbs

Description

This command defines the percentage or specifies the sum of the pool buffers that are used as a guideline for CBS calculations for access and network ingress and egress queues. Two actions are accomplished by this command.

  • A reference point is established to compare the currently assigned (provisioned) total CBS with the amount the buffer pool considers to be reserved. Based on the percentage of the pool reserved that has been provisioned, the over provisioning factor can be calculated.

  • The size of the shared portion of the buffer pool is indirectly established. The shared size is important to the calculation of the instantaneous-shared-buffer-utilization and the average-shared-buffer-utilization variables used in Random Early Detection (RED) per packet slope plotting.

This command does not actually set aside buffers within the buffer pool for CBS reservation. The CBS value per queue only determines the point at which enqueuing packets are subject to a RED slope. Oversubscription of CBS could result in a queue operating within its CBS size and still not able to enqueue a packet due to unavailable buffers. The resv-cbs parameter can be changed at any time.

If the total pool size is 10 MB and the resv-cbs set to 5, the 'reserved size’ is 500 KB.

The no form of this command restores the default value of 30.

Default

resv-cbs default

Parameters

percent-or-default

Specifies the pool buffer size percentage.

Values

0 to 100, default

Platforms

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

resv-ret

resv-ret

Syntax

resv-ret resv-ret

Context

[Tree] (config>isa>video-group resv-ret)

Full Context

configure isa video-group resv-ret

Description

This command provides a mechanism to reserve an explicit amount of egress bandwidth, in Mb/s, for RET for all the ISAs within a video group. If the amount of egress bandwidth is less than the reserved amount, FCC requests are discarded and only RET requests processed. The bandwidth is dynamically adjusted per ISA within the video group if an ISA becomes operational/non-operational within the group.

Default

resv-ret 0

Parameters

resv-ret

Specifies the egress bandwidth in Mb/s.

Values

0 to 10500

Platforms

7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

resverr

resverr

Syntax

resverr [detail]

no resverr

Context

[Tree] (debug>router>rsvp>packet resverr)

Full Context

debug router rsvp packet resverr

Description

This command debugs ResvErr packets.

The no form of the command disables the debugging.

Parameters

detail

Displays detailed information about ResvErr packets.

Platforms

All

resvtear

resvtear

Syntax

resvtear [detail]

no resvtear

Context

[Tree] (debug>router>rsvp>packet resvtear)

Full Context

debug router rsvp packet resvtear

Description

This command debugs ResvTear packets.

The no form of the command disables the debugging.

Parameters

detail

Displays detailed information about ResvTear packets.

Platforms

All

ret

ret

Syntax

ret percent

Context

[Tree] (config>isa>video-group>watermark>session ret)

[Tree] (config>isa>video-group>watermark>bandwidth ret)

Full Context

configure isa video-group watermark session ret

configure isa video-group watermark bandwidth ret

Description

This command sets the watermark to trigger the SNMP trap if the RET bandwidth or session exceeds the configured percentage. The bandwidth is the available egress bandwidth of the ISA. The SNMP trap is cleared when the consumption is lowered by 10%. For example, if the system resource of the bandwidth available is 10 Gb/s and the watermark is configured to be 90%, the SNMP trap is raised as the bandwidth exceeds 9 Gb/s (90% of 10 Gb/s). The SNMP trap is cleared when the bandwidth drops below 8.1 Gb/s (10% of 9 Gb/s = 0.9 Gb/s, and 9 Gb/s - 0.9 Gb/s = 8.1 Gb/s). The default value of the watermark is set at 90% of the system resources for both bandwidth and session.

Default

ret 90

Parameters

percent

Specifies the percentage of the system resources per ISA.

Values

1 to 99

Platforms

7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

ret-session-timeout

ret-session-timeout

Syntax

ret-session-timeout seconds

no ret-session-timeout

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if ret-session-timeout)

Full Context

configure mcast-management multicast-info-policy video-policy video-interface ret-session-timeout

Description

By default, the video ISA will wait for 5 minutes before closing the RTCP session from the subscriber. The RTCP session can be adjusted from 5 second to 5 minutes. The timeout is applicable to both RET and FCC RTCP sessions.

The no form of the command reverts to the default.

Default

ret-session-timeout 300

Parameters

seconds

Specifies the RET session timeout, in seconds.

Values

5 to 300

Platforms

7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

retail-service-id

retail-service-id

Syntax

retail-service-id service-id

no retail-service-id

Context

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host retail-service-id)

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host retail-service-id)

Full Context

configure subscriber-mgmt local-user-db ipoe host retail-service-id

configure subscriber-mgmt local-user-db ppp host retail-service-id

Description

This command indicates the service ID of the retailer VPRN service to which this session belongs. If the value of this object is non-zero, the session belongs to a retailer VPRN.

The no form of this command removes the service ID from the configuration.

Parameters

service-id

Specifies the retailer service ID or name.

Values

service-id:

1 to 2147483647

service-name:

up to 64 characters

Platforms

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

retail-svc-id

retail-svc-id

Syntax

retail-svc-id service-id

retail-svc-id

Context

[Tree] (config>service>vprn>sub-if>grp-if>sap>static-host retail-svc-id)

[Tree] (config>service>ies>sub-if>grp-if>sap>static-host retail-svc-id)

Full Context

configure service vprn subscriber-interface group-interface sap static-host retail-svc-id

configure service ies subscriber-interface group-interface sap static-host retail-svc-id

Description

This command specifies the service id of the retailer IES/VPRN service to which the static IPv6 host belongs. A corresponding retailer subscriber interface must exist in the specified service.

The no form of this command reverts to the default.

Parameters

service-id

Specifies the retailer service ID or retailer service name.

Values

service-id: 1 to 2148007978

svc-name: A string up to 64 characters

Platforms

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

retail-svc-id

Syntax

retail-svc-id service-id

no retail-svc-id

Context

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

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

Full Context

configure service vprn subscriber-interface group-interface wlan-gw vlan-tag-ranges range retail-svc-id

configure service ies subscriber-interface group-interface wlan-gw vlan-tag-ranges range retail-svc-id

Description

This command configures the retailer service.

Parameters

service-id

Specifies the identifier of the retail service.

Values

1 to 2147483650

svc-name: up to 64 characters

Platforms

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

retransmit-interval

retransmit-interval

Syntax

retransmit-interval seconds

no retransmit-interval

Context

[Tree] (config>service>vpls>sap>spb retransmit-interval)

[Tree] (config>service>vpls>spoke-sdp>spb retransmit-interval)

Full Context

configure service vpls sap spb retransmit-interval

configure service vpls spoke-sdp spb retransmit-interval

Description

This command configures the minimum time between LSP PDU retransmissions on a point-to-point interface. This command is valid only for interfaces on control B-VPLS.

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

Default

retransmit-interval 5

Parameters

seconds

The interval in seconds that SPB IS-IS LSPs can be sent on the interface.

Values

1 to 65535

Platforms

All

retransmit-interval

Syntax

retransmit-interval seconds

no retransmit-interval

Context

[Tree] (config>service>vpls>sap>spb retransmit-interval)

[Tree] (config>service>vpls>spoke-sdp>spb retransmit-interval)

Full Context

configure service vpls sap spb retransmit-interval

configure service vpls spoke-sdp spb retransmit-interval

Description

This command configures the minimum time between LSP PDU retransmissions on a point-to-point interface.

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

Default

retransmit-interval 100

Parameters

seconds

Specifies the interval in seconds that IS-IS LSPs can be sent on the interface

Values

1 to 65535

Platforms

All

retransmit-interval

Syntax

retransmit-interval seconds

no retransmit-interval

Context

[Tree] (config>service>vprn>isis>if retransmit-interval)

Full Context

configure service vprn isis interface retransmit-interval

Description

This command configures the minimum time between LSP PDU retransmissions on a point-to-point interface.

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

Default

retransmit-interval 5

Parameters

seconds

Specifies the interval in seconds that IS-IS LSPs can be sent on the interface

1 to 65535.

Platforms

All

retransmit-interval

Syntax

retransmit-interval seconds

no retransmit-interval

Context

[Tree] (config>service>vprn>ospf>area>virtual-link retransmit-interval)

[Tree] (config>service>vprn>ospf3>area>virtual-link retransmit-interval)

[Tree] (config>service>vprn>ospf>area>sham-link retransmit-interval)

[Tree] (config>service>vprn>ospf3>area>if retransmit-interval)

[Tree] (config>service>vprn>ospf>area>if retransmit-interval)

Full Context

configure service vprn ospf area virtual-link retransmit-interval

configure service vprn ospf3 area virtual-link retransmit-interval

configure service vprn ospf area sham-link retransmit-interval

configure service vprn ospf3 area interface retransmit-interval

configure service vprn ospf area interface retransmit-interval

Description

This command specifies the length of time, in seconds, that OSPF will wait before retransmitting an unacknowledged link state advertisement (LSA) to an OSPF neighbor.

The value should be longer than the expected round trip delay between any two routers on the attached network. Once the retransmit interval expires and no acknowledgment is received, the LSA is retransmitted.

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

Default

retransmit-interval 5

Parameters

seconds

The retransmit interval in seconds expressed as a decimal integer.

Values

1 to 3600

Platforms

All

retransmit-interval

Syntax

retransmit-interval seconds

no retransmit-interval

Context

[Tree] (config>router>isis>interface retransmit-interval)

Full Context

configure router isis interface retransmit-interval

Description

This command configures the minimum time between LSP PDU retransmissions on a point-to-point interface.

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

Default

retransmit-interval 5

Parameters

seconds

Specifies the interval, in seconds, that IS-IS LSPs can be sent on the interface.

Values

1 to 65535

Platforms

All

retransmit-interval

Syntax

retransmit-interval seconds

no retransmit-interval

Context

[Tree] (config>router>ospf3>area>virtual-link retransmit-interval)

[Tree] (config>router>ospf>area>interface retransmit-interval)

[Tree] (config>router>ospf3>area>interface retransmit-interval)

[Tree] (config>router>ospf>area>virtual-link retransmit-interval)

Full Context

configure router ospf3 area virtual-link retransmit-interval

configure router ospf area interface retransmit-interval

configure router ospf3 area interface retransmit-interval

configure router ospf area virtual-link retransmit-interval

Description

This command specifies the length of time, in seconds, that OSPF will wait before retransmitting an unacknowledged link state advertisement (LSA) to an OSPF neighbor.

The value should be longer than the expected round trip delay between any two routers on the attached network. After the retransmit-interval expires and no acknowledgment has been received, the LSA will be retransmitted.

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

Default

retransmit-interval 5

Parameters

seconds

Specifies the retransmit interval in seconds expressed as a decimal integer.

Values

1 to 1800

Platforms

All

retransmit-time

retransmit-time

Syntax

retransmit-time milli-seconds

no retransmit-time

Context

[Tree] (config>subscr-mgmt>rtr-adv-plcy retransmit-time)

[Tree] (config>service>ies>sub-if>ipv6>rtr-adv retransmit-time)

[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-adv retransmit-time)

[Tree] (config>router>router-advert>if retransmit-time)

[Tree] (config>service>vprn>sub-if>grp-if>ipv6>rtr-adv retransmit-time)

[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv retransmit-time)

[Tree] (config>service>vprn>router-advert>if retransmit-time)

Full Context

configure subscriber-mgmt router-advertisement-policy retransmit-time

configure service ies subscriber-interface ipv6 router-advertisements retransmit-time

configure service ies subscriber-interface group-interface ipv6 router-advertisements retransmit-time

configure router router-advertisement interface retransmit-time

configure service vprn subscriber-interface group-interface ipv6 router-advertisements retransmit-time

configure service vprn subscriber-interface ipv6 router-advertisements retransmit-time

configure service vprn router-advertisement interface retransmit-time

Description

This command configures the value to be placed in the retransmit timer field in router advertisements sent from this interface.

The no form of this command reverts to the default.

Default

retransmit-time 0

Parameters

milli-seconds

Specifies the retransmit time, in milli-seconds, for advertisement from this group-interface.

Values

0 to 1800000

Platforms

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

  • configure service ies subscriber-interface group-interface ipv6 router-advertisements retransmit-time
  • configure service ies subscriber-interface ipv6 router-advertisements retransmit-time
  • configure subscriber-mgmt router-advertisement-policy retransmit-time
  • configure service vprn subscriber-interface group-interface ipv6 router-advertisements retransmit-time
  • configure service vprn subscriber-interface ipv6 router-advertisements retransmit-time

All

  • configure service vprn router-advertisement interface retransmit-time
  • configure router router-advertisement interface retransmit-time

retries

retries

Syntax

retries number

no retries

Context

[Tree] (config>subscr-mgmt>pfcp-association>heartbeat retries)

Full Context

configure subscriber-mgmt pfcp-association heartbeat retries

Description

This command configures the number of times the same Heartbeat Request message is sent before the PFCP path to the peer is considered down.

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

Default

retries 4

Parameters

number

Specifies the number of times the same Heartbeat Request message is sent. This value should be identical on both the BNG UPF and CPF. For information about the BNG CUPS CPF configuration, refer to the CMG BNG CUPS Control Plane Function Guide and the 7750 SR MG and CMG CLI Reference Guide.

Values

1 to 15

Platforms

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

retries

Syntax

retries number

no retries

Context

[Tree] (config>subscr-mgmt>pfcp-association>tx retries)

Full Context

configure subscriber-mgmt pfcp-association tx retries

Description

This command configures the number of times a message is retried before the message is considered lost. This retry number is also known as N1.

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

Default

retries 3

Parameters

number

Specifies the number of times a message is retried.

This value should be identical on both the BNG UPF and CPF. For information about the BNG CUPS CPF configuration, refer to the CMG BNG CUPS Control Plane Function Guide and the 7750 SR MG and CMG CLI Reference Guide.

Values

1 to 7

Platforms

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

retries

Syntax

retries count

no retries

Context

[Tree] (config>system>grpc>tcp-keepalive retries)

Full Context

configure system grpc tcp-keepalive retries

Description

This command configures the number of TCP keepalive probes sent by the router that must be unacknowledged before the connection is closed.

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

Default

retries 4

Parameters

count

Specifies the number of missed keep-alives before the TCP connection is declared down.

Values

3 to 100

Default

4

Platforms

All

retries

Syntax

retries count

no retries

Context

[Tree] (config>system>telemetry>destination-group>tcp-keepalive retries)

[Tree] (config>system>grpc-tunnel>destination-group>tcp-keepalive retries)

Full Context

configure system telemetry destination-group tcp-keepalive retries

configure system grpc-tunnel destination-group tcp-keepalive retries

Description

This command configures the number of missed TCP keepalive probes before the TCP connection is closed and attempts are made to reach other destinations within the same destination group.

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

Default

retries 4

Parameters

count

Specifies the number of missed keep-alives before the TCP connection is declared down.

Values

3 to 100

Default

4

Platforms

All

retry

retry

Syntax

retry count

Context

[Tree] (config>aaa>l2tp-acct-plcy>radius-acct-server retry)

Full Context

configure aaa l2tp-accounting-policy radius-accounting-server retry

Description

This command configures the number of times the router attempts to contact the RADIUS server for authentication.

Note:

The retry count includes the first attempt.

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

Default

retry 3 (the initial attempt as well as two retried attempts)

Parameters

count

Specifies the retry count.

Values

1 to 10

Platforms

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

retry

Syntax

retry count

Context

[Tree] (config>app-assure>rad-acct-plcy>server retry)

Full Context

configure application-assurance radius-accounting-policy radius-accounting-server retry

Description

This command configures the number of times the router attempts to contact the RADIUS accounting server if a response to the initial message is not received.

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

Default

retry 3

Parameters

count

Specifies the retry count.

Values

1 to 10

Platforms

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

retry

Syntax

retry count

no retry

Context

[Tree] (config>subscr-mgmt>auth-plcy>radius-auth-server retry)

[Tree] (config>subscr-mgmt>acct-plcy>server retry)

Full Context

configure subscriber-mgmt authentication-policy radius-authentication-server retry

configure subscriber-mgmt radius-accounting-policy radius-accounting-server retry

Description

This command configures the number of times the router attempts to contact the RADIUS server for authentication or accounting, if not successful the first time.

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

Default

retry 3

Parameters

count

Specifies the retry count.

Values

1 to 10

Platforms

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

retry

Syntax

retry count

no retry

Context

[Tree] (config>aaa>radius-srv-plcy>servers retry)

Full Context

configure aaa radius-server-policy servers retry

Description

This command configures the number of times the router attempts to contact the RADIUS server, if not successful the first time.

The no form of this command reverts to the default.

Default

retry 3

Parameters

count

Specifies the number of times a signaling request message is transmitted towards the same peer.

Values

1 to 256

Platforms

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

retry

Syntax

retry minutes

no retry

Context

[Tree] (config>service>vpls>bgp-evpn>mac-duplication retry)

Full Context

configure service vpls bgp-evpn mac-duplication retry

Description

Specifies the timer after which the MAC in hold-down state is automatically flushed and the mac-duplication process starts again. This value is expected to be equal to two times or more than that of window.

If no retry is configured, this implies that, when mac-duplication is detected, MAC updates for that MAC will be held down till the user intervenes or a network event (that flushes the MAC) occurs.

Default

retry 9

Parameters

minutes

Specifies the BGP EVPN MAC duplication retry in minutes.

Values

2 to 60

Platforms

All

retry

Syntax

retry count

no retry

Context

[Tree] (config>service>vprn>aaa>remote-servers>radius retry)

Full Context

configure service vprn aaa remote-servers radius retry

Description

This command configures the number of times the router attempts to contact the RADIUS server for authentication if there are problems communicating with the server.

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

Default

retry 3

Parameters

count

Specifies the retry count.

Values

1 to 10

Platforms

All

retry

Syntax

retry count

no retry

Context

[Tree] (config>system>file-trans-prof retry)

Full Context

configure system file-transmission-profile retry

Description

This command specifies the number of retries on transport protocol level.

When the virtual router does not receive any data from a server (e.g., FTP or HTTP server) after the configured timeout seconds, the router may repeat the request to the server. The number of retries specifies the maximum number of repeated requests.

The no form of this command disables the retry.

Default

no retry

Parameters

count

Specifies the number of retries.

Values

1 to 256

Platforms

All

retry

Syntax

retry count

Context

[Tree] (config>aaa>isa-radius-plcy>servers retry)

Full Context

configure aaa isa-radius-policy servers retry

Description

This command configures the number of times the router attempts to contact the RADIUS server for authentication, if not successful the first time.

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

Default

retry 3

Parameters

count

Specifies the retry count.

Values

1 to 10

Platforms

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

retry

Syntax

retry count

no retry

Context

[Tree] (config>system>security>radius retry)

[Tree] (config>system>security>dot1x>radius-plcy retry)

Full Context

configure system security radius retry

configure system security dot1x radius-plcy retry

Description

This command configures the number of times the router attempts to contact the RADIUS server for authentication if there are problems communicating with the server.

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

Default

retry 3

Parameters

count

Specifies the retry count.

Values

1 to 10

Platforms

All

retry

Syntax

retry count

no retry

Context

[Tree] (config>system>security>ldap retry)

Full Context

configure system security ldap retry

Description

This command configures the number of retries for the SR OS in its attempt to reach the current LDAP server before attempting the next server.

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

Default

retry 3

Parameters

count

Specifies the number of retransmissions.

Values

1 to 10

Default

3

Platforms

All

retry-count

retry-count

Syntax

retry-count [count]

no retry-count

Context

[Tree] (config>subscr-mgmt>shcv-policy>periodic retry-count)

Full Context

configure subscriber-mgmt shcv-policy periodic retry-count

Description

This command configures the number of retransmissions.

The no form of this command reverts to the default.

Default

retry-count 1 — For trigger-type ip-conflict, host-limit-exceeded and mobility

retry-count 10 — For trigger-type inactivity and MAC learning

Parameters

count

Specifies the number of retransmissions in periodic connectivity verification.

Values

2 to 29

Platforms

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

retry-count

Syntax

retry-count [count]

no retry-count

Context

[Tree] (config>subscr-mgmt>shcv-policy>trigger retry-count)

Full Context

configure subscriber-mgmt shcv-policy trigger retry-count

Description

This command configures the number of retransmissions in periodic connectivity verification.

The no form of this command reverts to the default.

Default

retry-count 1

Parameters

count

Specifies the number of retransmissions in periodic connectivity verification.

Values

1 to 29

Platforms

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

retry-count

Syntax

retry-count retry-count

no retry-count

Context

[Tree] (config>service>epipe>spoke-sdp-fec retry-count)

Full Context

configure service epipe spoke-sdp-fec retry-count

Description

This optional command specifies the number of attempts software should make to reestablish the spoke SDP after it has failed. After each successful attempt, the counter is reset to zero.

When the specified number is reached, no more attempts are made and the spoke-sdp is put into the shutdown state.

Use the no shutdown command to bring up the path after the retry limit is exceeded.

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

Default

retry-count 30

Parameters

retry-count

The maximum number of retries before putting the spoke-sdp into the shutdown state.

Values

10 to 10000

Platforms

All

retry-count

Syntax

retry-count retry-count

no retry-count

Context

[Tree] (config>test-oam>ldp-treetrace>path-discovery retry-count)

[Tree] (config>test-oam>ldp-treetrace>path-probing retry-count)

Full Context

configure test-oam ldp-treetrace path-discovery retry-count

configure test-oam ldp-treetrace path-probing retry-count

Description

In the path discovery phase of the LDP tree trace feature, this command configures the number of retransmissions of an LSP trace message to discover the path of an LDP FEC when no response is received within the timeout parameter.

In the path-probing phase of the LDP tree trace, this command configures the number of retransmissions of an LSP ping message to probe the path of an LDP FEC when no response is received within the timeout parameter.

The no form of this command resets the retry count to its default value.

Default

no retry-count

Parameters

retry-count

Specifies the maximum number of consecutive time outs allowed before failing a path probe (ping).

Platforms

All

retry-count

Syntax

retry-count [count]

no retry-count

Context

[Tree] (config>service>pw-routing retry-count)

Full Context

configure service pw-routing retry-count

Description

This optional command specifies the number of attempts software should make to re-establish the spoke SDP after it has failed. After each successful attempt, the counter is reset to zero.

When the specified number is reached, no more attempts are made and the spoke SDP is put into the shutdown state.

Use the no shutdown command to bring up the path after the retry limit is exceeded.

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

Default

no retry-count

Parameters

count

Specifies the maximum number of retries before putting the spoke SDP into the shutdown state.

Values

10 to 10000

Platforms

All

retry-interval

retry-interval

Syntax

retry-interval min minimum max maximum

no retry-interval

Context

[Tree] (config>aaa>route-downloader retry-interval)

Full Context

configure aaa route-downloader retry-interval

Description

This command sets the duration, in minutes, of the retry interval. The retry interval is the interval meant for the system to retry sending an Access Request message after the previous one was unanswered (not with an access reject but rather just a RADIUS failure or ICMP port unreachable). This timer is actually an exponential backoff timer that starts at min and is capped at max minutes.

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

Default

retry-interval min 10 max 20

Parameters

min minimum

Specifies the duration, in minutes, of the retry interval. This duration grows exponentially after each sequential failure.

Values

1 to 1440

max maximum

Specifies the maximum duration, in minutes, of the retry interval.

Values

1 to 1440

Platforms

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

retry-interval

Syntax

retry-interval milliseconds

no retry-interval

Context

[Tree] (config>router>wpp>portals>portal retry-interval)

[Tree] (config>service>vprn>wpp>portals>portal retry-interval)

Full Context

configure router wpp portals portal retry-interval

configure service vprn wpp portals portal retry-interval

Description

This command configures the time interval between two consecutive retransmissions

The no form of this command reverts to the default.

Default

retry-interval 2000

Parameters

milliseconds

Specifies the time interval between two consecutive retransmissions.

Values

10 to 2000

Platforms

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

retry-interval

Syntax

retry-interval seconds

no retry-interval

Context

[Tree] (config>system>security>pki>ca-prof>auto-crl-update retry-interval)

Full Context

configure system security pki ca-profile auto-crl-update retry-interval

Description

This command specifies the interval, in seconds, that the system waits before retrying the configured url-entry list when schedule-type is next-update-based and none of the URLs return a qualified CRL.

The no form of this command causes the system to retry immediately without waiting.

Default

retry-interval 3600

Parameters

seconds

Specifies an interval, in seconds, before retrying to update the CRL.

Values

1 to 31622400

Platforms

All

retry-interval

Syntax

retry-interval seconds

Context

[Tree] (config>system>security>pki>cert-upd-prof retry-interval)

Full Context

configure system security pki certificate-update-profile retry-interval

Description

This command configures the retry interval after the update fails.

Default

retry-interval 3600

Parameters

seconds

Specifies a retry interval, in seconds, after a failed update.

Values

60 to 36000

Platforms

All

retry-limit

retry-limit

Syntax

retry-limit number

no retry-limit

Context

[Tree] (config>router>mpls>lsp retry-limit)

[Tree] (config>router>mpls>lsp-template retry-limit)

Full Context

configure router mpls lsp retry-limit

configure router mpls lsp-template retry-limit

Description

This optional command specifies the number of attempts software should make to re-establish the LSP after it has failed LSP. After each successful attempt, the counter is reset to zero.

When the specified number is reached, no more attempts are made and the LSP path is put into the shutdown state.

Use the config router mpls lsp lsp-name no shutdown command to bring up the path after the retry-limit is exceeded.

For P2MP LSP that are created based on the LSP template, all S2Ls must attempt to retry-limit before the client application is informed of failure.

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

Default

retry-limit 0 (no limit, retries forever)

Parameters

number

Specifies the number of times software will attempt to re-establish the LSP after it has failed. Allowed values are integers in the range of 0 to 10000.

Values

0 to 10000

Platforms

All

retry-on-igp-overload

retry-on-igp-overload

Syntax

[no] retry-on-igp-overload

Context

[Tree] (config>router>mpls retry-on-igp-overload)

Full Context

configure router mpls retry-on-igp-overload

Description

This command allows for the global configuration of the handling in the ingress LER of the LSP paths which transit an LSR that advertised the IS-IS overload bit.

By default, MPLS re-optimizes using make-before-break (MBB) the transit paths away from the node in an IS-IS overload state only at the time a manual or timer-based re-signal is performed for the LSP paths. MPLS will not act immediately on the receipt of the IS-IS overload bit.

When this command is enabled, MPLS in the ingress LER immediately tears down and re-signals all LSP paths away from a transit LSR node which advertised the IS-IS overload bit.

LSP paths that terminate on the node that advertised the IS-IS overload bit are not acted on whether this command is enabled or disabled.

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

Platforms

All

retry-timeout

retry-timeout

Syntax

retry-timeout timer

no retry-timeout

Context

[Tree] (config>port>ethernet>dwl retry-timeout)

Full Context

configure port ethernet down-when-looped retry-timeout

Description

This command configures the minimum wait time before re-enabling port after loop detection.

Default

no retry-timeout

Parameters

timer

Specifies the minimum wait time before re-enabling port after loop detection.

Values

0, 10 to 160

Platforms

All

retry-timeout

Syntax

retry-timeout timeout

no retry-timeout

Context

[Tree] (config>service>template>vpls-template>mac-move retry-timeout)

[Tree] (config>service>vpls>mac-move retry-timeout)

Full Context

configure service template vpls-template mac-move retry-timeout

configure service vpls mac-move retry-timeout

Description

This indicates the time in seconds to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled.

It is recommended that the retry-timeout value is larger or equal to 5s * cumulative factor of the highest priority port so that the sequential order of port blocking will not be disturbed by re-initializing lower priority ports.

A zero value indicates that the SAP will not be automatically re-enabled after being disabled. If, after the SAP is re-enabled it is disabled again, the retry timeout is increased with the provisioned retry timeout in order to avoid thrashing. For example, when retry-timeout is set to 15, it increments (15,30,45,60...).

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

Default

retry-timeout 10 (when mac-move is enabled)

Parameters

timeout

Specifies the time, in seconds, to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled.

Values

0 to 120

Platforms

All

retry-timer

retry-timer

Syntax

retry-timer retry-timer

no retry-timer

Context

[Tree] (config>service>epipe>spoke-sdp-fec retry-timer)

Full Context

configure service epipe spoke-sdp-fec retry-timer

Description

This command specifies a retry-timer for the spoke SDP. This is a configurable exponential back-off timer that determines the interval between retries to reestablish a spoke SDP if it fails and a label withdraw message is received with the status code "AII unreachable”.

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

Default

retry-timer 30

Parameters

retry-timer

The initial retry-timer value in seconds.

Values

10 to 480

Platforms

All

retry-timer

Syntax

retry-timer seconds

no retry-timer

Context

[Tree] (config>router>mpls>lsp retry-timer)

[Tree] (config>router>mpls>lsp-template retry-timer)

Full Context

configure router mpls lsp retry-timer

configure router mpls lsp-template retry-timer

Description

This command configures the time (in s), for LSP re-establishment attempts after it has failed. The retry time is jittered to +/- 25% of its nominal value.

For P2MP LSP created based on LSP template, all S2Ls must attempt to retry-limit before client application is informed of failure.

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

Default

retry-timer 30

Parameters

seconds

Specifies the amount of time (in s), between attempts to re-establish the LSP after it has failed. Allowed values are integers in the range of 1 to 600.

Values

1 to 600

Platforms

All

retry-timer

Syntax

retry-timer secs

no retry-timer

Context

[Tree] (config>service>pw-routing retry-timer)

Full Context

configure service pw-routing retry-timer

Description

This command configures a retry-timer for the spoke-SDP. This is a configurable exponential back-off timer that determines the interval between retries to re-establish a spoke-SDP if it fails and a label withdraw message is received with the status code "AII unreachable”.

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

Default

no retry-timer

Parameters

secs

Specifies initial retry-timer value in seconds.

Values

10 to 480

Platforms

All

return-path

return-path

Syntax

return-path

Context

[Tree] (config>test-oam>link-meas>template>twl return-path)

Full Context

configure test-oam link-measurement measurement-template twamp-light return-path

Description

Commands in this context configure the return-path TLV for the test packet.

Platforms

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

return-path-bfd-sid

return-path-bfd-sid

Syntax

return-path-bfd-sid ipv6-address

no return-path-bfd-sid

Context

[Tree] (conf>router>segment-routing>sr-policies>policy>srv6 return-path-bfd-sid)

Full Context

configure router segment-routing sr-policies static-policy segment-routing-v6 return-path-bfd-sid

Description

This command configures the Seamless Bidirectional Forwarding Detection (S-BFD) session to echo mode and pushes an additional SRv6 SID in the SRH on S-BFD packets only.

The command applies to the initiator of the S-BFD sessions. The return path SID refers to a binding SID on a SRv6 policy configured on the far-end router. Instead of being routed through the IGP path, the S-BFD packet returns to the initiator through this SRv6 return path.

The no form of this command disables the controlled return-path SID and echo mode for S-BFD. If the command is deleted, the S-BFD session returns to asynchronous mode and the initiator node does not push a return-path SID. Any S-BFD packets for this SRv6 policy that the terminating router receives are sent back using a routed return path.

Parameters

ipv6-address

Specifies the IPv6 address.

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

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

  • x: [0 to FFFF]H

  • d: [0 to 255]D

Platforms

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

return-path-label

return-path-label

Syntax

return-path-label label-value

no return-path-label

Context

[Tree] (config>router>mpls>lsp>bfd return-path-label)

[Tree] (config>router>mpls>lsp>primary>bfd return-path-label)

[Tree] (config>router>segment-routing>main-plcy return-path-label)

[Tree] (config>router>mpls>lsp>sec>bfd return-path-label)

[Tree] (config>router>mpls>lsp-template>bfd return-path-label)

Full Context

configure router mpls lsp bfd return-path-label

configure router mpls lsp primary bfd return-path-label

configure router segment-routing maintenance-policy return-path-label

configure router mpls lsp secondary bfd return-path-label

configure router mpls lsp-template bfd return-path-label

Description

This command configures the Seamless Bidirectional Forwarding Detection (S-BFD) session to echo mode and adds an additional MPLS label, referring to an MPLS-labeled reply path for the S-BFD packet, to the bottom of the label stack for the S-BFD packet.

The command applies to the initiator of the S-BFD sessions. The return-path label may be a binding SID for an SR policy or other MPLS path configured on the reflector router. Instead of being routed through the IGP path, the S-BFD packet returns to the initiator through this MPLS return path.

The no form of this command disables the controlled return-path label and echo mode for S-BFD. S-BFD returns to asynchronous mode and the initiator node does not push a return-path label. Any S-BFD packets for this LSP or path that the reflector receives are sent back using a routed return path.

Default

no return-path-label

Parameters

label-value

Specifies the label value.

Values

32 to 1048512

Platforms

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

  • configure router mpls lsp-template bfd return-path-label
  • configure router mpls lsp secondary bfd return-path-label
  • configure router mpls lsp primary bfd return-path-label
  • configure router mpls lsp bfd return-path-label

All

  • configure router segment-routing maintenance-policy return-path-label

reuse

reuse

Syntax

reuse integer

no reuse

Context

[Tree] (config>router>policy-options>damping reuse)

Full Context

configure router policy-options damping reuse

Description

This command configures the reuse parameter for the route damping profile.

When the Figure of Merit (FoM) value falls below the reuse threshold, the route is once again considered valid and can be reused or included in route advertisements.

The no form of this command removes the reuse parameter from the damping profile.

Default

no reuse

Parameters

integer

Specifies the reuse value expressed as a decimal integer.

Values

1 to 20000

Platforms

All

reuse-ext-ip

reuse-ext-ip

Syntax

[no] reuse-ext-ip

Context

[Tree] (config>service>nat>pcp-server-policy reuse-ext-ip)

Full Context

configure service nat pcp-server-policy reuse-ext-ip

Description

This command enables the system to reuse the external IP address assigned to a subscriber when the requested well-known port or external IP mapping is not available.

The no form of this command causes a request for a well-known port to be allocated exactly as requested but on a different external IP address from the one that the subscriber is already using. This occurs if the requested well-known port is already allocated to another subscriber which is sharing the same external IP address. The existing external IP address is initially allocated to the subscriber by the virtue of initial traffic flow.

Default

no reuse-ext-ip

Platforms

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

reverse-path

reverse-path

Syntax

[no] reverse-path

Context

[Tree] (config>router>mpls>mpls-tp>transit-path reverse-path)

Full Context

configure router mpls mpls-tp transit-path reverse-path

Description

This command enables the reverse path of an MPLS-TP reverse path to be created or edited.

The reverse path must be created after the forward path.

The no form of this command removes the reverse path. The reverse path must be removed before the forward path.

Default

no reverse-path

Platforms

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

revert

revert

Syntax

revert {latest-rb| checkpoint-id | rescue} [now]

Context

[Tree] (admin>rollback revert)

Full Context

admin rollback revert

Description

This command initiates a configuration rollback revert operation that will return the configuration state of the node to a previously saved checkpoint. The rollback revert minimizes impacts to running services. There are no impacts in areas of configuration that did not change since the checkpoint. Configuration parameters that changed (or items on which changed configuration have dependencies) are first removed (revert to default) and the previous values are then restored (can be briefly service impacting in changed areas).

Parameters

latest-rb

Specifies the most recently created rollback checkpoint (corresponds to the file-url.rb rollback checkpoint file).

checkpoint-id

Specifies the configuration to return to (which rollback checkpoint file to use). Checkpoint-id of 1 corresponds to the file-url.rb.1 rollback checkpoint file. The higher the id, the older the checkpoint. Max is the highest rollback checkpoint supported or configured.

Values

1 to 9

rescue

Specifies to revert to the rescue checkpoint.

now

Forces a rollback revert without any interactive confirmations (assumes 'y’ for any confirmations that would have occurred).

Platforms

All

revert

Syntax

[no] revert

Context

[Tree] (config>system>sync-if-timing revert)

Full Context

configure system sync-if-timing revert

Description

This command allows the clock to revert to a higher priority reference if the current reference goes offline or becomes unstable. When the failed reference becomes operational, it is eligible for selection. When the mode is non-revertive, a failed clock source is not selected again.

Default

no revert

Platforms

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

revert-members

revert-members

Syntax

revert-members [1..8]

no revert-members

Context

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

Full Context

configure service vprn isis link-group level revert-members

Description

This command sets the threshold for the minimum number of operational links to return the associated link group to its normal operating state and remove the associated offsets to the IS-IS metrics. If the number of operational links is equal to or greater than the configured revert-members threshold, the configured offsets are removed.

The no form of this command reverts the threshold back to the default, which is equal to the oper-members threshold value.

Default

no revert-members oper-members

Parameters

1..8

Specifies the number of revert members.

Values

1 to 8

Platforms

All

revert-members

Syntax

revert-members [1..8]

no revert-members

Context

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

Full Context

configure router isis link-group level revert-members

Description

This command sets the threshold for the minimum number of operational links to return the associated link group to its normal operating state and remove the associated offsets to the IS-IS metrics. If the number of operational links is equal to or greater than the configured revert-member threshold then the configured offsets are removed.

The no form of this command reverts the threshold back to the default which is equal to the oper-member threshold value.

Default

no revert-members oper-members

Parameters

1..8

Specifies the threshold for revertive members.

Values

1 to 8

Platforms

All

revert-time

revert-time

Syntax

revert-time minutes

no revert-time

Context

[Tree] (config>port>aps revert-time)

Full Context

configure port aps revert-time

Description

This command configures the revert-time timer to determine how long to wait before switching back to the working circuit after that circuit has been restored into service.

A change in the minutes value takes effect upon the next initiation of the wait to restore (WTR) timer. It does not modify the length of a WTR timer that has already been started. The WTR timer of a non-revertive switch can be assumed to be infinite.

The no form of this command restores the default (non-revertive mode).

Default

The default is to not revert back unless the protect circuit fails or there is an operator intervention.

Parameters

minutes

Specifies the time, in minutes, to wait before reverting back to the original working circuit after it has been restored into service.

Values

0 to 60 minutes

Default

5

Platforms

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

revert-time

Syntax

revert-time time

no revert-time

Context

[Tree] (config>eth-tunnel revert-time)

Full Context

configure eth-tunnel revert-time

Description

This command configure how long to wait before switching back to the primary path after it has been restored to Ethernet tunnel.

The no form of this command disables the revert behavior, effectively setting the revert time to zero.

Default

no revert-time

Parameters

time

Specifies the re-activation delay, in seconds, for the primary path.

Values

1 to 720

Platforms

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

revert-time

Syntax

revert-time [revert-time | infinite]

no revert-time

Context

[Tree] (config>service>ipipe>endpoint revert-time)

[Tree] (config>service>cpipe>endpoint revert-time)

[Tree] (config>service>epipe>endpoint revert-time)

Full Context

configure service ipipe endpoint revert-time

configure service cpipe endpoint revert-time

configure service epipe endpoint revert-time

Description

This command configures the time to wait before reverting back to the primary spoke SDP defined on this service endpoint, after having failed over to a backup spoke SDP.

Parameters

revert-time

Specifies the time, in seconds, to wait before reverting to the primary SDP.

Values

0 to 600

Default

0

infinite

Causes the endpoint to be non-revertive.

Platforms

All

  • configure service epipe endpoint revert-time
  • configure service ipipe endpoint revert-time

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

  • configure service cpipe endpoint revert-time

revert-time

Syntax

revert-time revert-time | infinite

no revert-time

Context

[Tree] (config>service>vpls>endpoint revert-time)

Full Context

configure service vpls endpoint revert-time

Description

This command configures the time to wait before reverting to primary spoke-SDP.

In a regular endpoint the revert-time setting affects just the pseudowire defined as primary (precedence 0). For a failure of the primary pseudowire followed by restoration the revert-timer is started. After it expires the primary pseudowire takes the active role in the endpoint. This behavior does not apply for the case when both pseudowires are defined as secondary. For example, if the active secondary pseudowire fails and is restored it will stay in standby until a configuration change or a force command occurs.

Parameters

revert-time

Specifies the time to wait, in seconds, before reverting back to the primary spoke-SDP defined on this service endpoint, after having failed over to a backup spoke-SDP

Values

0 to 600

infinite

Specifying this keyword makes endpoint non-revertive

Platforms

All

revert-time

Syntax

revert-time {revert-time | infinite}

no revert-time

Context

[Tree] (config>mirror>mirror-dest>endpoint revert-time)

Full Context

configure mirror mirror-dest endpoint revert-time

Description

This command configures the time to wait before reverting to the primary spoke SDP. This command has an effect only when used in conjunction with an endpoint which contains a SDP of type 'primary’. It is ignored and has no effect in all other cases. The revert-timer is the delay in seconds the system waits before it switches the path of the mirror service from an active secondary SDP in the endpoint into the endpoint primary SDP after the latter comes back up.

The no form of this command resets the timer to the default value of 0. This means that the mirror-service path is switched back to the endpoint primary sdp immediately after it comes back up.

Parameters

revert-time

Specifies a delay, in seconds, the system waits before it switches the path of the mirror service from an active secondary SDP in the endpoint into the endpoint primary SDP after the latter comes back up.

Values

0 to 600

infinite

Forces the mirror or LI service path to never revert to the primary SDP as long as the currently active secondary SDP is UP.

Platforms

All

revert-time

Syntax

revert-time {revert-time | infinite}

no revert-time

Context

[Tree] (config>service>sdp>mixed-lsp-mode revert-time)

Full Context

configure service sdp mixed-lsp-mode revert-time

Description

This command configures the delay period the SDP must wait before it reverts to a higher priority LSP type when one becomes available.

The no form of the command resets the timer to the default value of 0. This means the SDP reverts immediately to a higher priority LSP type when one becomes available.

Default

no revert-time

Parameters

revert-time

Specifies the delay period, in seconds, that the SDP must wait before it reverts to a higher priority LSP type when one becomes available. A value of zero means the SDP reverts immediately to a higher priority LSP type when one becomes available.

Values

0 to 600

infinite

This keyword forces the SDP to never revert to another higher priority LSP type unless the currently active LSP type is down.

Platforms

All

revert-time

Syntax

revert-time time

no revert-time

Context

[Tree] (config>eth-ring revert-time)

Full Context

configure eth-ring revert-time

Description

This command configures the revert time for an Eth-Ring. It ranges from 60 seconds to 720 second by 1 second intervals.

The no form of this command means non-revertive mode and revert time is essentially 0, and the revert timers are not set.

Default

revert-time 300

Parameters

time

Specifies the guard-time, in seconds.

Values

60 to 720

Platforms

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

revert-timer

revert-timer

Syntax

revert-timer timer-value

no revert-timer

Context

[Tree] (config>router>mpls>lsp revert-timer)

Full Context

configure router mpls lsp revert-timer

Description

This command configures a revert timer on an LSP. The timer starts when the LSP primary path recovers from a failure. The LSP reverts from a secondary path to the primary path when the timer expires, or when the secondary path fails.

The no form of this command cancels any currently outstanding revert timer. If the LSP is up when a no revert-timer is issued, the LSP will revert to the primary path. Otherwise the LSP reverts when the primary path is restored.

Default

no revert-timer

Parameters

timer-value

Specifies the amount of time, in one minute increments, between attempts to re-establish the LSP after it has failed.

Values

1 to 4320

Platforms

All

revert-timer

Syntax

revert-timer seconds

no revert-timer

Context

[Tree] (config>router>mpls>fwd-policies>fwd-policy revert-timer)

Full Context

configure router mpls forwarding-policies forwarding-policy revert-timer

Description

This command configures the revert timer in an MPLS forwarding policy.

When the primary direct or indirect next hop is restored and is added back into the routing table, CPM waits for an amount of time equal to the user-programmed revert timer before activating it and updating the data path. However, if the backup direct or indirect next hop fails while the timer is running, CPM activates it and updates the data path immediately.

A value of 0 disables the revert timer; meaning the policy reverts immediately.

The no form of this command removes the revert timer from the MPLS forwarding policy.

Default

revert-timer 0

Parameters

seconds

Specifies the revert-timer value, in number of seconds.

Values

1 to 600

Platforms

All

revert-timer

Syntax

revert-timer revert-timer

no revert-timer

Context

[Tree] (config>router>segment-routing>maintenance-policy revert-timer)

Full Context

configure router segment-routing maintenance-policy revert-timer

Description

This command configures the revert timer for SR Policy candidate paths.

The revert timer is started when the primary path (for example, the best preference programmed candidate path) recovers (for example, after the number of S-BFD sessions that are up is ≥ threshold and the hold-down-timer has expired) and switches back when the timer expires.

The no form of this command removes the revert timer from the SR policy.

Default

no revert-timer

Parameters

revert-timer

Specifies the revert timer, in minutes.

Values

1 to 4320

Platforms

All

revertive

revertive

Syntax

[no] revertive

Context

[Tree] (config>router>mpls>mpls-tp>protection-template revertive)

Full Context

configure router mpls mpls-tp protection-template revertive

Description

This command configured revertive behavior for MPLS-TP linear protection. The protect-tp-path MEP must be in the shutdown state for of the MPLS-TP LSPs referencing this protection template in order to change the revertive parameter.

Default

revertive

Platforms

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

revertive

Syntax

[no] revertive

Context

[Tree] (config>redundancy>multi-chassis>ipsec-domain revertive)

Full Context

configure redundancy multi-chassis ipsec-domain revertive

Description

This command configures whether to allow a revertive activity state after a designated active state recovers from an ineligibility event. The revertive function allows a router in an N:M domain to automatically take over as the active router in the domain, when it becomes eligible to do so.

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

Default

no revertive

Platforms

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

revertive-timer

revertive-timer

Syntax

revertive-timer sec

no revertive-timer

Context

[Tree] (config>service>vprn>mvpn>pt>selective>umh-rm>group>source revertive-timer)

[Tree] (config>service>vprn>mvpn>pt>inclusive>umh-rm revertive-timer)

Full Context

configure service vprn mvpn provider-tunnel selective umh-rate-monitoring group source revertive-timer

configure service vprn mvpn provider-tunnel inclusive umh-rate-monitoring revertive-timer

Description

This command configures the timer value (in seconds) after which to revert to the primary UMH after traffic is restored. This value must account for the traffic flapping from the primary UMH. If there is traffic flapping, the timer resets and starts over.

The no form of the command means that there is no revertive behavior.

Default

no revertive-timer

Parameters

sec

Specifies the timer value (in seconds).

Values

1 to 3600

Platforms

All

revocation-check

revocation-check

Syntax

revocation-check {crl | crl-optional}

Context

[Tree] (config>system>security>pki>ca-profile revocation-check)

Full Context

configure system security pki ca-profile revocation-check

Description

This command specifies the revocation method system used to check the revocation status of certificate issued by the CA, the default value is crl, which will use CRL. But if it is crl-optional, then it means when the user disables the ca-profile, then the system will try to load the configured CRL (specified by the crl-file command). However, if the system fails to load it for following reasons, then the system still brings the ca-profile oper-up, but leaves the CRL as non-exist.

  • CRL file does not exist

  • CRL is not properly encoded - maybe due to interrupted file transfer

  • CRL does not match cert

  • Wrong CRL version

  • CRL expired

If the system needs to use the CRL of a specific ca-profile to check the revocation status of an end-entity cert, and the CRL is non-existent due to the above reasons, then the system will treat it as being unable to get an answer from CRL and fall back to the next status-verify method or default-result.

If the system needs to check the revocation of a CA cert in cert chain, and if the CRL is non-existent due to the above reasons, then the system will skip checking the revocation status of the CA cert. For example, if CA1 is issued by CA2, if CA2’s revocation-check is crl-optional and the CA2’s CRL is non-existent, then the system will not check CA1 cert’s revocation status and consider it as "good”.

Note:

Users must shutdown the ca-profile to change the revocation-check configuration.

Default

revocation-check crl

Parameters

crl

Specifies to use the configured CRL.

crl-optional

Specifies that the CRL is optional.

Platforms

All

revoke-key

revoke-key

Syntax

revoke-key card cpm-slot serial-number cpm-serial-number confirmation-code code

Context

[Tree] (admin>system>security>secure-boot revoke-key)

Full Context

admin system security secure-boot revoke-key

Description

This command revokes secure boot keys.

Parameters

cpm-slot

Specifies the CPM slot.

Values

A,B

cpm-serial-number

Specifies the CPM serial number, up to 256 characters.

code

Specifies the signed software confirmation code, up to 32 characters.

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-s, 7950 XRS-20e

rib-api

rib-api

Syntax

[no] rib-api

Context

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

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

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

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

Full Context

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

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

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

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

Description

This command selects the RIB-API tunnel type.

This command enables tunnels programmed using the RibApi gRPC service to be used in resolving the next hops of routes imported into the EVPN service.

The no form of this command disables tunnels programmed using the RibApi gRPC service from being used in resolving the next hops.

Default

no rib-api

Platforms

All

rib-api

Syntax

rib-api

Context

[Tree] (config>router rib-api)

Full Context

configure router rib-api

Description

Commands in this context configure parameters related to the RIB-API gRPC service.

Platforms

All

rib-api

Syntax

[no] rib-api

Context

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

Full Context

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

Description

This command enables tunnels programmed using the RibApi gRPC service for use in resolving the indirect next hops of statically-configured IPv4 and IPv6 routes.

Platforms

All

rib-api

Syntax

[no] rib-api

Context

[Tree] (debug>router rib-api)

Full Context

debug router rib-api

Description

This command enables debugging for RIB-API protocol entities.

Platforms

All

rib-api

Syntax

rib-api

Context

[Tree] (config>system>grpc rib-api)

Full Context

configure system grpc rib-api

Description

Commands in this context control the RibAPI gRPC service.

Platforms

All

rib-api

Syntax

[no] rib-api

Context

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

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

Full Context

configure router bgp next-hop-resolution shortcut-tunnel family resolution-filter rib-api

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

Description

This command enables tunnels programmed using the RibApi gRPC service for use in resolving the next hops of label-IPv4 or label-IPv6 routes.

Platforms

All

rib-api

Syntax

rib-api

Context

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

Full Context

configure service vprn auto-bind-tunnel resolution-filter rib-api

Description

Note: This command is no longer supported and will be removed in a future release.

Platforms

All

rib-api-getversion

rib-api-getversion

Syntax

rib-api-getversion {permit | deny}

Context

[Tree] (config>system>security>profile>grpc>rpc-authorization rib-api-getversion)

Full Context

configure system security profile grpc rpc-authorization rib-api-getversion

Description

This command permits the use of GetVersion RPC provided by the RibApi service.

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

Default

rib-api-getversion permit

Parameters

permit

Specifies that the use of the GetVersion RPC is permitted.

deny

Specifies that the use of the GetVersion RPC is denied.

Platforms

All

rib-api-modify

rib-api-modify

Syntax

rib-api-modify {permit | deny}

Context

[Tree] (config>system>security>profile>grpc>rpc-authorization rib-api-modify)

Full Context

configure system security profile grpc rpc-authorization rib-api-modify

Description

This command permits the use of Modify RPC provided by the RibApi service.

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

Default

rib-api-modify permit

Parameters

permit

Specifies that the use of the Modify RPC is permitted.

deny

Specifies that the use of the Modify RPC is denied.

Platforms

All

rib-management

rib-management

Syntax

rib-management

Context

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

Full Context

configure service vprn bgp rib-management

Description

Commands in this context configure RIB management parameters.

Platforms

All

rib-management

Syntax

rib-management

Context

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

Full Context

configure router bgp rib-management

Description

Commands in this context configure RIB management parameters.

Platforms

All

rib-priority

rib-priority

Syntax

rib-priority high {prefix-list-name | tag tag}

no rib-priority

Context

[Tree] (config>service>vprn>isis rib-priority)

Full Context

configure service vprn isis rib-priority

Description

This command enabled RIB prioritization for the IS-IS protocol and specifies the prefix list or IS-IS tag value that will be used to select the specific routes that should be processed through the IS-IS route calculation process at a higher priority.

The no form of this command disables RIB prioritization.

Default

no rib-priority

Parameters

prefix-list-name

Specifies the prefix list which is used to select the routes that are processed at a higher priority through the route calculation process.

tag tag-value

Specifies the tag value that is used to match IS-IS routes that are to be processed at a higher priority through the route calculation process.

Values

1 to 4294967295

Platforms

All

rib-priority

Syntax

rib-priority high

no rib-priority

Context

[Tree] (config>service>vprn>ospf3>area>if rib-priority)

[Tree] (config>service>vprn>ospf>area>if rib-priority)

Full Context

configure service vprn ospf3 area interface rib-priority

configure service vprn ospf area interface rib-priority

Description

This command enables RIB prioritization for the OSPF/OSPFv3 protocol. When enabled at the OSPF interface level, all routes learned through the associated OSPF interface will be processed through the OSPF route calculation process at a higher priority.

The no form of rib-priority command disables RIB prioritization at the associated level.

Default

no rib-priority

Platforms

All

rib-priority

Syntax

rib-priority {high} prefix-list-name

no rib-priority

Context

[Tree] (config>service>vprn>ospf3 rib-priority)

[Tree] (config>service>vprn>ospf rib-priority)

Full Context

configure service vprn ospf3 rib-priority

configure service vprn ospf rib-priority

Description

This command enabled RIB prioritization for the OSPF protocol and specifies the prefix list that will be used to select the specific routes that should be processed through the OSPF route calculation process at a higher priority.

The no form of rib-priority command disables RIB prioritization at the associated level.

Default

no rib-priority

Parameters

prefix-list-name

Specifies the prefix list which is used to select the routes that are processed at a higher priority through the route calculation process.

Platforms

All

rib-priority

Syntax

rib-priority high {prefix-list-name | tag tag-value}

no rib-priority

Context

[Tree] (config>router>isis rib-priority)

Full Context

configure router isis rib-priority

Description

This command enabled RIB prioritization for the IS-IS protocol and specifies the prefix list or IS-IS tag value that will be used to select the specific routes that should be processed through the IS-IS route calculation process at a higher priority.

The no rib-priority form of command disables RIB prioritization.

Default

no rib-priority high

Parameters

prefix-list-name

Specifies the prefix list which is used to select the routes that are processed at a higher priority through the route calculation process.

tag tag-value

Specifies the tag value that is used to match IS-IS routes that are to be processed at a higher priority through the route calculation process.

Values

1 to 4294967295

Platforms

All

rib-priority

Syntax

rib-priority {high} prefix-list-name

no rib-priority {high}

Context

[Tree] (config>router>ospf3 rib-priority)

[Tree] (config>router>ospf rib-priority)

Full Context

configure router ospf3 rib-priority

configure router ospf rib-priority

Description

This command enables RIB prioritization for the OSPF protocol and specifies the prefix list used to select the specific routes that should be processed through the OSPF route calculation process at a higher priority.

The no form of this command disables RIB prioritization at the associated level.

Default

no rib-priority high

Parameters

prefix-list-name

Specifies the prefix list, up to 32 characters, which is used to select the routes that are processed at a higher priority through the route calculation process.

Platforms

All

rib-priority

Syntax

rib-priority {high}

no rib-priority

Context

[Tree] (config>router>ospf3>area>interface rib-priority)

[Tree] (config>router>ospf>area>interface rib-priority)

Full Context

configure router ospf3 area interface rib-priority

configure router ospf area interface rib-priority

Description

This command enables RIB prioritization for the OSPF/OSPFv3 protocol. When enabled at the OSPF interface level, all routes learned through the associated OSPF interface are processed through the OSPF route calculation process at a higher priority.

The no form of this command disables RIB prioritization at the associated level.

Default

no rib-priority

Parameters

high

Specifies that the name of the prefix list which contains prefixes get high priority for RIB-download. The high priority prefixes are downloaded first to the RIB. In doing so, the convergence time for these prefixes is better.

Platforms

All

ring

ring

Syntax

ring sync-tag [create]

no ring sync-tag

Context

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

Full Context

configure redundancy multi-chassis peer mc-ring ring

Description

This command configures a multi-chassis ring.

The no form of this command removes the sync-tag from the configuration.

Parameters

sync-tag

Specifies a synchronization tag, up to 32 characters, to be used while synchronizing this port with the multi-chassis peer.

create

Creates he multi-chassis peer ring instance. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

All

ring-node

ring-node

Syntax

ring-node ring-node-name [create]

no ring-node ring-node-name

Context

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

Full Context

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

Description

This command specifies the unique name of a multi-chassis ring access node.

Parameters

ring-node-name

Specifies the unique name of a multi-chassis ring access node. The name can be up to 32 characters.

create

Keyword used to create the ring node instance. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

All

ring-node

Syntax

ring-node ring-node-name

no ring-node

Context

[Tree] (config>service>epipe>sap ring-node)

Full Context

configure service epipe sap ring-node

Description

This command configures a multi-chassis ring-node for this SAP.

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

Platforms

All

rip

rip

Syntax

[no] rip

Context

[Tree] (config>service>vprn rip)

[Tree] (config>service>ies rip)

Full Context

configure service vprn rip

configure service ies rip

Description

This command enables the RIP protocol on the given VPRN IP interface.

The no form of this command disables the RIP protocol from the given VPRN IP interface.

Default

no rip

Platforms

All

rip

Syntax

[no] rip

Context

[Tree] (config>router rip)

Full Context

configure router rip

Description

This command creates the context to configure the RIP protocol instance.

When a RIP instance is created, the protocol is enabled by default. To start or suspend execution of the RIP protocol without affecting the configuration, use the [no] shutdown command.

The no form of the command deletes the RIP protocol instance removing all associated configuration parameters.

Default

no rip

Platforms

All

rip-policy

rip-policy

Syntax

rip-policy policy-name

no rip-policy

Context

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host rip-policy)

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

Full Context

configure subscriber-mgmt local-user-db ipoe host rip-policy

configure subscriber-mgmt local-user-db ppp host rip-policy

Description

This command configures the RIP policy name. This policy is applied to a subscriber IPv4 host to enable the BNG to learn RIP routes from the host. RIP routes are never sent to the hosts.

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

Parameters

policy-name

Specifies the RIP policy name, up to 32 characters.

Platforms

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

rip-policy

Syntax

rip-policy policy-name [create]

no rip-policy policy-name

Context

[Tree] (config>subscr-mgmt rip-policy)

Full Context

configure subscriber-mgmt rip-policy

Description

This command creates a RIP policy. This policy is applied to a subscriber IPv4 host to enable the BNG to learn RIP routes from the host. RIP routes are never sent to the hosts.

Parameters

policy-name

Specifies the RIP policy name up to 32 characters.

create

Keyword required to create the configuration context.

Platforms

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

rip-policy

Syntax

rip-policy rip-policy-name

no rip-policy

Context

[Tree] (config>service>ies>sub-if>grp-if>sap>static-host rip-policy)

Full Context

configure service ies subscriber-interface group-interface sap static-host rip-policy

Description

This command specifies the name of the RIP policy up to 32 characters.

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

Platforms

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

ripng

ripng

Syntax

[no] ripng

Context

[Tree] (config>router ripng)

Full Context

configure router ripng

Description

This command creates the context to configure the RIPng protocol instance.

When a RIPng instance is created, the protocol is enabled by default. To start or suspend execution of the RIP protocol without affecting the configuration, use the [no] shutdown command.

The no form of this command deletes the RIP protocol instance removing all associated configuration parameters.

Default

no ripng

Platforms

All

rmon

rmon

Syntax

rmon

Context

[Tree] (config>system>thresholds rmon)

Full Context

configure system thresholds rmon

Description

This command creates the context to configure generic RMON alarms and events.

Generic RMON alarms can be created on any SNMP object-ID that is valid for RMON monitoring (for example, an integer-based datatype).

The configuration of an event controls the generation and notification of threshold crossing events configured with the alarm command.

Platforms

All

roaming

roaming

Syntax

roaming bit [bit]

no roaming

Context

[Tree] (config>subscr-mgmt>gtp>peer-profile>charging roaming)

Full Context

configure subscriber-mgmt gtp peer-profile charging-characteristics roaming

Description

This command configures the charging characteristics for roaming UE.

The no form of this command removes the bit value from the configuration.

Default

no roaming

Parameters

bit

Specifies up to 16 bits to set in the Charging Characteristics Information Element (IE) for roaming UE, if not known by other means such as RADIUS.

Values

bit0, bit1, bit2, bit3, bit4, bit5, bit6, bit7, bit8, bit9, bit10, bit11, bit12, bit13, bit14, bit15

Platforms

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

robust-count

robust-count

Syntax

robust-count robust-count

no robust-count

Context

[Tree] (config>service>vpls>mesh-sdp>igmp-snooping robust-count)

[Tree] (config>service>vpls>sap>mld-snooping robust-count)

[Tree] (config>service>vpls>mesh-sdp>mld-snooping robust-count)

[Tree] (config>service>vpls>igmp-snooping robust-count)

[Tree] (config>service>vpls>sap>igmp-snooping robust-count)

[Tree] (config>service>vpls>spoke-sdp>mld-snooping robust-count)

[Tree] (config>service>vpls>spoke-sdp>igmp-snooping robust-count)

Full Context

configure service vpls mesh-sdp igmp-snooping robust-count

configure service vpls sap mld-snooping robust-count

configure service vpls mesh-sdp mld-snooping robust-count

configure service vpls igmp-snooping robust-count

configure service vpls sap igmp-snooping robust-count

configure service vpls spoke-sdp mld-snooping robust-count

configure service vpls spoke-sdp igmp-snooping robust-count

Description

If the send-queries command is enabled, this parameter allows tuning for the expected packet loss on a SAP or SDP. The robust-count variable allows tuning for the expected packet loss on a subnet and is comparable to a retry count. If this SAP or SDP is expected to be 'lossy', this parameter may be increased. IGMP snooping on this SAP or SDP is robust to (robust-count-1) packet losses.

If send-queries is not enabled, this parameter will be ignored.

Default

robust-count 2

Parameters

robust-count

Specifies the robust count for the SAP or SDP

Values

2 to 7 (for config>service>vpls>sap>igmp-snooping) 1 to 255 (for config>service>vpls>igmp-snooping)

Platforms

All

robust-count

Syntax

robust-count robust-count

no robust-count

Context

[Tree] (config>subscr-mgmt>msap-policy>vpls-only>igmp-snp robust-count)

Full Context

configure subscriber-mgmt msap-policy vpls-only-sap-parameters igmp-snooping robust-count

Description

This command configures the IGMP robustness variable. If the send-queries command is enabled, this parameter allows tuning for the expected packet loss on a SAP or SDP. The robust-count variable allows tuning for the expected packet loss on a subnet and is comparable to a retry count. If an MSAP or SDP is expected to be "lossy”, this parameter may be increased. IGMP snooping on an MSAP or SDP is robust to (robust-count-1) packet losses.

If send-queries is not enabled, this parameter is ignored.

The no form of this command reverts to the default.

Default

robust-count 2

Parameters

robust-count

Specifies the robust count for the SAP or SDP.

Values

2 to 7

Platforms

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

robust-count

Syntax

robust-count robust-count

no robust-count

Context

[Tree] (config>service>vprn>mld robust-count)

[Tree] (config>service>vprn>igmp robust-count)

Full Context

configure service vprn mld robust-count

configure service vprn igmp robust-count

Description

This command configures the robust count. The robust-count variable allows tuning for the expected packet loss on a subnet. If a subnet anticipates losses, the robust-count variable can be increased.

Default

robust-count 2

Parameters

robust-count

Specifies the robust count value.

Values

2 to 10

Platforms

All

robust-count

Syntax

robust-count robust-count

no robust-count

Context

[Tree] (config>router>igmp robust-count)

Full Context

configure router igmp robust-count

Description

This command configures the robust count. The robust-count variable allows tuning for the expected packet loss on a subnet. If a subnet anticipates losses, the robust-count variable can be increased.

Default

robust-count 2

Parameters

robust-count

Specify the robust count value.

Values

2 to 10

Platforms

All

robust-count

Syntax

robust-count robust-count

no robust-count

Context

[Tree] (config>router>mld robust-count)

Full Context

configure router mld robust-count

Description

This command configures the robust count. The robust-count variable allows tuning for the expected packet loss on a subnet. If a subnet anticipates losses, the robust-count variable can be increased.

Default

robust-count 2

Parameters

robust-count

Specify the robust count value.

Values

2 to 10

Platforms

All

robust-count

Syntax

robust-count robust-count

no robust-count

Context

[Tree] (config>service>pw-template>igmp-snooping robust-count)

Full Context

configure service pw-template igmp-snooping robust-count

Description

If the send-queries command is enabled, this parameter allows tuning for the expected packet loss. The robust-count variable allows tuning for the expected packet loss on a subnet and is comparable to a retry count.

If send-queries is not enabled, this parameter will be ignored.

Default

robust-count 2

Parameters

robust-count

Specifies the robust count for the SAP or SDP.

Values

2 to 7

Platforms

All

role

role

Syntax

role role-type

Context

[Tree] (config>system>satellite>port-template>port role)

Full Context

configure system satellite port-template port role

Description

This command configures the role that the associated port is to take on.

Parameters

none

Clears the role association for the associated port.

uplink

Specifies that the associated satellite port is assigned the role of an uplink port.

client

Specifies that the associated satellite port is assigned the role of a satellite client port.

system-default

Specifies that the associated satellite port is returned to the system default.

Platforms

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

rollback

rollback

Syntax

rollback

Context

[Tree] (config>system rollback)

Full Context

configure system rollback

Description

Configure parameters of the classic CLI configuration rollback functionality. Configuration rollback provides the ability to undo configuration and revert back to previous router configuration states.

Platforms

All

rollback

Syntax

rollback

Context

[Tree] (admin rollback)

Full Context

admin rollback

Description

Commands in this context configure rollback operations.

Platforms

All

rollback-location

rollback-location

Syntax

rollback-location file-url /rollback filename

no rollback-location

Context

[Tree] (config>system>rollback rollback-location)

Full Context

configure system rollback rollback-location

Description

The location and name of the rollback checkpoint files is configurable to be local (on compact flash) or remote. The file-url must not contain a suffix (just a path/directory + filename). The suffixes for rollback checkpoint files are ".rb”, ".rb.1", ..., ".rb.9" and are automatically appended to rollback checkpoint files.

Default

no rollback-location

Parameters

file-url

Specifies the URL or rollback filename.

Values

local-url | remote-url

local-url

[cflash-id/][file-path] up to 200 characters, including cflash-id directory length of up to 99 characters each

remote-url

[{ftp://}login:pswd@ remote-locn/][file-path] up to 255 characters, directory length of up to 99 characters each

remote-locn

[hostname | ipv4-address | ipv6-address]

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

interface - up to 32 characters each, for link local addresses

cflash-id

cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

rollback-filename

Specifies the rollback file name.

Values

suffixed with .rb, .rb.1 up to .9 during rollback checkpoint creation

Platforms

All

rollback-sync

rollback-sync

Syntax

rollback-sync

Context

[Tree] (admin>redundancy rollback-sync)

Full Context

admin redundancy rollback-sync

Description

This command copies the entire set of rollback checkpoint files from the active CPM CF to the standby CPM CF.

Platforms

All

rollback-sync

Syntax

[no] rollback-sync

Context

[Tree] (config>redundancy rollback-sync)

Full Context

configure redundancy rollback-sync

Description

The operator can enable automatic synchronization of rollback checkpoint files between the active CPM and standby CPM. When this automatic synchronization is enabled, a rollback save will cause the new checkpoint file to be saved on both the active and standby CPMs. The suffixes of the old checkpoint files on both active and standby CPMs are incremented. Note that automatic sync only causes the one new checkpoint file to be copied to both CFs (the other 9 checkpoints are not automatically copied from active to standby but that can be done manually with admin red rollback-sync).

Automatic synchronization of rollback checkpoint files across CPMs is only performed if the rollback-location is configured as a local file-url (for example, "cf3:/rollback-files/rollback). Synchronization is not done if the rollback-location is remote.

The config red sync {boot-env | config} and admin red sync {boot-env | config} do not apply to rollback checkpoint files. These commands do not manually or automatically sync rollback checkpoint files. The dedicated rollback-sync commands must be used to sync rollback checkpoint files.

Default

no rollback-sync

Platforms

All

rollover

rollover

Syntax

rollover minutes [retention hours]

no rollover

Context

[Tree] (config>log>file-id rollover)

Full Context

configure log file-id rollover

Description

This command configures how often an event or accounting log is rolled over or partitioned into a new file.

An event or accounting log is actually composed of multiple, individual files. The system creates a new file for the log based on the rollover time, expressed in minutes.

The retention option, expressed in hours, allows you to modify the default time to keep the file in the system. The retention time is based on the rollover time of the file.

If logs are needed to be retained for more than 16 days, use a CRON job to move the logs to a different location, either on a local drive or a remote server. For more information, contact Nokia support.

When multiple rollover commands for a file-id are entered, the last command overwrites the previous command.

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

Default

rollover 1440 retention 12

Parameters

minutes

Specifies the rollover time, in minutes.

Values

5 to 10080

retention hours

Specifies the retention period in hours, expressed as a decimal integer. The retention time is based on the time creation time of the file. The file becomes a candidate for removal once the creation datestamp + rollover time + retention time is less than the current timestamp.

Default

12

Values

1 to 500

Platforms

All

root

root

Syntax

root

Context

[Tree] (config>qos>policer-control-policy root)

Full Context

configure qos policer-control-policy root

Description

The root node contains the policer control policies configuration parameters for the root arbiter. Within the node, the parent policer’s maximum rate limit can be set, the strict priority level, and fair threshold portions may be defined per priority level.

The root node always exists and does not need to be created.

Platforms

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

root-address

root-address

Syntax

root-address ip-address

no root-address

Context

[Tree] (config>router>p2mp-sr-tree>p2mp-policy root-address)

Full Context

configure router p2mp-sr-tree p2mp-policy root-address

Description

This command configures the IP address of the P2MP SR tree root node of the P2MP policy. The root tree ID and the root address uniquely identify the P2MP policy on the root node.

The no form of this command removes the root address entry.

Parameters

ip-address

Specifies the IPv4 address of the root node.

Values

a.b.c.d

Platforms

All

root-address

Syntax

root-address ip-address

no root address

Context

[Tree] (config>router>p2mp-sr-tree>replication-segment root-address)

Full Context

configure router p2mp-sr-tree replication-segment root-address

Description

This command configures the replication segment with the IP address of the root node of the P2MP SR tree replication segment.

The no form of this command removes the root node address.

Parameters

ip-address

Specifies the IPv4 address.

Values

a.b.c.d

Platforms

All

root-and-leaf

root-and-leaf

Syntax

[no] root-and-leaf

Context

[Tree] (config>service>vpls>provider-tunnel>inclusive root-and-leaf)

Full Context

configure service vpls provider-tunnel inclusive root-and-leaf

Description

This command configures the node to operate as both root and leaf of the I-PMSI in a specified VPLS/B-VPLS instance.

By default, a node will behave as a leaf-only node. When the node is leaf only for the I-PMSI of type P2MP RSVP LSP, no PMSI Tunnel Attribute is included in BGP-AD route update messages and therefore no RSVP P2MP LSP is signaled but the node can join RSVP P2MP LSP rooted at other PE nodes participating in this VPLS/B-VPLS service. The user must still configure a LSP template even if the node is a leaf only.

For the I-PMSI of type mLDP, the leaf-only node will join I-PMSI rooted at other nodes it discovered but will not include a PMSI Tunnel Attribute in BGP-AD route update messages. This way a leaf-only node will forward packets to other nodes in the VPLS/B-VPLS using the point-to-point spoke-SDPs.

The no version of this command re-instates the default value.

Platforms

All

root-guard

root-guard

Syntax

[no] root-guard

Context

[Tree] (config>service>vpls>sap>stp root-guard)

[Tree] (config>service>vpls>spoke-sdp>stp root-guard)

[Tree] (config>service>template>vpls-sap-template>stp root-guard)

Full Context

configure service vpls sap stp root-guard

configure service vpls spoke-sdp stp root-guard

configure service template vpls-sap-template stp root-guard

Description

This command specifies whether this port is allowed to become an STP root port. It corresponds to the restrictedRole parameter in 802.1Q. If set, it can cause lack of spanning tree connectivity.

Default

no root-guard

Platforms

All

root-guard

Syntax

[no] root-guard

Context

[Tree] (config>service>pw-template>stp root-guard)

Full Context

configure service pw-template stp root-guard

Description

This command specifies whether this port is allowed to become an STP root port. It corresponds to the restrictedRole parameter in 802.1Q. If set, it can cause lack of spanning tree connectivity.

Default

no root-guard

Platforms

All

root-pool

root-pool

Syntax

[no] root-pool root-pool-id

Context

[Tree] (config>qos>hs-pool-policy>root-tier root-pool)

Full Context

configure qos hs-pool-policy root-tier root-pool

Description

Commands in this context configure root tier parameters. Within the root-tier context, root pools can be sized using the allocation-weight command or a slope policy can be associated with a root pool.

The no form of the command restores the default allocation-weight value and default slope policy to the specified root pool. Root pool 1 has a different default weight than root pools 2 through 16. The no root-pool command fails for root pools 2 through 16 if the root pool is currently the parent of a mid-tier pool.

Parameters

root-pool-id

Specifies the root pool ID. This is a required parameter when executing the root-pool command and specifies which root pool context is being entered.

Values

1 to 16

Platforms

7750 SR-7/12/12e

root-tier

root-tier

Syntax

root-tier

Context

[Tree] (config>qos>hs-pool-policy root-tier)

Full Context

configure qos hs-pool-policy root-tier

Description

Commands in this context configure root pool parameters. Within the root-tier context, root pools can be sized using the allocation-weight command or a slope policy can be associated with a root pool.

Platforms

7750 SR-7/12/12e

root-tree-id

root-tree-id

Syntax

root-tree-id tree-id

no root-tree-id

Context

[Tree] (config>router>p2mp-sr-tree>p2mp-policy root-tree-id)

Full Context

configure router p2mp-sr-tree p2mp-policy root-tree-id

Description

This command configures the P2MP SR tree ID on the root node of the P2MP policy. The root tree ID and the root address uniquely identify the P2MP policy on the root node.

The no form of this command removes the root tree ID entry.

Parameters

tree-id

Specifies the ID of the tree.

Values

8193 to 16286

Platforms

All

root-tree-id

Syntax

root-tree-id tree-id

no root-tree-id

Context

[Tree] (config>router>p2mp-sr-tree>replication-segment root-tree-id)

Full Context

configure router p2mp-sr-tree replication-segment root-tree-id

Description

This command configures the root-tree ID for the replication segment of the P2MP SR tree.

The no form of this command removes the root-tree ID.

Parameters

tree-id

Specifies the root-tree ID.

Values

8193 to 16286

Platforms

All

round-robin-inactive-records

round-robin-inactive-records

Syntax

[no] round-robin-inactive-records

Context

[Tree] (config>mcast-mgmt>chassis-level round-robin-inactive-records)

Full Context

configure mcast-management chassis-level round-robin-inactive-records

Description

This command specifies whether initially inactive multicast records use the IOM default secondary multicast path or not. When enabled, the system redistributes newly populated inactive records among all available IOM multicast paths and multicast switch fabric planes. When disabled, the system continues to set all initially inactive multicast records to use the IOM default secondary multicast path.

The no form of this command reverts to the default.

Platforms

7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR

route

route

Syntax

route index index [realm realm-string] [application application] [create]

no route index index

Context

[Tree] (config>aaa>diam>node>peer route)

Full Context

configure aaa diameter node peer route

Description

This command configures the index of the static route within the Diameter peer used to reach remote realms that are not directly connected to the origin realm, or to override the route preference (peer preference) of the directly-connected realms.

The no form of this command removes the route index information from the configuration.

Parameters

index

Specifies the index of the static route within the Diameter peer.

Values

1 to 15

realm-string

Specifies the destination realm reachable through this static route, up to 80 characters.

application

Specifies the ID of the Diameter application of the static route.

Values

nasreq, gy, gx

create

Keyword used to create the route index. 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

route-admin-tag-policy

route-admin-tag-policy

Syntax

[no] route-admin-tag-policy policy-name

Context

[Tree] (config>router>admin-tags route-admin-tag-policy)

Full Context

configure router admin-tags route-admin-tag-policy

Description

This command configures a route admin tag policy.

Up to 2,000 policies can be configured per system.

The no form of this command removes the route admin tag policy.

Parameters

policy-name

The name of the route admin tag policy, up to 32 characters.

Platforms

All

route-advertisement

route-advertisement

Syntax

[no] route-advertisement

Context

[Tree] (config>router>bgp>group>srv6 route-advertisement)

[Tree] (config>router>bgp>group>neighbor>srv6 route-advertisement)

Full Context

configure router bgp group segment-routing-v6 route-advertisement

configure router bgp group neighbor segment-routing-v6 route-advertisement

Description

Commands in this context configure the route advertisement options.

The no form of this command deletes the context.

Default

no route-advertisement

Platforms

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

route-distinguisher

route-distinguisher

Syntax

route-distinguisher auto-rd

route-distinguisher rd

no route-distinguisher

Context

[Tree] (config>subscr-mgmt>isa-svc-chain>evpn>bgp route-distinguisher)

Full Context

configure subscriber-mgmt isa-service-chaining evpn bgp route-distinguisher

Description

This command configures the Route Distinguisher (RD) field that is signaled in NLRI in EVPN routes.

The no form of this command reverts to the default.

Parameters

auto-rd

Specifies that the system automatically generates an RD.

rd

Specifies the RD.

Values

rd: ip-addr:comm-val | 2byte-asnumber:ext-comm-val | 4byte-asnumber:comm-val

ip-addr: a.b.c.d

comm-val: [0 to 65535]

2byte-asnumber: [1 to 65535]

ext-comm-val: [0 to 4294967295]

4byte-asnumber: [1 to 4294967295]

Platforms

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

route-distinguisher

Syntax

route-distinguisher auto-rd

no route-distinguisher

route-distinguisher rd

Context

[Tree] (config>service>epipe>bgp route-distinguisher)

[Tree] (config>service>vpls>bgp route-distinguisher)

Full Context

configure service epipe bgp route-distinguisher

configure service vpls bgp route-distinguisher

Description

This command configures the Route Distinguisher (RD) component that will be signaled in the MP-BGP NLRI for L2VPN and EVPN families. This value will be used for BGP-AD, BGP VPLS and BGP multi-homing NLRI if these features are configured.

If this command is not configured, the RD is automatically built using the BGP-AD VPLS ID. The following rules apply:

  • if BGP AD VPLS-id is configured and no RD is configured under BGP node - RD=VPLS-ID

  • if BGP AD VPLS-id is not configured then an RD value must be configured under BGP node (this is the case when only BGP VPLS is configured)

  • if BGP AD VPLS-id is configured and an RD value is also configured under BGP node, the configured RD value prevails

Values and format (6 bytes, other 2 bytes of type will be automatically generated)

Alternatively, the auto-rd option allows the system to automatically generate an RD based on the bgp-auto-rd-range command configured at the service level. For BGP-EVPN enabled VPLS and Epipe services, the route-distinguisher value can also be auto-derived from the evi value (config>service>vpls>bgp-evpn>evi or config>service>epipe>bgp-evpn>evi) if this command is not configured. See the config>service>system>bgp-evpn>eth-seg>service-carving>manual evi command description for more information.

Parameters

ip-addr:comm-val

Specifies the IP address.

Values

ip-addr: a.b.c.d

comm-val: 0 to 65535

as-number:ext-comm-val

Specifies the AS number.

Values

as-number: 1 to 65535

ext-comm-val: 0 to 4294967295

auto-rd

The system will generate an RD for the service according to the IP address and range configured in the bgp-auto-rd-range command.

Platforms

All

route-distinguisher

Syntax

route-distinguisher [ip-addr:comm-val | as-number:ext-comm-val]

no route-distinguisher

Context

[Tree] (config>service>system>bgp-evpn route-distinguisher)

Full Context

configure service system bgp-evpn route-distinguisher

Description

This command configures the Route Distinguisher (RD) component that will be signaled in the MP-BGP NLRI for EVPN corresponding to the base EVPN instance (Ethernet Segment routes). If the route-distinguisher component is not configured, the system will use system:ip-address as the default route-distinguisher

Default

no route-distinguisher

Parameters

ip-addr:comm-val

Specifies the IP address.

Values

ip-addr: a.b.c.d

comm-val: 0 to 65535

as-number:ext-comm-val

Specifies the AS number.

Values

as-number: 1 to 65535

ext-comm-val: 0 to 4294967295

Platforms

All

route-distinguisher

Syntax

route-distinguisher rd

route-distinguisher auto-rd

no route-distinguisher

Context

[Tree] (config>service>vprn>bgp-ipvpn>mpls route-distinguisher)

[Tree] (config>service>vprn>bgp-ipvpn>srv6 route-distinguisher)

[Tree] (config>service>vprn>bgp-evpn>mpls route-distinguisher)

Full Context

configure service vprn bgp-ipvpn mpls route-distinguisher

configure service vprn bgp-ipvpn segment-routing-v6 route-distinguisher

configure service vprn bgp-evpn mpls route-distinguisher

Description

This command specifies an identifier attached to a route, which enables the user to identify the VPN to which the route belongs. Each routing instance must have a unique (within the carrier’s domain) route distinguisher (RD) associated with it.

Alternatively, the auto-rd option allows the system to automatically generate an RD based on the bgp-auto-rd-range command configured at the service level.

The no form of this command removes the RD configuration.

Default

no route-distinguisher

Parameters

auto-rd

Keyword that allows the system to generate an RD for the service according to the IP address and range configured in the bgp-auto-rd-range command.

rd

Specifies the route distinguisher.

Values

rd: ip-addr:comm-val | 2byte-asnumber:ext-comm-val | 4byte-asnumber:comm-val

ip-addr: a.b.c.d

comm-val: [0 to 65535]

2byte-asnumber: [1 to 65535]

ext-comm-val: [0 to 4294967295]

4byte-asnumber: [1 to 4294967295]

Platforms

All

  • configure service vprn bgp-evpn mpls route-distinguisher
  • configure service vprn bgp-ipvpn mpls route-distinguisher

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

  • configure service vprn bgp-ipvpn segment-routing-v6 route-distinguisher

route-distinguisher

Syntax

route-distinguisher

Context

[Tree] (config>service>vprn route-distinguisher)

Full Context

configure service vprn route-distinguisher

Description

Note: This command is no longer supported and will be removed in a future release.

Platforms

All

route-distinguisher-list

route-distinguisher-list

Syntax

route-distinguisher-list name

no route-distinguisher-list name

Context

[Tree] (config>router>policy-options route-distinguisher-list)

Full Context

configure router policy-options route-distinguisher-list

Description

This command creates a list of entries used to match the RD in BGP routes of specific address families.

Parameters

name

Specifies the name of the RD list, up to 64 characters.

Platforms

All

route-distinguisher-list

Syntax

route-distinguisher-list name

no route-distinguisher-list name

Context

[Tree] (config>router>policy-options>policy-statement>entry>from route-distinguisher-list)

Full Context

configure router policy-options policy-statement entry from route-distinguisher-list

Description

This command configures a route distinguisher (RD) list as a match criterion for the policy statement entry.

This match condition is supported by policies applied as VRF import or BGP peer import policies. A BGP route can match a policy entry with this match criterion if the NLRI field contains an RD that is matched by at least one of the entries in the route-distinguisher-list.

BGP routes belonging to address families other than VPN-IPv4, VPN-IPv6, MCAST-VPN-IPv4, MCAST-VPN-IPv6, EVPN, FlowSpec-VPN IPv4, FlowSpec-VPN IPv6, MVPN-IPv4 or MVPN-IPv6 routes do not match policy entries with this match criterion.

Parameters

name

Specifies the (possibly parameterized) name of an RD list.

Platforms

All

route-downloader

route-downloader

Syntax

route-downloader name [create]

no route-downloader name

Context

[Tree] (config>aaa route-downloader)

Full Context

configure aaa route-downloader

Description

Commands in this context configure a route-downloader instance. The route-downloader is a process that uses radius access-request messages to a particular server. The server returns either an access-accept or access-deny message. Access-accept messages also contain the prefixes (in the form of static blackhole routes in various formats). Only a single route-downloader object can be created.

The no form of this command removes the name from the configuration. The object must be shutdown prior to deletion. No prefix is needed to delete an existing route-download object.

Parameters

name

Specifies the name of this RADIUS route downloader.

create

This keyword is mandatory while creating an instance of the route-download object.

Platforms

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

route-entry

route-entry

Syntax

[no] route-entry {ip-prefix/length | ip-prefix netmask}

[no] route-entry ipv6-prefix/prefix-length

Context

[Tree] (config>service>ies>sub-if>grp-if>sap>static-host>managed-routes route-entry)

[Tree] (config>service>vprn>sub-if>grp-if>sap>static-host>managed-routes route-entry)

Full Context

configure service ies subscriber-interface group-interface sap static-host managed-routes route-entry

configure service vprn subscriber-interface group-interface sap static-host managed-routes route-entry

Description

This command assigns a managed route to a specified subscriber host. As a consequence, a static route pointing subscriber-host IP address as a next hop is installed in the FIB.

The no form of this command removes the respective route. By default, there are no managed routes configured.

Parameters

ip-prefix/length

Specifies the IP prefix and length.

Syntax:

ip-prefix/length:

ip-prefix

a.b.c.d

ip-prefix-length

1 to 32

netmask

Specifies the subnet mask in dotted decimal notation.

Values

a.b.c.d (0.0.0.0 not allowed)

ipv6-prefix/prefix-length

Specifies the IPv6 prefix and prefix length.

Values

ipv6-prefix

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

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

x: [0 to FFFF]H

d: [0 to 255]D

ipv6-prefix-length

1 to 128

Platforms

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

route-exists

route-exists

Syntax

route-exists expression

no route-exists

Context

[Tree] (config>router>policy-options>policy-statement>entry>cond-expr route-exists)

Full Context

configure router policy-options policy-statement entry conditional-expression route-exists

Description

This command is used to specify a route existence expression to control evaluation of the policy entry. If the route existence expression evaluates to 'true’ the matching and action commands of the policy entry are applied as normal. If the route existence expression evaluates to 'false’ the entire policy entry is skipped and processing continues with the next entry; however, conditional expressions are only parsed when the route policy is used as a BGP export policy or VRF export policy.

Default

no route-exists

Parameters

expression

"["<pfx-list-name>”]” [all | none]

If neither the all nor the none keyword are used the match logic is 'any’ – that is, the route expression evaluates as 'true’ if any exact match entry in the referenced prefix-list has an active route in the route table associated with the policy.

all – the route expression evaluates as 'true’ only if all the exact match entries in the referenced prefix-list have an active route in the route table associated with the policy.

none – the route expression evaluates as 'true’ only if none of the exact match entries in the referenced prefix-list have an active route in the route table associated with the policy.

Platforms

All

route-limit

route-limit

Syntax

route-limit [limit]

Context

[Tree] (config>service>vprn>nat>outside>dnat-only route-limit)

[Tree] (config>router>nat>outside>dnat-only route-limit)

Full Context

configure service vprn nat outside dnat-only route-limit

configure router nat outside dnat-only route-limit

Description

This command limits the number of source routes (inside routes) that are installed on the outside in dnat-only case. In case that the number of actual routes is larger than the number of configured routes, the excess of the routes will not be installed in the routing table and a log will be raised.

The source IP addresses on the inside must be known in advance in a dnat-only instance. This is required so that the corresponding routes can be installed in the routing table and thus the downstream traffic is properly routed towards the MS-ISAs where the original translation was performed (and state is kept).

In the dnat-only case, it is mandatory that the inside (private side) and the outside (public side) are in separated VPRNs.

Default

route-limit 32768

Parameters

[1..131072]

Specifies the maximum number of source routes installed on the outside the dnat-only scenario.

Platforms

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

route-monitoring

route-monitoring

Syntax

route-monitoring pre-policy [post-policy]

route-monitoring post-policy

no route-monitoring

Context

[Tree] (config>service>vprn>bgp>group>monitor route-monitoring)

[Tree] (config>router>bgp>monitor route-monitoring)

[Tree] (config>service>vprn>bgp>monitor route-monitoring)

[Tree] (config>router>bgp>group>neighbor>monitor route-monitoring)

[Tree] (config>router>bgp>group>monitor route-monitoring)

Full Context

configure service vprn bgp group monitor route-monitoring

configure router bgp monitor route-monitoring

configure service vprn bgp monitor route-monitoring

configure router bgp group neighbor monitor route-monitoring

configure router bgp group monitor route-monitoring

Description

This command specifies if BMP sends pre-policy route monitoring messages, post-policy route monitoring messages, both types of messages, or none.

The no form of this command disables sending of route-monitoring messages.

Parameters

pre-policy

Enables sending pre-policy route monitoring messages using the pre-policy path attribute values, if available.

post-policy

Enables sending post-policy route monitoring messages using the post-policy path attribute values, if available.

Platforms

All

route-next-hop

route-next-hop

Syntax

route-next-hop {system-ipv4 | system-ipv6 | ip-address}

Context

[Tree] (config>service>epipe>bgp-evpn>srv6 route-next-hop)

[Tree] (config>service>vpls>bgp-evpn>mpls route-next-hop)

[Tree] (config>service>epipe>bgp-evpn>mpls route-next-hop)

[Tree] (config>service>vpls>bgp-evpn>srv6 route-next-hop)

Full Context

configure service epipe bgp-evpn segment-routing-v6 route-next-hop

configure service vpls bgp-evpn mpls route-next-hop

configure service epipe bgp-evpn mpls route-next-hop

configure service vpls bgp-evpn segment-routing-v6 route-next-hop

Description

This command configures the next hop of the EVPN routes.

Default

route-next-hop system-ipv4

Parameters

system-ipv4

Specifies the system IPv4 address as the next hop for the service EVPN routes.

system-ipv6

Specifies the system IPv6 address as the next hop for the service EVPN routes.

ip-address

Specifies the IPv4 address value as the next hop for the service EVPN.

Values

a.b.c.d

Platforms

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

  • configure service vpls bgp-evpn segment-routing-v6 route-next-hop
  • configure service epipe bgp-evpn segment-routing-v6 route-next-hop

All

  • configure service epipe bgp-evpn mpls route-next-hop
  • configure service vpls bgp-evpn mpls route-next-hop

route-next-hop

Syntax

route-next-hop {ip-address | ipv6-address}

no route-next-hop

Context

[Tree] (config>service>system>bgp-evpn>eth-seg route-next-hop)

Full Context

configure service system bgp-evpn ethernet-segment route-next-hop

Description

This command modifies the next hop to the configured IP address value, for the following routes:

  • ES

  • AD per-ES (irrespective of the evi-rt-set or evi-rt configuration mode)

The no form of the command changes the originating IP address back to the system-ip.

Default

no route-next-hop

Parameters

ip-address

Specifies an IPv4 or IPv6 address.

Values

ip-address | ipv6-address

Platforms

All

route-next-hop-policy

route-next-hop-policy

Syntax

route-next-hop-policy

Context

[Tree] (config>router route-next-hop-policy)

Full Context

configure router route-next-hop-policy

Description

This command creates the context to configure route next-hop policies.

Platforms

All

route-preference

route-preference

Syntax

route-preference primary {inband | outband} secondary {inband | outband | none}

no route-preference

Context

[Tree] (config>log route-preference)

Full Context

configure log route-preference

Description

This command specifies the primary and secondary routing preference for traffic generated for SNMP notifications and syslog messages. If the remote destination is not reachable through the routing context specified by primary route preference then the secondary routing preference will be attempted.

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

Default

no route-preference

Parameters

primary

Specifies the primary routing preference for traffic generated for SNMP notifications and syslog messages.

Default

outband

secondary

Specifies the secondary routing preference for traffic generated for SNMP notifications and syslog messages. The routing context specified by the secondary route preference will be attempted if the remote destination was not reachable by the primary routing preference, specified by primary route preference. The value specified for the secondary routing preference must be distinct from the value for primary route preference.

Default

inband

inband

Specifies that the logging utility will attempt to use the base routing context to send SNMP notifications and syslog messages to remote destinations.

outband

Specifies that the logging utility will attempt to use the management routing context to send SNMP notifications and syslog messages to remote destinations.

none

Specifies that no attempt will be made to send SNMP notifications and syslog messages to remote destinations.

Platforms

All

route-preference

Syntax

route-preference {both | inband | outband}

no route-preference

Context

[Tree] (config>system>security>tacplus route-preference)

[Tree] (config>system>security>radius route-preference)

[Tree] (config>system>security>ldap route-preference)

Full Context

configure system security tacplus route-preference

configure system security radius route-preference

configure system security ldap route-preference

Description

This command specifies the routing preference to reach the AAA server. If the configured option is to use both in-band and out-of-band routes, the out-of-band routes in the management routing instance are used to reach the server before the in-band routes in the Base routing instance.

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

Default

route-preference both

Parameters

both

Specifies the use of out-of-band routes before in-band routes.

inband

Specifies the use of in-band routes only.

outband

Specifies the use of out-of-band routes only.

Platforms

All

route-preference

Syntax

route-preference {both | inband | outband}

no route-preference

Context

[Tree] (config>router>pcep>pcc>peer route-preference)

Full Context

configure router pcep pcc peer route-preference

Description

This command specifies the routing preference to reach the PCE server. If the configured option is to use both in-band and out-of-band routes, the out-of-band routes in the management routing instance are used to reach the server before the in-band routes in the Base routing instance.

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

Default

route-preference both

Parameters

both

Specifies the use of out-of-band routes before in-band routes.

inband

Specifies the use of in-band routes only.

outband

Specifies the use of out-of-band routes only.

Platforms

All

route-recovery-wait

route-recovery-wait

Syntax

route-recovery-wait seconds

no route-recovery-wait

Context

[Tree] (config>log>app-route-notifications route-recovery-wait)

Full Context

configure log app-route-notifications route-recovery-wait

Description

The time delay that must pass before notifying specific CPM applications after the recovery or change of a route during normal operation.

The no form of this command disables the time-delay configuration.

Default

no route-recovery-wait

Parameters

seconds

Time delay in seconds.

Values

1 to 100

Platforms

All

route-refresh

route-refresh

Syntax

route-refresh [neighbor ip-address | group name]

no route-refresh

Context

[Tree] (debug>router>bgp route-refresh)

Full Context

debug router bgp route-refresh

Description

This command enables debugging for BGP route-refresh.

The no form of this command disables debugging.

Parameters

neighbor ip-address

Debugs only events affecting the specified BGP neighbor.

Values

ipv4-address:

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

ipv6-address:

  • x:x:x:x:x:x:x:x [-interface] (eight 16-bit pieces)

  • x:x:x:x:x:x:d.d.d.d [-interface]

  • x: [0 to FFFF]H

  • d: [0 to 255]D

  • interface: up to 32 characters for link local addresses

group name

Debugs only events affecting the specified peer group name, up to 64 characters, and associated neighbors.

Platforms

All

route-table

route-table

Syntax

route-table [ip-prefix/prefix-length]

route-table ip-prefix/prefix-length longer

no route-table

Context

[Tree] (debug>router>ip route-table)

Full Context

debug router ip route-table

Description

This command configures route table debugging.

Parameters

ip-prefix/prefix-length

The IP prefix for prefix list entry in dotted decimal notation.

Values

The following values apply to the 7750 SR and 7950 XRS:

ipv4-prefix

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

ipv4-prefix-length

0 to 32

ipv6-prefix

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

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

x:

[0 to FFFF]H

d:

[0 to 255]D

ipv6-prefix-length

0 to 128

Values

The following values apply to the 7450 ESS:

ipv4-prefix

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

ipv4-prefix-length

0 to 32

longer

Specifies the prefix list entry matches any route that matches the specified ip-prefix and prefix mask length values greater than the specified mask.

Platforms

All

route-table-import

route-table-import

Syntax

route-table-import policy-name

no route-table-import

Context

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

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

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

Full Context

configure service vprn bgp rib-management label-ipv4 route-table-import

configure service vprn bgp rib-management ipv4 route-table-import

configure service vprn bgp rib-management ipv6 route-table-import

Description

This command specifies the name of a route policy to control the importation of active routes from the IP route table into one of the BGP RIBs.

If the route-table-import command is not configured, or if the command refers to an empty policy, all non-BGP routes from the IP route table are imported into the applicable RIB.

If the route-table-import command is configured, then routes dropped or rejected by the configured policy are not installed in the associated RIB. Rejected routes cannot be advertised to BGP peers associated with the RIB, but they can still be used to resolve BGP next-hops of routes in that RIB. If the active route for a prefix is rejected by the route-table-import policy, then the best BGP route for that prefix in the BGP RIB can be advertised to peers as though it is used.

Aggregate routes are always imported into each RIB, independent of the route-table-import policy.

Route modifications specified in the actions of a route-table-import policy are ignored and have no effect on the imported routes.

Default

no route-table-import

Parameters

policy-name

Specifies the name of a policy-statement (up to 64 characters).

Platforms

All

route-table-import

Syntax

route-table-import policy-name

no route-table-import

Context

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

[Tree] (config>router>bgp>rib-management>label-ipv6 route-table-import)

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

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

Full Context

configure router bgp rib-management ipv4 route-table-import

configure router bgp rib-management label-ipv6 route-table-import

configure router bgp rib-management ipv6 route-table-import

configure router bgp rib-management label-ipv4 route-table-import

Description

This command specifies the name of a policy to control the importation of active routes from the IP route table into one of the BGP RIBs.

If the route-table-import command is not configured, or if the command refers to an empty policy, all non-BGP routes from the IP route table are imported into the applicable RIB.

If the route-table-import command is configured, then routes dropped or rejected by the configured policy are not installed in the associated RIB. Rejected routes cannot be advertised to BGP peers associated with the RIB, but they can still be used to resolve BGP next-hops of routes in that RIB. If the active route for a prefix is rejected by the route-table-import policy, then the best BGP route for that prefix in the BGP RIB can be advertised to peers as though it is used.

Aggregate routes are always imported into each RIB, independent of the route-table-import policy.

Route modifications specified in the actions of a route-table-import policy are ignored and have no effect on the imported routes.

Default

no route-table-import

Parameters

policy-name

Specifies the name of a policy-statement (up to 64 characters).

Platforms

All

route-target

route-target

Syntax

route-target export ext-community import ext-community

no route-target

Context

[Tree] (config>subscr-mgmt>isa-svc-chain>evpn>bgp route-target)

Full Context

configure subscriber-mgmt isa-service-chaining evpn bgp route-target

Description

This command configures route target attributes to be signaled in EVPN routes used for service chaining.

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

Parameters

export

Specifies the route target to be used by BGP in this EVPN service when exporting EVPN routes.

import

Specifies the route target to be used by BGP in this EVPN service when importing EVPN routes.

ext-community

Specifies the extended community.

Values

rd: ip-addr:comm-val | 2byte-asnumber:ext-comm-val | 4byte-asnumber:comm-val

ip-addr: a.b.c.d

comm-val: [0 to 65535]

2byte-asnumber: [1 to 65535]

ext-comm-val: [0 to 4294967295]

4byte-asnumber: [1 to 4294967295]

Platforms

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

route-target

Syntax

route-target {ext-community | {[export ext-community][import ext-community]}}

no route-target

Context

[Tree] (config>service>epipe>bgp route-target)

[Tree] (config>service>vpls>bgp-ad route-target)

[Tree] (config>service>vpls>bgp route-target)

Full Context

configure service epipe bgp route-target

configure service vpls bgp-ad route-target

configure service vpls bgp route-target

Description

This command configures the route target (RT) component that will be signaled in the related MP- BGP attribute to be used for BGP auto-discovery, BGP VPLS, BGP multi-homing and EVPN if these features are configured in this VPLS service, or for BGP multi-homing, BGP-VPWS and EVPN in case of Epipe services.

If this command is not used in VPLS services, the RT is built automatically using the VPLS ID. The extended community can have the same two formats as the VPLS ID, a two-octet AS-specific extended community, IPv4 specific extended community. For BGP EVPN enabled VPLS and Epipe services, the route target can also be auto-derived from the evi value (config>service>vpls>bgp-evpn>evi or config>service>epipe>bgp-evpn>evi) if this command is not configured.

Parameters

export ext-community

Specifies communities allowed to be sent to remote PE neighbors.

import ext-community

Specifies communities allowed to be accepted from remote PE neighbors.

Platforms

All

route-target-list

route-target-list

Syntax

route-target-list comm-id [comm-id]]

no route-target-list [comm-id]

Context

[Tree] (config>router>bgp route-target-list)

Full Context

configure router bgp route-target-list

Description

This command specifies the route target(s) to be accepted from or advertised to peers. If the route-target-list is a non-null list, only routes with one or more of the given route targets are accepted from or advertised to peers.

The route-target-list is assigned at the global level and applies to all peers connected to the system.

This command is only applicable if the router is a route-reflector server.

The no form of this command with a specified route target community removes the specified community from the route-target-list. The no form of this command entered without a route target community removes all communities from the list.

Default

no route-target-list

Parameters

comm-id

Specifies up to 15 route target communities.

Values

[target: {ip-address:comm-val | 2byte-asnumber:ext-comm-val | 4byte-asnumber:comm-val}

where:

  • ip-address — a.b.c.d

  • comm-val — 0 to 65535

  • 2byte-asnumber — 0 to 65535

  • ext-comm-val — 0 to 4294967295

  • 4byte-asnumber — 0 to 4294967295

Platforms

All

route-unknown

route-unknown

Syntax

[no] route-unknown [{ip-prefix/mask | ipv6-address/prefix-length}]

Context

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

Full Context

configure vrrp policy priority-event route-unknown

Description

This command creates a context to configure a route unknown priority control event that monitors the existence of a specific active IP route prefix within the routing table.

The route-unknown command configures a priority control event that defines a link between the VRRP priority control policy and the Route Table Manager (RTM). The RTM registers the specified route prefix as monitored by the policy. If any change (add, delete, new next hop) occurs relative to the prefix, the policy is notified and takes correct action according to the priority event definition. If the route prefix exists and is active in the routing table according to the conditions defined, the event is in the cleared state. If the route prefix is removed, becomes inactive or fails to meet the event criteria, the event is in the set state.

The command creates a route-unknown node identified by prefix/mask-length and containing event control commands.

Multiple unique (different prefix/mask-length) route-unknown event nodes can be configured within the priority-event node up to the maximum limit of 32 events.

The route-unknown command can reference any valid IP address mask-length pair. The IP address and associated mask length define a unique IP router prefix. The dynamic monitoring of the route prefix results in one of the event operational states listed in Route-unknown Operational States.

Table 3. Route-unknown Operational States

route-unknown Operational State

Description

Set – non-existent

The route does not exist in the route table

Set – inactive

The route exists in the route table but is not being used

Set – wrong next hop

The route exists in the route table but does not meet the next-hop requirements

Set – wrong protocol

The route exists in the route table but does not meet the protocol requirements

Set – less specific found

The route exists in the route table but does is not an exact match and does not meet any less-specific requirements

Set – default best match

The route exists in the route table as the default route but the default route is not allowed for route matching

Cleared – less specific found

A less specific route exists in the route table and meets all criteria including the less-specific requirements

Cleared – found

The route exists in the route table manager and meets all criteria

An existing route prefix in the RTM must be active (used by the IP forwarding engine) to clear the event operational state. It may be less specific (the defined prefix may be contained in a larger prefix according to Classless Inter-Domain Routing (CIDR) techniques) if the event has the less-specific statement defined. The less specific route that incorporates the router prefix may be the default route (0.0.0.0) if the less-specific allow-default statement is defined. The matching prefix may be required to have a specific next hop IP address if defined by the event next-hop command. Finally, the source of the RTM prefix may be required to be one of the dynamic routing protocols or be statically defined if defined by the event protocol command. If an RTM prefix is not found that matches all the above criteria (if defined in the event control commands), the event is considered to be set. If a matching prefix is found in the RTM, the event is considered to be cleared.

When an event transitions from clear to set, the set is processed immediately and must be reflected in the associated virtual router instances in-use priority value. As the event transitions from clear to set, a hold-set timer is loaded with the value configured by the events hold-set command. This timer prevents the event from clearing until it expires, damping the effect of event flapping. If the event clears and becomes set again before the hold-set timer expires, the timer is reset to the hold-set value, extending the time before another clear can take effect.

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

Default

no route-unknown — No route unknown priority control events are defined for the priority control event policy.

Parameters

ip-prefix/mask

The IP prefix address in dotted decimal notation and the subnet mask length expressed as a decimal integer associated with the IP prefix defining the route prefix to be monitored by the route unknown priority control event.

Values

The following values apply to the 7750 SR, 7950 XRS, and 7450 ESS:

ip-prefix/mask:

ip-prefix

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

mask

0 to 32

ipv6-address/prefix-length

The IPv6 address of the host for which the specific event will monitor connectivity. The ipv6-address can only be monitored by a single event in this policy. The IPv6 address can be monitored by multiple VRRP priority control policies. The IPv6 address can be used in one or multiple ping requests. Each VRRP priority control host-unreachable and ping destined to the same ipv6-address is uniquely identified on a per message basis. Each session originates a unique identifier value for the ICMP echo request messages it generates. This allows received ICMP echo reply messages to be directed to the appropriate sending application.

Values

The following values apply to the 7750 SR and 7950 XRS:

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

prefix-length

0 to 128

Platforms

All

routed-subnet-transparent-forward

routed-subnet-transparent-forward

Syntax

[no] routed-subnet-transparent-forward

Context

[Tree] (config>router>subscriber-mgmt>dhcpv4 routed-subnet-transparent-forward)

[Tree] (config>service>vprn>subscriber-mgmt>dhcpv4 routed-subnet-transparent-forward)

Full Context

configure router subscriber-mgmt dhcpv4 routed-subnet-transparent-forward

configure service vprn subscriber-mgmt dhcpv4 routed-subnet-transparent-forward

Description

This command configures the transparent forwarding of DHCPv4 packets that are received on a subscriber interface with a source IP in a routed subnet that is associated with a routed IPoE session or host. Supported routed subnets are RADIUS and NASREQ framed routes or routes learned via an ESM dynamic BGP peer and managed routes associated with a static IPv4 host.

The no form of this command disables transparent forwarding of DHCPv4 packets.

Default

no routed-subnet-transparent-forward

Platforms

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

router

router

Syntax

router router-instance

router service-name service-name

no router

Context

[Tree] (config>aaa>l2tp-acct-plcy>radius-acct-server router)

Full Context

configure aaa l2tp-accounting-policy radius-accounting-server router

Description

This command specifies the number of times the router attempts to contact the RADIUS server for authentication, if not successful the first time.

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

Parameters

router-instance

Specifies the router instance.

Values

router-name | vprn-svc-id

router-name

Base, management

Default - Base

vprn-svc-id

1 to 2147483647

service-name

Specifies the service name, up to 64 characters.

Platforms

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

router

Syntax

router router-instance

router service-name service-name

no router

Context

[Tree] (config>app-assure>rad-acct-plcy>server router)

Full Context

configure application-assurance radius-accounting-policy radius-accounting-server router

Description

This command specifies the number of times the router attempts to contact the RADIUS server for authentication, if not successful the first time.

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

Default

no router

Parameters

router-instance

Specifies the router name or service ID used to specify the router instance.

service-name

Specifies the service name to identify the service, up to 64 characters.

Platforms

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

router

Syntax

router router-instance

router service-name service-name

no router

Context

[Tree] (config>subscr-mgmt>auth-plcy>radius-auth-server router)

[Tree] (config>subscr-mgmt>acct-plcy>server router)

Full Context

configure subscriber-mgmt authentication-policy radius-authentication-server router

configure subscriber-mgmt radius-accounting-policy radius-accounting-server router

Description

This command specifies the virtual router instance applicable for the set of configured RADIUS servers. This value cannot be changed once a RADIUS server is configured for this policy. When the value is zero, both base and management router instances are matched.

The no form of this command reverts to the default.

Parameters

router-instance

Specifies the virtual router instance

Values

router-name:

Base, management

service-id:

1 to 2147483647

service-name

Specifies the service name, up to 64 characters..

Platforms

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

router

Syntax

router router-instance

router service service-name

no router

Context

[Tree] (config>aaa>diam>node router)

Full Context

configure aaa diameter node router

Description

This command references the routing-instance from which diameter peering connection is initiated.

The no form of this command reverts to the default.

Default

router "Base”

Parameters

router-instance

Specifies the router instance.

Values

router-name | vprn-svc-id

router-name: Base, management Default - Base

vprn-svc-id: 1 to 2147483647

service-name

Specifies the service name, up to 64 characters.

Platforms

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

router

Syntax

router router-instance

no router

Context

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

Full Context

configure subscriber-mgmt wlan-gw tunnel-query router

Description

This command enables matching only on tunnels that are terminated in the specified routing instance.

The no form of this command disables matching on a routing instance.

Default

no router

Parameters

router-instance

Specifies the routing instance in the form of router-name or vprn-svc-id.

Values

router-name — Base

vprn-svc-id — 1 to 2147483647

Platforms

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

router

Syntax

router router-instance

router service-name service-name

no router

Context

[Tree] (config>aaa>radius-srv-plcy>servers router)

Full Context

configure aaa radius-server-policy servers router

Description

This command specifies the virtual router instance applicable for the set of configured RADIUS servers. This value cannot be changed once a RADIUS server is configured for this policy.

The no form of this command reverts to the default.

Parameters

router-instance

Specifies the router instance.

Values

service-name

Service name, up to 64 characters.

router-instance:

router-name, service-id

router-name:

Base, management

service-id:

1 to 2147483647

service-name

Specifies the router name service-id up to 64 characters.

Platforms

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

router

Syntax

router router-instance

no router

Context

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw router)

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

Full Context

configure service vprn subscriber-interface group-interface wlan-gw router

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

Description

This command specifies the routing instance that wlan-gw gateway endpoint resides in.

The no form of this command removes the value from the wlan-gw configuration.

Default

router

Parameters

router-instance

Specifies the identifier of the virtual router instance where the tunneled UE traffic is routed.

Platforms

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

router

Syntax

router [router-instance] [create]

no router [router-instance]

Context

[Tree] (config router)

Full Context

configure router

Description

Commands in this context configure router parameters including interfaces, route policies and protocols. This command is also used to create CPM router instances.

For CPM router instances, this command enters or creates a user-created CPM router instance. A CPM router instance is a not a VPRN router instance. VPRN router instances are configured under configure service vprn. CPM router instances are the only type of non-VPRN router instances that can be created by a user, and they have a user-defined name. CPM router instances only use CPM/CCM ethernet ports as interfaces.

Parameters

router-instance

Specifies the router name or CPM router instance.

Values

router-instance : router name

router-name

Base | management | cpm-vr-name

cpm-vr-name

[32 characters maximum]

Default

Base

create

Mandatory keyword when creating a router instance. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

All

router

Syntax

router router-instance group tunnel-group-name

router group tunnel-group-name service-name service-name

no router

Context

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

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

Full Context

configure service epipe sap l2tpv3-session router

configure service vpls sap l2tpv3-session router

Description

This command configures the service and L2TPv3 group to which this L2TPv3 session should be associated. The associated services are used to provide transport for the L2TPv3 tunnel. The service can be specified with either the service-name or router ID. The group name specifies the L2TPv3 group parameters that should be associated with the session.

The no form of this command deletes the router configuration.

Parameters

router-instance

Specifies the router name or service ID used to identify the router instance.

Values

router-instance: router-name or vprn-svc-id

router-name

"Base”

vprn-svc-id

1 to 2147483647

Default

Base

tunnel-group-name

Specifies the tunnel group name, up to 32 characters.

service-name

Specifies the service name, up to 64 characters.

Platforms

All

router

Syntax

router [router-instance]

router service-name service-name

Context

[Tree] (debug router)

Full Context

debug router

Description

Commands in this context enable debugging of various protocols and areas of a router-instance.

Parameters

router-instance

Specifies the router name, CPM router instance, or service ID.

Values

router-name or service-id

router-instance : router-name

router-name

Base | management | cpm-vr-name

cpm-vr-name

[32 characters maximum]

service-id: 1 to 2147483647

Default

Base

service-name

Specifies the service name, up to 64 characters.

Platforms

All

router

Syntax

router router-instance

router service vprn-service-name

Context

[Tree] (config>system>file-trans-prof router)

Full Context

configure system file-transmission-profile router

Description

This command specifies the routing instance that the transport protocol uses.

Default

router Base

Parameters

router-instance

Specifies the router instance on which the file transmission connection will be established.

This variant of this command is only supported in 'classic' configuration-mode (configure system management-interface configuration-mode classic). The router service vprn-service-name variant can be used in all configuration modes.

Values

{router-name | vprn-svc-id}

router-name:

Base, management

router-name is an alias for input only. The router-name gets replaced with an id automatically by SR OS in the configuration).

vprn-svc-id:

1 to 2147483647

Default

Base

service vprn-service-name

Identifies the service, up to 64 characters.

Platforms

All

router

Syntax

router router-instance

router service vprn-service-instance

no router

Context

[Tree] (config>system>management-interface>remote-management router)

Full Context

configure system management-interface remote-management router

Description

This command defines the router instance in which all remote managers are reachable.

If this command is also configured for a specific manager in the config>system> management-interface>remote-management>manager context, that configuration takes precedence.

The no form of this command configures management as the router (default).

Default

router management

Parameters

router-instance

Specifies a router instance on which the remote management connection is established, up to 32 characters.

service vprn-service-instance

Specifies a VPRN service instance, up to 64 characters.

Platforms

All

router

Syntax

router router-instance

router service vprn-service-instance

no router

Context

[Tree] (config>system>management-interface>remote-management>manager router)

Full Context

configure system management-interface remote-management manager router

Description

This command defines the router instance in which this manager is reachable.

This command takes precedence over the same command configured in the global context (config>system>management-interface>remote-management).

The no form of this command causes the router to be inherited from the global context (config>system>management-interface>remote-management).

Default

management

Parameters

router-instance

Specifies the router instance on which the remote management connection is established for this manager, up to 32 characters.

service vprn-service-instance

Specifies a VPRN service instance, up to 64 characters.

Platforms

All

router

Syntax

router router-instance

no router

Context

[Tree] (config>isa>nat-group>inter-chassis-redundancy router)

Full Context

configure isa nat-group inter-chassis-redundancy router

Description

This command configures routing instance through which ISAs communicate between redundant nodes and synchronize their flow state.

The no form of this command removes the router instance from the configuration.

Default

no router

Parameters

router-instance

Specifies the router name or service ID for the router instance.

Values

<router-name>| <vprn-svc-id>

router-name: "Base"

vprn-svc-id: 1 to 2147483647

Platforms

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

router

Syntax

router router-instance

router service-name service-name

no router

Context

[Tree] (config>aaa>isa-radius-plcy>servers router)

Full Context

configure aaa isa-radius-policy servers router

Description

This command specifies the number of times the router attempts to contact the RADIUS server for authentication, if not successful the first time.

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

Default

no router

Platforms

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

router

Syntax

router router-instance

router service-name service-name

no router

Context

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

Full Context

configure mirror mirror-dest encap layer-3-encap router

Description

This command specifies the routing instance into which to inject the mirrored packets. The packets are forwarded in the routing instance based on the configurable destination IP address in the inserted IP header. If a mirror-dest is configured to inject into a VPRN service, then that VPRN service cannot be deleted. A mirror-dest with layer-3-encap is set to operationally down if the configured destination IP address is not reachable via an interface in the routing instance or service configured for the mirror-dest. No changes are allowed to the router configuration once a gateway is configured. A service must already exist before it is specified as a router-instance. VPRN and IES services share the same number space for the service-id, but IES services cannot be specified as the router-instance for routable LI encap.

Forwarding of routable encapsulated LI packets out an R-VPLS interface is not supported. A mirror-dest configured with routable encapsulation can be bound to a routing instance that also has an R-VPLS bound to it but the operator must ensure that the destination of the LI packets is not reachable via any R-VPLS interfaces. Any routable encapsulated LI packets that arrive at the egress of an R-VPLS interface are discarded. Parallel use of routable LI encapsulation and R-VPLS in the same routing instance is supported as long as the mirrored packets do not egress out the R-VPLS interface.

Default

router Base

Parameters

router-instance

Specifies the router instance.

Values

<router-name> | <service-id>

router-name

"Base”, name

service-id

1 to 2147483647

service-name

Specifies the service name, up to 64 characters.

Platforms

All

router

Syntax

router router-instance

no router

Context

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

Full Context

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

Description

This command specifies the routing instance into which to inject the mirrored packets. The packets will be forwarded in the routing instance based on the configurable destination IP address in the inserted IP header. This parameter can be overridden by RADIUS.

If a mirror destination is configured to inject into a VPRN service, that VPRN service cannot be deleted. A mirror destination with Layer 3 encapsulation will be set to operationally down if the configured destination IP address is not reachable via an interface in the routing instance or service configured for the mirror destination. A service must exist before it is specified as a router instance. VPRN and IES services share the same number space for the service ID; however, IES services cannot be specified as the router instance for routable LI encapsulation.

Default

router "Base”

Parameters

router-instance

Specifies the router instance using the router name or service ID.

Values

router-instance

router-name | vprn-svc-id

router-name

"Base”

vprn-svc-id

1 to 2147483647

Platforms

All

router

Syntax

router router-name

no router

Context

[Tree] (config>li>x-interfaces>lics>lic router)

Full Context

configure li x-interfaces lics lic router

Description

This command configures the router instance that the X-interfaces must use for communication.

The no form of this command reverts to the default.

Parameters

router-name

Specifies the router name or VPRN service ID.

Values

<router-name>, <vprn-svc-id>

router-name

Base

vprn-svc-id

1 to 2147483647

Platforms

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

router

Syntax

router router-or-service

router service-name service-name

no router

Context

[Tree] (config>oam-pm>session>ip router)

Full Context

configure oam-pm session ip router

Description

This command numerically references the source context from which the TWAMP Light packet is launched. The router-instance router-instance configuration, under the same context as the router command, is the preferred method for referencing. This method references the launch context by name, and not number, or alias that converts service-name to a number.

The no form of this command restores the default value.

Parameters

router-or-service

Specifies the numerical reference to the router instance or service. Well known router-name "Base" is allowed for convenience, but mapped numerically.

Values

{router-name | vprn-svc-id}

router-name:

Base

vprn-svc-id:

1 to 2147483647

The parameter router-instance is preferred for specifying the router or service.

service-name

Specifies the alias function that allows the service-name to be used converted and stored as service ID, up to 64 characters. The parameter router-instance is preferred for specifying the router or service.

Platforms

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

router

Syntax

no router router-instance interface interface-name

router router-instance interface interface-name [direction {ingress | egress | both}]

Context

[Tree] (config>cflowd>collector>exp-filter>if-list router)

Full Context

configure cflowd collector export-filter interface-list router

Description

This command configures the interface flow data sent to this collector.

The no form of this command removes the specified interface from the interface-list filter.

Parameters

router-instance

Specifies the router instance ID associated with the interface name

Values

router-name | vprn-svc-id

router-name: Base, management Default - Base

vprn-svc-id: 1 to 2147483647

interface-name

Specifies the interface name, up to 32 characters and must start with a letter, for the router to the service interface or SAP.

ingress

Keyword to specify that ingress flows are sent to the associated Cflowd Collector.

Default

both

egress

Keyword to specify that egress flows are sent to the associated Cflowd Collector.

Default

both

both

Keyword to specify that both ingress and egress flows are sent to the associated Cflowd Collector.

Default

both

Platforms

All

router

Syntax

[no] router router-instance

Context

[Tree] (config>cflowd>collector>export-filter router)

Full Context

configure cflowd collector export-filter router

Description

This command allows the flow data from only specific router instances to be sent to the associated collector.

Multiple router instances can be configured by issuing the command multiple times with the different router-instances.

The no form of this command removes the specified router-instance restriction, which means flows from that router-instance will no longer be exported. If all router-instances are removed, then flows from all router instances are sent to the associated collector.

Default

no router

Parameters

router-instances

Specifies the router name or router instance VPRN service ID. Only "Base” is supported.

Values

router-name: Base, management Default - management

vprn-svc-id: 1 to 2147483647

Platforms

All

router

Syntax

router {router-name | vprn-svc-id}

Context

[Tree] (config>cflowd>collector router)

Full Context

configure cflowd collector router

Description

This command configures the flow data sent to the associated collector to be sent within the specified router context. If this parameter is not specified, flow data is exported using the management routing context.

Default

router management

Parameters

router-name

Specifies the router name.

Values

Base, management

Default

management

vprn-svc-id

Specifies the router instance VPRN service ID.

Values

1 to 2147483647

Platforms

All

router

Syntax

router router-instance

router service-name service-name

no router

Context

[Tree] (config>filter>redirect-policy router)

Full Context

configure filter redirect-policy router

Description

This command enhances VRF support in redirect policies. When a router instance is specified, the configured destination tests are run in the specified router instance, and the PBR action is executed in the specified router instance. If no destination is active or if the hardware does not support PBR action "next-hop router”, action forward will be executed (i.e. routing will be performed in the context of the incoming interface routing instance).

The no form of the command preserves backward-compatibility. Tests always run in the "Base” routing instance context, and the PBR action executes in the routing context of the ingress interface that the filter using this redirect policy is deployed on.

Default

no router

Parameters

router-instance

Specifies a router instance in the form of router-name or service-id.

Values

router-name — Base

service-id — Specifies an existing Layer 3 service [1 to 2147483647]

service-name

Specifies the name of a configured Layer 3 service.

Platforms

All

router

Syntax

router {eq | neq} router-instance [regexp]

no router

Context

[Tree] (config>log>filter>entry>match router)

Full Context

configure log filter entry match router

Description

This command specifies the log event matches for the router instance using a special vrtr-name format used by the logging system.

The no form of this command removes the log event matches.

Parameters

eq

Determines if the matching criteria should be equal to the specified value.

neq

Determines if the matching criteria should not be equal to the specified value.

router-instance

Specifies a router name, up to 32 characters, to be used in the match criteria. The router-instance in this command is a name for a router instance in a special format used in the logging system (called the vrtr-name). Examples of vrtr-names include Base and vprn101 (where 101 is the service-id of the VPRN service). It represents the router instance that generated the log event.

regexp

Specifies the type of string comparison to use to determine if the log event matches the value of the specified router instance. When the regexp keyword is specified, the string in the router command is a regular expression string that is matched against the vrtr-name string in the log event being filtered.

Platforms

All

router

Syntax

router service-name service-name

router router-instance

no router

Context

[Tree] (config>system>security>mgmt-access-filter>ip-filter>entry router)

[Tree] (config>system>security>mgmt-access-filter>ipv6-filter>entry router)

Full Context

configure system security management-access-filter ip-filter entry router

configure system security management-access-filter ipv6-filter entry router

Description

This command configures a router name or service ID to be used as a management access filter match criterion.

The no form the command removes the router name or service ID from the match criteria.

Parameters

router-instance

Specifies one of the following parameters for the router instance:

router-name — Specifies a router name or CPM router instance, up to 32 characters to be used in the match criteria.

Values

"Base” | "management” | "vpls-management”

Default

Base

vprn-svc-id — Specifies a CPM router instance to be used in the match criteria.

Values

1 to 2147483647

service name

Specifies an existing service name, up to 64 characters.

Platforms

All

router

Syntax

router service-name service-name

router router-instance

no router

Context

[Tree] (cfg>sys>sec>cpm>ip-filter>entry>match router)

[Tree] (cfg>sys>sec>cpm>ipv6-filter>entry>match router)

Full Context

configure system security cpm-filter ip-filter entry match router

configure system security cpm-filter ipv6-filter entry match router

Description

This command specifies a router name or a service-id to be used in the match criteria.

Default

no router

Parameters

router-instance

Specifies one of the following parameters for the router instance:

router-name — Specifies a router name up to 32 characters to be used in the match criteria.

service-id — Specifies an existing service ID to be used in the match criteria.

Values

1 to 2147483647

service-name

Specifies an existing service name, up to 64 characters.

Platforms

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

router

Syntax

router service-name service-name

router router-instance

no router

Context

[Tree] (config>bmp>station>connection router)

Full Context

configure bmp station connection router

Description

This command configures the router instance to be used to connect to the associate BMP monitoring station.

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

Parameters

service-name

Specifies the name associated with the VPRN service through which the BMP monitoring station connection should traverse.

router-instance

Specifies the routing instance where the lead pool resides.

Values

router-name | vprn-service-id

router-name: "Base" Default - Base

vprn-svc-id: 1 to 2147483647

service-name: The service name up to 64 characters in length.

Platforms

All

router-advertisement

router-advertisement

Syntax

[no] router-advertisement

Context

[Tree] (config>service>vprn router-advertisement)

Full Context

configure service vprn router-advertisement

Description

This command configures router advertisement properties. By default, it is disabled for all IPv6 enabled interfaces.

The no form of this command disables all IPv6 interface. However, the no interface interface-name command disables a specific interface.

Default

no router-advertisement

Platforms

All

router-advertisement

Syntax

[no] router-advertisement

Context

[Tree] (config>router router-advertisement)

Full Context

configure router router-advertisement

Description

This command configures router advertisement properties. By default, it is disabled for all IPv6 enabled interfaces.

The no form of this command disables all IPv6 interface. However, the no interface interface-name command disables a specific interface.

Default

disabled

Platforms

All

router-advertisement-policy

router-advertisement-policy

Syntax

router-advertisement-policy policy

no router-advertisement-policy

Context

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host router-advertisement-policy)

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host router-advertisement-policy)

Full Context

configure subscriber-mgmt local-user-db ppp host router-advertisement-policy

configure subscriber-mgmt local-user-db ipoe host router-advertisement-policy

Description

This command applies an RA policy to the host.

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

Parameters

policy

Specifies the policy name, up to 32 characters.

Platforms

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

router-advertisement-policy

Syntax

router-advertisement-policy name [create]

no router-advertisement-policy name

Context

[Tree] (config>subscr-mgmt router-advertisement-policy)

Full Context

configure subscriber-mgmt router-advertisement-policy

Description

This command creates a router advertisement policy or enters the context to configure a router advertisement policy. The keyword create is mandatory when creating a router advertisement policy the first time.

The no form of this command deletes the specified router advertisement policy.

Parameters

name

Specifies the router advertisement policy name up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

create

Specifies the keyword used to create the router advertisement policy. 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

router-advertisements

router-advertisements

Syntax

[no] router-advertisements

Context

[Tree] (config>service>vprn>sub-if>grp-if>ipv6 router-advertisements)

[Tree] (config>service>vprn>sub-if>ipv6 router-advertisements)

[Tree] (config>service>ies>sub-if>ipv6 router-advertisements)

[Tree] (config>service>ies>sub-if>grp-if>ipv6 router-advertisements)

Full Context

configure service vprn subscriber-interface group-interface ipv6 router-advertisements

configure service vprn subscriber-interface ipv6 router-advertisements

configure service ies subscriber-interface ipv6 router-advertisements

configure service ies subscriber-interface group-interface ipv6 router-advertisements

Description

This command enables IPv6 router advertisements for this interface.

The no form of this command disables the router advertisements.

Default

router-advertisements

Platforms

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

router-id

router-id

Syntax

router-id ip-address

no router-id

Context

[Tree] (config>service>vprn router-id)

[Tree] (config>service>vprn>bgp router-id)

[Tree] (config>service>vprn>ospf router-id)

Full Context

configure service vprn router-id

configure service vprn bgp router-id

configure service vprn ospf router-id

Description

This command sets the router ID for a specific VPRN context.

When configuring the router ID in the base instance of OSPF it overrides the router ID configured in the config>router context. The default value for the base instance is inherited from the configuration in the config>router context. If the router ID in the config>router context is not configured, the following applies:

  • The system uses the system interface address (which is also the loopback address).

  • If a system interface address is not configured, use the last 32 bits of the chassis MAC address.

If neither the router ID nor system interface are defined, the router ID from the base router context is inherited.

This is a required command when configuring multiple instances and the instance being configured is not the base instance.

When configuring a new router ID, the instance is not automatically restarted with the new router ID. The next time the instance is initialized, the new router ID is used.

To force the new router ID to be used, issue the shutdown and no shutdown commands for the instance, or reboot the entire router.

It is possible to configure an SR OS to operate with an IPv6 only BOF and no IPv4 system interface address. When configured in this manner, the operator must explicitly define IPv4 router IDs for protocols such as OSPF and BGP as there is no mechanism to derive the router ID from an IPv6 system interface address.

The no form of this command removes the router ID definition from the given VPRN context.

Default

no router-id

Parameters

ip-address

The IP address must be given in dotted decimal notation.

Platforms

All

router-id

Syntax

router-id ip-address

no router-id

Context

[Tree] (config>service>vprn>isis router-id)

Full Context

configure service vprn isis router-id

Description

This command sets the router ID for a specific VPRN context.

If neither the router ID nor system interface are defined, the router ID from the base router context is inherited.

The no form of this command removes the router ID definition from the given VPRN context.

Default

no router-id

Parameters

ip-address

The IP address must be given in dotted decimal notation.

Platforms

All

router-id

Syntax

[no] router-id ip

Context

[Tree] (config>router>mpls>srlg-database router-id)

Full Context

configure router mpls srlg-database router-id

Description

Commands in this context configure the link members of SRLG groups for a specific router in the network. The user must also use this command to enter the local interface SRLG membership into the user SRLG database. Use by CSPF of all interface SRLG membership information of a specific router ID may be temporarily disabled by shutting down the node. If this occurs, CSPF assumes these interfaces have no SRLG membership association.

The no form of this command will delete all interface entries under the router ID.

Parameters

ip-address

Specifies the router ID for this system. This must be the router ID configured under the base router instance, the base OSPF instance or the base IS-IS instance.

Platforms

All

router-id

Syntax

router-id ip-address

no router-id

Context

[Tree] (config>router router-id)

Full Context

configure router router-id

Description

This command configures the router ID for the router instance.

The router ID is used by both OSPF and BGP routing protocols in this instance of the routing table manager. IS-IS uses the router ID value as its system ID.

When configuring a new router ID, protocols are not automatically restarted with the new router ID. The next time a protocol is initialized, the new router ID is used. This can result in an interim period of time when different protocols use different router IDs.

It is possible to configure SR OS to operate with an IPv6 only BOF and no IPv4 system interface address. When configured in this manner, the operator must explicitly define IPv4 router IDs for protocols such as OSPF and BGP as there is no mechanism to derive the router ID from an IPv6 system interface address.

To force the new router ID to be used, issue the shutdown and no shutdown commands for each protocol that uses the router ID, or restart the entire router.

The system uses the system interface address which is also the loopback address. If a system interface address is not configured, use the last 32 bits of the chassis MAC address.

The no form of this command removes the configured value and the last 32 bits of the chassis MAC address are used.

Default

no router-id

Parameters

ip-address

Specifies the 32 bit router ID expressed in dotted decimal notation or as a decimal value.

Platforms

All

router-id

Syntax

router-id ip-address

no router-id

Context

[Tree] (config>router>bgp router-id)

Full Context

configure router bgp router-id

Description

This command specifies the router ID to be used with this BGP instance.

Changing the BGP router ID on an active BGP instance causes the BGP instance to restart with the new router ID.

It is possible to configure an SR OS to operate with an IPv6 only BOF and no IPv4 system interface address. When configured in this manner, the operator must explicitly define IPv4 router IDs for protocols such as OSPF and BGP as there is no mechanism to derive the router ID from an IPv6 system interface address.

When no router-id is configured for BGP, the system interface IP address is used.

Default

no router-id

Parameters

ip-address

Specifies the router ID, expressed as any non-zero value in the range 0.0.0.1 to 255.255.255.255 (or when converted to decimal it can have any value in the range 1-4294967295). It is recommended to use the system IPv4 address.

Platforms

All

router-id

Syntax

router-id router-id

no router-id

Context

[Tree] (config>router>isis router-id)

Full Context

configure router isis router-id

Description

This command configures the router ID.

The no form of this command deletes the router ID.

Parameters

router-id

The IP address of the router.

Platforms

All

router-id

Syntax

router-id ip-address

no router-id

Context

[Tree] (config>router>ospf3 router-id)

[Tree] (config>router>ospf router-id)

Full Context

configure router ospf3 router-id

configure router ospf router-id

Description

This command configures the router ID for the OSPF instance. This command configures the router ID for the OSPF instance.

When configuring the router ID in the base instance of OSPF it overrides the router ID configured in the config>router context.

The default value for the base instance is inherited from the configuration in the config>router context. If the router ID in the config>router context is not configured, the following applies:

  • the system uses the system interface address (which is also the loopback address)

  • if a system interface address is not configured, it uses the last 32 bits of the chassis MAC address

This is a required command when configuring multiple instances and the instance being configured is not the base instance.

When configuring a new router ID, the instance is not automatically restarted with the new router ID. The next time the instance is initialized, the new router ID is used.

To force the new router ID to be used, issue the shutdown and no shutdown commands for the instance, or reboot the entire router.

It is possible to configure an SR OS to operate with an IPv6 only BOF and no IPv4 system interface address. When configured in this manner, the operator must explicitly define IPv4 router IDs for protocols such as OSPF and BGP as there is no mechanism to derive the router ID from an IPv6 system interface address.

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

Platforms

All

router-instance

router-instance

Syntax

router-instance router-instance

no router-instance

Context

[Tree] (config>oam-pm>session>ip router-instance)

Full Context

configure oam-pm session ip router-instance

Description

This command references the source context from which the TWAMP Light packet is launched by name. The router-instance router-instance configuration is the preferred method for referencing and references the launch context by name, not number or alias that converts service-name to a number.

The no form of this command restores the default value.

Parameters

router-instance

Specifies the preferred method for entering a service name. Stored as the service name. Only the service linking function is allowed for both mixed-mode and model-driven configuration modes, up to 64 characters.

Platforms

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

router-instance

Syntax

router-instance router-instance

router-instance service vprn-service-instance

no router-instance

Context

[Tree] (config>system>telemetry>destination-group>destination router-instance)

[Tree] (config>system>grpc-tunnel>destination-group>destination router-instance)

Full Context

configure system telemetry destination-group destination router-instance

configure system grpc-tunnel destination-group destination router-instance

Description

This command configures the router instance for the destination group.

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

Default

router-instance management

Parameters

router-instance

Specifies the router instance type, up to 32 characters.

Values

management, base

vprn-service-instance

Specifies the VPRN service instance, up to 64 characters.

Platforms

All

router-lifetime

router-lifetime

Syntax

router-lifetime seconds

router-lifetime no-default-router

no router-lifetime

Context

[Tree] (config>subscr-mgmt>rtr-adv-plcy router-lifetime)

Full Context

configure subscriber-mgmt router-advertisement-policy router-lifetime

Description

This command specifies the router lifetime.

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

Default

router-lifetime 4500

Parameters

seconds

Specifies the time, in seconds, for the prefix to remain preferred.

Values

2700 to 9000

no-default-router

Specifies that the router is not to be used as a default router.

Platforms

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

router-lifetime

Syntax

router-lifetime seconds

router-lifetime no-default-router

no router-lifetime

Context

[Tree] (config>service>ies>sub-if>grp-if>ipv6>rtr-adv router-lifetime)

[Tree] (config>service>vprn>sub-if>grp-if>ipv6>rtr-adv router-lifetime)

[Tree] (config>service>ies>sub-if>ipv6>rtr-adv router-lifetime)

[Tree] (config>service>vprn>sub-if>ipv6>rtr-adv router-lifetime)

Full Context

configure service ies subscriber-interface group-interface ipv6 router-advertisements router-lifetime

configure service vprn subscriber-interface group-interface ipv6 router-advertisements router-lifetime

configure service ies subscriber-interface ipv6 router-advertisements router-lifetime

configure service vprn subscriber-interface ipv6 router-advertisements router-lifetime

Description

This command configures the value to be placed in the router lifetime field of router advertisements sent from this interface. A value of zero indicates this router should not be used by hosts as a default router.

The no form of this command reverts to the default.

Default

router-lifetime 4500

Parameters

seconds

Specifies the router lifetime in seconds for this group-interface.

Values

2700 to 9000

no-default-router

Specifies that the router is not to be used as a default router.

Platforms

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

router-lifetime

Syntax

router-lifetime seconds

no router-lifetime

Context

[Tree] (config>service>vprn>router-advert>if router-lifetime)

[Tree] (config>router>router-advert>if router-lifetime)

Full Context

configure service vprn router-advertisement interface router-lifetime

configure router router-advertisement interface router-lifetime

Description

This command sets the router lifetime.

Default

router life-time 1800

Parameters

seconds

The length of time, in seconds, (relative to the time the packet is sent) that the prefix is valid for route determination.

Values

0, 4 to 9000 seconds. 0 means that the router is not a default router on this link.

Platforms

All

router-solicit

router-solicit

Syntax

router-solicit

Context

[Tree] (config>service>vprn>sub-if>ipv6 router-solicit)

[Tree] (config>service>ies>sub-if>ipv6 router-solicit)

[Tree] (config>service>vprn>sub-if>grp-if>ipv6 router-solicit)

[Tree] (config>service>ies>sub-if>grp-if>ipv6 router-solicit)

Full Context

configure service vprn subscriber-interface ipv6 router-solicit

configure service ies subscriber-interface ipv6 router-solicit

configure service vprn subscriber-interface group-interface ipv6 router-solicit

configure service ies subscriber-interface group-interface ipv6 router-solicit

Description

Commands in this context configure parameters used for router-solicit based authentication.

Platforms

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

router-solicitation

router-solicitation

Syntax

[no] router-solicitation

Context

[Tree] (config>service>ies>sub-if>grp-if>ipv6>auto-reply router-solicitation)

[Tree] (config>service>vprn>sub-if>grp-if>ipv6>auto-reply router-solicitation)

Full Context

configure service ies subscriber-interface group-interface ipv6 auto-reply router-solicitation

configure service vprn subscriber-interface group-interface ipv6 auto-reply router-solicitation

Description

This command enables auto-reply router solicitation.

The no form of this command disables auto-reply router solicitation.

Default

router-solicitation

Platforms

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

router-target-as-number

router-target-as-number

Syntax

router-target-as-number as-number

no router-target-as-number

Context

[Tree] (config>subscr-mgmt>vrgw>lanext router-target-as-number)

Full Context

configure subscriber-mgmt vrgw lanext router-target-as-number

Description

This command specifies the AS number for the HLE service. It is used to derive the route target (RT) and route distinguisher (RD) for the HLE EVPN service only when the RADIUS server does not return a specific route target or route distinguisher.

The derived RT is in the "target:<configured-router-target-as-number>:<returned Alc-Bridge-Id>” format.

The derived RD is in the "<configured-router-target-as-number>:<returned Alc-Bridge-Id>” format.

The no form of this command removes the AS number from the configuration.

Parameters

as-number

Specifies the AS number of the HLE service.

Values

1 to 65535

Platforms

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

router-unsolicited-na-flood-evpn

router-unsolicited-na-flood-evpn

Syntax

[no] router-unsolicited-na-flood-evpn

Context

[Tree] (config>service>vpls>proxy-nd router-unsolicited-na-flood-evpn)

Full Context

configure service vpls proxy-nd router-unsolicited-na-flood-evpn

Description

This command controls whether the system floods router unsolicited Neighbor Advertisements to EVPN. The NA messages impacted by this command are NA messages with the following flags: S=0 and R=1.

The no form of the command will only flood to local SAPs/binds but not to EVPN destinations. This is only recommended in networks where CEs are routers directly connected to the PEs. Networks using aggregation switches between the host/routers and the PEs should flood unsolicited NA messages in EVPN to ensure that the remote caches are updated and BGP does not miss the advertisement of these entries.

Default

router-unsolicited-na-flood-evpn

Platforms

All

routing-type0

routing-type0

Syntax

routing-type0 {true | false}

no routing-type0

Context

[Tree] (config>filter>ipv6-filter>entry>match routing-type0)

Full Context

configure filter ipv6-filter entry match routing-type0

Description

This command enables match on existence of Routing Type Extension Header type 0 in the IPv6 filter policy.

The no form of this command ignores Routing Type Extension Header type 0 presence/absence in a packet when evaluating match criteria of a given filter policy entry.

Default

no routing-type0

Parameters

true

Specifies whether a packet contains Routing Type Extension Header type 0.

false

Specifies whether a packet does not contain Routing Type Extension Header type 0.

Platforms

All

rp

rp

Syntax

rp

Context

[Tree] (config>service>vprn>pim rp)

Full Context

configure service vprn pim rp

Description

This command enables access to the context to configure the rendezvous point (RP) of a PIM protocol instance.

A Nokia PIM router acting as an RP must respond to a PIM register message specifying an SSM multicast group address by sending stop register message(s) to the first hop router. It does not build an (S, G) shortest path tree toward the first hop router. An SSM multicast group address can be either from the SSM default range of 232/8 or from a multicast group address range that was explicitly configured for SSM.

Default

rp enabled when PIM is enabled.

Platforms

All

rp

Syntax

rp

Context

[Tree] (config>router>pim rp)

Full Context

configure router pim rp

Description

Commands in this context configure rendezvous point (RP) parameters. The address of the root of the group’s shared multicast distribution tree is known as its RP. Packets received from a source upstream and join messages from downstream routers rendezvous at this router.

If this command is not enabled, then the router can never become the RP.

Platforms

All

rp-candidate

rp-candidate

Syntax

rp-candidate

Context

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

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

Full Context

configure service vprn pim rp rp-candidate

configure service vprn pim rp ipv6 rp-candidate

Description

Commands in this context configure the candidate rendezvous point (RP) parameters.

Default

enabled when PIM is enabled

Platforms

All

rp-candidate

Syntax

rp-candidate

Context

[Tree] (config>router>pim>rp rp-candidate)

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

Full Context

configure router pim rp rp-candidate

configure router pim rp ipv6 rp-candidate

Description

Commands in this context configure the Candidate RP parameters.

Routers use a set of available rendezvous points distributed in Bootstrap messages to get the proper group-to-RP mapping. A set of routers within a domain are also configured as candidate RPs (C-RPs); typically, these will be the same routers that are configured as candidate BSRs.

Every multicast group has a shared tree through which receivers learn about new multicast sources and new receivers learn about all multicast sources. The rendezvous point (RP) is the root of this shared tree.

Default

rp-candidate shutdown

Platforms

All

rp-set-peer

rp-set-peer

Syntax

[no] rp-set-peer ip-address

Context

[Tree] (config>service>vprn>pim>rp>anycast rp-set-peer)

Full Context

configure service vprn pim rp anycast rp-set-peer

Description

This command configures a peer in the anycast RP-set. The address identifies the address used by the other node as the RP candidate address for the same multicast group address range as configured on this node.

This is a manual procedure. Caution should be taken to produce a consistent configuration of an RP-set for a given multicast group address range. The priority should be identical on each node and be a higher value than any other configured RP candidate that is not a member of this RP-set.

Although there is no set maximum of addresses that can be configured in an RP-set, up to 15 multicast addresses is recommended.

The no form of this command removes an entry from the list.

Parameters

ip-address

Specifies the address used by the other node as the RP candidate address for the same multicast group address range as configured on this node.

Platforms

All

rp-set-peer

Syntax

[no] rp-set-peer ipv6-address

Context

[Tree] (config>service>vprn>pim>rp>ipv6>anycast rp-set-peer)

Full Context

configure service vprn pim rp ipv6 anycast rp-set-peer

Description

This command configures an IPv6 peer in the anycast rp-set. The address identifies the address used by the other node as the RP candidacy address for the same multicast group address range as configured on this node.

This is a manual procedure. Caution should be taken to produce a consistent configuration of an RP- set for a given multicast group address range. The priority should be identical on each node and be a higher value than any other configured RP candidate that is not a member of this rp-set.

Although there is no set maximum of addresses that can be configured in an rp-set, up to 15 multicast addresses is recommended.

The no form of this command removes an entry from the list.

Parameters

ipv6-address

Specifies the address used by the other node as the RP candidacy address for the same multicast group address range as configured on this node.

Values

ipv6-address

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

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

x [0 to FFFF]H

d [0 to 255]D

Platforms

All

rp-set-peer

Syntax

[no] rp-set-peer ip-address

Context

[Tree] (config>router>pim>rp>anycast rp-set-peer)

Full Context

configure router pim rp anycast rp-set-peer

Description

This command configures an IP peer in the anycast RP-set. The address identifies the address used by the other node as the RP candidate address for the same multicast group address range as configured on this node.

This is a manual procedure. Caution should be taken to produce a consistent configuration of an RP-set for a given multicast group address range. The priority should be identical on each node and be a higher value than any other configured RP candidate that is not a member of this RP-set.

Although there is no set maximum number of addresses that can be configured in an RP-set, up to 15 IP addresses is recommended.

The no form of this command removes an entry from the list.

Parameters

ip-address

Specifies an IP peer in the anycast RP-set.

Platforms

All

rp-set-peer

Syntax

[no] rp-set-peer ipv6-address

Context

[Tree] (config>router>pim>rp>ipv6>anycast rp-set-peer)

Full Context

configure router pim rp ipv6 anycast rp-set-peer

Description

This command configures a peer in the anycast RP-set. The address identifies the address used by the other node as the RP candidate address for the same multicast group address range as configured on this node.

This is a manual procedure. Caution should be taken to produce a consistent configuration of an RP-set for a given multicast group address range. The priority should be identical on each node and be a higher value than any other configured RP candidate that is not a member of this RP-set.

Although there is no set maximum number of addresses that can be configured in an RP-set, up to 15 IP addresses is recommended.

The no form of this command removes the IPv6 address from the anycast RP set.

Parameters

ipv6-address

Specifies an IPv6 peer in the anycast RP-set.

Platforms

All

rpc-authorization

rpc-authorization

Syntax

rpc-authorization

Context

[Tree] (config>system>security>profile>grpc rpc-authorization)

Full Context

configure system security profile grpc rpc-authorization

Description

This command opens a configuration context for configuring user privileges related to RPCs.

Platforms

All

rpf-select

rpf-select

Syntax

rpf-select

Context

[Tree] (config>service>vprn>mvpn rpf-select)

Full Context

configure service vprn mvpn rpf-select

Description

This command enables context for VRF extranet mapping for C-instance receivers in this receiver MVPN instance to multicast streams in P-instance core MVPN instances.

Platforms

All

rpf-table

rpf-table

Syntax

rpf-table {rtable-m | rtable-u | both}

no rpf-table

Context

[Tree] (config>service>vprn>msdp rpf-table)

Full Context

configure service vprn msdp rpf-table

Description

This command configures the sequence of route tables used to find a Reverse Path Forwarding (RPF) interface for a particular multicast route.

By default, only the unicast route table is looked up to calculate RPF interface towards the source/rendezvous point. However, the operator can specify the following:

  • use the unicast route table only

  • use the multicast route table only or

  • use both the route tables

The no form of this command reverts to the default.

Default

rpf-table rtable-u

Parameters

rtable-m

Specifies that only the multicast route table will be used by the multicast protocol (PIM) for IPv4 RPF checks. This route table will contain routes submitted by static routes, ISIS and OSPF.

rtable-u

Specifies only that the unicast route table will be used by the multicast protocol (PIM) for IPv4 RPF checks. This route table will contain routes submitted by all the unicast routing protocols.

both

Will always look up first in the multicast route table and, if there is a route, it will use it. If PIM does not find a route in the first lookup, it will try to find it in the unicast route table. Rtable-m is checked before rtable-u.

Platforms

All

rpf-table

Syntax

rpf-table {rtable-m | rtable-u | both}

no rpf-table

Context

[Tree] (config>service>vprn>pim rpf-table)

[Tree] (config>router>msdp rpf-table)

Full Context

configure service vprn pim rpf-table

configure router msdp rpf-table

Description

This command configures the sequence of route tables used to find a Reverse Path Forwarding (RPF) interface for a particular multicast route.

By default, only the unicast route table is looked up to calculate RPF interface towards the source/rendezvous point. However, the operator can specify the following:

  • use the unicast route table only

  • use the multicast route table only

  • use both the route tables

Default

rpf-table rtable-u

Parameters

rtable-m

Specifies that only the multicast route table will be used by the multicast protocol (PIM) for IPv4 RPF checks. This route table will contain routes submitted by static routes, IS-IS and OSPF.

rtable-u

Specifies only that the unicast route table will be used by the multicast protocol (PIM) for IPv4 RPF checks. This route table will contain routes submitted by all the unicast routing protocols.

both

Specifies that the multicast route table will be used first by the multicast protocol (PIM) for checks, and then the unicast route table will be used if the multicast route table lookup fails. rtable-m is checked before rtable-u.

Platforms

All

rpf-table

Syntax

rpf-table {rtable-m | rtable-u | both}

no rpf-table

Context

[Tree] (config>router>pim rpf-table)

Full Context

configure router pim rpf-table

Description

This command configures the sequence of route tables used to find a Reverse Path Forwarding (RPF) interface for a particular multicast route.

By default, only the unicast route table is looked up to calculate RPF interface towards the source or rendezvous point. However, the operator can specify one of the following:

  • use the unicast route table only

  • use the multicast route table only

  • use both the route tables

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

Default

rpf-table rtable-u

Parameters

rtable-m

Specifies that only the multicast route table will be used by the multicast protocol (PIM) for IPv4 RPF checks. This route table will contain routes submitted by static routes, ISIS and OSPF.

rtable-u

Specifies only that the unicast route table will be used by the multicast protocol (PIM) for IPv4 RPF checks. This route table will contain routes submitted by all the unicast routing protocols.

both

Specifies to always lookup first in the multicast route table and if there is a route, it will use it. If PIM does not find a route in the first lookup, it will try to find it in the unicast route table. Rtable-m is checked before rtable-u.

Platforms

All

rpf6-table

rpf6-table

Syntax

rpf6-table {rtable6-m | rtable6-u | both}

no rpf6-table

Context

[Tree] (config>service>vprn>pim rpf6-table)

Full Context

configure service vprn pim rpf6-table

Description

This command configures the sequence of route tables used to find a Reverse Path Forwarding (RPF) interface for a specific multicast route.

By default, only the unicast route table is looked up to calculate the RPF interface toward the source/rendezvous point. However, the operator can specify to use the following:

  • unicast route table only

  • multicast route table only

  • both route tables

Default

rpf6-table rtable6-u

Parameters

rtable6-m

Specifies that only the multicast route table will be used by the multicast protocol (PIM) for IPv6 RPF checks. This route table will contain routes submitted by static routes, ISIS and OSPF.

rtable6-u

Specifies that only the unicast route table will be used by the multicast protocol (PIM) for IPv6 RPF checks. This route table will contain routes submitted by all unicast routing protocols.

both

Specifies that the multicast route table will be used first by the multicast protocol (PIM) for IPv6 RPF checks, then the unicast route table will be used if the multicast route table lookup fails.

Platforms

All

rpf6-table

Syntax

rpf6-table {rtable6-m | rtable6-u | both}

no rpf6-table

Context

[Tree] (config>router>pim rpf6-table)

Full Context

configure router pim rpf6-table

Description

This command configures the sequence of route tables used to find a Reverse Path Forwarding (RPF) interface for a particular multicast route.

By default, only the unicast route table is looked up to calculate RPF interface towards the source/rendezvous point. However, the operator can specify the following:

  • use unicast route table only

  • use multicast route table only or

  • use both the route tables

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

Default

rpf6-table rtable6-u

Parameters

rtable6-m

Specifies that only the multicast route table will be used by the multicast protocol (PIM) for IPv6 RPF checks. This route table will contain routes submitted by static routes, ISIS and OSPF.

rtable6-u

Specifies that only the unicast route table will be used by the multicast protocol (PIM) for IPv6 RPF checks. This route table will contain routes submitted by all the unicast routing protocols.

both

Specifies that the multicast route table will be used first by the multicast protocol (PIM) for IPv6 RPF checks, and then the unicast route table will be used if the multicast route table lookup fails.

Platforms

All

rpfv

rpfv

Syntax

rpfv [detail]

no rpfv

Context

[Tree] (debug>router>pim rpfv)

Full Context

debug router pim rpfv

Description

This command enables debugging for PIM RPF vector.

The no form of this command disables debugging for PIM RPF vector.

Parameters

detail

Debugs detailed RPF vector information.

Platforms

All

rpfv

Syntax

rpfv core

rpfv mvpn

rpfv core mvpn

no rpfv [core] [mvpn]

Context

[Tree] (config>router>pim rpfv)

Full Context

configure router pim rpfv

Description

This command enables RPF Vector processing for Inter-AS Rosen MVPN Option-B and Option-C. The rpfv must be enabled on every node for Inter-AS Option B/C MVPN support.

If rpfv is configured, MLDP inter-AS resolution cannot be used. These two features are mutually exclusive.

The no form of this command reverts to the default.

Default

no rpfv

Parameters

mvpn

Enables MVPN RPF vector processing for Inter-AS Option B/C MVPN based on RFC 5496 and RFC 6513. If a core RPF vector is received, it will be dropped before a message is processed.

core

Enables core RPF vector (no RD) processing for Inter-AS Option B/C MVPN, which allows SR OS interoperability as P-router with third-party vendors that do not encode RD in the RPF vector for Inter-AS MVPN.

core mvpn

Enables core RPF vector (no RD) processing for Inter-AS Option B/C MVPN, which allows SR OS interoperability as P-router with third-party vendors that do not encode RD in the RPF vector for Inter-AS MVPN.

The no version of this command disables RPF Vector processing. If RPF vector is received in a PIM join message, the vector will be removed before local processing of PIM message starts.

Platforms

All

rpki-session

rpki-session

Syntax

[no] rpki-session ip-address

Context

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

Full Context

configure router origin-validation rpki-session

Description

This command configures a session with an RPKI local cache server by using the RPKI-Router protocol. It is over these sessions that the router learns dynamic VRP entries expressing valid origin AS and prefix associations. SR OS supports the RPKI-Router protocol over TCP/IPv4 or TCP/IPv6 transport. The router can set up an RPKI-Router session using the base routing table (in-band) or the management router (out-of-band). Configure the command in the config>router management instance to configure a session using the management port.

Default

no rpki-session

Parameters

ip-address

Specifies the IPv4 address or an IPv6 address. If the IPv6 address is link-local then the interface name must be appended to the IPv6 address after a hyphen (-).

Platforms

All

rpki-session

Syntax

[no] rpki-session ip-address

Context

[Tree] (debug>router rpki-session)

Full Context

debug router rpki-session

Description

This command enables and configures debugging for RPKI session.

The no form of this command disables debugging for RPKI session.

Parameters

ip-address

Debugs the RPKI session associated with the specified IP 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

interface

up to 32 characters, mandatory for link local addresses

Platforms

All

rpl-end

rpl-end

Syntax

[no] rpl-end

Context

[Tree] (config>eth-ring>path rpl-end)

Full Context

configure eth-ring path rpl-end

Description

This command configures the G.8032 path as a ring protection link end. The ring should be declared as either a RPL owner or RPL neighbor for this command to be allowed. Only path a or path b can be declared an RPL-end.

The no form of this command sets the rpl-end to default no rpl-end.

Default

no rpl-end

Platforms

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

rpl-node

rpl-node

Syntax

rpl-node [owner | nbr]

no rpl-node

Context

[Tree] (config>eth-ring rpl-node)

Full Context

configure eth-ring rpl-node

Description

This command configures the G.8032 ring protection link type as owner or neighbor. The no form of the command means this node is not connected to an RPL link. When RPL owner or neighbor is specified either the a or b path must be configured with the rpl-end command. An owner is responsible for operation of the rpl link. Configuring the RPL as neighbor is optional (can be left as no rpl-node) but if the command is used the nbr is mandatory.

On a sub-ring without virtual channel it is mandatory to configure sub-ring non-virtual-link on all nodes on the sub-ring to propagate the R-APS messages around the sub-ring.

The no form of this command removes the RPL link.

Default

no rpl-node

Parameters

owner

Specifies the owner link type.

nbr

Specifies the neighbor link type.

Platforms

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

rr

rr

Syntax

[no] rr

Context

[Tree] (debug>router>rsvp>event rr)

Full Context

debug router rsvp event rr

Description

This command debugs refresh reduction events.

The no form of the command disables the debugging.

Platforms

All

rr-use-route-table

rr-use-route-table

Syntax

rr-use-route-table

no rr-use-route-table

Context

[Tree] (config>router>bgp>next-hop-res>labeled-routes rr-use-route-table)

Full Context

configure router bgp next-hop-resolution labeled-routes rr-use-route-table

Description

This command enables BGP to perform a lookup of IGP routes in the route table to resolve the BGP next-hop of label-IPv4 and label-IPv6 routes. This is useful for a Route Reflector (RR) that does not participate in tunnel signaling protocols such as LDP and RSVP and therefore, does not have tunnels to resolve the BGP next-hops of label-unicast routes.

Configure the disable-route-table-install command before you configure the rr-use-route-table command because forwarding would otherwise be incorrect for cases where label routes are resolved this way.

Default

no rr-use-route-table

Platforms

All

rs-fec-mode

rs-fec-mode

Syntax

rs-fec-mode rs-fec-mode

no rs-fec-mode

Context

[Tree] (config>port>connector rs-fec-mode)

Full Context

configure port connector rs-fec-mode

Description

This command is used for breakout connectors when all connector ports must use the same rs-fec-mode setting.

In all other cases, the rs-fec-mode is set using the configure port ethernet rs-fec-mode command for each individual connector port.

See "Forward Error Correction" in the Interface Configuration Guide for more information about rs-fec-mode settings.

Default

no rs-fec-mode

Parameters

rs-fec-mode

Specifies the RS-FEC mode to support.

Values

cl91-514-528, cl91-514-544

Platforms

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

rs-fec-mode

Syntax

rs-fec-mode rs-fec-mode

no rs-fec-mode

Context

[Tree] (config>port>ethernet rs-fec-mode)

Full Context

configure port ethernet rs-fec-mode

Description

This command enables RS-FEC on the Ethernet port. RS-FEC Clause 91 is required for QSFP28, CFP4, 100GBase-SR4, 100GBase-ER4 lite, and CWDM4 for the QSFP28 package optics for short-reach optics.

See "Forward Error Correction" in the Interface Configuration Guide for more information about rs-fec-mode settings.

Default

no rs-fec-mode

Parameters

rs-fec-mode

Specifies the RS-FEC mode to support.

Values

cl91-514-528, cl74, cl108

Platforms

All

rsa

rsa

Syntax

rsa

Context

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

Full Context

configure system security user public-keys rsa

Description

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

Platforms

All

rsa-key

rsa-key

Syntax

rsa-key key-id [create]

no rsa-key key-id

Context

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

Full Context

configure system security user public-keys rsa rsa-key

Description

This command creates an RSA 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 the RSA 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

rsa-signature

rsa-signature

Syntax

rsa-signature {pkcs1 | pss}

Context

[Tree] (config>ipsec>cert-profile>entry rsa-signature)

Full Context

configure ipsec cert-profile entry rsa-signature

Description

This command specifies the signature scheme for RSA key.

Default

rsa-signature pkcs1

Parameters

pkcs1

Specifies the RSA pkcs#1 v1.5 signature scheme.

pss

Specifies the RSA probabilistic signature scheme.

Platforms

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

rsvp

rsvp

Syntax

[no] rsvp

Context

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

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

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

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

Full Context

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

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

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

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

Description

This command selects the RSVP-TE tunnel type.

The rsvp value instructs BGP to search for the best metric RSVP LSP to the address of the BGP next hop. This address can correspond to the system interface or to another loopback interface used by the BGP instance on the remote node. The LSP metric is provided by MPLS in the tunnel table. In the case of multiple RSVP LSPs with the same lowest metric, BGP selects the LSP with the lowest tunnel-id.

The no form of this command removes the RSVP-TE tunnel type.

Default

no rsvp

Platforms

All

rsvp

Syntax

rsvp

Context

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

Full Context

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

Description

Note: This command is no longer supported and will be removed in a future release.

Platforms

All

rsvp

Syntax

[no] rsvp

Context

[Tree] (config>service>vpls>provider-tunnel>inclusive rsvp)

Full Context

configure service vpls provider-tunnel inclusive rsvp

Description

This command creates the context to configure the parameters of an RSVP P2MP LSP used for forwarding Broadcast, Unicast unknown and Multicast (BUM) packets of a VPLS or B-VPLS instance.

Platforms

All

rsvp

Syntax

rsvp

no rsvp

Context

[Tree] (config>service>vprn>mvpn>pt>inclusive rsvp)

[Tree] (config>service>vprn>mvpn>pt>selective rsvp)

Full Context

configure service vprn mvpn provider-tunnel inclusive rsvp

configure service vprn mvpn provider-tunnel selective rsvp

Description

Commands in this context configure the RSVP P2MP LSP for the provider tunnel.

The no form of this command removes the rsvp context including all the statements in the context.

Default

no rsvp

Platforms

All

rsvp

Syntax

[no] rsvp

Context

[Tree] (config>router rsvp)

Full Context

configure router rsvp

Description

Commands in this context configure RSVP protocol parameters. RSVP is not enabled by default and must be explicitly enabled (no shutdown).

RSVP is used to set up LSPs. RSVP should be enabled on all router interfaces that participate in signaled LSPs.

The no form of this command deletes this RSVP protocol instance and removes all configuration parameters for this RSVP instance. To suspend the execution and maintain the existing configuration, use the shutdown command. RSVP must be shutdown before the RSVP instance can be deleted. If RSVP is not shutdown, the no rsvp command does nothing except issue a warning message on the console indicating that RSVP is still administratively enabled.

Default

no shutdown

Platforms

All

rsvp

Syntax

rsvp [lsp lsp-name] [sender source-address] [endpoint endpoint-address] [tunnel-id tunnel-id] [lsp-id lsp-id] [interface ip-int-name]

no rsvp

Context

[Tree] (debug>router rsvp)

Full Context

debug router rsvp

Description

This command enables and configures debugging for RSVP.

Parameters

lsp lsp-name

Specifies the LSP name up to 64 characters in length.

sender source-address

Specifies the IP address of the sender.

endpoint endpoint-address

Specifies the far-end IP address.

tunnel-id tunnel-id

Specifies the RSVP tunnel ID.

Values

0 to 4294967295

lsp-id lsp-id

Specifies the LSP ID.

Values

1 to 65535

interface ip-int-name

Specifies the interface name. The interface name can be up to 32 characters long and must be unique. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

Platforms

All

rsvp

Syntax

[no] rsvp

Context

[Tree] (config>router>gtm>pt>inclusive rsvp)

[Tree] (config>router>gtm>pt>selective rsvp)

Full Context

configure router gtm provider-tunnel inclusive rsvp

configure router gtm provider-tunnel selective rsvp

Description

This command enables the use of P2MP RSVP as the inclusive or selective provider tunnel.

The no form of this command removes the RSVP context including all the statements in the context.

Default

no rsvp

Platforms

All

rsvp

Syntax

rsvp

Context

[Tree] (config>oam-pm>session>mpls>lsp rsvp)

Full Context

configure oam-pm session mpls lsp rsvp

Description

Commands in this context configure an RSVP LSP and its attributes to be tested.

Platforms

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

rsvp

Syntax

[no] rsvp

Context

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

[Tree] (config>router>bgp>next-hop-res>lbl-routes>transport-tunn>family>res-filter rsvp)

Full Context

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

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

Description

This command selects RSVP tunneling for next-hop resolution and specifies RSVP tunnels in a tunnel table to IPv4 destinations. This option allows BGP to use the best metric RSVP LSP to the address of the BGP next-hop. This address can correspond to the system interface or to another loopback interface of the remote BGP router. In the case of multiple RSVP LSPs with the same lowest metric, BGP selects the LSP with the lowest tunnel ID.

Platforms

All

rsvp

Syntax

[no] rsvp

Context

[Tree] (conf>router>isis>igp-sc>tunn-nh>family>res-filter rsvp)

Full Context

configure router isis igp-shortcut tunnel-next-hop family resolution-filter rsvp

Description

This command selects the RSVP-TE tunnel type in the resolution of the IP prefix or SR tunnel family using IGP shortcuts.

Platforms

All

rsvp

Syntax

[no] rsvp

Context

[Tree] (config>router>ospf>igp-sc>tunnel-nh>family>res-filter rsvp)

[Tree] (config>router>ospf3>igp-sc>tunnel-nh>family>res-filter rsvp)

Full Context

configure router ospf igp-shortcut tunnel-next-hop family resolution-filter rsvp

configure router ospf3 igp-shortcut tunnel-next-hop family resolution-filter rsvp

Description

This command selects the RSVP-TE tunnel type in the resolution of the IP prefix or SR tunnel family using IGP shortcuts.

Platforms

All

rsvp-auto

rsvp-auto

Syntax

rsvp-auto

Context

[Tree] (config>oam-pm>session>mpls>lsp rsvp-auto)

Full Context

configure oam-pm session mpls lsp rsvp-auto

Description

Commands in this context configure the RSVP auto LSP and its attributes for testing.

Platforms

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

rsvp-resv-style

rsvp-resv-style

Syntax

rsvp-resv-style [se | ff]

Context

[Tree] (config>router>mpls>lsp rsvp-resv-style)

Full Context

configure router mpls lsp rsvp-resv-style

Description

This command specifies the RSVP reservation style, shared explicit (se) or fixed filter (ff). A reservation style is a set of control options that specify a number of supported parameters. The style information is part of the LSP configuration.

Default

rsvp-resv-style se

Parameters

ff

Fixed filter is single reservation with an explicit scope. This reservation style specifies an explicit list of senders and a distinct reservation for each of them. A specific reservation request is created for data packets from a particular sender. The reservation scope is determined by an explicit list of senders.

se

Shared explicit is shared reservation with a limited scope. This reservation style specifies a shared reservation environment with an explicit reservation scope. This reservation style creates a single reservation over a link that is shared by an explicit list of senders. Because each sender is explicitly listed in the RESV message, different labels can be assigned to different sender-receiver pairs, thereby creating separate LSPs.

Platforms

All

rsvp-shortcut

rsvp-shortcut

Syntax

rsvp-shortcut [ip-address]

no rsvp-shortcut

Context

[Tree] (debug>router>ospf rsvp-shortcut)

Full Context

debug router ospf rsvp-shortcut

Description

This command debugs the OSPFv2 RSVP shortcut.

Parameters

ip-address

Specifies the IP address to debug.

Platforms

All

rsvp-te

rsvp-te

Syntax

rsvp-te rsvp-te

no rsvp-te

Context

[Tree] (config>router>mpls>lsp-self-ping rsvp-te)

Full Context

configure router mpls lsp-self-ping rsvp-te

Description

This command enables LSP Self Ping on all RSVP-TE LSPs, unless an individual LSP is explicitly disabled under the lsp>lsp-self-ping command or in the LSP template.

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

Default

rsvp-te disable

Parameters

rsvp-te

Specifies whether LSP Self Ping is enabled on RSVP-TE LSPs.

Values

enable, disable

Platforms

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

rsvp-te

Syntax

rsvp-te value

no rsvp-te

Context

[Tree] (config>router>mpls>tunnel-table-pref rsvp-te)

Full Context

configure router mpls tunnel-table-pref rsvp-te

Description

This command configures the tunnel table preference for RSVP-TE LSP tunnel type away from its default value.

The tunnel table preference applies to the next-hop resolution of BGP routes of the following families: EVPN, IPv4, IPv6, VPN-IPv4, VPN-IPv6, label-IPv4, and label-IPv6 in the tunnel table.

This feature does not apply to a VPRN, VPLS, or VLL service with explicit binding to an SDP that enabled the mixed-lsp-mode option. The tunnel preference in such an SDP is fixed and is controlled by the service manager. The configuration of the tunnel table preference parameter does not modify the behavior of such an SDP and the services that bind to it.

It is recommended to not set two or more tunnel types to the same preference value. In such a situation, the tunnel table prefers the tunnel type which was first introduced in SR OS implementation historically.

The no form of this command reverts to the default.

Default

rsvp-te 7

Parameters

value

Specifies the tunnel table preference value for RSVP-TE LSP.

Values

1 to 255

Default

7

Platforms

All

rsvp-te

Syntax

[no] rsvp-te

Context

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

Full Context

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

Description

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

The rsvp-te value instructs the code to search for the set of lowest metric RSVP-TE LSPs to the address of the indirect next-hop. The LSP metric is provided by MPLS in the tunnel table. The static route treats a set of RSVP-TE LSPs with the same lowest metric as an ECMP set. The user has the option of configuring a list of RSVP-TE LSP names to be used exclusively instead of searching in the tunnel table. In that case, all LSPs must have the same LSP metric in order for the static route to use them as an ECMP set. Otherwise, only the LSPs with the lowest common metric value will be selected.

A P2P auto-lsp that is instantiated via an LSP template can be selected in TTM when resolution is set to any. However, Nokia does not recommend configuring an auto-lsp name explicitly under the rsvp-te node as the auto-generated name can change if the node reboots, which will blackhole the traffic of the static route.

Default

no rsvp-te

Platforms

All

rsvp-te

Syntax

[no] rsvp-te

Context

[Tree] (config>oam-pm>session>ip>tunnel>mpls rsvp-te)

Full Context

configure oam-pm session ip tunnel mpls rsvp-te

Description

This command configures the specification of RSVP-TE specific tunnel information that is used to transport the test packets. Entering this context removes all other tunnel type options configured under the configure oam-pm session ip tunnel mpls context. Only a single mpls type can be configured for an OAM-PM session.

The no form of this command deletes the context and all configurations under it.

Platforms

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

rsvp-te-auto

rsvp-te-auto

Syntax

rsvp-te-auto

Context

[Tree] (config>oam-pm>session>ip>tunnel>mpls rsvp-te-auto)

Full Context

configure oam-pm session ip tunnel mpls rsvp-te-auto

Description

This command configures the specification of the RSVP-TE Auto (RSVP-TE with dynamically-created LSPs) tunnel information that is used to transport the test packets. Entering this context removes all other tunnel type options configured under the configure oam-pm session ip tunnel mpls context. Only a single mpls type can be configured for an OAM-PM session.

The no form of this command deletes the context and all configurations under it.

Platforms

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

rt-buffer-size

rt-buffer-size

Syntax

rt-buffer-size rt-buffer-size

no rt-buffer-size

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>video rt-buffer-size)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>source-override>video rt-buffer-size)

Full Context

configure mcast-management multicast-info-policy bundle channel video rt-buffer-size

configure mcast-management multicast-info-policy bundle channel source-override video rt-buffer-size

Description

This command configures the retransmission buffer for channels within the bundle or channel range.

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

Default

300

Parameters

rt-buffer-size

Specifies the buffer size, in milliseconds, to store channel packets.

Values

300 to 8000

Platforms

7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

rt-payload-type

rt-payload-type

Syntax

rt-payload-type payload-type

no rt-payload-type

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if rt-payload-type)

Full Context

configure mcast-management multicast-info-policy video-policy video-interface rt-payload-type

Description

This command describes the format to be used by Retransmission (RT) server to send retransmission packets. The RET server interface allows the payload type within the retransmission packets to be configured.

Default

rt-payload-type 99 — Indicates that the frames will be sent in the RFC 4588, RTP Retransmission Payload Format, format.

Parameters

payload-type

Indicates the format expected for received retransmission packets. The value 33 indicates that the frames will be received as originally sent. A value between 96 and 127 indicates the dynamic payload type value (per RFC 3551) to be used for RFC 4588 formatted retransmission packets.

Values

33, 96 to 127

Platforms

7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

rt-rate

rt-rate

Syntax

rt-rate rt-burst-percentage

no rt-rate

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>pip rt-rate)

[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>sd rt-rate)

[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if rt-rate)

[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if>hd rt-rate)

Full Context

configure mcast-management multicast-info-policy video-policy video-interface pip rt-rate

configure mcast-management multicast-info-policy video-policy video-interface sd rt-rate

configure mcast-management multicast-info-policy video-policy video-interface rt-rate

configure mcast-management multicast-info-policy video-policy video-interface hd rt-rate

Description

This command sets the rate of nominal bandwidth at which retransmission packets are sent to the retransmission client for requests directed to the IP address.

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

Default

rt-rate 5

Parameters

rt-burst-percentage

Specifies the percentage of nominal bandwidth to send retransmission packets.

Values

1 to 100

Default

5

Platforms

7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

rt-server

rt-server

Syntax

rt-server disable

rt-server ip-address port port-num

no rt-server

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>video rt-server)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>source-override>video rt-server)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>video rt-server)

Full Context

configure mcast-management multicast-info-policy bundle channel video rt-server

configure mcast-management multicast-info-policy bundle channel source-override video rt-server

configure mcast-management multicast-info-policy bundle video rt-server

Description

This command enables and configures the upstream retransmission server configuration parameters.

The no form of the command removes the upstream retransmission server configuration and implies the configuration is inherited from a higher context or from the default policy.

Default

no rt-server – The upstream retransmission server settings are inherited.

Parameters

disable

This keyword explicitly disables the upstream retransmission server within the policy. For the default bundle within the default Multicast Information Policy, the no form of the command and the disable keyword have the same meaning and imply the server is disabled.

ip-address

The IP address of the upstream retransmission server.

port num

The UDP port to use to send RET requests to the upstream RET server.

Values

1024 to 5999, 6251 to 65535

Platforms

7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

rt-server

Syntax

rt-server [client client-ip [source-port src-port]]

no rt-server

Context

[Tree] (debug>service>id>video-interface rt-server)

Full Context

debug service id video-interface rt-server

Description

This command enables debugging for the RET server.

Parameters

client client-ip

Specifies the client IP address.

source src-port

Specifies the source port.

Values

1 to 65535

Platforms

7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

rtm

rtm

Syntax

rtm [rp-address]

no rtm

Context

[Tree] (debug>router>msdp rtm)

Full Context

debug router msdp rtm

Description

This command enables debugging for Multicast Source Discovery Protocol (MSDP) route table manager (RTM).

The no form of the command disables MSDP RTM debugging.

Parameters

rp-address

Debugs the IP multicast address for which this entry contains information.

Platforms

All

rtm

Syntax

rtm [detail]

no rtm

Context

[Tree] (debug>router>pim rtm)

Full Context

debug router pim rtm

Description

This command enables debugging for PIM RTM.

The no form of this command disables debugging for PIM RTM.

Parameters

detail

Displays detailed RTM information.

Platforms

All

rtm

Syntax

rtm [neighbor ip-address | group name]

no rtm

Context

[Tree] (debug>router>bgp rtm)

Full Context

debug router bgp rtm

Description

This command logs RTM changes in the debug log.

The no form of this command disables debugging.

Parameters

neighbor ip-address

Debugs only events affecting the specified BGP neighbor.

Values

ipv4-address:

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

ipv6-address:

  • x:x:x:x:x:x:x:x [-interface] (eight 16-bit pieces)

  • x:x:x:x:x:x:d.d.d.d [-interface]

  • x: [0 to FFFF]H

  • d: [0 to 255]D

  • interface: up to 32 characters for link local addresses

group name

Debugs only events affecting the specified peer group name, up to 64 characters, and associated neighbors.

Platforms

All

rtm

Syntax

rtm [ip-address]

no rtm

Context

[Tree] (debug>router>isis rtm)

Full Context

debug router isis rtm

Description

This command enables debugging for IS-IS route table manager (RTM).

The no form of the command disables debugging.

Parameters

ip-address

The specified IP address.

Values

ipv4-address:

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

ipv6-address:

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

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

  • x: [0 to FFFF]H

  • d: [0 to 255]D

Platforms

All

rtm

Syntax

rtm [ip-address]

no rtm

Context

[Tree] (debug>router>ospf3 rtm)

[Tree] (debug>router>ospf rtm)

Full Context

debug router ospf3 rtm

debug router ospf rtm

Description

This command enables debugging for OSPF RTM.

Parameters

ip-address

Specifies the IP address to debug.

Values

ipv4-address:

  • a.b.c.d

ipv6-address:

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

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

  • x: [0 to FFFF]H

  • d: [0 to 255]D

Platforms

All

rtm-debounce-time

rtm-debounce-time

Syntax

rtm-debounce-time debounce-time

no rtm-debounce-time

Context

[Tree] (config>router>l2tp rtm-debounce-time)

[Tree] (config>service>vprn>l2tp rtm-debounce-time)

Full Context

configure router l2tp rtm-debounce-time

configure service vprn l2tp rtm-debounce-time

Description

This command configures the amount of time, in milliseconds, that the system waits before declaring an L2TP tunnel down when the remote endpoint IP address cannot be resolved to an active IP route in the local routing table.

The default behavior is for the L2TP tunnel to not be declared down based on the remote endpoint IP address reachability.

The no form of this command returns the rtm-debounce-time to a value of 0.

Default

no rtm-debounce-time

Parameters

debounce-time

Specifies the amount of time, in milliseconds, that the system waits before declaring the associated L2TP tunnel as down.

Values

0 to 5000

Platforms

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

rtp-header

rtp-header

Syntax

[no] rtp-header

Context

[Tree] (config>service>epipe>sap>cem rtp-header)

[Tree] (config>service>cpipe>sap>cem rtp-header)

Full Context

configure service epipe sap cem rtp-header

configure service cpipe sap cem rtp-header

Description

This command specifies whether an RTP header is used when packets are transmitted to the packet service network (PSN) by the CEM SAP. This mode must be enabled for differential-timed DS1/E1s. It can optionally be enabled for other DS1/E1s for interoperability purposes.

Default

no rtp-header

Platforms

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

rtp-header

Syntax

[no] rtp-header

Context

[Tree] (config>mirror>mirror-dest>sap>cem rtp-header)

Full Context

configure mirror mirror-dest sap cem rtp-header

Description

This command specifies whether an RTP header is used when packets are transmitted to the packet service network (PSN) by the CEM SAP.

Platforms

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

rtp-performance

rtp-performance

Syntax

rtp-performance

Context

[Tree] (config>app-assure>group>cflowd rtp-performance)

Full Context

configure application-assurance group cflowd rtp-performance

Description

This command configures the cflowd RTP performance export.

Platforms

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

rtr-adv-lsa-limit

rtr-adv-lsa-limit

Syntax

rtr-adv-lsa-limit [1..4294967295] [log-only] [threshold percent]

rtr-adv-lsa-limit [1..4294967295] [log-only] [threshold percent] overload-timeout forever

rtr-adv-lsa-limit [1..4294967295] [log-only] [threshold percent] overload-timeout seconds

no rtr-adv-lsa-limit

Context

[Tree] (config>service>vprn>ospf rtr-adv-lsa-limit)

Full Context

configure service vprn ospf rtr-adv-lsa-limit

Description

This command configures the maximum number of LSAs OSPF can learn from another router, in order to protect the system from a router that accidentally advertises a large number of LSAs. When the number of advertised LSAs reaches the configured percentage of this limit, an SNMP trap is sent. If the limit is exceeded, OSPF goes into overload.

The overload-timeout option allows the administrator to control how long OSPF is in overload as a result of the advertised LSA limit being reached. At the end of this duration of time the system automatically attempts to restart OSPF. One possible value for the overload-timeout is forever, which means OSPF is never restarted automatically and this corresponds to the default behavior when the overload-timeout option is not configured.

The no form of this command removes the rtr-adv-lsa-limit.

Default

rtr-adv-lsa-limit forever

Parameters

log-only

Enables the warning message to be sent at the specified threshold percentage, and also when the limit is exceeded. However, overload is not set.

percent

The threshold value (as a percentage) that triggers a warning message to be sent.

Values

0 to 100

seconds

Specifies duration in seconds before restarting OSPF.

Values

1 to 1800

Platforms

All

rtr-adv-lsa-limit

Syntax

rtr-adv-lsa-limit limit [log-only] [ threshold percent]

rtr-adv-lsa-limit limit [log-only] [ threshold percent] [overload-timeout {seconds | forever}]

no rtr-adv-lsa-limit

Context

[Tree] (config>router>ospf3 rtr-adv-lsa-limit)

[Tree] (config>router>ospf rtr-adv-lsa-limit)

Full Context

configure router ospf3 rtr-adv-lsa-limit

configure router ospf rtr-adv-lsa-limit

Description

This command configures the maximum number of LSAs OSPF can learn from another router, in order to protect the system from a router that accidentally advertises a large number of LSAs. When the number of advertised LSAs reaches the configured percentage of this limit, an SNMP trap is sent. If the limit is exceeded, OSPF goes into overload.

The overload-timeout option allows the administrator to control how long OSPF is in overload as a result of the advertised LSA limit being reached. At the end of this duration of time, the system automatically exits overload. One possible value for the overload-timeout is forever, which means OSPF is never exiting overload.

The no form of this command removes the rtr-adv-lsa-limit.

Default

no rtr-adv-lsa-limit

Parameters

log-only

Enables the warning message to be sent at the specified threshold percentage, and also when the limit is exceeded. However, overload is not set.

percent

Specifies the threshold value (as a percentage) that triggers a warning message to be sent.

Values

0 to 100

limit

Specifies the number of LSAs, expressed as a decimal integer, that can be learned.

Values

1 to 4294967295

second

Specifies duration in minutes before restarting OSPF.

Values

Values 1 to 1800

forever

Specifies that OSPF is restarted only after the clear router ospf | ospf3 overload rtr-adv-lsa-limit command is executed.

Platforms

All

rtr-solicit-user-db

rtr-solicit-user-db

Syntax

rtr-solicit-user-db local-user-db

no rtr-solicit-user-db

Context

[Tree] (config>service>vpls>sap rtr-solicit-user-db)

Full Context

configure service vpls sap rtr-solicit-user-db

Description

This command enabled access to LUDB for SLAAC hosts under the capture SAP. The name of this ludb must match the name of ludb configured under the configure>service>vprn/ies>sub-if>group-if>ipv6>router-solicit hierarchy.

The no form of this command reverts to the default.

Parameters

local-user-db

Specifies the name of the local-user-database up to 32 characters.

Platforms

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

rtsp

rtsp

Syntax

[no] rtsp

Context

[Tree] (config>service>nat>firewall-policy>alg rtsp)

[Tree] (config>service>nat>up-nat-policy>alg rtsp)

[Tree] (config>service>nat>nat-policy>alg rtsp)

Full Context

configure service nat firewall-policy alg rtsp

configure service nat up-nat-policy alg rtsp

configure service nat nat-policy alg rtsp

Description

This command enables RTSP ALG.

The no form of the command disables RTSP ALG.

Default

no rtsp

Platforms

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

  • configure service nat firewall-policy alg rtsp

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

  • configure service nat nat-policy alg rtsp
  • configure service nat up-nat-policy alg rtsp

rtt-threshold

rtt-threshold

Syntax

rtt-threshold threshold

no rtt-threshold

Context

[Tree] (config>app-assure>group>aa-sub-cong rtt-threshold)

[Tree] (config>app-assure>group>anl>source rtt-threshold)

Full Context

configure application-assurance group aa-sub-congestion-detection rtt-threshold

configure application-assurance group access-network-location source rtt-threshold

Description

This command configures the roundtrip delay threshold used by the DEM gateway algorithm to determine ANL congestion or subscriber congestion for NLB-DEM.

Default

rtt-threshold 173

Parameters

threshold

Specifies the maximum acceptable round trip time (RTT), in milliseconds, for TCP connections with no congestion. Any measured RTT above the threshold is considered an indication of possible congestion.

Values

0 to 500

Platforms

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

rtt-threshold-rat

rtt-threshold-rat

Syntax

rtt-threshold-rat rat-type rat-type rtt-threshold rtt-threshold

no rtt-threshold-rat rat-type rat-type

Context

[Tree] (config>app-assure>group>aa-sub-cong rtt-threshold-rat)

[Tree] (config>app-assure>group>anl>source rtt-threshold-rat)

Full Context

configure application-assurance group aa-sub-congestion-detection rtt-threshold-rat

configure application-assurance group access-network-location source rtt-threshold-rat

Description

This command configures the roundtrip delay threshold for each RAT type to be used for a congestion detection algorithm (if applicable).

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

Default

rtt-threshold-rat 173

Parameters

rat-type

Specifies the 3GPP RAT type.

Values

utran, geran, wlan, gan, hspa-evol, eutran, virtual, eutran-nb, ehrpd, hrpd, cdma-1x, umb, wifi, nr, lte-m

rtt-threshold

Specifies the parameter used by the DEM-GW algorithm that determines ANL congestion or subscriber congestion in the case of NLB-DEM. It specifies the maximum acceptable round trip time (RTT), under no congestion, in milliseconds. Any measured RTT above the threshold is considered an indication of possible congestion.

Values

0 to 500

Platforms

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

rtt-threshold-tolerance

rtt-threshold-tolerance

Syntax

rtt-threshold-tolerance tolerance

no rtt-threshold-tolerance

Context

[Tree] (config>app-assure>group>aa-sub-cong rtt-threshold-tolerance)

[Tree] (config>app-assure>group>anl>source rtt-threshold-tolerance)

Full Context

configure application-assurance group aa-sub-congestion-detection rtt-threshold-tolerance

configure application-assurance group access-network-location source rtt-threshold-tolerance

Description

This command configures the ANL roundtrip delay threshold tolerance used by the DEM gateway algorithm to determine ANL-level or subscriber-level congestion.

Default

rtt-threshold-tolerance 50

Parameters

tolerance

Specifies the ratio, in percentage, of RTTs above the configured threshold (rtt-threshold) over the total RTT measurements.

The ratio is calculated as follows, measured across a one-minute period:

rtt-threshold-tolerance = #(RTTs > rtt-threshold)/ (Total #RTTs)

If the rtt-threshold-tolerance ratio is exceeded, the ANL is declared congested.

Values

0 to 100

Default

50

Platforms

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

rule-prefix

rule-prefix

Syntax

rule-prefix rule-prefix

no rule-prefix

Context

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

Full Context

configure service nat map-domain mapping-rule rule-prefix

Description

This command configures a MAP rule prefix.

Parameters

rule-prefix

Specifies the IPv6 MAP rule prefix.

Values

<ipv6-prefix/prefix-length> :

ipv6-prefix —— x:x:x:x:x:x:x:x (eight 16-bit pieces)

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

x—[0 to FFFF]H

d—[0 to 255]D

prefix-length—[0 to 64]

Platforms

VSR

run-as-user

run-as-user

Syntax

run-as-user user-name

no run-as-user

Context

[Tree] (config>python>python-script run-as-user)

Full Context

configure python python-script run-as-user

Description

This command configures a user that is different from the current user of the session. Script authentication, authorization, accounting, and any activity within the script, is run as the specified user.

The no form of this command specifies that the current user of the session is used.

Default

no run-as-user

Parameters

user-name

Specifies the name of the user, up to 32 characters, that is used to run the script.

Platforms

All

rx-discard-on-ndf

rx-discard-on-ndf

Syntax

rx-discard-on-ndf {bm | bum | none}

Context

[Tree] (config>service>vpls>vxlan rx-discard-on-ndf)

Full Context

configure service vpls vxlan rx-discard-on-ndf

Description

This command, supported by static and BGP-EVPN VXLAN binds, determines the type of traffic that the Non Designated Forwarder (NDF) PE discards in an EVPN multi-homed Ethernet Segment. It is only relevant when the VXLAN instance is associated to a network-interconnect-vxlan ES. The option BM is the default option and discards BM on reception (unicast, known and known is allowed). The option BUM discards any BUM frame on reception. Option none allows any BUM traffic on reception.

Default

rx-discard-on-ndf bm

Parameters

bm

Discards Broadcast and Multicast on the EVPN Non Designated Forwarder (NDF) router, but not Unknown Unicast.

bum

Discards Broadcast, Multicast and Unknown Unicast traffic on the NDF.

none

Allows Broadcast, Multicast or Unknown Unicast traffic on the NDF.

Platforms

All

rx-eth-ed

rx-eth-ed

Syntax

[no] rx-eth-ed

Context

[Tree] (config>eth-ring>path>eth-cfm>mep>grace>eth-ed rx-eth-ed)

[Tree] (config>port>ethernet>eth-cfm>mep>grace>eth-ed rx-eth-ed)

[Tree] (config>eth-tunnel>path>eth-cfm>mep>grace>eth-ed rx-eth-ed)

[Tree] (config>lag>eth-cfm>mep>grace>eth-ed rx-eth-ed)

Full Context

configure eth-ring path eth-cfm mep grace eth-ed rx-eth-ed

configure port ethernet eth-cfm mep grace eth-ed rx-eth-ed

configure eth-tunnel path eth-cfm mep grace eth-ed rx-eth-ed

configure lag eth-cfm mep grace eth-ed rx-eth-ed

Description

This command enables the reception and processing of the ITU-T Y.1731 ETH-ED PDU on the MEP.

The no form of this command disables the reception of the ITU-T Y.1731 ETH-ED PDU on the MEP.

Default

rx-eth-ed

Platforms

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

rx-eth-ed

Syntax

[no] rx-eth-ed

Context

[Tree] (config>service>epipe>sap>eth-cfm>mep>grace>eth-ed rx-eth-ed)

[Tree] (config>service>ipipe>sap>eth-cfm>mep>grace>eth-ed rx-eth-ed)

[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep>grace>eth-ed rx-eth-ed)

Full Context

configure service epipe sap eth-cfm mep grace eth-ed rx-eth-ed

configure service ipipe sap eth-cfm mep grace eth-ed rx-eth-ed

configure service epipe spoke-sdp eth-cfm mep grace eth-ed rx-eth-ed

Description

This command enables the reception and processing of the ITU-T Y.1731 ETH-ED PDU on the MEP.

The no form of this command disables the reception of the ITU-T Y.1731 ETH-ED PDU on the MEP.

Default

rx-eth-ed

Platforms

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

rx-eth-ed

Syntax

[no] rx-eth-ed

Context

[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep>grace>eth-ed rx-eth-ed)

[Tree] (config>service>vpls>sap>eth-cfm>mep>grace>eth-ed rx-eth-ed)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep>grace>eth-ed rx-eth-ed)

[Tree] (config>service>vpls>eth-cfm>mep>grace>eth-ed rx-eth-ed)

Full Context

configure service vpls spoke-sdp eth-cfm mep grace eth-ed rx-eth-ed

configure service vpls sap eth-cfm mep grace eth-ed rx-eth-ed

configure service vpls mesh-sdp eth-cfm mep grace eth-ed rx-eth-ed

configure service vpls eth-cfm mep grace eth-ed rx-eth-ed

Description

This command enables the reception and processing of the ITU-T Y.1731 ETH-ED PDU on the MEP.

The no form of this command disables the reception of the ITU-T Y.1731 ETH-ED PDU on the MEP.

Default

rx-eth-ed

Platforms

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

rx-eth-ed

Syntax

[no] rx-eth-ed

Context

[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>mep>grace>eth-ed rx-eth-ed)

[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>mep>grace>eth-ed rx-eth-ed)

[Tree] (config>service>ies>if>sap>eth-cfm>mep>grace>eth-ed rx-eth-ed)

Full Context

configure service ies subscriber-interface group-interface sap eth-cfm mep grace eth-ed rx-eth-ed

configure service ies interface spoke-sdp eth-cfm mep grace eth-ed rx-eth-ed

configure service ies interface sap eth-cfm mep grace eth-ed rx-eth-ed

Description

This command enables the reception and processing of the ITU-T Y.1731 ETH-ED PDU on the MEP.

The no form of this command disables the reception of the ITU-T Y.1731 ETH-ED PDU on the MEP.

Default

rx-eth-ed

Platforms

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

  • configure service ies subscriber-interface group-interface sap eth-cfm mep grace eth-ed rx-eth-ed

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

  • configure service ies interface spoke-sdp eth-cfm mep grace eth-ed rx-eth-ed
  • configure service ies interface sap eth-cfm mep grace eth-ed rx-eth-ed

rx-eth-ed

Syntax

[no] rx-eth-ed

Context

[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm>mep>grace>eth-ed rx-eth-ed)

[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>mep>grace>eth-ed rx-eth-ed)

[Tree] (config>service>vprn>if>sap>eth-cfm>mep>grace>eth-ed rx-eth-ed)

Full Context

configure service vprn subscriber-interface group-interface sap eth-cfm mep grace eth-ed rx-eth-ed

configure service vprn interface spoke-sdp eth-cfm mep grace eth-ed rx-eth-ed

configure service vprn interface sap eth-cfm mep grace eth-ed rx-eth-ed

Description

This command enables the reception and processing of the ITU-T Y.1731 ETH-ED PDU on the MEP.

The no form of this command disables the reception of the ITU-T Y.1731 ETH-ED PDU on the MEP.

Default

rx-eth-ed

Platforms

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

  • configure service vprn subscriber-interface group-interface sap eth-cfm mep grace eth-ed rx-eth-ed

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

  • configure service vprn interface sap eth-cfm mep grace eth-ed rx-eth-ed
  • configure service vprn interface spoke-sdp eth-cfm mep grace eth-ed rx-eth-ed

rx-eth-ed

Syntax

[no] rx-eth-ed

Context

[Tree] (config>router>if>eth-cfm>mep>grace>eth-ed rx-eth-ed)

Full Context

configure router interface eth-cfm mep grace eth-ed rx-eth-ed

Description

This command enables the reception and processing of the ITU-T Y.1731 ETH-ED PDU on the MEP.

The no form of this command disables the reception of the ITU-T Y.1731 ETH-ED PDU on the MEP.

Default

rx-eth-ed

Platforms

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

rx-eth-vsm-grace

rx-eth-vsm-grace

Syntax

[no] rx-eth-vsm-grace

Context

[Tree] (config>eth-tunnel>path>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

[Tree] (config>port>ethernet>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

[Tree] (config>lag>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

[Tree] (config>eth-ring>path>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

Full Context

configure eth-tunnel path eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

configure port ethernet eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

configure lag eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

configure eth-ring path eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

Description

This command enables the reception and processing of the Nokia ETH-CFM Grace PDU on the MEP.

The Nokia Grace function is a vendor-specific PDU that informs MEP peers that the local node may be entering a period of expected defect.

The no form of this command disables the reception of the Nokia ETH-CFM Grace PDU on the MEP.

Default

rx-eth-vsm-grace

Platforms

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

rx-eth-vsm-grace

Syntax

[no] rx-eth-vsm-grace

Context

[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

[Tree] (config>service>ipipe>sap>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

[Tree] (config>service>epipe>sap>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

Full Context

configure service epipe spoke-sdp eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

configure service ipipe sap eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

configure service epipe sap eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

Description

This command enables the reception and processing of the Nokia ETH-CFM Grace PDU on the MEP.

The Nokia Grace function is a vendor-specific PDU that informs MEP peers that the local node may be entering a period of expected defect.

The no form of this command disables the reception of the Nokia ETH-CFM Grace PDU on the MEP.

Default

rx-eth-vsm-grace

Platforms

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

rx-eth-vsm-grace

Syntax

[no] rx-eth-vsm-grace

Context

[Tree] (config>service>vpls>sap>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

[Tree] (config>service>vpls>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

Full Context

configure service vpls sap eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

configure service vpls spoke-sdp eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

configure service vpls eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

configure service vpls mesh-sdp eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

Description

This command enables the reception and processing of the Nokia ETH-CFM Grace PDU on the MEP.

The Nokia Grace function is a vendor-specific PDU that informs MEP peers that the local node may be entering a period of expected defect.

The no form of this command disables the reception of the Nokia ETH-CFM Grace PDU on the MEP.

Default

rx-eth-vsm-grace

Platforms

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

rx-eth-vsm-grace

Syntax

[no] rx-eth-vsm-grace

Context

[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

[Tree] (config>service>ies>if>sap>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

Full Context

configure service ies subscriber-interface group-interface sap eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

configure service ies interface sap eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

configure service ies interface spoke-sdp eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

Description

This command enables the reception and processing of the Nokia ETH-CFM Grace PDU on the MEP.

The Nokia Grace function is a vendor-specific PDU that informs MEP peers that the local node may be entering a period of expected defect.

The no form of this command disables the reception of the Nokia ETH-CFM Grace PDU on the MEP.

Default

rx-eth-vsm-grace

Platforms

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

  • configure service ies subscriber-interface group-interface sap eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

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

  • configure service ies interface spoke-sdp eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace
  • configure service ies interface sap eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

rx-eth-vsm-grace

Syntax

[no] rx-eth-vsm-grace

Context

[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

[Tree] (config>service>vprn>if>sap>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

Full Context

configure service vprn subscriber-interface group-interface sap eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

configure service vprn interface sap eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

configure service vprn interface spoke-sdp eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

Description

This command enables the reception and processing of the Nokia ETH-CFM Grace PDU on the MEP.

The Nokia Grace function is a vendor-specific PDU that informs MEP peers that the local node may be entering a period of expected defect.

The no form of this command disables the reception of the Nokia ETH-CFM Grace PDU on the MEP.

Default

rx-eth-vsm-grace

Platforms

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

  • configure service vprn subscriber-interface group-interface sap eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

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

  • configure service vprn interface sap eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace
  • configure service vprn interface spoke-sdp eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

rx-eth-vsm-grace

Syntax

[no] rx-eth-vsm-grace

Context

[Tree] (config>router>if>eth-cfm>mep>grace>eth-vsm-grace rx-eth-vsm-grace)

Full Context

configure router interface eth-cfm mep grace eth-vsm-grace rx-eth-vsm-grace

Description

This command enables the reception and processing of the Nokia ETH-CFM Grace PDU on the MEP.

The Nokia Grace function is a vendor-specific PDU that informs MEP peers that the local node may be entering a period of expected defect.

The no form of this command disables the reception of the Nokia ETH-CFM Grace PDU on the MEP.

Default

rx-eth-vsm-grace

Platforms

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

rx-los-reaction

rx-los-reaction

Syntax

rx-los-reaction {squelch}

no rx-los-reaction

Context

[Tree] (config>port>dwdm>coherent rx-los-reaction)

Full Context

configure port dwdm coherent rx-los-reaction

Description

This command configures the reaction to an RX LOS.

Note:

If rx-los-reaction squelch is disabled for some coherent DWDM transceivers, the transceiver only reports local fault alarms when an RX LOS condition occurs; however, the port returns to service faster after the LOS condition is cleared. For these transceivers, if rx-los-reaction squelch is enabled, there is better visibility of individual alarms (for example, signal-fail, local fault, and no-am-lock), but the port takes longer to return to service after the LOS condition is cleared.

Parameters

squelch

Specifies to squelch (turn off) the transmit signal on RX LOS.

Platforms

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

rx-los-thresh

rx-los-thresh

Syntax

rx-los-thresh threshold

Context

[Tree] (config>port>dwdm>coherent rx-los-thresh)

Full Context

configure port dwdm coherent rx-los-thresh

Description

This command configures the average input power LOS threshold.

Default

-23.00

Parameters

threshold

Specifies the RX LOS threshold.

Values

-30.00 to -13.00

Platforms

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

rx-must-be-encrypted

rx-must-be-encrypted

Syntax

[no] rx-must-be-encrypted

Context

[Tree] (config>port>ethernet>dot1x>macsec rx-must-be-encrypted)

Full Context

configure port ethernet dot1x macsec rx-must-be-encrypted

Description

When the rx-must-be-encrypted option is enabled, all traffic that is not MACsec-secured that is received on the port is dropped.

When the rx-must-be-encrypted option is disabled, all arriving traffic, whether MACsec secured or not, will be accepted.

Note:

This command is only available on the NULL port level and does not have per-VLAN granularity.

The no form of this command disables the rx-must-be encrypted option.

Default

rx-must-be-encrypted

Platforms

All

rx-must-be-encrypted

Syntax

[no] rx-must-be-encrypted

Context

[Tree] (config>anysec>tnl-enc>sec-term-pol rx-must-be-encrypted)

Full Context

configure anysec tunnel-encryption security-termination-policy rx-must-be-encrypted

Description

This command accepts all arriving traffic that is ANYsec secured on the port. All other traffic is dropped.

The no form of this command accepts all arriving traffic regardless of whether ANYsec secured or not.

Default

no rx-must-be-encrypted

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

rx-update-pacing

rx-update-pacing

Syntax

rx-update-pacing seconds

Context

[Tree] (config>port>ethernet>eth-cfm>mep>eth-bn rx-update-pacing)

Full Context

configure port ethernet eth-cfm mep eth-bn rx-update-pacing

Description

This command sets the pace for update messages to and from the eth-cfm subsystem to the QoS subsystem. The most recent update messages are held by the ETH-CFM subsystem, but the most recent update is held until the expiration of the pacing timer.

Parameters

seconds

The time to wait before sending subsequent updates (in seconds).

Values

1 to 600

Default

5

Platforms

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