t Commands

t2-paths

t2-paths

Syntax

t2-paths

Context

[Tree] (config>mcast-mgmt>bw-plcy t2-paths)

Full Context

configure mcast-management bandwidth-policy t2-paths

Description

Commands in this context configure T2 path queuing parameters for primary and secondary paths.

Platforms

7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR

t391

t391

Syntax

t391 [value]

no t391

Context

[Tree] (config>port>ethernet>elmi t391)

Full Context

configure port ethernet elmi t391

Description

This command configures the polling timer for UNI-C.

Parameters

value

Specifies the polling timer for UNI-C.

Values

5 to 30

Platforms

All

t392

t392

Syntax

t392 [value]

no t392

Context

[Tree] (config>port>ethernet>elmi t392)

Full Context

configure port ethernet elmi t392

Description

This command configures the polling verification timer for UNI-N.

Parameters

value

Specifies the polling verification timer for UNI-N.

Values

5 to 30

Platforms

All

tab

tab

Syntax

[no] tab

Context

[Tree] (config>system>management-interface>cli>md-cli>environment>command-completion tab)

Full Context

configure system management-interface cli md-cli environment command-completion tab

Description

This command enables completion on the tab character.

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

Default

tab

Platforms

All

table-size

table-size

Syntax

table-size table-size

Context

[Tree] (config>service>vpls>proxy-nd table-size)

[Tree] (config>service>vpls>proxy-arp table-size)

Full Context

configure service vpls proxy-nd table-size

configure service vpls proxy-arp table-size

Description

This command adds a table-size limit per service. By default, the table-size limit is 250; it can be set up to 16k entries per service. A non-configurable implicit high watermark of 95% and low watermark of 90% exists, per service and per system. When those watermarks are reached, a syslog/trap is triggered. When the system/service limit is reached, entries for a specified IP can be replaced (a different MAC can be learned and added) but no new IP entries will be added, regardless of the type (Static, evpn, dynamic). If the user attempts to change the table-size value to a value that cannot accommodate the number of existing entries, the attempt will fail.

Default

table-size 250

Parameters

table-size

Specifies the table-size as number of entries for the service.

Values

1 to 16384

Platforms

All

tacplus

tacplus

Syntax

no tacplus

tacplus create

Context

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

Full Context

configure service vprn aaa remote-servers tacplus

Description

This command creates the context to configure TACACS+ authentication on the VPRN.

Configure multiple server addresses for each router for redundancy.

The no form of this command removes the TACACS+ configuration.

Platforms

All

tacplus

Syntax

[no] tacplus

Context

[Tree] (config>system>security tacplus)

Full Context

configure system security tacplus

Description

This command creates the context to configure TACACS+ authentication on the router.

Configure multiple server addresses for each router for redundancy.

The no form of this command removes the TACACS+ configuration.

Platforms

All

tacplus-map-to-priv-lvl

tacplus-map-to-priv-lvl

Syntax

tacplus-map-to-priv-lvl [admin-priv-lvl]

no tacplus-map-to-priv-lvl

Context

[Tree] (config>system>security>password>enable-admin-control tacplus-map-to-priv-lvl)

Full Context

configure system security password enable-admin-control tacplus-map-to-priv-lvl

Description

When tacplus-map-to-priv-lvl is enabled, and tacplus authorization is enabled with the use-priv-lvl option, typing enable-admin starts an interactive authentication exchange from the node to the TACACS+ server. The start message (service=enable) contains the user-id and the requested admin-priv-lvl. Successful authentication results in the use of a new profile (as configured under config>system>security>tacplus>priv-lvl-map).

Platforms

All

tag

tag

Syntax

tag tag

no tag [tag]

Context

[Tree] (config>service>vprn>static-route-entry tag)

Full Context

configure service vprn static-route-entry tag

Description

This command associates a 4-byte route-tag with the static route. The tag value can be used in route policies to control distribution of the static route into other protocols.

The tag specified at this level of the static route causes tag values configured under the next-hop, black-hole, and indirect contexts of the static route to be ignored.

The no form of this command removes the tag association.

Default

no tag

Parameters

tag

Specifies an integer value.

Values

1 to 4294967295

Platforms

All

tag

Syntax

tag tag-value

no tag [tag-value]

Context

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

[Tree] (config>service>vprn>static-route-entry>next-hop tag)

[Tree] (config>service>vprn>static-route-entry>ipsec-tunnel tag)

Full Context

configure service vprn static-route-entry indirect tag

configure service vprn static-route-entry next-hop tag

configure service vprn static-route-entry ipsec-tunnel tag

Description

This command adds a 32-bit integer tag to the associated static route.

The tag value can be used in route policies to control distribution of the route into other protocols.

Default

no tag

Parameters

tag-value

Specifies an integer tag value.

Values

32 bit integer

Platforms

All

tag

Syntax

tag tag

no tag

Context

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

Full Context

configure service vprn isis interface tag

Description

This command configures a route tag to the specified IP address of an interface.

Parameters

tag

Specifies the tag value.

Values

1 to 4294967295

Platforms

All

tag

Syntax

tag tag

no tag [tag]

Context

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

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

[Tree] (config>router>static-route-entry>black-hole tag)

[Tree] (config>router>static-route-entry>indirect tag)

Full Context

configure router static-route-entry tag

configure router static-route-entry next-hop tag

configure router static-route-entry black-hole tag

configure router static-route-entry indirect tag

Description

This command associates a 4-byte route-tag with the static route. The tag value can be used in route policies to control distribution of the static route into other protocols.

The tag specified at this level of the static route causes tag values configured under the next-hop, black-hole and indirect contexts of the static route to be ignored.

The no form of this command removes the tag association.

Default

no tag

Parameters

tag

Specifies an integer tag value.

Values

1 to 4294967295

Platforms

All

tag

Syntax

tag tag

no tag

Context

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

Full Context

configure router isis interface tag

Description

This command configures a route tag to the specified IP address of an interface.

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

Parameters

tag

Specifies a route tag.

Values

1 to 4294967295

Platforms

All

tag

Syntax

tag tag

no tag

Context

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

Full Context

configure router isis interface tag

Description

This command configures a route tag to the specified IP address of an interface.

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

Default

no tag

Parameters

tag

Specifies a route tag.

Values

1 to 4294967295

Platforms

All

tag

Syntax

tag {no-tag | tag}

no tag

Context

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

Full Context

configure router policy-options policy-statement entry from tag

Description

This command matches the tag value in static or IGP routes. A decimal or hexadecimal value of 4 octets can be entered. For IS-IS, OSPF, and static routes, all four octets can be used. For RIP and RIPng, only the two most significant octets are used if more than two octets are configured.

The no form of this command removes the tag field match criterion.

Default

no tag

Parameters

tag

Matches the configured tag value.

Values

Accepts decimal or hexadecimal formats:

  • IS-IS, OSPF and static routes: 0x0 – 0xFFFFFFFF or 1 – 4294967295

  • RIP and RIPng: 0x0 – 0xFFFF or 1 – 65535

no-tag

Specifies that no tag value is set.

Platforms

All

tag

Syntax

tag tag

no tag

Context

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

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

Full Context

configure router policy-options policy-statement default-action tag

configure router policy-options policy-statement entry action tag

Description

This command assigns a tag to routes matching the entry, which is then applied to IGP routes. A decimal or hexadecimal value of 4 octets can be entered.

For IS-IS and OSPF, all four octets can be used.

For RIP and RIPng, only the two most significant octets are used if more than two octets are configured.

The no form of this command removes the tag.

Default

no tag

Parameters

tag

Assigns an IS-IS, OSPF, RIP or RIPng tag to routes matching the entry.

Values

Accepts decimal or hexadecimal formats:

IS-IS and OSPF: 0x0–0xFFFFFFFF or 1–4294967295

RIP and RIPng: 0x0–0xFFFF or 1–65535

name — The tag 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 (#, $, spaces, and so on), the entire string must be enclosed within double quotes. Policy parameters must start and end with at-signs (@); for example, "@variable@”.

Platforms

All

tag

Syntax

tag tag-id

no tag

Context

[Tree] (config>qos>sap-ingress>ipv6-criteria>entry tag)

[Tree] (config>qos>sap-ingress>ip-criteria>entry tag)

Full Context

configure qos sap-ingress ipv6-criteria entry tag

configure qos sap-ingress ip-criteria entry tag

Description

This command associates a tag with the criteria entry.

Tag identifiers are not supported in SAP ingress QoS policies, MAC criteria statements, or in SAP egress QoS policies.

The no form of this command removes the tag.

Parameters

tag-id

Specifies the tag ID.

Values

1 to 255

Platforms

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

tag

Syntax

tag tag

no tag

Context

[Tree] (config>router>isis>srv6>locator tag)

Full Context

configure router isis segment-routing-v6 locator tag

Description

This command configures a route tag to advertise in the locator TLV.

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

Default

no tag

Parameters

tag

Specifies a route tag.

Values

1 to 4294967295

Platforms

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

tag

Syntax

tag value

no tag

Context

[Tree] (config>service>vprn>sub-if>grp-if>sap>static-host>managed-routes>route-entry tag)

[Tree] (config>service>ies>sub-if>grp-if>sap>static-host>managed-routes>route-entry tag)

Full Context

configure service vprn subscriber-interface group-interface sap static-host managed-routes route-entry tag

configure service ies subscriber-interface group-interface sap static-host managed-routes route-entry tag

Description

This command associates a route tag with the provisioned managed route.

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

Default

no tag

Parameters

value

Specifies the tag value.

Values

1 to 4294967295

Platforms

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

tag-protocol-id

tag-protocol-id

Syntax

tag-protocol-id tag-protocol-id

no tag-protocol-id

Context

[Tree] (config>test-oam>build-packet>header>dot1q tag-protocol-id)

[Tree] (debug>oam>build-packet>packet>field-override>header>dot1q tag-protocol-id)

Full Context

configure test-oam build-packet header dot1q tag-protocol-id

debug oam build-packet packet field-override header dot1q tag-protocol-id

Description

This command defines the Dot1Q tag protocol ID to be used in the test Dot1Q header.

The no form of this command removes the tag protocol ID value.

Default

tag-protocol-id 0x8100 (33024)

Parameters

tag-protocol-id

Specifies the Dot1Q tag protocol ID to be used in the test Dot1Q header in either decimal or hexadecimal.

Values

1536 to 65535

Platforms

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

tag-protocol-id

Syntax

tag-protocol-id tag-protocol-id

no tag-protocol-id

Context

[Tree] (config>test-oam>build-packet>header>pbb tag-protocol-id)

Full Context

configure test-oam build-packet header pbb tag-protocol-id

Description

This command defines the PBB Tag Protocol Identifier (TPID) to be used in the test PBB header.

The no form of this command reverts to the default.

Default

tag-protocol-id 0x88E7 (35047)

Parameters

tag-protocol-id

Specifies a tag Protocol Identifier (TPID) for a PBB packet header to be launched by the OAM find-egress tool.

Values

1536 to 65535

Platforms

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

tag-protocol-id

Syntax

tag-protocol-id tag-protocol-id

no tag-protocol-id

Context

[Tree] (debug>oam>build-packet>packet>field-override>header>pbb tag-protocol-id)

Full Context

debug oam build-packet packet field-override header pbb tag-protocol-id

Description

This command defines the PBB TPID to be used in the PBB header.

The no form of this command reverts to the default.

Default

tag-protocol-id 0

Parameters

tag-protocol-id

Specifies a TPID for a PBB packet header to be launched by the OAM find-egress tool.

Values

1536 to 65535

Platforms

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

taii-type2

taii-type2

Syntax

taii-type2 global-id:node-id:ac-id

no taii-type2

Context

[Tree] (config>service>cpipe>spoke-sdp>pw-path-id taii-type2)

[Tree] (config>service>vpls>spoke-sdp>pw-path-id taii-type2)

[Tree] (config>service>epipe>spoke-sdp>pw-path-id taii-type2)

Full Context

configure service cpipe spoke-sdp pw-path-id taii-type2

configure service vpls spoke-sdp pw-path-id taii-type2

configure service epipe spoke-sdp pw-path-id taii-type2

Description

This command configures the Target Individual Attachment Identifier (TAII) for an MPLS-TP spoke SDP. If this is configured on a spoke SDP for which vc-switching is also configured (for example, it is at an S-PE), then the values must match those of the saii-type2 of the mate spoke SDP.

Parameters

global-id

Specifies the global ID at the target PE or T-PE for the MPLS-TP PW for a spoke SDP.

Values

0 to 4294967295

node-id

Specifies the node ID at the target PE or T-PE for the MPLS-TP PW for a spoke SDP.

Values

a.b.c.d or 0 to 4294967295

ac-id

Specifies the attachment circuit ID at the target PE or T-PE for the MPLS-TP PW for a spoke SDP. If this node is the source of the PW, then the AC ID must be set to a locally unique value.

Values

1 to 4294967295

Platforms

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

taii-type2

Syntax

taii-type2 global-id:prefix:ac-id

no taii-type2

Context

[Tree] (config>service>epipe>spoke-sdp-fec taii-type2)

Full Context

configure service epipe spoke-sdp-fec taii-type2

Description

taii-type2 configures the target attachment individual identifier for the SDP SDP. This is only applicable to FEC129 AII type 2.

This command is blocked in CLI if this end of the spoke SDP is configured for single-sided auto configuration (using the auto-config command).

Parameters

global-id

Specifies a global ID of this router T-PE. This value must correspond to one of the global_id values configured for a local-prefix under config>service>pw-routing>local-prefix context.

Values

1 to 4294967295

prefix

Speecifies prefix on this router T-PE that the spoke SDP SDP is associated with. This value must correspond to one of the prefixes configured under config>service>pw-routing>local-prefix context.

Values

an IPv4-formatted address a.b.c.d or 1 to 4294967295

ac-id

Specifies an unsigned integer representing a locally unique identifier for the spoke SDP.

Values

1 to 4294967295

Platforms

All

taii-type2

Syntax

taii-type2 global-id:node-id:ac-id

no taii-type2

Context

[Tree] (config>service>ies>if>spoke-sdp>pw-path-id taii-type2)

Full Context

configure service ies interface spoke-sdp pw-path-id taii-type2

Description

This command configures the target individual attachment identifier (TAII) for an MPLS-TP spoke-sdp. If this is configured on a spoke-sdp for which vc-switching is also configured (for example, it is at an S-PE), then the values must match those of the saii-type2 of the mate spoke-sdp.

Parameters

global-id

Specifies the global ID at the target PE or T-PE for the MPLS-TP PW for a spoke-SDP.

Values

0 to 4294967295

node-id

Specifies the node ID at the target PE or T-PE for the MPLS-TP PW for a spoke-SDP.

Values

a.b.c.d or 0 to 4294967295

ac-id

Specifies the attachment circuit ID at the target PE or T-PE for the MPLS-TP PW for a spoke-SDP. If this node is the source of the PW, then the AC ID must be set to a locally unique value.

Values

1 to 4294967295

Platforms

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

taii-type2

Syntax

taii-type2 global-id:node-id:ac-id

no taii-type2

Context

[Tree] (config>service>vprn>red-if>spoke-sdp>pw-path-id taii-type2)

Full Context

configure service vprn redundant-interface spoke-sdp pw-path-id taii-type2

Description

This command configures the target individual attachment identifier (TAII) for an MPLS-TP spoke SDP. If this is configured on a spoke SDP for which vc-switching is also configured (for example, it is at an S-PE), then the values must match those of the saii-type2 of the mate spoke SDP.

Parameters

global-id

Specifies the global ID at the target PE or T-PE for the MPLS-TP PW for a spoke SDP.

Values

0 to 4294967295

node-id

Specifies the node ID at the target PE or T-PE for the MPLS-TP PW for a spoke SDP.

Values

a.b.c.d or 1 to 4294967295

ac-id

Specifies the attachment circuit ID at the target PE or T-PE for the MPLS-TP PW for a spoke SDP. If this node is the source of the PW, then the AC ID must be set to a locally unique value.

Values

1 to 4294967295

Platforms

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

taii-type2

Syntax

taii-type2 global-id:node-id:ac-id

no taii-type2

Context

[Tree] (config>mirror>mirror-dest>spoke-sdp>pw-path-id taii-type2)

[Tree] (config>mirror>mirror-dest>remote-src>spoke-sdp>pw-path-id taii-type2)

Full Context

configure mirror mirror-dest spoke-sdp pw-path-id taii-type2

configure mirror mirror-dest remote-source spoke-sdp pw-path-id taii-type2

Description

This command configures the target individual attachment identifier (TAII) for an MPLS-TP spoke SDP. If this is configured on a spoke SDP for which vc-switching is also configured (for example, it is at an S-PE), then the values must match those of the saii-type2 of the mate spoke SDP.

Parameters

global-id

Specifies the global ID at the target PE or T-PE for the MPLS-TP PW for a spoke SDP.

Values

0 to 4294967295

node-id

Specifies the node ID at the target PE or T-PE for the MPLS-TP PW for a spoke SDP.

Values

a.b.c.d or 0 to 4294967295

ac-id

Specifies the attachment circuit ID at the target PE or T-PE for the MPLS-TP PW for a spoke SDP. If this node is the source of the PW, then the AC ID must be set to a locally unique value.

Values

1 to 4294967295

Platforms

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

tail-end

tail-end

Syntax

[no] tail-end

Context

[Tree] (config>router>lsp-bfd tail-end)

Full Context

configure router lsp-bfd tail-end

Description

This command enables the context to configure LSP BFD tail end parameters.

The no form of this command removes the context.

Default

no tail-end

Platforms

All

target-name

target-name

Syntax

target-name {node-name | user-agent | custom-string name}

no target-name

Context

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

Full Context

configure system grpc-tunnel tunnel target-name

Description

This command assigns a target name that the node will register with.

The no form of this command removes the target name.

Default

no target-name

Parameters

node-name

Keyword to register the tunnel with the node name configured using the configure system name command.

user-agent

Keyword to register the tunnel with the user agent name string defined as node-name:vendor:model:software-version.

custom-string

Assigns an arbitrary string as the target name.

name

Specifies a string, up to 64 characters, that defines the target name.

Platforms

All

target-power

target-power

Syntax

target-power power

Context

[Tree] (config>port>dwdm>coherent target-power)

Full Context

configure port dwdm coherent target-power

Description

This command configures the target transmit optical power for the port.

Default

target-power 1.00

Parameters

power

Specifies the desired average output power in dBm.

Values

-20.00 to 3.00

Platforms

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

target-retry-wait

target-retry-wait

Syntax

target-retry-wait seconds

Context

[Tree] (config>li>x-interfaces>x3>timeouts target-retry-wait)

Full Context

configure li x-interfaces x3 timeouts target-retry-wait

Description

This command configures the retry interval for target tunnel set up.

Parameters

seconds

Specifies the time that the system must wait before attempting another tunnel creation request to avoid overloading the LIC.

Values

300 to 1200

Default

300

Platforms

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

target-type

target-type

Syntax

target-type {grpc-server | ssh-server | custom-type type}

no target-type

Context

[Tree] (config>system>grpc-tunnel>tunnel>handler target-type)

Full Context

configure system grpc-tunnel tunnel handler target-type

Description

This command assigns a server as a handler for all tunnel sessions.

The no form of this command disables the tunnel handler server.

Default

no target-type

Parameters

grpc-server

Keyword that assigns the gRPC server as a handler for all tunnels sessions. The gRPC-tunnel protocol value corresponds to "GNMI_GNOI”.

ssh-server

Keyword that assigns the SSH server as a handler for all tunnels sessions. The gRPC-tunnel protocol value corresponds to "SSH”.

custom-type

Keyword that assigns an arbitrary string as the target type.

type

Specifies a string, up to 255 characters, defining the client to serve as a handler for all tunnel sessions. Values used by gRPC tunnel protocol, such as "GNMI_GNOI” or "SSH” can also be used.

Platforms

All

targeted-session

targeted-session

Syntax

targeted-session

Context

[Tree] (config>router>ldp targeted-session)

Full Context

configure router ldp targeted-session

Description

This command configures targeted LDP sessions. Targeted sessions are LDP sessions between non-directly connected peers. Hello messages are sent directly to the peer platform instead of to all the routers on this subnet multicast address. The user can configure different default parameters for IPv4 and IPv6 LDP targeted hello adjacencies.

The discovery messages for an indirect LDP session are addressed to the specified peer and not to the multicast address.

Platforms

All

task

task

Syntax

task [detail]

no task

Context

[Tree] (debug>router>pcep>pcc>conn task)

[Tree] (debug>router>pcep>pcc task)

Full Context

debug router pcep pcc connection task

debug router pcep pcc task

Description

This command enables debugging for PCC or connection task events.

The no form of this command disables debugging.

Parameters

detail

Keyword used to specify detailed information about PCC or connection task events.

Platforms

All

task

Syntax

task [detail]

no task

Context

[Tree] (debug>router>pcep>pce task)

[Tree] (debug>router>pcep>pce>conn task)

Full Context

debug router pcep pce task

debug router pcep pce connection task

Description

This command enables debugging for PCE or connection task events.

The no form of this command disables debugging.

Parameters

detail

Keyword used to specify detailed information about PCE or connection task events.

Platforms

VSR-NRC

task-scheduling-int

task-scheduling-int

Syntax

task-scheduling-int percent-of-default

no task-scheduling-int

Context

[Tree] (config>card>virt-sched-adj task-scheduling-int)

Full Context

configure card virtual-scheduler-adjustment task-scheduling-int

Description

This command overrides the system default time between scheduling the hierarchical virtual scheduling task. By default, the system "wakes” the virtual scheduler task every 50ms; this is equivalent to five 10ms timer ticks. The task-scheduling-int command uses a percent value parameter to modify the number of timer ticks.

While the system accepts a wide range of percent values, the result is rounded to the nearest 10ms tick value. The fastest wake interval is 10ms (1 timer tick).

The no form of this command restores the default task scheduling interval of the card’s hierarchical virtual scheduler task.

Parameters

percent-of-default:

Specifies that the percent-of-default parameter is required and is used to modify the default task scheduling interval for the hierarchical virtual scheduling task on the card. Defining 100.00 percent is equivalent to removing the override.

Values

0.01% to 1000.00%

Default

100.00%

Platforms

All

tcp

tcp

Syntax

tcp

Context

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

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

Full Context

debug oam build-packet packet field-override header tcp

configure test-oam build-packet header tcp

Description

This command creates a TCP header and enables the context to define the associated parameters.

Platforms

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

tcp-ack

tcp-ack

Syntax

tcp-ack {true | false}

no tcp-ack

Context

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>egr-ip>entry>match tcp-ack)

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>egr-ipv6>entry>match tcp-ack)

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>ingr-ipv6>entry>match tcp-ack)

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>ingr-ip>entry>match tcp-ack)

Full Context

configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ip-filter-entries entry match tcp-ack

configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ipv6-filter-entries entry match tcp-ack

configure subscriber-mgmt category-map category exhausted-credit-service-level ingress-ipv6-filter-entries entry match tcp-ack

configure subscriber-mgmt category-map category exhausted-credit-service-level ingress-ip-filter-entries entry match tcp-ack

Description

This command configures the TCP ACK match condition.

The no form of this command reverts to the default.

Parameters

true

Enables checking for the ACK bit.

false

Disables checking for the ACK bit.

Platforms

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

tcp-ack

Syntax

tcp-ack {true | false}

no tcp-ack

Context

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

[Tree] (config>filter>ipv6-filter>entry>match tcp-ack)

Full Context

configure filter ip-filter entry match tcp-ack

configure filter ipv6-filter entry match tcp-ack

Description

This command configures an IP filter match criterion based on the Acknowledgment (ACK) TCP Flag bit, defined in RFC 793, as being set or not in the TCP header of an IP packet.

The no form of the command removes the criterion from the match entry.

Default

no tcp-ack

Parameters

true

Specifies matching on IP packets that have the selected TCP flag bit set in the TCP header.

false

Specifies matching on IP packets that do not have the selected TCP flag bit set in the TCP header.

Platforms

All

tcp-ack

Syntax

tcp-ack {true | false}

no tcp-ack

Context

[Tree] (cfg>sys>sec>cpm>ip-filter>entry>match tcp-ack)

[Tree] (cfg>sys>sec>cpm>ipv6-filter>entry>match tcp-ack)

Full Context

configure system security cpm-filter ip-filter entry match tcp-ack

configure system security cpm-filter ipv6-filter entry match tcp-ack

Description

This command configures matching on the ACK bit being set or reset in the control bits of the TCP header of an IP or IPv6 packet as an IP filter match criterion.

Note:

An entry containing Layer 4 match criteria will not match non-initial (2nd, 3rd, etc) fragments of a fragmented packet since only the first fragment contains the Layer 4 information.

The no form of this command removes the criterion from the match entry.

Default

no tcp-ack

Parameters

true

Specifies matching on IP or IPv6 packets that have the ACK bit set in the control bits of the TCP header of an IP or IPv6 packet.

false

Specifies matching on IP or IPv6 packets that do not have the ACK bit set in the control bits of the TCP header of the IP or IPv6 packet.

Platforms

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

tcp-adv-func

tcp-adv-func

Syntax

tcp-adv-func size

Context

[Tree] (config>isa>aa-grp>shared-resources tcp-adv-func)

Full Context

configure isa aa-group shared-resources tcp-adv-func

Description

This command configures the allocation of shared resource pool for TCP advanced functions.

Default

tcp-adv-func 100

Parameters

size

Specifies the allocation of the shared resource pool.

Values

0 to 100

tcp-client-reset

tcp-client-reset

Syntax

[no] tcp-client-reset

Context

[Tree] (config>app-assure>group>http-redirect tcp-client-reset)

Full Context

configure application-assurance group http-redirect tcp-client-reset

Description

This command enables an HTTP-redirect policy to initiate a TCP reset towards the client if the AA policy results in a redirect with packet drop but the http redirect cannot be delivered. Scenarios for this include HTTPs (TLS) sessions, blocking of non-HTTP TCP traffic, and blocking of existing flows after a policy re-evaluate of an existing subscriber.

The no form of this command disables the command.

Platforms

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

tcp-cwr

tcp-cwr

Syntax

tcp-cwr {true | false}

no tcp-cwr

Context

[Tree] (config>filter>ipv6-filter>entry>match tcp-cwr)

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

Full Context

configure filter ipv6-filter entry match tcp-cwr

configure filter ip-filter entry match tcp-cwr

Description

This command configures an IP filter match criterion based on the Congestion Window Reduced (CWR) TCP Flag bit, defined in RFC 3168, as being set or not in the TCP header of an IP packet.

The no form of the command removes the criterion from the match entry.

Default

no tcp-cwr

Parameters

true

Specifies matching on IP packets that have the selected TCP flag bit set in the TCP header.

false

Specifies matching on IP packets that do not have the selected TCP flag bit set in the TCP header.

Platforms

All

tcp-ece

tcp-ece

Syntax

tcp-ece {true | false}

no tcp-ece

Context

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

[Tree] (config>filter>ipv6-filter>entry>match tcp-ece)

Full Context

configure filter ip-filter entry match tcp-ece

configure filter ipv6-filter entry match tcp-ece

Description

This command configures an IP filter match criterion based on the ECN-Echo (ECE) TCP Flag bit, defined in RFC 3168, as being set or not in the TCP header of an IP packet.

The no form of the command removes the criterion from the match entry.

Default

no tcp-ece

Parameters

true

Specifies matching on IP packets that have the selected TCP flag bit set in the TCP header.

false

Specifies matching on IP packets that do not have the selected TCP flag bit set in the TCP header.

Platforms

All

tcp-established

tcp-established

Syntax

tcp-established [hrs hours] [min minutes] [sec seconds]

no tcp-established

Context

[Tree] (config>service>nat>up-nat-policy>timeouts tcp-established)

[Tree] (config>service>nat>firewall-policy>timeouts tcp-established)

[Tree] (config>service>nat>nat-policy>timeouts tcp-established)

Full Context

configure service nat up-nat-policy timeouts tcp-established

configure service nat firewall-policy timeouts tcp-established

configure service nat nat-policy timeouts tcp-established

Description

This command configures the idle timeout applied to a TCP session in the established state.

Default

tcp-established hrs 2 min 4

Parameters

hours

Specifies the timeout hours field.

Values

1 to 24

minutes

Specifies the timeout minutes field.

Values

1 to 59

seconds

Specifies the timeout seconds field.

Values

1 to 59

Platforms

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

  • configure service nat up-nat-policy timeouts tcp-established
  • configure service nat nat-policy timeouts tcp-established

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

  • configure service nat firewall-policy timeouts tcp-established

tcp-established

Syntax

[no] tcp-established

Context

[Tree] (config>filter>ipv6-filter>entry>match tcp-established)

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

Full Context

configure filter ipv6-filter entry match tcp-established

configure filter ip-filter entry match tcp-established

Description

This command matches packets with the TCP flag ACK or RST.

Default

tcp-established

Platforms

All

tcp-fin

tcp-fin

Syntax

tcp-fin {true | false}

no tcp-fin

Context

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

[Tree] (config>filter>ipv6-filter>entry>match tcp-fin)

Full Context

configure filter ip-filter entry match tcp-fin

configure filter ipv6-filter entry match tcp-fin

Description

This command configures an IP filter match criterion based on the FIN TCP Flag bit, defined in RFC 793, as being set or not in the TCP header of an IP packet.

The no form of the command removes the criterion from the match entry.

Default

no tcp-fin

Parameters

true

Specifies matching on IP packets that have the selected TCP flag bit set in the TCP header.

false

Specifies matching on IP packets that do not have the selected TCP flag bit set in the TCP header.

Platforms

All

tcp-keepalive

tcp-keepalive

Syntax

tcp-keepalive

Context

[Tree] (config>system>grpc tcp-keepalive)

Full Context

configure system grpc tcp-keepalive

Description

Commands in this context configure the sending of TCP keepalives by the router towards all gRPC clients.

Enabling TCP keepalive speeds up the detection of certain failures. The TCP keepalives sent by the router are controlled by three commands: idle-time, interval, and retries. The router starts sending TCP keepalives when the connection has been idle (no TCP segments sent or received) for more than idle-time seconds. At that point, the router sends a probe (TCP ACK with a sequence number = current sequence number - 1) and expects a TCP ACK. It repeats this probe every interval seconds for the configured number of retries. If no response is received to any of the probes, the connection is immediately closed, which starts the purge timer if the TCP connection is currently supporting the RibApi service.

Platforms

All

tcp-keepalive

Syntax

tcp-keepalive

Context

[Tree] (config>bmp>station>connection tcp-keepalive)

Full Context

configure bmp station connection tcp-keepalive

Description

Commands in this context configure TCP keepalive parameters for the station.

Platforms

All

tcp-keepalive

Syntax

tcp-keepalive

Context

[Tree] (config>system>grpc-tunnel>destination-group tcp-keepalive)

[Tree] (config>system>telemetry>destination-group tcp-keepalive)

Full Context

configure system grpc-tunnel destination-group tcp-keepalive

configure system telemetry destination-group tcp-keepalive

Description

Commands in this context configure TCP keepalive commands.

Platforms

All

tcp-mss

tcp-mss

Syntax

tcp-mss mss-value

no tcp-mss

Context

[Tree] (config>service>ies>if tcp-mss)

[Tree] (config>service>ies>if>ipv6 tcp-mss)

Full Context

configure service ies interface tcp-mss

configure service ies interface ipv6 tcp-mss

Description

This command statically sets the TCP maximum segment size (MSS) for TCP connections originated from the associated IP interface to the specified value.

The no form of this command removes the static value and allows the TCP MSS value to be calculated based on the IP MTU value by subtracting the base IP and TCP header lengths from the IP MTU value (tcp_mss = ip_mtu – 40).

Default

no tcp-mss

Parameters

mss-value

The TCP MSS value that should be used in the TCP SYN packet during the three-way handshake negotiation of a TCP connection.

Note: 9158 = max-IP_MTU (9198)-40

Values

536 to 9746 (IPv4) 1220 to 9726 (IPv6)

Platforms

All

tcp-mss

Syntax

tcp-mss mss-value

no tcp-mss

Context

[Tree] (config>service>vprn>if>ipv6 tcp-mss)

[Tree] (config>service>vprn>if tcp-mss)

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

Full Context

configure service vprn interface ipv6 tcp-mss

configure service vprn interface tcp-mss

configure service vprn network-interface tcp-mss

Description

This command statically sets the TCP maximum segment size (MSS) for TCP connections originated from the associated IP or network interface to the specified value.

The no form of this command removes the static value and allows the TCP MSS value to be calculated based on the IP MTU value by subtracting the base IP and TCP header lengths from the IP MTU value (tcp_mss = ip_mtu – 40).

Default

no tcp-mss

Parameters

mss-value

Specifies the TCP MSS value that should be used in the TCP SYN packet during the three-way handshake negotiation of a TCP connection.

Note: 9746 = max-IP_MTU (9786)-40

Values

384 to 9746 (IPv4 or network)

1220 to 9726(IPv6)

Platforms

All

tcp-mss

Syntax

tcp-mss mss-value

no tcp-mss

Context

[Tree] (config>router>if tcp-mss)

[Tree] (config>router>if>ipv6 tcp-mss)

Full Context

configure router interface tcp-mss

configure router interface ipv6 tcp-mss

Description

This command statically sets the TCP maximum segment size (MSS) for TCP connections originated from the associated IP interface to the specified value.

The no form of this command removes the static value and allows the TCP MSS value to be calculated based on the IP MTU value by subtracting the base IP and TCP header lengths from the IP MTU value (tcp_mss = ip_mtu – 40).

Default

no tcp-mss

Parameters

mss-value

Specifies the TCP MSS value that should be used in the TCP SYN packet during the three-way handshake negotiation of a TCP connection.

9158 = max-IP_MTU (9198)-40

Values

536 to 9746 (IPv4) 1220 to 9726 (IPv6)

Platforms

All

tcp-mss

Syntax

tcp-mss mss-value

no tcp-mss

Context

[Tree] (config>service>vprn>bgp tcp-mss)

[Tree] (config>router>bgp tcp-mss)

Full Context

configure service vprn bgp tcp-mss

configure router bgp tcp-mss

Description

This command configures an override for the TCP maximum segment size to use with a specific peer or set of peers (depending on the scope of the command).

The configured value controls two properties of the TCP connection as follows:

  • TCP MSS option — The router advertises the TCP MSS option value in the TCP SYN packet it sends as part of the 3-way handshake. The advertised value may be lower than the configured value, depending on the IP MTU of the first hop IP interface. The peers are asked to abide by this value when sending TCP segments to the local router.

  • TCP maximum segment size — The actual transmitted size may be lower than the configured value, depending on the TCP MSS option value signaled by the peers, the effect of path MTU discovery, or other factors.

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

Default

no tcp-mss

Parameters

mss-value

Specifies the The router uses the TCP SYN to advertise the TCP MSS option value towards its peer. MSS value, in bytes, to use with the peers that fall within the scope of the command.

Values

384 to 9746

Platforms

All

tcp-mss

Syntax

tcp-mss ip-stack

tcp-mss mss-value

no tcp-mss

Context

[Tree] (config>service>vprn>bgp>group>neighbor tcp-mss)

[Tree] (config>router>bgp>group tcp-mss)

[Tree] (config>service>vprn>bgp>group tcp-mss)

[Tree] (config>router>bgp>group>neighbor tcp-mss)

Full Context

configure service vprn bgp group neighbor tcp-mss

configure router bgp group tcp-mss

configure service vprn bgp group tcp-mss

configure router bgp group neighbor tcp-mss

