t Commands – Part III

Context

[Tree] (tree)

Full Context

tree

Description

This command displays the command hierarchy structure of the current working context.

Parameters

detail

Displays parameter information for each command shown in the tree output.

flat

Displays the full context on each line.

Platforms

All

Context

[Tree] (config>router>p2mp-sr-tree>p2mp-policy tree-id)

Full Context

configure router p2mp-sr-tree p2mp-policy 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.

Default

no tree-id

Parameters

tree-id

Specifies the ID of the tree.

Values

8193 to 16286

Platforms

All

Context

[Tree] (config>router>p2mp-sr-tree>replication-segment tree-id)

Full Context

configure router p2mp-sr-tree replication-segment tree-id

Description

This command configures the tree ID for the replication segment of the P2MP SR tree.

The no form of this command removes the tree ID from the replication segment.

Default

no tree-id

Parameters

tree-id

Specifies the tree ID.

Values

8193 to 16286

Platforms

All

Context

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

Full Context

configure subscriber-mgmt shcv-policy trigger

Description

This command enables to context to configure SHCV triggers.

Parameters

trigger-type

Specifies the trigger SHCV properties for the subscriber management group-interface.

Values

ip-conflict — Upon detecting an IP conflict for the new host, a trigger SHCV is sent using a unicast ARP/NS. The request verifies the old host’s connectivity to the BNG. An unresponsive host is removed from the system, allowing the new host to connect. The new host must resend its address request in order to be created as an ESM host in the system.

host-limit-exceeded — Upon exceeding the limit for (sla-profile host-limits or session-limits, sub-profile host-limits or session-limits, ipoe-session sap-session-limit, ipoe-session session-limit, and arp-host host-limit), a trigger SHCV is sent. The request verifies the old host’s connectivity to the BNG. An unresponsive host is removed from the system, allowing the new host to connect. The new host must resend its address request in order to be created as an ESM host in the system.

inactivity — A trigger SHCV is sent to the idle host to verify the host’s connectivity to the BNG. An unresponsive host is removed from the system.

mobility — Detects an IP or MAC conflict between different SAPs. Upon detecting a MAC or an IP conflict, a trigger SHCV is sent. The request verifies the old host’s connectivity to the BNG. An unresponsive host is removed from the system, allowing the new host to connect. The new host must resend its address request in order to be created as an ESM host in the system.

mac-learning — Specifies the trigger SHCV properties to learn the MAC address of static hosts. Upon a no shutdown, a trigger SHCV is sent to the host to learn the host’s MAC address.

Platforms

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

Context

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

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw>mobility trigger)

Full Context

configure service ies subscriber-interface group-interface wlan-gw mobility trigger

configure service vprn subscriber-interface group-interface wlan-gw mobility trigger

Description

This command specifies the type of packet used as a mobility trigger.

The no form of this command removes the parameters from the configuration and disables data-plane mobility.

Parameters

data

Specifies that data traffic be used as a trigger.

iapp

Specifies that Inter Access Point Protocol (IAPP) messages be used as a trigger.

control

Specifies that control traffic can be used as a trigger.

Platforms

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

Context

[Tree] (debug>router>rip trigger)

Full Context

debug router rip trigger

Description

This command enables debugging for RIP trigger updates.

Parameters

ip-int-name | ip-address

Debugs the RIP updates sent on the neighbor IP address or interface.

Platforms

All

Context

[Tree] (debug>router>ripng trigger)

Full Context

debug router ripng trigger

Description

This command enables debugging for RIP trigger updates.

Parameters

ip-int-name| ipv6-address

Debugs the RIP updates sent on the neighbor IP address or interface.

Platforms

All

Context

[Tree] (config>system>alarm-contact-input trigger-alarm-msg)

Full Context

configure system alarm-contact-input trigger-alarm-msg

Description

This command configures a message string to send with SNMP trap and log event messages that are generated when the system generates an alarm. The system generates the default message "Alarm Input Triggered” if no message is configured. The trigger-alarm-msg string is included in the log event when the pin changes from the normal state.

The no form of this command reverts to the default message "Alarm Input Triggered”.

Default

no-trigger-alarm-msg

Parameters

message-string

Specifies a printable character string, up to 160 characters.

Platforms

7750 SR-a

Context

[Tree] (config>log>event-trigger>event trigger-entry)

Full Context

configure log event-trigger event trigger-entry

Description

This command configures an instance of a trigger for an EHS handler. A trigger entry binds a set of matching criteria for a log event to a particular handler. If the log event occurs in the system and matches the criteria configured in the associated log filter then the handler will be executed.

The no form of this command removes the specified trigger entry.

Parameters

entry-id

Specifies the identifier of the EHS event trigger entry.

Values

1 to 1500

Platforms

All

Context

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

Full Context

configure port ethernet efm-oam trigger-fault

Description

This command configures the appropriate flag field in the Information OAM PDU, bursting three consecutive packets during the off cycle. If the local port state is operational, this command changes the local port state to "Link Up”. If the local port state is not operational, this configuration is installed as an EFM reason to prevent the port from returning to an Up operational state. This command can be used as a precursor to a port shutdown. This terminates the peering relationship without having to wait for protocol timeouts, assuming the peer supports the necessary action when receiving the dying gasp or critical event flag setting.

The no form of this command disables this functionality.

Default

no trigger-fault

Parameters

dying-gasp

Keyword to set the dying gasp flag.

critical-event

Keyword to set the critical event flag.

Platforms

All

Context

[Tree] (config>service>vpls>sap trigger-packet)

Full Context

configure service vpls sap trigger-packet

Description

This command enables triggering packet to initiate RADIUS authentication that provides a service context. The authentication, together with the service context for this request, creates a managed SAP. The VLAN is the same as the triggering packet. This SAP behaves as a regular SAP but the configuration is not user-editable and not maintained in the configuration file. The managed SAP remains active as long as the session is active.

The no form of this command reverts to the default.

Parameters

dhcp

Specifies whether the receipt of DHCP trigger packets on this VPLS SAP when the keyword capture-sap is specified in the sap command creation string, will result in a RADIUS authentication that will provide a service context and the creation of a SAP with a value of managed.

pppoe

Specifies whether the receipt of PPPoE trigger packets on this VPLS SAP when the keyword capture-sap is specified in the sap command creation string, will result in a RADIUS authentication that will provide a service context and the creation of a SAP with a value of managed.

arp

Indicates that ARP is the type of trigger packets for this entry.

dhcp6

Indicates that DHCP6 is the type of trigger packets for this entry.

rtr-solicit

Indicates that router solicit is the type of trigger packets for this entry.

data

Indicates that data is the type of trigger packets for this entry.

Platforms

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

Context

[Tree] (config>subscr-mgmt>git trigger-packet)

Full Context

configure subscriber-mgmt group-interface-template trigger-packet

Description

This command configures the router to process the specified types of trigger packets on dynamic SAPs.

The no form of this command disables the processing of trigger packets.

Platforms

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

Context

[Tree] (config>router triggered-policy)

Full Context

configure router triggered-policy

Description

This command triggers route policy re-evaluation.

By default, when a change is made to a policy in the config router policy options context and then committed, the change is effective immediately. There may be circumstances when the changes should or must be delayed; for example, if a policy change is implemented that would affect every BGP peer on a router, the consequences could be dramatic. It is more effective to control changes on a peer by peer basis.

If the triggered-policy command is enabled, and a given peer is established, and you want the peer to remain up, then, in order for a change to a route policy to take effect, a clear command with the soft or soft-inbound option must be used. In other words, when a triggered-policy is enabled, any routine policy change or policy assignment change within the protocol will not take effect until the protocol is reset or a clear command is issued to re-evaluate route policies; for example, clear router bgp neighbor x.x.x.x soft. This keeps the peer up and the change made to a route policy is applied only to that peer, or group of peers.

Default

no triggered-policy

Platforms

All

Context

[Tree] (config>subscr-mgmt>acct-plcy triggered-updates)

Full Context

configure subscriber-mgmt radius-accounting-policy triggered-updates

Description

Commands in this context configure non-periodic accounting updates that are triggered by specific events.

Platforms

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

Context

[Tree] (config>ipsec>trust-anchor-profile trust-anchor)

Full Context

configure ipsec trust-anchor-profile trust-anchor

Description

This command specifies a CA profile as a trust anchor CA. Up to 8 multiple trust anchors can be specified in a single trust anchor profile.

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

Parameters

ca-profile-name

Specifies the name of the trust anchor profile, up to 32 characters.

Platforms

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

Context

[Tree] (config>system>security>tls>trust-anchor-profile trust-anchor)

Full Context

configure system security tls trust-anchor-profile trust-anchor

Description

This command configures a trust anchor with a CA profile used by the TLS profile. Up to eight CA profiles can be configured under the trust anchor. TLS will read the CA profiles one by one to try to authenticate the server certificate.

Parameters

ca-profile-name

Specifies the name of the TLS trust anchor, up to 32 characters.

Platforms

All

Context

[Tree] (config>ipsec trust-anchor-profile)

Full Context

configure ipsec trust-anchor-profile

Description

This command specifies the trust anchor profile name for the IPsec tunnel or IPsec GW.

Default

no trust-anchor-profile

Parameters

name

Specifies the name of trust anchor profile up to 32 characters.

Platforms

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

Context

[Tree] (config>service>ies>if>sap>ipsec-gw>cert trust-anchor-profile)

[Tree] (config>ipsec>trans-mode-prof>dyn>cert trust-anchor-profile)

[Tree] (config>router>if>ipsec>ipsec-tunnel>dyn>cert trust-anchor-profile)

[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel>dyn>cert trust-anchor-profile)

[Tree] (config>service>vprn>if>sap>ipsec-gw>cert trust-anchor-profile)

[Tree] (config>service>ies>if>ipsec>ipsec-tunnel>dyn>cert trust-anchor-profile)

[Tree] (config>service>vprn>if>sap>ipsec-tunnel>cert trust-anchor-profile)

Full Context

configure service ies interface sap ipsec-gw cert trust-anchor-profile

configure ipsec ipsec-transport-mode-profile dynamic-keying cert trust-anchor-profile

configure router interface ipsec ipsec-tunnel dynamic-keying cert trust-anchor-profile

configure service vprn interface ipsec ipsec-tunnel dynamic-keying cert trust-anchor-profile

configure service vprn interface sap ipsec-gw cert trust-anchor-profile

configure service ies interface ipsec ipsec-tunnel dynamic-keying cert trust-anchor-profile

configure service vprn interface sap ipsec-tunnel cert trust-anchor-profile

Description

This command specifies the name of trust anchor profile used for certificate authentication.

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

Default

no trust-anchor-profile

Parameters

name

Specifies the name of trust anchor profile, up to 32 characters.

Platforms

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

• configure service vprn interface sap ipsec-gw cert trust-anchor-profile
• configure ipsec ipsec-transport-mode-profile dynamic-keying cert trust-anchor-profile
• configure service ies interface sap ipsec-gw cert trust-anchor-profile

VSR

• configure router interface ipsec ipsec-tunnel dynamic-keying cert trust-anchor-profile
• configure service vprn interface ipsec ipsec-tunnel dynamic-keying cert trust-anchor-profile
• configure service ies interface ipsec ipsec-tunnel dynamic-keying cert trust-anchor-profile

Context

[Tree] (config>system>security>tls>server-tls-profile>authenticate-client trust-anchor-profile)

[Tree] (config>system>security>tls>client-tls-profile trust-anchor-profile)

Full Context

configure system security tls server-tls-profile authenticate-client trust-anchor-profile

configure system security tls client-tls-profile trust-anchor-profile

Description

This command assigns the trust anchor used by this TLS profile to authenticate the server or client.

The no form of the command removes the configured trust anchor profile.

Parameters

name

Specifies the name of the trust anchor profile.

Platforms

All

Context

[Tree] (config>system>security>tls trust-anchor-profile)

Full Context

configure system security tls trust-anchor-profile

Description

This command configures a trust anchor profile to be used in the TLS profile. The trust anchor is used for authentication of the server certificate.

Parameters

name

Specifies the name of the trust anchor profile, up to 32 characters.

create

Keyword used to create the trust anchor profile.

Platforms

All

Context

[Tree] (config>router>if>dhcp trusted)

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

[Tree] (config>service>ies>if>dhcp trusted)

[Tree] (config>service>vprn>if>dhcp trusted)

Full Context

configure router interface dhcp trusted

configure service ies subscriber-interface group-interface dhcp trusted

configure service ies interface dhcp trusted

configure service vprn interface dhcp trusted

Description

This command enables relaying untrusted packets. According to RFC 3046, DHCP Relay Agent Information Option, a DHCP request where the giaddr is 0.0.0.0 and which contains an Option 82 field in the packet, should be discarded, unless it arrives on a "trusted” circuit. If the trusted mode is enabled on an IP interface, the Relay Agent (the router) modifies the requested giaddr to be equal to the ingress interface and forward the request.

The no form of this command reverts to the default.

Default

no trusted

Platforms

All

• configure service ies interface dhcp trusted
• configure router interface dhcp trusted
• configure service vprn interface dhcp trusted

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

• configure service ies subscriber-interface group-interface dhcp trusted

Context

[Tree] (config>service>vpls>bgp-evpn>mac-duplication trusted-mac-time)

Full Context

configure service vpls bgp-evpn mac-duplication trusted-mac-time

Description

This command determines how long a MAC address needs to stay in the FDB as type learned without being flushed or changed in its type so that the MAC is declared as trusted for the mac-duplication procedures. If the MAC changes from SAP to SAP within the same VPLS service and node, the MAC does not reset its trusted MAC timer.

Default

trusted-mac-time 5

Parameters

range

Specifies the time, in minutes, before the MAC address can be flushed from the FDB.

Values

1 to 15

Platforms

All

Context

[Tree] (config>app-assure>group>ip-id-asst>pdns trusted-server)

Full Context

configure application-assurance group ip-identification-assist passive-dns trusted-server

Description

Commands in this context configure a DNS server that the IP identification assist feature is allowed to passively monitor.

The no form of this command deletes the DNS server.

Parameters

address

Specifies the IPv4 or IPv6 address for the DNS server.

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

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

Context

[Tree] (config>ipsec ts-list)

Full Context

configure ipsec ts-list

Description

This command creates a new traffic selector (TS).

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

Parameters

list-name

Specifies the name of the TS-list.

Platforms

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

Context

[Tree] (config>system>security>tech-support ts-location)

