t Commands – Part I
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.
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.
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.
Platforms
All
tacplus
tacplus
Syntax
no tacplus
tacplus [create]
Context
[Tree] (config>service>vprn>aaa>rmt-srv 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.
Parameters
- create
-
Keyword to create 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.
Platforms
All
tag
Syntax
tag tag-value
no tag [tag-value]
Context
[Tree] (config>service>vprn>static-route-entry>next-hop tag)
[Tree] (config>service>vprn>static-route-entry>ipsec-tunnel tag)
[Tree] (config>service>vprn>static-route-entry>indirect tag)
Full Context
configure service vprn static-route-entry next-hop tag
configure service vprn static-route-entry ipsec-tunnel tag
configure service vprn static-route-entry indirect 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.
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.
Platforms
All
tag
Syntax
tag tag
no tag [tag]
Context
[Tree] (config>router>static-route-entry>indirect tag)
[Tree] (config>router>static-route-entry tag)
[Tree] (config>router>static-route-entry>black-hole tag)
[Tree] (config>router>static-route-entry>next-hop tag)
Full Context
configure router static-route-entry indirect tag
configure router static-route-entry tag
configure router static-route-entry black-hole tag
configure router static-route-entry next-hop 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.
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.
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.
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.
- 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>entry>action tag)
[Tree] (config>router>policy-options>policy-statement>default-action tag)
Full Context
configure router policy-options policy-statement entry action tag
configure router policy-options policy-statement default-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.
Platforms
All
tag
Syntax
tag tag-id
no tag
Context
[Tree] (config>qos>sap-ingress>ip-criteria>entry tag)
[Tree] (config>qos>sap-ingress>ipv6-criteria>entry tag)
Full Context
configure qos sap-ingress ip-criteria entry tag
configure qos sap-ingress ipv6-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.
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.
Platforms
7450 ESS, 7750 SR, 7750 SR-s, 7950 XRS, VSR
tag
Syntax
tag value
no tag
Context
[Tree] (config>service>ies>sub-if>grp-if>sap>static-host>managed-routes>route-entry tag)
[Tree] (config>service>vprn>sub-if>grp-if>sap>static-host>managed-routes>route-entry tag)
Full Context
configure service ies subscriber-interface group-interface sap static-host managed-routes route-entry tag
configure service vprn 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.
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] (debug>oam>build-packet>packet>field-override>header>dot1q tag-protocol-id)
[Tree] (config>test-oam>build-packet>header>dot1q tag-protocol-id)
Full Context
debug oam build-packet packet field-override header dot1q tag-protocol-id
configure test-oam build-packet 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.
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.
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.
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>epipe>spoke-sdp>pw-path-id taii-type2)
[Tree] (config>service>vpls>spoke-sdp>pw-path-id taii-type2)
Full Context
configure service cpipe spoke-sdp pw-path-id taii-type2
configure service epipe spoke-sdp pw-path-id taii-type2
configure service vpls 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.
- node-id
-
Specifies the node ID at the target PE or T-PE for the MPLS-TP PW for a spoke SDP.
- 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.
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.
- 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.
- ac-id
-
Specifies an unsigned integer representing a locally unique identifier for the spoke SDP.
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.
- node-id
-
Specifies the node ID at the target PE or T-PE for the MPLS-TP PW for a spoke-SDP.
- 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.
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.
- node-id
-
Specifies the node ID at the target PE or T-PE for the MPLS-TP PW for a spoke SDP.
- 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.
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.
- node-id
-
Specifies the node ID at the target PE or T-PE for the MPLS-TP PW for a spoke SDP.
- 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.
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.
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.
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 task)
[Tree] (debug>router>pcep>pcc>conn task)
Full Context
debug router pcep pcc task
debug router pcep pcc connection 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>conn task)
[Tree] (debug>router>pcep>pce task)
Full Context
debug router pcep pce connection task
debug router pcep pce 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.
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>ingr-ipv6>entry>match tcp-ack)
[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>ingr-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>egr-ip>entry>match tcp-ack)
Full Context
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
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 egress-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>ipv6-filter>entry>match tcp-ack)
[Tree] (config>filter>ip-filter>entry>match tcp-ack)
Full Context
configure filter ipv6-filter entry match tcp-ack
configure filter ip-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.
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>shr-res-pool tcp-adv-func)
Full Context
configure isa application-assurance-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.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
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>firewall-policy>timeouts tcp-established)
[Tree] (config>service>nat>nat-policy>timeouts tcp-established)
[Tree] (config>service>nat>up-nat-policy>timeouts tcp-established)
Full Context
configure service nat firewall-policy timeouts tcp-established
configure service nat nat-policy timeouts tcp-established
configure service nat up-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.
- minutes
-
Specifies the timeout minutes field.
- seconds
-
Specifies the timeout seconds field.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat firewall-policy timeouts tcp-established
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat nat-policy timeouts tcp-established
- configure service nat up-nat-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>telemetry>destination-group tcp-keepalive)
[Tree] (config>system>grpc-tunnel>destination-group tcp-keepalive)
Full Context
configure system telemetry destination-group tcp-keepalive
configure system grpc-tunnel 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>ipv6 tcp-mss)
[Tree] (config>service>ies>if tcp-mss)
Full Context
configure service ies interface ipv6 tcp-mss
configure service ies interface 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
Platforms
All
tcp-mss
Syntax
tcp-mss mss-value
no tcp-mss
Context
[Tree] (config>service>vprn>nw-if tcp-mss)
[Tree] (config>service>vprn>if tcp-mss)
[Tree] (config>service>vprn>if>ipv6 tcp-mss)
Full Context
configure service vprn network-interface tcp-mss
configure service vprn interface tcp-mss
configure service vprn interface ipv6 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
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
Platforms
All
tcp-mss
Syntax
tcp-mss mss-value
no tcp-mss
Context
[Tree] (config>router>bgp tcp-mss)
[Tree] (config>service>vprn>bgp tcp-mss)
Full Context
configure router bgp tcp-mss
configure service vprn 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.
Platforms
All
tcp-mss
Syntax
tcp-mss ip-stack
tcp-mss mss-value
no tcp-mss
Context
[Tree] (config>service>vprn>bgp>group tcp-mss)
[Tree] (config>router>bgp>group>neighbor tcp-mss)
[Tree] (config>router>bgp>group tcp-mss)
[Tree] (config>service>vprn>bgp>group>neighbor tcp-mss)
Full Context
configure service vprn bgp group tcp-mss
configure router bgp group neighbor tcp-mss
configure router bgp group tcp-mss
configure service vprn 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.
- 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.
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>policy>aqp>entry>action tcp-mss-adjust)
Full Context
configure application-assurance group policy 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.
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>up-nat-policy tcp-mss-adjust)
[Tree] (config>service>nat>firewall-policy tcp-mss-adjust)
[Tree] (config>service>nat>nat-policy tcp-mss-adjust)
Full Context
configure service nat up-nat-policy tcp-mss-adjust
configure service nat firewall-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.
Platforms
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
7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat firewall-policy tcp-mss-adjust
tcp-mss-adjust
Syntax
tcp-mss-adjust
Context
[Tree] (config>filter>ipv6-filter>entry>action tcp-mss-adjust)
[Tree] (config>filter>ip-filter>entry>action tcp-mss-adjust)
Full Context
configure filter ipv6-filter entry action tcp-mss-adjust
configure filter ip-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.
Platforms
7750 SR-1-24D, 7750 SR-1-46S, 7750 SR-1-48D, 7750 SR-1-92S, 7750 SR-1x-48D, 7750 SR-1x-92S, 7750 SR-1se, 7750 SR-2se, 7750 SR-7s, 7750 SR-14s, 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.
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>firewall-policy>timeouts tcp-rst)
[Tree] (config>service>nat>nat-policy>timeouts tcp-rst)
Full Context
configure service nat up-nat-policy timeouts tcp-rst
configure service nat firewall-policy timeouts tcp-rst
configure service nat nat-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.
- sec
-
Specifies the timeout, in seconds, after receiving a RST and closing the session before going to the LISTEN state again.
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.
-
The TCP stack used toward the core network is new-reno, and it is not configurable.
-
TCP BBR, BBRv2, TCP Illinois, and TCP Westwood implement a sender-side modification of the TCP congestion window algorithm that improves on the performance of TCP Reno in wireless networks with lossy links.
The no form of this command configures the router to use the default value.
Default
tcp-westwood
Parameters
- tcp-stack-type
-
Specifies the TCP stack used toward the subscriber.
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>egr-ipv6>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-ip>entry>match tcp-syn)
[Tree] (config>subscr-mgmt>cat-map>category>exh-lvl>ingr-ipv6>entry>match tcp-syn)
Full Context
configure subscriber-mgmt category-map category exhausted-credit-service-level egress-ipv6-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-ip-filter-entries entry match tcp-syn
configure subscriber-mgmt category-map category exhausted-credit-service-level ingress-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>up-nat-policy>timeouts tcp-syn)
[Tree] (config>service>nat>nat-policy>timeouts tcp-syn)
[Tree] (config>service>nat>firewall-policy>timeouts tcp-syn)
Full Context
configure service nat up-nat-policy timeouts tcp-syn
configure service nat nat-policy timeouts tcp-syn
configure service nat firewall-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.
- minutes
-
Specifies the timeout minutes field.
- seconds
-
Specifies the timeout seconds field.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat up-nat-policy timeouts tcp-syn
- configure service nat 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>ip-filter>entry>match tcp-syn)
[Tree] (config>filter>ipv6-filter>entry>match tcp-syn)
Full Context
configure filter ip-filter entry match tcp-syn
configure filter ipv6-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.
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>up-nat-policy>timeouts tcp-time-wait)
[Tree] (config>service>nat>firewall-policy>timeouts tcp-time-wait)
Full Context
configure service nat nat-policy timeouts tcp-time-wait
configure service nat up-nat-policy timeouts tcp-time-wait
configure service nat firewall-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.
- seconds
-
Specifies the timeout seconds field.
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>firewall-policy>timeouts tcp-transitory)
[Tree] (config>service>nat>nat-policy>timeouts tcp-transitory)
[Tree] (config>service>nat>up-nat-policy>timeouts tcp-transitory)
Full Context
configure service nat firewall-policy timeouts tcp-transitory
configure service nat nat-policy timeouts tcp-transitory
configure service nat up-nat-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.
- minutes
-
Specifies the timeout minutes field.
- seconds
-
Specifies the timeout seconds field.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat firewall-policy timeouts tcp-transitory
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
tcp-urg
tcp-urg
Syntax
tcp-urg {true | false}
no tcp-urg
Context
[Tree] (config>filter>ipv6-filter>entry>match tcp-urg)
[Tree] (config>filter>ip-filter>entry>match tcp-urg)
Full Context
configure filter ipv6-filter entry match tcp-urg
configure filter ip-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.
- 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
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.
- 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.
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.
- class-type ct-number
-
Specifies the Diff-Serv Class Type number. One or more system forwarding classes can be mapped to a CT.
- priority priority
-
Specifies the LSP priority.
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.
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.
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)
Full Context
debug router rsvp 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.
Platforms
All
tech-support
tech-support
Syntax
tech-support [file-url]
Context
[Tree] (admin tech-support)
[Tree] (admin>satellite>eth-sat tech-support)
Full Context
admin tech-support
admin satellite eth-sat 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)
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.
Platforms
All
- admin tech-support
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- admin satellite eth-sat tech-support
tei-set
tei-set
Syntax
[no] tei-set
Context
[Tree] (config>mcast-mgmt>mcast-info-plcy>bundle>channel>video>analyzer>alarms tei-set)
[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)
Full Context
configure mcast-management multicast-info-policy bundle channel video analyzer alarms tei-set
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
Description
This command configures the analyzer to check for TEI set errors.
Default
no tei-set
Platforms
7450 ESS, 7750 SR, 7750 SR-s
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.
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
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 7450 ESS, 7750 SR, 7950 XRS, and VSR 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).
- 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.
- router-instance
-
Specifies the router name or service ID used to identify the router instance.
- 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.
Platforms
All
telnet
telnet-max-sessions
telnet-max-sessions
Syntax
telnet-max-sessions number-of-sessions
no telnet-max-sessions
Context
[Tree] (config>system>security>cli-session-group telnet-max-sessions)
[Tree] (config>system>security>profile telnet-max-sessions)
Full Context
configure system security cli-session-group telnet-max-sessions
configure system security profile 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.
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>vrrp telnet-reply)
[Tree] (config>service>vprn>if>ipv6>vrrp telnet-reply)
Full Context
configure service vprn interface vrrp telnet-reply
configure service vprn 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 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>template>vpls-template temp-flooding)
[Tree] (config>service>vpls temp-flooding)
Full Context
configure service template vpls-template temp-flooding
configure service vpls 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
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>tcp-perf template)
[Tree] (config>app-assure>group>cflowd>volume template)
[Tree] (config>app-assure>group>cflowd>comp template)
Full Context
configure application-assurance group cflowd tcp-performance template
configure application-assurance group cflowd volume template
configure application-assurance group cflowd comprehensive 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 template)
[Tree] (config>app-assure>group>http-error-redirect template)
Full Context
configure application-assurance group template
configure application-assurance group http-error-redirect 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.
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.
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.
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.
-
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.
-
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.
-
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.
- minutes
-
Specifies the time interval, in minutes, after which IPFIX templates are resent to this collector.
- seconds
-
Specifies the time interval, in seconds, after which IPFIX templates are resent to this collector.
- days
-
Specifies the time interval, in days, after which IPFIX templates are resent to this collector.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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>lmm test-duration)
[Tree] (config>oam-pm>session>ethernet>slm test-duration)
[Tree] (config>oam-pm>session>ethernet>dmm test-duration)
Full Context
configure oam-pm session ethernet lmm test-duration
configure oam-pm session ethernet slm test-duration
configure oam-pm session ethernet dmm 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.
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.
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.
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.
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.
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>port>ethernet>eth-cfm>mep>eth-test test-pattern)
[Tree] (config>router>if>eth-cfm>mep>eth-test test-pattern)
Full Context
configure lag eth-cfm mep eth-test-enable test-pattern
configure port ethernet eth-cfm mep eth-test-enable test-pattern
configure router interface 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>epipe>spoke-sdp>eth-cfm>mep>eth-test-enable test-pattern)
[Tree] (config>service>epipe>sap>eth-cfm>mep>eth-test-enable test-pattern)
[Tree] (config>service>ipipe>sap>eth-cfm>mep>eth-test-enable test-pattern)
Full Context
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
configure service ipipe 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>sap>eth-cfm>mep>eth-test-enable test-pattern)
[Tree] (config>service>vpls>mesh-sdp>eth-cfm>mep>eth-test-enable test-pattern)
[Tree] (config>service>vpls>spoke-sdp>eth-cfm>mep>eth-test-enable test-pattern)
Full Context
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
configure service vpls 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.
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>ies>if>sap>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>spoke-sdp>eth-cfm>mep>eth-test-enable test-pattern)
Full Context
configure service ies interface sap 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 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.
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
- 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>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)
[Tree] (config>service>vprn>if>sap>eth-cfm>mep>eth-test-enable test-pattern)
Full Context
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
configure service vprn 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.
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 third-party-nexthop)
[Tree] (config>service>vprn>bgp>group>neighbor third-party-nexthop)
[Tree] (config>service>vprn>bgp>group third-party-nexthop)
Full Context
configure service vprn bgp third-party-nexthop
configure service vprn bgp group neighbor third-party-nexthop
configure service vprn bgp group 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.
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.
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.
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>e1 threshold)
[Tree] (config>port>tdm>ds1 threshold)
Full Context
configure port tdm e1 threshold
configure port tdm ds1 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.
Platforms
All
threshold
Syntax
threshold
Context
[Tree] (config>test-oam>link-meas>template>sw threshold)
[Tree] (config>test-oam>link-meas>template>asw threshold)
Full Context
configure test-oam link-measurement measurement-template sample-window threshold
configure test-oam link-measurement measurement-template aggregate-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 thresholds)
[Tree] (config>router>dhcp6>server>pool>prefix 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 thresholds
configure router dhcp6 local-dhcp-server pool prefix 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.
- seconds
-
Specifies the number of seconds that an event throttling interval lasts.
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.
- low-threshold Mbps
-
Specifies the low threshold value.
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.
- 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.
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.
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.
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.
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.
- 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.
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.
- seconds
-
Specifies the time frame, in seconds, that is used to limit the number of time-exceeded ICMP message to be issued.
Platforms
All
time-exceeded
Syntax
time-exceeded [number seconds]
no time-exceeded
Context
[Tree] (config>service>vprn>if>ipv6>icmp6 time-exceeded)
[Tree] (config>router>if>ipv6>icmp6 time-exceeded)
Full Context
configure service vprn interface ipv6 icmp6 time-exceeded
configure router 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.
- seconds
-
Determines the time frame, in seconds, that is used to limit the number of time-exceeded messages issued per time frame.
Platforms
All