Description

This command configures an override for the TCP maximum segment size to use with a specific peer or set of peers (depending on the scope of the command).

The configured value controls two properties of the TCP connection as follows:

  • TCP MSS option — The router advertises the TCP MSS option value in the TCP SYN packet it sends as part of the 3-way handshake. The advertised value may be lower than the configured value, depending on the IP MTU of the first hop IP interface. The peers are asked to abide by this value when sending TCP segments to the local router.

  • TCP maximum segment size — The actual transmitted size may be lower than the configured value, depending on the TCP MSS option value signaled by the peers, the effect of path MTU discovery, or other factors.

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

Default

no tcp-mss

Parameters

mss-value

Specifies the TCP MSS value, in bytes, to use with the peers that fall within the scope of the command.

Values

384 to 9746

ip-stack

This keyword requests that TCP MSS be derived from mechanisms and configurations outside of BGP, including the configuration of tcp-mss at the IP interface level. It provides a method to override inheritance within the BGP configuration.

Platforms

All

tcp-mss-adjust

tcp-mss-adjust

Syntax

tcp-mss-adjust segment-size

no tcp-mss-adjust

Context

[Tree] (config>service>ies>sub-if>grp-if>wlan-gw tcp-mss-adjust)

[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw tcp-mss-adjust)

Full Context

configure service ies subscriber-interface group-interface wlan-gw tcp-mss-adjust

configure service vprn subscriber-interface group-interface wlan-gw tcp-mss-adjust

Description

This command configures the TCP Maximum Segment Size (MSS) adjustment for the wlan-gw gateway.

The no form of this command disables adjusting tcp-mss values.

For DSM, this only applies to packets sent in the downstream direction (TCP SYN towards UE). For the upstream direction, it is also required to configure MSS adjust under the applicable NAT-policy.

Parameters

segment-size

Specifies the value to put into the TCP Maximum Segment Size (MSS) option if not already present, or if the present value is higher.

Values

160 to 10240

Platforms

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

tcp-mss-adjust

Syntax

tcp-mss-adjust segment-size

no tcp-mss-adjust

Context

[Tree] (config>app-assure>group>aqp>entry>action tcp-mss-adjust)

Full Context

configure application-assurance group app-qos-policy entry action tcp-mss-adjust

Description

This command configures the value to adjust the TCP Maximum Segment Size (MSS) option. The no form of this command disables the segment size adjustment.

Default

no tcp-mss-adjust

Parameters

segment-size

Specifies the value to put into the TCP Maximum Segment Size (MSS) option if not already present, or if the present value is higher.

Values

160 to 10240

tcp-mss-adjust

Syntax

tcp-mss-adjust segment-size

no tcp-mss-adjust

Context

[Tree] (config>service>nat>firewall-policy tcp-mss-adjust)

[Tree] (config>service>nat>up-nat-policy tcp-mss-adjust)

[Tree] (config>service>nat>nat-policy tcp-mss-adjust)

Full Context

configure service nat firewall-policy tcp-mss-adjust

configure service nat up-nat-policy tcp-mss-adjust

configure service nat nat-policy tcp-mss-adjust

Description

This command configures the value to adjust the TCP Maximum Segment Size (MSS) option.

The no form of the command returns the segment size to the default.

Default

no tcp-mss-adjust

Parameters

segment-size

Specifies the value to put into the TCP Maximum Segment Size (MSS) option if not already present, or if the present value is higher.

Values

160 to 10240

Platforms

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

  • configure service nat firewall-policy tcp-mss-adjust

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

  • configure service nat up-nat-policy tcp-mss-adjust
  • configure service nat nat-policy tcp-mss-adjust

tcp-mss-adjust

Syntax

tcp-mss-adjust

Context

[Tree] (config>filter>ip-filter>entry>action tcp-mss-adjust)

[Tree] (config>filter>ipv6-filter>entry>action tcp-mss-adjust)

Full Context

configure filter ip-filter entry action tcp-mss-adjust

configure filter ipv6-filter entry action tcp-mss-adjust

Description

This command activates the adjustment of the TCP Maximum Segment Size (MSS) option of TCP packets matching the entry.

Platforms

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

tcp-mss-adjust

Syntax

tcp-mss-adjust segment-size

no tcp-mss-adjust

Context

[Tree] (config>service>nat>map-domain tcp-mss-adjust)

Full Context

configure service nat map-domain tcp-mss-adjust

Description

This command enables the TCP maximum segment size (MSS) adjustments in a MAP domain. The TCP SYN and SYN-ACK packets are intercepted in both directions, and if their MSS value is larger than the one configured using this command, the MSS value in the packet is re-written (lowered) to the configured value. The end hosts use the lowest setting of the two hosts. The MSS value does not account for the IP or TCP header length.

If the MSS value in the SYN or SYN-ACK is not found, a new value is added and set to the configured value.

Default

no tcp-mss-adjust

Parameters

segment-size

Specifies the maximum size of the segment.

Values

160 to 8626

Platforms

VSR

tcp-ns

tcp-ns

Syntax

tcp-ns {true | false}

no tcp-ns

Context

[Tree] (config>filter>ipv6-filter>entry>match tcp-ns)

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

Full Context

configure filter ipv6-filter entry match tcp-ns

configure filter ip-filter entry match tcp-ns

Description

This command configures an IP filter match criterion based on the Nonce Sum (NS) TCP Flag bit, defined in RFC 3540, as being set or not in the TCP header of an IP packet.

The no form of the command removes the criterion from the match entry.

Default

no tcp-ns

Parameters

true

Specifies matching on IP packets that have the selected TCP flag bit set in the TCP header.

false

Specifies matching on IP packets that do not have the selected TCP flag bit set in the TCP header.

Platforms

All

tcp-optimizer

tcp-optimizer

Syntax

tcp-optimizer tcp-optimizer-name [create]

no tcp-optimizer tcp-optimizer-name

Context

[Tree] (config>app-assure>group tcp-optimizer)

Full Context

configure application-assurance group tcp-optimizer

Description

This command configures the TCP optimizer policy. When a TCP optimizer policy is removed or deleted, the existing flows using this policy are abandoned, and optimization is stopped. If, however, the TCP optimizer action is removed from a session-filter entry (in the config>app-assure>group>sess-fltr>entry action context), the existing flows are not affected.

The no form of this command removes the specified TCP optimizer policy.

Parameters

tcp-optimizer-name

Specifies the name of the TCP optimizer policy, up to 32characters.

create

This keyword is mandatory when creating a TCP optimizer policy.

Platforms

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

tcp-option-number

tcp-option-number

Syntax

tcp-option-number

Context

[Tree] (config>system>security>keychain tcp-option-number)

Full Context

configure system security keychain tcp-option-number

Description

Commands in this context configure the TCP option number to be placed in the TCP packet header.

Platforms

All

tcp-performance

tcp-performance

Syntax

tcp-performance

Context

[Tree] (config>app-assure>group>cflowd tcp-performance)

Full Context

configure application-assurance group cflowd tcp-performance

Description

Commands in this context configure Cflowd TCP performance export parameters.

Platforms

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

tcp-protocols

tcp-protocols

Syntax

tcp-protocols protocol-set

Context

[Tree] (config>app-assure>group>tether-detect>ttl-mon tcp-protocols)

Full Context

configure application-assurance group tethering-detection ttl-monitoring tcp-protocols

Description

This command configures whether AA analyzes all TCP traffic or only traffic from standard applications that generate consistent TTL values. Configuring AA to analyze all TCP traffic is typically recommended.

Default

tcp-protocols standard

Parameters

protocol-set

Specifies the scope of analysis for TCP traffic.

Values

standard, all

Platforms

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

tcp-psh

tcp-psh

Syntax

tcp-psh {true | false}

no tcp-psh

Context

[Tree] (config>filter>ipv6-filter>entry>match tcp-psh)

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

Full Context

configure filter ipv6-filter entry match tcp-psh

configure filter ip-filter entry match tcp-psh

Description

This command configures an IP filter match criterion based on the Push (PSH) TCP Flag bit, defined in RFC 793, as being set or not in the TCP header of an IP packet.

The no form of the command removes the criterion from the match entry.

Default

no tcp-psh

Parameters

true

Specifies matching on IP packets that have the selected TCP flag bit set in the TCP header.

false

Specifies matching on IP packets that do not have the selected TCP flag bit set in the TCP header.

Platforms

All

tcp-rst

tcp-rst

Syntax

tcp-rst [min minutes] [sec sec]

no tcp-rst

Context

[Tree] (config>service>nat>up-nat-policy>timeouts tcp-rst)

[Tree] (config>service>nat>nat-policy>timeouts tcp-rst)

[Tree] (config>service>nat>firewall-policy>timeouts tcp-rst)

Full Context

configure service nat up-nat-policy timeouts tcp-rst

configure service nat nat-policy timeouts tcp-rst

configure service nat firewall-policy timeouts tcp-rst

Description

This command suspends the use of the outside TCP ports that have been used in translations for TCP connections that are closed via TCP RST. Once this timer expires, the outside ports can be reused for new TCP translations.

The no form of the command reverts to the default.

Default

no tcp-rst

Parameters

minutes

Specifies the timeout, in minutes, after receiving a RST and closing the session before going to the LISTEN state again.

Values

1 to 4

sec

Specifies the timeout, in seconds, after receiving a RST and closing the session before going to the LISTEN state again.

Values

1 to 59

Platforms

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

  • configure service nat up-nat-policy timeouts tcp-rst
  • configure service nat nat-policy timeouts tcp-rst

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

  • configure service nat firewall-policy timeouts tcp-rst

tcp-rst

Syntax

tcp-rst {true | false}

no tcp-rst

Context

[Tree] (config>filter>ipv6-filter>entry>match tcp-rst)

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

Full Context

configure filter ipv6-filter entry match tcp-rst

configure filter ip-filter entry match tcp-rst

Description

This command configures an IP filter match criterion based on the Reset (RST) TCP Flag bit, defined in RFC 793, as being set or not in the TCP header of an IP packet.

The no form of the command removes the criterion from the match entry.

Default

no tcp-rst

Parameters

true

Specifies matching on IP packets that have the selected TCP flag bit set in the TCP header.

false

Specifies matching on IP packets that do not have the selected TCP flag bit set in the TCP header.

Platforms

All

tcp-session-parameters

tcp-session-parameters

Syntax

tcp-session-parameters

Context

[Tree] (config>router>ldp tcp-session-parameters)

Full Context

configure router ldp tcp-session-parameters

Description

Commands in this context configure parameters applicable to TCP transport session of an LDP session to remote peer.

Platforms

All

tcp-stack

tcp-stack

Syntax

tcp-stack tcp-stack-type

Context

[Tree] (config>app-assure>group>tcp-optimizer tcp-stack)

Full Context

configure application-assurance group tcp-optimizer tcp-stack

Description

This command configures the TCP stack used toward the subscriber.

Note:
  • The TCP stack used toward the core network is new-reno, and it is not configurable.

  • TCP BBR, TCP Illinois, and TCP Westwood implement a sender-side modification of the TCP congestion window algorithm that improves upon the performance of TCP Reno in wireless networks with lossy links.

The no form of this command reverts to the default.

Default

tcp-westwood

Parameters

tcp-stack-type

Specifies the TCP stack used toward the subscriber.

Values

tcp-bbr | tcp-illinois | tcp-new-reno | tcp-westwood

Platforms

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

tcp-syn

tcp-syn

Syntax

tcp-syn {true | false}

no tcp-syn

Context

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>ingr-ipv6>entry>match tcp-syn)

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>egr-ip>entry>match tcp-syn)

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>ingr-ip>entry>match tcp-syn)

[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>egr-ipv6>entry>match tcp-syn)

Full Context

configure subscriber-mgmt category-map category exhausted-credit-service-level ingress-ipv6-filter-entries entry match tcp-syn

configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ip-filter-entries entry match tcp-syn

configure subscriber-mgmt category-map category exhausted-credit-service-level ingress-ip-filter-entries entry match tcp-syn

configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ipv6-filter-entries entry match tcp-syn

Description

This command configures the TCP SYN match condition.

The no form of this command reverts to the default.

Parameters

true

Enables checking for the SYN bit.

false

Disables checking for the SYN bit.

Platforms

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

tcp-syn

Syntax

tcp-syn [hrs hours] [min minutes] [sec seconds]

no tcp-syn

Context

[Tree] (config>service>nat>nat-policy>timeouts tcp-syn)

[Tree] (config>service>nat>firewall-policy>timeouts tcp-syn)

[Tree] (config>service>nat>up-nat-policy>timeouts tcp-syn)

Full Context

configure service nat nat-policy timeouts tcp-syn

configure service nat firewall-policy timeouts tcp-syn

configure service nat up-nat-policy timeouts tcp-syn

Description

This command configures the timeout applied to a TCP session in the SYN state.

Default

tcp-syn sec 15

Parameters

hours

Specifies the timeout hours field.

Values

1 to 24

minutes

Specifies the timeout minutes field.

Values

1 to 59

seconds

Specifies the timeout seconds field.

Values

1 to 59

Platforms

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

  • configure service nat nat-policy timeouts tcp-syn
  • configure service nat up-nat-policy timeouts tcp-syn

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

  • configure service nat firewall-policy timeouts tcp-syn

tcp-syn

Syntax

tcp-syn {true | false}

no tcp-syn

Context

[Tree] (config>filter>ipv6-filter>entry>match tcp-syn)

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

Full Context

configure filter ipv6-filter entry match tcp-syn

configure filter ip-filter entry match tcp-syn

Description

This command configures an IP filter match criterion based on the Synchronize (SYN) TCP Flag bit, defined in RFC 793, as being set or not in the TCP header of an IP packet.

The no form of the command removes the criterion from the match entry.

Default

no tcp-syn

Parameters

true

Specifies matching on IP packets that have the selected TCP flag bit set in the TCP header.

false

Specifies matching on IP packets that do not have the selected TCP flag bit set in the TCP header.

Platforms

All

tcp-syn

Syntax

tcp-syn {true | false}

no tcp-syn

Context

[Tree] (cfg>sys>sec>cpm>ipv6-filter>entry>match tcp-syn)

[Tree] (cfg>sys>sec>cpm>ip-filter>entry>match tcp-syn)

Full Context

configure system security cpm-filter ipv6-filter entry match tcp-syn

configure system security cpm-filter ip-filter entry match tcp-syn

Description

This command configures matching on the SYN bit being set or reset in the control bits of the TCP header of an IP or IPv6 packet as an IP filter match criterion.

Note:

An entry containing Layer 4 match criteria will not match non-initial (2nd, 3rd, etc) fragments of a fragmented packet since only the first fragment contains the Layer 4 information.

The SYN bit is normally set when the source of the packet wants to initiate a TCP session with the specified destination IP or IPv6 address.

The no form of this command removes the criterion from the match entry.

Default

no tcp-syn

Parameters

true

Specifies matching on IP or IPv6 packets that have the SYN bit set in the control bits of the TCP header.

false

Specifies matching on IP or IPv6 packets that do not have the SYN bit set in the control bits of the TCP header.

Platforms

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

tcp-time-wait

tcp-time-wait

Syntax

tcp-time-wait [min minutes] [sec seconds]

no tcp-time-wait

Context

[Tree] (config>service>nat>nat-policy>timeouts tcp-time-wait)

[Tree] (config>service>nat>firewall-policy>timeouts tcp-time-wait)

[Tree] (config>service>nat>up-nat-policy>timeouts tcp-time-wait)

Full Context

configure service nat nat-policy timeouts tcp-time-wait

configure service nat firewall-policy timeouts tcp-time-wait

configure service nat up-nat-policy timeouts tcp-time-wait

Description

This command configures the timeout applied to a TCP session in a time-wait state.

Default

no tcp-time-wait

Parameters

minutes

Specifies the timeout minutes field.

Values

1 to 4

seconds

Specifies the timeout seconds field.

Values

1 to 59

Platforms

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

  • configure service nat up-nat-policy timeouts tcp-time-wait
  • configure service nat nat-policy timeouts tcp-time-wait

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

  • configure service nat firewall-policy timeouts tcp-time-wait

tcp-transitory

tcp-transitory

Syntax

tcp-transitory [hrs hours] [min minutes] [sec seconds]

no tcp-transitory

Context

[Tree] (config>service>nat>up-nat-policy>timeouts tcp-transitory)

[Tree] (config>service>nat>nat-policy>timeouts tcp-transitory)

[Tree] (config>service>nat>firewall-policy>timeouts tcp-transitory)

Full Context

configure service nat up-nat-policy timeouts tcp-transitory

configure service nat nat-policy timeouts tcp-transitory

configure service nat firewall-policy timeouts tcp-transitory

Description

This command configures the idle timeout applied to a TCP session in a transitory state.

Default

tcp-transitory min 4

Parameters

hours

Specifies the timeout hours field.

Values

1 to 24

minutes

Specifies the timeout minutes field.

Values

1 to 59

seconds

Specifies the timeout seconds field.

Values

1 to 59

Platforms

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

  • configure service nat nat-policy timeouts tcp-transitory
  • configure service nat up-nat-policy timeouts tcp-transitory

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

  • configure service nat firewall-policy timeouts tcp-transitory

tcp-urg

tcp-urg

Syntax

tcp-urg {true | false}

no tcp-urg

Context

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

[Tree] (config>filter>ipv6-filter>entry>match tcp-urg)

Full Context

configure filter ip-filter entry match tcp-urg

configure filter ipv6-filter entry match tcp-urg

Description

This command configures an IP filter match criterion based on the Urgent (URG) TCP Flag bit, defined in RFC 793, as being set or not in the TCP header of an IP packet.

The no form of the command removes the criterion from the match entry.

Default

no tcp-urg

Parameters

true

Specifies matching on IP packets that have the selected TCP flag bit set in the TCP header.

false

Specifies matching on IP packets that do not have the selected TCP flag bit set in the TCP header.

Platforms

All

tcp-validate

tcp-validate

Syntax

tcp-validate tcp-validate-name

no tcp-validate

Context

[Tree] (config>app-assure>group>policy>aqp>entry>action tcp-validate)

Full Context

configure application-assurance group policy app-qos-policy entry action tcp-validate

Description

This command assigns an existing TCP validation policy as an action on flows matching this AQP entry.

tcp-validate can only be called from AQP entries that:

  • have no matching conditions that relate to information extracted from the incoming IP packets; for example, no application or IP address.

  • allow the following match conditions:

    • none

    • aa-sub

    • characteristic

    • traffic-direction (both only)

      traffic-direction cannot be unidirectional (from or to sub). It can either be set to both or left unspecified.

The no form of this command removes the TCP validation policy action from flows matching this AQP entry.

Default

no tcp-validate

Parameters

tcp-validate-name

Specifies the name of the TCP validation policy for this application assurance profile. The TCP validation policy is configured using the config>app-assure>group>tcp-validate tcp-validate-name command.

Platforms

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

tcp-validate

Syntax

tcp-validate tcp-validate-name direction direction [create]

no tcp-validate tcp-validate-name direction direction

Context

[Tree] (config>app-assure>group>statistics>tca tcp-validate)

Full Context

configure application-assurance group statistics threshold-crossing-alert tcp-validate

Description

This command configures TCA for the counter, and enables the capture of drop or admit events due to the specified TCP validation function.

Parameters

tcp-validate-name

Specifies the name of the TCP validation policy up to 32 characters.

direction

Specifies the traffic direction in relation to the AA subscriber.

Values

from-sub, to-sub

create

This keyword is mandatory when creating a TCA instance.

Platforms

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

tcp-validate

Syntax

tcp-validate tcp-validate-name [create]

no tcp-validate tcp-validate-name

Context

[Tree] (config>app-assure>group tcp-validate)

Full Context

configure application-assurance group tcp-validate

Description

This command configures a TCP validation policy.

The no form of this command removes the specified TCP validation policy.

Default

no tcp-validate

Parameters

tcp-validate-name

Specifies the name of the TCP validation policy up to 32 characters.

create

This keyword is mandatory when creating a TCP validation policy.

Platforms

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

tcp-validate-stats

tcp-validate-stats

Syntax

[no] tcp-validate-stats

Context

[Tree] (config>app-assure>group>statistics>aa-admit-deny tcp-validate-stats)

Full Context

configure application-assurance group statistics aa-admit-deny tcp-validate-stats

Description

This command configures whether to include or exclude TCP validation admit-deny statistics in accounting records.

Default

no tcp-validate-stats

Platforms

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

tdcm

tdcm

Syntax

tdcm

Context

[Tree] (config>port>dwdm tdcm)

Full Context

configure port dwdm tdcm

Description

This command configures the Tunable Dispersion Compensation Module parameters.

Platforms

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

tdm

tdm

Syntax

tdm

Context

[Tree] (config>port tdm)

Full Context

configure port tdm

Description

Commands in this context configure DS-1/E-1 and DS-3/E-3 parameters for a port on a channelized MDA T1/E1. This context cannot be accessed on non-channelized MDAs.

TDM is a mechanism to divide the bandwidth of a stream into separate channels or time slots by assigning each stream a different time slot in a set. TDM repeatedly transmits a fixed sequence of time slots over a single transmission channel. Each individual data stream is reassembled at the receiving end based on the timing.

Platforms

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

tdm-sat

tdm-sat

Syntax

tdm-sat sat-id [create]

no tdm-sat sat-id

Context

[Tree] (config>system>satellite tdm-sat)

Full Context

configure system satellite tdm-sat

Description

Commands in this context configure the specified TDM satellite.

The no form of the command deletes the specified TDM satellite.

Parameters

sat-id

Specifies the satellite ID for the associated TDM satellite.

Values

1 to 20

create

The keyword used to create a new TDM satellite context. The create keyword requirement can be enabled/disabled in the environment>create context.

Platforms

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

te

te

Syntax

[no] te

Context

[Tree] (debug>router>mpls>event te)

Full Context

debug router mpls event te

Description

This command debugs te events.

The no form of the command disables the debugging.

Platforms

All

te-class

te-class

Syntax

te-class te-class-number class-type ct-number priority priority

no te-class te-class-number

Context

[Tree] (config>router>rsvp>diffserv-te te-class)

Full Context

configure router rsvp diffserv-te te-class

Description

This command configures a TE class. A TE class is defined as:

TE Class = {Class Type (CT), LSP priority}

Eight TE classes are supported. There is no default TE class once Diff-Serv is enabled. The user has to explicitly define each TE class.

When Diff-Serv is disabled, there will be an internal use of the default CT (CT0) and eight pre-emption priorities as shown in Default Class Type.

Table 1. Default Class Type

Class Type (CT internal)

LSP Priority

0

7

0

6

0

5

0

4

0

3

0

2

0

1

0

0

The no form of this command deletes the TE class.

Parameters

te-class te-class-number

Specifies the TE class number.

Values

0 to 7

class-type ct-number

Specifies the Diff-Serv Class Type number. One or more system forwarding classes can be mapped to a CT.

Values

0 to 7

priority priority

Specifies the LSP priority.

Values

0 to 7

Platforms

All

te-down-threshold

te-down-threshold

Syntax

te-down-threshold threshold-level [threshold-level]

no te-down-threshold

Context

[Tree] (config>router>rsvp>interface te-down-threshold)

[Tree] (config>router>rsvp te-down-threshold)

Full Context

configure router rsvp interface te-down-threshold

configure router rsvp te-down-threshold

Description

This command configures the specific threshold levels per node and per interface. Threshold levels are for reserved bandwidth per interface. The te-threshold-update command is used to enable or disable threshold-based IGP TE updates. Any reserved bandwidth change per interface is compared with all the threshold levels and trigger an IGP TE update if a defined threshold level is crossed in either direction (LSP setup or teardown). Threshold-based updates must be supported with both ISIS and OSPF. A minimum of one and a maximum of 16 threshold levels is supported.

Threshold levels configured per node is inherited by all configured RSVP interfaces. Threshold levels defined under the RSVP interface is used to trigger IGP updates if non-default threshold levels are configured.

The no form of this command resets te-down-threshold to its default value.

Default

no te-down-threshold (equals following values 100 99 98 97 96 95 90 85 80 75 60 45 30 15 0)

Parameters

threshold-level

Specifies the threshold level.

Values

0 to 100

Platforms

All

te-metric

te-metric

Syntax

te-metric value

no te-metric

Context

[Tree] (config>router>mpls>interface te-metric)

Full Context

configure router mpls interface te-metric

Description

This command configures the TE metric used on the interface. This metric is in addition to the interface metric used by IGP for the shortest path computation.

This metric is flooded as part of the TE parameters for the interface using an opaque LSA or an LSP. The IS-IS TE metric is encoded as sub-TLV 18 as part of the extended IS reachability TLV. The metric value is encoded as a 24-bit unsigned integer. The OSPF TE metric is encoded as a sub-TLV Type 5 in the Link TLV. The metric value is encoded as a 32-bit unsigned integer.

When the use of the TE metric is enabled for an LSP, CSPF will first prune all links in the network topology which do not meet the constraints specified for the LSP path. Such constraints include bandwidth, admin-groups, and hop limit. Then, CSPF will run an SPF on the remaining links. The shortest path among the all SPF paths will be selected based on the TE metric instead of the IGP metric which is used by default.

The TE metric in CSPF LSP path computation can be configured by entering the command config>router>mpls>lsp>metric-type te.

Note that the TE metric is only used in CSPF computations for MPLS paths and not in the regular SPF computation for IP reachability.

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

Default

no te-metric

The value of the IGP metric is advertised in the TE metric sub-TLV by IS-IS and OSPF.

Parameters

value

Specifies the metric value.

Values

1 to 16777215

Platforms

All

te-threshold-update

te-threshold-update

Syntax

[no] te-threshold-update

Context

[Tree] (config>router>rsvp te-threshold-update)

Full Context

configure router rsvp te-threshold-update

Description

This command is used to control threshold-based IGP TE updates. The te-threshold-update command must enable IGP TE update based only on bandwidth reservation thresholds per interface and must block IGP TE update on bandwidth changes for each reservation. Threshold levels can be defined using the te-up-threshold and te-down-threshold commands at the global RSVP or per-interface level.

The no form of this command should reset te-threshold-update to the default value and disable threshold based update.

Default

no te-threshold-update

Platforms

All

te-threshold-update

Syntax

te-threshold-update

no te-threshold-update

Context

[Tree] (debug>router>rsvp>event te-threshold-update)

[Tree] (debug>router>rsvp>interface>event te-threshold-update)

Full Context

debug router rsvp event te-threshold-update

debug router rsvp interface event te-threshold-update

Description

This command debugs the TE threshold update and the dark bandwidth threshold events.

The no form of this command disables the debugging.

Platforms

All

te-up-threshold

te-up-threshold

Syntax

te-up-threshold threshold-level [threshold-level]

no te-up-threshold

Context

[Tree] (config>router>rsvp te-up-threshold)

[Tree] (config>router>rsvp>interface te-up-threshold)

Full Context

configure router rsvp te-up-threshold

configure router rsvp interface te-up-threshold

Description

This command configures the specific threshold levels per node and per interface. Threshold levels are for reserved bandwidth per interface. The te-threshold-update command is used to enable or disable threshold-based IGP TE updates. Any reserved bandwidth change per interface is compared with all the threshold levels and trigger an IGP TE update if a defined threshold level is crossed in either direction (LSP setup or teardown). Threshold-based updates must be supported with both ISIS and OSPF. A minimum of one and a maximum of 16 threshold levels must be supported.

Threshold levels configured per node is inherited by all configured RSVP interfaces. Threshold levels defined under the RSVP interface is used to trigger IGP updates if non-default threshold levels are configured.

The no form of this command resets te-up-threshold to its default value.

Default

no te-up-threshold (equals values of 0 15 30 45 60 75 80 85 90 95 96 97 98 99 100)

Parameters

threshold-level

Specifies the threshold level.

Values

0 to 100

Platforms

All

tech-support

tech-support

Syntax

tech-support [file-url]

Context

[Tree] (admin>satellite>eth-sat tech-support)

[Tree] (admin tech-support)

Full Context

admin satellite eth-sat tech-support

admin tech-support

Description

This command creates a system core dump. If the file-url is omitted, and a ts-location is defined, then the tech support file will have an automatic SR OS generated file name based on the system name and the date and time and will be saved to the directory indicated by the configured ts-location.

The format of the auto-generated filename is ts-XXXXX.YYYYMMDD.HHMMUTC.dat where:

  • XXXXX: system name with special characters expanded to avoid problems with file systems (for example, a '.' is expanded to %2E.)

  • YYYYMMDD: Date with leading zeros on year, month and day

  • HHMM: Hours and Minutes in UTC time (24hr format, always 4 chars, with leading zeros on hours and minutes)

Note:

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

Parameters

file-url

Specifies the file URL location to save the binary file.

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:// | tftp://}login:pswd@remote-locn/][file-path]

199 chars max

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

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

  • admin satellite eth-sat tech-support

All

  • admin tech-support

tei-set

tei-set

Syntax

[no] tei-set

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>source-override>video>analyzer>alarms tei-set)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>video>analyzer>alarms tei-set)

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>video>analyzer>alarms tei-set)

Full Context

configure mcast-management multicast-info-policy bundle channel source-override video analyzer alarms tei-set

configure mcast-management multicast-info-policy bundle video analyzer alarms tei-set

configure mcast-management multicast-info-policy bundle channel video analyzer alarms tei-set

Description

This command configures the analyzer to check for TEI set errors.

Default

no tei-set

Platforms

7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

teid-load-balancing

teid-load-balancing

Syntax

[no] teid-load-balancing

Context

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

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

Full Context

configure service template vpls-template load-balancing teid-load-balancing

configure service vpls load-balancing teid-load-balancing

Description

This command enables inclusion of TEID in hashing for GTP-U/C encapsulates traffic for GTPv1/GTPv2. The no form of this command ignores TEID in hashing.

Default

no teid-load-balancing

Platforms

All

teid-load-balancing

Syntax

[no] teid-load-balancing

Context

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

Full Context

configure service ies interface load-balancing teid-load-balancing

Description

This command enables inclusion of TEID in hashing for GTP-U/C encapsulates traffic for GTPv1/GTPv2. The no form of this command ignores TEID in hashing.

Default

no teid-load-balancing

Platforms

All

teid-load-balancing

Syntax

[no] teid-load-balancing

Context

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

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

Full Context

configure service vprn network-interface load-balancing teid-load-balancing

configure service vprn interface load-balancing teid-load-balancing

Description

This command enables inclusion of TEID in hashing for GTP-U/C encapsulates traffic for GTPv1/GTPv2.

The no form of this command ignores TEID in hashing.

Default

no teid-load-balancing

Platforms

All

teid-load-balancing

Syntax

[no] teid-load-balancing

Context

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

Full Context

configure router interface load-balancing teid-load-balancing

Description

This command enables inclusion of TEID in hashing for GTP-U/C encapsulates traffic for GTPv1/GTPv2. The no form of this command ignores TEID in hashing.

Default

no teid-load-balancing

Platforms

All

teidc-change

teidc-change

Syntax

[no] teidc-change

Context

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

Full Context

configure subscriber-mgmt radius-accounting-policy triggered-updates gtp-change teidc-change

Description

This command configures the router to send an interim accounting update when GTP-C TEIDs are changed.

Note: Changes to GTP-C TEIDs typically indicate an MME change.

The no form of the command configures the router not to send an interim accounting update when GTP-C TEIDs are changed.

Default

no teidc-change

Platforms

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

teidu-change

teidu-change

Syntax

[no] teidu-change

Context

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

Full Context

configure subscriber-mgmt radius-accounting-policy triggered-updates gtp-change teidu-change

Description

This command configures the router to send an interim accounting update when GTP-U TEIDs are changed. This update typically happens during mobility, idling, or service request procedures.

The no form of the command configures the router not to send an interim accounting update when GTP-U TEIDs are changed.

Default

no teidu-change

Platforms

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

telemetry

telemetry

Syntax

telemetry

Context

[Tree] (config>system telemetry)

[Tree] (admin>system telemetry)

Full Context

configure system telemetry

admin system telemetry

Description

Commands in this context configure the dial-out telemetry commands.

Platforms

All

telemetry-data

telemetry-data

Syntax

[no] telemetry-data

Context

[Tree] (config>system>security>management-interface>output-authorization telemetry-data)

Full Context

configure system security management-interface output-authorization telemetry-data

Description

This command controls output authorization of telemetry configuration and state data in gNMI Subscribe RPC responses.

When enabled, telemetry data output authorization is performed, which may significantly increase the system response time with command authorization requests, especially when remote AAA servers are used.

By default, authorization checks are not performed for telemetry data.

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

Default

no telemetry-data

Platforms

All

telnet

telnet

Syntax

telnet {ip-address | dns-name} [port] service-name service-name [source ip-address]

telnet {ip-address | dns-name} [port] [router router-instance] [source ip-address]

Context

[Tree] (telnet)

Full Context

telnet

Description

This command opens a Telnet session to a remote host. In SR-series networks, the Telnet servers limit Telnet clients to three login attempts; if unsuccessful, the Telnet client session is disconnected. The number is not user configurable.

If a source address is specified, it is used for the source IP address in the originated IP packets for the Telnet session.

Parameters

ip-address

Specifies the IP address or the DNS name (if DNS name resolution is configured).

Values

ipv4-address

a.b.c.d

ipv6-address

x:x:x:x:x:x:x:x[-interface]

x:x:x:x:x:x:d.d.d.d[-interface]

x: [0 to FFFF]H

d: [0 to 255]D ipv6-address

interface: up to 32 characters, mandatory for link local addresses

dns-name

up to 128 characters

Note:

IPv6 applies to the 7750 SR and 7950 XRS.

dns-name

Specifies the DNS name (if DNS name resolution is configured), up to 128 characters.

port

Specifies the TCP port number to use Telnet to the remote host, expressed as a decimal integer.

Values

1 to 65535

Default

23

router-instance

Specifies the router name or service ID used to identify the router instance.

Values

router-instance: router-name or vprn-svc-id

router-name

"Base”, "management”, vpls-management”

vprn-svc-id

1 to 2147483647

Default

Base

service-name

Specifies the service name, up to 64 characters.

source ip-address

Specifies the source IP address to use as the source of the Telnet packets.

Values

ipv4-address:

a.b.c.d

ipv6-address:

x:x:x:x:x:x:x:x

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

x:

[0 to FFFF]H

d:

[0 to 255]

Platforms

All

telnet

Syntax

telnet

Context

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

Full Context

configure system login-control telnet

Description

This command creates the context to configure the Telnet login control parameters.

Platforms

All

telnet-max-sessions

telnet-max-sessions

Syntax

telnet-max-sessions number-of-sessions

no telnet-max-sessions

Context

[Tree] (config>system>security>profile telnet-max-sessions)

[Tree] (config>system>security>cli-session-group telnet-max-sessions)

Full Context

configure system security profile telnet-max-sessions

configure system security cli-session-group telnet-max-sessions

Description

This command is used to limit the number of Telnet-based CLI sessions available to all users that are part of a particular profile, or to all users of all profiles that are part of the same cli-session-group.

The no form of this command disables the command and the profile/group limit is not applied on the number of sessions.

Default

no telnet-max-sessions

Parameters

number-of-sessions

Specifies the maximum number of allowed Telnet-based CLI sessions.

Values

0 to 50

Platforms

All

telnet-reply

telnet-reply

Syntax

[no] telnet-reply

Context

[Tree] (config>service>ies>if>ipv6>vrrp telnet-reply)

Full Context

configure service ies interface ipv6 vrrp telnet-reply

Description