Full Context

configure system security tech-support ts-location

Description

The ts-location command is used (along with an automatic system generated file name) when no file-url parameter is provided for the admin tech-support command. If no ts-location is defined then the operator must provide a file-url with the admin tech-support command itself.

The directory specified for the ts-location is not auto-created by SR OS. The operator must ensure that it exists.

See the admin tech-support command for more details about the system generated file name.

Default

no ts-location

Parameters

file-url

Specifies the destination directory for auto-named tech-support files (when no file-url is specified with the admin tech-support command). The file-url for the ts-location must be a directory (no filename or extension). The root directory (for example, cf1:\) is blocked for local compact flash destinations. A sub-directory (for example, cf2:\tech-support) must be used if local cf is the location.

Values

local-url | remote-url
local-url	[cflash-id/][file-path] 200 chars max, including cflash-id
	directory length 99 chars max each
remote-url	[ftp://login:pswd@remote-locn/][file-path]
	247 chars max
	directory length 99 chars max 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:

Platforms

All

Context

[Tree] (config>ipsec>client-db>client ts-negotiation)

Full Context

configure ipsec client-db client ts-negotiation

Description

This command specifies the traffic selector (TS) to be used for tunnel setup.

The no form of this command reverts to the default.

Default

no ts-negotiation

Parameters

list-name

Specifies the TS list used by this tunnel, up to 32 characters.

Platforms

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

Context

[Tree] (config>service>ies>if>sap>ipsec-gw ts-negotiation)

[Tree] (config>service>vprn>if>sap>ipsec-gw ts-negotiation)

Full Context

configure service ies interface sap ipsec-gw ts-negotiation

configure service vprn interface sap ipsec-gw ts-negotiation

Description

This command enables the IKEv2 traffic selector negotiation with the specified ts-list.

Parameters

list-name

Specifies the ts-list name

Platforms

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

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>video>analyzer>alarms ts-sync-loss)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>source-override>video>analyzer>alarms ts-sync-loss)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>video>analyzer>alarms ts-sync-loss)

Full Context

configure mcast-management multicast-info-policy bundle channel video analyzer alarms ts-sync-loss

configure mcast-management multicast-info-policy bundle channel source-override video analyzer alarms ts-sync-loss

configure mcast-management multicast-info-policy bundle video analyzer alarms ts-sync-loss

Description

This command configures the analyzer to check for synchronization loss errors.

Default

no ts-sync-loss

Platforms

7450 ESS, 7750 SR, 7750 SR-s

Context

[Tree] (config>subscr-mgmt>pfcp-association>tx ttl)

Full Context

configure subscriber-mgmt pfcp-association tx ttl

Description

This command configures initial TTL value that is sent in the IP header.

Default

ttl 255

Parameters

value

Specifies the TTL value, in seconds.

This value must 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 255

Platforms

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

Context

[Tree] (config>saa>test>type-multi-line>lsp-ping ttl)

[Tree] (config>saa>test>type-multi-line>lsp-ping>sr-policy ttl)

Full Context

configure saa test type-multi-line lsp-ping ttl

configure saa test type-multi-line lsp-ping sr-policy ttl

Description

This command configures a time-to-live value for the MPLS label.

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

Default

ttl 255

Parameters

label-ttl

Specifies the time-to-live value.

Values

1 to 255

Default

255

Platforms

All

Context

[Tree] (config>saa>test>type-multi-line>lsp-trace>sr-policy ttl)

Full Context

configure saa test type-multi-line lsp-trace sr-policy ttl

Description

This command configures minimum and maximum time-to-live values.

The no form of this command removes the configuration.

Parameters

min-label-ttl

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

Values

1 to 255

Default

1

max-label-ttl

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

Values

1 to 255

Default

30

Platforms

All

Context

[Tree] (config>oam-pm>session>ip ttl)

Full Context

configure oam-pm session ip ttl

Description

This command defines the value of the TTL field of the packet header.

The no form of this command restores the default value.

Default

ttl 225

Parameters

time-to-live

Specifies the value to be used in the TTL field.

Values

1 to 255

Default

255

Platforms

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

Context

[Tree] (config>oam-pm>session>mpls ttl)

Full Context

configure oam-pm session mpls ttl

Description

This command defines the value of the MPLS TTL for DM packets.

The no form of this command reverts the default value.

Default

ttl 255

Parameters

time-to-live

Specifies the value to be used in the TTL field.

Values

1 to 255

Default

255

Platforms

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

Context

[Tree] (config>test-oam>icmp>ping-template ttl)

Full Context

configure test-oam icmp ping-template ttl

Description

This command configures the TTL value used in the outgoing ping packet. The interface being tested must be directly connected on the same subnet.

The no form of this command reinstates the default value for TTL.

Default

ttl 1

Parameters

value

Specifies the value to be used in the TTL field.

Values

1 to 255

Platforms

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

Context

[Tree] (config>test-oam>link-meas>template>twl ttl)

Full Context

configure test-oam link-measurement measurement-template twamp-light ttl

Description

This command configures the Time to Live (TTL) value in the TWAMP Light test packet.

Default

ttl 1

Parameters

time-to-live

Specifies the value to be used in the TTL field.

Values

1 to 255

Platforms

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

Context

[Tree] (config>filter>ip-filter>entry>match ttl)

Full Context

configure filter ip-filter entry match ttl

Description

This command configures the Time To Live (TTL) match criteria.

The no form of this command removes the configuration.

Default

no ttl

Parameters

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

ttl-value

Specifies the maximum TTL value.

Values

0 to 255

Platforms

All

Context

[Tree] (config>test-oam>lag-meas>template>twl ttl)

Full Context

configure test-oam lag-ip-measurement lag-ip-measurement-template twamp-light ttl

Description

This command configures the time-to-live (TTL) in the IP header of the launched TWAMP Light packet.

Default

ttl 1

Parameters

time-to-live

Specifies the TTL value, expressed as a decimal integer.

Values

1 to 255

Default

1

Platforms

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

Context

[Tree] (config>service>ies>if>icmp ttl-expired)

Full Context

configure service ies interface icmp ttl-expired

Description

This command configures the rate Internet Control Message Protocol (ICMP) TTL expired messages are issued by the IP interface.

By default, generation of ICMP TTL expired messages is enabled at a maximum rate of 100 per 10 second time interval.

The no form of this command disables the limiting the rate of TTL expired messages on the router interface and reverts to the default values.

Default

ttl-expired 100 10

Parameters

number

The maximum number of ICMP TTL expired messages to send, expressed as a decimal integer. This parameter must be specified with the seconds parameter.

Values

10 to 2000

seconds

The time frame in seconds used to limit the number of ICMP TTL expired messages that can be issued, expressed as a decimal integer.

Values

1 to 60

Platforms

All

Context

[Tree] (config>service>ies>sub-if>grp-if>icmp ttl-expired)

[Tree] (config>service>vprn>sub-if>grp-if>icmp ttl-expired)

Full Context

configure service ies subscriber-interface group-interface icmp ttl-expired

configure service vprn subscriber-interface group-interface icmp ttl-expired

Description

This command configures the rate Internet Control Message Protocol (ICMP) TTL expired messages are issued by the IP interface.

By default, generation of ICMP TTL expired messages is enabled at a maximum rate of 100 per 10 second time interval.

The no form of this command disables limiting the rate of TTL expired messages on the router interface and reverts to the default values.

Default

ttl-expired 100 10

Parameters

number

Specifies the maximum number of ICMP TTL expired messages to send, expressed as a decimal integer. This parameter must be specified with the seconds parameter.

Values

10 to 2000

seconds

Specifies the time frame in seconds used to limit the number of ICMP TTL expired messages that can be issued, expressed as a decimal integer.

Values

1 to 60

use-matching-address

Specifies to use a matching subscriber interface address as the source address.

Platforms

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

Context

[Tree] (config>subscr-mgmt>git>ipv4>icmp ttl-expired)

Full Context

configure subscriber-mgmt group-interface-template ipv4 icmp ttl-expired

Description

This command configures the rate at which ICMP TTL expired messages are issued by the IP interface.

By default, generation of ICMP TTL expired messages is enabled at a maximum rate of 100 per 10 second time interval.

The no form of this command disables limiting of the rate at which TTL expired messages are generated on the router interface.

Default

ttl-expired number 100 seconds 10

Parameters

number

Specifies the maximum number of ICMP TTL expired messages to send. This parameter must be specified with the seconds parameter.

Values

10 to 2000

seconds

Specifies the time, in seconds, used to limit the number of ICMP TTL expired messages that can be generated, expressed as a decimal integer.

Values

1 to 60

Platforms

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

Context

[Tree] (config>service>vprn>nw-if>icmp ttl-expired)

[Tree] (config>service>vprn>if>icmp ttl-expired)

Full Context

configure service vprn network-interface icmp ttl-expired

configure service vprn interface icmp ttl-expired

Description

This command configures the rate of Internet Control Message Protocol (ICMP) TTL expired messages are issued by the IP interface.

By default, generation of ICMP TTL expired messages is enabled at a maximum rate of 100 per 10 second time interval.

The no form of this command disables the limiting the rate of TTL expired messages on the router interface.

Default

ttl-expired 100 10

Parameters

number

Specifies the maximum number of ICMP TTL expired messages to send, expressed as a decimal integer. This parameter must be specified with the seconds parameter.

Values

10 to 2000

seconds

Specifies the time frame in seconds used to limit the number of ICMP TTL expired messages that can be issued, expressed as a decimal integer.

Values

1 to 60

Platforms

All

Context

[Tree] (config>router>if>icmp ttl-expired)

Full Context

configure router interface icmp ttl-expired

Description

This command configures the rate that Internet Control Message Protocol (ICMP) Time To Live (TTL) expired messages are issued by the IP interface.

By default, generation of ICMP TTL expired messages is enabled at a maximum rate of 100 per 10 second time interval.

The no form of this command disables the generation of TTL expired messages.

Default

ttl-expired 100 10 — Maximum of 100 TTL expired message in 10 seconds.

Parameters

number

The maximum number of ICMP TTL expired messages to send, expressed as a decimal integer. The seconds parameter must also be specified.

Values

10 to 2000

seconds

The time frame, in seconds, used to limit the number of ICMP TTL expired messages that can be issued, expressed as a decimal integer.

Values

1 to 60

Platforms

All

Context

[Tree] (config>app-assure>group>tether-detect ttl-monitoring)

Full Context

configure application-assurance group tethering-detection ttl-monitoring

Description

Commands in this context configure the scope of analysis for TCP and UDP traffic for tethering detection.

Platforms

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

Context

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

Full Context

configure service vprn ttl-propagate

Description

Commands in this context configure TTL propagation for transit and locally generated packets in a given VPRN routing context.

Platforms

All

Context

[Tree] (config>router ttl-propagate)

Full Context

configure router ttl-propagate

Description

Commands in this context configure TTL propagation for transit and locally generated packets in the Global Routing Table (GRT) and VPRN routing contexts

Platforms

All

Context

[Tree] (config>subscr-mgmt>bgp-prng-plcy ttl-security)

Full Context

configure subscriber-mgmt bgp-peering-policy ttl-security

Description

This command configures the TTL security parameters for incoming packets.

The no form of this command reverts to the default.

Parameters

min-ttl-value

Specifies the minimum TTL value for an incoming BGP packet.

Values

1 to 255

Platforms

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

Context

[Tree] (config>service>vprn>bgp>group ttl-security)

[Tree] (config>service>vprn>bgp>group>neighbor ttl-security)

Full Context

configure service vprn bgp group ttl-security

configure service vprn bgp group neighbor ttl-security

Description

Configure TTL security parameters for incoming packets.

Parameters

min-ttl-value

Specifies the minimum TTL value for an incoming BGP packet.

Values

1 to 255

Default

1

Platforms

All

Context

[Tree] (config>router>ldp>tcp-session-params>peer-transport ttl-security)

[Tree] (config>system>login-control>ssh ttl-security)

[Tree] (config>router>bgp>group>neighbor ttl-security)

[Tree] (config>router>bgp>group ttl-security)

[Tree] (config>system>login-control>telnet ttl-security)

Full Context

configure router ldp tcp-session-parameters peer-transport ttl-security

configure system login-control ssh ttl-security

configure router bgp group neighbor ttl-security

configure router bgp group ttl-security

configure system login-control telnet ttl-security

Description

This command configures TTL security parameters for incoming packets. When the feature is enabled, LDP will accept incoming IP packets from a peer only if the TTL value in the packet is greater than or equal to the minimum TTL value configured for that peer. Per-peer-queueing must be enabled in order for TTL protection to operate.

The no form of this command disables TTL security.

Parameters

min-ttl-value

Specifies the minimum TTL value for an incoming BGP packet.

Values

1 to 255

Platforms

All

Context

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

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

Full Context

configure router l2tp group tunnel

configure service vprn l2tp group tunnel

Description

This command configures an L2TP tunnel. A tunnel exists between a LAC-LNS pair and consists of a Control Connection and zero or more L2TP sessions. The tunnel carries encapsulated PPP datagrams and control messages between the LAC and the L2TP Network Server (LNS).

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

Parameters

tunnel-name

Specifies a valid string to identify an L2TP, up to 32 characters.

create

Mandatory keyword to create a new tunnel.

Platforms

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

Context

[Tree] (debug>router>l2tp tunnel)

Full Context

debug router l2tp tunnel

Description

This command enables debugging for an L2TP tunnel.

Parameters

connection-id

Specifies the connection ID of the L2TP session associated with this session.

Values

1 to 4294967295

Platforms

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

Context

[Tree] (config>service>epipe>pbb tunnel)

Full Context

configure service epipe pbb tunnel

Description

This command configures a Provider Backbone Bridging (PBB) tunnel with Backbone VPLS (B-VPLS) service information.

Parameters

service-id

Specifies the B-VPLS service for the PBB tunnel associated with this service.

Values

service-id: 1 to 2147483648

svc-name: 64 characters maximum

backbone-dest-mac mac-name

Specifies the backbone destination MAC name for PBB packets up to 32 characters in length.

backbone-dest-mac ieee-address

Specifies the backbone destination MAC-address for PBB packets as xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx.

isid ISID

Specifies a 24 bit service instance identifier for the PBB tunnel associated with this service. As part of the PBB frames, it is used at the destination PE as a demultiplexer field.

Values

0 to 16777215

Platforms

All

Context

[Tree] (debug>ipsec tunnel)

Full Context

debug ipsec tunnel

Description

This command enables debugging for specified IPsec tunnel.

Parameters

ipsec-tunnel-name

Specifies the name of ipsec-tunnel, up to 32 characters.

detail

Displays detailed debug information.

no-dpd-debug

Stops logging IKEv1 and IKEv2 DPD events for less noise during debug.

display-keys

Specifies the IKE-SA and CHILD-SA keys for inclusion in the debug output.

Platforms

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

Context

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

Full Context

debug router rib-api tunnel

Description

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

Parameters

ip-address

Specifies the IPv4 or IPv6 address of the RIB-API tunnel.

Values

ipv4-address:	a.b.c.d
ipv6-address:	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x:	[0 to FFFF]H
	d:	[0 to 255]D

Platforms

All

Context

[Tree] (config>system>grpc-tunnel tunnel)

Full Context

configure system grpc-tunnel tunnel

Description

Commands in this context configure gRPC tunnel parameters for the specified tunnel. There can be multiple tunnels to one or more destinations.

The no form of this command removes the specified gRPC tunnel.

Parameters

name

Specifies the tunnel name, up to 32 characters.

create

Keyword used to create a tunnel.

Platforms

All

Context

[Tree] (config>oam-pm>session>ip tunnel)

Full Context

configure oam-pm session ip tunnel

Description

Commands in this context configure packet tunneling options for the session. This command and the oam-pm session ip forwarding command are mutually exclusive.

Platforms

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

Context

[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute tunnel-client-attrs)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute tunnel-client-attrs

Description

This command specifies that tunnel attributes should be included into RADIUS accounting 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

Context

[Tree] (config>port>ethernet>dot1x tunnel-dot1q)

Full Context

configure port ethernet dot1x tunnel-dot1q

Description

This command configures the tunneling of single tagged (dot1q) dot1x packets arriving on the port. When enabled, the router extracts these packets to the CPM.

The no form of this command disables the tunelling of the dot1q dot 1x packets on the port.

Default

tunnel-dot1q

Platforms

All

Context

[Tree] (config>router>ldp tunnel-down-damp-time)

Full Context

configure router ldp tunnel-down-damp-time

Description

This command specifies the time interval (in s), that LDP waits before posting a tunnel down event to the Tunnel Table Manager (TTM).

When LDP can no longer resolve a FEC and de-activates it, it de-programs the NHLFE in the data path. It will however delay deleting the LDP tunnel entry in the TTM until the tunnel-down-damp-time timer expires. This means users of the LDP tunnel, such as SDPs (all services) and BGP (L3 VPN), will not be notified immediately. Traffic is still blackholed because the forwarding engine NHLFE has been de-programmed.

If the FEC gets resolved before the tunnel-down-damp-time timer expires, then LDP programs the forwarding engine with the new NHLFE and performs a tunnel modify event in TTM updating the dampened entry in TTM with the new NHLFE information. If the FEC does not get resolved and the tunnel-down-damp-time timer expires, LDP posts a tunnel down event to TTM which deletes the LDP tunnel.

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

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

The no form of this command resumes the default value of this command.

Default

no tunnel-down-damp-time (which equals a value of 3 seconds)

Parameters

seconds

Specifies the time interval (in s), that LDP waits before posting a tunnel down event to the Tunnel Table Manager.

Platforms

All

Context

[Tree] (config>service>vpls tunnel-elmi)

Full Context

configure service vpls tunnel-elmi

Description

This command enables the tunneling of E-LMI packets in a VPLS service. The following must also be the case for this command to function:

• the configure port ethernet elmi mode uni-n command is not configured

• the configure service vpls tunnel-elmi true command is enabled

• the E-LMI packets map to that VPLS service

This command configures E-LMI packets in a VPLS service to be tunneled when the configure port ethernet elmi mode uni-n is not configured and the configure service vpls tunnel-elmi is enabled and the E-LMI packets map to that VPLS service.

The no form of this command disables tunneling of the E-LMI packets for a VPLS service.

Default

no tunnel-elmi

Platforms

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

Context

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw tunnel-encaps)

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

Full Context

configure service vprn subscriber-interface group-interface wlan-gw tunnel-encaps

configure service ies subscriber-interface group-interface wlan-gw tunnel-encaps

Description

Commands in this context configure tunnel encapsulation parameters.

Platforms

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

Context

[Tree] (config>anysec tunnel-encryption)

Full Context

configure anysec tunnel-encryption

Description

Commands in this context configure tunnel encryption.

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

Context

[Tree] (debug>router>isis tunnel-endpoint)

Full Context

debug router isis tunnel-endpoint

Description

This command enables debugging for an ISIS tunnel endpoint.

The no form of the command disables the debugging.

Parameters

tunnel-spf

Debugs tunnel SPF information.

ip-address

When specified, only packets with the specified address are debugged.

Platforms

All

Context

[Tree] (debug>router>ospf tunnel-endpoint)

[Tree] (debug>router>ospf3 tunnel-endpoint)

Full Context

debug router ospf tunnel-endpoint

debug router ospf3 tunnel-endpoint

Description

This command enables debugging for OSPF tunnel endpoints.

Parameters

tunnel-spf

Specifies the tunnel SPF IP address.

tunnel-leak

Specifies the tunnel leak IP address.

ip-address

Specifies the IP address.

Platforms

All

Context

[Tree] (config>test-oam>build-packet>header>gtp-user tunnel-endpoint-id)

Full Context

configure test-oam build-packet header gtp-user tunnel-endpoint-id

Description

This command defines the GTP tunnel endpoint ID for the GTP user header.

The no form of this command removes the tunnel endpoint ID value.

Default

tunnel-endpoint-id 0

Parameters

tunnel-endpoint-id

Specifies the GTP tunnel endpoint ID to be used in the test GTP header.

Values

0 to 4294967295

Platforms

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

Context

[Tree] (debug>oam>build-packet>packet>field-override>header>gtp-user tunnel-endpoint-id)

Full Context

debug oam build-packet packet field-override header gtp-user tunnel-endpoint-id

Description

This command debugs the GTP tunnel endpoint ID for the GTP user header.

The no form of this command removes the tunnel endpoint ID value.

Default

no override

Parameters

tunnel-endpoint-id

Specifies the GTP tunnel endpoint ID to be used in the test GTP header.

Values

0 to 4294967295

Platforms

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

Context

[Tree] (config>service>sdp tunnel-far-end)

Full Context

configure service sdp tunnel-far-end

Description

This command enables the user to specify an SDP tunnel destination address that is different from the configuration in the SDP far-end option. The SDP must be shutdown first to add or change the configuration of the tunnel-far-end option.

When this option is enabled, service packets are encapsulated using an LDP LSP with a FEC prefix matching the value entered in ip-address. By default, service packets are encapsulated using an LDP LSP with a FEC prefix matching the address entered in the SDP far-end option.

The T-LDP session to the remote PE is still targeted to the address configured under the far-end option. This means that targeted hello messages are sent to the far-end address, which is also the LSR-ID of the remote node. TCP based LDP messages, such as initialization and label mapping messages, are sent to the address specified in the transport-address field of the "hello” message received from the remote PE. This address can be the same as the remote PE LSR-ID, or a different address. This feature works, however, if the signaling option in the SDP is set to off instead of tldp, in which case, the service labels are statically configured.

This feature operates on an SDP of type LDP only. It can be used with VLL, VPLS, and VPRN services when an explicit binding to an SDP with the tunnel-far-end is specified. It also operates with a spoke interface on an IES or VPRN service. Finally, this feature operates with a BGP AD based VPLS service when the use-provisioned-sdp option is enabled in the pseudowire template.

This feature is not supported in an SDP of type MPLS when an RSVP LSP name is configured under the SDP. It also does not work with a mixed-lsp SDP.

The no form of this command disables the use of the tunnel-far-end option and returns to using the address specified in the far-end.

Default

no tunnel-far-end

Parameters

ip-address | ipv6-address

Specifies the system address of the far-end router for the SDP in dotted decimal notation.

Platforms

All

Context

[Tree] (config>service>ipipe>eth-cfm tunnel-fault)

[Tree] (config>service>vpls>sap>eth-cfm tunnel-fault)

[Tree] (config>service>ies>eth-cfm tunnel-fault)

[Tree] (config>service>vpls>eth-cfm tunnel-fault)

[Tree] (config>service>vprn>eth-cfm tunnel-fault)

[Tree] (config>service>epipe>sap>eth-cfm tunnel-fault)

[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm tunnel-fault)

[Tree] (config>service>vprn>if>sap>eth-cfm tunnel-fault)

[Tree] (config>service>epipe>eth-cfm tunnel-fault)

[Tree] (config>service>ipipe>sap>eth-cfm tunnel-fault)

[Tree] (config>service>ies>if>sap>eth-cfm tunnel-fault)

[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm tunnel-fault)

Full Context

configure service ipipe eth-cfm tunnel-fault

configure service vpls sap eth-cfm tunnel-fault

configure service ies eth-cfm tunnel-fault

configure service vpls eth-cfm tunnel-fault

configure service vprn eth-cfm tunnel-fault

configure service epipe sap eth-cfm tunnel-fault

configure service ies subscriber-interface group-interface sap eth-cfm tunnel-fault

configure service vprn interface sap eth-cfm tunnel-fault

configure service epipe eth-cfm tunnel-fault

configure service ipipe sap eth-cfm tunnel-fault

configure service ies interface sap eth-cfm tunnel-fault

configure service vprn subscriber-interface group-interface sap eth-cfm tunnel-fault

Description

Allows the individual service SAPs to react to changes in the tunnel MEP state. When tunnel-fault accept is configured at the service level, the SAP will react according to the service type, Epipe will set the operational flag and VPLS, IES and VPRN SAP operational state will become down on failure or up on clear. This command triggers the OAM mapping functions to mate SAPs and bindings in an Epipe service as well as setting the operational flag. If AIS generation is the requirement for the Epipe services this command is not required. See the ais-enable command under the config>service>epipe>sap>eth-cfm>ais-enable context for more details. This works in conjunction with the tunnel-fault accept on the individual SAPs. Both must be set to accept to react to the tunnel MEP state. By default the service level command is "ignore” and the SAP level command is "accept”. This means simply changing the service level command to "accept” will enable the feature for all SAPs. This is not required for Epipe services that only wish to generate AIS on failure.

Default

tunnel-fault ignore (Service Level)

tunnel-fault accept (SAP Level for Epipe and VPLS)

Parameters

accept

Shares fate with the facility tunnel MEP.

ignore

Does not share fate with the facility tunnel MEP.

Platforms

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

• configure service epipe eth-cfm tunnel-fault
• configure service ipipe eth-cfm tunnel-fault
• configure service vpls eth-cfm tunnel-fault
• configure service ies interface sap eth-cfm tunnel-fault
• configure service vpls sap eth-cfm tunnel-fault
• configure service epipe sap eth-cfm tunnel-fault
• configure service ipipe sap eth-cfm tunnel-fault
• configure service ies eth-cfm tunnel-fault
• configure service vprn eth-cfm tunnel-fault
• configure service vprn interface sap eth-cfm tunnel-fault

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

• configure service vprn subscriber-interface group-interface sap eth-cfm tunnel-fault
• configure service ies subscriber-interface group-interface sap eth-cfm tunnel-fault

Context

[Tree] (config>isa tunnel-group)

Full Context

configure isa tunnel-group

Description

This command allows a tunnel group to be created or edited. A tunnel group is a set of one or more MS-ISAs that support the origination and termination of IPsec and IP/GRE tunnels. All of the MS-ISAs in a tunnel group must have isa-tunnel as their configured mda-type.

The no form of this command deletes the specified tunnel group from the configuration

Parameters

tunnel-group-id

Identifies the tunnel group.

Values

1 to 16

isa-scale-mode

Defines the maximum number of tunnels (all types combined) which can be established on each ISA of the tunnel group and for the whole tunnel-group. When it is not explicitly specified, isa-scale-mode has a default value, but that value is different on different platforms.

Values

tunnel-limit-2k, tunnel-limit-32k, tunnel-limit-64k, tunnel-limit-8, tunnel-limit-32

create

Mandatory keyword used when creating tunnel group in the ISA context. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

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

Context

[Tree] (config>redundancy>multi-chassis>peer>mc-ipsec tunnel-group)

Full Context

configure redundancy multi-chassis peer mc-ipsec tunnel-group

Description

This command enables multi-chassis redundancy for specified tunnel-group; or enters an already configured tunnel-group context. The configured tunnel-group could failover independently.

The no form of this command removes the tunnel group ID from the configuration.

Parameters

tunnel-group-id

Specifies the tunnel-group identifier.

Values

1 to 16

Platforms

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

Context

[Tree] (config>redundancy>multi-chassis>peer>mc-ipsec tunnel-group)

Full Context

configure redundancy multi-chassis peer mc-ipsec tunnel-group

Description

This command enables multi-chassis redundancy for specified tunnel-group; or enters an already configured tunnel-group context. The configured tunnel-group could failover independently.

The no form of this command removes the tunnel group ID from the configuration.

Parameters

tunnel-group-id

Specifies the tunnel-group identifier.

Values

1 to 16

Platforms

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

Context

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

Full Context

configure redundancy multi-chassis peer sync tunnel-group

Description

This command enables multi-chassis synchronization of IPsec states of specified tunnel-groups with a peer. The sync-tag parameter is used to match corresponding tunnel-group on both peers. IPsec states will be synchronized between tunnel-groups with same sync-tag.

Parameters

tunnel-group-id

Specifies the ID of the tunnel group.

tag-name

Specifies the name of the sync-tag.

Platforms

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

Context

[Tree] (config>redundancy>multi-chassis>ipsec-domain tunnel-group)

Full Context

configure redundancy multi-chassis ipsec-domain tunnel-group

Description

This command specifies the tunnel group ID for the IPsec domain.

The no form of this command removes the tunnel group ID from the configuration.

Default

no tunnel-group

Parameters

tunnel-group-id

Specifies the tunnel group ID, up to 64 characters.

Platforms

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

Context

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

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

Full Context

configure test-oam build-packet header l2tp tunnel-id

debug oam build-packet packet field-override header l2tp tunnel-id

Description

This command defines the tunnel ID to be used in the L2TP header.

The no form of this command removes the tunnel ID value.

Default

tunnel-id 0

Parameters

tunnel-id

Specifies the L2TP tunnel ID to be used in the L2TP header.

Values

0 to 65535

Platforms

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

Context