This command enables the non-owner master to reply to TCP port 23 Telnet requests directed at the virtual router instances IP addresses. The Telnet request can be received on any routed interface. Telnet must not have been disabled at the management security level (either on the parental IP interface or based on the Telnet source host address). Proper login and CLI command authentication is still enforced.

When telnet-reply is not enabled, TCP port 23 Telnet packets to non-owner master virtual IP addresses are silently discarded.

Non-owner backup virtual routers never respond to Telnet requests regardless of the telnet-reply configuration.

The telnet-reply command is only available in non-owner VRRP nodal context. If the telnet-reply command is not executed, Telnet packets to the virtual router instance IP addresses will be silently discarded.

The no form of this command restores the default operation of discarding all Telnet packets destined to the non-owner virtual router instance IP addresses.

Default

no telnet-reply

Platforms

All

telnet-reply

Syntax

[no] telnet-reply

Context

[Tree] (config>service>ies>if>vrrp telnet-reply)

Full Context

configure service ies interface vrrp telnet-reply

Description

The telnet-reply command enables the non-owner master to reply to TCP port 23 Telnet Requests directed at the virtual router instances IP addresses. The Telnet request can be received on any routed interface. Telnet must not have been disabled at the management security level (either on the parental IP interface or based on the Telnet source host address). Proper login and CLI command authentication is still enforced.

When telnet-reply is not enabled, TCP port 23 Telnet packets to non-owner master virtual IP addresses are silently discarded.

Non-owner backup virtual routers never respond to Telnet Requests regardless of the telnet-reply configuration.

The telnet-reply command is only available in non-owner VRRP nodal context. If the telnet-reply command is not executed, Telnet packets to the virtual router instance IP addresses will be silently discarded.

The no form of this command restores the default operation of discarding all Telnet packets destined to the non-owner virtual router instance IP addresses.

Default

no telnet-reply

Platforms

All

telnet-reply

Syntax

[no] telnet-reply

Context

[Tree] (config>service>vprn>if>ipv6>vrrp telnet-reply)

[Tree] (config>service>vprn>if>vrrp telnet-reply)

Full Context

configure service vprn interface ipv6 vrrp telnet-reply

configure service vprn interface vrrp telnet-reply

Description

This command enables the non-owner master to reply to TCP port 23 Telnet Requests directed at the virtual router instance’s IP addresses. The Telnet request can be received on any routed interface. Telnet must not have been disabled at the management security level (either on the parental IP interface or based on the Telnet source host address). Proper login and CLI command authentication is still enforced.

When telnet-reply is not enabled, TCP port 23 Telnet packets to non-owner master virtual IP addresses are silently discarded.

Non-owner backup virtual routers never respond to Telnet Requests regardless of the telnet-reply configuration.

The telnet-reply command is only available in non-owner VRRP nodal context. If the telnet-reply command is not executed, Telnet packets to the virtual router instance IP addresses will be silently discarded.

The no form of this command restores the default operation of discarding all Telnet packets destined to the non-owner virtual router instance IP addresses.

Default

no telnet-reply

Platforms

All

telnet-reply

Syntax

[no] telnet-reply

Context

[Tree] (config>router>if>ipv6>vrrp telnet-reply)

[Tree] (config>router>if>vrrp telnet-reply)

Full Context

configure router interface ipv6 vrrp telnet-reply

configure router interface vrrp telnet-reply

Description

This command enables the non-owner master to reply to TCP port 23 Telnet requests directed at the virtual router instances’ IP addresses.

Non-owner virtual router instances are limited by the VRRP specifications to responding to ARP requests destined to the virtual router IP addresses and routing IP packets not addressed to the virtual router IP addresses. Many network administrators find this limitation frustrating when troubleshooting VRRP connectivity issues.

This limitation can be disregarded for certain applications. Ping, SSH and Telnet can each be individually enabled or disabled on a per-virtual-router-instance basis.

The telnet-reply command enables the non-owner master to reply to Telnet requests directed at the virtual router instances’ IP addresses. The Telnet request can be received on any routed interface. Telnet must not have been disabled at the management security level (either on the parental IP interface or based on the Telnet source host address). Correct login and CLI command authentication is still enforced.

When telnet-reply is not enabled, Telnet requests to non-owner master virtual IP addresses are silently discarded.

Non-owner backup virtual routers never respond to Telnet requests regardless of the telnet-reply setting.

The telnet-reply command is only available in non-owner vrrp nodal context.

By default, Telnet requests to the virtual router instance IP addresses will be silently discarded.

The no form of the command configures discarding all Telnet request messages destined to the non-owner virtual router instance IP addresses.

Default

no telnet-reply — Telnet requests to the virtual router instance IP addresses are discarded.

Platforms

All

telnet-server

telnet-server

Syntax

[no] telnet-server

Context

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

Full Context

configure system security telnet-server

Description

This command enables Telnet servers running on the system.

Telnet servers are shut down by default. At system startup, only SSH servers are enabled.

Telnet servers in networks limit a Telnet clients to three retries to login. The Telnet server disconnects the Telnet client session after three retries.

The no form of this command disables Telnet servers running on the system.

Platforms

All

telnet6-server

telnet6-server

Syntax

[no] telnet6-server

Context

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

Full Context

configure system security telnet6-server

Description

This command enables Telnet IPv6 servers running on the system and only applies to the 7750 SR and 7950 XRS.

Telnet servers are shut down by default. At system startup, only SSH servers are enabled.

The no form of this command disables Telnet IPv6 servers running on the system.

Platforms

All

temp-flooding

temp-flooding

Syntax

temp-flooding flood-time

no temp-flooding

Context

[Tree] (config>service>vpls temp-flooding)

[Tree] (config>service>template>vpls-template temp-flooding)

Full Context

configure service vpls temp-flooding

configure service template vpls-template temp-flooding

Description

The temporary flooding is designed to minimize failover times by eliminating the time it takes to flush the MAC tables and if MVRP is enabled the time it takes for MVRP registration. Temporary flooding is initiated only upon xSTP TCN reception. During this procedure while the MAC flush takes place the frames received on one of the VPLS SAPs/pseudowires are flooded in a VPLS context which for MVRP case includes also the unregistered MVRP trunk ports. The MAC Flush action is initiated by the STP TCN reception or if MVRP is enabled for the data VPLS, by the reception of a MVRP New message for the SVLAN ID associated with the data VPLS. As soon as the MAC Flush is done, regardless of whether the temp-flooding timer expired or not, traffic will be delivered according to the regular FDB content which may be built from MAC Learning or based on MVRP registrations. This command provides a flood-time value that configures a fixed amount of time, in seconds, during which all traffic is flooded (BUM or known unicast) as a safety mechanism. Once the flood-time expires, traffic will be delivered according to the regular FDB content which may be built from MAC Learning or based on MVRP registrations. The temporary flooding timer should be configured in such a way to allow auxiliary processes like MAC Flush, MMRP and/or MVRP to complete/converge. The temporary flooding behavior applies to regular VPLS, VPLS instantiated with VPLS-template, IVPLS and BVPLS when MMRP is disabled.

The no form of this command disables the temporary flooding behavior.

Default

no temp-flooding

Parameters

flood-time

Specifies the flood time, in seconds

Values

3 to 600

Platforms

All

template

template

Syntax

template

Context

[Tree] (config>service template)

Full Context

configure service template

Description

This is the node for service templates.

Platforms

All

template

Syntax

template

Context

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

[Tree] (config>app-assure>group>cflowd>comp template)

[Tree] (config>app-assure>group>cflowd>tcp-perf template)

Full Context

configure application-assurance group cflowd volume template

configure application-assurance group cflowd comprehensive template

configure application-assurance group cflowd tcp-performance template

Description

Commands in this context configure the template for cflowd comprehensive, TCP performance, or volume fields.

Platforms

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

template

Syntax

template template-id

no template

Context

[Tree] (config>app-assure>group>http-error-redirect template)

[Tree] (config>app-assure>group template)

Full Context

configure application-assurance group http-error-redirect template

configure application-assurance group template

Description

This command refers to the template of parameters passed from the AA-ISA to the redirect server via JavaScript in the redirect packet. The template is specific to the redirect server being used in the network.

Currently, two partners are used and tested with AA-ISA redirect solution, Barefruit and Xerocole.

The no form of this command reverts to the default.

Parameters

template-id

Specifies an HTTP error redirect template.

1 = Barefruit specific template

2 = xerocole specific template.

Values

0 to 4294967295

Platforms

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

template

Syntax

template value

no template

Context

[Tree] (config>app-assure>group>http-notif template)

Full Context

configure application-assurance group http-notification template

Description

This command configures the template which defines the format and parameters included in the http notification message.

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

Default

no template

Parameters

value

Specifies the template id of this HTTP Notification.

Values

1 — Javascript-url with SubID and optional Http-Url-Param

2 — Javascript-url and optional Http-Url-Param

Platforms

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

template

Syntax

template template-id

no template

Context

[Tree] (config>app-assure>group>http-redirect template)

Full Context

configure application-assurance group http-redirect template

Description

This command configures the template that defines which parameters are appended to the HTTP host redirect field in the redirect message.

The HTTP redirect template provides HTTP 302 redirect containing only the URL specified in the redirect policy, with no other parameters.

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

Default

no template

Parameters

template-id

Specifies the HTTP Policy Redirect template.

Values

1 — Javascript based redirect embedded in HTTP 200 OK response with a predefined number of arguments automatically appended to the redirect URL

2 — HTTP 302 Redirect with a predefined number of arguments automatically appended to the redirect URL.

3 — HTTP 302 Redirect with no parameters appended to the URL (empty).

4 — Empty Redirect format using Javascript.

5 — Redirect supporting macro substitution using HTTP 302.

6 — Redirect supporting macro substitution using Javascript.

Platforms

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

template

Syntax

[no] template template-name

Context

[Tree] (config>router>bier template)

Full Context

configure router bier template

Description

This command creates a BIER template to be assigned to IGP.

The no form of this command removes a specific template.

Parameters

template-name

The name of the template to be created or removed, up to 32 characters.

Platforms

All

template

Syntax

[no] template name

Context

[Tree] (config>router>route-next-hop-policy template)

Full Context

configure router route-next-hop-policy template

Description

This command creates a template to configure the attributes of a Loop-Free Alternate (LFA) Shortest Path First (SPF) policy. An LFA SPF policy allows the user to apply specific criteria, such as admin group and SRLG constraints, to the selection of an LFA backup next-hop for a subset of prefixes that resolve to a specific primary next-hop.

The user first creates a route next-hop policy template under the global router context and then applies it to a specific OSPF or IS-IS interface in the global routing instance or in a VPRN instance.

A policy template can be used in both IS-IS and OSPF to apply the specific criteria to prefixes protected by LFA. Each instance of IS-IS or OSPF can apply the same policy template to one or more interface.

The commands within the route next-hop policy template use the begin-commit-abort model. The following are the steps to create and modify the template:

To create a template, the user enters the name of the new template directly under the route-next-hop-policy context.

  1. To delete a template that is not in use, the user enters the no form for the template name under the route-next-hop-policy context.

  2. The user enters the editing mode by executing the begin command under the route-next-hop-policy context. The user can then edit and change any number of route next-hop policy templates. However, the parameter value will still be stored temporarily in the template module until the commit is executed under the route-next-hop-policy context. Any temporary parameter changes will be lost if the user enters the abort command before the commit command.

  3. The user is allowed to create or delete a template instantly once in the editing mode without the need to enter the commit command. Furthermore, the abort command, if entered, will have no effect on the prior deletion or creation of a template.

Once the commit command is issued, IS-IS or OSPF will re-evaluate the templates and if there are any net changes, it will schedule a new LFA SPF to re-compute the LFA next-hop for the prefixes associated with these templates.

Parameters

name

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

Platforms

All

template

Syntax

template template-name

no template

Context

[Tree] (config>router>isis>level>bier template)

Full Context

configure router isis level bier template

Description

This command assigns a BIER template to an IS-IS level.

The no form of this command removes templates from the IS-IS level.

Parameters

template-name

Specifies the BIER template name.

Platforms

All

template

Syntax

template template-name

no template

Context

[Tree] (config>router>ospf>area>bier template)

Full Context

configure router ospf area bier template

Description

This command configures an OSPF BIER template at the OSPF area level.

The no form of this command removes templates from the OSPF area.

Parameters

template-name

The name of the template, up to 32 characters.

Platforms

All

template-format

template-format

Syntax

template-format {format1 | format2}

no template-format

Context

[Tree] (config>service>ipfix>ipfix-export-policy template-format)

Full Context

configure service ipfix ipfix-export-policy template-format

Description

This command selects one of two template formats that contains a set of element IDs and their interpretation in IPFIX NAT flow logging. The difference between the two formats is related to the fields conveying information about the translated source IP addresses and ports (outside IP addresses and ports). Further, format 1 conveys information about the translated source port (post NAT) in the sourceTransportPort information element while format 2 conveys this information in the postNAPTsourceTrasportPort element.

Further, format1 conveys information about the translated source port (post NAT) in the information element sourceTransportPort while a new information element postNAPTsourceTrasportPort is introduced in format2 to carry this information.

For more information about template formats, refer to "Template Formats” in the 7450 ESS, 7750 SR, and VSR Multiservice Integrated Service Adapter and Extended Services Appliance Guide, where the table lists supported information elements and their description for each format.

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

Default

template-format format1

Parameters

format1

Specifies that template format 1 is used by the IPFIX collectors associated with this IPFIX Export policy.

format2

Specifies that template format 2 is used by the IPFIX collectors associated with this IPFIX Export policy.

Platforms

All

template-refresh-timeout

template-refresh-timeout

Syntax

template-refresh-timeout [hrs hours] [min minutes] [sec seconds] [days days]

no template-refresh-timeout

Context

[Tree] (config>service>ipfix>export-policy>collector template-refresh-timeout)

Full Context

configure service ipfix ipfix-export-policy collector template-refresh-timeout

Description

This command configures the time interval in which Template Set messages are sent to the collector node. Template sets is an IPFIX message that defines fields for subsequent IPFIX messages but contains no data of its own. In other words, IPFIX data is not passed as set of TLVs, but instead data is encoded with a scheme defined through the Template Set message.

Default

template-refresh-timeout min 10

Parameters

hours

Specifies the time interval, in hours, after which IPFIX templates are resent to this collector.

Values

1 to 24

minutes

Specifies the time interval, in minutes, after which IPFIX templates are resent to this collector.

Values

1 to 59

seconds

Specifies the time interval, in seconds, after which IPFIX templates are resent to this collector.

Values

1 to 59

days

Specifies the time interval, in days, after which IPFIX templates are resent to this collector.

Values

1

Platforms

All

template-retransmit

template-retransmit

Syntax

template-retransmit seconds

no template-retransmit

Context

[Tree] (config>app-assure>group>cflowd template-retransmit)

Full Context

configure application-assurance group cflowd template-retransmit

Description

This command configures the period of time, in seconds, for the template to be retransmitted.

Default

template-retransmit 600

Parameters

seconds

Specifies the time period for the template to be retransmitted.

Values

10 to 600

Default

600

Platforms

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

template-retransmit

Syntax

template-retransmit seconds

no template-retransmit

Context

[Tree] (config>cflowd template-retransmit)

Full Context

configure cflowd template-retransmit

Description

This command specifies the interval for sending template definitions.

Default

template-retransmit 600

Parameters

seconds

Specifies the value expressed in seconds before sending template definitions.

Values

10 to 600

Platforms

All

template-set

template-set

Syntax

template-set {basic | mpls-ip | l2-ip | mpls-transport}

Context

[Tree] (config>cflowd>collector template-set)

Full Context

configure cflowd collector template-set

Description

This command specifies the set of templates sent to the collector when using cflowd Version 9 or Version 10.

Default

template-set basic

Parameters

basic

Specifies that basic flow data is sent.

mpls-ip

Specifies that extended flow data is sent that includes IP and MPLS flow information.

If the sampled traffic is part of a locally configured service or IPv4 or IPv6 traffic is being forwarded with an MPLS shortcut, then the MPLS labels associated with that service encapsulation are included in the extended flow data for both network ingress and egress sampling.

l2-ip

Specifies that extended flow data is sent that includes Layer 2 (Ethernet) and IP flow information. This template is only applicable for V10 (IPFIX) collectors.

mpls-transport

Specifies that cflowd can collect flow statistics for MPLS traffic using only the outer transport label, EXP bit value, and ingress interface as the flow identifier. This template enables the collection of flow statistics on a core router to develop LSP usage statistics.

Platforms

All

terminal

terminal

Syntax

terminal

no terminal

Context

[Tree] (environment terminal)

Full Context

environment terminal

Description

Commands in this context configure the terminal screen length for the current CLI session.

Platforms

All

termination-fpe

termination-fpe

Syntax

termination-fpe termination-fpe

no termination-fpe

Context

[Tree] (config>router>segment-routing>srv6>locator termination-fpe)

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

Full Context

configure router segment-routing segment-routing-v6 locator termination-fpe

configure router segment-routing segment-routing-v6 micro-segment block termination-fpe

Description

This command configures the association between the FPE ID and the locator for termination of SRv6 in local services. One or more FPEs can be configured for SRv6 termination, where a termination SRv6 FPE is assigned one or more configured locators or micro-segment locators.

The no form of this command removes the association.

Parameters

termination-fpe

Specifies the FPE ID for SRv6 termination.

Values

1 to 64

Platforms

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

tertiary

tertiary

Syntax

tertiary

Context

[Tree] (config>subscr-mgmt>sub-ident-pol tertiary)

Full Context

configure subscriber-mgmt sub-ident-policy tertiary

Description

Commands in this context configure tertiary identification script parameters.

Platforms

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

tertiary-config

tertiary-config

Syntax

tertiary-config file-url

no tertiary-config

Context

[Tree] (bof tertiary-config)

Full Context

bof tertiary-config

Description

This command specifies the name and location of the tertiary configuration file.

The system attempts to use the configuration specified in tertiary-config if both the primary and secondary config files cannot be located. If this file cannot be located, the system boots with the factory default configuration.

Note that if an error in the configuration file is encountered, the boot process aborts.

The no form of this command removes the tertiary-config configuration.

Parameters

file-url

Specifies the tertiary configuration file location, expressed as a file URL.

Values

file-url

{local-url | remote-url} (up to 180 characters)

local-url

[cflash-id/][file-path]

remote-url

[{ftp://| tftp://} login:pswd@remote-locn/][file-path]

cflash-id

cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

Platforms

All

tertiary-dns

tertiary-dns

Syntax

tertiary-dns ip-address

no tertiary-dns

Context

[Tree] (config>service>vprn>dns tertiary-dns)

Full Context

configure service vprn dns tertiary-dns

Description

This command configures the tertiary DNS server for DNS name resolution. The tertiary DNS server is used only if the primary DNS server and the secondary DNS server do not respond.

DNS name resolution can be used when executing ping, traceroute, and service-ping, and also when defining file URLs. DNS name resolution is not supported when DNS names are embedded in configuration files.

The no form of this command removes the tertiary DNS server from the configuration.

Default

no tertiary-dns — No tertiary DNS server is configured.

Parameters

ip-address

The IP or IPv6 address of the tertiary DNS server.

Values

ipv4-address -a.b.c.d

ipv6-address:

x:x:x:x:x:x:x:x[-interface]

x:x:x:x:x:x:d.d.d.d[-interface]

x: [0 to FFFF]H

d: [0 to 255]D

interface - 32 characters max, for link local addresses.

Platforms

All

tertiary-dns

Syntax

tertiary-dns ip-address

no tertiary-dns [ip-address]

Context

[Tree] (bof tertiary-dns)

Full Context

bof tertiary-dns

Description

This command configures the tertiary DNS server for DNS name resolution. The tertiary DNS server is used only if the primary DNS server and the secondary DNS server do not respond.

DNS name resolution can be used when executing ping, traceroute, and service-ping, and also when defining file URLs. DNS name resolution is not supported when DNS names are embedded in configuration files.

The no form of this command removes the tertiary DNS server from the configuration.

Default

no tertiary-dns

Parameters

ip-address

Specifies the IP or IPv6 address of the tertiary DNS server.

Values

ipv4-address

a.b.c.d

ipv6-address

x:x:x:x:x:x:x:x[-interface]

x:x:x:x:x:x:d.d.d.d[-interface]

x: [0 to FFFF]H

d: [0 to 255]D

interface

32 chars max, for link local addresses

Note:

IPv6 is applicable to the 7750 SR and 7950 XRS only.

Platforms

All

tertiary-image

tertiary-image

Syntax

tertiary-image file-url

no tertiary-image

Context

[Tree] (bof tertiary-image)

Full Context

bof tertiary-image

Description

This command specifies the tertiary directory location for runtime image file loading.

The system attempts to load all runtime image files configured in the primary-image first. If this fails, the system attempts to load the runtime images from the location configured in the secondary-image. If the secondary image load fails, the tertiary image specified in tertiary-image is used.

All runtime image files (*.tim files) must be located in the same directory.

The no form of this command removes the tertiary-image configuration.

Parameters

file-url

Specifies the file URL; can be either local (this CPM) or a remote FTP server.

Values

file-url

{local-url | remote-url} (up to 180 characters)

local-url

[cflash-id/][file-path]

remote-url

[{ftp://| tftp://} login:pswd@remote-locn/][file-path]

cflash-id

cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

Platforms

All

tertiary-ip-address

tertiary-ip-address

Syntax

tertiary-ip-address ipv4-address

no tertiary-ip-address

Context

[Tree] (config>router>bgp>orr>location tertiary-ip-address)

Full Context

configure router bgp optimal-route-reflection location tertiary-ip-address

Description

This command specifies the tertiary IP address of a reference location used for BGP optimal route reflection. Up to three IPv4 addresses and three IPv6 addresses can be specified per location.

If the TE DB is unable to find a node in its topology database that matches the primary address, then the TE DB tries to find a node with the matching secondary address. If this attempt also fails, the TE DB then tries to find a node with the matching tertiary address.

The IP addresses specified for a location should be topologically "close” to a set of clients that should all receive the same optimal path for that location.

The no form of this command removes the tertiary IP address information.

Default

no tertiary-ip-address

Parameters

ipv4-address

Specifies the tertiary IPv4 address of a location, expressed in dotted decimal notation.

Values

a.b.c.d

Platforms

All

tertiary-ipv6-address

tertiary-ipv6-address

Syntax

tertiary-ipv6-address ipv6-address

no tertiary-ipv6-address

Context

[Tree] (config>router>bgp>orr>location tertiary-ipv6-address)

Full Context

configure router bgp optimal-route-reflection location tertiary-ipv6-address

Description

This command specifies the tertiary IPv6 address of a reference location used for BGP optimal route reflection. Up to three IPv4 addresses and three IPv6 addresses can be specified per location.

If the TE DB is unable find a node in its topology database that matches a primary address of the location, then it tries to find a node matching a secondary address. If this attempt also fails, the TE DB tries to find a node matching a tertiary address.

The IP addresses specified for a location should be topologically "close” to a set of clients that should all receive the same optimal path for that location.

The no form of this command removes the tertiary IPv6 address information.

Default

no tertiary-ipv6-address

Parameters

ipv6-address

Specifies the tertiary IPv6 address of a location.

Values

ipv6-address:

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

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

  • x: [0 to FFFF]H

  • d: [0 to 255]D

Platforms

All

tertiary-location

tertiary-location

Syntax

tertiary-location file-url

no tertiary-location

Context

[Tree] (config>system>software-repository tertiary-location)

Full Context

configure system software-repository tertiary-location

Description

This command configures the tertiary location for the files in the software repository. See the software-repository command description for more information.

The no form of the command removes the tertiary location.

Parameters

file-url

Specifies the tertiary location to be used to access the files in the software repository.

Values

file url

local-url | remote-url

local-url

[cflash-id/][file-path]

up to 200 characters, including cflash-id directory length 99 characters each

remote-url

[{ftp://} login:pswd@remote-locn/][file-path]

243 characters maximum

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

cflash-id

cf1:, cf1-A:, cf1-B:, cf2:, cf2-A:, cf2-B:, cf3:, cf3-A:, cf3-B:

Platforms

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

tertiary-url

tertiary-url

Syntax

tertiary-url url

no tertiary-url

Context

[Tree] (config>python>py-script tertiary-url)

Full Context

configure python python-script tertiary-url

Description

This command specifies the location of tertiary Python script. The system supports three locations for each Python-script. Users can store scripts file on either a local CF card or a FTP server.

The no form of this command removes the URL.

Parameters

url

Specifies the tertiary URL of the Python script up to 180 characters, either a local CF card URL or a FTP server URL.

Platforms

All

test

test

Syntax

[no] test test-name [owner test-owner]

Context

[Tree] (config>saa test)

Full Context

configure saa test

Description

This command identifies a test and enables the context to provide the test parameters for the named test. After the creation of the test instance, the test can be started in the OAM context.

A test can only be modified while it is shut down.

The no form of this command removes the test from the configuration. To remove a test, it cannot be active at the time.

Parameters

test-name

Identifies the SAA test name, up to 32 characters.

test-owner

Specifies the owner, up to 32 characters, of an SAA operation. If a value is not specified, the default owner is used.

Default

"TiMOS CLI”

Platforms

All

test-account

test-account

Syntax

test-account

Context

[Tree] (config>aaa>radius-srv-plcy>servers>health-check test-account)

Full Context

configure aaa radius-server-policy servers health-check test-account

Description

This command sets up a test account as a probing mechanism to check the connectivity of all configured RADIUS authentication servers within the RADIUS server policy.

Platforms

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

test-completion-enable

test-completion-enable

Syntax

[no] test-completion-enable

Context

[Tree] (config>saa>test>trap-gen test-completion-enable)

Full Context

configure saa test trap-gen test-completion-enable

Description

This command enables the generation of a trap when an SAA test completes.

The no form of this command disables the trap generation.

Platforms

All

test-duration

test-duration

Syntax

test-duration seconds

no test-duration

Context

[Tree] (config>oam-pm>session>ethernet>slm test-duration)

[Tree] (config>oam-pm>session>ethernet>dmm test-duration)

[Tree] (config>oam-pm>session>ethernet>lmm test-duration)

Full Context

configure oam-pm session ethernet slm test-duration

configure oam-pm session ethernet dmm test-duration

configure oam-pm session ethernet lmm test-duration

Description

This optional command defines the length of time the test runs before stopping automatically. This command is only a valid option when a session has been configured with a session-type of on-demand. This is not an option when the session-type is configured as proactive. On-demand tests do not start until the config>oam-pm>session>start command has been issued and they stop when the config>oam-pm>session>stop command is issued.

The no form of this command removes a previously configured test-duration and allow the test to run until manually stopped.

Parameters

seconds

Specifies the number of seconds the test runs from its start time.

Values

1 to 86400

Platforms

All

test-duration

Syntax

test-duration seconds

no test-duration

Context

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

Full Context

configure oam-pm session ip twamp-light test-duration

Description

This command defines the length of time the test runs before stopping automatically. This optional command is only valid when a session has been configured with a session-type of on-demand. This is not an option when the session-type is configured as proactive. On-demand tests do not start until the config>oam-pm>session>start command has been issued and they stop when the config>oam-pm>session>stop command is issued.

The no form of this command removes a previously configured test-duration value and allows the TWAMP Light test to execute until it is stopped manually.

Parameters

seconds

Specifies the length of time, in seconds, that the TWAMP Light test runs.

Values

1 to 86400

Platforms

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

test-duration

Syntax

test-duration seconds

no test-duration

Context

[Tree] (config>oam-pm>session>mpls>dm test-duration)

Full Context

configure oam-pm session mpls dm test-duration

Description

This command defines the length of time the test runs before stopping automatically. This command is only valid when a session has been configured with a session-type of on-demand. This is not an option when the session-type is configured as proactive.

On-demand tests do not start until the oam-pm>session>start command has been issued and they stops when scheduled or the oam-pm>session>stop command is issued.

The no form of this command removes a previously configured test-duration and allow the test to run until manually stopped.

Parameters

seconds

Specifies the number of seconds the test runs from its start time.

Values

1 to 8640

Platforms

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

test-duration

Syntax

test-duration

Context

[Tree] (config>test-oam>sath>svc-test test-duration)

Full Context

configure test-oam service-activation-testhead service-test test-duration

Description

Commands in this context configure the test duration for the various functional test types.

Platforms

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

test-fail-enable

test-fail-enable

Syntax

[no] test-fail-enable

Context

[Tree] (config>saa>test>trap-gen test-fail-enable)

Full Context

configure saa test trap-gen test-fail-enable

Description

This command enables the generation of a trap when a test fails. In the case of a ping test, the test is considered failed (for trap generation) if the number of failed probes is at least the value of the test-fail-threshold parameter.

The no form of this command disables the trap generation.

Platforms

All

test-fail-threshold

test-fail-threshold

Syntax

test-fail-threshold threshold

no test-fail-threshold

Context

[Tree] (config>saa>test>trap-gen test-fail-threshold)

Full Context

configure saa test trap-gen test-fail-threshold

Description

This command configures the threshold for trap generation on test failure.

This command has no effect when test-fail-enable is disabled. This command is not applicable to SAA trace route tests.

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

Default

test-fail-threshold 1

Parameters

threshold

Specifies the number of consecutive test failures required to generate a trap.

Values

0 to 15

Platforms

All

test-oam

test-oam

Syntax

test-oam

Context

[Tree] (config test-oam)

Full Context

configure test-oam

Description

Commands in this context configure operations, administration, and maintenance (OAM) test parameters.

Platforms

All

test-pattern

test-pattern

Syntax

test-pattern {all-zeros | all-ones} [crc-enable]

no test-pattern

Context

[Tree] (config>eth-tunnel>path>eth-cfm>mep>eth-test-enable test-pattern)

Full Context

configure eth-tunnel path eth-cfm mep eth-test-enable test-pattern

Description

This command configures the test pattern for eth-test frames.

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

Parameters

all-zeros

Specifies to use all zeros in the test pattern.

all-ones

Specifies to use all ones in the test pattern.

crc-enable

Generates a CRC checksum.

Default

all-zeros

Platforms

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

test-pattern

Syntax

test-pattern {all-zeros | all-ones} [crc-enable]

no test-pattern

Context

[Tree] (config>lag>eth-cfm>mep>eth-test test-pattern)

[Tree] (config>router>if>eth-cfm>mep>eth-test test-pattern)

[Tree] (config>port>ethernet>eth-cfm>mep>eth-test test-pattern)

Full Context

configure lag eth-cfm mep eth-test-enable test-pattern

configure router interface eth-cfm mep eth-test-enable test-pattern

configure port ethernet eth-cfm mep eth-test-enable test-pattern

Description

This command specifies the test pattern of the ETH-TEST frames. This does not have to be configured the same on the sender and the receiver.

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

Default

test-pattern all-zeros

Parameters

all-zeros

Specifies to use all zeros in the test pattern.

all-ones

Specifies to use all ones in the test pattern.

crc-enable

Generates a CRC checksum.

Platforms

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

test-pattern

Syntax

test-pattern {all-zeros | all-ones} [crc-enable]

no test-pattern

Context

[Tree] (config>service>ipipe>sap>eth-cfm>mep>eth-test-enable test-pattern)

[Tree] (config>service>epipe>spoke-sdp>eth-cfm>mep>eth-test-enable test-pattern)

[Tree] (config>service>epipe>sap>eth-cfm>mep>eth-test-enable test-pattern)

Full Context

configure service ipipe sap eth-cfm mep eth-test-enable test-pattern

configure service epipe spoke-sdp eth-cfm mep eth-test-enable test-pattern

configure service epipe sap eth-cfm mep eth-test-enable test-pattern

Description

This command configures the test pattern for eth-test frames.

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

Default

test-pattern all-zeros

Parameters

all-zeros

Specifies to use all zeros in the test pattern.

all-ones

Specifies to use all ones in the test pattern.

crc-enable

Generates a CRC checksum.

Platforms

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

test-pattern

Syntax

test-pattern {all-zeros | all-ones} [crc-enable]

no test-pattern

Context

[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep>eth-test-enable test-pattern)

[Tree] (config>service>vpls>sap>eth-cfm>mep>eth-test-enable test-pattern)

[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep>eth-test-enable test-pattern)

Full Context

configure service vpls spoke-sdp eth-cfm mep eth-test-enable test-pattern

configure service vpls sap eth-cfm mep eth-test-enable test-pattern

configure service vpls mesh-sdp eth-cfm mep eth-test-enable test-pattern

Description

This command configures the test pattern for eth-test frames.

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

Parameters

all-zeros

Specifies to use all zeros in the test pattern

all-ones

Specifies to use all ones in the test pattern

crc-enable

Generates a CRC checksum

Default

all-zeros

Platforms

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

test-pattern

Syntax

test-pattern {all-zeros | all-ones} [crc-enable]

no test-pattern

Context

[Tree] (config>service>ies>if>spoke-sdp>eth-cfm>mep>eth-test-enable test-pattern)

[Tree] (config>service>ies>sub-if>grp-if>sap>eth-cfm>mep>eth-test-enable test-pattern)

[Tree] (config>service>ies>if>sap>eth-cfm>mep>eth-test-enable test-pattern)

Full Context

configure service ies interface spoke-sdp eth-cfm mep eth-test-enable test-pattern

configure service ies subscriber-interface group-interface sap eth-cfm mep eth-test-enable test-pattern

configure service ies interface sap eth-cfm mep eth-test-enable test-pattern

Description

This command configures the test pattern for eth-test frames.

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

Parameters

all-zeros

Specifies to use all zeros in the test pattern.

all-ones

Specifies to use all ones in the test pattern.

crc-enable

Generates a CRC checksum.

Default

all-zeros

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 eth-test-enable test-pattern
  • configure service ies interface sap eth-cfm mep eth-test-enable test-pattern

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

  • configure service ies subscriber-interface group-interface sap eth-cfm mep eth-test-enable test-pattern

test-pattern

Syntax

test-pattern {all-zeros | all-ones} [crc-enable]

no test-pattern

Context

[Tree] (config>service>vprn>if>sap>eth-cfm>mep>eth-test-enable test-pattern)

[Tree] (config>service>vprn>sub-if>grp-if>sap>eth-cfm>eth-test-enable test-pattern)

[Tree] (config>service>vprn>if>spoke-sdp>eth-cfm>mep>eth-test-enable test-pattern)

Full Context

configure service vprn interface sap eth-cfm mep eth-test-enable test-pattern

configure service vprn subscriber-interface group-interface sap eth-cfm eth-test-enable test-pattern

configure service vprn interface spoke-sdp eth-cfm mep eth-test-enable test-pattern

Description

This command configures the test pattern for eth-test frames.

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

Default

test-pattern all-zeros

Parameters

all-zeros

Specifies to use all zeros in the test pattern.

all-ones

Specifies to use all ones in the test pattern.

crc-enable

generates a CRC checksum.

Platforms

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

test-pattern

Syntax

test-pattern {all-zeros | all-ones} [crc-enable]

no test-pattern

Context

[Tree] (config>router>if>eth-cfm>mep>eth-test-enable test-pattern)

Full Context

configure router interface eth-cfm mep eth-test-enable test-pattern

Description

This command specifies the test pattern of the eth-test frames. The test pattern does not need to be configured the same on the transmitter and the receiver.

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

Default

test-pattern all-zeros

Parameters

all-zeros

Specifies to use all zeros in the test pattern.

all-ones

Specifies to use all ones in the test pattern.

crc-enable

Generates a CRC checksum.

Platforms

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

test-pattern

Syntax

test-pattern {all-zeros | all-ones} [crc-enable]

no test-pattern

Context

[Tree] (config>eth-ring>path>eth-cfm>mep>eth-test-enable test-pattern)

Full Context

configure eth-ring path eth-cfm mep eth-test-enable test-pattern

Description

This command configures the test pattern for eth-test frames.

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

Default

test-pattern all-zeros

Parameters

all-zeros

Specifies to use all zeros in the test pattern.

all-ones

Specifies to use all ones in the test pattern.

crc-enable

Generates a CRC checksum.

Platforms

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

test-types

test-types

Syntax

test-types

Context

[Tree] (config>test-oam>sath>svc-test>svc-stream test-types)

Full Context

configure test-oam service-activation-testhead service-test service-stream test-types

Description

Commands in this context configure the types of tests to perform on a specific service stream.

Platforms

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

tethered-flow

tethered-flow

Syntax

[no] tethered-flow

Context

[Tree] (config>app-assure>group>policy>chrg-fltr>entry>match tethered-flow)

Full Context

configure application-assurance group policy charging-filter entry match tethered-flow

Description

This command configures the addition of the tethering status to the match criteria used by this charging filter entry.

The no form of this command removes the tethering status match criteria.

Default

no tethered-flow

Platforms

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

tethering-detection

tethering-detection

Syntax

tethering-detection

Context

[Tree] (config>app-assure>group tethering-detection)

Full Context

configure application-assurance group tethering-detection

Description

Commands in this context configure tethering detection for the group. The shutdown and no shutdown commands are used in this context to enable or disable tethering detection.

Default

tethering-detection shutdown

Platforms

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

tethering-summary

tethering-summary

Syntax

[no] tethering-summary

Context

[Tree] (config>app-assure>group>statistics>aa-partition tethering-summary)

Full Context

configure application-assurance group statistics aa-partition tethering-summary

Description

This command enables tethering summary statistics collection within an aa-partition.

The no form of this command disables tethering summary statistics collection.

Platforms

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

third-party

third-party

Syntax

[no] third-party

Context

[Tree] (config>service>nat>pcp-server-policy>option third-party)

Full Context

configure service nat pcp-server-policy option third-party

Description

This command enables/disables support for the third-party option.

Default

no third-party

Platforms

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

third-party-nexthop

third-party-nexthop

Syntax

third-party-nexthop

no third-party-nexthop

Context

[Tree] (config>service>vprn>bgp>group>neighbor third-party-nexthop)

[Tree] (config>service>vprn>bgp>group third-party-nexthop)

[Tree] (config>service>vprn>bgp third-party-nexthop)

Full Context

configure service vprn bgp group neighbor third-party-nexthop

configure service vprn bgp group third-party-nexthop

configure service vprn bgp third-party-nexthop

Description

Use this command to enable the router to send third-party next-hop to EBGP peers in the same subnet as the source peer, as described in RFC 4271. If enabled when an IPv4 or IPv6 route is received from one EBGP peer and advertised to another EBGP peer in the same IP subnet, the BGP next-hop is left unchanged. Third-party next-hop is not done if the address family of the transport does not match the address family of the route.

The no form of this command prevents BGP from performing any third party next-hop processing toward any single-hop EBGP peers within the scope of the command. No third-party next-hop means the next-hop will always carry the IP address of the interface used to establish the TCP connection to the peer.

Default

no third-party-nexthop

Platforms

All

third-party-nexthop

Syntax

third-party-nexthop

no third-party-nexthop

Context

[Tree] (config>router>bgp>group>neighbor third-party-nexthop)

[Tree] (config>router>bgp third-party-nexthop)

Full Context

configure router bgp group neighbor third-party-nexthop

configure router bgp third-party-nexthop

Description

Use this command to enable the router to send third-party next-hop to EBGP peers in the same subnet as the source peer, as described in RFC 4271. If enabled when an IPv4 or IPv6 route is received from one EBGP peer and advertised to another EBGP peer in the same IP subnet, the BGP next-hop is left unchanged. Third-party next-hop is not done if the address family of the transport does not match the address family of the route.

The no form of this command prevents BGP from performing any third party next-hop processing toward any single-hop EBGP peers within the scope of the command. No third-party next-hop means the next-hop will always carry the IP address of the interface used to establish the TCP connection to the peer.

Default

no third-party-nexthop

Platforms

All

three-way-hello

three-way-hello

Syntax

[no] three-way-hello

Context

[Tree] (config>service>vprn>mvpn>pt>inclusive>pim three-way-hello)

Full Context

configure service vprn mvpn provider-tunnel inclusive pim three-way-hello

Description

This command enables PIM three-way hello on the inclusive provider tunnel.

The no form of this command disables the PIM three-way hello.

Default

disabled

Platforms

All

three-way-hello

Syntax

[no] three-way-hello

Context

[Tree] (config>service>vprn>pim>if three-way-hello)

Full Context

configure service vprn pim interface three-way-hello

Description

This command configures the compatibility mode for enabling the three way hello.

Platforms

All

three-way-hello

Syntax

three-way-hello [compatibility-mode]

no three-way-hello

Context

[Tree] (config>router>pim>interface three-way-hello)

Full Context

configure router pim interface three-way-hello

Description

This command sets the compatibility mode to enable three-way hello. By default, the value is disabled on all interface which specifies that the standard two-way hello is supported. When enabled, the three-way hello is supported.

The no form of this command disables three-way hello.

Default

no three-way-hello

Platforms

All

threshold

threshold

Syntax

threshold xpl-errors

Context

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

Full Context

configure card mda egress-xpl threshold

Description

This command configures the Egress XPL Error Threshold value used by the fail-on-error feature.

Default

threshold 1000

Parameters

xpl-errors

Specifies an upper limit on the frequency of Egress XPL Errors that can occur on the MDA. When fail-on-error is enabled, if the MDA experiences more than xpl-errors errors per minute for the specified number of minutes from the window minutes command, the MDA will be put in the failed state.

The threshold value cannot be changed while fail-on-error is enabled for this MDA.

Values

1 to 1000000

Platforms

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

threshold

Syntax

threshold xpl-errors

Context

[Tree] (config>card>mda>ingress-xpl threshold)

Full Context

configure card mda ingress-xpl threshold

Description

This command configures the Ingress XPL Error Threshold value used by the fail-on-error feature.

Default

threshold 1000

Parameters

xpl-errors

Specifies an upper limit on the frequency of Ingress XPL Errors that can occur on the MDA. When fail-on-error is enabled, if the MDA experiences more than xpl-errors errors per minute for the specified number of minutes from the window minutes command, the MDA will be put in the failed state.

The threshold value cannot be changed while fail-on-error is enabled for this MDA.

Values

1 to 1000000

Platforms

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

threshold

Syntax

threshold {ber-sd | ber-sf} rate threshold-rate

no threshold {ber-sd | ber-sf}

Context

[Tree] (config>port>sonet-sdh threshold)

Full Context

configure port sonet-sdh threshold

Description

This command configures the line signal degradation bit error rate (BER) and line signal failure thresholds.

Line signal (b2) bit interleaved parity error rates are measured and when they cross either the degradation or failure thresholds alarms are raised (see the report-alarm command), furthermore if the failure threshold is crossed the link will be set to operationally down.

For APS configurations, if the ber-sd or ber-sf threshold rates must be modified, the changes must be performed at the line level on both the working and protect APS port member.

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

Default

threshold ber-sd rate 6 — Signal degrade BER threshold of 10-6.

threshold ber-sf rate 3 — Signal failure BER threshold of 10-3.

Parameters

ber-sd

Specifies the BER that specifies signal degradation.

ber-sf

Specifies the BER that specifies signal failure.

threshold-rate

The BER negative exponent (n in 10-n), expressed as a decimal integer.

Values

3 to 9 (10-3 to 10-9) for ber-sd, 3 to 6 for ber-sf

Platforms

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

threshold

Syntax

threshold {ber-sd | ber-sf} rate {1 | 5 | 10 | 50 | 100}

no threshold {ber-sd | ber-sf}

Context

[Tree] (config>port>tdm>ds1 threshold)

[Tree] (config>port>tdm>e1 threshold)

Full Context

configure port tdm ds1 threshold

configure port tdm e1 threshold

Description

This command configures the line signal degradation bit error rate (BER) and line signal failure thresholds.

Line signal (b2) bit interleaved parity error rates are measured and when they cross either the degradation or failure thresholds alarms are raised (see the report-alarm command), furthermore if the failure threshold is crossed the link will be set to operationally down.

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

Default

threshold ber-sd rate 5 threshold ber-sf rate 50

Parameters

ber-sd

Specifies the BER that specifies signal degradation.

ber-sf

Specifies the BER that specifies signal failure.

rate

Specifies the number of errors, in millions.

Platforms

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

threshold

Syntax

threshold threshold

no threshold

Context

[Tree] (config>router>segment-routing>maintenance-policy threshold)

Full Context

configure router segment-routing maintenance-policy threshold

Description

This command configures the minimum number of S-BFD sessions that must be up in order to consider the SR policy candidate path to which the maintenance template is bound to be up. If it is below this number, then the policy candidate path is marked as BFD degraded by the system. This command is only valid in the ecmp-protected mode.

The no form of this command reverts to the default.

Default

threshold 1

Parameters

threshold

Specifies the minimum number of S-BFD sessions that must be up.

Values

1 to 32

Platforms

All

threshold

Syntax

threshold

Context

[Tree] (config>test-oam>link-meas>template>asw threshold)

[Tree] (config>test-oam>link-meas>template>sw threshold)

Full Context

configure test-oam link-measurement measurement-template aggregate-sample-window threshold

configure test-oam link-measurement measurement-template sample-window threshold

Description

Commands in this context configure the applicable thresholds for the sample windows.

Platforms

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

threshold-crossing-alert

threshold-crossing-alert

Syntax

threshold-crossing-alert

Context

[Tree] (config>app-assure>group>statistics threshold-crossing-alert)

Full Context

configure application-assurance group statistics threshold-crossing-alert

Description

Commands in this context configure the generation of threshold crossing alerts (TCAs).

Platforms

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

thresholds

thresholds

Syntax

thresholds

Context

[Tree] (config>service>vprn>dhcp6>server>pool thresholds)

[Tree] (config>router>dhcp6>server>pool>prefix thresholds)

[Tree] (config>router>dhcp6>server>pool thresholds)

[Tree] (config>service>vprn>dhcp6>server>pool>prefix thresholds)

Full Context

configure service vprn dhcp6 local-dhcp-server pool thresholds

configure router dhcp6 local-dhcp-server pool prefix thresholds

configure router dhcp6 local-dhcp-server pool thresholds

configure service vprn dhcp6 local-dhcp-server pool prefix thresholds

Description

Commands in this context configure pool level thresholds.

Default

thresholds

Platforms

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

thresholds

Syntax

thresholds

Context

[Tree] (config>system thresholds)

Full Context

configure system thresholds

Description

Commands in this context configure monitoring thresholds.

Platforms

All

throttle-rate

throttle-rate

Syntax

throttle-rate events [interval seconds]

no throttle-rate

Context

[Tree] (config>log throttle-rate)

Full Context

configure log throttle-rate

Description

This command configures the number of events and interval length to be applied to all event types that have throttling enabled by the event-control command and do not have a specific-throttle-rate configured.

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

Default

throttle-rate 2000 interval 1

Parameters

events

Specifies the number of log events that can be logged within the specified interval for a specific event. Once the limit has been reached, any additional events of that type will be dropped, for example, the event drop count will be incremented. At the end of the throttle interval if any events have been dropped a trap notification will be sent.

Values

1 to 20000

Default

2000

seconds

Specifies the number of seconds that an event throttling interval lasts.

Values

1 to 1200

Default

1

Platforms

All

throughput-alarm

throughput-alarm

Syntax

throughput-alarm high-threshold Mbps low-threshold Mbps

no throughput-alarm

Context

[Tree] (config>li>x-interfaces>x3>alarms throughput-alarm)

Full Context

configure li x-interfaces x3 alarms throughput-alarm

Description

This command configures the thresholds for raising the throughput alarm. The throughput is shared with other ISA BB applications. The low threshold value must be configured with a smaller value than the high threshold.

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

Parameters

high-threshold Mbps

Specifies the high threshold value.

Values

1 to 4294967295

low-threshold Mbps

Specifies the low threshold value.

Values

1 to 4294967295

Platforms

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

ti-lfa

ti-lfa

Syntax

ti-lfa [max-sr-frr-labels value] [max-srv6-frr-sids sids-value]

no ti-lfa

Context

[Tree] (config>router>isis>lfa ti-lfa)

Full Context

configure router isis loopfree-alternates ti-lfa

Description

This command enables the use of the Topology-Independent LFA (TI-LFA) algorithm in the LFA SPF calculation for this IS-IS instance.

The no form of this command disables the use of the TI-LFA algorithm in the LFA SPF calculation for this IS-IS instance.

Default

no ti-lfa

Parameters

value

Specifies the maximum number of labels allowed in the segment list of the TI-LFA repair tunnel. A higher value results in better coverage by TI-LFA at the expense of increased packet encapsulation overhead. The TI-LFA algorithm uses this value to limit the search for the Q-node from the P-node on the post-convergence path.

Values

0 to 3

Default

2

sids-value

Specifies the maximum number of SRv6 SIDs allowed in the segment list of the TI-LFA repair tunnel. A higher value results in better coverage by TI-LFA at the expense of increased packet encapsulation overhead. The TI-LFA algorithm uses this value to limit the search for the Q-node from the P-node on the post-convergence path.

Values

0 to 3

Default

1

Platforms

All

ti-lfa

Syntax

ti-lfa [max-sr-frr-labels value]

no ti-lfa

Context

[Tree] (config>router>ospf3>loopfree-alternates ti-lfa)

[Tree] (config>router>ospf>loopfree-alternates ti-lfa)

Full Context

configure router ospf3 loopfree-alternates ti-lfa

configure router ospf loopfree-alternates ti-lfa

Description

This command enables the use of the Topology Independent Loop-Free Alternate (TI-LFA) algorithm in the LFA SPF calculation for this OSPF or OSPFv3 instance.

The no form of this command disables the use of the TI-LFA algorithm in the LFA SPF calculation in this OSPF or OSPFv3 instance.

Default

no ti-lfa

Parameters

max-sr-frr-labels [value]]

Specifies the maximum number of labels allowed in the segment list of the TI-LFA repair tunnel. A higher value results in better coverage by TI-LFA at the expense of increased packet encapsulation overhead. The TI-LFA algorithm uses this value to limit the search for the Q-node from the P-node on the post-convergence path.

Values

0 to 3

Default

2

Platforms

All

tier

tier

Syntax

tier {1 | 2}

Context

[Tree] (config>qos>policer-control-policy tier)

Full Context

configure qos policer-control-policy tier

Description

This command is used to create, configure, and delete tiered arbiters. Two tiers are supported that always exist, specified as tier 1 and tier 2. Tiered arbiters enable the creation of a bandwidth control hierarchy for managing child policers in an arbitrary fashion. Each arbiter enables parenting of child policers within eight strict levels of priority and a maximum aggregate rate may be defined for the children that the arbiter will enforce. Arbiters created on tier 1 are automatically parented to the root arbiter that is always present. Arbiters created on tier 2 default to the root arbiter as parent but can also be explicitly parented to a tier 2 arbiter. Child policers associated with an instance of the policer-control-policy can be parented to any tiered arbiter or to the root arbiter.

Platforms

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

tier

Syntax

[no] tier tier

Context

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

Full Context

configure qos scheduler-policy tier

Description

This command identifies the level of hierarchy that a group of schedulers are associated with. Within a tier level, a scheduler can be created or edited. Schedulers created within a tier can only be a child (take bandwidth from a scheduler in a higher tier). Tier levels increase sequentially with 1 being the highest tier. All tier 1 schedulers are considered to be root and cannot be a child of another scheduler. Schedulers defined in tiers other than 1 can also be root (parentless).

3 tiers (levels 1, 2, and 3) are supported.

The save config and show config commands only display information on scheduler tiers that contain defined schedulers. When all schedulers have been removed from a level, that level ceases to be included in output from these commands.

Parameters

tier

This parameter is required to indicate the group of schedulers to create or be edited. Tier levels cannot be created or deleted. If a value for level is given that is out-of-range, an error will occur and the current context of the CLI session will not change.

Values

1 to 3

Platforms

All

time

time

Syntax

time

Context

[Tree] (config>system time)

Full Context

configure system time

Description

Commands in this context configure the system time zone and time synchronization parameters.

Platforms

All

time

Syntax

time time

Context

[Tree] (config>system>security>pki>cert-udp-prof>sched time)

Full Context

configure system security pki certificate-update-profile schedule time

Description

This command configures the time relative to the valid certificate period.

Default

time 86400

Parameters

time

Specifies the time relative to valid certificate period.

Values

3600 to 157680000

Platforms

All

time-average-factor

time-average-factor

Syntax

time-average-factor taf-value [dec-only]

no time-average-factor

Context

[Tree] (config>qos>adv-config-policy>child-control>offered-measurement time-average-factor)

Full Context

configure qos adv-config-policy child-control offered-measurement time-average-factor

Description

This command is used to weight the new offered rate with a portion of the previous offered rate. It would be expected that this command would mainly be used with the dec-only option enabled.

The adjustment to the offered rate is performed using the following formula when taf-value is not set to '0’:

Adjusted_Rate = ((Prev_Offered_Rate x (taf-value – 1)) + New_Offered_Rate) / taf-value

If the dec-only option is specified, the adjustment is only applied when New_Offered_Rate is less than the Prev_Offered_Rate. When taf-value is set to '0’, the adjustment is never applied.

The no form of this command is used to remove the time average factor adjustments to new offered rate measurements.

Parameters

taf-value

The taf-value is specified as a whole number between 0 and 64. The value '0’ has special meaning in that it disables the time average factor adjustment and has the same effect as no time-average-factor.

Default

0

Values

0 to 64

dec-only

This keyword is an optional parameter. When enabled, the time average factor adjustment is only applied if the new offered rate is decreasing compared to the previous offered rate. If the new offered rate is greater than the previous offered rate, the adjustment is not applied.

Platforms

All

time-average-factor

Syntax

time-average-factor value

no time-average-factor

Context

[Tree] (config>qos>slope-policy time-average-factor)

Full Context

configure qos slope-policy time-average-factor

Description

This command sets a weighting factor to calculate the new shared buffer average utilization after assigning buffers for a packet entering a queue. To derive the new shared buffer average utilization, the buffer pool takes a portion of the previous shared buffer average and adds it to the inverse portion of the instantaneous shared buffer utilization.

The time-average-factor command sets the weighting factor between the old shared buffer average utilization and the current shared buffer instantaneous utilization when calculating the new shared buffer average utilization

The TAF value applies to all high- and low-priority RED slopes for ingress and egress access buffer pools controlled by the slope policy.

The no form of this command restores the default setting.

Default

time-average-factor 7

Parameters

value

Represents the Time Average Factor (TAF), expressed as a decimal integer. The value specified for TAF affects the speed at which the shared buffer average utilization tracks the instantaneous shared buffer utilization. A low value weights the new shared buffer average utilization calculation more to the shared buffer instantaneous utilization; zero using it exclusively. A high value weights the new shared buffer average utilization calculation more to the previous shared buffer average utilization value.

Values

0 to 15

Platforms

All

time-display

time-display

Syntax

time-display {local | utc}

Context

[Tree] (environment time-display)

Full Context

environment time-display

Description

This command displays time stamps in the CLI session based on local time or Coordinated Universal Time (UTC).

The system keeps time internally in UTC and is capable of displaying the time in either UTC or local time based on the time zone configured.

This environment command only applies to times displayed in the current CLI session. This includes displays of event logs and all other places where a time stamp is displayed.

In event logs, the selected time is used to control the timestamps in the CLI output of show log log-id and in YANG state in the /state/log/log-id branch (for logs such as session, cli, memory, SNMP and NETCONF).

Also see the configure log log-id time-format command.

Default

time-display local

Parameters

local

Indicates that local time should be used.

utc

Indicates that UTC time should be used.

Platforms

All

time-display

Syntax

time-display {local | utc}

Context

[Tree] (config>system>management-interface>cli>md-cli>environment time-display)

Full Context

configure system management-interface cli md-cli environment time-display

Description

This command configures whether the time is displayed in coordinated Universal Time (UTC) or local time (as configured in config>system>time).

Default

time-display local

Parameters

local

Specifies that the local time zone is used.

utc

Specifies that UTC is used.

Platforms

All

time-exceeded

time-exceeded

Syntax

time-exceeded [number seconds]

no time-exceeded

Context

[Tree] (config>service>ies>if>ipv6>icmp6 time-exceeded)

Full Context

configure service ies interface ipv6 icmp6 time-exceeded

Description

This command specifies whether time-exceeded ICMP messages should be sent. When enabled, ICMPv6 time-exceeded messages are generated by this interface.

When disabled, ICMPv6 time-exceeded messages are not sent.

The no form of this command reverts to the default.

Default

time-exceeded 100 10

Parameters

number

Specifies the number of time-exceeded ICMP messages are to be issued in the time frame specified by the seconds parameter.

Values

10 to 2000

seconds

Specifies the time frame, in seconds, that is used to limit the number of time-exceeded ICMP message to be issued.

Values

1 to 60

Platforms

All

time-exceeded

Syntax

time-exceeded [number seconds]

no time-exceeded

Context

[Tree] (config>router>if>ipv6>icmp6 time-exceeded)

[Tree] (config>service>vprn>if>ipv6>icmp6 time-exceeded)

Full Context

configure router interface ipv6 icmp6 time-exceeded

configure service vprn interface ipv6 icmp6 time-exceeded

Description

This command configures rate for ICMPv6 time-exceeded messages.

Parameters

number

Limits the number of time-exceeded messages issued per the time frame specified in seconds parameter.

Values

10 to 2000

seconds

Determines the time frame, in seconds, that is used to limit the number of time-exceeded messages issued per time frame.

Values

1 to 60

Platforms

All

time-format

time-format

Syntax

time-format {local | utc}

Context

[Tree] (config>service>vprn>log>log-id time-format)

Full Context

configure service vprn log log-id time-format

Description

This command specifies whether the time should be displayed in local or Coordinated Universal Time (UTC) format.

Default

time-format utc

Parameters

local

Specifies that timestamps are written in the system’s local time.

utc

Specifies that timestamps are written using the UTC value. This was formerly called Greenwich Mean Time (GMT) and Zulu time.

Platforms

All

time-format

Syntax

time-format {local | utc}

Context

[Tree] (config>li>log>log-id time-format)

Full Context

configure li log log-id time-format

Description

This command specifies whether the time should be displayed in local or Coordinated Universal Time (UTC) format.

Default

time-format utc

Parameters

local

Specifies that timestamps are written in the system’s local time.

utc

Specifies that timestamps are written using the UTC value. This was formerly called Greenwich Mean Time (GMT) and Zulu time.

Platforms

All

time-format

Syntax

time-format {local | utc}

Context

[Tree] (config>log>log-id time-format)

Full Context

configure log log-id time-format

Description

This command specifies whether the time should be output in local or Coordinated Universal Time (UTC) format in the following event log locations:

  • in the syslog TIMESTAMP field
  • in the timestamp of log events inside log files on local storage devices

The timestamp in the filename of event log files is not affected by this command.

The output of show log log-id and the output of YANG state under /state/log/log-id are not affected by this command. See the environment time-display command.

Default

time-format utc

Parameters

local

Specifies that timestamps are written in the system’s local time.

utc

Specifies that timestamps are written using the UTC value. This was formerly called Greenwich Mean Time (GMT) and Zulu time.

Platforms

All

time-limit

time-limit

Syntax

time-limit limit-value

Context

[Tree] (config>call-trace>trace-profile time-limit)

Full Context

configure call-trace trace-profile time-limit

Description

This command specifies how long a trace may run before it is stopped.

Default

time-limit 86400

Parameters

limit-value

Specifies the maximum duration of a single call trace job in seconds. After reaching the limit the call trace job for a given host is automatically terminated.

Values

1 to 604800

Platforms

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

time-range

time-range

Syntax

time-range daily start start-time end end-time [on day [day]]

time-range weekly start start-time end end-time

no time-range

Context

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

Full Context

configure application-assurance group policer tod-override time-range

Description

This command configures up to seven time-ranges applicable to a particular override-id. The time-range can be configured as daily or weekly policies.

When using a daily override the operator can select which days during the week from Sunday to Saturday it is applicable along with the start/end hour/min time range repeated over these days.

When using a weekly override the operator can select between which days in the week the policy start up to the hours/min for both start day and end day.

Default

no time-range

Parameters

daily

Schedule the override as a daily occurrence.

weekly

Schedule the override as a weekly occurrence.

Values

start-time

daily

<hh>:<mm>

weekly

<day>,<hh>:<mm>

<hh> : 0..23

<mm> : 0 | 15 | 30 | 45

end-time

daily

<hh>:<mm>

weekly

<day>,<hh>:<mm>

<hh> 0..23

<mm> 0 | 15 | 30 | 45

day

sunday | monday | tuesday | wednesday | thursday | friday | saturday

Platforms

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

time-stamp

time-stamp

Syntax

[no] time-stamp

Context

[Tree] (environment time-stamp)

Full Context

environment time-stamp

Description

This command specifies whether the time-stamp should be displayed before the prompt.

Platforms

All

timeout

timeout

Syntax

timeout [sec seconds] [min minutes]

Context

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

Full Context

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

Description

This command configures the time that the router waits for a response from a RADIUS server.

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

Default

timeout sec 5

Parameters

seconds

Specifies the time, in seconds, that the router waits for a response from a RADIUS server.

Values

1 to 59

minutes

Specifies the time, in minutes, that the router waits for a response from a RADIUS server.

Values

1 to 1

Platforms

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

timeout

Syntax

timeout seconds

Context

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

Full Context

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

Description

This command configures the number of seconds the router waits for a response from a RADIUS server.

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

Default

timeout 5

Parameters

seconds

Specifies the time the router waits for a response from a RADIUS server.

Values

1 to 90

Platforms

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

timeout

Syntax

timeout seconds

Context

[Tree] (config>service>vprn>sub-if>grp-if>sap>static-host>managed-routes>route-entry>cpe-check timeout)

[Tree] (config>service>ies>sub-if>grp-if>sap>static-host>managed-routes>route-entry>cpe-check timeout)

Full Context

configure service vprn subscriber-interface group-interface sap static-host managed-routes route-entry cpe-check timeout

configure service ies subscriber-interface group-interface sap static-host managed-routes route-entry cpe-check timeout

Description

This command configures the time the system waits for a reply to a specific ping before concluding the ping has been missed.

Default

timeout 1

Parameters

seconds

Specifies the time, in seconds, that the router waits for a response.

Values

1 to 10

Platforms

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

timeout

Syntax

timeout seconds

no timeout

Context

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

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

Full Context

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

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

Description

This command configures the number of seconds the router waits for a response from a RADIUS server.

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

Default

timeout 3

Parameters

seconds

Specifies the time, in seconds, that the router waits for a response from a RADIUS server, expressed as a decimal integer.

Values

1 to 90

Platforms

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

timeout

Syntax

timeout seconds

no timeout

Context

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

Full Context

configure subscriber-mgmt shcv-policy periodic timeout

Description

This command configures the timeout before a retransmission in triggered connectivity verification.

The no form of this command reverts to the default.

Default

timeout 10

Parameters

seconds

Specifies the timeout, in seconds, before a retransmission in triggered connectivity verification.

Values

10 to 60

Platforms

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

timeout

Syntax

timeout seconds

no timeout

Context

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

Full Context

configure subscriber-mgmt shcv-policy trigger timeout

Description

This command configures the timeout before a retransmission.

The no form of this command reverts to the default.

Default

timeout 1 — trigger-type ip-conflict, host-limit-exceeded and mobility

timeout 2 — trigger-type inactivity and mac-learning

Parameters

seconds

Specifies the retry timeout in seconds.

Values

1 to 60

Platforms

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

timeout

Syntax

timeout [sec seconds] [min minutes]

no timeout

Context

[Tree] (config>aaa>radius-srv-plcy>servers timeout)

Full Context

configure aaa radius-server-policy servers timeout

Description

This command configures the time the router waits for a response from a RADIUS server.

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

Default

timeout sec 5

Parameters

seconds

Specifies the number of seconds for the timeout.

Values

1 to 59

minutes

Specifies the number of minutes for the timeout.

Values

1 to 5

Values

Max. value = 5 min 40 sec

Platforms

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

timeout

Syntax

timeout [hrs hours] [min minutes] [sec seconds]

no timeout

Context

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

[Tree] (config>router>radius-proxy>server>cache timeout)

Full Context

configure service vprn radius-proxy server cache timeout

configure router radius-proxy server cache timeout

Description

This command configures the time for which the cache entry is kept if there is no corresponding DHCP DISCOVER. At the expiry of this time, the cache entry is deleted.

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

Default

timeout min 5

Parameters

hours

Specifies, in hours, the timeout after which an entry in the cache will expire.

Values

1

minutes

Specifies, in minutes, the timeout after which an entry in the cache will expire.

Values

1 to 59

seconds

Specifies, in seconds, the timeout after which an entry in the cache will expire.

Values

1 to 59

Platforms

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

timeout

Syntax

timeout seconds

Context

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

Full Context

configure subscriber-mgmt pfcp-association heartbeat timeout

Description

This command configures the timeout period, after which, a Heartbeat Request message is considered unanswered.

Default

timeout 5

Parameters

seconds

Specifies the timeout value, in seconds. This interval should be identical on both the BNG UPF and CPF. For information about the BNG CUPS CPF configuration, refer to the CMG BNG CUPS Control Plane Function Guide and the 7750 SR MG and CMG CLI Reference Guide.

Values

1 to 20

Platforms

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

timeout

Syntax

timeout seconds

Context

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

Full Context

configure subscriber-mgmt pfcp-association tx timeout

Description

This command configures the timeout period, after which, a message is considered unanswered. This timeout value is also known as T1.

Default

timeout 5

Parameters

seconds

Specifies the timeout 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 30

Platforms

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

timeout

Syntax

timeout seconds

no timeout

Context

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

Full Context

configure service vprn aaa remote-servers radius timeout

Description

This command configures the number of seconds the router waits for a response from a RADIUS server.

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

Default

timeout 3

Parameters

seconds

Specifies the number of seconds the router waits for a response from a RADIUS server, expressed as a decimal integer.

Values

1 to 90

Platforms

All

timeout

Syntax

timeout seconds

no timeout

Context

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

Full Context

configure service vprn aaa remote-servers tacplus timeout

Description

This command configures the number of seconds the router waits for a response from a TACACS+ server.

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

Default

timeout 3

Parameters

seconds

Specifies the number of seconds the router waits for a response from a TACACS+ server, expressed as a decimal integer.

Values

1 to 90

Platforms

All

timeout

Syntax

timeout seconds

no timeout

Context

[Tree] (config>router>mpls>lsp-self-ping timeout)

Full Context

configure router mpls lsp-self-ping timeout

Description

This command configures a timeout value for LSP Self Ping. The LSP Self Ping timer is started when the RESV message is received for an LSP. The system then periodically sends LSP Self Ping packets until the timer expiry or the receipt of the first LSP Self Ping reply, whichever comes first. If the timeout expires before an LSP Self Ping packet is received, then the configured timeout-action is performed.

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

Default

timeout 300

Parameters

seconds

Specifies the value, in seconds, of the fast retry timer for a secondary path.

Values

3 to 3600

Platforms

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

timeout

Syntax

timeout seconds

Context

[Tree] (config>system>file-trans-prof timeout)

Full Context

configure system file-transmission-profile timeout

Description

This command specifies timeout value in seconds for transport protocol. The timeout is the maximum waiting time to receive any data from the server (e.g., FTP or HTTP server).

Default

timeout 60

Parameters

seconds

Specifies the connection timeout (in seconds) for the file transmission.

Values

1 to 3600

Platforms

All

timeout

Syntax

timeout [sec seconds] [min minutes]

no timeout

Context

[Tree] (config>aaa>isa-radius-plcy>servers timeout)

Full Context

configure aaa isa-radius-policy servers timeout

Description

This command configures the number of seconds the router waits for a response from a RADIUS server.

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

Default

timeout sec 5

Parameters

seconds

Specifies the wait for a response from a RADIUS server, in seconds.

minutes

Specifies the wait for a response from a RADIUS server, in minutes.

Platforms

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

timeout

Syntax

timeout timeout

no timeout

Context

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

Full Context

configure test-oam ldp-treetrace path-discovery timeout

Description

This command configures the time the node waits for the response to an LSP Trace message discovering the path of an LDP FEC before it declares failure. After consecutive failures equal to the retry-count parameter, the node gives up.

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

Default

timeout 30

Parameters

timeout

Specifies the timeout parameter, in seconds, within a range of 1 to 60, expressed as a decimal integer.

Values

1 to 60

Platforms

All

timeout

Syntax

timeout timeout

no timeout

Context

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

Full Context

configure test-oam ldp-treetrace path-probing timeout

Description

This command configures the time the node waits for the response to an LSP Ping message probing the path of an LDP FEC before it declares failure. After consecutive failures equal to the retry-count parameter, the node gives up.

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

Default

timeout 1

Parameters

timeout

Specifies the timeout parameter, in minutes, expressed as a decimal integer.

Values

1 to 3

Platforms

All

timeout

Syntax

timeout timeout

no timeout

Context

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

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

Full Context

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

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

Description

This command configures the number, 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 last probe for a specific test. Upon the expiration of the time out, the test is marked complete and no more packets are processed for any of the request probes.

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

Default

timeout 5

Parameters

timeout

Specifies the timeout value in seconds.

Values

1 to 10

Default

5

Platforms

All

timeout

Syntax

timeout timeout

no timeout

Context

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

Full Context

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

Description

This command configures 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 the message time out, the requesting router assumes that the message response is not received. A request timeout message is displayed by the CLI for each message request sent that expires. Any response received after the request times out is silently discarded.

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

Default

timeout 3

Parameters

timeout

Specifies the timeout value in seconds.

Values

1 to 60

Default

3

Platforms

All

timeout

Syntax

timeout [seconds]

no timeout

Context

[Tree] (config>filter>redirect-policy>dest>ping-test timeout)

Full Context

configure filter redirect-policy destination ping-test timeout

Description

Specifies the amount of time, in seconds, that is allowed for receiving a response from the far-end host. If a reply is not received within this time the far-end host is considered unresponsive.

Default

timeout 1

Parameters

seconds

Specifies the amount of time, in seconds, that is allowed for receiving a response from the far end host.

Values

1 to 60

Platforms

All

timeout

Syntax

timeout seconds

no timeout

Context

[Tree] (config>vrrp>vrrp-policy-id>priority-event>host-unreachable timeout)

Full Context

configure vrrp vrrp-policy-id priority-event host-unreachable timeout

Description

This command defines the time, in seconds, that must pass before considering the far-end IP host unresponsive to an outstanding ICMP echo request message.

The timeout value is not directly related to the configured interval parameter. The timeout value may be larger, equal, or smaller, relative to the interval value.

If the timeout value is larger than the interval value, multiple ICMP echo request messages may be outstanding. Every ICMP echo request message transmitted to the far end host is tracked individually according to the message identifier and sequence number.

With each consecutive attempt to send an ICMP echo request message, the timeout timer is loaded with the timeout value. The timer decrements until:

  • an internal error occurs preventing message sending (request unsuccessful)

  • an internal error occurs preventing message reply receiving (request unsuccessful)

  • a required route table entry does not exist to reach the IP address (request unsuccessful)

  • a required ARP entry does not exist and ARP request timed out (request unsuccessful)

  • a valid reply is received (request successful)

It is possible for a required ARP request to succeed or timeout after the message timeout timer expires. In this case, the message request is unsuccessful.

If an ICMP echo reply message is not received prior to the timeout period for a given ICMP echo request, that request is considered to be dropped and increments the consecutive message drop counter for the priority event.

If an ICMP echo reply message with the same sequence number as an outstanding ICMP echo request message is received prior to that message timing out, the request is considered successful. The consecutive message drop counter is cleared and the request message no longer is outstanding.

If an ICMP Echo Reply message with a sequence number equal to an ICMP echo request sequence number that had previously timed out is received, that reply is silently discarded while incrementing the priority event reply discard counter.

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

Default

timeout 1

Parameters

seconds

The number of seconds before an ICMP echo request message is timed out. Once a message is timed out, a reply with the same identifier and sequence number is discarded.

Values

1 to 60

timeout

Syntax

timeout timeout

no timeout

Context

[Tree] (config>service>sdp>keep-alive timeout)

Full Context

configure service sdp keep-alive timeout

Description

This command configures the time interval that the SDP waits before tearing down the session.

Default

timeout 5

Parameters

timeout

Specifies the timeout time, in seconds.

Values

1 to 10

Platforms

All

timeout

Syntax

timeout seconds

no timeout

Context

[Tree] (config>system>security>radius timeout)

Full Context

configure system security radius timeout

Description

This command configures the number of seconds the router waits for a response from a RADIUS server.

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

Default

timeout 3

Parameters

seconds

Specifies the number of seconds the router waits for a response from a RADIUS server, expressed as a decimal integer.

Values

1 to 90

Platforms

All

timeout

Syntax

timeout seconds

no timeout

Context

[Tree] (config>system>security>tacplus timeout)

Full Context

configure system security tacplus timeout

Description

This command configures the number of seconds the router waits for a response from a TACACS+ server.

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

Default

timeout 3

Parameters

seconds

The number of seconds the router waits for a response from a TACACS+ server, expressed as a decimal integer.

Values

1 to 90

Platforms

All

timeout

Syntax

timeout seconds

no timeout

Context

[Tree] (config>system>security>ldap timeout)

Full Context

configure system security ldap timeout

Description

The timeout value is the number of seconds that the SR OS will wait for a response from the current server that it is trying to establish a connection with. If the server does not reply within the configured timeout value, the SR OS will increment the retry counter by 1. The SR OS attempts to establish the connection to the current server up to the configured retry value before it moves to the next configured server.

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

Default

timeout 3

Parameters

seconds

The length of time that the SR OS waits for a response from the server.

Values

1 to 90

Default

3

Platforms

All

timeout

Syntax

timeout seconds

no timeout

Context

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

Full Context

configure system security dot1x radius-plcy timeout

Description

This command configures the number of seconds the router waits for a response from a RADIUS server.

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

Default

timeout 3

Parameters

seconds

Specifies the number of seconds the router waits for a response from a RADIUS server, expressed as a decimal integer.

Values

1 to 90

Platforms

All

timeout

Syntax

timeout seconds

no timeout

Context

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

Full Context

configure test-oam icmp ping-template timeout

Description

This command configures the time the function waits before declaring an ICMP echo request packet is lost. This is the timer used to time out the interval transmitted packets. The timeout can be equal to or lower than the interval but not higher.

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

Default

timeout 5

Parameters

seconds

Specifies the time, in seconds, before declaring an ICMP echo request being lost.

Platforms

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

timeout-action

timeout-action

Syntax

timeout-action action

no timeout-action

Context

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

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

Full Context

configure router l2tp tunnel-selection-blacklist timeout-action

configure service vprn l2tp tunnel-selection-blacklist timeout-action

Description

This command defines an action that is executed on the entity (peer/tunnel) in the denylist once the entity becomes eligible for selection again.

The no form of this command reverts to the default.

Default

timeout-action remove-from-blacklist

Parameters

action

Specifies the Action to be taken when a tunnel or peer has been in the denylist for the max-period of time.

Values

remove-from-blacklist — The peer or tunnel in the denylist is removed completely from the denylist and made eligible for the selection process once the max-time expires. In this mode of operation, multiple new sessions can be mapped into the same, newly released tunnel from the denylist. The first such session will try to setup the tunnel, while the other is buffered until the tunnel establishment process is completed. In case that the tunnel remains unavailable, it is placed in the denylist again. Consequently, all new sessions are re-negotiated over an alternate tunnel.

try-one-session — Once the max-time expired, the peer or tunnel in the denylist is made available for selection only to a single new session request. Only upon successful tunnel establishment will the incoming new sessions be eligible to be mapped into this tunnel. This behavior will avoid session establishment delays in case that the tunnel just removed from the denylist is still unavailable.

Platforms

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

timeout-action

Syntax

timeout-action {retry | switch}

no timeout-action

Context

[Tree] (config>router>mpls>lsp-self-ping timeout-action)

Full Context

configure router mpls lsp-self-ping timeout-action

Description

This command configures an action that the router takes when the timeout LSP self ping timeout timer expires. The lsp-self-ping timer is started when the RESV is received for an LSP. If the retry is configured and the timeout expires before an LSP self ping packet is received, then the system tears down the candidate path and goes back to CSPF for a new path. If the switch is configured and the timeout expires before an LSP self ping packet is received, then the system switches to the candidate path.

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

Default

timeout-action retry

Parameters

retry

Specifies to retry the candidate path when the timeout expires.

switch

Specifies to switch to the candidate path when the timeout expires.

Platforms

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

timeouts

timeouts

Syntax

[no] timeouts

Context

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

[Tree] (config>service>nat>nat-policy timeouts)

[Tree] (config>service>nat>up-nat-policy timeouts)

Full Context

configure service nat firewall-policy timeouts

configure service nat nat-policy timeouts

configure service nat up-nat-policy timeouts

Description

This command configures session idle timeouts for this policy.

Platforms

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

  • configure service nat firewall-policy timeouts

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

  • configure service nat up-nat-policy timeouts
  • configure service nat nat-policy timeouts

timeouts

Syntax

timeouts

Context

[Tree] (config>li>x-interfaces>x1 timeouts)

[Tree] (config>li>x-interfaces>x3 timeouts)

[Tree] (config>li>x-interfaces>x2 timeouts)

Full Context

configure li x-interfaces x1 timeouts

configure li x-interfaces x3 timeouts

configure li x-interfaces x2 timeouts

Description

This command configures the X1, X2, and X3 messages timeout.

Platforms

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

timers

timers

Syntax

timers

Context

[Tree] (config>service>dynsvc timers)

Full Context

configure service dynamic-services timers

Description

Commands in this context configure dynamic data services related timers.

Platforms

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

timers

Syntax

timers

Context

[Tree] (config>service>vpls>spb timers)

Full Context

configure service vpls spb timers

Description

Commands in this context configure SPB timers.

Platforms

All

timers

Syntax

[no] timers

Context

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

Full Context

configure service vprn isis timers

Description

This command configures the IS-IS timer values.

Default

n/a

Platforms

All

timers

Syntax

timers

Context

[Tree] (config>service>vprn>ospf timers)

[Tree] (config>service>vprn>ospf3 timers)

Full Context

configure service vprn ospf timers

configure service vprn ospf3 timers

Description

Commands in this context configure OSPF timers. Timers control the delay between receipt of a LSA requiring a Dijkstra (Shortest Path First (SPF)) calculation and the minimum time between successive SPF calculations.

Changing the timers affect CPU utilization and network reconvergence times. Lower values reduce convergence time but increase CPU utilization. Higher values reduce CPU utilization but increase reconvergence time.

Platforms

All

timers

Syntax

timers update timeout flush

no timers

Context

[Tree] (config>service>vprn>ripng timers)

[Tree] (config>service>vprn>rip timers)

[Tree] (config>service>vprn>rip>group>neighbor timers)

[Tree] (config>service>vprn>ripng>group timers)

[Tree] (config>service>vprn>ripng>group>neighbor timers)

[Tree] (config>service>vprn>rip>group timers)

Full Context

configure service vprn ripng timers

configure service vprn rip timers

configure service vprn rip group neighbor timers

configure service vprn ripng group timers

configure service vprn ripng group neighbor timers

configure service vprn rip group timers

Description

This command configures the values for the update, timeout, and flush timers:

  • update timer

    Determines how often RIP updates are sent.

  • timeout timer

    If a router is not updated by the time the timer expires, the route is declared invalid, but maintained in the RIP database.

  • flush timer

    Determines how long a route is maintained in the RIP database, after it has been declared invalid. Once this timer expires it is flushed from the RIP database completely.

The no form of this command resets all timers to their default values of 30, 180, and 120 seconds respectively.

Default

no timers

Parameters

update

The RIP update timer value in seconds.

Values

1 to 600

Default

30

timeout

The RIP timeout timer value in seconds.

Values

1 to 1200

Default

180

flush

The RIP flush timer value in seconds.

Values

1 to 1200

Default

120

Platforms

All

timers

Syntax

timers [neighbor ip-address | group name]

no timers

Context

[Tree] (debug>router>bgp timers)

Full Context

debug router bgp timers

Description

This command logs all BGP timer events to the debug log.

The no form of this command disables debugging.

Parameters

neighbor ip-address

Debugs only events affecting the specified BGP neighbor.

Values

ipv4-address:

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

ipv6-address:

  • x:x:x:x:x:x:x:x [-interface] (eight 16-bit pieces)

  • x:x:x:x:x:x:d.d.d.d [-interface]

  • x: [0 to FFFF]H

  • d: [0 to 255]D

  • interface: up to 32 characters for link local addresses

group name

Debugs only events affecting the specified peer group name, up to 64 characters, and associated neighbors.

Platforms

All

timers

Syntax

[no] timers

Context

[Tree] (config>router>isis timers)

Full Context

configure router isis timers

Description

This command configures the IS-IS timer values.

Platforms

All

timers

Syntax

timers

Context

[Tree] (config>router>ospf timers)

[Tree] (config>router>ospf3 timers)

Full Context

configure router ospf timers

configure router ospf3 timers

Description

Commands in this context configure OSPF timers. Timers control the delay between receipt of a link state advertisement (LSA) requiring a Dijkstra (Shortest Path First (SPF)) calculation and the minimum time between successive SPF calculations.

Changing the timers affects CPU utilization and network re-convergence times. Lower values reduce convergence time but increase CPU utilization. Higher values reduce CPU utilization but increase re-convergence time.

Platforms

All

timers

Syntax

timers update timeout flush

no timers

Context

[Tree] (config>router>rip timers)

[Tree] (config>router>ripng>group>neighbor timers)

[Tree] (config>router>ripng>group timers)

[Tree] (config>router>ripng timers)

[Tree] (config>router>rip>group timers)

[Tree] (config>router>rip>group>neighbor timers)

Full Context

configure router rip timers

configure router ripng group neighbor timers

configure router ripng group timers

configure router ripng timers

configure router rip group timers

configure router rip group neighbor timers

Description

This command configures values for the update, timeout and flush RIP timers.

The RIP update timer determines how often RIP updates are sent.

If the route is not updated by the time the RIP timeout timer expires, the route is declared invalid but is maintained in the RIP database.

The RIP flush timer determines how long a route is maintained in the RIP database after it has been declared invalid. After the flush timer expires, the route is removed from the RIP database.

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

Default

timers 30 180 120

Parameters

update

Specifies the RIP update timer value in seconds expressed as a decimal integer.

Values

1 to 600

timeout

Specifies the RIP timeout timer value in seconds expressed as a decimal integer.

Values

1 to 1200

flush

Specifies the RIP flush timer value in seconds expressed as a decimal integer.

Values

1 to 1200

Platforms

All

timeslots

timeslots

Syntax

timeslots timeslots

no timeslots

Context

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

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

Full Context

configure port tdm e1 channel-group timeslots

configure port tdm ds1 channel-group timeslots

Description

This command defines the list of DS-0 timeslots to be used in the DS-1 or E-1 channel-group. The timeslots are defaulted as defined below when encap-type is set to/from atm. ATM channel groups do not allow timeslots to change.

The no form of this command removes DS-0 timeslots from a channel group.

Parameters

timeslots

Specifies the timeslot(s) to be associated with the channel group. The value can consist of a list of timeslots. Each member of the list can either be a single timeslot or a range of timeslots.

Values

1 to 24 for DS-1 interfaces (the full range is auto-configured for ATM channel groups and cannot be changed) 2 to 32 for E-1 interfaces (the 2 to 16,18 to 32 ranges are auto-configured for ATM channel groups and cannot be changed)

Platforms

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

timestamp

timestamp

Syntax

[no] timestamp

Context

[Tree] (config>system>management-interface>cli>md-cli>environment>prompt timestamp)

Full Context

configure system management-interface cli md-cli environment prompt timestamp

Description

This command displays the timestamp before the first prompt line.

The no form of this command suppresses the timestamp before the first prompt line.

Default

timestamp

Platforms

All

timestamp-format

timestamp-format

Syntax

timestamp-format timestamp-format

Context

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

Full Context

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

Description

This command configures the format of the timestamp used in the TWAMP Light PDU.This configuration places the requested timestamp format in the packet using the appropriate epoch. This is unrelated to any time distribution protocol being used to synchronize time between clocks.

Default

timestamp-format ntp

Parameters

parameter

Specifies the timestamp format to be used in the TWAMP Light PDU.

Values

ntp, ptp

Platforms

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

timing

timing

Syntax

timing frames-per-delta-t frames consec-delta-t deltas chli-threshold threshold

no timing

Context

[Tree] (config>oam-pm>session>ethernet>lmm>availability timing)

Full Context

configure oam-pm session ethernet lmm availability timing

Description

This command defines various availability parameters for LMM availability testing. This command does not define the probe interval. Validation occurs when the LMM test is activated using the no shutdown command. The maximum size of the availability window cannot exceed 100 seconds (100 000 milliseconds). LMM test activation fails if the availability window exceeds the maximum value.

The no form of this command restores the default values for all timing parameters, and uses those values to compute availability and set the loss frequency.

Parameters

frames

Specifies the number of SLM frames that define the size of the small measurement window. Each delta-t is marked as a high-loss interval or non-high-loss interval based on the flr-threshold. The size of the delta-t measurement is the product of the number of frames and the interval.

Values

1 to 50

Default

10

deltas

Specifies the number of consecutive delta-t measurement intervals that make up the sliding window over which availability and unavailability determined. Transitions from one state to another occurs when the consec-delta-t are in a new state. The sliding window cannot exceed 100 seconds.

Values

2 to 10

Default

10

threshold

Specifies the number of consecutive unavailable delta-t intervals that, when reached or exceeded, increments the CHLI counter. A CHLI counter is an indication that the sliding window is available but has crossed a threshold of consecutive unavailable delta-t intervals. A CHLI can only be incremented once during a sliding window and, by default, is incremented during times of availability.

Values

1 to 9

Default

5

Platforms

All

timing

Syntax

timing frames-per-delta-t frames consec-delta-t deltas interval milliseconds chli-threshold threshold

no timing

Context

[Tree] (config>oam-pm>session>ethernet>slm timing)

Full Context

configure oam-pm session ethernet slm timing

Description

This command defines various availability parameters and the probe spacing (interval) for the SLM frames. The maximum size of the availability window cannot exceed 10 s (10 000 ms).

The no form of this command installs the default values for all timing parameters and use those values to compute availability and set the SLM frequency. If an SLM test is in the no shutdown state, it always has timing parameters, default or operator configured.

Parameters

frames

Specifies the of SLM frames that define the size of the delta-t (small measurement window). Each delta-t is marked as available or unavailable based on the flr-threshold. The size of the delta-t measurement is the product of the number of frames and the interval.

Values

1 to 50

Default

10

deltas

Specifies the number of consecutive delta-t small measurement intervals that make up the sliding window over which availability and unavailability is determined. Transitions from one state to another occurs when the consec-delta-t is in a new state.

Values

2 to 10

Default

10

milliseconds

Specifies the number of milliseconds between the transmission of the SLM frames. By design, the default value for the SLM interval is different than the default interval for DMM.

Values

50, 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000

Default

100

threshold

Specifies the number of consecutive high loss intervals (unavailable delta-t) that when equal to or exceeded increments the CHLI counter. A CHLI counter is an indication that the sliding window is available but has crossed a threshold consecutive of unavailable delta-t intervals. A CHLI can only be incremented once during a sliding window and, by default, it is only incremented during times of availability.

Values

1 to 9

Default

5

Platforms

All

timing

Syntax

timing frames-per-delta-t frames consec-delta-t deltas chli-threshold threshold

no timing

Context

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

Full Context

configure oam-pm session ip twamp-light loss timing

Description

This command defines various availability parameters but not the probe interval. A single TWAMP-Light frame is used to collect both delay and loss metrics; the interval is common to both and as such not unique per metric type. Any TWAMP light test that is attempting to become active validates the configuration of the timing parameter regardless of which statistics are being recorded.

The no form of this command restores the default values for all timing parameters and use those values to compute availability and set the loss frequency.

Default

timing frames-per-delta-t 1 consec-delta-t 10 chli-threshold 5

Parameters

frames

Defines the size of the small measurement window. Each delta-t is marked as available of unavailable based on the flr-threshold. The size of the delta-t measurement is the product of the number of frames and the interval. This value defaults to a different value thank single probe per metric approaches.

Values

1 to 50

Default

1

deltas

Specifies the number of consecutive delta-t small measurement intervals that make up the sliding window over which availability and unavailability are determined. Transitions from one state to another occurs when the consec-delta-t are now in a new state. The sliding window cannot exceed 100 seconds.

Values

2 to 10

Default

10

threshold

Specifies the number of consecutive high loss intervals (unavailable delta-t) that when equal to or exceeded increments the CHLI counter. A CHLI counter is an indication that the sliding window is available but has crossed a threshold consecutive of unavailable delta-t intervals. A CHLI can only be incremented once during a sliding window and, by default, is only incremented during times of availability.

Values

1 to 9

Default

5

Platforms

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

tls

tls

Syntax

tls

Context

[Tree] (config>system>security tls)

Full Context

configure system security tls

Description

This command configures TLS parameters.

Platforms

All

tls-client-profile

tls-client-profile

Syntax

tls-client-profile profile-name

no tls-client-profile

Context

[Tree] (config open-flow of-switch of-controller tls-client-profile)

Full Context

configure open-flow of-switch of-controller tls-client-profile

Description

This command configures the use of Transport Layer Security (TLS) on the control channel to a given OpenFlow controller for this OpenFlow switch.

The no form of this command deletes removed TLS from the control channel.

Parameters

profile-name

Specifies the use of TLS for the control channel. A named TLS profile must also be specified, referring to a TLS profile configured under config>system>security>tls.

Platforms

All

tls-client-profile

Syntax

tls-client-profile name

no tls-client-profile

Context

[Tree] (config system telemetry destination-group tls-client-profile)

[Tree] (config system grpc-tunnel destination-group tls-client-profile)

Full Context

configure system telemetry destination-group tls-client-profile

configure system grpc-tunnel destination-group tls-client-profile

Description

This command configures a TLS client profile to a destination group.

This command is mutually exclusive with the allow-unsecured-connection command.

The no form of this command removes the TLS client profile.

Default

no tls-client-profile

Parameters

name

Specifies the TLS client profile name, up to 32 characters.

Platforms

All

tls-client-profile

Syntax

tls-client-profile tls-client-profile

no tls-client-profile

Context

[Tree] (config log syslog tls-client-profile)

[Tree] (config service vprn log syslog tls-client-profile)

Full Context

configure log syslog tls-client-profile

configure service vprn log syslog tls-client-profile

Description

This command specifies the Transport Layer Security (TLS) client profile used to encrypt syslog communications. When configured, syslog messages are sent using TLS.

Any change to this command results in a brief interruption of the event log, which may cause the loss of a few syslog messages.

The no form of this command removes TLS encryption of syslog communications and sends syslog messages over UDP.

Parameters

tls-client-profile

Specifies the name of a TLS profile configured in the config>system>security>tls context, up to 32 characters.

Platforms

All

tls-client-profile

Syntax

tls-client-profile profile-name

no tls-client-profile

Context

[Tree] (config router pcep pcc peer tls-client-profile)

Full Context

configure router pcep pcc peer tls-client-profile

Description

This command configures a TLS client profile on the PCC. When the TLS profile is configured, the PCC tries to establish a PCEP connection with the PCE over TLS. Because SR OS supports a strict TLS-only mode, both the PCE and PCC must support TLS. If a TLS failure occurs, the connection over TLS is closed and a new connection is retried within 60 seconds.

The no form of this command removes TLS encryption from the communication between this PCC and the PCE.

Default

no tls-client-profile

Parameters

profile-name

Specifies the TLS client profile name, up to 32 characters.

Platforms

All

tls-extension

tls-extension

Syntax

tls-extension

Context

[Tree] (config>app-assure>group>http-enrich tls-extension)

Full Context

configure application-assurance group http-enrich tls-extension

Description

Commands in this context configure the TLS extension field name.

Platforms

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

tls-profile

tls-profile

Syntax

tls-profile tls-profile-name

no tls-profile

Context

[Tree] (config system security ldap server tls-profile)

Full Context

configure system security ldap server tls-profile

Description

This command attaches a TLS client profile to the LDAP client. The parameter in the TLS profile is used to encrypt the LDAP connection to the server. Each LDAP server can use its own TLS profile.

When a TLS profile is assigned, the LDAP application will send encrypted PDUs from the client to the LDAP server. If TLS is operationally down, the LDAP application should not send any PDUs.

The no form of this command removes the TLS profile from LDAP and disables the TLS encryption from LDAP.

Parameters

tls-profile-name

Specifies the TLD profile for encryption.

Platforms

All

tls-re-negotiate-timer

tls-re-negotiate-timer

Syntax

tls-re-negotiate-timer timer-min

no tls-re-negotiate-timer

Context

[Tree] (config>system>security>tls>server-tls-profile tls-re-negotiate-timer)

Full Context

configure system security tls server-tls-profile tls-re-negotiate-timer

Description

This command configures the timed interval after which the server is triggered to send a Hello request message to all clients and force a renegotiation of the symmetric encryption key. When an interval of 0 is configured, the server will never send a hello request message.

Default

tls-re-negotiate-timer 0

Parameters

timer-min

Specifies the interval, in minutes, after which the server is triggered to send a Hello request message.

Values

0 to 65000

Platforms

All

tls-server-profile

tls-server-profile

Syntax

tls-server-profile name

no tls-server-profile

Context

[Tree] (config system grpc tls-server-profile)

Full Context

configure system grpc tls-server-profile

Description

This command adds a configured TLS server profile to the gRPC session. The TLS server is used for encryption of the gRPC session. gRPC will not transmit any PDUs if there is a TLS server profile assigned to it and the TLS connection is down.

The no form of this command removes the specified TLS server profile from the gRPC session.

Parameters

name

Specifies the name of the TLS server profile configured under the config>system>security>tls context.

Platforms

All

tls-server-profile

Syntax

tls-server-profile name

no tls-server-profile

Context

[Tree] (config router pcep pce tls-server-profile)

Full Context

configure router pcep pce tls-server-profile

Description

This command configures a TLS server profile on the PCE. When a TLS server profile is configured, the PCE accepts TLS handshakes from the PCC. Because SR OS supports a strict TLS mode only, both the PCE and the PCC must support TLS. If a TLS failure occurs, the connection over TLS is closed and a new connection is retried within 60 seconds.

The no form of this command removes the specified TLS server profile.

Default

no tls-server-profile

Parameters

name

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

Platforms

VSR-NRC

tls-wait-timer

tls-wait-timer

Syntax

tls-wait-timer tls-wait-timer

no tls-wait-timer

Context

[Tree] (config>router>pcep>pcc>peer tls-wait-timer)

Full Context

configure router pcep pcc peer tls-wait-timer

Description

This command configures the time that the PCC waits before declaring a TLS handshake failure if the handshake is not established.

The no form of this command reverts to the default.

Default

tls-wait-timer 60

Parameters

tls-wait-timer

Specifies the time, in seconds.

Values

60 to 255

Platforms

All

tls13-cipher

tls13-cipher

Syntax

tls13-cipher index name cipher-suite-code

no tls13-cipher index

Context

[Tree] (config>system>security>tls>server-cipher-list tls13-cipher)

[Tree] (config>system>security>tls>client-cipher-list tls13-cipher)

Full Context

configure system security tls server-cipher-list tls13-cipher

configure system security tls client-cipher-list tls13-cipher

Description

This command configures the TLS 1.3-supported ciphers that are used by the client and server.

The no form of this command removes the cipher suite.

Parameters

index

Specifies the index number, which provides the location of the cipher in the negotiation list. The lower index numbers are higher in the negotiation list, and the higher index numbers are at the bottom of the list.

Values

1 to 255

cipher-suite-code
Specifies the cipher suite code.
Values

tls-aes128-gcm-sha256

tls-aes256-gcm-sha384

tls-chacha20-poly1305-sha256

tls-aes128-ccm-sha256

tls-aes128-ccm8-sha256

Platforms

All

tls13-group

tls13-group

Syntax

tls13-group index name group-suite-code

no tls13-group index

Context

[Tree] (config>system>security>tls>server-group-list tls13-group)

[Tree] (config>system>security>tls>client-group-list tls13-group)

Full Context

configure system security tls server-group-list tls13-group

configure system security tls client-group-list tls13-group

Description

This command configures the TLS 1.3-supported group suite codes sent by the client or server in their respective Hello messages.

SR OS supports the use of Elliptic-curve Diffie-Hellman Ephemeral (ECDHE) groups.

The no form of this command removes the group suite code.

Parameters

index

Specifies the index number , which provides the location of the group suite code in the client or server group list. The lower index numbers are higher in the list and the higher index numbers are at the bottom of the list.

Values

1 to 255

group-suite-code

Specifies the group suite code.

Values

tls-ecdhe-256

tls-ecdhe-384

tls-ecdhe-521

tls-x25519

tls-x448

Platforms

All

tls13-signature

tls13-signature

Syntax

tls13-signature index name signature-suite-code

no tls13-signature index

Context

[Tree] (config>system>security>tls>client-signature-list tls13-signature)

[Tree] (config>system>security>tls>server-signature-list tls13-signature)

Full Context

configure system security tls client-signature-list tls13-signature

configure system security tls server-signature-list tls13-signature

Description

This command configures the TLS 1.3-supported signature suite codes sent by the client or server in their respective Hello messages.

The no form of this command removes the signature suite code.

Parameters

index

Specifies the index number, which provides the location of the signature suite code in the client or server group list. The lower index numbers are higher in the list, and the higher index numbers are at the bottom of the list.

Values

1 to 255

signature-suite-code

Specifies the signature suite code.

Values

tls-rsa-pkcs1-sha256

tls-rsa-pkcs1-sha384

tls-rsa-pkcs1-sha512

tls-ecdsa-secp256r1-sha256

tls-ecdsa-secp384r1-sha384

tls-ecdsa-secp521r1-sha512

tls-rsa-pss-rsae-sha256

tls-rsa-pss-rsae-sha384

tls-rsa-pss-rsae-sha512

tls-rsa-pss-pss-sha256

tls-rsa-pss-pss-sha384

tls-rsa-pss-pss-sha512

tls-ed25519

tls-ed448

Platforms

All

to

to

Syntax

to [ip-address | node-id [a.b.c.d | 1...4294967295]]

Context

[Tree] (config>router>mpls>lsp to)

Full Context

configure router mpls lsp to

Description

This command specifies the IP address or MPLS-TP node-id of the egress router for the LSP. This command is mandatory to create an LSP.

An IP address for which a route does not exist is allowed in the configuration. If the LSP signaling fails because the destination is not reachable, an error is logged and the LSP operational status is set to down.

For a non MPLS-TP LSP, the to ip-address can be an IP address of a network IP interface, the system interface, or a loopback interface of the egress router. When used in a SDP, if the LSP to address does not match the SDP address, the LSP is not included in the SDP definition.

For an MPLS-TP LSP, the to node-id may be either in 4-octet IPv4 address format, or a 32-bit unsigned integer. This command is mandatory to create an MPLS-TP LSP. A value of zero is invalid. This to address is used in the MPLS-TP LSP ID, and the MPLS-TP MEP ID for the LSP.

Default

no default

Parameters

ip-address

Specifies the IP address of the egress router. When the LSP type is sr-te, then an IPv6 address can be used.

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 (hexadecimal)

d — 0 to 255 (decimal)

node-id a.b.c.d. | 1...4294967295

4-octet IPv4 formatted or unsigned 32-bit integer MPLS-TP node-id of the egress router.

Platforms

All

to

Syntax

to ip-address

Context

[Tree] (config>router>mpls>static-lsp to)

Full Context

configure router mpls static-lsp to

Description

This command specifies the IP address of the egress router for the static LSP. When creating an LSP this command is required. The to IP address may be the address of a local interface, the system IP interface, or of a loopback interface of the egress router. When used in a SDP and the to address does not match the far-end SDP address, the LSP is not included in the SDP definition.

Parameters

ip-address

Specifies the system IP address of the egress router.

Platforms

All

to

Syntax

to memory [size]

to netconf [size]

to session

to snmp [size] [send-using-vprn service-id]

Context

[Tree] (config>li>log>log-id to)

Full Context

configure li log log-id to

Description

Commands in this context configure the destination type for the event log.

The source of the data stream must be specified in the from command prior to configuring the destination with the to command.

The to command cannot be modified or re-entered. If the destination or maximum size of a memory log, NETCONF log, or SNMP log needs to be modified, the log ID must be removed and then re-created.

Parameters

memory

Specifies that log events are directed to a memory file. A memory file is a circular buffer; when the file is full, each new entry replaces the oldest entry in the log. If the optional size parameter is not configured, the default value is used.

Default

100

netconf

Specifies that log events are directed to a NETCONF session as notifications. A NETCONF client can subscribe to a NETCONF log using the configured netconf-stream stream-name for the log in a subscription request. One or more NETCONF sessions can subscribe to a NETCONF log or stream.

session

Specifies that log events are directed to the current console or telnet session. This command is only valid for the duration of the session. When the session is terminated, the to session configuration is removed. A log ID with a session destination is saved in the configuration file but the to session part is not stored.

snmp

Specifies that log events are directed to the snmp-trap-group associated with the log ID. A local circular memory log is maintained for SNMP logs.

size

The size parameter indicates the number of events that can be stored into memory.

Default

100

Values

50 to 1024

send-using-vprn service-id

Configures the lawful intercept (LI) SNMP notifications to transmit in a VPRN. The parameter is the service ID of the VPRN. This configuration is useful when doing management of LI using a VPRN.

The specified VPRN service must exist. After an LI log is configured using the send-using-vprn command, the VPRN service cannot be deleted without removing the LI log ID first.

When unconfigured, the outgoing routing instance of LI SNMP notifications is determined by the configure log route-preference command.

Platforms

All

to

Syntax

to ipv4-address

no to

Context

[Tree] (config>oam-pm>session>mpls>lsp>rsvp-auto to)

Full Context

configure oam-pm session mpls lsp rsvp-auto to

Description

This command specifies an IPv4 address used (with the LSP template) to identify the LSP to be tested.

One of three mandatory configuration statements that are required to identify automatically created RSVP LSPs, using config>router>mpls>lsp-template. The config>router>mpls>auto-lsp>lsp-template links three distinct functions, the config>router>policy-options>prefix-list, config>router>policy-options>policy-statement>entry>from and the config>router>mpls> lsp-template. The to address is the same address configured as the from address for the config>router>policy-options>policy-statement>entry>from. The required identifiers are from, lsp-template and to, all under this node.

Parameters

ipv4-address

Specifies the IPv4 address.

Values

a.b.c.d

Platforms

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

to

Syntax

to file file-id

Context

[Tree] (config>log>accounting-policy to)

Full Context

configure log accounting-policy to

Description

This command specifies the destination for the accounting records selected for the accounting policy.

Parameters

file-id

Specifies the destination for the accounting records selected for this destination. The characteristics of the file ID must have already been defined in the config>log>file context. A file ID can only be used once.

The file is generated when the file policy is referenced. This command identifies the type of accounting file to be created. The file definition defines its characteristics.

If the to command is executed while the accounting policy is in operation, then it becomes active during the next collection interval.

Values

1 to 99

Platforms

All

to

Syntax

[no] to

Context

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

Full Context

configure router policy-options policy-statement entry to

Description

This command creates the context to configure export policy match criteria based on a route’s destination or the protocol into which the route is being advertised.

If no condition is specified, all route destinations are considered to match.

The to command context only applies to export policies. If it is used for an import policy, match criteria is ignored.

The no form of this command deletes export match criteria for the route policy statement entry.

Platforms

All

to

Syntax

to cli [size]

to console

to file log-file-id

to memory [size]

to netconf [size]

to session

to snmp [size]

to syslog syslog-id

Context

[Tree] (config>log>log-id to)

Full Context

configure log log-id to

Description

This command specifies a destination for the log event data.

The source of the data stream must be specified in the from command before configuring the destination with the to command.

The to command cannot be modified or re-entered. If the destination or maximum size of an SNMP or memory log needs to be modified, the log ID must be removed and then recreated.

Parameters

cli

Specifies that log events are directed to any subscribed CLI session. Subscribe to a CLI log from within a CLI session using the tools>perform>log>subscribe-to log-id log-id command. Events are sent to the CLI session for the duration of that CLI session, or until an unsubscribe-from command is issued. A local circular memory log is maintained for CLI logs.

console

Specifies that log events events are directed to the console port. If the console is not connected, all the entries are dropped.

file log-file-id

Specifies that log events are directed to a file with the specified log-file-id. The characteristics of the log-file-id referenced in this parameter must have already been defined in the config>log>file file-id context. When the file-id location parameter is modified, log files are not written to the new location until a rollover occurs or the log is manually cleared. A rollover can be forced by using the clear>log command. Subsequent log entries are then written to the new location. If a rollover does not occur or the log is not cleared, the old location continues to be used.

Values

1 to 99, name (up to 64 characters max)

memory

Specifies that log events are directed to a memory file. A memory file is a circular buffer; when the file is full, each new entry replaces the oldest entry in the log. If the optional size parameter is not configured, the default value is used.

Default

100

netconf

Specifies that log events are directed to a NETCONF session as notifications. A NETCONF client can subscribe to a NETCONF log using the configured netconf-stream stream-name for the log in a subscription request. One or more NETCONF sessions can subscribe to a NETCONF log or stream.

session

Specifies that log events are directed to the current console or telnet session. This command is only valid for the duration of the session. When the session is terminated, the to session configuration is removed. A log ID with a session destination is saved in the configuration file but the to session part is not stored.

size

Specifies the maximum size of the log data destination, in bytes.

Values

50 to 3000

snmp

Specifies that log events are directed to the snmp-trap-group associated with the log ID. A local circular memory log is maintained for SNMP logs.

syslog syslog-id

Specifies that log events are directed to the specified syslog collector. To remain consistent with the standards governing syslog, messages to syslog are truncated to 1024 bytes. The characteristics of the syslog-id referenced in this parameter must have already been defined in the config>log>syslog syslog-id context.

Values

1 to 10

Platforms

All

to

Syntax

to ipv4-address

no to

Context

[Tree] (config>oam-pm>session>ip>tunnel>mpls>rsvp-te-auto to)

Full Context

configure oam-pm session ip tunnel mpls rsvp-te-auto to

Description

This command configures the termination point of the RSV LSP. Configure the following three commands to identify an RSVP-TE Auto LSP: from, to, and lsp-template.When all three of these values are configured, the specific RSVP LSP can be identified and the test packets can be carried across the tunnel

The no form of this command removes the IPv4 address.

Parameters

ipv4-address

Specifies IPv4 address.

Values

ipv4-address: a.b.c.d (host bits must be 0)

Platforms

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

to-aa-sub-counters

to-aa-sub-counters

Syntax

to-aa-sub-counters

no to-aa-sub-counters

Context

[Tree] (config>log>acct-policy>cr>aa to-aa-sub-counters)

Full Context

configure log accounting-policy custom-record aa-specific to-aa-sub-counters

Description

Commands in this context configure Application Assurance "to subscriber” counter parameters and only applies to the 7750 SR.

The no form of this command excludes the "to subscriber” count.

Platforms

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

to-client-options

to-client-options

Syntax

to-client-options

Context

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

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host to-client-options)

Full Context

configure subscriber-mgmt local-user-db ipoe host to-client-options

configure subscriber-mgmt local-user-db ppp host to-client-options

Description

Commands in this context configure DHCP options to send to the client.

Platforms

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

to-sap

to-sap

Syntax

to-sap sap-id

no to-sap

Context

[Tree] (config>service>vpls>sap>snooping>mvr to-sap)

Full Context

configure service vpls sap snooping mvr to-sap

Description

In some situations, the multicast traffic should not be copied from the MVR VPLS to the SAP on which the IGMP message was received (standard MVR behavior) but to another SAP.

This command configures the SAP to which the multicast data needs to be copied.

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

Parameters

sap-id

Specifies the SAP to which multicast channels should be copied.

to-sap

Syntax

to-sap sap-id

no to-sap

Context

[Tree] (config>service>vpls>sap>igmp-snooping>mvr to-sap)

Full Context

configure service vpls sap igmp-snooping mvr to-sap

Description

In some situations, the multicast traffic should not be copied from the MVR VPLS to the SAP on which the IGMP message was received (standard MVR behavior) but to another SAP.

This command configures the SAP to which the multicast data needs to be copied.

Default

no to-sap

Parameters

sap-id

Specifies the SAP to which multicast channels should be copied

Platforms

All

to-server-options

to-server-options

Syntax

[no] to-server-options

Context

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

Full Context

configure subscriber-mgmt local-user-db ipoe host to-server-options

Description

Commands in this context configure DHCP options to send to the server.

Platforms

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

to-subscriber

to-subscriber

Syntax

to-subscriber

Context

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

Full Context

configure isa application-assurance-group qos egress to-subscriber

Description

Commands in this context configure Quality of Service for this application assurance group to-subscriber logical port, traffic destined to AA subscribers and entering an application assurance engine.

Platforms

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

tod-override

tod-override

Syntax

tod-override tod-override-id [create]

no tod-override tod-override-id

Context

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

Full Context

configure application-assurance group policer tod-override

Description

This commands creates a time of day override policy for a given policer. Up to 8 overrides can be configured per policer. Rate/mbs/cbs/flow-rate/flow-count configured in each override-id will override the default policer values at the specified time of day configured in the override.

Parameters

tod-override-id

Specifies the time of day override ID.

Values

1 to 255

create

Keyword used to create the time of day override policy.

Platforms

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

tolerance

tolerance

Syntax

tolerance [seconds | forever]

no tolerance

Context

[Tree] (config>system>security>keychain>direction>bi>entry tolerance)

[Tree] (config>system>security>keychain>direction>uni>receive>entry tolerance)

Full Context

configure system security keychain direction bi entry tolerance

configure system security keychain direction uni receive entry tolerance

Description

This command configures the amount of time that an eligible receive key should overlap with the active send key or to never expire.

Parameters

seconds

Specifies the duration that an eligible receive key overlaps with the active send key.

Values

0 to 4294967294 seconds

forever

Specifies that an eligible receive key overlap with the active send key forever.

Platforms

All

tos-marking-state

tos-marking-state

Syntax

tos-marking-state {trusted | untrusted}

no tos-marking-state

Context

[Tree] (config>service>ies>sub-if>grp-if tos-marking-state)

[Tree] (config>service>vprn>sub-if>grp-if tos-marking-state)

[Tree] (config>service>ies>if tos-marking-state)

[Tree] (config>service>vprn>interface tos-marking-state)

Full Context

configure service ies subscriber-interface group-interface tos-marking-state

configure service vprn subscriber-interface group-interface tos-marking-state

configure service ies interface tos-marking-state

configure service vprn interface tos-marking-state

Description

This command is used to alter the default trusted state to a non-trusted state. When unset or reverted to the trusted default, the ToS field are not remarked by egress network IP interfaces unless the egress network IP interface has the remark-trusted state set, in which case the egress network interface treats all VPRN and network IP interface as untrusted.

When the ingress interface is set to untrusted, all egress network IP interfaces remark IP packets received on the network interface according to the egress marking definitions on each network interface. The egress network remarking rules also apply to the ToS field of IP packets routed using IGP shortcuts (tunneled to a remote next-hop). However, the tunnel QoS markings are always derived from the egress network QoS definitions.

Egress marking and remarking is based on the internal forwarding class and profile state of the packet once it reaches the egress interface. The forwarding class is derived from ingress classification functions. The profile of a packet is either derived from ingress classification or ingress policing.

The default marking state for network IP interfaces is trusted. This is equivalent to declaring no tos-marking-state on the network IP interface. When undefined or set to tos-marking-state trusted, the trusted state of the interface will not be displayed when using show config or show info unless the detail parameter is given. The save config command will not store the default tos-marking-state trusted state for network IP interfaces unless the detail parameter is also specified.

The no form of this command restores the trusted state to a network IP interface. This is equivalent to executing the tos-marking-state trusted command.

Default

tos-marking-state trusted

Parameters

trusted

The default prevents the ToS field to not be remarked by egress network IP interfaces unless the egress network IP interface has the remark-trusted state set.

untrusted

Specifies that all egress network IP interfaces will remark IP packets received on the network interface according to the egress marking definitions on each network interface.

Platforms

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

  • configure service vprn subscriber-interface group-interface tos-marking-state
  • configure service ies subscriber-interface group-interface tos-marking-state

All

  • configure service ies interface tos-marking-state
  • configure service vprn interface tos-marking-state

tos-marking-state

Syntax

tos-marking-state {trusted | untrusted}

no tos-marking-state

Context

[Tree] (config>service>vprn>nw-if tos-marking-state)

Full Context

configure service vprn network-interface tos-marking-state

Description

This command is used to alter the default trusted state to a non-trusted state. When unset or reverted to the trusted default, the ToS field will not be remarked by egress network IP interfaces unless the egress network IP interface has the remark-trusted state set, in which case the egress network interface treats all VPRN and network IP interface as untrusted.

When the ingress interface is set to untrusted, all egress network IP interfaces will remark IP packets received on the network interface according to the egress marking definitions on each network interface. The egress network remarking rules also apply to the ToS field of IP packets routed using IGP shortcuts (tunneled to a remote next-hop). However, the tunnel QoS markings are always derived from the egress network QoS definitions. Egress marking and remarking is based on the internal forwarding class and profile state of the packet once it reaches the egress interface. The forwarding class is derived from ingress classification functions. The profile of a packet is either derived from ingress classification or ingress policing.

The default marking state for network IP interfaces is trusted. This is equivalent to declaring no tos-marking-state on the network IP interface. When undefined or set to tos-marking-state trusted, the trusted state of the interface will not be displayed when using show config or show info unless the detail parameter is given. The save config command will not store the default tos-marking-state trusted state for network IP interfaces unless the detail parameter is also specified.

The no tos-marking-state command is used to restore the trusted state to a network IP interface. This is equivalent to executing the tos-marking-state trusted command.

Default

tos-marking-state trusted

Parameters

trusted

The default prevents the ToS field to not be remarked by egress network IP interfaces unless the egress network IP interface has the remark-trusted state set.

untrusted

Specifies that all egress network IP interfaces will remark IP packets received on the network interface according to the egress marking definitions on each network interface.

Platforms

All

tos-marking-state

Syntax

tos-marking-state {trusted | untrusted}

no tos-marking-state

Context

[Tree] (config>router>if tos-marking-state)

Full Context

configure router interface tos-marking-state

Description

This command is used on a network IP interface to alter the default trusted state to a non-trusted state. When unset or reverted to the trusted default, the ToS field will not be remarked by egress network IP interfaces unless the egress network IP interface has the remark-trusted state set, in which case the egress network interface treats all IES and network IP interface as untrusted. When the ingress network IP interface is set to untrusted, all egress network IP interfaces will remark IP packets received on the network interface according to the egress marking definitions on each network interface. The egress network remarking rules also apply to the ToS field of IP packets routed using IGP shortcuts (tunneled to a remote next-hop). However, the tunnel QoS markings are always derived from the egress network QoS definitions. Egress marking and remarking is based on the internal forwarding class and profile state of the packet once it reaches the egress interface. The forwarding class is derived from ingress classification functions. The profile of a packet is either derived from ingress classification or ingress policing. The default marking state for network IP interfaces is trusted. This is equivalent to declaring no tos-marking-state on the network IP interface. When undefined or set to tos-marking-state trusted, the trusted state of the interface will not be displayed when using show config or show info unless the detail parameter is given. The save config command will not store the default tos-marking-state trusted state for network IP interfaces unless the detail parameter is also specified.

The no form of this command is used to restore the trusted state to a network IP interface. This is equivalent to executing the tos-marking-state trusted command.

Default

tos-marking-state trusted

Parameters

trusted

Specifies that the default prevents the ToS field to not be remarked by egress network IP interfaces unless the egress network IP interface has the remark-trusted state set

untrusted

Specifies that all egress network IP interfaces will remark IP packets received on the network interface according to the egress marking definitions on each network interface.

Platforms

All

total

total

Syntax

total percent

Context

[Tree] (config>isa>video-group>watermark>session total)

[Tree] (config>isa>video-group>watermark>bandwidth total)

Full Context

configure isa video-group watermark session total

configure isa video-group watermark bandwidth total

Description

This command sets the watermark to trigger the SNMP trap if the combined FCC and RET bandwidth or session exceeds the configured percentage. The bandwidth is the available egress bandwidth of the ISA. The SNMP trap is cleared when the consumption is lowered by 10%. For example, if the system resource of the bandwidth available is 10 Gb/s and the watermark is configured to be 90%, the SNMP trap is raised as the bandwidth exceeds 9 Gb/s (90% of 10 Gb/s). The SNMP trap is cleared when the bandwidth drops below 8.1 Gb/s (10% of 9 Gb/s = 0.9 Gb/s, and 9 Gb/s - 0.9 Gb/s = 8.1 Gb/s). The default value of the watermark is set at 90% of the system resources for both bandwidth and session.

Default

total 90

Parameters

percent

Specifies the percentage of the system resources per ISA.

Values

1 to 99

Platforms

7450 ESS, 7750 SR, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

total-capacity

total-capacity

Syntax

total-capacity capacity

no total-capacity

Context

[Tree] (config>mcast-mgmt>chassis-level>plane-capacity total-capacity)

Full Context

configure mcast-management chassis-level per-mcast-plane-capacity total-capacity

Description

This command configures the total multicast plane capacity supported individually by all switch fabric multicast planes.

The multicast plane capacity is determined based on the provisioned line cards and switch fabrics in the chassis.

The no form of this command reverts to the default.

Parameters

capacity

Specifies the multicast plane capacity in Mb/s.

Values

2000, 4000, 5250, 8250, 15000, 19000, dynamic (Specifies that multicast plane capacity is determined based on provisioned line cards and switch fabrics in the chassis.)

Platforms

7450 ESS, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-7/12/12e, 7750 SR-s, 7950 XRS, VSR

total-flow-duration

total-flow-duration

Syntax

[no] total-flow-duration

Context

[Tree] (config>log>acct-policy>cr>aa>aa-sub-cntr total-flow-duration)

Full Context

configure log accounting-policy custom-record aa-specific aa-sub-counters total-flow-duration

Description

This command includes the total flow duration flow count in the AA subscriber's custom record. This command only applies to the 7750 SR.

The no form of this command excludes the total flow duration flow count.

Platforms

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

total-flows-completed-count

total-flows-completed-count

Syntax

[no] total-flows-completed-count

Context

[Tree] (config>log>acct-policy>cr>aa>aa-sub-cntr total-flows-completed-count)

Full Context

configure log accounting-policy custom-record aa-specific aa-sub-counters total-flows-completed-count

Description

This command includes the total flows completed count in the AA subscriber's custom record. This command only applies to the 7750 SR.

The no form of this command excludes the total flow duration flow count.

Platforms

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

tp-tunnel-id-range

tp-tunnel-id-range

Syntax

tp-tunnel-id-range start-id end-id

no tp-tunnel-id-range

Context

[Tree] (config>router>mpls>mpls-tp tp-tunnel-id-range)

Full Context

configure router mpls mpls-tp tp-tunnel-id-range

Description

This command configures the range of MPLS tunnel IDs reserved for MPLS-TP LSPs. The maximum difference between the start-id and end-id is 4K.

The tunnel ID referred to here is the RSVP-TE tunnel ID. This maps to the MPLS-TP Tunnel Number. There are some cases where the dynamic LSPs may have caused fragmentation to the number space such that contiguous range [end-id start-id] is not available. In these cases, the command will fail.

There are no default values for the start-id and end-id of the tunnel id range, and they must be configured to enable MPLS-TP.

Default

no tp-tunnel-id-range

Parameters

start-id

Specifies the start ID.

Values

1 to 61440

end-id

Specifies the end ID.

Values

1 to 61440

Platforms

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

trace

trace

Syntax

trace sap sap-id [mac ieee-address] [circuit-id circuit-id] [remote-id remote-id] [profile trace-profile-name] [trace-existing-sessions] [max-jobs num] [name trace-name]

trace mac ieee-address [sap sap-id] [circuit-id circuit-id] [remote-id remote-id] [profile trace-profile-name] [trace-existing-sessions] [max-jobs num] [name trace-name]

trace circuit-id circuit-id [profile trace-profile-name] [trace-existing-sessions] [max-jobs num] [name trace-name]

trace remote-id remote-id [profile trace-profile-name] [trace-existing-sessions] [max-jobs num] [name trace-name]

no trace [sap sap-id] [mac ieee-address] [{circuit-id circuit-id | remote-id remoteid}]

no trace name trace-name

Context

[Tree] (debug>call-trace>ipoe trace)

Full Context

debug call-trace ipoe trace

Description

This command enables tracing for IPoE sessions specified by the configured parameters. This command can trace a single session or multiple sessions, and can use wildcard characters.

This command can be executed multiple times to start multiple traces. When rules overlap, such as for a wildcard SAP and a specific SAP, the rule that a specific trace is associated with cannot be guaranteed.

The no form of this command prevents new traces from being configured and terminates all trace jobs that were previously started using the trace command.

Parameters

circuit-id

Specifies a circuit ID that is used to filter sessions to trace. The circuit-id and remote-id parameters are mutually exclusive.

ieee-address

Specifies a MAC address that is used to identify a session to trace, in the format "ab:cd:ef:01:23:45”. A wildcard character can be used to match all remaining octets; for example, the format "ab:cd:ef:*” can be used to filter by OUI.

num

Specifies the maximum number of jobs that may be started with this rule.

Values

1 to 50

Default

1

remote-id

Specifies a remote ID that is used to filter sessions to trace. The remote-id and circuit-id parameters are mutually exclusive.

sap-id

Specifies a SAP to trace. The following formats are accepted:

  • port/lag/pw-port:svlan.cvlan

  • port/lag/pw-port:vlan

  • port/lag/pw-port

  • port/lag/pw-port:vlan.*

  • port/lag/pw-port:* (also matches *.*)

trace-existing-sessions

Specifies that existing IPoE sessions is traced. If this parameter is not included, only new IPoE sessions is traced.

trace-name

Specifies the name by which the trace is referenced, up to 16 characters.

trace-profile-name

Specifies the name of the trace profile to be applied. The default parameters is used if a trace profile is not specified.

Platforms

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

trace-profile

trace-profile

Syntax

trace-profile profile-name [create]

no trace-profile profile-name

Context

[Tree] (config call-trace trace-profile)

Full Context

configure call-trace trace-profile

Description

This command creates a profile that can be applied to a specific trace job.

Parameters

profile-name

Specifies the unique name of the call trace profile.

create

Keyword used to create the trace profile instance. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

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

trace-string

trace-string

Syntax

trace-string [trace-string]

no trace-string

Context

[Tree] (config>port>sonet-sdh>path trace-string)

Full Context

configure port sonet-sdh path trace-string

Description

This command specifies that a J1-path-trace that identifies the circuit is inserted continuously at source. This can be checked against the expected value by the receiver. If no trace string is entered then a null string is used.

The no form of this command resets the string to its default.

This command is supported on TDM satellite.

Default

The default J1 value is Alcatel XXX YYY where XXX is the platform number, such as "7750” or "7450”, and YYY is the platform acronym, such as "SR” or "ESS”. The value does not change when the encap-type changes. The J1 string contains all zeros for a non-provisioned path.

Parameters

trace-string

Specifies either a string up to 62 bytes for SONET or 15 bytes for SDH. If the string contains spaces, enclose it in quotation marks. String 'zeros’ will send all zeros in the J1 bytes.

Platforms

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

traceroute

traceroute

Syntax

Context

[Tree] (traceroute)

Full Context

traceroute

Description

This command determines the route to a destination address. DNS lookups for the responding hosts are enabled by default.

Parameters

candidate-path

Specifies a candidate path of the SRv6 policy to traceroute. The candidate path does not need to be the currently active candidate path.

dest-port-udp-fixed

Specifies that the destination UDP port number should not increment with each packet transmitted. By default, the UDP traceroute starts with destination UDP port 33434 and each subsequent packet sent to this destination UDP port increases by 1. The next packet uses UDP seat port 33435, the next 33436, and so on.

For a UDP test, this parameter prevents the per-transmitted packet increment of the destination UDP port number. The TCP protocol does not increment the destination TCP port, using a single destination TCP port for all traceroute packets for the test.

decode

Perform additional original datagram parsing functions. This parameter must be used with the detail parameter.

detail

Specifies to display additional information about the resulting packet.

distinguisher
Specifies the distinguisher of the SRv6 policy candidate path to send the traceroute probe on. This parameter must be configured if protocol-owner is configured to bgp.
Values

1 to 4294967295

dns-name

Specifies the DNS name, up to 63 characters, of the far-end device on which to send the traceroute request message.

endpoint ipv6-address
Specifies an SRv6 policy for a specific endpoint as the target of the traceroute.
Values

ipv6-address:

x:x:x:x:x:x:x:x

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

x:

[0 to FFFF]H

d:

[0 to 255]D

ip-address

Specifies the far-end IP address on which to send the traceroute request message in dotted decimal notation.

Values

ipv4-address:

a.b.c.d

ipv6-address:

x:x:x:x:x:x:x:x

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

x:

[0 to FFFF]H

d:

[0 to 255]D

max-ttl

Specifies the maximum Time-To-Live (TTL) value to include in the traceroute request, expressed as a decimal integer.

Values

1 to 255

Default

30

milliseconds

Specifies the time in milliseconds to wait for a response to a probe, expressed as a decimal integer.

Values

1 to 60000

Default

5000

min-ttl

Specifies the IP TTL in the initial traceroute packet to target a specific node or starting node along the path.

Values

1 to 255

Default

1

no-dns

Specifies that, when the no-dns keyword is specified, DNS lookups of the responding hosts are not performed, and only the IP addresses are printed.

original-datagram

Parse the returned original datagram including any IPv6 and SRH header information.

pad-size

Specifies the number of bytes added to the UDP or TCP payload.

Values

0 to 9786

Default

0

port-number

Specifies the transport protocol destination port number.

Values

1 to 65535

Default

33434

preference
Specifies the preference of the SRv6 policy candidate path to send the traceroute probe on.
Values

0 to 4294967295

Default

100

probes-per-hop

Specifies the number of probes per hop.

Values

1 to 10

Default

3

protocol-owner
Specifies the protocol owner of the SRv6 policy candidate path to traceroute.
Values

bgp — Specifies a BGP SRv6 policy.

static — Specifies a locally configured static SRv6 policy.

protocol udp | tcp

Sets the transport protocol for the traceroute packet. The TCP protocol is silently discarded on a targeted VRPN service. VPRN services only respond to UDP traceroutes.

Default

udp

router-or-service

Specifies the routing instance or service, by number. The router-instance parameter is the preferred parameter to specify the router or service.

Values

router-name: Base, management, vpls-management

vprn-svc-id: 1 to 2147483647

Default

Base

router-instance

Specifies the preferred method for entering a service name. Stored as the service name, this is the only service-linking function allowed for both mixed-mode and model-driven configuration modes.

Values

router-name: Base, management, vpls-management

vprn-svc-name: up to 64 characters

service-name

Specifies the alias function that allows the service name to be used, converted, and stored as service ID.

source ip-address

Specifies the source IP address to use as the source of the probe packets, in dotted decimal notation. If the IP address is not one of the device’s interfaces, an error is returned.

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

type-of-service

Specifies the Type-of-Service (ToS) bits in the IP header of the probe packets, expressed as a decimal integer.

Values

0 to 255

Default

0

srv6-policy
Keyword to specify that the traceroute probe is applied to an SRv6 policy matching a specific color and endpoint. The traceroute probe may optionally be targeted at a specific segment list of the SRv6 policy. When the segment list is not specified, the traceroute probe is sent on the lowest available segment list.
color-id
Specifies the SRv6 policy color ID.
Values

0 to 4294967295

segment-list
Specifies the SRv6 policy segment list to trace.
Values

1 to 32

Platforms

All

Output

ICMPv4 Type 3 symbols in CLI, ICMPv6 Type 1 symbols in CLI, and ICMPv6 Type 2 symbols in CLI describe the ICMPv4 Type 3, and the ICMPv6 Type 1 and 2 symbols in the CLI outputs. For references without a symbol in the form !<code>, see www.iana.org/assignments/icmp-parameters/icmp-parameters.xhtml.

The following output is an example of traceroute for an IPv4 prefix.

Output Example
A:node-2# traceroute 192.168.xx.xx4
traceroute to 192.168.xx.xx4, 30 hops max, 40 byte packets
 1  192.168.xx.xx4 0.000 ms  0.000 ms  0.000 ms

The following output is an example of traceroute for an IPv4 prefix resolved to an IPv4 SR policy with ICMP tunneling enabled.

Output Example
A:node-2# traceroute 11.21.1.6 detail no-dns 
traceroute to 11.21.1.6, 30 hops max, 40 byte packets
  1   1  10.10.11.3  3.36 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28303, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28306, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =  524283, Exp = 7, TTL =   1, S = 1
  1   2  10.10.11.3  3.68 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28303, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28306, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =  524283, Exp = 7, TTL =   1, S = 1
  1   3  10.10.11.3  4.18 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28303, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28306, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =  524283, Exp = 7, TTL =   1, S = 1
  2   1  10.10.10.5  3.77 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28506, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =  524283, Exp = 7, TTL =   2, S = 1
  2   2  10.10.10.5  8.02 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28506, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =  524283, Exp = 7, TTL =   2, S = 1
  2   3  10.10.10.5  4.72 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28506, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =  524283, Exp = 7, TTL =   2, S = 1
  3   1  11.21.1.6  5.33 ms
  3   2  11.21.1.6  4.77 ms
  3   3  11.21.1.6  4.07 ms

The following output is an example of traceroute for an IPv6 prefix resolved to an IPv4 SR policy with ICMP tunneling enabled.

Output Example
A:node-2# traceroute fc00::b15:106 detail no-dns 
traceroute to fc00::b15:106, 30 hops max, 60 byte packets
  1   1  fc00::a0a:b03  3.41 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28303, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28306, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =       2, Exp = 7, TTL =   1, S = 1
  1   2  fc00::a0a:b03  2.58 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28303, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28306, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =       2, Exp = 7, TTL =   1, S = 1
  1   3  fc00::a0a:b03  3.90 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28303, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28306, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =       2, Exp = 7, TTL =   1, S = 1
  2   1  fc00::a0a:a05  4.65 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28506, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =       2, Exp = 7, TTL =   2, S = 1
  2   2  fc00::a0a:a05  4.85 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28506, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =       2, Exp = 7, TTL =   2, S = 1
  2   3  fc00::a0a:a05  4.78 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28506, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =       2, Exp = 7, TTL =   2, S = 1
  3   1  fc00::b15:106  2.89 ms
  3   2  fc00::b15:106  3.58 ms
  3   3  fc00::b15:106  4.15 ms

The following output is an example of traceroute for an IPv6 prefix resolved to an IPv6 SR-OSPF3 tunnel with ICMP tunneling enabled.

Output Example
A:node-2# traceroute fc00::b14:106 detail 
traceroute to fc00::b14:106, 30 hops max, 60 byte packets
  1   1  fc00::a0a:402  (fc00::a0a:402)  4.38 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   29266, Exp = 7, TTL =   1, S = 1
  1   2  fc00::a0a:402  (fc00::a0a:402)  3.42 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   29266, Exp = 7, TTL =   1, S = 1
  1   3  fc00::a0a:402  (fc00::a0a:402)  4.19 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   29266, Exp = 7, TTL =   1, S = 1
  2   1  fc00::a0a:904  (fc00::a0a:904)  4.05 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   29466, Exp = 7, TTL =   1, S = 1
  2   2  fc00::a0a:904  (fc00::a0a:904)  3.62 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   29466, Exp = 7, TTL =   1, S = 1
  2   3  fc00::a0a:904  (fc00::a0a:904)  4.64 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   29466, Exp = 7, TTL =   1, S = 1
  3   1  fc00::b14:106  (fc00::b14:106)  3.35 ms
  3   2  fc00::b14:106  (fc00::b14:106)  4.02 ms
  3   3  fc00::b14:106  (fc00::b14:106)  3.30 ms

The following output is an example of traceroute for a label-ipv4 prefix resolved to an IPv6 SR-TE LSP with ICMP tunneling enabled (requires IPv4 system address).

Output Example
A:node-2# traceroute 11.21.1.1 source 11.21.1.6 detail 
traceroute to 11.21.1.1 from 11.21.1.6, 30 hops max, 40 byte packets
  1   1  10.20.1.4  (10.20.1.4)  4.96 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =  524270, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =  524285, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =  524236, Exp = 7, TTL =   1, S = 1
  1   2  10.20.1.4  (10.20.1.4)  5.35 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =  524270, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =  524285, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =  524236, Exp = 7, TTL =   1, S = 1
  1   3  10.20.1.4  (10.20.1.4)  5.43 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =  524270, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =  524285, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =  524236, Exp = 7, TTL =   1, S = 1
  2   1  10.20.1.2  (10.20.1.2)  4.72 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =  524285, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =  524236, Exp = 7, TTL =   2, S = 1
  2   2  10.20.1.2  (10.20.1.2)  5.71 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =  524285, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =  524236, Exp = 7, TTL =   2, S = 1
  2   3  10.20.1.2  (10.20.1.2)  5.03 ms
         returned MPLS Label Stack Object
            entry  1:  MPLS Label =  524285, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =  524236, Exp = 7, TTL =   2, S = 1
  3   1  11.21.1.1  (11.21.1.1)  3.51 ms
  3   2  11.21.1.1  (11.21.1.1)  3.91 ms
  3   3  11.21.1.1  (11.21.1.1)  3.09 ms

The following output is an example of traceroute for a label-ipv6 prefix resolved to an IPv4 SR-TE LSP with ICMP tunneling enabled.

Output Example
A:node-2# traceroute fc00::b15:101 detail 
traceroute to fc00::b15:101, 30 hops max, 60 byte packets
  1   1  fc00::a0a:404  (fc00::a0a:404)  3.36 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =  524270, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =  524285, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =       2, Exp = 7, TTL =   1, S = 1
  1   2  fc00::a0a:404  (fc00::a0a:404)  3.46 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =  524270, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =  524285, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =       2, Exp = 7, TTL =   1, S = 1
  1   3  fc00::a0a:404  (fc00::a0a:404)  3.77 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =  524270, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =  524285, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =       2, Exp = 7, TTL =   1, S = 1
  2   1  fc00::a0a:102  (fc00::a0a:102)  4.54 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =  524285, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =       2, Exp = 7, TTL =   2, S = 1
  2   2  fc00::a0a:102  (fc00::a0a:102)  4.70 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =  524285, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =       2, Exp = 7, TTL =   2, S = 1
  2   3  fc00::a0a:102  (fc00::a0a:102)  3.63 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =  524285, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =       2, Exp = 7, TTL =   2, S = 1
  3   1  fc00::b15:101  (fc00::b15:101)  3.40 ms
  3   2  fc00::b15:101  (fc00::b15:101)  3.15 ms
  3   3  fc00::b15:101  (fc00::b15:101)  3.23 ms

The following output is an example of traceroute for a vpn-ipv4 prefix resolved to an IPv6 SR-TE LSP with ICMP tunneling enabled (requires IPv4 system address).

Output Example
A:node-2# traceroute router-instance "vprn.sr-te.4" 1.0.4.1 source 6.0.4.1 detail 
traceroute to 1.0.4.1 from 6.0.4.1, 30 hops max, 40 byte packets
  1   1  10.20.1.4  (10.20.1.4)  5.03 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28462, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28261, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =  524241, Exp = 7, TTL =   1, S = 1
  1   2  10.20.1.4  (10.20.1.4)  4.52 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28462, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28261, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =  524241, Exp = 7, TTL =   1, S = 1
  1   3  10.20.1.4  (10.20.1.4)  5.61 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28462, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28261, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =  524241, Exp = 7, TTL =   1, S = 1
  2   1  10.20.1.2  (10.20.1.2)  5.38 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28262, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28261, Exp = 7, TTL =   2, S = 0
             entry  3:  MPLS Label =  524241, Exp = 7, TTL =   2, S = 1
  2   2  10.20.1.2  (10.20.1.2)  5.39 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28262, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28261, Exp = 7, TTL =   2, S = 0
             entry  3:  MPLS Label =  524241, Exp = 7, TTL =   2, S = 1
  2   3  10.20.1.2  (10.20.1.2)  5.27 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28262, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28261, Exp = 7, TTL =   2, S = 0
             entry  3:  MPLS Label =  524241, Exp = 7, TTL =   2, S = 1
  3   1  1.0.4.1  (1.0.4.1)  4.09 ms
  3   2  1.0.4.1  (1.0.4.1)  4.47 ms
  3   3  1.0.4.1  (1.0.4.1)  4.13 ms

The following output is an example of traceroute for a vpn-ipv6 prefix resolved to an IPv6 SR-TE LSP with ICMP tunneling enabled.

Output Example
A:node-2# traceroute router 5004 fc00::100:401 detail 
traceroute to fc00::100:401, 30 hops max, 60 byte packets
  1   1  fc00::a0a:404  (fc00::a0a:404)  5.45 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28462, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28261, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =  524241, Exp = 7, TTL =   1, S = 1
  1   2  fc00::a0a:404  (fc00::a0a:404)  5.14 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28462, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28261, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =  524241, Exp = 7, TTL =   1, S = 1
  1   3  fc00::a0a:404  (fc00::a0a:404)  5.31 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28462, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28261, Exp = 7, TTL =   1, S = 0
             entry  3:  MPLS Label =  524241, Exp = 7, TTL =   1, S = 1
  2   1  fc00::a0a:102  (fc00::a0a:102)  4.70 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28262, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28261, Exp = 7, TTL =   2, S = 0
             entry  3:  MPLS Label =  524241, Exp = 7, TTL =   2, S = 1
  2   2  fc00::a0a:102  (fc00::a0a:102)  5.20 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28262, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28261, Exp = 7, TTL =   2, S = 0
             entry  3:  MPLS Label =  524241, Exp = 7, TTL =   2, S = 1
  2   3  fc00::a0a:102  (fc00::a0a:102)  5.16 ms
         returned MPLS Label Stack Object
             entry  1:  MPLS Label =   28262, Exp = 7, TTL =   1, S = 0
             entry  2:  MPLS Label =   28261, Exp = 7, TTL =   2, S = 0
             entry  3:  MPLS Label =  524241, Exp = 7, TTL =   2, S = 1
  3   1  fc00::100:401  (fc00::100:401)  5.38 ms
  3   2  fc00::100:401  (fc00::100:401)  4.48 ms
  3   3  fc00::100:401  (fc00::100:401)  4.39 ms

The following output is an example of traceroute for an IPv4 prefix using the tcp and the detail options.

Output Example
Note: Reaching the destination and the port is closed on the destination.
A:node-2# traceroute 192.168.34.2 protocol tcp detail
traceroute to 192.168.34.2, 30 hops max, 40 byte packets
  1   1  192.168.13.2  (192.168.13.2)  0.755 ms
  1   2  192.168.13.2  (192.168.13.2)  0.913 ms
  1   3  192.168.13.2  (192.168.13.2)  0.928 ms
  2   1  192.168.34.2  (192.168.34.2)  1.19 ms (port closed)
  2   2  192.168.34.2  (192.168.34.2)  1.29 ms (port closed)
  2   3  192.168.34.2  (192.168.34.2)  1.59 ms (port closed)

The following output is an example of traceroute for an IPv4 prefix using the tcp and the detail options.

Output Example
Note: Reaching the destination and the port is open on the destination.
A:node-2# traceroute 192.168.34.2 protocol tcp dest-port 862 detail
traceroute to 192.168.34.2, 30 hops max, 40 byte packets
  1   1  192.168.13.2  (192.168.13.2)  0.915 ms
  1   2  192.168.13.2  (192.168.13.2)  0.861 ms
  1   3  192.168.13.2  (192.168.13.2)  0.825 ms
  2   1  192.168.34.2  (192.168.34.2)  1.42 ms (port open)
  2   2  192.168.34.2  (192.168.34.2)  1.27 ms (port open)
  2   3  192.168.34.2  (192.168.34.2)  1.52 ms (port open)

The following output is an example of traceroute of an SRv6 SID using the decode original-datagram option.

Output Example
A:node-2# traceroute 2002:abcd:1100:102:1:: detail decode original-datagram probe-count 1 
traceroute to 2002:abcd:1100:102:1::, 30 hops max, 60 byte packets
  1   1  2001:100:4:12::4  (2001:100:4:12::4)  1.23 ms
         Original Datagram
             IPv6 Header, Hop Limit 1, DSCP be
                 SA = 2001:1:1:1::112, DA = 2002:abcd:1100:102:1::
  2   1  2001:100:3:4::3  (2001:100:3:4::3)  2.25 ms
         Original Datagram
             IPv6 Header, Hop Limit 1, DSCP be
                 SA = 2001:1:1:1::112, DA = 2002:abcd:1100:101:1::
             Segment Routing Header SRv6, Segments Left 1
                 Segment_List[0] = 2002:abcd:1100:102:1::
  3   1  2001:100:1:3::1  (2001:100:1:3::1)  3.21 ms
         Original Datagram
             IPv6 Header, Hop Limit 1, DSCP be
                 SA = 2001:1:1:1::112, DA = 2002:abcd:1100:101:1::
             Segment Routing Header SRv6, Segments Left 1
                 Segment_List[0] = 2002:abcd:1100:102:1::
  4   1  2001:1:1:1::102  (2001:1:1:1::102)  9.16 ms
         Original Datagram
             IPv6 Header, Hop Limit 1, DSCP be
                 SA = 2001:1:1:1::112, DA = 2002:abcd:1100:102:1::
             Segment Routing Header SRv6, Segments Left 0
                 Segment_List[0] = 2002:abcd:1100:102:1::

The following output is an example of traceroute of an SRv6 policy.

Output Example
A:node-2# traceroute srv6-policy color 10 endpoint 6:6:6:6::86 probe-count 1                                 
traceroute srv6-policy color 10 endpoint 6:6:6:6::86, 30 hops max, 60 byte packets (excluding SRH)
  1  fc00::a0a:203 (fc00::a0a:203)    2.76 ms
  2  fc00::a0a:505 (fc00::a0a:505)    5.11 ms
  3  6:6:6:6::86 (6:6:6:6::86)    6.18 ms

The following output is an example of traceroute of an SRv6 policy using the decode original-datagram option.

Output Example
A:node-2# traceroute srv6-policy color 10 endpoint 6:6:6:6::86 probe-count 1 detail decode original-datagram 
traceroute srv6-policy color 10 endpoint 6:6:6:6::86, 30 hops max, 60 byte packets (excluding SRH)
  1   1  fc00::a0a:203  (fc00::a0a:203)  2.70 ms
         Original Datagram
             IPv6 Header, Hop Limit 1, DSCP be
                 SA = 1:1:1:1::61, DA = 3:3:3:3:0:a::
             Segment Routing Header SRv6, Segments Left 2
                 Segment_List[0] = 6:6:6:6::86
                 Segment_List[1] = 5:5:5:5:0:a::
  2   1  fc00::a0a:505  (fc00::a0a:505)  4.88 ms
         Original Datagram
             IPv6 Header, Hop Limit 1, DSCP be
                 SA = 1:1:1:1::61, DA = 5:5:5:5:0:a::
             Segment Routing Header SRv6, Segments Left 1
                 Segment_List[0] = 6:6:6:6::86
                 Segment_List[1] = 5:5:5:5:0:a::
  3   1  6:6:6:6::86  (6:6:6:6::86)  5.51 ms
         Original Datagram
             IPv6 Header, Hop Limit 1, DSCP be
                 SA = 1:1:1:1::61, DA = 6:6:6:6::86

The following output is an example of traceroute for a candidate path of an SRv6 policy.

Output Example
A:node-2# traceroute srv6-policy color 20 endpoint fc00::a14:106 probe-count 1 detail candidate-path protocol-owner static distinguisher 126 preference 100 
traceroute srv6-policy color 20 endpoint fc00::a14:106 candidate-path protocol-owner static preference 100 distinguisher 126, 30 hops max, 60 byte packets (excluding SRH)
  1   1  fc00::a0a:203  (fc00::a0a:203)  2.87 ms
  2   1  fc00::a0a:505  (fc00::a0a:505)  4.58 ms
  3   1  fc00::a14:106  (fc00::a14:106)  6.28 ms
Table 2. ICMPv4 Type 3 symbols in CLI
Symbol Description Code
!N Destination Network Unreachable 0
!P Destination Protocol Unreachable 2
! Destination Port Unreachable 3
!F-mtu Fragmentation Needed and Don't Fragment was Set 4
!S Source Route Failed 5
!X Communication Administratively Prohibited 13
!V Host Precedence Violation 14
!C Precedence Cutoff In Effect 15
Table 3. ICMPv6 Type 1 symbols in CLI
Symbol Description Code
!N No Route to Destination 0
!H Destination Address Unreachable 3
! Destination Port Unreachable 4
Table 4. ICMPv6 Type 2 symbols in CLI
Symbol Description Code
!F-mtu MTU Exceeded - Fragmentation Required 0

traceroute-reply

traceroute-reply

Syntax

[no] traceroute-reply

Context

[Tree] (config>service>ies>if>ipv6>vrrp traceroute-reply)

Full Context

configure service ies interface ipv6 vrrp traceroute-reply

Description

This command is valid only if the VRRP virtual router instance associated with this entry is a non-owner.

When this command is enabled, a non-owner master can reply to traceroute requests directed to the virtual router instance IP addresses.

A non-owner backup virtual router never responds to such traceroute requests regardless of the trace-route-reply status.

Default

no traceroute-reply

Platforms

All

traceroute-reply

Syntax

[no] traceroute-reply

Context

[Tree] (config>service>ies>if>vrrp traceroute-reply)

Full Context

configure service ies interface vrrp traceroute-reply

Description

This command is valid only if the VRRP virtual router instance associated with this entry is a non-owner.

When this command is enabled, a non-owner master can reply to traceroute requests directed to the virtual router instance IP addresses.

A non-owner backup virtual router never responds to such traceroute requests regardless of the trace-route-reply status.

Default

no traceroute-reply

Platforms

All

traceroute-reply

Syntax

[no] traceroute-reply

Context

[Tree] (config>service>vprn>if>ipv6>vrrp traceroute-reply)

[Tree] (config>service>vprn>if>vrrp traceroute-reply)

Full Context

configure service vprn interface ipv6 vrrp traceroute-reply

configure service vprn interface vrrp traceroute-reply

Description

This command is valid only if the VRRP virtual router instance associated with this entry is a non-owner.

When this command is enabled, a non-owner master can reply to traceroute requests directed to the virtual router instance IP addresses.

A non-owner backup virtual router never responds to such traceroute requests regardless of the trace-route-reply status.

Default

no traceroute-reply

Platforms

All

traceroute-reply

Syntax

[no] traceroute-reply

Context

[Tree] (config>router>if>vrrp traceroute-reply)

[Tree] (config>router>if>ipv6>vrrp traceroute-reply)

Full Context

configure router interface vrrp traceroute-reply

configure router interface ipv6 vrrp traceroute-reply

Description

This command is valid only if the VRRP virtual router instance associated with this entry is a non-owner.

When this command is enabled, a non-owner master can reply to traceroute requests directed to the virtual router instance IP addresses.

A non-owner backup virtual router never responds to such traceroute requests regardless of the trace-route-reply status.

Traceroute must not have been disabled at the management security level (either on the parental IP interface or the source host address).

Default

no traceroute-reply

Platforms

All

track-accounting

track-accounting

Syntax

track-accounting [start] [stop][interim-update][accounting-on] [accounting-off]

no track-accounting

Context

[Tree] (config>service>vprn>radius-proxy>server>cache track-accounting)

[Tree] (config>router>radius-proxy>server>cache track-accounting)

Full Context

configure service vprn radius-proxy server cache track-accounting

configure router radius-proxy server cache track-accounting

Description

This command specifies the type of RADIUS accounting packets from RADIUS client (a WIFI AP) that the router should track.

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

Parameters

start

Specifies that the router will update the associated ESM-host with the RADIUS client (for example, a WIFI AP) that generated the accounting-start. This is required in cases where a UE roams to a new AP that does not re-authenticate due to key caching.

stop

Specifies that the router will remove the corresponding ESM host and forward the accounting-stop packet to the external RADIUS server.

accounting-on | accounting-off

Specifies that the router will remove all ESM hosts associated with the RADIUS client (a WIFI AP), and forward the accounting-on packet to the external RADIUS server.

interim-update

Specifies that the router will update the associated ESM-host with the RADIUS client (a WIFI AP) that generated the interim-update. The interim-updates with the updated information are sent to the RADIUS server as scheduled.

Platforms

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

track-authentication

track-authentication

Syntax

track-authentication [accept]

no track-authentication

Context

[Tree] (config>router>radius-proxy>server>cache track-authentication)

[Tree] (config>service>vprn>radius-proxy>server>cache track-authentication)

Full Context

configure router radius-proxy server cache track-authentication

configure service vprn radius-proxy server cache track-authentication

Description

This command specifies if RADIUS authentication (from the AP) should be tracked in order to update the ESM host with the RADIUS client (for example, WIFI AP) on UE mobility. It also specifies the authentication packet from RADIUS client (for example, a WIFI AP) that the router should track for mobility.

The no form of this command stops tracking authentication for UE mobility.

Default

track-authentication accept

Parameters

accept

Indicates access-accept is tracked for mobility.

Platforms

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

track-delete-hold-time

track-delete-hold-time

Syntax

track-delete-hold-time seconds

no track-delete-hold-time

Context

[Tree] (config>router>radius-proxy>server>cache track-delete-hold-time)

Full Context

configure router radius-proxy server cache track-delete-hold-time

Description

This command specifies the delete hold-time in case the DHCP host gets a trigger to delete from the matched RADIUS Proxy server.

The no form of this command reverts to the default.

Default

track-delete-hold-time 0

Parameters

seconds

Specifies the delete hold time, in seconds.

Values

0 to 600

Platforms

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

track-mobility

track-mobility

Syntax

track-mobility

Context

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

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

Full Context

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

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

Description

Commands in this context configure RADIUS-proxy cache information required for subscribers that are created via data-triggered authentication. The RADIUS proxy cache enables efficient handling of UE mobility.

Platforms

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

track-password-change

track-password-change

Syntax

[no] track-password-change

Context

[Tree] (config>service>vprn>l2tp>group>l2tpv3 track-password-change)

Full Context

configure service vprn l2tp group l2tpv3 track-password-change

Description

This command enables tracking of password changes, allowing password tunnel passwords to be changed without bringing down active tunnels or sessions. This is only supported with L2TPv3.

The no form of this command disables password change tracking.

Default

no track-password-change

Platforms

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

track-srrp

track-srrp

Syntax

track-srrp srrp-instance peer ip-address sync-tag sync-tag

no track-srrp srrp-instance

Context

[Tree] (config>router>l2tp>failover track-srrp)

[Tree] (config>service>vprn>l2tp>failover track-srrp)

Full Context

configure router l2tp failover track-srrp

configure service vprn l2tp failover track-srrp

Description

This command sets the sync-tag to be used to synchronize the tunnels with track-srrp srrp-id to MCS peer IP-@. The same sync-tag should be configured on the MCS peer.

The no form of this command reverts to the default.

Default

Removes the sync-tag for the indicated track-srrp.

Parameters

srrp-instance

Specifies the Simple Router Redundancy Protocol (SRRP) instance used for Multi-Chassis redundancy failover that is associated with this Layer Two Tunneling Protocol Tunnel.

sync-tag

Specifies a synchronization tag to be used while synchronizing with the peer.

Platforms

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

track-srrp

Syntax

[no] track-srrp [srrp-instance]

Context

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

Full Context

configure redundancy multi-chassis peer sync track-srrp-instances track-srrp

Description

This command configures a tracked SRRP instance.

The no form of this command removes the SRRP instance identifier from the configuration.

Parameters

srrp-instance

Indicates the unique identifier of the tracked SRRP instance.

Values

1 to 4294967295

Platforms

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

track-srrp

Syntax

track-srrp srrp-id

no track-srrp

Context

[Tree] (config>service>vpls>sap track-srrp)

Full Context

configure service vpls sap track-srrp

Description

This command configures the SRRP instance this capture SAP will track. This is a capture SAP level command. This command is important in PPPoE deployments with MSAPs. PPPoE operation requires that the MAC address learned by the client at the very beginning of the session negotiation phase remains unchanged for the lifetime of the session (RFC 2516). This command ensures that the virtual MAC address used during the PPPoE session negotiation phase on the capture SAP is the same virtual MAC address that is used by the SRRP on the group interface on which the session is established. Therefore, it is mandated that the SRRP instance (and implicitly the group-interface) where the session belongs to is known in advance. If the group interface name for the session is returned by the RADIUS, it must be ensured that this group interface is the one on which the tracked SRRP instance is configured. PPPoE sessions on the same capture SAP cannot be shared across multiple group interfaces, but instead they all must belong to a single group interface that is known in advance.

The same restrictions apply to IPoE clients in MC Redundancy scenario if they are to be supported concurrently on the same capture SAP as PPPoE.

The supported capture SAP syntax is this:

sap <port-id>:X.* capture-sap

The capture SAP syntax that is not supported is this:

sap <port-id>:*.* capture-sap

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

Parameters

srrp-id

Specifies the SRRP instance number.

Values

1 to 4294967295

Platforms

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

track-srrp-instances

track-srrp-instances

Syntax

track-srrp-instances

Context

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

Full Context

configure redundancy multi-chassis peer sync track-srrp-instances

Description

Commands in this context configure tracked SRRP instances.

Platforms

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

tracking-support

tracking-support

Syntax

[no] tracking-support

Context

[Tree] (config>service>vprn>mvpn>pt>inclusive>pim tracking-support)

Full Context

configure service vprn mvpn provider-tunnel inclusive pim tracking-support

Description

This command enables the setting of the T bit in the LAN Prune Delay option of the Hello message. This indicates the router's capability to disable Join message suppression.

The no form of this command disables the setting.

Default

no tracking-support

Platforms

All

tracking-support

Syntax

[no] tracking-support

Context

[Tree] (config>service>vprn>pim>if tracking-support)

Full Context

configure service vprn pim interface tracking-support

Description

This command sets the T bit in the LAN Prune Delay option of the Hello Message. This indicates the router's capability to disable Join message suppression.

Default

no tracking-support

Platforms

All

tracking-support

Syntax

[no] tracking-support

Context

[Tree] (config>router>pim>interface tracking-support)

Full Context

configure router pim interface tracking-support

Description

This command sets the T bit in the LAN Prune Delay option of the Hello Message. This indicates the router's capability to enable join message suppression. This capability allows for upstream routers to explicitly track join membership.

The no form of this command disables tracking support.

Default

no tracking-support

Platforms

All

traffic-capture

traffic-capture

Syntax

[no] traffic-capture

Context

[Tree] (debug>app-assure>group traffic-capture)

Full Context

debug application-assurance group traffic-capture

Description

This command configures debugging for traffic capture.

Platforms

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

traffic-class

traffic-class

Syntax

traffic-class traffic-class

no traffic-class

Context

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

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

Full Context

debug oam build-packet packet field-override header mpls traffic-class

configure test-oam build-packet header mpls traffic-class

Description

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

The no form of this command removes the traffic class value.

Default

traffic-class 0 (BE)

Parameters

traffic-class

Specifies the MPLS traffic class to be used in the MPLS header.

Values

0 to 7

Platforms

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

traffic-direction

traffic-direction

Syntax

traffic-direction {subscriber-to-network | network-to-subscriber | both}

Context

[Tree] (config>app-assure>group>policy>aqp>entry>match traffic-direction)

Full Context

configure application-assurance group policy app-qos-policy entry match traffic-direction

Description

This command specifies the direction of traffic where the AQP match entry will be applied.

To use a policer action with the AQP entry the match criteria must specify a traffic-direction of either subscriber-to-network or network-to-subscriber.

Default

traffic-direction both

Parameters

subscriber-to-network

Traffic from a local subscriber will match this AQP entry.

network-to-subscriber

Traffic to a local subscriber will match this AQP entry.

both

Combines subscriber-to-network and network-to-subscriber.

Platforms

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

traffic-engineering

traffic-engineering

Syntax

[no] traffic-engineering

Context

[Tree] (config>router>isis traffic-engineering)

Full Context

configure router isis traffic-engineering

Description

This command enables this IS-IS instance to advertise TE link attributes for RSVP-TE and SR-TE enabled interfaces.

Default

no traffic-engineering

Platforms

All

traffic-engineering

Syntax

[no] traffic-engineering

Context

[Tree] (config>router>ospf traffic-engineering)

Full Context

configure router ospf traffic-engineering

Description

This command enables the advertisement of the traffic engineering information for the router and its links.

Traffic engineering enables the router to perform route calculations constrained by nodes or links. The traffic engineering of this router are limited to calculations based on link and nodal constraints.

The no form of this command disables the advertisement of the traffic engineering information.

Default

no traffic-engineering

Platforms

All

traffic-engineering-options

traffic-engineering-options

Syntax

[no] traffic-engineering-options

Context

[Tree] (config>router>isis traffic-engineering-options)

Full Context

configure router isis traffic-engineering-options

Description

Commands in this context configure advanced traffic-engineering options.

The no form of this command deletes the context.

Default

no traffic-engineering-options

Platforms

All

traffic-engineering-options

Syntax

[no] traffic-engineering-options

Context

[Tree] (config>router>ospf traffic-engineering-options)

Full Context

configure router ospf traffic-engineering-options

Description

Commands in this context configure the advanced traffic-engineering options.

The no form of this command removes the context to configure the advanced traffic-engineering options.

Default

no traffic-engineering-options

Platforms

All

traffic-identification

traffic-identification

Syntax

traffic-identification

Context

[Tree] (config>service>vprn>nat>inside traffic-identification)

[Tree] (config>router>nat>inside traffic-identification)

Full Context

configure service vprn nat inside traffic-identification

configure router nat inside traffic-identification

Description

Commands in this context configure traffic idenification for NAT processing.

Platforms

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

traffic-rate-delta

traffic-rate-delta

Syntax

traffic-rate-delta rate

no traffic-rate-delta

Context

[Tree] (config>service>vprn>mvpn>pt>inclusive>umh-rm traffic-rate-delta)

[Tree] (config>service>vprn>mvpn>pt>selective>umh-rm>group>source traffic-rate-delta)

Full Context

configure service vprn mvpn provider-tunnel inclusive umh-rate-monitoring traffic-rate-delta

configure service vprn mvpn provider-tunnel selective umh-rate-monitoring group source traffic-rate-delta

Description

This command configures the bandwidth delta upwards of which the traffic is switched from the primary UMH to the backup UMH.

The no form of this command removes UMH redundancy with bandwidth monitoring.

Default

1

Parameters

rate

Specifies the bandwidth delta, in kbps.

Values

1 to 4294967294

Platforms

All

traffic-type

traffic-type

Syntax

[no] traffic-type

Context

[Tree] (config>app-assure>group>statistics>aa-partition traffic-type)

Full Context

configure application-assurance group statistics aa-partition traffic-type

Description

This command enables traffic type statistics collection within an aa-partition.

The no form of this command disables traffic type statistics collection.

Platforms

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

transceiver

transceiver

Syntax

transceiver

Context

[Tree] (config>port transceiver)

Full Context

configure port transceiver

Description

Commands in this context configure transceiver parameters.

Platforms

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

transform

transform

Syntax

transform transform-id [transform-id]

no transform

Context

[Tree] (config>service>vprn>if>ipsec>ipsec-tunnel>dyn transform)

[Tree] (config>service>ies>if>ipsec>ipsec-tunnel>dyn transform)

[Tree] (config>ipsec>tnl-temp transform)

[Tree] (config>ipsec>trans-mode-prof>dyn transform)

[Tree] (config>router>if>ipsec>ipsec-tunnel>dyn transform)

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

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

[Tree] (config>service>vprn>if>sap>ipsec-tunnel transform)

Full Context

configure service vprn interface ipsec ipsec-tunnel dynamic-keying transform

configure service ies interface ipsec ipsec-tunnel dynamic-keying transform

configure ipsec tunnel-template transform

configure ipsec ipsec-transport-mode-profile dynamic-keying transform

configure router interface ipsec ipsec-tunnel dynamic-keying transform

configure service ies interface sap ipsec-gw transform

configure service vprn interface sap ipsec-gw transform

configure service vprn interface sap ipsec-tunnel transform

Description

This command associates the IPsec transform sets allowed for this the CHILD_SA. A maximum of four transforms can be specified. The transforms are listed in decreasing order of preference (the first one specified is the most preferred).

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

Default

no transform

Parameters

transform-id

Specifies a number to identify a tranform used for CHILD_SA negotiation. Up to four transform ID can be specified.

Values

1 to 2048

Platforms

VSR

  • configure service vprn interface ipsec ipsec-tunnel dynamic-keying transform
  • configure router interface ipsec ipsec-tunnel dynamic-keying transform
  • configure service ies interface ipsec ipsec-tunnel dynamic-keying transform

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

  • configure ipsec tunnel-template transform
  • configure service ies interface sap ipsec-gw transform
  • configure ipsec ipsec-transport-mode-profile dynamic-keying transform
  • configure service vprn interface sap ipsec-gw transform
  • configure service vprn interface sap ipsec-tunnel transform

transform

Syntax

transform transform-id [transform-id]

no transform

Context

[Tree] (config>service>vprn>if>sap>ipsec-tun>dyn transform)

Full Context

configure service vprn interface sap ipsec-tunnel dynamic-keying transform

Description

This command associates the IPsec transform sets allowed for this tunnel. A maximum of four transforms can be specified. The transforms are listed in decreasing order of preference (the first one specified is the most preferred).

Default

no transform

Parameters

transform-id

Specifies the value used for transforms for dynamic keying.

Values

1 to 2048

Platforms

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

transit

transit

Syntax

transit [inherit | all | vc-only | none]

Context

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

Full Context

configure service vprn ttl-propagate transit

Description

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

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

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

Default

transit inherit

Parameters

inherit

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

none

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

vc-only

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

all

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

Platforms

All

transit-auto-create

transit-auto-create

Syntax

transit-auto-create

Context

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

Full Context

configure application-assurance group transit-ip-policy transit-auto-create

Description

This command enables seen-IP auto creation of transit subscribers using the transit-IP-policy name and subscriber IP address as the AA-sub name. The default app-profile configured against the transit-ip-policy is applied to these subscribers.

Platforms

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

transit-delay

transit-delay

Syntax

transit-delay seconds

no transit-delay

Context

[Tree] (config>service>vprn>ospf3>area>virtual-link transit-delay)

[Tree] (config>service>vprn>ospf3>area>if transit-delay)

[Tree] (config>service>vprn>ospf>area>if transit-delay)

[Tree] (config>service>vprn>ospf>area>sham-link transit-delay)

[Tree] (config>service>vprn>ospf>area>virtual-link transit-delay)

Full Context

configure service vprn ospf3 area virtual-link transit-delay

configure service vprn ospf3 area interface transit-delay

configure service vprn ospf area interface transit-delay

configure service vprn ospf area sham-link transit-delay

configure service vprn ospf area virtual-link transit-delay

Description

This command configures the estimated time, in seconds, that it takes to transmit a LSA on the interface or virtual link or sham-link.

The no form of this command reverts to the default delay time.

Default

transit-delay 1

Parameters

seconds

The transit delay in seconds expressed as a decimal integer.

Values

0 to 3600

Platforms

All

transit-delay

Syntax

transit-delay seconds

no transit-delay

Context

[Tree] (config>router>ospf3>area>virtual-link transit-delay)

[Tree] (config>router>ospf>area>interface transit-delay)

[Tree] (config>router>ospf>area>virtual-link transit-delay)

[Tree] (config>router>ospf3>area>interface transit-delay)

Full Context

configure router ospf3 area virtual-link transit-delay

configure router ospf area interface transit-delay

configure router ospf area virtual-link transit-delay

configure router ospf3 area interface transit-delay

Description

This command configures the estimated time, in seconds, that it takes to transmit a link state advertisement (LSA) on the interface or virtual link.

The no form of this command reverts to the default delay time.

Default

transit-delay 1

Parameters

seconds

Specifies the transit delay in seconds expressed as a decimal integer.

Values

1 to 1800

Platforms

All

transit-ip-policy

transit-ip-policy

Syntax

transit-ip-policy ip-policy-id [create]

no transit-ip-policy ip-policy-id

Context

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

Full Context

configure application-assurance group transit-ip-policy

Description

This command defines a transit AA subscriber IP policy. Transit AA subscribers are managed by the system through the use of this policy assigned to services, which determines how transit subs are created and removed for that service.

The no form of this command deletes the policy from the configuration. All associations must be removed in order to delete a policy.

Parameters

ip-policy-id

An integer that identifies a transit IP profile entry.

Values

1 to 65535

create

Keyword used to create the entry.

Platforms

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

transit-path

transit-path

Syntax

transit-path path-name

no transit-path

Context

[Tree] (config>router>mpls>mpls-tp transit-path)

Full Context

configure router mpls mpls-tp transit-path

Description

This command enables the configuration or editing of an MPLS-TP transit path at an LSR.

Default

no transit-path

Parameters

path-name

Specifies the template of up to 32 characters in printable 7-bit ASCII, enclosed in double quotes.

Platforms

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

transit-policy

transit-policy

Syntax

transit-policy ip ip-aasub-policy-id

transit-policy prefix prefix-aasub-policy-id

no transit-policy

Context

[Tree] (config>service>vpls>sap transit-policy)

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

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

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

[Tree] (config>service>vprn>if>sap transit-policy)

[Tree] (config>service>epipe>sap transit-policy)

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

[Tree] (config>service>ies>if>sap transit-policy)

Full Context

configure service vpls sap transit-policy

configure service epipe spoke-sdp transit-policy

configure service ies interface spoke-sdp transit-policy

configure service vprn interface spoke-sdp transit-policy

configure service vprn interface sap transit-policy

configure service epipe sap transit-policy

configure service vpls spoke-sdp transit-policy

configure service ies interface sap transit-policy

Description

This command associates a transit AA subscriber IP or prefix policy to the service. The transit policy must be defined prior to associating the policy with a SAP in the config>app-assure>group>transit-ip-policy or transit-prefix-policy context.

The no form of this command removes the association of the policy to the service.

Default

no transit-policy

Parameters

ip-aasub-policy-id

Specifies a transit IP policy ID.

Values

1 to 65535

prefix-aasub-policy-id

Specifies a transit prefix policy ID.

Values

1 to 65535

Platforms

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

transit-policy

Syntax

transit-policy prefix prefix-aasub-policy-id

no transit-policy

Context

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

[Tree] (config>service>ipipe>sap transit-policy)

Full Context

configure service ipipe spoke-sdp transit-policy

configure service ipipe sap transit-policy

Description

This command associates an AA transit policy to the service. The transit IP policy must be defined prior to associating the policy with a SAP in the config>application assurance>group>policy>transit-ip-policy context.

Transit AA subscribers are managed by the system through this service policy, which determines how transit subs are created and removed for that service.

The no form of this command removes the association of the policy to the service.

Default

no transit-policy

Parameters

prefix-aasub-policy-id

Specifies an integer identifying a prefix transit profile entry.

Values

1 to 65535

Platforms

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

transit-prefix-ipv4-entries

transit-prefix-ipv4-entries

Syntax

transit-prefix-ipv4-entries entries

no transit-prefix-ipv4-entries

Context

[Tree] (config>isa>aa-grp transit-prefix-ipv4-entries)

Full Context

configure isa application-assurance-group transit-prefix-ipv4-entries

Description

This command defines the number of transit-prefix IPv4 entries for an ISA.

The no form of this command removes the assignment of entries space from the configuration. All entries must be removed in order to delete the configuration.

Default

no transit-prefix-ipv4-entries

Parameters

entries

Specifies an integer that determines the number of transit-prefix-ipv4 entries.

Values

0 to 16383

Platforms

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

transit-prefix-ipv4-remote-entries

transit-prefix-ipv4-remote-entries

Syntax

transit-prefix-ipv4-remote-entries entries

no transit-prefix-ipv4-remote-entries

Context

[Tree] (config>isa>aa-grp transit-prefix-ipv4-remote-entries)

Full Context

configure isa application-assurance-group transit-prefix-ipv4-remote-entries

Description

This command configures the ISA-AA-group transit prefix IPv4 remote entry limit. This entry space is allocated on the IOM within a common area with the second MDA/ISA position of the IOM and also used for IPv4filter entries for system SDPs. The per-ISA size allocated for transit-prefix-ipv4 entries should be set to allow sufficient space on the IOM for SDP IPv4 filters.

The no form of this command removes the assignment of entries space from the configuration. All entries must be removed in order to delete the configuration.

Default

no transit-prefix-ipv4-remote-entries

Parameters

entries

Specifies the ISA-AA-Group transit prefix IPv4 remote entry limit.

Values

0 to 2047

Platforms

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

transit-prefix-ipv6-entries

transit-prefix-ipv6-entries

Syntax

transit-prefix-ipv6-entries entries

no transit-prefix-ipv6-entries

Context

[Tree] (config>isa>aa-grp transit-prefix-ipv6-entries)

Full Context

configure isa application-assurance-group transit-prefix-ipv6-entries

Description

This command configures the ISA-AA-group transit prefix IPv6 entry limit for each ISA in the group. This entry space is allocated on the IOM within a common area with the second MDA / ISA position of the IOM and also used for ipv6-filter entries for system SDPs. The per-ISA size allocated for transit-prefix-ipv6 entries should be set to allow sufficient space on the IOM for SDP ipv6-filters.

The no form of this command removes the assignment of entries space from the configuration. All entries must be removed in order to delete the configuration.

Default

no transit-prefix-ipv6-entries

Parameters

entries

Specifies the ISA-AA-Group transit prefix IPv6 entry limit.

Values

0 to 8191

Platforms

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

transit-prefix-ipv6-remote-entries

transit-prefix-ipv6-remote-entries

Syntax

transit-prefix-ipv6-remote-entries entries

no transit-prefix-ipv6-remote-entries

Context

[Tree] (config>isa>aa-grp transit-prefix-ipv6-remote-entries)

Full Context

configure isa application-assurance-group transit-prefix-ipv6-remote-entries

Description

This command configures the ISA-AA-group transit prefix IPv6 remote entry limit. This entry space is allocated on the IOM within a common area with the second MDA/ISA position of the IOM and also used for IPv6filter entries for system SDPs. The per-ISA size allocated for transit-prefix-ipv6 entries should be set to allow sufficient space on the IOM for SDP IPv6 filters.

The no form of this command removes the assignment of entries space from the configuration. All entries must be removed in order to delete the configuration.

Default

no transit-prefix-ipv6-remote-entries

Parameters

entries

Specifies the ISA-AA-Group transit prefix IPv6 remote entry limit.

Values

0 to 1023

Platforms

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

transit-prefix-policy

transit-prefix-policy

Syntax

transit-prefix-policy prefix-policy-id [create]

no transit-prefix-policy prefix-policy-id

Context

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

Full Context

configure application-assurance group transit-prefix-policy

Description

This command defines a transit aa subscriber prefix policy. Transit AA subscribers are managed by the system through the use of this policy assigned to services, which determines how transit subs are created and removed for that service.

The no form of this command deletes the policy from the configuration. All associations must be removed in order to delete a policy.

Parameters

prefix-policy-id

Indicates the transit prefix policy to which this subscriber belongs.

Values

1 to 65535

create

Mandatory keyword used when creating transit prefix policy. The create keyword requirement can be enabled/disabled in the environment>create context.

Platforms

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

transmission-profile

transmission-profile

Syntax

transmission-profile name

no transmission-profile

Context

[Tree] (config>system>security>pki>ca-profile>ocsp transmission-profile)

Full Context

configure system security pki ca-profile ocsp transmission-profile

Description

This command specifies the transmission-profile for OCSP. When specified, this configuration overrides the service service-id or service service-name configured in the config>system>security>pki>ca-profile>ocsp context.

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

Default

no transmission-profile

Parameters

name

Specifies the file transmission profile name, up to 32 characters.

Platforms

All

transmission-profile

Syntax

transmission-profile name

no transmission-profile

Context

[Tree] (config>system>security>pki>est-profile transmission-profile)

Full Context

configure system security pki est-profile transmission-profile

Description

This command specifies the transmission profile name created in the config>system file-transmission-profile context for the EST profile.

The no form of the command removes the name from the EST profile configuration.

Default

no transmission-profile

Parameters

name

Specifies the file transmission profile name, up to 32 characters.

Platforms

All

transmit-interval

transmit-interval

Syntax

[no] transmit-interval interval [multiplier multiplier]

Context

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

Full Context

configure port ethernet efm-oam transmit-interval

Description

This command configures the transmit interval of OAM PDUs.

Default

transmit-interval 10 multiplier 5

Parameters

interval

Specifies the transmit interval, in 100 milliseconds.

Values

1 to 600

multiplier

Specifies the multiplier for transmit-interval to set local link down timer.

Values

2 to 5

Platforms

All

transmit-interval

Syntax

transmit-interval transmit-interval

no transmit-interval

Context

[Tree] (config>lag>bfd>family transmit-interval)

Full Context

configure lag bfd family transmit-interval

Description

This command specifies the transmit timer used for micro-BFD session over the associated LAG links.

The no form of this command removes the transmit timer from the configuration.

Default

transmit-interval 100

Parameters

transmit-interval

Specifies the interval value, in milliseconds.

Values

10 to 100000

Default

100 for CPM3 or later, 1000 for all others

Platforms

All

transmit-interval

Syntax

transmit-interval transmit-interval

no transmit-interval

Context

[Tree] (config>router>bfd>bfd-template transmit-interval)

Full Context

configure router bfd bfd-template transmit-interval

Description

This command specifies the transmit timer used for BFD packets. If the template is used for a BFD session on an MPLS-TP LSP, then this timer is used for CC packets.

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

Default

transmit-interval 100

Parameters

transmit-interval

Specifies the transmit interval. The minimum interval that can be configured is hardware dependent.

Values

10 ms to 100,000 ms in 1 ms intervals

Default

10 ms for CPM3 or higher; 1 second for other hardware

Platforms

All

transmit-interval

Syntax

transmit-interval transmit-interval

no transmit-interval

Context

[Tree] (config>router>lsp-bfd>tail-end transmit-interval)

Full Context

configure router lsp-bfd tail-end transmit-interval

Description

This command configures the LSP BFD minimum transmit interval for the tail end of LSP BFD sessions.

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

Default

transmit-interval 1000

Parameters

transmit-interval

Specifies the transmit interval, in milliseconds.

Values

100 to 1000

Default

1000

Platforms

All

transmit-period

transmit-period

Syntax

transmit-period seconds

no transmit-period

Context

[Tree] (config>port>ethernet>dot1x transmit-period)

Full Context

configure port ethernet dot1x transmit-period

Description

This command configures the period after which the router sends a new EAPOL request message.

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

Default

transmit-period 30

Parameters

seconds

Specifies the server transmit period in seconds.

Values

1 to 3600

Platforms

All

transport-address

transport-address

Syntax

transport-address {interface | system}

no transport-address

Context

[Tree] (config>router>ldp>if-params>ipv6 transport-address)

[Tree] (config>router>ldp>if-params>if>ipv6 transport-address)

[Tree] (config>router>ldp>if-params>if>ipv4 transport-address)

[Tree] (config>router>ldp>if-params>ipv4 transport-address)

Full Context

configure router ldp interface-parameters ipv6 transport-address

configure router ldp interface-parameters interface ipv6 transport-address

configure router ldp interface-parameters interface ipv4 transport-address

configure router ldp interface-parameters ipv4 transport-address

Description

This command configures the transport address to be used when setting up the LDP TCP sessions. The transport address can be configured as interface or system. The transport address can be configured globally (applies to all LDP interfaces) or per interface. The most specific value is used.

The config>router>ldp>if-params>ipv6> transport-address command is not supported on the 7450 ESS.

With the transport-address command, you can set up the LDP interface to the connection which can be set to the interface address or the system address. However, there can be an issue of which address to use when there are parallel adjacencies. This situation can not only happen with parallel links, it could be a link and a targeted adjacency since targeted adjacencies request the session to be set up only to the system IP address.

The transport-address value should not be interface if multiple interfaces exist between two LDP neighbors. Depending on the first adjacency to be formed, the TCP endpoint is chosen. In other words, if one LDP interface is set up as transport-address interface and another for transport-address system, then, depending on which adjacency was set up first, the TCP endpoint addresses are determined. After that, because the hello contains the LSR ID, the LDP session can be checked to verify that it is set up and then match the adjacency to the session.

For any iLDP interface, as the local-lsr-id parameters is changed to interface, the transport-address configuration loses effectiveness. Since it will be ignored and the iLDP session will always use the relevant interface IP address as transport-address even though system is chosen.

The no form of this command, at the global level, sets the transport address to the default value.

The no form of this command, at the interface level, sets the transport address to the value defined under the global level.

Default

system

Parameters

interface

Specifies the IP interface address is used to set up the LDP session between neighbors. The transport address interface cannot be used if multiple interfaces exist between two neighbors, since only one LDP session is set up between two neighbors.

system

Specifies the system IP address is used to set up the LDP session between neighbors.

Platforms

All

transport-encryption

transport-encryption

Syntax

transport-encryption

Context

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

Full Context

configure redundancy multi-chassis peer sync transport-encryption

Description

Commands in this context configure MCS applications that need to encrypt synchronized states for transportation .

Platforms

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

transport-tunnel

transport-tunnel

Syntax

transport-tunnel

Context

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

Full Context

configure router bgp next-hop-resolution labeled-routes transport-tunnel

Description

Commands in this context configure options for the next-hop resolution of BGP labeled routes (VPN-IP and labeled-unicast) using tunnels in TTM. The context allows the selection of different tunnel resolution options for different types of BGP labeled routes: label-unicast IPv4, label-unicast IPv6, and VPN-IP routes (both VPN-IPv4 and VPN-IPv6).

By default (if this context and the resolution options are not configured), these routes resolve only to LDP tunnels.

If the resolution option is explicitly set to disabled, the default binding to LDP tunnel resumes. If resolution is set to any, then any supported tunnel type is allowed and the selection is based on the lowest numerical TTM preference value.

Platforms

All

transport-type

transport-type

Syntax

transport-type {ip}

no transport-type

Context

[Tree] (config>service>vprn>l2tp>l2tpv3 transport-type)

[Tree] (config>router>l2tp>l2tpv3 transport-type)

Full Context

configure service vprn l2tp l2tpv3 transport-type

configure router l2tp l2tpv3 transport-type

Description

This command configures the transport type to be used to carry the L2TPv3 tunnel. Currently, only IP transport is supported.

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

Default

no transport-type

Parameters

ip

Specifies that IP should be used as the transport type for the L2TPv3 tunnel.

Platforms

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

trap-gen

trap-gen

Syntax

trap-gen

Context

[Tree] (config>saa>test trap-gen)

Full Context

configure saa test trap-gen

Description

Commands in this context configure trap generation for the SAA test.

Platforms

All

trap-target

trap-target

Syntax

trap-target name address ip-address [port port] [snmpv1 | snmpv2c | snmpv3] notify-community communityName | snmpv3SecurityName [security-level {no-auth-no-privacy | auth-no-privacy | privacy}] [replay]

no trap-target name

Context

[Tree] (config>service>vprn>log>snmp-trap-group trap-target)

Full Context

configure service vprn log snmp-trap-group trap-target

Description

This command adds/modifies a trap receiver and configures the operational parameters for the trap receiver. A trap reports significant events that occur on a network device such as errors or failures.

Before an SNMP trap can be issued to a trap receiver, the log-id, snmp-trap-group, and at least one snmp-trap-group must be configured.

The snmp-trap-group command is used to add or remove a trap receiver from an snmp-trap-group. The operational parameters specified in the command include:

  • The IP address of the trap receiver

  • The UDP port used to send the SNMP trap

  • SNMP version

  • SNMP community name for SNMPv1 and SNMPv2c receivers.

  • Security name and level for SNMPv3 trap receivers.

A single snmp-trap-group log-id can have multiple trap-receivers. Each trap receiver can have different operational parameters.

An address can be configured as a trap receiver more than once as long as a different port is used for each instance.

To prevent resource limitations, only configure a maximum of 10 trap receivers.

If the same trap-target name port port parameter value is specified in more than one SNMP trap group, each trap destination should be configured with a different notify-community value. This allows a trap receiving an application, such as NMS, to reconcile a separate event sequence number stream for each router event log when multiple event logs are directed to the same IP address and port destination.

The no form of this command removes the SNMP trap receiver from the SNMP trap group.

Default

No SNMP trap targets are defined.

Parameters

name

specifies the name of the trap target up to 28 characters in length

address ip-address

The IP address of the trap receiver in dotted decimal notation. Only one IP address destination can be specified per trap destination group.

Values

ipv4-address

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

ipv6-address

x:x:x:x:x:x:x:x[-interface]

x:x:x:x:x:x:d.d.d.d[-interface]

x: [0 to FFFF]H

d: [0 to 255]D

interface: 32 characters maximum, mandatory for link local addresses

The ipv6-address applies to the 7750 SR.

port

Specifies the destination UDP port used to send traps to the destination, expressed as a decimal integer. Only one port can be specified per trap-target statement. If multiple traps need to be issued to the same address then multiple ports must be configured.

Values

1 to 65535

Default

162

snmpv1 | snmpv2c | snmpv3

Specifies the SNMP version format to use for traps sent to the trap receiver.

The keyword snmpv1 selects the SNMP version 1 format. When specifying snmpv1, the notify-community must be configured for the proper SNMP community string that the trap receiver expects to be present in alarms and traps messages. If the SNMP version is changed from snmpv3 to snmpv1, then the notify-community parameter must be changed to reflect the community string rather than the security-name that is used by snmpv3.

The keyword snmpv2c selects the SNMP version 2c format. When specifying snmpv2c, the notify-community must be configured for the proper SNMP community string that the trap receiver expects to be present in alarms and traps messages. If the SNMP version is changed from snmpv3 to snmpv2c, then the notify-community parameter must be changed to reflect the community string rather than the security-name that is used by snmpv3.

The keyword snmpv3 selects the SNMP version 3 format. When specifying snmpv3, the notify-community must be configured for the SNMP security-name. If the SNMP version is changed from snmpv1 or snmpv2c to snmpv3, then the notify-community parameter must be changed to reflect the security-name rather than the community string used by snmpv1 or snmpv2c.

Pre-existing conditions are checked before the snmpv3SecurityName is accepted. These are:

  • The username must be configured.

  • The v3 access group must be configured.

  • The v3 notification view must be configured.

Values

snmpv1, snmpv2c, snmpv3

Default

snmpv3

notify-community community | security-name

Specifies the community string for snmpv1 or snmpv2c or the snmpv3 security-name. If no notify-community is configured, then no alarms nor traps will be issued for the trap destination. If the SNMP version is modified, the notify-community must be changed to the proper form for the SNMP version.

community

The community string as required by the snmpv1 or snmpv2c trap receiver. Allowed values are any string up to 31 characters, composed of printable, 7-bit ASCII characters. If the string contains special characters (for example, #, $, spaces), the entire string must be enclosed within double quotes.

security-name

The security-name as defined in the config>system>security>user context for SNMP v3. The security-name can be an ASCII string up to 31 characters in length.

security-level {no-auth-no-privacy | auth-no-privacy | privacy}

Specifies the required authentication and privacy levels required to access the views configured on this node when configuring an snmpv3 trap receiver.

The keyword no-auth-no-privacy specifies no authentication and no privacy (encryption) are required.

The keyword auth-no-privacy specifies authentication is required but no privacy (encryption) is required. When this option is configured the security-name must be configured for authentication.

The keyword privacy specifies both authentication and privacy (encryption) is required. When this option is configured the security-name must be configured for authentication and privacy.

Values

no-auth-no-privacy, auth-no-privacy, privacy

Default

no-auth-no-privacy. This parameter can only be configured if SNMPv3 is also configured.

replay

Enable replay of missed events to target. If replay is applied to an SNMP trap target address, the address is monitored for reachability. Reachability is determined by whether or not there is a route in the routing table by which the target address can be reached. Before sending a trap to a target address, the SNMP module asks the PIP module if there is either an in-band or out-of-band route to the target address. If there is no route to the SNMP target address, the SNMP module saves the sequence-id of the first event that will be missed by the trap target. When the routing table changes again so that there is now a route by which the SNMP target address can be reached, the SNMP module replays (for example, retransmits) all events generated to the SNMP notification log while the target address was removed from the route table. Because of route table change convergence time, it is possible that one or more events may be lost at the beginning or end of a replay sequence. The cold-start-wait and route-recovery-wait timers under config>log>app-route-notifications can help reduce the probability of lost events.

Platforms

All

trap-target

Syntax

trap-target name [address ip-address] [port port] [snmpv1 | snmpv2c | snmpv3] notify-community communityName | snmpv3SecurityName [security-level {no-auth-no-privacy | auth-no-privacy | privacy}] [replay]

no trap-target name

Context

[Tree] (config>log>snmp-trap-group trap-target)

Full Context

configure log snmp-trap-group trap-target

Description

This command configures a trap receiver and configures the operational parameters for the trap receiver. A trap reports significant events that occur on a network device such as errors or failures.

Before an SNMP trap can be issued to a trap receiver, the log-id, snmp-trap-group and at least one trap-target must be configured.

The trap-target command is used to add/remove a trap receiver from an snmp-trap-group. The operational parameters specified in the command include:

  • The IP address of the trap receiver

  • The UDP port used to send the SNMP trap

  • SNMP version

  • SNMP community name for SNMPv1 and SNMPv2c receivers.

  • Security name and level for SNMPv3 trap receivers.

A single snmp-trap-group log-id can have multiple trap-receivers. Each trap receiver can have different operational parameters.

An address can be configured as a trap receiver more than once as long as a different port is used for each instance.

To prevent resource limitations, only configure a maximum of 10 trap receivers.

Note:

If the same trap-target name port port parameter value is specified in more than one SNMP trap group, each trap destination should be configured with a different notify-community value. This allows a trap receiving an application, such as NMS, to reconcile a separate event sequence number stream for each router event log when multiple event logs are directed to the same IP address and port destination.

The no form of this command removes the SNMP trap receiver from the SNMP trap group.

Parameters

name

Specifies the name of the trap target, up to 28 characters.

ip-address

Specifies the IP address of the trap receiver in dotted decimal notation. Only one IP address destination can be specified per trap destination group. ipv6 applies to the 7750 SR only.

Values

ipv4-address

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

ipv6-address

x:x:x:x:x:x:x:x[-interface]

x:x:x:x:x:x:d.d.d.d[-interface]

x: [0..FFFF]H

d: [0..255]D

interface: 32 characters maximum, mandatory for link local addresses

port

Specifies the destination UDP port used for sending traps to the destination, expressed as a decimal integer. Only one port can be specified per trap-target statement. If multiple traps need to be issued to the same address then multiple ports must be configured.

Default

162

Values

1 to 65535

snmpv1 | snmpv2c | snmpv3

Specifies the SNMP version format to use for traps sent to the trap receiver.

The keyword snmpv1 selects the SNMP version 1 format. When specifying snmpv1, the notify-community must be configured for the proper SNMP community string that the trap receiver expects to be present in alarms and traps messages. If the SNMP version is changed from snmpv3 to snmpv1, then the notify-community parameter must be changed to reflect the community string rather than the security-name that is used by snmpv3.

The keyword snmpv2c selects the SNMP version 2c format. When specifying snmpv2c, the notify-community must be configured for the proper SNMP community string that the trap receiver expects to be present in alarms and traps messages. If the SNMP version is changed from snmpv3 to snmpv2c, then the notify-community parameter must be changed to reflect the community string rather than the security-name that is used by snmpv3.

The keyword snmpv3 selects the SNMP version 3 format. When specifying snmpv3, the notify-community must be configured for the SNMP security-name. The security name is the name of a locally configured user. If the SNMP version is changed from snmpv1 or snmpv2c to snmpv3, then the notify-community parameter must be changed to reflect the security-name rather than the community string used by snmpv1 or snmpv2c.

The following conditions must all be met before traps will be issued using an SNMPv3 trap-target:

The user name must be configured, and must be configured with an snmp group that exists.

The v3 access group must be configured, or be one of the built-in SR OS views.

The v3 notification view must be configured, or be one of the built-in SR OS views.

Default

snmpv3

Values

snmpv1, snmpv2c, snmpv3

community | security-name

Specifies the community string for snmpv1 or snmpv2c or the snmpv3 security-name. If the notify-community is not configured, then no alarms or traps will be issued for the trap destination. If the SNMP version is modified, the notify-community must be changed to the proper form for the SNMP version.

community-name

Specifies the community string as required by the snmpv1 or snmpv2c trap receiver. Allowed values are any string up to 31 characters, composed of printable, 7-bit ASCII characters. If the string contains special characters (for example, #, $, spaces), the entire string must be enclosed within double quotes.

security-name

For SNMPv3 trap targets, specifies the security-name as defined in the config>system> security>user context. The security-name can be an ASCII string up to 31 characters in length.

security-level {no-auth-no-privacy | auth-no-privacy | privacy}

Specifies the required authentication and privacy levels required to access the views configured on this node when configuring an snmpv3 trap receiver.

The keyword no-auth-no-privacy specifies no authentication and no privacy (encryption) are required.

The keyword auth-no-privacy specifies authentication is required but no privacy (encryption) is required. When this option is configured the security-name must be configured for authentication.

The keyword privacy specifies both authentication and privacy (encryption) is required. When this option is configured the security-name must be configured for authentication and privacy.

Default

no-auth-no-privacy. This parameter can only be configured if SNMPv3 is also configured.

Values

no-auth-no-privacy, auth-no-privacy, privacy

replay

Enables the replay of missed events to target. If replay is applied to an SNMP trap target address, the address is monitored for reachability. Reachability is determined by whether or not there is a route in the routing table by which the target address can be reached. Before sending a trap to a target address, the SNMP module asks the PIP module if there is either an in-band or out-of-band route to the target address. If there is no route to the SNMP target address, the SNMP module saves the sequence-id of the first event that will be missed by the trap target. When the routing table changes again so that there is now a route by which the SNMP target address can be reached, the SNMP module replays (for example, retransmits) all events generated to the SNMP notification log while the target address was removed from the route table.

Note:

Due to route table change convergence time, it is possible that one or more events may be lost at the beginning or end of a replay sequence. The cold-start-wait and route-recovery-wait timers under the config>log>app-route-notifications context can help reduce the probability of lost events.

Platforms

All

tree

tree

Syntax

tree [detail] [flat]

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

trigger

trigger

Syntax

trigger trigger-type

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

trigger

Syntax

trigger [data] [iapp] [control]

no trigger

Context

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

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

Full Context

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

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

trigger

Syntax

[no] trigger [neighbor ip-int-name | ip-address]

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

trigger

Syntax

[no] trigger [neighbor ip-int-name | ipv6-address]

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

trigger-alarm-msg

trigger-alarm-msg

Syntax

trigger-alarm-msg message-string

no trigger-alarm-msg

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

trigger-entry

trigger-entry

Syntax

[no] trigger-entry entry-id

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

trigger-fault

trigger-fault

Syntax

trigger-fault {dying-gasp | critical-event}

no trigger-fault

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

trigger-packet

trigger-packet

Syntax

trigger-packet [dhcp] [pppoe] [arp] [dhcp6] [rtr-solicit] [data]

no trigger-packet

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

trigger-packet

Syntax

[no] trigger-packet

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

triggered-policy

triggered-policy

Syntax

[no] triggered-policy

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

triggered-updates

triggered-updates

Syntax

triggered-updates

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

trust-anchor

trust-anchor

Syntax

[no] trust-anchor ca-profile-name

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

trust-anchor

Syntax

[no] trust-anchor ca-profile-name

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

trust-anchor-profile

trust-anchor-profile

Syntax

trust-anchor-profile name [create]

no trust-anchor-profile name

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

trust-anchor-profile

Syntax

trust-anchor-profile name

no trust-anchor-profile

Context

[Tree] (config router if ipsec ipsec-tunnel dyn 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)

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

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

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

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

Full Context

configure router interface ipsec ipsec-tunnel dynamic-keying 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

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

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

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

configure service vprn interface ipsec ipsec-tunnel dynamic-keying 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

VSR

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

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

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

trust-anchor-profile

Syntax

trust-anchor-profile name

no trust-anchor-profile

Context

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

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

Full Context

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

configure system security tls server-tls-profile authenticate-client 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

trust-anchor-profile

Syntax

trust-anchor-profile name [create]

no trust-anchor-profile name

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

trusted

trusted

Syntax

[no] trusted

Context

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

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

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

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

Full Context

configure router interface dhcp trusted

configure service vprn interface dhcp trusted

configure service ies subscriber-interface group-interface dhcp trusted

configure service ies 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 router interface dhcp trusted
  • configure service vprn interface dhcp trusted
  • configure service ies 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

trusted-mac-time

trusted-mac-time

Syntax

trusted-mac-time range

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

trusted-server

trusted-server

Syntax

trusted-server address [create]

[no] trusted-server address

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

ts-list

ts-list

Syntax

ts-list list-name [create]

no ts-list list-name

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

ts-location

ts-location

Syntax

ts-location file-url

no ts-location

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

ts-negotiation

ts-negotiation

Syntax

ts-negotiation ts-list list-name

no ts-negotiation

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

ts-negotiation

Syntax

ts-negotiation ts-list list-name

no ts-negotiation

Context

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

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

Full Context

configure service vprn interface sap ipsec-gw ts-negotiation

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

ts-sync-loss

ts-sync-loss

Syntax

[no] ts-sync-loss

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>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>channel>video>analyzer>alarms ts-sync-loss)

Full Context

configure mcast-management multicast-info-policy bundle 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 channel 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-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s

ttl

ttl

Syntax

ttl value

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

ttl

Syntax

ttl label-ttl

no ttl

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

ttl

Syntax

ttl min-ttl min-label-ttl max-ttl max-label-ttl

no ttl

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

ttl

Syntax

ttl time-to-live

no ttl

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

ttl

Syntax

ttl time-to-live

no ttl

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

ttl

Syntax

ttl value

no ttl

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

ttl

Syntax

ttl time-to-live

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

ttl

Syntax

ttl {lt | gt | eq} ttl-value

ttl range ttl-value ttl-value

no ttl

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

ttl-expired

ttl-expired

Syntax

ttl-expired number seconds

no ttl-expired [number seconds]

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

ttl-expired

Syntax

ttl-expired number seconds [use-matching-address]

no ttl-expired [number seconds]

Context

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

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

Full Context

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

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

ttl-expired

Syntax

ttl-expired [number number] [seconds seconds]

no ttl-expired

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

ttl-expired

Syntax

ttl-expired [number seconds]

no ttl-expired

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

ttl-expired

Syntax

ttl-expired [number seconds]

no ttl-expired

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

ttl-monitoring

ttl-monitoring

Syntax

ttl-monitoring

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

ttl-propagate

ttl-propagate

Syntax

ttl-propagate

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

ttl-propagate

Syntax

ttl-propagate

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

ttl-security

ttl-security

Syntax

ttl-security min-ttl-value

no ttl-security

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

ttl-security

Syntax

ttl-security min-ttl-value

no ttl-security

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

ttl-security

Syntax

ttl-security min-ttl-value

no ttl-security

Context

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

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

[Tree] (config>system>login-control>ssh 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 router bgp group neighbor ttl-security

configure system login-control ssh 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

tunnel

tunnel

Syntax

tunnel tunnel-name [create]

no tunnel tunnel-name

Context

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

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

Full Context

configure service vprn l2tp group tunnel

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

tunnel

Syntax

tunnel connection-id

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

tunnel

Syntax

tunnel service-id backbone-dest-mac mac-name isid ISID

tunnel service-id backbone-dest-mac ieee-address isid ISID

no tunnel

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

tunnel

Syntax

tunnel ipsec-tunnel-name [detail] [no-dpd-debug] [display-keys]

no tunnel ipsec-tunnel-name

Context

[Tree] (debug>ipsec tunnel)

Full Context

debug ipsec tunnel

Description

This command enables debugging for specified IPsec tunnel.

Note:

Up to 16 IPsec tunnels are allowed, to enable debugging, at a time.

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

tunnel

Syntax

[no] tunnel ip-address

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

tunnel

Syntax

tunnel name [create]

no tunnel name

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

tunnel

Syntax

tunnel

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

tunnel-client-attrs

tunnel-client-attrs

Syntax

[no] tunnel-client-attrs

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

tunnel-dot1q

tunnel-dot1q

Syntax

[no] tunnel-dot1q

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

tunnel-down-damp-time

tunnel-down-damp-time

Syntax

tunnel-down-damp-time seconds

no tunnel-down-damp-time

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

tunnel-elmi

tunnel-elmi

Syntax

[no] tunnel-elmi

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

tunnel-encaps

tunnel-encaps

Syntax

tunnel-encaps

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

tunnel-encryption

tunnel-encryption

Syntax

tunnel-encryption

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

tunnel-endpoint

tunnel-endpoint

Syntax

tunnel-endpoint [tunnel-spf] [tunnel-leak ip-address]

no tunnel-endpoint

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

tunnel-endpoint

Syntax

tunnel-endpoint [tunnel-spf ip-address] [tunnel-leak ip-address]

Context

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

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

Full Context

debug router ospf3 tunnel-endpoint

debug router ospf 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

tunnel-endpoint-id

tunnel-endpoint-id

Syntax

tunnel-endpoint-id tunnel-endpoint-id

no tunnel-endpoint-id

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

tunnel-endpoint-id

Syntax

tunnel-endpoint-id tunnel-endpoint-id

no tunnel-endpoint-id

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

tunnel-far-end

tunnel-far-end

Syntax

tunnel-far-end ip-address | ipv6-address

no tunnel-far-end [ip-address | ipv6-address]

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

tunnel-fault

tunnel-fault

Syntax

tunnel-fault {accept | ignore}

Context

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

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

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

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

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

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

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

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

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

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

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

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

Full Context

configure service vprn eth-cfm tunnel-fault

configure service epipe sap eth-cfm tunnel-fault

configure service ies interface sap eth-cfm tunnel-fault

configure service vpls sap eth-cfm tunnel-fault

configure service vprn interface sap eth-cfm tunnel-fault

configure service ipipe sap eth-cfm tunnel-fault

configure service ies eth-cfm tunnel-fault

configure service epipe eth-cfm tunnel-fault

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

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

configure service vpls eth-cfm tunnel-fault

configure service ipipe 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 ipipe eth-cfm tunnel-fault
  • configure service vpls eth-cfm tunnel-fault
  • configure service vpls sap eth-cfm tunnel-fault
  • configure service ies eth-cfm tunnel-fault
  • configure service epipe eth-cfm tunnel-fault
  • configure service vprn eth-cfm tunnel-fault
  • configure service ies interface sap eth-cfm tunnel-fault
  • configure service epipe sap eth-cfm tunnel-fault
  • configure service ipipe sap 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

tunnel-group

tunnel-group

Syntax

tunnel-group tunnel-group-id [create]

tunnel-group tunnel-group-id isa-scale-mode isa-scale-mode [create]

no tunnel-group tunnel-group-id

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. On VSR, isa-scale-mode must be specified, which defines the number of tunnels on each ISA.

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.

Values

tunnel-limit-32k, where k equals 1024

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

tunnel-group

Syntax

tunnel-group tunnel-group-id [create]

no tunnel-group tunnel-group-id

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

tunnel-group

Syntax

tunnel-group tunnel-group-id [create]

no tunnel-group tunnel-group-id

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

tunnel-group

Syntax

tunnel-group tunnel-group-id sync-tag tag-name [create]

no tunnel-group tunnel-group-id

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

tunnel-group

Syntax

tunnel-group tunnel-group-id

no tunnel-group

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

tunnel-id

tunnel-id

Syntax

tunnel-id tunnel-id

no tunnel-id

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

tunnel-interface

tunnel-interface

Syntax

[no] tunnel-interface {rsvp-p2mp lsp-name | ldp-p2mp p2mp-id sender sender-address [root-node]}

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

tunnel-interface

Syntax

tunnel-interface [rsvp-p2mp lsp-name] [sender ip-address] [detail]

tunnel-interface [ldp-p2mp p2mp-id] [sender ip-address] [detail]

no tunnel-interface [rsvp-p2mp lsp-name] [sender ip-address]

no tunnel-interface [ldp-p2mp p2mp-id] [sender ip-address]

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

tunnel-interface

Syntax

[no] tunnel-interface rsvp-p2mp lsp-name sender ip-address

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

tunnel-local-address

tunnel-local-address

Syntax

tunnel-local-address ip-address

no tunnel-local-address

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

tunnel-member-pool

tunnel-member-pool

Syntax

tunnel-member-pool name [create]

no tunnel-member-pool name

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

tunnel-mtu

tunnel-mtu

Syntax

tunnel-mtu mtu-bytes

no tunnel-mtu

Context

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

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

Full Context

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

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

tunnel-mtu

Syntax

tunnel-mtu mtu-bytes

no tunnel-mtu

Context

[Tree] (config>router>nat>inside>dual-stack-lit>address tunnel-mtu)

Full Context

configure router nat inside dual-stack-lit 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.

tunnel-mtu

Syntax

tunnel-mtu bytes

no tunnel-mtu

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

tunnel-mtu

Syntax

tunnel-mtu bytes

no tunnel-mtu

Context

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

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

Full Context

configure router ospf segment-routing tunnel-mtu

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

tunnel-nearest-bridge

tunnel-nearest-bridge

Syntax

[no] tunnel-nearest-bridge

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

tunnel-next-hop

tunnel-next-hop

Syntax

tunnel-next-hop

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

tunnel-next-hop

Syntax

tunnel-next-hop

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.

Note:

An SR tunnel cannot resolve to SR-TE IGP shortcuts.

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

tunnel-next-hop

Syntax

tunnel-next-hop

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.

Note:

An SR tunnel cannot resolve to SR-TE IGP shortcuts.

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

tunnel-port-policy

tunnel-port-policy

Syntax

tunnel-port-policy [tunnel-port-policy]

no tunnel-port-policy

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

tunnel-qinq

tunnel-qinq

Syntax

[no] tunnel-qinq

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

tunnel-query

tunnel-query

Syntax

tunnel-query query-id [name name] [create]

no tunnel-query query-id

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

tunnel-remote-address

tunnel-remote-address

Syntax

tunnel-remote-address ip-address

no tunnel-remote-address

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

tunnel-resource-limit

tunnel-resource-limit

Syntax

tunnel-resource-limit direction direction [create]

no tunnel-resource-limit direction direction

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

tunnel-router

tunnel-router

Syntax

tunnel-router router-instance

no tunnel-router

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

tunnel-selection-blacklist

tunnel-selection-blacklist

Syntax

tunnel-selection-blacklist

Context

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

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

Full Context

configure service vprn l2tp tunnel-selection-blacklist

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

tunnel-server-attrs

tunnel-server-attrs

Syntax

[no] tunnel-server-attrs

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

tunnel-session-limit

tunnel-session-limit

Syntax

tunnel-session-limit session-limit

tunnel-session-limit unlimited

no tunnel-session-limit

Context

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

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

Full Context

configure router l2tp tunnel-session-limit

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

tunnel-source-ip

tunnel-source-ip

Syntax

tunnel-source-ip ipv6-address/prefix-length

no tunnel-source-ip

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

tunnel-table

tunnel-table

Syntax

tunnel-table [ip-address] [{ldp | rsvp [tunnel-id tunnel-id] | sdp [sdp-id sdp-id}]]

Context

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

Full Context

debug router ip tunnel-table

Description

This command enables debugging for tunnel tables.

Platforms

All

tunnel-table-pref

tunnel-table-pref

Syntax

tunnel-table-pref preference

no tunnel-table-pref

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

tunnel-table-pref

Syntax

tunnel-table-pref

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

tunnel-table-pref

Syntax

tunnel-table-pref preference-value

no tunnel-table-pref

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

tunnel-table-pref

Syntax

tunnel-table-pref preference

no tunnel-table-pref

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

tunnel-table-pref

Syntax

tunnel-table-pref preference

no tunnel-table-pref

Context

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

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

Full Context

configure router ospf3 segment-routing tunnel-table-pref

configure router ospf 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).

Note:

The preference of an SR-TE LSP is not configurable and is the second most preferred tunnel type after RSVP-TE. The preference is the same whether if the SR-TE LSP was resolved in IS-IS or 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

tunnel-template

tunnel-template

Syntax

tunnel-template tunnel-template-id

no tunnel-template

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

tunnel-template

Syntax

tunnel-template ipsec-template-identifier [ create]

no tunnel-template ipsec-template-identifier

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

tunnel-termination

tunnel-termination

Syntax

tunnel-termination {ip-address | ipv6-address} fpe fpe-id [create]

no tunnel-termination {ip-address | ipv6-address}

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

tunnel-termination

Syntax

tunnel-termination ip-address fpe fpe-id [create]

no tunnel-termination ip-address

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

tunnel-termination

Syntax

tunnel-termination [ip-address | ipv6-address] fpe fpe-id [create]

no tunnel-termination [ip-address | ipv6-address]

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

tunnel-type

tunnel-type

Syntax

tunnel-type {gre | l2tp | l2 | vxlan | not-specified}

no tunnel-type

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

tunneling

tunneling

Syntax

[no] tunneling

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

tunneling

Syntax

[no] tunneling

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

tunneling

Syntax

[no] tunneling

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

tunneling

Syntax

[no] tunneling

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

twamp

twamp

Syntax

twamp

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

twamp-light

twamp-light

Syntax

twamp-light [test-id test-id] [create]

no twamp-light

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

twamp-light

Syntax

twamp-light

Context

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

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

[Tree] (config>router twamp-light)

Full Context

configure service vprn twamp-light

configure test-oam twamp twamp-light

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

twamp-light

Syntax

twamp-light

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

twamp-light

Syntax

twamp-light

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

twamp-light

Syntax

twamp-light

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

two-way-delay-test

two-way-delay-test

Syntax

two-way-delay-test {mac-address | remote-mepid mep-id} mep mep-id domain md-index association ma-index [priority priority]

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

two-way-slm-test

two-way-slm-test

Syntax

two-way-slm-test {mac-address | remote-mepid mep-id} mep mep-id domain md-index association ma-index [priority priority] [send-count send-count] [size data-size] [timeout timeout] [interval interval]

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

tx

tx

Syntax

tx

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

tx

Syntax

tx auto-generated

tx bytes byte-string [byte-string...(up to 64 byte-strings max, 64 bytes max)]

tx string identifier

no tx

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, config>port>dwdm>coherent channel, config>port>dwdm>tdcm 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

tx

Syntax

tx byte

tx auto

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

tx

Syntax

tx auto-generated

tx bytes byte-string [byte-string)]

tx string identifier

no tx

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, config>port>dwdm>coherent channel, config>port>dwdm>tdcm 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

tx

Syntax

tx {string identifier | bytes byte-sequence | auto-generated}

Context

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

Full Context

configure port otu psi-trace tx

Description

This command allows the user to configure the transmit trace in bytes 1 to 255 (skipping byte 0) of the payload structure identifier (PSI) of the OPU 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 255 bytes.

Default

Blank (all zeros)

Parameters

auto-generated

Sets the default PSI trace.

identifier

Sets the PSI trace to the string provided by the user. If the string is less than 255 bytes, the remaining bytes will be set to 0.

byte-sequence

[byte1 byte2 to byte64] Sets the PSI trace 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

tx-credit-max

tx-credit-max

Syntax

tx-credit-max count

no tx-credit-max

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

tx-dus

tx-dus

Syntax

[no] tx-dus

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

tx-eth-ed

tx-eth-ed

Syntax

[no] tx-eth-ed

Context

[Tree] (config>lag>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>port>ethernet>eth-cfm>mep>grace>eth-ed tx-eth-ed)

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

Full Context

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

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

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

configure eth-ring path 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

tx-eth-ed

Syntax

[no] tx-eth-ed

Context

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

[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)

Full Context

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

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

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

tx-eth-ed

Syntax

[no] tx-eth-ed

Context

[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>sap>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 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 sap 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

tx-eth-ed

Syntax

[no] tx-eth-ed

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

tx-eth-ed

Syntax

[no] tx-eth-ed

Context

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

[Tree] (config>service>vprn>sub-if>grp-if>sap>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 interface spoke-sdp eth-cfm mep grace eth-ed tx-eth-ed

configure service vprn subscriber-interface group-interface sap 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, 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

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

tx-eth-ed

Syntax

[no] 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

tx-eth-vsm-grace

tx-eth-vsm-grace

Syntax

[no] tx-eth-vsm-grace

Context

[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>port>ethernet>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 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 port ethernet 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

tx-eth-vsm-grace

Syntax

[no] tx-eth-vsm-grace

Context

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

[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)

Full Context

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

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

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

tx-eth-vsm-grace

Syntax

[no] tx-eth-vsm-grace

Context

[Tree] (config>service>vpls>sap>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)

[Tree] (config>service>vpls>mesh-sdp>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 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

configure service vpls mesh-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, 7950 XRS

tx-eth-vsm-grace

Syntax

[no] tx-eth-vsm-grace

Context

[Tree] (config>service>ies>if>sap>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)

[Tree] (config>service>ies>if>spoke-sdp>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 subscriber-interface group-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

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

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

tx-eth-vsm-grace

Syntax

[no] tx-eth-vsm-grace

Context

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

[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>spoke-sdp>eth-cfm>mep>grace>eth-vsm-grace tx-eth-vsm-grace)

Full Context

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

configure service vprn subscriber-interface group-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, 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

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

tx-eth-vsm-grace

Syntax

[no] 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

tx-hold-multiplier

tx-hold-multiplier

Syntax

tx-hold-multiplier multiplier

no tx-hold-multiplier

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

tx-interval

tx-interval

Syntax

tx-interval interval

no tx-interval

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

tx-mgmt-address

tx-mgmt-address

Syntax

tx-mgmt-address [system] [system-ipv6] [ oob] [oob-ipv6]

no tx-mgmt-address

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

tx-timer

tx-timer

Syntax

tx-timer seconds

no tx-timer

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

tx-tlvs

tx-tlvs

Syntax

tx-tlvs [port-desc] [ sys-name] [sys-desc] [sys-cap]

no tx-tlvs

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

tx-while-sync-uncertain

tx-while-sync-uncertain

Syntax

[no] tx-while-sync-uncertain

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

type

type

Syntax

type {sr-mpls | srv6}

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

type

Syntax

type reflector-type

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

type

Syntax

[no] type {internal | external}

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

type

Syntax

[no] type

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

type

Syntax

type [type] [vendor-id vendor-id]

no type

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

type

Syntax

[no] type {internal | external}

Context

[Tree] (config>service>vprn>bgp>group>neighbor type)

[Tree] (config>service>vprn>bgp>group type)

Full Context

configure service vprn bgp group neighbor type

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

type

Syntax

type [hub | spoke | subscriber-split-horizon]

no type

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

type

Syntax

[no] type

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

type

Syntax

type filter-type

no type

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

type

Syntax

type filter-type

no type

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

type

Syntax

type redirect-list-type

no type

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

type

Syntax

type {normal | src-mac | packet-length| destination-class}

Context

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

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

Full Context

configure filter ipv6-filter type

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

type

Syntax

type filter-type

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

type

Syntax

type {cpm-np}

no type

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

type

Syntax

type file-url [no-redirect] [client-tls-profile profile] [proxy proxy-url]

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

type

Syntax

type schedule-type

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

type

Syntax

type indicator-type

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

type

Syntax

type all

type [gnmi-capabilities] [gnmi-get] [gnmi-set] [gnmi-subscribe] [gnoi-cert-mgmt-rpcs]

no type

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

type

Syntax

[no] type {internal | external}

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

type

Syntax

type {1 | 2}

no type

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

type

Syntax

type {type | param-name}

no type

Context

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

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

Full Context

configure router policy-options policy-statement entry action type

configure router policy-options policy-statement default-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 (#, $, spaces, and so on), the entire string must be enclosed within double quotes. Policy parameters must start and end with at-signs (@); for example, "@variable@”.

Platforms

All

type-multi-line

type-multi-line

Syntax

[no] type-multi-line

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