[Tree] (config>router>igmp tunnel-interface)

[Tree] (config>router tunnel-interface)

Full Context

configure router igmp tunnel-interface

configure router tunnel-interface

Description

This command creates a tunnel interface associated with an RSVP P2MP LSP. IPv4 multicast packets are forwarded over the P2MP LSP at the ingress LER based on a static join configuration of the multicast group against the tunnel interface associated with the originating P2MP LSP. At the egress LER, packets of a multicast group are received from the P2MP LSP via a static assignment of the specific <S,G> to the tunnel interface associated with a terminating LSP.

At ingress LER, the tunnel interface identifier consists of a string of characters representing the LSP name for the RSVP P2MP LSP. The user can create one or more tunnel interfaces and associate each to a different RSVP P2MP LSP.

At egress LER, the tunnel interface identifier consists of a couple of string of characters representing the LSP name for the RSVP P2MP LSP followed by the system address of the ingress LER. The LSP name must correspond to a P2MP LSP name configured by the user at the ingress LER. The LSP name string must not contain "::” (two :s) nor contain a ":” (single ":”) at the end of the LSP name. However, a ":” (single ":”) can appear anywhere in the string except at the end of the name.

Parameters

rsvp-p2mp lsp-name

Specifies the LSP. The LSP name can be up to 32 characters long and must be unique.

ldp-p2mp p2mp-id

Identifier used for signaling MLDP P2MP LSP.

Values

1 to 4294967296 (on leaf node)

1 to 8192 (on root node)

sender sender-address

Specifies the sender IP address: a.b.c.d.

Platforms

All

Context

[Tree] (debug>router>pim tunnel-interface)

Full Context

debug router pim tunnel-interface

Description

This command enables debugging for PIM tunnel interfaces.

The no form of this command disables debugging for PIM tunnel interfaces.

Parameters

lsp-name

Specifies the LSP for RSVP P2MP.

ip-address

Specifies the IP address of the sender.

p2mp-id

Specifies the P2MP ID for LDP P2MP.

detail

Displays detailed information for PIM tunnel interfaces.

Platforms

All

Context

[Tree] (config>router>pim tunnel-interface)

Full Context

configure router pim tunnel-interface

Description

This command creates a tunnel interface associated with an RSVP P2MP LSP. IPv4 multicast packets are forwarded over the P2MP LSP at the ingress LER based on a static join configuration of the multicast group against the tunnel interface associated with the originating P2MP LSP. At the egress LER, packets of a multicast group are received from the P2MP LSP via a static assignment of the specific <S,G> to the tunnel interface associated with a terminating LSP.

At ingress LER, the tunnel interface identifier consists of a string of characters representing the LSP name for the RSVP P2MP LSP. The user can create one or more tunnel interfaces in PIM and associate each to a different RSVP P2MP LSP.

At egress LER, the tunnel interface identifier consists of a couple of string of characters representing the LSP name for the RSVP P2MP LSP followed by the system address of the ingress LER. The LSP name must correspond to a P2MP LSP name configured by the user at the ingress LER. The LSP name string must not contain "::” (two :s) nor contain a ":” (single ":”) at the end of the LSP name. However, a ":” (single ":”) can appear anywhere in the string except at the end of the name.

The no form of this command removes the tunnel parameters.

Parameters

lsp-name

Specifies the LSP, up to 32 characters.

ip-address

Specifies the sender IP address.

Platforms

All

Context

[Tree] (config>subscr-mgmt>wlan-gw>ue-query tunnel-local-address)

Full Context

configure subscriber-mgmt wlan-gw ue-query tunnel-local-address

Description

This command enables matching on UEs that are active on a tunnel which is connected to the specified IP address on the WLAN-GW.

The no form of this command disables matching on the local tunnel address.

Default

no tunnel-local-address

Parameters

ip-address

Specifies the IPv4 or IPv6 address of the local tunnel.

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

Context

[Tree] (config>isa tunnel-member-pool)

Full Context

configure isa tunnel-member-pool

Description

Commands in this context configure associated ESA VM and MDAs.

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

Parameters

name

Specifies the tunnel member pool name of the command, up to 32 characters.

create

Keyword used to create the command instance.

Platforms

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

Context

[Tree] (config>router>nat>inside>dslite>address tunnel-mtu)

[Tree] (config>service>vprn>nat>inside>dslite>address tunnel-mtu)

Full Context

configure router nat inside dual-stack-lite address tunnel-mtu

configure service vprn nat inside dual-stack-lite address tunnel-mtu

Description

This command configures the DS-Lite tunnel MTU for this DS-Lite address.

The no form of this command reverts the default.

Default

tunnel-mtu 1500

Parameters

mtu-bytes

Specifies the DS-Lite tunnel MTU.

Values

512 to 9212

Platforms

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

Context

[Tree] (config>router>nat>inside>dslite>address tunnel-mtu)

Full Context

configure router nat inside dual-stack-lite address tunnel-mtu

Description

This command sets the size of the payload in IPv6 packet in downstream DS-Lite direction. The payload is, in essence, the tunneled IPv4 packet.

Platforms

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

Context

[Tree] (config>router>isis>segment-routing tunnel-mtu)

Full Context

configure router isis segment-routing tunnel-mtu

Description

This command configures the MTU of all SR tunnels within each IGP instance.

The MTU of a SR tunnel populated into TTM is determined like in the case of an IGP tunnel; for example, LDP LSP, based on the outgoing interface MTU minus the label stack size. Remote LFA can add, at most, one more label to the tunnel for a total of two labels. There is no default value for this command. If the user does not configure an SR tunnel MTU, the MTU is determined by IGP as explained below.

The MTU of the SR tunnel in bytes is then determined as follows:

SR_Tunnel_MTU = MIN {Cfg_SR_MTU, IGP_Tunnel_MTU- (1+frr-overhead)*4}

Where:

Cfg_SR_MTU is the MTU configured by the user for all SR tunnels within a given IGP instance using the above CLI. If no value was configured by the user, the SR tunnel MTU will be determined by the IGP interface calculation explained next.

IGP_Tunnel_MTU is the minimum of the IS-IS or OSPF interface MTU among all the ECMP paths or among the primary and LFA backup paths of this SR tunnel.

frr-overhead is set to 1 if segment-routing and remote-lfa options are enabled in the IGMP instance. Otherwise, it is set to 0.

The SR tunnel MTU is dynamically updated anytime any of the above parameters used in its calculation changes. This includes when the set of the tunnel next-hops changes or the user changes the configured SR MTU or interface MTU value.

Default

no tunnel-mtu

Parameters

bytes

Specifies the size of the Maximum Transmission Unit (MTU) in bytes.

Values

512 to 9786

Platforms

All

Context

[Tree] (config>router>ospf3>segm-rtng tunnel-mtu)

[Tree] (config>router>ospf>segm-rtng tunnel-mtu)

Full Context

configure router ospf3 segment-routing tunnel-mtu

configure router ospf segment-routing tunnel-mtu

Description

This command configures the MTU of all SR tunnels within each IGP instance.

The MTU of a SR tunnel populated into the TTM is determined as the same as an IGP tunnel; for example, for an LDP LSP, based on the outgoing interface MTU minus the label stack size. Remote LFA can add, at most, one more label to the tunnel for a total of two labels. There is no default value for this command. If the user does not configure an SR tunnel MTU, the MTU will be determined by IGP as follows:

The MTU of the SR tunnel in bytes is then determined as follows:

SR_Tunnel_MTU = MIN {Cfg_SR_MTU, IGP_Tunnel_MTU- (1+frr—overhead)X4}

Where:

• Cfg_SR_MTU is the MTU configured by the user for all SR tunnels within an IGP instance using the tunnel-mtu command. If no value is configured by the user, the SR tunnel MTU is determined by the IGP interface calculation explained in the next bullet point.

• IGP_Tunnel_MTU is the minimum of the IS-IS or OSPF interface MTU among all the ECMP paths or among the primary and LFA backup paths of this SR tunnel.

• frr-overhead is set to 1 if the segment-routing and remote-lfa options are enabled in the IGMP instance. Otherwise, it is set to 0.

The SR tunnel MTU is dynamically updated whenever any of the above parameters used in its calculation changes. This includes if the set of the tunnel next-hops changes or the user changes the configured SR MTU or interface MTU value.

Default

no tunnel-mtu

Parameters

bytes

Specifies the size of the MTU in bytes.

Values

512 to 9786

Platforms

All

Context

[Tree] (cfg>port>eth>lldp>dstmac tunnel-nearest-bridge)

Full Context

configure port ethernet lldp dest-mac tunnel-nearest-bridge

Description

This command allows LLDP packets received on the port with the destination address of the nearest bridge to be tunneled without being intercepted on the local port. The dest-mac nearest-bridge must be disabled for tunneling to occur. This is applicable to NULL SAP Epipe and VPLS services only.

Default

no tunnel-nearest-bridge

Platforms

All

Context

[Tree] (config>lag>lldp-member-template>dstmac tunnel-nearest-bridge)

Full Context

configure lag lldp-member-template dest-mac tunnel-nearest-bridge

Description

This command allows LLDP packets received on the port with the destination address of the nearest bridge to be tunneled without being intercepted on the local port. The dest-mac nearest-bridge must be disabled for tunneling to occur. This is applicable to NULL SAP Epipe and VPLS services only.

The no form of this command disables the packets from being tunneled.

Default

no tunnel-nearest-bridge

Platforms

All

Context

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

Full Context

configure router static-route-entry indirect tunnel-next-hop

Description

Commands in this context configure the static route's nexthop to be resolved to an indirect tunnel next-hop.

Platforms

All

Context

[Tree] (config>router>isis>igp-shortcut tunnel-next-hop)

Full Context

configure router isis igp-shortcut tunnel-next-hop

Description

Commands in this context configure the resolution of IGP IPv4 prefix families, IGP IPv6 prefix families, SR-ISIS IPv4 tunnel families, SR-ISIS IPv6 tunnel families, and SR-OSPF IPv4 tunnel families using IGP shortcuts.

The resolution node is introduced to provide flexibility in the selection of the tunnel types for each of the IP prefix and SR tunnel families.

The IPv4 family option causes the IS-IS or OSPF SPF to include the IPv4 IGP shortcuts in the IP reach calculation of IPv4 nodes and prefixes. RSVP-TE or SR-TE LSPs terminating on a node identified by its router ID can be used to reach IPv4 prefixes owned by this node or for which this node is the IPv4 next hop.

The IPv6 family option causes the IS-IS or OSPFv3 SPF to include the IPv4 IGP shortcuts in the IP reach calculation of IPv6 nodes and prefixes. RSVP-TE or SR-TE LSPs terminating on a node identified by its router ID can be used to reach IPv6 prefixes owned by this node or for which this node is the IPv6 next-hop. The resolution of IPv6 prefixes is supported in OSPFv3 and in both IS-IS MT=0 and MT=2.

The IS-IS and OSPFv3 IPv6 routes resolved to IPv4 IGP shortcuts are used to:

• forward packets of IS-IS or OSPFv3 prefixes matching these routes

• forward CPM-originated IPv6 packets

• resolve the BGP next hop of BGP IPv6 prefixes

• resolve the indirect next hop of static IPv6 routes

In the data path, a packet for an IPv6 prefix has a label stack that consists of the IPv6 Explicit-Null label value of 2 at the bottom of the label stack followed by the label stack of the IPv4 RSVP-TE LSP.

There is no default behavior for IPv4 prefixes to automatically resolve to RSVP-TE or SR-TE LSPs used as IGP shortcuts by only enabling the igp-shortcut context. Instead, the user must enable the ipv4 family or ipv6 family and set the resolution to the value of rsvp-te to select the RSVP-TE tunnel type, or to the value of sr-te to select the SR-TE tunnel type.

Setting the resolution to the any value means that IGP selects the tunnels used as IGP shortcuts according to the TTM preference for the tunnel type. The RSVP-TE LSP type is of higher priority than the SR-TE LSP type.

An IP prefix of family=ipv4 or family=ipv6 always resolves to a single type of tunnel rsvp-te or sr-te. Rsvp-te type is preferred if both types are allowed by the prefix family resolution and both types exist in the set of tunnel next-hops of the prefix. The feature does not support mixing tunnel types per prefix.

If resolution for the IPv4 or IPv6 family is set to disabled, the corresponding prefixes are resolved to IP next-hops in the multicast routing table.

The srv4 family enables the resolution of SR-OSPF IPv4 tunnels and SR-ISIS IPv4 tunnels in MT=0 over RSVP-TE IPv4 IGP shortcuts. A maximum of 32 ECMP tunnel next-hops can be programmed for an SR-OSPF or an SR-ISIS IPv4 tunnel.

The srv6 family enables the resolution of SR-ISIS IPv6 tunnels in MT=0 over RSVP-TE IPv4 IGP shortcuts. A maximum of 32 ECMP tunnel next-hops can be programmed for an SR-ISIS IPv6 tunnel.

One or more RSVP-TE LSPs can be selected if resolution=match-family-ip and the corresponding IPv4 or IPv6 prefix resolves to RSVP-TE LSPs.

If resolution for the SRv4 or SRv6 tunnel family is set to disabled, the corresponding tunnels are resolved to IP next-hops in the multicast routing table.

To enable (disable) IGP shortcuts in the IGP instance, the user must perform a shutdown or no shutdown in the igp-shortcut context.

Platforms

All

Context

[Tree] (config>router>ospf3>igp-shortcut tunnel-next-hop)

[Tree] (config>router>ospf>igp-shortcut tunnel-next-hop)

Full Context

configure router ospf3 igp-shortcut tunnel-next-hop

configure router ospf igp-shortcut tunnel-next-hop

Description

Commands in this context configure the resolution of IGP IPv4 prefix families, IGP IPv6 prefix families, SR-ISIS IPv4 tunnel families, SR-ISIS IPv6 tunnel families, and SR-OSPF IPv4 tunnel families using IGP shortcuts.

The resolution node is introduced to provide flexibility in the selection of the tunnel types for each of the IP prefix and SR tunnel families.

The IPv4 family option causes the IS-IS or OSPF SPF to include the IPv4 IGP shortcuts in the IP reach calculation of IPv4 nodes and prefixes. RSVP-TE or SR-TE LSPs terminating on a node identified by its router ID can be used to reach IPv4 prefixes owned by this node or for which this node is the IPv4 next hop.

The IPv6 family option causes the IS-IS or OSPFv3 SPF to include the IPv4 IGP shortcuts in the IP reach calculation of IPv6 nodes and prefixes. RSVP-TE or SR-TE LSPs terminating on a node identified by its router ID can be used to reach IPv6 prefixes owned by this node or for which this node is the IPv6 next hop. The resolution of IPv6 prefixes is supported in OSPFv3 and in both IS-IS MT=0 and MT=2.

The IS-IS and OSPFv3 IPv6 routes resolved to IPv4 IGP shortcuts are used to:

• forward packets of IS-IS or OSPFv3 prefixes matching these routes

• forward CPM-originated IPv6 packets

• resolve the BGP next hop of BGP IPv6 prefixes

• resolve the indirect next hop of static IPv6 routes

In the data path, a packet for an IPv6 prefix has a label stack that consists of the IPv6 Explicit-Null label value of 2 at the bottom of the label stack followed by the label stack of the IPv4 RSVP-TE LSP.

There is no default behavior for IPv4 prefixes to automatically resolve to RSVP-TE or SR-TE LSPs used as IGP shortcuts by only enabling the igp-shortcut context. Instead, the user must enable the ipv4 family or ipv6 family and set the resolution to the value of rsvp-te to select the RSVP-TE tunnel type, or to the value of sr-te to select the SR-TE tunnel type.

Setting the resolution to the any value means that IGP selects the tunnels used as IGP shortcuts according to the TTM preference for the tunnel type. The RSVP-TE LSP type is of higher priority than the SR-TE LSP type.

An IP prefix of family=ipv4 or family=ipv6 always resolves to a single type of tunnel rsvp-te or sr-te. Rsvp-te type is preferred if both types are allowed by the prefix family resolution and both types exist in the set of tunnel next-hops of the prefix. The feature does not support mixing tunnel types per prefix.

If resolution for the IPv4 or IPv6 family is set to disabled, the corresponding prefixes are resolved to IP next-hops in the multicast routing table.

The srv4 family enables the resolution of SR-OSPF IPv4 tunnels and SR-ISIS IPv4 tunnels in MT=0 over RSVP-TE IPv4 IGP shortcuts. A maximum of 32 ECMP tunnel next-hops can be programmed for an SR-OSPF or an SR-ISIS IPv4 tunnel.

The srv6 family enables the resolution of SR-ISIS IPv6 tunnels in MT=0 over RSVP-TE IPv4 IGP shortcuts. A maximum of 32 ECMP tunnel next-hops can be programmed for an SR-ISIS IPv6 tunnel.

One or more RSVP-TE LSPs can be selected if resolution=match-family-ip and the corresponding IPv4 or IPv6 prefix resolves to RSVP-TE LSPs.

If resolution for the SRv4 or SRv6 tunnel family is set to disabled, the corresponding tunnels are resolved to IP next-hops in the multicast routing table.

To enable or disable IGP shortcuts in the IGP instance, the user must perform a shutdown or no shutdown in the igp-shortcut context.

Platforms

All

Context

[Tree] (config>isa>wlan-gw-group tunnel-port-policy)

Full Context

configure isa wlan-gw-group tunnel-port-policy

Description

This command configures the tunnel port policy of this WLAN Gateway ISA group. If a tunnel port policy is associated with a WLAN Gateway ISA group, ports created for this group can take applicable configuration from that policy. This policy is applicable to those ports that take part in the per-tunnel QoS processing.

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

Default

no-tunnel-policy

Parameters

tunnel-port-policy

Specifies the tunnel port policy of this WLAN Gateway ISA group, up to 32 characters.

Platforms

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

Context

[Tree] (config>port>ethernet>dot1x tunnel-qinq)

Full Context

configure port ethernet dot1x tunnel-qinq

Description

This command configures the tunneling of double tagged (QinQ) dot1x packets. When enabled, the router extracts the packets to the CPM.

The no form of this command disables the tunelling of the QinQ dot1x packets on the port.

Default

tunnel-qinq

Platforms

All

Context

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

Full Context

configure subscriber-mgmt wlan-gw tunnel-query

Description

This command creates a tunnel query where filter criteria over WLAN-GW tunnels are defined. This query can later be used to retrieve the state of the tunnels and Layer 2 access points (which are modeled as tunnels) matching the configured criteria.

The no form of this command removes the query.

Parameters

query-id

Specifies the ID assigned to a query.

Values

1 to 1024

name

Specifies the name assigned to a query, up to 32 characters.

create

Creates a tunnel query.

Platforms

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

Context

[Tree] (config>subscr-mgmt>wlan-gw>ue-query tunnel-remote-address)

Full Context

configure subscriber-mgmt wlan-gw ue-query tunnel-remote-address

Description

This command enables matching on UEs that are active on a tunnel with the specified source IP address.

The no form of this command disables matching on the remote tunnel address.

Default

no tunnel-remote-address

Parameters

ip-address

Specifies the IPv4 or IPv6 address of the remote tunnel.

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

Context

[Tree] (config>app-assure>group>statistics>tca>gtp-filter tunnel-resource-limit)

Full Context

configure application-assurance group statistics threshold-crossing-alert gtp-filter tunnel-resource-limit

Description

This command configures a TCA for the counter capturing the usage of the total number of GTP tunnel resources. A tunnel-resource-limit TCA can be created for traffic generated from the subscriber side of AA (from-sub) or from the network side (to-sub). The create keyword is mandatory when creating a TCA.

Parameters

direction

Specifies the traffic direction.

Values

from-sub, to-sub

create

Keyword used to create the TCA.

Platforms

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

Context

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

Full Context

configure subscriber-mgmt wlan-gw ue-query tunnel-router

Description

This command enables matching on UEs that are active on a tunnel which is terminated in the specified router instance.

The no form of this command disables matching on the tunnel router instance.

Default

no tunnel-router

Parameters

router-instance

Specifies the routing instance.

Values

router-name - Base

vprn-svc-id - 1 to 2147483647

Platforms

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

Context

[Tree] (config>router>l2tp tunnel-selection-blacklist)

[Tree] (config>service>vprn>l2tp tunnel-selection-blacklist)

Full Context

configure router l2tp tunnel-selection-blacklist

configure service vprn l2tp tunnel-selection-blacklist

Description

Commands in this context configure L2TP tunnel selection denylist parameters.

Platforms

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

Context

[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute tunnel-server-attrs)

[Tree] (config>subscr-mgmt>auth-policy>include-radius-attribute tunnel-server-attrs)

Full Context

configure subscriber-mgmt radius-accounting-policy include-radius-attribute tunnel-server-attrs

configure subscriber-mgmt authentication-policy include-radius-attribute tunnel-server-attrs

Description

This command enables the generation of the tunnel-server RADIUS attribute.

The no form of this command disables the generation of the tunnel-server-attrs RADIUS attribute.

Platforms

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

Context

[Tree] (config>service>vprn>l2tp tunnel-session-limit)

[Tree] (config>router>l2tp tunnel-session-limit)

Full Context

configure service vprn l2tp tunnel-session-limit

configure router l2tp tunnel-session-limit

Description

This command configures the L2TP session limit for each tunnel of the specified router.

The no form of this command removes the tunnel session limit value from the configuration.

Default

no tunnel-session-limit

Parameters

session-limit

Specifies the allowed number of sessions within the given context.

Values

1 to 65535

unlimited

Specifies to use the maximum number of sessions available.

Platforms

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

Context

[Tree] (config>router>wlan-gw>xconnect tunnel-source-ip)

[Tree] (config>service>vprn>wlan-gw>xconnect tunnel-source-ip)

Full Context

configure router wlan-gw xconnect tunnel-source-ip

configure service vprn wlan-gw xconnect tunnel-source-ip

Description

This command configures the IPv6 address and prefix for the tunnel source.

The no form of this command removes IPv6 address and prefix length from the cross-connect configuration.

Parameters

ipv6-address/prefix-length

Specifies the tunnel source IPv6 address and prefix length of the cross-connect.

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..FFFF]H

d [0..255]D

(no multicast address)

prefix-length [1 to 128]

Platforms

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

Context

[Tree] (debug>router>ip tunnel-table)

Full Context

debug router ip tunnel-table

Description

This command enables debugging for tunnel tables.

Platforms

All

Context

[Tree] (config>router>ldp tunnel-table-pref)

Full Context

configure router ldp tunnel-table-pref

Description

This command configures the tunnel table preference for LDP 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 value.

Default

tunnel-table-pref 9

Parameters

preference

Specifies the preference value.

Values

1 to 255

Default

9

Platforms

All

Context

[Tree] (config>router>mpls tunnel-table-pref)

Full Context

configure router mpls tunnel-table-pref

Description

Commands in this context configure the tunnel table preference for RSVP-TE LSP and SR-TE LSP tunnel types.

Platforms

All

Context

[Tree] (config>router>mpls>fwd-policies>fwd-policy tunnel-table-pref)

Full Context

configure router mpls forwarding-policies forwarding-policy tunnel-table-pref

Description

This command configures the TTM preference value of an MPLS forwarding policy.

The preference-value parameter is used by applications to select one tunnel type to bind to in TTM when multiple tunnel types are enabled for the application.

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 removes the configured TTM preference parameter value of the MPLS forwarding policy and assigns the default value.

Default

no tunnel-table-pref

Parameters

preference-value

Specifies the preference value.

Values

1 to 255

Default

4

Platforms

All

Context

[Tree] (config>router>isis>segment-routing tunnel-table-pref)

Full Context

configure router isis segment-routing tunnel-table-pref

Description

This command configures the TTM preference of SR tunnels created by the IGP instance. This is used in the case of BGP shortcuts, VPRN auto-bind, or BGP transport tunnel when the new tunnel binding commands are configured to the any value which parses the TTM for tunnels in the protocol preference order. The user can choose to either go with the global TTM preference or list explicitly the tunnel types they want to use. When they list the tunnel types explicitly, the TTM preference will still be used to select one type over the other. In both cases, a fallback to the next preferred tunnel type is performed if the selected one fails. Also, a reversion to a more preferred tunnel type is performed as soon as one is available.

The segment routing module adds to TTM a SR tunnel entry for each resolved remote node SID prefix and programs the data path with the corresponding LTN with the push operation pointing to the primary and LFA backup NHLFEs.

The default preference for SR tunnels in the TTM is set lower than LDP tunnels but higher than BGP tunnels to allow controlled migration of customers without disrupting their current deployment when they enable segment routing. The following is the setting of the default preference of the various tunnel types. This includes the preference of SR tunnels based on shortest path (referred to as SR-ISIS and SR-OSPF).

The global default TTM preference for the tunnel types is as follows:

• ROUTE_PREF_RSVP 7

• ROUTE_PREF_SR_TE 8

• ROUTE_PREF_LDP 9

• ROUTE_PREF_OSPF_TTM 10

• ROUTE_PREF_ISIS_TTM 11

• ROUTE_PREF_BGP_TTM 12

• ROUTE_PREF_GRE 255

The default value for SR-ISIS or SR-OSPF is the same regardless if one or more IS-IS or OSPF instances programmed a tunnel for the same prefix. The selection of a SR tunnel in this case will be based on lowest IGP instance-id.

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.

Default

tunnel-table-pref 11

Parameters

preference

Specifies the integer value to represent the preference of IS-IS or OSPF SR tunnels in TTM.

Values

1 to 255

Platforms

All

Context

[Tree] (config>router>ospf>segm-rtng tunnel-table-pref)

[Tree] (config>router>ospf3>segm-rtng tunnel-table-pref)

Full Context

configure router ospf segment-routing tunnel-table-pref

configure router ospf3 segment-routing tunnel-table-pref

Description

This command configures the TTM preference of shortest path SR tunnels created by the IGP instance. This is used for BGP shortcuts, VPRN auto-bind, or BGP transport tunnel when the tunnel binding commands are configured to the any value, which parses the TTM for tunnels in the protocol preference order. The user can choose to either accept the global TTM preference or explicitly list the tunnel types they want to use. If the user lists the tunnel types explicitly, the TTM preference is still used to select one type over the other. In both cases, a fallback to the next preferred tunnel type is performed if the selected type fails. A reversion to a more preferred tunnel type is performed as soon as one is available.

The segment routing module adds to the TTM an SR tunnel entry for each resolved remote node SID prefix and programs the data path having the corresponding LTN with the push operation pointing to the primary and LFA backup NHLFEs.

The default preference for shortest path SR tunnels in the TTM is set lower than LDP tunnels but higher than BGP tunnels to allow controlled migration of customers without disrupting their current deployment when they enable segment routing. The following is the value of the default preference for the various tunnel types. This includes the preference of SR tunnels based on shortest path (referred to as SR-ISIS and SR-OSPF).

The global default TTM preference for the tunnel types is as follows:

• ROUTE_PREF_RSVP 7

• ROUTE_PREF_SR_TE 8

• ROUTE_PREF_LDP 9

• ROUTE_PREF_OSPF_TTM 10

• ROUTE_PREF_ISIS_TTM 11

• ROUTE_PREF_BGP_TTM 12

• ROUTE_PREF_GRE 255

The default value for SR-ISIS or SR-OSPF is the same regardless if one or more IS-IS or OSPF instances programmed a tunnel for the same prefix. The selection of a SR tunnel in this case will be based on the lowest IGP instance ID. Similarly, IPv6 SR-ISIS and SR-OSPF3 tunnels are programmed into TTMv6 with the same default preference value as IPv4 SR-ISIS and IPv4 SR-OSPF respectively.

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.

Default

tunnel-table-pref 10

Parameters

preference

Specifies the integer value to represent the preference of IS-IS, OSPF, or OSPF3 SR tunnels in the TTM.

Values

1 to 255

Platforms

All

Context

[Tree] (config>ipsec>client-db>client tunnel-template)

Full Context

configure ipsec client-db client tunnel-template

Description

This command specifies the tunnel template to be used for tunnel setup.

The no form of this command reverts to the default.

Default

no tunnel-template

Parameters

tunnel-template-id

Specifies the identifier of the tunnel template.

Values

1 to 2048

Platforms

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

Context

[Tree] (config>ipsec tunnel-template)

Full Context

configure ipsec tunnel-template

Description

This command creates a tunnel template. Up to 2000 templates are allowed.

Parameters

ipsec-template-identifier

Specifies the template identifier.

Values

1 to 2048

create

Mandatory keyword used when creating a tunnel-template in the IPsec context. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

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

Context

[Tree] (config>service>vprn>vxlan tunnel-termination)

Full Context

configure service vprn vxlan tunnel-termination

Description

This command instructs the system to redirect traffic to the corresponding PXC interface associated with the configured FPE when the destination IP address matches the configured tunnel termination IP address. Because the IP address is registered, the system can respond to ICMP packets directed to it.

The no form of this command removes the non-system IP address as the tunnel termination IP address.

Parameters

ip-address | ipv6-address

Specifies the non-system IPv4 or IPv6 address that terminates the VXLAN.

Values

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

where:

x: [0 to FFFF]H

d: [0 to 255]D

fpe-id

Specifies the FPE identifier associated with the PXC port or LAG that processes and terminates the VXLAN.

Values

1 to 64

create

Mandatory keyword to create the FPE.

Platforms

All

Context

[Tree] (config>service>system>vxlan tunnel-termination)

Full Context

configure service system vxlan tunnel-termination

Description

This command instructs the system to redirect traffic to the corresponding PXC interface associated with the configured Forwarding Path Extension (FPE) when the destination IP address matches the configured tunnel-termination IP address. The IP address is also registered, which enables the system to respond to ICMP packets directed to it.

Parameters

ip-address

Specifies the non-system IPv4 or IPv6 address that terminates the VXLAN.

fpe-id

Specifies the FPE identifier associated with the PXC port or LAG that processes and terminates the VXLAN.

Values

1 to 64

create

Creates the FPE.

Platforms

All

Context

[Tree] (config>service>system>gre-eth-bridged tunnel-termination)

Full Context

configure service system gre-eth-bridged tunnel-termination

Description

This command configures an end-point IP address for a GRE tunnel carrying Ethernet payload that is to be terminated on a PW SAP. It also associates this IP address with the FPE object that is providing cross-connect logic between the tunnel and the PW port. This IP address fully supports ICMP protocols such as PING, traceroute, and others.

Parameters

ip-address

The tunnel end-point IP address in the SR OS node.

ipv6-address

The tunnel end-point IPv6 address in the SR OS node.

fpe id

The FPE ID that is providing cross-connect service between the GRE tunnel and the PW port.

Values

1 to 64

Platforms

All

Context

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

Full Context

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

Description

This command enables matching on UEs that are active on a tunnel of the specified type. The not-specified value disables matching on the tunnel type.

The no form of this command reverts to the default.

Default

tunnel-type not-specified

Parameters

gre

Specifies that the tunnel is of type GRE.

l2tp

Specifies that the tunnel is of type L2TPv3.

l2

Specifies that the UE is connected over a Layer 2 access point.

vxlan

Specifies that the tunnel is of type VXLAN.

not-specified

Specifies that no tunnel type matches on UEs.

Platforms

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

Context

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

Full Context

configure port ethernet efm-oam tunneling

Description

This command enables EFM OAM PDU tunneling. Enabling tunneling will allow a port mode Epipe SAP to pass OAM frames through the pipe to the far end.

The no form of this command disables tunneling.

Default

no tunneling

Platforms

All

Context

[Tree] (config>port>ethernet>dot1x tunneling)

Full Context

configure port ethernet dot1x tunneling

Description

This command enables the tunneling of untagged 802.1x frames received on a port and is supported only when dot1x port-control is set to force-auth. 802.1x tunneling is applicable to both Epipe and VPLS services using either a null SAP or a default SAP on a dot1q port. When configured, untagged 802.1x frames will be switched into the service with the corresponding supported SAP.

The no form of this command disables tunneling of untagged 802.1x frames.

Default

no tunneling

Platforms

All

Context

[Tree] (config>router>ldp>targ-session>peer-template tunneling)

[Tree] (config>router>ldp>targ-session>peer tunneling)

Full Context

configure router ldp targeted-session peer-template tunneling

configure router ldp targeted-session peer tunneling

Description

This command enables LDP over tunnels.

The no form of this command disables tunneling.

Default

no tunneling

Platforms

All

Context

[Tree] (config>router>ldp>targ-session>auto-rx>ipv4 tunneling)

[Tree] (config>router>ldp>targ-session>auto-tx>ipv4 tunneling)

Full Context

configure router ldp targeted-session auto-rx ipv4 tunneling

configure router ldp targeted-session auto-tx ipv4 tunneling

Description

This command enables the local system to use the targeted LDP session to send FEC/label bindings that it has advertised to other LDP peers. For LDP rLFA, the source node requires the PQ node's label binding information in order to reach the destination. Therefore, this command must be enabled for the auto-rx context. However, because auto-rx has lower precedence, tunneling must be enabled under the auto-tx command, in case auto-rx is in a no shutdown state on the same system.

The no form of this command disables the local system from sending FEC/label bindings.

Default

no tunneling

Platforms

All

Context

[Tree] (config>test-oam twamp)

Full Context

configure test-oam twamp

Description

This command enables TWAMP functionality.

Platforms

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

Context

[Tree] (config>oam-pm>session>ip twamp-light)

Full Context

configure oam-pm session ip twamp-light

Description

This command assigns an identifier to the TWAMP Light test and creates the individual test.

The no form of this command removes the TWAMP Light test function from the OAM-PM session.

Parameters

test-id

Specifies the value of the 4-byte local test identifier not sent in the TWAMP Light packets.

Values

0 to 2147483647 | auto

auto - automatically assigns a test-id

create

Creates the test.

Platforms

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

Context

[Tree] (config>test-oam>twamp twamp-light)

[Tree] (config>router twamp-light)

[Tree] (config>service>vprn twamp-light)

Full Context

configure test-oam twamp twamp-light

configure router twamp-light

configure service vprn twamp-light

Description

Commands in this context configure TWAMP Light parameters.

Platforms

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

Context

[Tree] (config>test-oam>link-meas>template twamp-light)

Full Context

configure test-oam link-measurement measurement-template twamp-light

Description

Commands in this context configure TWAMP Light test values.

Platforms

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

Context

[Tree] (config>router>if>if-attr>delay>dyn twamp-light)

Full Context

configure router interface if-attribute delay dynamic twamp-light

Description

Commands in this context configure TWAMP Light parameters that are used with the measurement-template when assigned to IP interfaces.

Platforms

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

Context

[Tree] (config>router>if>if-attr>delay>dyn twamp-light)

Full Context

configure router interface if-attribute delay dynamic twamp-light

Description

Commands in this context configure TWAMP Light parameters that are used with the measurement-template when assigned to IP interfaces.

Platforms

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

Context

[Tree] (config>test-oam>lag-meas>template twamp-light)

Full Context

configure test-oam lag-ip-measurement lag-ip-measurement-template twamp-light

Description

Commands in this context configure the TWAMP Light packet values.

Platforms

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

Context

[Tree] (oam>eth-cfm two-way-delay-test)

Full Context

oam eth-cfm two-way-delay-test

Description

This command issues an ETH-CFM two-way delay test.

Parameters

mac-address

Specifies a unicast destination MAC address.

Values

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

remote-mepid mep-id

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

Values

1 to 8191

mep mep-id

Specifies the local MEP ID.

Values

1 to 8191

md-index

Specifies the MD index.

Values

1 to 4294967295

ma-index

Specifies the MA index.

Values

1 to 4294967295

priority

Specifies the priority.

Values

0 to 7

Default

7

Platforms

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

Context

[Tree] (oam>eth-cfm two-way-slm-test)

Full Context

oam eth-cfm two-way-slm-test

Description

This command configures an Ethernet CFM two-way SLM test in SAA.

Parameters

mac-address

Specifies a unicast destination MAC address in the format xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx.

remote-mepid mep-id

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

Values

1 to 8191

mep mep-id

Specifies the local MEP ID.

Values

1 to 8191

md-index

Specifies the MD index.

Values

1 to 4294967295

ma-index

Specifies the MA index.

Values

1 to 4294967295

priority

Specifies the priority.

Values

0 to 7

Default

7

send-count

Specifies the number of messages to send, expressed as a decimal integer. The count parameter is used to override the default number of message requests sent. The message interval value must be expired before the next message request is sent.

Values

1 to 1000

Default

1

data-size

Specifies the size of the data portion of the data TLV. If 0 is specified, no data TLV is added to the packet.

Values

0 to 1500

Default

0

timeout

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

Values

1 to 10

Default

5

interval

Specifies the interval parameter in seconds, expressed as a decimal integer. This parameter is used to configure the spacing between probes within a test run.

Values

0.1 to 0.9, 1 to 10

Default

5

Platforms

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

Context

[Tree] (config>subscr-mgmt>pfcp-association tx)

Full Context

configure subscriber-mgmt pfcp-association tx

Description

Commands in this context configure parameters that determine how PFCP messages are sent.

Default

tx

Platforms

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

Context

[Tree] (config>port>otu>pm-tti tx)

Full Context

configure port otu pm-tti tx

Description

This command enables the user to configure the transmit (tx) trail trace identifier (TTI) for path monitoring (PM) in the ODU overhead. This identifier can be a string or a non-printable sequence of bytes. The length of the string or sequence of bytes cannot exceed 64 bytes.

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

Default

Auto-generated in the format of nodename:iomnum/mdanum/portnum/dwdmchan

The auto-generated value has five sections:

• Nodename — The first section is the name of the node.

• iomnum — The second section contains the IOM slot number.

• mdanum — The third section contains the MDA slot number.

• portnum — The fourth section contains the port number.

• dwdmchan — The fifth section contains the DWDM channel number (see the table "DWDM Channel Numbers” in the channel command [config>port>dwdm channel and config>port>dwdm>coherent channel]).

Parameters

auto-generated

Specifies to use the system generated (default) TTI.

identifier

Sets the PM TTI to the string provided by the user. If the string is less than 64 bytes, the remaining bytes will be set to 0.

byte-string

Sets the PM TTI to the sequence of bytes provided by the user. If the user provides less than 64 bytes, the remaining bytes will be set to 0. A 1 byte sequence of 0xFF will set the default strings. Up to 64 byte strings can be specified in a single statement.

Values

0 to FF, in hexadecimal byte notation

Platforms

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

Context

[Tree] (config>port>otu>psi-payload tx)

Full Context

configure port otu psi-payload tx

Description

This command allows the user to configure the transmit payload type value in byte 0 of the payload structure identifier (PSI) of the OPU overhead.

Default

3 for 10GE-LAN/WAN or OC192 with OTU encapsulation; 5 for GFP framed 10GE-LAN with OTU encapsulation.

Parameters

auto

Transmits the standard value in the payload type field.

byte

Specifies the transmit payload type value in bytes.

Values

[00 to FF] Hexadecimal notation

Default

00

Platforms

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

Context

[Tree] (config>port>otu>sm-tti tx)

Full Context

configure port otu sm-tti tx

Description

This command allows the user to configure the transmit (tx) trail trace identifier (TTI) for section monitoring (SM) in the OTU overhead. This identifier can be a string or a non-printable sequence of bytes. The length of the string or sequence of bytes cannot exceed 64 bytes.

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

Default

Auto-generated in the format of nodename:iomnum/mdanum/portnum/dwdmchan

The auto-generated value has five sections:

• Nodename — The first section is the name of the node.

• iomnum — The second section contains the IOM slot number.

• mdanum — The third section contains the MDA slot number.

• portnum — The fourth section contains the port number.

• dwdmchan — The fifth section contains the DWDM channel number (see the table "DWDM Channel Numbers” in the channel command [config>port>dwdm channel and config>port>dwdm>coherent channel]).

Parameters

auto-generated

Specifies to use the system generated (default) TTI.

identifier

Sets the SM TTI to the string provided by the user. If the string is less than 64 bytes, the remaining bytes will be set to 0. Up to 64 byte strings can be specified in a single statement.

byte-string

Sets the SM TTI to the sequence of bytes provided by the user. If the user provides less than 64 bytes, the remaining bytes will be set to 0. A 1 byte sequence of 0xFF will set the default strings.

Values

0 to FF, in hexadecimal byte notation

Platforms

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

Context

[Tree] (config>system>lldp tx-credit-max)

Full Context

configure system lldp tx-credit-max

Description

This command configures the maximum consecutive LLDPDUs transmitted.

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

Default

no tx-credit-max

Parameters

count

Specifies the maximum consecutive LLDPDUs transmitted.

Values

1 to 100

Default

5

Platforms

All

Context

[Tree] (config>port>sonet-sdh tx-dus)

[Tree] (config>port>ethernet>ssm tx-dus)

Full Context

configure port sonet-sdh tx-dus

configure port ethernet ssm tx-dus

Description

This command forces the QL value transmitted from the SSM channel of the SONET/SDH port or the Synchronous Ethernet port to be set to QL-DUS/QL-DNU. This capability is provided to block the use of the interface from the SR/ESS for timing purposes.

This command is supported on TDM satellite.

Default

no tx-dus

Platforms

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

• configure port sonet-sdh tx-dus

All

• configure port ethernet ssm tx-dus

Context

[Tree] (config>port>ethernet>eth-cfm>mep>grace>eth-ed tx-eth-ed)

[Tree] (config>eth-tunnel>path>eth-cfm>mep>grace>eth-ed tx-eth-ed)

[Tree] (config>eth-ring>path>eth-cfm>mep>grace>eth-ed tx-eth-ed)

[Tree] (config>lag>eth-cfm>mep>grace>eth-ed tx-eth-ed)

Full Context

configure port ethernet eth-cfm mep grace eth-ed tx-eth-ed

configure eth-tunnel path eth-cfm mep grace eth-ed tx-eth-ed

configure eth-ring path eth-cfm mep grace eth-ed tx-eth-ed

configure lag eth-cfm mep grace eth-ed tx-eth-ed

Description

This command enables the transmission of the ITU-T Y.1731 ETH-ED PDU from the MEP when a system soft reset notification is received for one or more cards.

The config>eth-cfm>system>grace-tx-enable command must be configured to instruct the system that the node is capable of transmitting expected defect windows to the peers. Only one form of ETH-CFM grace (Nokia ETH-CFM Grace or ITU-T Y.1731 ETH-ED) may be transmitted.

The no form of this command disables the transmission of the ITU-T Y.1731 ETH-ED PDU from the MEP.

Default

no tx-eth-ed

Platforms

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

Context

[Tree] (config>service>ipipe>sap>eth-cfm>mep>grace>eth-ed tx-eth-ed)

[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep>grace>eth-ed tx-eth-ed)

[Tree] (config>service>epipe>sap>eth-cfm>mep>grace>eth-ed tx-eth-ed)

Full Context

configure service ipipe sap eth-cfm mep grace eth-ed tx-eth-ed

configure service epipe spoke-sdp eth-cfm mep grace eth-ed tx-eth-ed

configure service epipe sap eth-cfm mep grace eth-ed tx-eth-ed

Description

This command enables the transmission of the ITU-T Y.1731 ETH-ED PDU from the MEP when a system soft reset notification is received for one or more cards.

The config>eth-cfm>system>grace-tx-enable command must be configured to instruct the system that the node is capable of transmitting expected defect windows to the peers. Only one form of ETH-CFM grace (Nokia ETH-CFM Grace or ITU-T Y.1731 ETH-ED) may be transmitted.

The no form of this command disables the transmission of the ITU-T Y.1731 ETH-ED PDU from the MEP.

Default

no tx-eth-ed

Platforms

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

Context

[Tree] (config>service>vpls>sap>eth-cfm>mep>grace>eth-ed tx-eth-ed)

[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep>grace>eth-ed tx-eth-ed)

[Tree] (config>service>vpls>eth-cfm>mep>grace>eth-ed tx-eth-ed)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep>grace>eth-ed tx-eth-ed)

Full Context

configure service vpls sap eth-cfm mep grace eth-ed tx-eth-ed

configure service vpls spoke-sdp eth-cfm mep grace eth-ed tx-eth-ed

configure service vpls eth-cfm mep grace eth-ed tx-eth-ed

configure service vpls mesh-sdp eth-cfm mep grace eth-ed tx-eth-ed

Description

This command enables the transmission of the ITU-T Y.1731 ETH-ED PDU from the MEP when a system soft reset notification is received for one or more cards.

The config>eth-cfm>system>grace-tx-enable command must be configured to instruct the system that the node is capable of transmitting expected defect windows to the peers. Only one form of ETH-CFM grace (Nokia ETH-CFM Grace or ITU-T Y.1731 ETH-ED) may be transmitted.

The no form of this command disables the transmission of the ITU-T Y.1731 ETH-ED PDU from the MEP.

Default

no tx-eth-ed

Platforms

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

Context

[Tree] (config>service>ies>if>sap>eth-cfm>mep>grace>eth-ed tx-eth-ed)

[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>mep>grace>eth-ed tx-eth-ed)

[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>mep>grace>eth-ed tx-eth-ed)

Full Context

configure service ies interface sap eth-cfm mep grace eth-ed tx-eth-ed

configure service ies interface spoke-sdp eth-cfm mep grace eth-ed tx-eth-ed

configure service ies subscriber-interface group-interface sap eth-cfm mep grace eth-ed tx-eth-ed

Description

This command enables the transmission of the ITU-T Y.1731 ETH-ED PDU from the MEP when a system soft reset notification is received for one or more cards.

The config>eth-cfm>system>grace-tx-enable command must be configured to instruct the system that the node is capable of transmitting expected defect windows to the peers. Only one form of ETH-CFM grace (Nokia ETH-CFM Grace or ITU-T Y.1731 ETH-ED) may be transmitted.

The no form of this command disables the transmission of the ITU-T Y.1731 ETH-ED PDU from the MEP.

Default

no tx-eth-ed

Platforms

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 tx-eth-ed
• configure service ies interface sap eth-cfm mep grace eth-ed tx-eth-ed

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 tx-eth-ed

Context

[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm>mep>grace>eth-ed tx-eth-ed)

[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>mep>grace>eth-ed tx-eth-ed)

[Tree] (config>service>vprn>if>sap>eth-cfm>mep>grace>eth-ed tx-eth-ed)

Full Context

configure service vprn subscriber-interface group-interface sap eth-cfm mep grace eth-ed tx-eth-ed

configure service vprn interface spoke-sdp eth-cfm mep grace eth-ed tx-eth-ed

configure service vprn interface sap eth-cfm mep grace eth-ed tx-eth-ed

Description

This command enables the transmission of the ITU-T Y.1731 ETH-ED PDU from the MEP when a system soft reset notification is received for one or more cards.

The config>eth-cfm>system>grace-tx-enable command must be configured to instruct the system that the node is capable of transmitting expected defect windows to the peers. Only one form of ETH-CFM grace (Nokia ETH-CFM Grace or ITU-T Y.1731 ETH-ED) may be transmitted.

The no form of this command disables the transmission of the ITU-T Y.1731 ETH-ED PDU from the MEP.

Default

no tx-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 tx-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 tx-eth-ed
• configure service vprn interface spoke-sdp eth-cfm mep grace eth-ed tx-eth-ed

Context

[Tree] (config>router>if>eth-cfm>mep>grace>eth-ed tx-eth-ed)

Full Context

configure router interface eth-cfm mep grace eth-ed tx-eth-ed

Description

This command enables the transmission of the ITU-T Y.1731 ETH-ED PDU from the MEP when a system soft reset notification is received for one or more cards.

The config>eth-cfm>system>grace-tx-enable command must be configured to instruct the system that the node is capable of transmitting expected defect windows to the peers. Only one form of ETH-CFM grace (Nokia ETH-CFM Grace or ITU-T Y.1731 ETH-ED) may be transmitted.

The no form of this command disables the transmission of the ITU-T Y.1731 ETH-ED PDU from the MEP.

Default

no tx-eth-ed

Platforms

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

Context

[Tree] (config>port>ethernet>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

[Tree] (config>eth-ring>path>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

[Tree] (config>lag>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

[Tree] (config>eth-tunnel>path>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

Full Context

configure port ethernet eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

configure eth-ring path eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

configure lag eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

configure eth-tunnel path eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

Description

This command enables the transmission of the Nokia ETH-CFM Grace PDU from the MEP when a system soft reset notification is received for one or more cards.

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 config>eth-cfm>system>grace-tx-enable command must be configured to instruct the system that the node is capable of transmitting expected defect windows to the peers. Only one form of ETH-CFM grace (Nokia ETH-CFM Grace or ITU-T Y.1731 ETH-ED) may be transmitted.

The no form of this command disables the transmission of the Nokia ETH-CFM Grace PDU from the MEP.

Default

tx-eth-vsm-grace

Platforms

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

Context

[Tree] (config>service>epipe>sap>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

[Tree] (config>service>ipipe>sap>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

Full Context

configure service epipe sap eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

configure service epipe spoke-sdp eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

configure service ipipe sap eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

Description

This command enables the transmission of the Nokia ETH-CFM Grace PDU from the MEP when a system soft reset notification is received for one or more cards.

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 config>eth-cfm>system>grace-tx-enable command must be configured to instruct the system that the node is capable of transmitting expected defect windows to the peers. Only one form of ETH-CFM grace (Nokia ETH-CFM Grace or ITU-T Y.1731 ETH-ED) may be transmitted.

The no form of this command disables the transmission of the Nokia ETH-CFM Grace PDU from the MEP.

Default

tx-eth-vsm-grace

Platforms

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

Context

[Tree] (config>service>vpls>sap>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

[Tree] (config>service>vpls>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

Full Context

configure service vpls sap eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

configure service vpls mesh-sdp eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

configure service vpls spoke-sdp eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

configure service vpls eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

Description

This command enables the transmission of the Nokia ETH-CFM Grace PDU from the MEP when a system soft reset notification is received for one or more cards.

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 config>eth-cfm>system>grace-tx-enable command must be configured to instruct the system that the node is capable of transmitting expected defect windows to the peers. Only one form of ETH-CFM grace (Nokia ETH-CFM Grace or ITU-T Y.1731 ETH-ED) may be transmitted.

The no form of this command disables the transmission of the Nokia ETH-CFM Grace PDU from the MEP.

Default

tx-eth-vsm-grace

Platforms

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

Context

[Tree] (config>service>ies>if>sap>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

Full Context

configure service ies interface sap eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

configure service ies interface spoke-sdp eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

configure service ies subscriber-interface group-interface sap eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

Description

This command enables the transmission of the Nokia ETH-CFM Grace PDU from the MEP when a system soft reset notification is received for one or more cards.

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 config>eth-cfm>system>grace-tx-enable command must be configured to instruct the system that the node is capable of transmitting expected defect windows to the peers. Only one form of ETH-CFM grace (Nokia ETH-CFM Grace or ITU-T Y.1731 ETH-ED) may be transmitted.

The no form of this command disables the transmission of the Nokia ETH-CFM Grace PDU from the MEP.

Default

tx-eth-vsm-grace

Platforms

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 tx-eth-vsm-grace
• configure service ies interface sap eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

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 tx-eth-vsm-grace

Context

[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

[Tree] (config>service>vprn>if>sap>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

Full Context

configure service vprn subscriber-interface group-interface sap eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

configure service vprn interface sap eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

configure service vprn interface spoke-sdp eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

Description

This command enables the transmission of the Nokia ETH-CFM Grace PDU from the MEP when a system soft reset notification is received for one or more cards.

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 config>eth-cfm>system>grace-tx-enable command must be configured to instruct the system that the node is capable of transmitting expected defect windows to the peers. Only one form of ETH-CFM grace (Nokia ETH-CFM Grace or ITU-T Y.1731 ETH-ED) may be transmitted.

The no form of this command disables the transmission of the Nokia ETH-CFM Grace PDU from the MEP.

Default

tx-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 tx-eth-vsm-grace

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

• configure service vprn interface spoke-sdp eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace
• configure service vprn interface sap eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

Context

[Tree] (config>router>if>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

Full Context

configure router interface eth-cfm mep grace eth-vsm-grace tx-eth-vsm-grace

Description

This command enables the transmission of the Nokia ETH-CFM Grace PDU from the MEP when a system soft reset notification is received for one or more cards.

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 config>eth-cfm>system>grace-tx-enable command must be configured to instruct the system that the node is capable of transmitting expected defect windows to the peers. Only one form of ETH-CFM grace (Nokia ETH-CFM Grace or ITU-T Y.1731 ETH-ED) may be transmitted.

The no form of this command disables the transmission of the Nokia ETH-CFM Grace PDU from the MEP.

Default

tx-eth-vsm-grace

Platforms

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

Context

[Tree] (config>system>lldp tx-hold-multiplier)

Full Context

configure system lldp tx-hold-multiplier

Description

This command configures the multiplier of the tx-interval.

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

Default

no tx-hold-multiplier

Parameters

multiplier

Specifies the multiplier of the tx-interval.

Values

2 to 10

Default

4

Platforms

All

Context

[Tree] (config>system>lldp tx-interval)

Full Context

configure system lldp tx-interval

Description

This command configures the LLDP transmit interval time.

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

Default

no tx-interval

Parameters

interval

Specifies the LLDP transmit interval time.

Values

5 to 32768

Default

30

Platforms

All

Context

[Tree] (config>port>ethernet>lldp>dstmac tx-mgmt-address)

Full Context

configure port ethernet lldp dest-mac tx-mgmt-address

Description

This command specifies which management address to transmit. The operator can choose to send the system IPv4 address, the system IPv6 address, the out-of-band IPv4 address, the out-of-band IPv6 address, or any combination of these. The system address is sent only once. The address must be configured for the specific version of the protocol in order to send the management address.

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

Default

no tx-mgmt-address

Parameters

system

Specifies to use the system IP address. The system address will only be transmitted once it has been configured if this parameter is specified.

system-ipv6

Specifies to use the system IPv6 address. The system address will only be transmitted once it has been configured if this parameter is specified.

oob

Specifies to use the out-of-band IPv4 address for active CPM.

oob-ipv6

Specifies to use the out-of-band IPv6 address for active CPM.

Platforms

All

Context

[Tree] (config>lag>lldp-member-template>dstmac tx-mgmt-address)

Full Context

configure lag lldp-member-template dest-mac tx-mgmt-address

Description

This command configures the management address to transmit. The operator can choose to send the system IPv4 address, system IPv6 address, out-of-band IPv4 address, out-of-band IPv6 address, or any combination of these. The system address is sent only once. The address must be configured for the specific version of the protocol to send the management address.

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

Default

no tx-mgmt-address

Parameters

system

Keyword to use the system IP address. The system address is only transmitted after it has been configured if this keyword is specified.

system-ipv6

Keyword to use the system IPv6 address. The system address must be configured before it can be transmitted using this keyword.

oob

Keyword to use the out-of-band IPv4 address for active CPM.

oob-ipv6

Keyword to use the out-of-band IPv6 address for active CPM.

Platforms

All

Context

[Tree] (config>port>ethernet tx-pause-frames)

Full Context

configure port ethernet tx-pause-frames

Description

This command enables the transmission of PAUSE frames, when required, based on the rate of the received traffic.

This command is only supported for FP4- or FP5-based ports on the 7750 SR and 7950 XRS.

This command is not supported for ports configured as satellite host, ESA host, or PXC.

The no form of this command disables the transmission of the PAUSE frames.

Default

tx-pause-frames

Platforms

All

Context

[Tree] (config>subscr-mgmt>diameter-application-policy tx-timer)

Full Context

configure subscriber-mgmt diameter-application-policy tx-timer

Description

This command defines the time-out period for the application’s request messages (CCR-I/U/T).

The on-failure configuration determines the action that taken once the message times out.

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

Default

tx-timer 10

Parameters

seconds

Specifies the Tx Timer value (in seconds) for this policy.

Values

10 to 1000

Platforms

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

Context

[Tree] (config>port>ethernet>lldp>dstmac tx-tlvs)

Full Context

configure port ethernet lldp dest-mac tx-tlvs

Description

This command specifies which LLDP TLVs to transmit. The TX TLVs, defined as a bitmap, includes the basic set of LLDP TLVs whose transmission is allowed on the local LLDP agent by the network management. Each bit in the bitmap corresponds to a TLV type associated with a specific optional TLV. Organizationally-specific TLVs are excluded from this bitmap.

There is no bit reserved for the management address TLV type since transmission of management address TLVs are controlled by another object.

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

Default

no tx-tlvs

Parameters

port-desc

Indicates that the LLDP agent should transmit port description TLVs.

sys-name

Indicates that the LLDP agent should transmit system name TLVs.

sys-desc

Indicates that the LLDP agent should transmit system description TLVs.

sys-cap

Indicates that the LLDP agent should transmit system capabilities TLVs.

Platforms

All

Context

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

Full Context

configure lag lldp-member-template dest-mac tx-tlvs

Description

This command configures which LLDP TLVs to transmit. The TX TLVs, defined as a bitmap, include the basic set of LLDP TLVs whose transmission is allowed on the local LLDP agent by the network management. Each bit in the bitmap corresponds to a TLV type associated with a specific optional TLV. Organizationally specific TLVs are excluded from this bitmap.

No bit is reserved for the management address TLV type because transmission of these TLVs is controlled by another object.

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

Default

no tx-tlvs

Parameters

port-desc

Keyword to specify that the LLDP agent transmits port description TLVs.

sys-name

Keyword to specify that the LLDP agent transmits system name TLVs.

sys-desc

Keyword to specify that the LLDP agent transmits system description TLVs.

sys-cap

Keyword to specify that the LLDP agent transmits system capabilities TLVs.

Platforms

All

Context

[Tree] (config>system>ptp tx-while-sync-uncertain)

Full Context

configure system ptp tx-while-sync-uncertain

Description

This command configures the local PTP clock to transmit Announce messages to downstream clocks, indicating it has not yet stabilized on the recovered synchronization source (upstream clocks or GM clock). While the PTP clock is unsynchronized, the SyncUncertain state is true.

The no form of this command prevents the local PTP clock from sending Announce messages to downstream clocks to indicate it is not synchronized to a valid timing source. If the no form of this command is used while the clock’s SyncUncertain state is true, unicast negotiation grant requests are not granted and current grants are canceled.

Default

tx-while-sync-uncertain

Platforms

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

Context

[Tree] (conf>router>segment-routing>sr-policies>policy type)

Full Context

configure router segment-routing sr-policies static-policy type

Description

This command configures the type of the static policy. Only commands relevant to the type of the static policy (SRv6 or SR-MPLS) can be executed. The type of the static policy can only be changed to a new type if there is no configuration present for the old type, or if all configuration for the old type is deleted.

Default

type sr-mpls

Parameters

sr-mpls

Specifies segment routing MPLS.

srv6

Specifies segment routing IPv6.

Platforms

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

Context

[Tree] (config>service>vprn>twamp-light>refl type)

[Tree] (config>router>twamp-light>reflector type)

Full Context

configure service vprn twamp-light reflector type

configure router twamp-light reflector type

Description

This command configures the processing behavior of the TWAMP Light reflector. When the value is twamp-light, the reflector does not check the received PDU as a traditional base TWAMP Light packet without TLV processing. When the value is stamp, the reflector attempts to find and process supported STAMP TLVs that follow the base STAMP packet.

In mixed environments where different types of session senders may be targeting a common TWAMP Light reflector, the value should be set to stamp. When the reflector is operating in stamp mode, the primary parsing is based on STAMP, checking and processing known TLVs, and also determining when TLVs are not present and the arriving PDU is a TWAMP Light PDU. A session sender launching a TWAMP Light-based packet must use all zeros and a padding pattern zero when the pad size is non zero.

Default

type twamp-light

Parameters

reflector-type

Specifies the type of processing behavior for the reflector.

Values

stamp, twamp-light

Platforms

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

Context

[Tree] (config>subscr-mgmt>bgp-prng-plcy type)

Full Context

configure subscriber-mgmt bgp-peering-policy type

Description

This command designates the BGP peer as type internal or external.

The type of internal indicates the peer is an IBGP peer while the type of external indicates that the peer is an EBGP peer.

By default, the OS derives the type of neighbor based on the local AS specified. If the local AS specified is the same as the AS of the router, the peer is considered internal. If the local AS is different, then the peer is considered external.

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

Parameters

internal

Configures the peer as internal.

external

Configures the peer as external.

Platforms

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

Context

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

Full Context

configure subscriber-mgmt wlan-gw tunnel-query type

Description

This command enables matching on specific tunnel types. If no tunnel type match criteria is specified, type matching is implicitly disabled.

Platforms

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

Context

[Tree] (config>router>radius-proxy>server>attribute-matching type)

[Tree] (config>service>vprn>radius-proxy>server>attribute-matching type)

Full Context

configure router radius-proxy server attribute-matching type

configure service vprn radius-proxy server attribute-matching type

Description

This command specifies the RADIUS VSA type for the entries to be matched with.

Parameters

type

Specifies the RADIUS server policy matching attribute-type.

Values

1 to 255

vendor-id

Specifies the vendor ID number.

Values

1 to 16777215, nokia

Platforms

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

Context

[Tree] (config>service>vprn>bgp>group type)

[Tree] (config>service>vprn>bgp>group>neighbor type)

Full Context

configure service vprn bgp group type

configure service vprn bgp group neighbor type

Description

This command designates the BGP peer as type internal or external.

The type of internal indicates the peer is an IBGP peer while the type of external indicates that the peer is an EBGP peer.

By default, the OS derives the type of neighbor based on the local AS specified. If the local AS specified is the same as the AS of the router, the peer is considered internal. If the local AS is different, then the peer is considered external.

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

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

Default

no type

Parameters

internal

Configures the peer as internal.

external

Configures the peer as external.

no type

Type of neighbor is derived on the local AS specified.

Platforms

All

Context

[Tree] (config>service>vprn type)

Full Context

configure service vprn type

Description

This command designates the type of VPRN instance being configured for hub and spoke topologies. Use the no form to reset to the default of a fully meshed VPRN.

Default

no type

Parameters

hub

Specifies a hub VPRN which allows all traffic from the hub SAPs to be routed to the destination directly, while all traffic from spoke VPRNs or network interfaces can only be routed to a hub SAP.

spoke

Specifies a spoke VPRN which allows traffic from associated SAPs or spoke terminations to only be forwarded through routes learned from separate VPRN, which should be configured as a type Hub VPRN.

subscriber-split-horizon

Controls the flow of traffic for wholesale subscriber applications.

Platforms

All

Context

[Tree] (config>saa>test type)

Full Context

configure saa test type

Description

This command creates the context to provide the test type for the named test. Only a single test type can be configured.

A test can only be modified while the test is in shut down mode.

Once a test type has been configured, the command can be modified by re-entering the command. However, the test type must be the same as the previously entered test type.

To change the test type, the old command must be removed using the config>saa>test>no type command.

The no form of this command removes the test type parameters from the configuration.

Platforms

All

Context

[Tree] (config>qos>sap-ingress>ip-criteria type)

[Tree] (config>qos>sap-ingress>ipv6-criteria type)

Full Context

configure qos sap-ingress ip-criteria type

configure qos sap-ingress ipv6-criteria type

Description

This command sets the ip-criteria and ipv6-criteria type to control the type of match entries configurable in this context.

Default

type normal

Parameters

filter-type

Specifies which type of entries that the ip-criteria and ipv6-criteria statements can contain.

Values

normal — Regular match criteria are allowed; VXLAN VNI matching is not allowed.

tagged-entries — Specifies that entries within that criteria statement are tagged. Tagged entries are not populated by default, they are only populated when their tag value is activated using the criteria override under an Ethernet SAP.

The type can only be changed from normal to tagged-entries if there are no ip-criteria or ipv6-criteria entries configured and the SAP ingress QoS policy is not applied to any object.

A SAP ingress QoS policy configured with a criteria statement with type tagged-entries is not supported within an SLA profile, sub profile or MSAP policy, or under an IES/VPRN group interface SAP.

The configuration of type tagged-entries is mutually exclusive with the configuration of the match dst-port in the same criteria statement.

vxlan-vni — Matching is allowed on a VXLAN VNI for VXLAN and VXLAN GPE frames.

The type cannot be changed when ip-criteria or ipv6-criteria entries are configured. If there are no ip-criteria or ipv6-criteria entries configured, the type can be changed from vxlan-vni to normal. The type can only be changed from normal to vxlan-vni if there are no ip-criteria or ipv6-criteria entries configured but it is necessary that the SAP ingress QoS policy is also not applied to any object in order to change from normal to vxlan-vni.

A SAP ingress QoS policy configured with type vxlan-vni can be applied to any Ethernet SAPs, except for a PW-SAP, B-VPLS SAP, or CCAG SAP, in any applicable service.

Platforms

All

Context

[Tree] (config>qos>sap-ingress>mac-criteria type)

Full Context

configure qos sap-ingress mac-criteria type

Description

This command sets the mac-criteria type.

Default

type normal

Parameters

filter-type

Specifies which type of entries this MAC filter can contain.

Values

normal — Regular match criteria are allowed; ISID match not allowed.

vid — Configures the VID filter type used to match on ethernet_II frame types. This allows matching VLAN tags for explicit filtering.

Platforms

All

Context

[Tree] (config>qos>queue-group-redirect-list type)

Full Context

configure qos queue-group-redirect-list type

Description

This command configures the type of a queue group redirect list. The default value is vxlan-vni, which is the only possible value.

Parameters

redirect-list-type

Specifies the type of the queue group redirect list. The queue group redirect list is used to match VXLAN VNIs in IPv4 and IPv6 VXLAN or VXLAN GPE packets.

Values

vxlan-vni

Platforms

All

Context

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

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

Full Context

configure filter ip-filter type

configure filter ipv6-filter type

Description

This command configures the filter policy type. The policy type defines the list of match criteria supported in a filter policy.

Default

type normal

Parameters

normal

Specifies the default filter policy type.

src-mac

Specifies the source MAC filter policy type to match on source MAC addresses in VPLS services.

packet-length

Specifies the packet-length filter policy type to match on the total packet length.

destination-class

Specifies the destination-class filter policy. This filter policy type is supported on egress networks, IES, VPRN, and R-VPLS interfaces.

Platforms

All

Context

[Tree] (config>filter>mac-filter type)

Full Context

configure filter mac-filter type

Description

This command configures the MAC Filter Policy type as being either normal, ISID or VID.

Default

type normal

Parameters

filter-type

Specifies which type of entry this MAC filter can contain.

Values

normal — regular match criteria are allowed; ISID or VID filter match criteria not allowed

isid — only ISID match criteria are allowed

vid — only VID match criteria are allowed on ethernet_II frame types

Platforms

All

Context

[Tree] (config>router>bfd>bfd-template type)

Full Context

configure router bfd bfd-template type

Description

This command selects the CPM network processor as the local termination point for the BFD session. This is enabled by default.

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

Default

no type

Platforms

All

Context

[Tree] (file type)

Full Context

file type

Description

This command displays the contents of a text file.

Parameters

file-url

Specifies the file contents to display.

Values

local-url	[cflash-id/][file-path] up to 200 characters, including cflash-id directory length up to 99 each
remote-url	[{ftp:// | tftp:// | http:// | https://}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:

profile

Specifies the TLS client profile configured under config>system>security>tls> client-tls-profile to use.

proxy-url

Specifies the URL of an HTTP proxy. For example, http://proxy.mydomain.com:8000. This URL must be an HTTP URL and not an HTTPS URL.

no-redirect

Specifies to automatically refuse any HTTP redirects without prompting the user.

Platforms

All

Context

[Tree] (config>system>cron>sched type)

Full Context

configure system cron schedule type

Description

This command specifies how the system should interpret the commands contained within the schedule node.

Default

type periodic

Parameters

schedule-type

Specifies the type of schedule for the system to interpret the commands contained within the schedule node.

Values

periodic — Specifies a schedule which runs at a given interval. The interval must be specified for this feature to run successfully.

calendar — Specifies a schedule which runs based on a calendar. The month, weekday, day-of-month, and minute parameters must be specified for this feature to run successfully.

oneshot — Specifies a schedule which runs one time only. As soon as the first event specified in these parameters takes place and the associated event occurs, the schedule enters a shutdown state. The month, weekday, day-of-month, and minute parameters must be specified for this feature to run successfully.

Default

periodic

Platforms

All

Context

[Tree] (config>system>management-interface>cli>md-cli>environment>progress-indicator type)

Full Context

configure system management-interface cli md-cli environment progress-indicator type

Description

This command specifies the type of progress indicator used in the MD-CLI.

Default

type dots

Parameters

indicator-type

Specifies the progress indicator type.

Values

dots: displays the progress indicator as dynamically changing dots

Platforms

All

Context

[Tree] (debug>system>grpc type)

Full Context

debug system grpc type

Description

This command enables debugging for all RPCs or a particular RPC.

The no form of this command deactivates debugging for all RPCs.

Parameters

all

Specifies that debugging is enabled for all RPCs.

gnmi-capabilities

Specifies that debugging is enabled for gNMI capability RPC.

gnmi-get

Specifies that debugging is enabled for gNMI get RPC.

gnmi-set

Specifies that debugging is enabled for gNMI set RPC.

gnmi-subscribe

Specifies that debugging is enabled for gNMI subscribe RPC.

gnoi-cert-mgmt-rpcs

Specifies that debugging is enabled for gNOI certificate management RPCs.

Platforms

All

Context

[Tree] (config>router>bgp>group>neighbor type)

[Tree] (config>router>bgp>group type)

Full Context

configure router bgp group neighbor type

configure router bgp group type

Description

This command designates the BGP peer as type internal or external.

The type of internal indicates the peer is an IBGP peer while the type of external indicates that the peer is an EBGP peer.

By default, the router derives the type of neighbor based on the local AS specified. If the local AS specified is the same as the AS of the router, the peer is considered internal. If the local AS is different, then the peer is considered external.

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

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

Default

no type

Parameters

internal

Configures the peer as internal.

external

Configures the peer as external.

Platforms

All

Context

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

Full Context

configure router policy-options policy-statement entry from type

Description

This command configures an OSPF type metric as a match criterion in the route policy statement entry.

If no type is specified, any OSPF type is considered a match.

The no form of this command removes the OSPF type match criterion.

Default

no type

Parameters

1

Matches OSPF routes with type 1 LSAs.

2

Matches OSPF routes with type 2 LSAs.

Platforms

All

Context

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

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

Full Context

configure router policy-options policy-statement default-action type

configure router policy-options policy-statement entry action type

Description

This command sets the subtype for the Type 5 LSA (external LSA).

The no form of this command disables assigning a type in the route policy entry.

Default

type 2

Parameters

type

Specifies the type metric.

Values

Subtype 1 — The external metric in the external LSA is comparable with the internal metric, and thus one can sum up all the metrics along the path (both internal and external) to get the total cost to the destination.

Subtype 2 — The metric in the external LSA is much more important than the internal metric, so the internal metrics should only be considered when comparing two external routes that have the same external metric.

param-name

The type parameter variable name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes. Policy parameters must start and end with at-signs (@); for example, "@variable@”.

Platforms

All

Context

[Tree] (config>saa>test type-multi-line)

Full Context

configure saa test type-multi-line

Description

This command creates the context to configure the OAM probe type and its parameters in a flexible multi-line format.

The no form of this command removes the context.

Platforms

All