h Commands

Context

[Tree] (config>port>ethernet>dampening half-life)

Full Context

configure port ethernet dampening half-life

Description

This command configures the half-life decay time and the maximum period of time for which the port up state can be suppressed.

The half-life and max-time values must be set at the same time; the ratio of max-time/ half-life must be less than or equal to 49 and greater than or equal to 1.

Parameters

half-life

Specifies the required elapsed time, in seconds, before penalties decay to one-half the initial amount.

Values

1 to 2000

Default

5

max-time

Specifies the maximum suppression time, in seconds, which is the time it can take after the physical link comes up before the worst case accumulated penalties have decayed to the reuse threshold. The maximum penalty is derived from the maximum suppression time, half-life, and reuse threshold, using the following equation:

maximum penalty = (reuse threshold) X 2 expo:(max-time/half-life)

Values

1 to 43200

Default

20

Platforms

All

Context

[Tree] (config>router>policy-options>damping half-life)

Full Context

configure router policy-options damping half-life

Description

This command configures the half-life parameter for the route damping profile.

The half-life value is the time, expressed in minutes, required for a route to remain stable in order for the Figure of Merit (FoM) value to be reduced by one half; for example, if the half-life value is 6 (minutes) and the route remains stable for 6 minutes, then the new FoM value is 3 (minutes). After another 3 minutes pass and the route remains stable, the new FoM value is 1.5 (minutes).

When the FoM value falls below the config>router>policy-options>damping reuse threshold, the route is once again considered valid and can be reused or included in route advertisements.

The no form of this command removes the half life parameter from the damping profile.

Default

no half-life

Parameters

minutes

Specifies the half-life in minutes expressed as a decimal integer.

Values

1 to 45

Platforms

All

Context

[Tree] (config>log>event-handling handler)

Full Context

configure log event-handling handler

Description

This command configures an EHS handler.

The no form of this command removes the specified EHS handler.

Parameters

event-handler-name

Specifies the name of the EHS handler, up to 32 characters maximum.

Platforms

All

Context

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

Full Context

configure system grpc-tunnel tunnel handler

Description

Commands in this context configure tunnel handler parameters. There can be multiple handlers created for any tunnel.

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

Parameters

name

Specifies the handler name, up to 32 characters.

create

Keyword used to create a tunnel.

Platforms

All

Context

[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes hardware-timestamp)

Full Context

configure aaa isa-radius-policy acct-include-attributes hardware-timestamp

Description

This command enables the inclusion of the hardware timestamp attributes.

The no form of the command excludes the hardware timestamp attributes.

Default

no hardware-timestamp

Platforms

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

Context

[Tree] (config>system>security>management-interface>grpc hash-algorithm)

[Tree] (config>system>security>management-interface>netconf hash-algorithm)

[Tree] (config>system>security>management-interface>md-cli hash-algorithm)

Full Context

configure system security management-interface grpc hash-algorithm

configure system security management-interface netconf hash-algorithm

configure system security management-interface md-cli hash-algorithm

Description

This command specifies the format of the input and output for encrypted configuration secrets.

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

Default

hash-algorithm hash2

Parameters

hash

Specifies hash. Use this option to transport a phrase between modules and nodes.

hash2

Specifies hash2 which is module-specific.

custom

Specifies the custom encryption to management interface.

cleartext

Specifies that the phrase is displayed as cleartext everywhere.

Platforms

All

Context

[Tree] (config>system>security>pki>cert-upd-prof hash-algorithm)

Full Context

configure system security pki certificate-update-profile hash-algorithm

Description

This command configures the hash algorithm used to generate a certificate request.

Default

hash-algorithm sha256

Parameters

algorithm

Specifies the hash option.

Values

md5, sha1, sha224, sha256, sha384, sha512

Platforms

All

Context

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

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

[Tree] (config>service>pw-template hash-label)

Full Context

configure service epipe spoke-sdp hash-label

configure service ipipe spoke-sdp hash-label

configure service pw-template hash-label

Description

This command enables the use of the hash label on a VLL, VPRN or VPLS service bound to any MPLS type encapsulated SDP, as well as to a VPRN service that is using the auto-bind-tunnel with the resolution-filter set to any MPLS tunnel type. This feature is not supported on a service bound to a GRE SDP or for a VPRN service using the autobind mode with the gre option. This feature is also not supported on multicast packets forwarded using RSVP P2MP LSP or mLDP LSP in both the base router instance and in the multicast VPN (mVPN) instance. It is, however, supported when forwarding multicast packets using an IES/VPRN spoke-interface.

When this feature is enabled, the ingress data path is modified such that the result of the hash on the packet header is communicated to the egress data path for use as the value of the label field of the hash label. The egress data path appends the hash label at the bottom of the stack (BoS) and sets the S-bit to one (1).

To allow applications where the egress LER infers the presence of the hash label implicitly from the value of the label, the Most Significant Bit (MSB) of the result of the hash is set before copying into the Hash Label. This means that the value of the hash label will always be in the range [524,288 - 1,048,575] and will not overlap with the signaled/static LSP and signaled/static service label ranges. This also guarantees that the hash label will not match a value in the reserved label range.

The (unmodified) result of the hash continues to be used for the purpose of ECMP and LAG spraying of packets locally on the ingress LER. Note, however, that for VLL services, the result of the hash is overwritten and the ECMP and LAG spraying will be based on service-id when ingress SAP shared queuing is not enabled. However, the hash label will still reflect the result of the hash such that an LSR can use it to perform fine grained load balancing of VLL pseudowire packets.

Packets generated in CPM and that are forwarded labeled within the context of a service (for example, OAM packets) must also include a Hash Label at the BoS and set the S-bit accordingly.

The TTL of the hash label is set to a value of 0.

The user enables the signaling of the hash-label capability under a VLL spoke-sdp, a VPLS spoke-sdp or mesh SDP, or an IES/VPRN spoke interface by adding the signal-capability option. In this case, the decision whether to insert the hash label on the user and control plane packets by the local PE is solely determined by the outcome of the signaling process and can override the local PE configuration. The following are the procedures:

• The local PE will insert the flow label interface parameters sub-TLV with F=1 in the PW ID FEC element in the label mapping message for that spoke SDP or mesh SDP.

• If the remote PE includes this sub-TLV with F=1 or F=0, then local PE must insert the hash label in the user and control plane packets.

• If remote PE does not include this sub-TLV (for example, it does not support it, or it is supported but the user did not enable the hash-label option or the signal-capability option), then the local PE establishes the PW but must not insert the hash label in the user and control packets over that spoke SDP or mesh SDP. If the remote PE does not support the signal-capability option, then there are a couple of possible outcomes:

  • If the hash-label option was enabled on the local configuration of the spoke SDP or mesh SDP at the remote PE, the PW packets received by the local PE will have the hash label included. These packets must be dropped. The only way to solve this is to disable the signaling capability option on the local node which will result in the insertion of the hash label by both PE nodes.

  • If the hash-label option is not supported or was not enabled on the local configuration of the spoke SDP or mesh SDP at the remote PE, the PW received by the local PE will not have the hash label included.

• The user can enable or disable the signal-capability option in CLI as needed. When doing so, the 7450 ESS or 7750 SR must withdraw the label it sent to its peer and send a new label mapping message with the new value of the F bit in the flow label interface parameters sub-TLV of the PW ID FEC element.

The no form of this command disables the use of the hash label.

Default

no hash-label

Parameters

signal-capability

Enables the signaling and negotiation of the use of the hash label between the local and remote PE nodes. The signal-capability option is not supported on a VPRN spoke-sdp.

Platforms

All

Context

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

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

Full Context

configure service vpls spoke-sdp hash-label

configure service vpls mesh-sdp hash-label

Description

This command enables the use of the hash label on a VLL, VPRN, or VPLS service bound to any MPLS type encapsulated SDP, as well as to a VPRN service using the auto-bind-tunnel with the resolution-filter set to any MPLS tunnel type. This feature is not supported on a service bound to a GRE SDP or for a VPRN service using the autobind mode with the gre option. This feature is also not supported on multicast packets forwarded using RSVP P2MP LSP or mLDP LSP in both the base router instance and in the multicast VPN (mVPN) instance. It is, however, supported when forwarding multicast packets using an IES/VPRN spoke-interface.

When this feature is enabled, the ingress data path is modified such that the result of the hash on the packet header is communicated to the egress data path for use as the value of the label field of the hash label. The egress data path appends the hash label at the bottom of the stack (BoS) and sets the S-bit to one (1).

To allow applications where the egress LER infers the presence of the hash label implicitly from the value of the label, the Most Significant Bit (MSB) of the result of the hash is set before copying into the Hash Label. This means that the value of the hash label will always be in the range [524,288 - 1,048,575] and will not overlap with the signaled/static LSP and signaled/static service label ranges. This also guarantees that the hash label will not match a value in the reserved label range.

The (unmodified) result of the hash continues to be used for the purpose of ECMP and LAG spraying of packets locally on the ingress LER. Note, however, that for VLL services, the result of the hash is overwritten and the ECMP and LAG spraying will be based on service-id when ingress SAP shared queuing is not enabled. However, the hash label will still reflect the result of the hash such that an LSR can use it to perform fine grained load balancing of VLL pseudowire packets.

Packets generated in CPM and that are forwarded labeled within the context of a service (for example, OAM packets) must also include a Hash Label at the BoS and set the S-bit accordingly.

The TTL of the hash label is set to a value of 0.

The user enables the signaling of the hash-label capability under a VLL spoke-sdp, a VPLS spoke-sdp or mesh-sdp, or an IES/VPRN spoke interface by adding the signal-capability option. In this case, the decision whether to insert the hash label on the user and control plane packets by the local PE is solely determined by the outcome of the signaling process and can override the local PE configuration. The following are the procedures:

• The 7450 ESS, 7750 SR, and 7950 XRS local PE will insert the flow label interface parameters sub-TLV with F=1 in the pseudowire ID FEC element in the label mapping message for that spoke-sdp or mesh-sdp.

• If the remote PE includes this sub-TLV with F=1 or F=0, then local PE must insert the hash label in the user and control plane packets.

• If remote PE does not include this sub-TLV (for example, it does not support it, or it is supported but the user did not enable the hash-label option or the signal-capability option), then the local PE establishes the pseudowire but must not insert the hash label in the user and control packets over that spoke-sdp or mesh-sdp. If the remote PE does not support the signal-capability option, then there are a couple of possible outcomes:

  • If the hash-label option was enabled on the local configuration of the spoke-sdp or mesh-sdp at the remote PE, the pseudowire packets received by the local PE will have the hash label included. These packets must be dropped. The only way to solve this is to disable the signaling capability option on the local node which will result in the insertion of the hash label by both PE nodes.

  • If the hash-label option is not supported or was not enabled on the local configuration of the spoke-sdp or mesh-sdp at the remote PE, the pseudowire received by the local PE will not have the hash label included.

• The user can enable or disable the signal-capability option in CLI as needed. When doing so, the 7450 ESS, 7750 SR, and 7950 XRS must withdraw the label it sent to its peer and send a new label mapping message with the new value of the F bit in the flow label interface parameters sub-TLV of the pseudowire ID FEC element.

The no form of this command disables the use of the hash label.

Default

no hash-label

Parameters

signal-capability

Enables the signaling and negotiation of the use of the hash label between the local and remote PE nodes. The signal-capability option is not supported on a VPRN spoke-sdp.

Platforms

All

Context

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

Full Context

configure service ies interface spoke-sdp hash-label

Description

This command enables the use of the hash label on a VLL, VPLS, or VPRN service bound to any MPLS-type encapsulated SDP, as well as to a VPRN service using auto-bind-tunnel with the resolution-filter configures as any MPLS tunnel type. This feature is not supported on a service bound to a GRE SDP or for a VPRN service using the autobind mode with the gre option.

When this feature is enabled, the ingress data path is modified such that the result of the hash on the packet header is communicated to the egress data path for use as the value of the label field of the hash label. The egress data path appends the hash label at the bottom of the stack (BoS) and sets the S-bit to 1 to indicate that.

In order to allow for applications whereby the egress LER infers the presence of the hash label implicitly from the value of the label, the Most Significant Bit (MSB) of the result of the hash is set before copying into the hash label. This means that the value of the hash label will always be in the range [524,288 to 1,048,575] and will not overlap with the signaled/static LSP and signaled/static service label ranges. This also guarantees that the hash label will not match a value in the reserved label range.

The (unmodified) result of the hash continues to be used for the purpose of ECMP and LAG spraying of packets locally on the ingress LER. For VLL services, the result of the hash is overwritten and the ECMP and LAG spraying will be based on service-id when ingress SAP shared queuing is not enabled. However, the hash label will still reflect the result of the hash such that an LSR can use it to perform fine grained load balancing of VLL pseudowire packets.

Packets that are generated in CPM and forwarded labeled within the context of a service (for example, OAM packets) must also include a hash label at the BoS and set the S-bit accordingly.

The TTL of the hash label is set to a value of 0.

The user enables the signaling of the hash-label capability under a VLL spoke-sdp, a VPLS spoke-sdp or mesh-sdp, or an IES/VPRN spoke interface by adding the signal-capability option. In this case, the decision whether to insert the hash label on the user and control plane packets by the local PE is solely determined by the outcome of the signaling process and can override the local PE configuration. The following are the procedures:

• The local PE will insert the flow label interface parameters sub-TLV with F=1 in the PW ID FEC element in the label mapping message for that spoke-sdp or mesh-sdp.

• If the remote PE includes this sub-TLV with F=1 or F=0, then local PE must insert the hash label in the user and control plane packets.

• If remote PE does not include this sub-TLV (for example, it does not support it, or it is supported but the user did not enable the hash-label option or the signal-capability option), then the local PE establishes the PW but must not insert the hash label in the user and control packets over that spoke-sdp or mesh-sdp. If the remote PE does not support the signal-capability option, then there are a couple of possible outcomes:

  • If the hash-label option was enabled on the local configuration of the spoke-sdp or mesh-sdp at the remote PE, the PW packets received by the local PE will have the hash label included. These packets must be dropped. The only way to solve this is to disable the signaling capability option on the local node which will result in the insertion of the hash label by both PE nodes.

  • If the hash-label option is not supported or was not enabled on the local configuration of the spoke-sdp or mesh-sdp at the remote PE, the PW received by the local PE will not have the hash label included.

• The user can enable or disable the signal-capability option in CLI as needed. When doing so, the router must withdraw the label it sent to its peer and send a new label mapping message with the new value of the F bit in the flow label interface parameters sub-TLV of the PW ID FEC element.

The no form of this command disables the use of the hash label.

Default

no hash-label

Parameters

signal-capability

Enables the signaling and negotiation of the use of the hash label between the local and remote PE nodes. The signal-capability option is not supported on a VPRN spoke-sdp.

Platforms

All

Context

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

[Tree] (config>service>vprn>spoke-sdp hash-label)

[Tree] (config>service>vprn hash-label)

Full Context

configure service vprn interface spoke-sdp hash-label

configure service vprn spoke-sdp hash-label

configure service vprn hash-label

Description

This command enables the use of the hash label on a VLL, VPLS, or VPRN service bound to any MPLS-type encapsulated SDP as well as to a VPRN service using auto-bind-tunnel with the resolution-filter configured as any MPLS tunnel type. This feature is not supported on a service bound to a GRE SDP or for a VPRN service using the autobind mode with the gre option.

When this feature is enabled, the ingress data path is modified such that the result of the hash on the packet header is communicated to the egress data path for use as the value of the label field of the hash label. The egress data path appends the hash label at the bottom of the stack (BoS) and sets the S-bit to 1 to indicate that.

In order to allow for applications whereby the egress LER infers the presence of the Hash Label implicitly from the value of the label, the Most Significant Bit (MSB) of the result of the hash is set before copying into the Hash Label. This means that the value of the hash label will always be in the range [524,288 - 1,048,575] and will not overlap with the signaled/static LSP and signaled/static service label ranges. This also guarantees that the hash label will not match a value in the reserved label range.

The (unmodified) result of the hash continues to be used for the purpose of ECMP and LAG spraying of packets locally on the ingress LER. For VLL services, the result of the hash is overwritten and the ECMP and LAG spraying will be based on service-id when ingress SAP shared queuing is not enabled. However, the hash label will still reflect the result of the hash such that an LSR can use it to perform fine grained load balancing of VLL pseudowire packets.

Packets that are generated in CPM and forwarded labeled within the context of a service (for example, OAM packets) must also include a Hash Label at the BoS and set the S-bit accordingly.

The TTL of the hash label is set to a value of 0.

The no form of this command disables the use of the hash label.

Default

no hash-label

Parameters

signal-capability

Specifies whether the service should send the Stack Capability and check whether the capability is received from the peer via LDP interface parameters.

Platforms

All

Context

[Tree] (config>service>vprn>pim>rp>bsr-candidate hash-mask-len)

Full Context

configure service vprn pim rp bsr-candidate hash-mask-len

Description

This command is used to configure the length of a mask that is to be combined with the group address before the hash function is called. All groups with the same hash map to the same RP. For example, if this value is 24, only the first 24 bits of the group addresses matter. This mechanism is used to map one group or multiple groups to an RP.

Default

hash-mask-len 30

Parameters

hash-mask-length

The hash mask length.

Values

0 to 32

Platforms

All

Context

[Tree] (config>service>vprn>pim>rp>ipv6>bsr-candidate hash-mask-len)

Full Context

configure service vprn pim rp ipv6 bsr-candidate hash-mask-len

Description

This command is used to configure the length of a mask that is to be combined with the group address before the hash function is called. All groups with the same hash map to the same RP. For example, if this value is 24, only the first 24 bits of the group addresses matter. This mechanism is used to map one group or multiple groups to an RP.

Default

hash-mask-len 126

Parameters

hash-mask-length

The hash mask length.

Values

0 to 128

Platforms

All

Context

[Tree] (config>router>pim>rp>ipv6>bsr-candidate hash-mask-len)

[Tree] (config>router>pim>rp>bsr-candidate hash-mask-len)

Full Context

configure router pim rp ipv6 bsr-candidate hash-mask-len

configure router pim rp bsr-candidate hash-mask-len

Description

This command configures the length of a mask that is to be combined with the group address before the hash function is called. All groups with the same hash map to the same RP. For example, if this value is 24, only the first 24 bits of the group addresses matter. This mechanism is used to map one group or multiple groups to an RP.

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

Default

hash-mask-len 30 — for config>router>pim>rp>bsr-candidate

hash-mask-len 126 — for config>router>pim>rp>ipv6> bsr-candidate

Parameters

hash-mask-length

Specifies the hash mask length.

Values

0 to 32 (v4)

0 to 128 (v6)

Platforms

All

Context

[Tree] (config>lag hash-weight-threshold)

Full Context

configure lag hash-weight-threshold

Description

This command controls the operational status of the LAG or the IGP cost based on the sum of the hash-weight values for the active links in the LAG.

The no form of this command disables the hash weight threshold.

Parameters

weight

Specifies the value for the sum of all the active LAG ports hash-weight at or below which the configured action is invoked. If the sum of hash-weight for operational LAG links exceeds the hash-weight-threshold value, then no action is taken.

Values

1 to 6400000

action

Specifies the action to take if the sum of the hash-weight for active links in the LAG is equal or below the threshold value.

Values

down — Specifies that the LAG is operationally DOWN. The LAG is only considered as UP once the number of hash-weight for the active links exceeds the configured threshold value.

dynamic-cost — Specifies that dynamic cost is activated. The LAG remains operationally UP with a link cost relative to the number of operational links. The link is only considered as operationally DOWN when all links in the LAG are down.

static-cost — Specifies that static cost is activated. The LAG remains operationally UP with the configured cost, regardless of the number of operational links. The link is only considered as operationally DOWN when all links in the LAG are down. If this parameter is used with an IGP, its reference-bandwidth must also be configured.

static-cost

Specifies the decimal integer static cost of the LAG.

Values

1 to 16777215

Platforms

All

Context

[Tree] (config>system>security>password hashing)

Full Context

configure system security password hashing

Description

This command configures the password hashing algorithm.

Default

hashing bcrypt

Parameters

bcrypt

Keyword to indicate that the command configures the bcrypt algorithm.

sha2-pbkdf2

Keyword to indicate that the command configures the PBKDF2 algorithm hashed via SHA2.

sha3-pbkdf2

Keyword to indicate that the command configures the PBKDF2 algorithm hashed via SHA3.

Platforms

All

Context

[Tree] (config>mcast-mgmt>mcast-info-plcy>video-policy>video-if hd)

Full Context

configure mcast-management multicast-info-policy video-policy video-interface hd

Description

This command configures properties relating to requests received by the video interface for High Definition (HD) channel requests.

Platforms

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

Context

[Tree] (conf>router>segment-routing>sr-policies>policy head-end)

Full Context

configure router segment-routing sr-policies static-policy head-end

Description

This command associates a head-end location with a statically-defined segment-routing policy. The head-end identifies the router that is the target to install the policy. This is a mandatory parameter and configuration command for enabling the segment-routing policy; if the head-end parameter value is not configured, the execution of the no shutdown command on the static segment routing policy fails.

To associate a static policy with the local router as head-end, the keyword local must be specified. The static policy is associated with another (non-local) router, if the head-end parameter is set to any IPv4 address. When a non-local, static segment routing policy that originates as a BGP route is imported into BGP, the configured head-end address is converted to an IPv4-address specific route-target extended community that is automatically added to the route.

The no form of this command removes the head-end association.

Default

no head-end

Parameters

local

Keyword indicating that the policy is intended to be used by the local router and not advertised to other BGP routers.

ipv4-address

Specifies the IP address of the target head-end router.

Values

ipv4-address:

a.b.c.d

Platforms

All

Context

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

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

Full Context

debug oam build-packet packet field-override header

configure test-oam build-packet header

Description

Commands in this context configure header parameters.

The no form of this command deletes the associated header.

Parameters

header-number

Specifies the ID for the header being defined or referenced.

Values

1 to 65535

create

Creates a header instance. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

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

Context

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>msg header-sanity)

Full Context

configure application-assurance group statistics threshold-crossing-alert gtp-filter message-type header-sanity

Description

This command configures a TCA for the counter capturing hits for the GTP filter header sanity. A GTP filter header-sanity TCA can be created for traffic generated from the subscriber side of AA ( from-sub) or for traffic generated from the network toward the AA subscriber (to-sub). The create keyword is mandatory when creating a TCA.

Parameters

direction

Specifies the traffic direction.

Values

from-sub, to-sub

create

Keyword used to create the TCA.

Platforms

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

Context

[Tree] (debug>oam>build-packet>packet header-sequence)

Full Context

debug oam build-packet packet header-sequence

Description

This command configures the sequence of headers for a packet to be launched by the OAM find-egress tool.

Parameters

header-sequence

Specifies the sequence of headers, such as "h7/h255/h32", where h7 is the header for the lowest level protocol.

Platforms

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

Context

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

Full Context

configure aaa radius-server-policy servers health-check

Description

Commands in this context configure health check parameters for the RADIUS server.

Platforms

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

Context

[Tree] (config>system>security>password health-check)

Full Context

configure system security password health-check

Description

This command enables health check monitoring of the RADIUS, TACACS+, and LDAP servers by sending authentication requests for an unknown user at regular intervals. If a response is not received, the operational status of the server is changed to down. The operational status is changed to up when responses are received.

When RADIUS over TLS is configured, Status-Server packets are sent at 30-second intervals as specified in RFC 3539, regardless of whether health checks are enabled.

The no form of this command disables health monitoring of RADIUS, TACACS+, and LDAP servers. In this case, the operational status for the server is up if a response was received for the last user request.

Default

health-check interval 30

Parameters

interval

Specifies the polling interval for RADIUS, TACACS+, and LDAP servers.

Values

6 to 1500

Default

30

Platforms

All

Context

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

Full Context

configure subscriber-mgmt pfcp-association heartbeat

Description

Commands in this context configure parameters for transmitting PFCP Heartbeat Request messages to a PFCP peer.

Default

heartbeat

Platforms

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

Context

[Tree] (config>router>ldp>if-params>if>ipv4 hello)

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

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

[Tree] (config>router>ldp>targ-session>ipv4 hello)

[Tree] (config>router>ldp>targ-session>ipv6 hello)

[Tree] (config>router>ldp>if-params>ipv6 hello)

[Tree] (config>router>ldp>if-params>if>ipv6 hello)

[Tree] (config>router>ldp>if-params>ipv4 hello)

Full Context

configure router ldp interface-parameters interface ipv4 hello

configure router ldp targeted-session peer-template hello

configure router ldp targeted-session peer hello

configure router ldp targeted-session ipv4 hello

configure router ldp targeted-session ipv6 hello

configure router ldp interface-parameters ipv6 hello

configure router ldp interface-parameters interface ipv6 hello

configure router ldp interface-parameters ipv4 hello

Description

This command configures the time interval to wait before declaring a neighbor down. The factor parameter derives the Hello interval.

The config>router>ldp>if-params>ipv6>hello and config>router>ldp>targ-session>ipv6>hello commands are not supported on the 7450 ESS.

Hold time is local to the system and sent in the Hello messages to the neighbor. Hold time cannot be less than three times the Hello interval. The hold time can be configured globally (applies to all LDP interfaces) or per interface. The most specific value is used.

When LDP session is being set up, the hold down time is negotiated to the lower of the two peers. Once an operational value is agreed upon, the Hello factor is used to derive the value of the Hello interval.

The no form of the command at the interface-parameters and targeted-session level sets the hello timeout and the hello factor to the default values.

The no form of the command, at the interface level, sets the hello timeout and the hello factor to the value defined under the interface-parameters level.

The no form of this command, at the peer level, sets the hello timeout and the hello factor to the value defined under the targeted-session level.

The session must be flapped for the new settings to operate.

Default

Hello Timeout Factors lists the default values.

Parameters

timeout

Configures the time interval, in seconds, that LDP waits before a neighbor down.

Values

1 to 65535

factor

Specifies the number of keepalive messages that should be sent on an idle LDP session in the Hello timeout interval.

Values

1 to 255

Platforms

All

Context

[Tree] (debug>router>ldp>if>packet hello)

[Tree] (debug>router>ldp>peer>packet hello)

Full Context

debug router ldp interface packet hello

debug router ldp peer packet hello

Description

This command enables debugging for LDP Hello packets.

The no form of the command disables the debugging output.

Parameters

detail

Displays detailed information.

Platforms

All

Context

[Tree] (debug>router>rsvp>packet hello)

Full Context

debug router rsvp packet hello

Description

This command debugs Hello packets.

The no form of the command disables the debugging.

Parameters

detail

Displays detailed information about Hello packets.

Platforms

All

Context

[Tree] (config>service>vprn>isis>interface hello-auth-keychain)

[Tree] (config>router>isis hello-auth-keychain)

[Tree] (config>service>vprn>isis>interface>level hello-auth-keychain)

[Tree] (config>router>isis>level hello-auth-keychain)

Full Context

configure service vprn isis interface hello-auth-keychain

configure router isis hello-auth-keychain

configure service vprn isis interface level hello-auth-keychain

configure router isis level hello-auth-keychain

Description

This command configures an authentication keychain to use for the protocol interface. The keychain allows the rollover of authentication keys during the lifetime of a session.

Default

no hello-auth-keychain

Parameters

name

Specifies the name of the keychain, up to 32 characters, to use for the specified protocol session or sessions.

Platforms

All

Context

[Tree] (config>service>vprn>isis hello-authentication)

[Tree] (config>service>vprn>isis>if hello-authentication)

[Tree] (config>service>vprn>isis>level hello-authentication)

Full Context

configure service vprn isis hello-authentication

configure service vprn isis interface hello-authentication

configure service vprn isis level hello-authentication

Description

This command enables authentication of individual IS-IS Hello packets for the VPRN instance.

The no form of this command suppresses authentication of Hello packets.

Platforms

All

Context

[Tree] (config>router>isis hello-authentication)

[Tree] (config>router>isis>level hello-authentication)

[Tree] (config>router>isis>interface hello-authentication)

Full Context

configure router isis hello-authentication

configure router isis level hello-authentication

configure router isis interface hello-authentication

Description

This command enables authentication of individual IS-IS packets of HELLO type.

The no form of this command suppresses authentication of HELLO packets.

Default

hello-authentication

Platforms

All

Context

[Tree] (config>service>vprn>isis>if>level hello-authentication-key)

[Tree] (config>service>vprn>isis>if hello-authentication-key)

Full Context

configure service vprn isis interface level hello-authentication-key

configure service vprn isis interface hello-authentication-key

Description

This command configures the authentication key (password) for Hello PDUs. Neighboring routers use the password to verify the authenticity of Hello PDUs sent from this interface. Both the Hello authentication key and the Hello authentication type on a segment must match. The hello-authentication-type must be specified.

To configure the Hello authentication key in the interface context use the hello-authentication-key in the config>router>isis>if context.

To configure or override the Hello authentication key for a specific level, configure the hello-authentication-key in the config>router>isis>if>level context.

If both IS-IS and hello-authentication are configured, Hello messages are validated using Hello authentication. If only IS-IS authentication is configured, it will be used to authenticate all IS-IS (including Hello) protocol PDUs.

When the Hello authentication key is configured in the config>router>isis>if context, it applies to all levels configured for the interface.

The no form of this command removes the authentication-key from the configuration.

Default

no hello-authentication-key — No Hello authentication key is configured.

Parameters

authentication-key

The Hello authentication key (password). The key can be any combination of ASCII characters up to 254 characters in length (un-encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).

hash-key

The hash key. The key can be any combination of ASCII characters up to 342 characters in length (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).

This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.

hash

Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.

hash2

Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.

custom

Specifies the custom encryption to management interface.

Platforms

All

Context

[Tree] (config>router>isis>if>level hello-authentication-key)

[Tree] (config>router>isis>interface hello-authentication-key)

Full Context

configure router isis interface level hello-authentication-key

configure router isis interface hello-authentication-key

Description

This command configures the authentication key (password) for Hello PDUs. Neighboring routers use the password to verify the authenticity of Hello PDUs sent from this interface. Both the Hello authentication key and the Hello authentication type on a segment must match. The hello-authentication-type must be specified.

To configure the Hello authentication key in the interface context, use the hello-authentication-key in the config>router>isis>interface context.

To configure or override the Hello authentication key for a specific level, configure the hello-authentication-key in the config>router>isis>interface>level context.

If both IS-IS and hello-authentication are configured, Hello messages are validated using Hello authentication. If only IS-IS authentication is configured, it will be used to authenticate all IS-IS (including Hello) protocol PDUs.

When the Hello authentication key is configured in the config>router>isis>interface context, it applies to all levels configured for the interface.

The no form of this command removes the authentication-key from the configuration.

Parameters

authentication-key

Specifies the Hello authentication key (password). The key can be any combination of ASCII characters, up to 254 characters (un-encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).

hash-key

Specifies the hash key. The key can be any combination of ASCII characters, up to 342 characters (encrypted). If spaces are used in the string, enclose the entire string in quotation marks (" ”).

This is useful when a user must configure the parameter, but, for security purposes, the actual unencrypted key value is not provided.

hash

Specifies the key is entered in an encrypted form. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.

hash2

Specifies the key is entered in a more complex encrypted form that involves more variables than the key value alone, meaning that the hash2 encrypted variable cannot be copied and pasted. If the hash or hash2 parameter is not used, the key is assumed to be in an unencrypted, cleartext form. For security, all keys are stored in encrypted form in the configuration file with the hash or hash2 parameter specified.

custom

Specifies the custom encryption to management interface.

Platforms

All

Context

[Tree] (config>service>vprn>isis>if>level hello-authentication-type)

[Tree] (config>service>vprn>isis>if hello-authentication-type)

Full Context

configure service vprn isis interface level hello-authentication-type

configure service vprn isis interface hello-authentication-type

Description

This command enables Hello authentication at either the interface or level context. Both the Hello authentication key and the Hello authentication type on a segment must match. The hello authentication-key statement must also be included.

To configure the Hello authentication type at the interface context, use hello-authentication-type in the config>router>isis>if context.

To configure or override the Hello authentication setting for a given level, configure the hello-authentication-type in the config>router>isis>if>level context.

The no form of this command disables Hello authentication.

Default

no hello-authentication-type — Hello authentication is disabled

Parameters

password

Specifies simple password (plain text) authentication is required.

message-digest

Specifies MD5 authentication in accordance with RFC2104 (HMAC: Keyed-Hashing for Message Authentication) is required.

Platforms

All

Context

[Tree] (config>router>isis>interface hello-authentication-type)

[Tree] (config>router>isis>if>level hello-authentication-type)

Full Context

configure router isis interface hello-authentication-type

configure router isis interface level hello-authentication-type

Description

This command enables Hello authentication at either the interface or level context. Both the Hello authentication key and the Hello authentication type on a segment must match. The hello authentication-key statement must also be included.

To configure the Hello authentication type at the interface context, use hello-authentication-type in the config>router>isis>interface context.

To configure or override the Hello authentication setting for a given level, configure the hello-authentication-type in the config>router>isis>interface>level context.

The no form of this command disables Hello authentication.

Parameters

password

Specifies simple password (plain text) authentication is required.

message-digest

Specifies MD5 authentication in accordance with RFC 2104 (HMAC: Keyed-Hashing for Message Authentication) is required.

Platforms

All

Context

[Tree] (config>service>vprn>l2tp hello-interval)

[Tree] (config>service>vprn>l2tp>group hello-interval)

[Tree] (config>router>l2tp hello-interval)

[Tree] (config>router>l2tp>group>tunnel hello-interval)

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

[Tree] (config>router>l2tp>group hello-interval)

Full Context

configure service vprn l2tp hello-interval

configure service vprn l2tp group hello-interval

configure router l2tp hello-interval

configure router l2tp group tunnel hello-interval

configure service vprn l2tp group tunnel hello-interval

configure router l2tp group hello-interval

Description

This command configures the time interval between two consecutive tunnel Hello messages. The Hello message is an L2TP control message sent by either peer of a LAC-LNS control connection. This control message is used as a keepalive for the tunnel.

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

Default

hello-interval 300

Parameters

hello-interval

Specifies the time interval, in seconds, between two consecutive tunnel Hello messages.

Default

no hello-interval

Values

10 to 3600

infinite

Specifies that no Hello interval messages are sent.

Platforms

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

Context

[Tree] (config>service>vpls>spoke-sdp>spb>level hello-interval)

[Tree] (config>service>vpls>sap>spb>level hello-interval)

Full Context

configure service vpls spoke-sdp spb level hello-interval

configure service vpls sap spb level hello-interval

Description

This command configures the interval in seconds between Hello messages issued on this interface at this level. This command is valid only for interfaces on control B-VPLS.

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

Default

hello-interval 3 — Hello interval default for the designated inter-system.

hello-interval 9 — Hello interval default for non-designated inter-systems.

Parameters

seconds

The Hello interval in seconds expressed as a decimal integer.

Values

1 to 20000

Platforms

All

Context

[Tree] (config>router>isis>if>level hello-interval)

[Tree] (config>service>vprn>isis>if>level hello-interval)

Full Context

configure router isis interface level hello-interval

configure service vprn isis interface level hello-interval

Description

This command configures the interval between IS-IS Hello PDUs issued on the interface at this level. The hello-interval, along with the hello-multiplier, is used to calculate a hold time, which is communicated to a neighbor in a Hello PDU.

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

Default

3 – for designated intermediate system interfaces

9 – for non-designated intermediate system interfaces and point-to-point interfaces

Parameters

seconds

The Hello interval in seconds expressed as a decimal integer.

Values

1 to 20000

Platforms

All

Context

[Tree] (config>service>vprn>mvpn>pt>inclusive>pim hello-interval)

Full Context

configure service vprn mvpn provider-tunnel inclusive pim hello-interval

Description

This command configures the frequency at which PIM Hello messages are transmitted on this interface.

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

Default

hello-interval 30

Parameters

hello-interval

Specifies the Hello interval in seconds. A 0 (zero) value disables the sending of Hello messages (the PIM neighbor will never timeout the adjacency).

Values

0 to 255 seconds

Platforms

All

Context

[Tree] (config>service>vprn>ospf3>area>if hello-interval)

[Tree] (config>service>vprn>ospf>area>sham-link hello-interval)

[Tree] (config>service>vprn>ospf>area>virtual-link hello-interval)

[Tree] (config>service>vprn>ospf>area>if hello-interval)

[Tree] (config>service>vprn>ospf3>area>virtual-link hello-interval)

Full Context

configure service vprn ospf3 area interface hello-interval

configure service vprn ospf area sham-link hello-interval

configure service vprn ospf area virtual-link hello-interval

configure service vprn ospf area interface hello-interval

configure service vprn ospf3 area virtual-link hello-interval

Description

This command configures the interval between OSPF Hello messages issued on the interface, virtual link, or sham-link.

The Hello interval, in combination with the dead-interval, is used to establish and maintain the adjacency. Use this parameter to edit the frequency that Hello packets are sent.

Reducing the interval, in combination with an appropriate reduction in the associated dead-interval, allows for faster detection of link and/or router failures at the cost of higher processing costs.

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

Default

hello-interval 10 — a 10-second Hello interval

Parameters

seconds

The Hello interval in seconds expressed as a decimal integer.

Values

1 to 65535

Platforms

All

Context

[Tree] (config>service>vprn>pim>if hello-interval)

Full Context

configure service vprn pim interface hello-interval

Description

This command configures the frequency at which PIM Hello messages are transmitted on this interface.

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

Default

hello-interval 30

Parameters

hello-interval

Specifies the Hello interval in seconds. A 0 (zero) value disables the sending of Hello messages (the PIM neighbor will never timeout the adjacency).

Values

0 to 255 seconds

Platforms

All

Context

[Tree] (config>router>rsvp>interface hello-interval)

Full Context

configure router rsvp interface hello-interval

Description

This command configures the time interval between RSVP Hello messages.

RSVP Hello packets are used to detect loss of RSVP connectivity with the neighboring node. Hello packets detect the loss of neighbor far quicker than it would take for the RSVP session to time out based on the refresh interval. After the loss of the of number keep-multiplier consecutive Hello packets, the neighbor is declared to be in a down state.

The no form of this command reverts to the default value of the hello-interval. To disable sending hello messages, set the value to zero.

Default

hello-interval 3000

Parameters

milli-seconds

Specifies the RSVP Hello interval (in ms), in multiples of 1000. A 0 (zero) value disables the sending of RSVP Hello messages.

Values

0 to 60000 ms (in multiples of 1000)

Platforms

All

Context

[Tree] (config>router>pim>interface hello-interval)

Full Context

configure router pim interface hello-interval

Description

This command configures the frequency at which PIM Hello messages are transmitted on this interface.

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

Default

hello-interval 30

Parameters

hello-interval

Specifies the Hello interval in seconds. A 0 (zero) value disables the sending of Hello messages (the PIM neighbor will never timeout the adjacency).

Values

0 to 255 seconds

Platforms

All

Context

[Tree] (config>router>ospf>area>interface hello-interval)

[Tree] (config>router>ospf3>area>virtual-link hello-interval)

[Tree] (config>router>ospf3>area>interface hello-interval)

[Tree] (config>router>ospf>area>virtual-link hello-interval)

Full Context

configure router ospf area interface hello-interval

configure router ospf3 area virtual-link hello-interval

configure router ospf3 area interface hello-interval

configure router ospf area virtual-link hello-interval

Description

This command configures the interval between OSPF Hellos issued on the interface or virtual link.

The Hello interval, in combination with the dead-interval, is used to establish and maintain the adjacency. Use this parameter to edit the frequency that Hello packets are sent.

Reducing the interval, in combination with an appropriate reduction in the associated dead-interval , allows for faster detection of link and/or router failures at the cost of higher processing costs.

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

Default

hello-interval 10

Parameters

seconds

Specifies the Hello interval, in seconds, expressed as a decimal integer.

Values

1 to 65535

Platforms

All

Context

[Tree] (config>system>management-interface>remote-management hello-interval)

Full Context

configure system management-interface remote-management hello-interval

Description

This command configures the time interval between Hello messages sent from the SR OS node to the remote manager.

Default

hello-interval 10

Parameters

number

Specifies the Hello interval, in minutes.

Values

10 to 3600

Platforms

All

Context

[Tree] (config>service>vpls>spoke-sdp>spb>level hello-multiplier)

[Tree] (config>service>vpls>sap>spb>level hello-multiplier)

Full Context

configure service vpls spoke-sdp spb level hello-multiplier

configure service vpls sap spb level hello-multiplier

Description

This command configures the number of missing Hello PDUs from a neighbor SPB declares the adjacency down. This command is valid only for interfaces on control B-VPLS.

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

Default

hello-interval 3 — SPB can miss up to 3 Hello messages before declaring the adjacency down.

Parameters

multiplier

The multiplier for the Hello interval expressed as a decimal integer.

Values

2 to 100

Platforms

All

Context

[Tree] (config>router>isis>if>level>level-number hello-multiplier)

[Tree] (config>service>vprn>isis>if>level hello-multiplier)

Full Context

configure router isis interface level level-number hello-multiplier

configure service vprn isis interface level hello-multiplier

Description

This command configures the number of missing Hello messages from a neighbor before the router declares the adjacency down.

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

Default

hello-multiplier 3

Parameters

multiplier

The multiplier for the Hello interval expressed as a decimal integer.

Values

2 to 100

Platforms

All

Context

[Tree] (config>service>vprn>mvpn>pt>inclusive>pim hello-multiplier)

Full Context

configure service vprn mvpn provider-tunnel inclusive pim hello-multiplier

Description

This command configures the multiplier to determine the hold time for a PIM neighbor on this interface.

The hello-multiplier in conjunction with the hello-interval determines the holdtime for a PIM neighbor.

Parameters

deci-units

Specify the value, specified in multiples of 0.1, for the formula used to calculate the holdtime based on the hello-multiplier:

(hello-interval X hello-multiplier) / 10

This allows the PIMv2 default hello-multiplier of 3.5 and the default timeout of 105 seconds to be supported.

Values

20 to 100

Default

35

Platforms

All

Context

[Tree] (config>service>vprn>pim>if hello-multiplier)

Full Context

configure service vprn pim interface hello-multiplier

Description

This command configures the multiplier to determine the hold time for a PIM neighbor on this interface.

The hello-multiplier in conjunction with the hello-interval determines the holdtime for a PIM neighbor.

Default

hello-multiplier 35

Parameters

deci-units

Specify the value, specified in multiples of 0.1, for the formula used to calculate the holdtime based on the hello-multiplier:

(hello-interval X hello-multiplier) / 10

This allows the PIMv2 default hello-multiplier of 3.5 and the default timeout of 105 seconds to be supported.

Values

20 to 100

Platforms

All

Context

[Tree] (config>router>pim>interface hello-multiplier)

Full Context

configure router pim interface hello-multiplier

Description

This command configures the multiplier to determine the holdtime for a PIM neighbor on this interface.

The hello-multiplier in conjunction with the hello-interval determines the holdtime for a PIM neighbor.

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

Default

hello-multiplier 35

Parameters

deci-units

Specifies the value, in multiples of 0.1, for the formula used to calculate the holdtime based on the hello-multiplier:

(hello-interval X hello-multiplier) / 10

This allows the PIMv2 default hello-multiplier of 3.5 and the default timeout of 105 seconds to be supported.

Values

20 to 100

Default

35

Platforms

All

Context

[Tree] (config>router>isis>if>level hello-multiplier)

Full Context

configure router isis interface level hello-multiplier

Description

This command configures a Hello multiplier. The hello-multiplier, along with the hello-interval, is used to calculate a hold time, which is communicated to a neighbor in a Hello PDU.

The hold time is the time in which the neighbor expects to receive the next Hello PDU. If the neighbor receives a Hello within this time, the hold time is reset. If the neighbor does not receive a Hello within the hold time, it brings the adjacency down.

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

Default

hello-multiplier 3

Parameters

multiplier

Specifies the multiplier for the Hello interval expressed as a decimal integer.

Values

2 to 100

Platforms

All

Context

[Tree] (config>service>vprn>isis hello-padding)

[Tree] (config>service>vprn>isis>if hello-padding)

[Tree] (config>service>vprn>isis>if>level hello-padding)

[Tree] (config>service>vprn>isis>level hello-padding)

Full Context

configure service vprn isis hello-padding

configure service vprn isis interface hello-padding

configure service vprn isis interface level hello-padding

configure service vprn isis level hello-padding

Description

This command enables the IS-IS Hello (IIH) message padding to ensure that IS-IS LSPs can traverse the link. When this option is enabled, IS-IS Hello messages are padded to the maximum LSP MTU value, which can be set with the lsp-mtu-size command. If link MTU is greater than the maximum LSP MTU value, padding to the link MTU is applied.

The no form of this command disables IS-IS Hello message padding at this level. However, the router may still perform Hello padding if it was set at a higher level in the configuration. To ensure that Hello message padding is disabled, set all levels of configuration to no hello-padding.

Default

no hello-padding

Parameters

adaptive

Specifies the adaptive padding option; this option is able to detect MTU asymmetry from one side of the connection but uses more overhead than loose padding.

• point-to-point interface—Hello PDUs are padded until the sender declares an adjacency on the link to be in the state up. If the implementation supports RFC 3373/5303, Three-Way Handshake for IS-IS Point-to-Point Adjacencies, then this is when the three-way state is up. If the implementation uses the "classic” algorithm described in ISO 10589, this is when the adjacency state is up. If the neighbor does not support the adjacency state TLV, then padding continues.

• broadcast interface—Padding starts until at least one adjacency is up on the interface.

loose

Specifies the loose padding option; the loose padding may not be able to detect certain conditions such as asymmetrical MTUs between the routing devices.

• point-to-point interface—the Hello packet is padded from the initial detection of a new neighbor until the adjacency transitions to the INIT state

• broadcast interface—padding starts until at least one adjacency (broadcast only has up/down) is up on the interface

none

Specifies that the Hello message padding is not enabled at this level, even if it is configured at one of the parent levels.

strict

Specifies the strict padding option.

• point-to-point interface—padding is done for all adjacency states, and is continuous. Strict padding has the most overhead but detects MTU issues on both sides of a link

• broadcast interface—padding is done for all adjacency states, and is continuous. Strict padding has the most overhead but detects MTU issues on both sides of a link

Platforms

All

Context

[Tree] (config>router>isis>level hello-padding)

[Tree] (config>router>isis>interface>level hello-padding)

[Tree] (config>router>isis>interface hello-padding)

[Tree] (config>router>isis hello-padding)

Full Context

configure router isis level hello-padding

configure router isis interface level hello-padding

configure router isis interface hello-padding

configure router isis hello-padding

Description

This command enables IS-IS Hello (IIH) message padding to ensure that IS-IS LSPs can traverse the link. When this option is enabled, IS-IS Hello messages are padded to the maximum LSP MTU value, which can be set with the lsp-mtu-size command. If link MTU is greater than the maximum LSP MTU value, padding to the link MTU is applied.

The no form of this command disables IS-IS Hello padding at this level. However, the router may still perform Hello padding if it was set at a higher level in the configuration. To ensure that Hello message padding is disabled, set all levels of configuration to no hello-padding.

Default

no hello-padding

Parameters

none

Specifies that the Hello message padding is not enabled at this level, even if it is configured at one of the parent levels.

adaptive

Specifies the adaptive padding option; this option is able to detect LSP MTU asymmetry from one side of the connection but uses more overhead than loose padding.

1. point-to-point interface—Hello PDUs are padded until the sender declares an adjacency on the link to be in state up. If the implementation supports RFC 3373/5303, "Three-Way Handshake for IS-IS Point-to- Point Adjacencies” then this is when the three-way state is Up. If the implementation use the "classic” algorithm described in ISO 10589, this is when adjacency state is Up. If the neighbor does not support the adjacency state TLV, then padding continues.

2. broadcast interface—Padding starts until at least one adjacency is up on the interface.

loose

Specifies the loose padding option; the loose padding may not be able to detect certain situations such as asymmetrical LSP MTUs between the routing devices.

1. point-to-point interface—The Hello packet is padded from the initial detection of a new neighbor until the adjacency transitions to the INIT state.

2. broadcast interface—Padding starts until there is at least one adjacency (broadcast only has up/down) is up on the interface.

strict

Specifies the strict padding option; this option is the most overhead-intensive but detects LSP MTU issues on both sides of a link.

1. point-to-point interface—Padding is done for all adjacency states, and is continuous.

2. broadcast interface—Padding is done for all adjacency states, and is continuous.

Platforms

All

Context

[Tree] (config>router>ldp>targ-session>ipv4 hello-reduction)

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

[Tree] (config>router>ldp>targ-session>ipv6 hello-reduction)

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

Full Context

configure router ldp targeted-session ipv4 hello-reduction

configure router ldp targeted-session peer hello-reduction

configure router ldp targeted-session ipv6 hello-reduction

configure router ldp targeted-session peer-template hello-reduction

Description

This command enables the suppression of periodic targeted Hello messages between LDP peers once the targeted LDP session is brought up.

The config>router>ldp>targ-session>ipv6>hello-reduction command is not supported on the 7450 ESS.

When this feature is enabled, the target Hello adjacency is brought up by advertising the Hold-Time value the user configured in the " hello timeout” parameter for the targeted session. The LSR node will then start advertising an exponentially increasing Hold-Time value in the Hello message as soon as the targeted LDP session to the peer is up. Each new incremented Hold-Time value is sent in a number of Hello messages equal to the value of the argument factor, which represents the dampening factor, before the next exponential value is advertised. This provides time for the two peers to settle on the new value. When the Hold-Time reaches the maximum value of 0xffff (binary 65535), the two peers will send Hello messages at a frequency of every [(65535-1)/local helloFactor] seconds for the lifetime of the targeted-LDP session (for example, if the local Hello Factor is three (3), then Hello messages will be sent every 21844 seconds.

The LSR node continues to compute the frequency of sending the Hello messages based on the minimum of its local Hold-time value and the one advertised by its peer as in RFC 5036. Thus for the targeted LDP session to suppress the periodic Hello messages, both peers must bring their advertised Hold-Time to the maximum value. If one of the LDP peers does not, the frequency of the Hello messages sent by both peers will continue to be governed by the smaller of the two Hold-Time values.

When the user enables the Hello reduction option on the LSR node while the targeted LDP session to the peer is operationally up, the change will take effect immediately. In other words, the LSR node will start advertising an exponentially increasing Hold-Time value in the Hello message, starting with the current configured Hold-Time value.

When the user disables the Hello reduction option while the targeted LDP session to the peer is operationally up, the change in the Hold-Time from 0xffff (binary 65535) to the user configured value for this peer will take effect immediately. The local LSR will immediately advertise the value of the user configured Hold-Time value and will not wait until the next scheduled time to send a Hello to make sure the peer adjusts its local hold timeout value immediately.

In general, any configuration change to the parameters of the T-LDP Hello adjacency (modifying the Hello adjacency Hello Timeout or factor, enabling/disabling Hello reduction, or modifying Hello reduction factor) will cause the LSR node to trigger immediately an updated Hello message with the updated Hold Time value without waiting for the next scheduled time to send a Hello.

The no form of this command disables the Hello reduction feature.

Default

no hello-reduction

Parameters

factor

Specifies the integer that specifies the Hello reduction dampening factor.

Values

3 to20

Platforms

All

Context

[Tree] (config>service>template>vpls-template>stp hello-time)

[Tree] (config>service>vpls>stp hello-time)

Full Context

configure service template vpls-template stp hello-time

configure service vpls stp hello-time

Description

This command configures the Spanning Tree Protocol (STP) Hello time for the Virtual Private LAN Service (VPLS) STP instance.

The Hello time parameter defines the default timer value that controls the sending interval between BPDU configuration messages by this bridge, on ports where this bridge assumes the designated role.

The active Hello time for the spanning tree is determined by the root bridge (except when the STP is running in RSTP mode, then the Hello time is always taken from the locally configured parameter).

The configured hello-time can also be used to calculate the forward delay. See auto-edge ( config>service>vpls>sap>stp auto-edge, config>service>template>vpls-sap-template>stp auto-edge, config>service>vpls>spoke-sdp>stp auto-edge).

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

Default

hello-time 2

Parameters

hello-time

The Hello time for the STP instance in seconds.

Values

1 to 10

Platforms

All

Context

[Tree] (config>service>sdp>keep-alive hello-time)

Full Context

configure service sdp keep-alive hello-time

Description

This command configures the time period between SDP keepalive messages on the SDP-ID for the SDP connectivity monitoring messages.

The no form of this command reverts the hello-time seconds value to the default setting.

Default

hello-time 10

Parameters

seconds

Specifies the time period in seconds between SDP keepalive messages, expressed as a decimal integer.

Values

1 to 3600

Platforms

All

Context

[Tree] (help)

Full Context

help

Description

This command provides a brief description of the help system. The following information is shown:

Help may be requested at any point by hitting a question mark '?'.
In case of an executable node, the syntax for that node will be displayed with an
explanation of all parameters.
In case of sub-commands, a brief description is provided.
Global Commands:
Help on global commands can be observed by issuing "help globals" at any time.
Editing Commands:
Help on editing commands can be observed by issuing "help edit" at any time.

Parameters

help

Displays a brief description of the help system.

edit

Displays help on editing.

Available editing keystrokes:

Delete current character.....................Ctrl-d
Delete text up to cursor.....................Ctrl-u
Delete text after cursor.....................Ctrl-k
Move to beginning of line....................Ctrl-a
Move to end of line..........................Ctrl-e
Get prior command from history...............Ctrl-p
Get next command from history................Ctrl-n
Move cursor left.............................Ctrl-b
Move cursor right............................Ctrl-f
Move back one word...........................Esc-b
Move forward one word........................Esc-f
Convert rest of word to uppercase............Esc-c
Convert rest of word to lowercase............Esc-l
Delete remainder of word.....................Esc-d
Delete word up to cursor.....................Ctrl-w
Transpose current and previous character.....Ctrl-t
Enter command and return to root prompt......Ctrl-z
Refresh input line...........................Ctrl-l

global

Displays help on global commands.

Available global commands:

back            - Go back a level in the command tree
echo            - Echo the text that is typed in
exec            - Execute a file - use -echo to show the commands and
                  prompts on the screen
exit            - Exit to intermediate mode - use option all to exit to
                  root prompt
help            - Display help
history         - Show command history
info            - Display configuration for the present node
logout          - Log off this system
oam             + OAM Test Suite
ping            - Verify the reachability of a remote host
pwc             - Show the present working context
sleep           - Sleep for specified number of seconds
ssh             - SSH to a host
telnet          - Telnet to a host
traceroute      - Determine the route to a destination address
tree            - Display command tree structure from the context of
                  execution
write           - Write text to another user

special-characters

Displays help on special characters.

Use the following CLI commands to display more information about commands and command syntax:

?

Lists all commands in the current context.

string?

Lists all commands available in the current context that start with the string.

command ?

Displays command’s syntax and associated keywords.

string<Tab> or string<Space>

Completes a partial command name (auto-completion) or lists available commands that match the string.

Platforms

All

Context

[Tree] (config>service>vprn>isis>graceful-restart helper-disable)

Full Context

configure service vprn isis graceful-restart helper-disable

Description

This command disables helper support for IS-IS graceful restart (GR).

When graceful-restart is enabled, the router can be a helper (that is, the router is helping a neighbor to restart), a restarting router, or both. The router only supports the helper mode. It will not act as a restarting router, because the high availability feature set already preserves IS-IS forwarding information such that this functionality is not needed.

The no helper-disable command enables helper support and is the default when graceful restart is enabled.

Default

no helper-disable

Platforms

All

Context

[Tree] (config>service>vprn>ospf>graceful-restart helper-disable)

[Tree] (config>service>vprn>ospf3>graceful-restart helper-disable)

Full Context

configure service vprn ospf graceful-restart helper-disable

configure service vprn ospf3 graceful-restart helper-disable

Description

This command disables helper support for OSPF graceful restart (GR).

When graceful-restart is enabled, the router can be a helper (that is, the router is helping a neighbor to restart), a restarting router, or both. The router only supports helper mode. It will not act as a restarting router, because the high availability feature set already preserves OSPF forwarding information such that this functionality is not needed.

The no helper-disable command enables helper support and is the default when graceful restart is enabled.

Default

no helper-disable

Platforms

All

Context

[Tree] (config>router>isis>graceful-restart helper-disable)

Full Context

configure router isis graceful-restart helper-disable

Description

This command disables helper support for IS-IS graceful restart (GR).

When graceful-restart is enabled, the router can be a helper (that is, the router is helping a neighbor to restart), a restarting router, or both. The router only supports the helper mode. It will not act as a restarting router, because the high availability feature set already preserves IS-IS forwarding information so that this functionality is not needed.

The no form of this command enables helper support and is the default when graceful restart is enabled.

Platforms

All

Context

[Tree] (config>router>ospf3>graceful-restart helper-disable)

[Tree] (config>router>ospf>graceful-restart helper-disable)

Full Context

configure router ospf3 graceful-restart helper-disable

configure router ospf graceful-restart helper-disable

Description

This command disables helper support for OSPF graceful restart (GR).

When graceful-restart is enabled, the router can be a helper (that is, the router is helping a neighbor to restart), a restarting router, or both. The router only supports the helper mode. It will not act as a restarting router because the high availability feature set already preserves OSPF forwarding information so that this functionality is not needed.

The no form of this command enables helper support and is the default when graceful-restart is enabled.

Default

no helper-disable

Platforms

All

Context

[Tree] (config>service>vprn>bgp>graceful-restart>long-lived helper-override-restart-time)

[Tree] (config>service>vprn>bgp>group>graceful-restart>long-lived helper-override-restart-time)

[Tree] (config>service>vprn>bgp>group>neighbor>graceful-restart>long-lived helper-override-restart-time)

Full Context

configure service vprn bgp graceful-restart long-lived helper-override-restart-time

configure service vprn bgp group graceful-restart long-lived helper-override-restart-time

configure service vprn bgp group neighbor graceful-restart long-lived helper-override-restart-time

Description

This command overrides the restart-time advertised by a peer (in its GR capability) with a locally-configured value. This override applies only to AFI/SAFI that were included in the GR capability of the peer. The restart-time is always zero for AFI/SAFI not included in the GR capability. This command is useful if the local router wants to force LLGR phase to begin after a set time for all protected AFI/SAFI.

By default, the restart time for all AFI/SAFI in the GR capability is the value signaled by the peer.

Default

no helper-override-restart-time

Parameters

seconds

The locally-imposed restart time for all AFI/SAFI included in the peer’s GR capability.

Values

0 to 4095

Platforms

All

Context

[Tree] (config>router>bgp>group>neighbor>graceful-restart>long-lived helper-override-restart-time)

[Tree] (config>router>bgp>group>graceful-restart>long-lived helper-override-restart-time)

[Tree] (config>router>bgp>graceful-restart>long-lived helper-override-restart-time)

Full Context

configure router bgp group neighbor graceful-restart long-lived helper-override-restart-time

configure router bgp group graceful-restart long-lived helper-override-restart-time

configure router bgp graceful-restart long-lived helper-override-restart-time

Description

This command overrides the restart-time advertised by a peer (in its GR capability) with a locally-configured value. This override applies only to AFI/SAFI that were included in the GR capability of the peer. The restart-time is always zero for AFI/SAFI not included in the GR capability. This command is useful if the local router wants to force LLGR phase to begin after a set time for all protected AFI/SAFI.

By default, the restart time for all AFI/SAFI in the GR capability is the value signaled by the peer.

Default

no helper-override-restart-time

Parameters

seconds

The locally-imposed restart time for all AFI/SAFI included in the peer’s GR capability.

Values

0 to 4095

Platforms

All

Context

[Tree] (config>service>vprn>bgp>graceful-restart>long-lived helper-override-stale-time)

[Tree] (config>service>vprn>bgp>graceful-restart>long-lived>family helper-override-stale-time)

[Tree] (config>service>vprn>bgp>group>neighbor>graceful-restart>long-lived>family helper-override-stale-time)

[Tree] (config>service>vprn>bgp>group>graceful-restart>long-lived helper-override-stale-time)

[Tree] (config>service>vprn>bgp>group>graceful-restart>long-lived>family helper-override-stale-time)

[Tree] (config>service>vprn>bgp>group>neighbor>graceful-restart>long-lived helper-override-stale-time)

Full Context

configure service vprn bgp graceful-restart long-lived helper-override-stale-time

configure service vprn bgp graceful-restart long-lived family helper-override-stale-time

configure service vprn bgp group neighbor graceful-restart long-lived family helper-override-stale-time

configure service vprn bgp group graceful-restart long-lived helper-override-stale-time

configure service vprn bgp group graceful-restart long-lived family helper-override-stale-time

configure service vprn bgp group neighbor graceful-restart long-lived helper-override-stale-time

Description

This command overrides the LLGR stale-time advertised by a peer (in its LLGR capability) with a locally-configured value. When configured in the long-lived configuration context, helper-override-stale-time applies to all AFI/SAFI in the advertised LLGR capability except for any AFI/SAFI with a family-specific override. A family-specific override is configured with the helper-override-stale-time command in a family context.

By default, the LLGR stale-time for an AFI/SAFI is the value signaled by the peer in the corresponding AFI/SAFI part of the LLGR capability.

Default

no helper-override-stale-time

Parameters

seconds

Specifies the locally imposed LLGR stale time in seconds.

Values

0 to 16777215

Platforms

All

Context

[Tree] (config>router>bgp>group>graceful-restart>long-lived helper-override-stale-time)

[Tree] (config>router>bgp>group>neighbor>graceful-restart>long-lived helper-override-stale-time)

[Tree] (config>router>bgp>group>graceful-restart>long-lived>family helper-override-stale-time)

[Tree] (config>router>bgp>graceful-restart>long-lived>family helper-override-stale-time)

[Tree] (config>router>bgp>graceful-restart>long-lived helper-override-stale-time)

[Tree] (config>router>bgp>group>neighbor>graceful-restart>long-lived>family helper-override-stale-time)

Full Context

configure router bgp group graceful-restart long-lived helper-override-stale-time

configure router bgp group neighbor graceful-restart long-lived helper-override-stale-time

configure router bgp group graceful-restart long-lived family helper-override-stale-time

configure router bgp graceful-restart long-lived family helper-override-stale-time

configure router bgp graceful-restart long-lived helper-override-stale-time

configure router bgp group neighbor graceful-restart long-lived family helper-override-stale-time

Description

This command overrides the LLGR stale-time advertised by a peer (in its LLGR capability) with a locally-configured value. When configured in the long-lived configuration context, helper-override-stale-time applies to all AFI/SAFI in the advertised LLGR capability except for any AFI/SAFI with a family-specific override. A family-specific override is configured with the helper-override-stale-time command in a family context.

By default, the LLGR stale-time for an AFI/SAFI is the value signaled by the peer in the corresponding AFI/SAFI part of the LLGR capability.

Default

no helper-override-stale-time

Parameters

seconds

Specifies the locally imposed LLGR stale time in seconds.

Values

0 to 16777215

Platforms

All

Context

[Tree] (config>card>fp hi-bw-mcast-src)

Full Context

configure card fp hi-bw-mcast-src

Description

This command designates the forwarding plane as a high-bandwidth IP multicast source, expecting the ingress traffic to include high-bandwidth IP multicast traffic. When configured, the system attempts to allocate a dedicated multicast switch fabric plane (MSFP) to the forwarding plane. If a group is specified, all FPs in the group will share the same MSFP. If the alarm parameter is specified and the system cannot allocate a dedicated MSFP to the new group or FP, the FPs will be brought online and generate an event (SYSTEM: 2052 - tmnxChassisHiBwMulticastAlarm). Similarly, if during normal operation there is a failure or removal of resources, an event will be generated if the system cannot maintain separation of MSFPs for the MDAs.

The no form of this command removes the high-bandwidth IP multicast source designation from the forwarding plane.

Default

no hi-bw-mcast-src

Parameters

alarm

Enables event generation if the MDA is required to share an MSFP with another MDA that is in a different group. MDAs within the same group sharing an MSFP will not cause this alarm.

group-id

Specifies the logical MSFP group for the MDA. MDAs configured with the same group-id will be placed on the same MSFP.

Values

0 to 32 (A value of 0 removes the MDA from the group).

Default

By default, "none” is used, and the system will attempt to assign a unique MSFP to the MDA.

default-paths-only

When this parameter is specified the system will only attempt to allocate the two default paths (one high priority and one low priority) to dedicated MSFPs.

Platforms

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

Context

[Tree] (config>qos>sap-egress>queue>drop-tail high)

Full Context

configure qos sap-egress queue drop-tail high

Description

Commands in this context configure the queue high drop tail parameters. The high drop tail defines the queue depth beyond which in-profile packets will not be accepted into the queue and will be discarded.

Platforms

All

Context

[Tree] (cfg>qos>qgrps>egr>qgrp>queue>drop-tail high)

Full Context

configure qos queue-group-templates egress queue-group queue drop-tail high

Description

Commands in this context configure the queue high drop-tail parameters. The high drop tail defines the queue depth beyond which in-profile packets will not be accepted into the queue and will be discarded.

Platforms

All

Context

[Tree] (config>python>py-pol>cache>minimum-lifetimes high-availability)

Full Context

configure python python-policy cache minimum-lifetimes high-availability

Description

This command specifies the minimum lifetime of an entry that it could be synced across CPM.

The no form of this command reverts to the default.

Parameters

seconds

Specifies the minimal lifetime in seconds.

Values

1 to 600

Platforms

All

Context

[Tree] (config>subscr-mgmt>acct-plcy>cr>ref-queue>i-counters high-octets-discarded-count)

[Tree] (config>subscr-mgmt>acct-plcy>cr>queue>i-counters high-octets-discarded-count)

Full Context

configure subscriber-mgmt radius-accounting-policy custom-record ref-queue i-counters high-octets-discarded-count

configure subscriber-mgmt radius-accounting-policy custom-record queue i-counters high-octets-discarded-count

Description

This command includes the high octets discarded count.

For queues with stat-mode v4-v6, this command includes the IPv4 octets discarded count instead.

The no form of this command excludes the high octets discarded count.

Platforms

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

Context

[Tree] (config>log>acct-policy>cr>queue>i-counters high-octets-discarded-count)

[Tree] (config>log>acct-policy>cr>ref-queue>i-counters high-octets-discarded-count)

Full Context

configure log accounting-policy custom-record queue i-counters high-octets-discarded-count

configure log accounting-policy custom-record ref-queue i-counters high-octets-discarded-count

Description

This command includes the high octets discarded count.

The no form of this command excludes the high octets discarded count.

Default

no high-octets-discarded-count

Platforms

All

Context

[Tree] (config>subscr-mgmt>acct-plcy>cr>queue>i-counters high-octets-offered-count)

[Tree] (config>subscr-mgmt>acct-plcy>cr>ref-queue>i-counters high-octets-offered-count)

Full Context

configure subscriber-mgmt radius-accounting-policy custom-record queue i-counters high-octets-offered-count

configure subscriber-mgmt radius-accounting-policy custom-record ref-queue i-counters high-octets-offered-count

Description

This command includes the high octets offered count.

The no form of this command excludes the high octets offered count.

Platforms

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

Context

[Tree] (config>log>acct-policy>cr>ref-queue>i-counters high-octets-offered-count)

[Tree] (config>log>acct-policy>cr>queue>i-counters high-octets-offered-count)

Full Context

configure log accounting-policy custom-record ref-queue i-counters high-octets-offered-count

configure log accounting-policy custom-record queue i-counters high-octets-offered-count

Description

This command includes the high octets offered count.

The no form of this command excludes the high octets offered count.

Default

no high-octets-offered-count

Platforms

All

Context

[Tree] (config>subscr-mgmt>acct-plcy>cr>ref-queue>i-count high-packets-discarded-count)

[Tree] (config>subscr-mgmt>acct-plcy>cr>queue>i-count high-packets-discarded-count)

Full Context

configure subscriber-mgmt radius-accounting-policy custom-record ref-queue i-counters high-packets-discarded-count

configure subscriber-mgmt radius-accounting-policy custom-record queue i-counters high-packets-discarded-count

Description

This command includes the high packets discarded count.

For queues with stat-mode v4-v6, this command includes the IPv4 packets discarded count instead.

The no form of this command excludes the high packets discarded count.

Platforms

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

Context

[Tree] (config>log>acct-policy>cr>ref-queue>i-counters high-packets-discarded-count)

[Tree] (config>log>acct-policy>cr>queue>i-counters high-packets-discarded-count)

Full Context

configure log accounting-policy custom-record ref-queue i-counters high-packets-discarded-count

configure log accounting-policy custom-record queue i-counters high-packets-discarded-count

Description

This command includes the high packets discarded count.

The no form of this command excludes the high packets discarded count.

Default

no high-packets-discarded-count

Platforms

All

Context

[Tree] (config>subscr-mgmt>acct-plcy>cr>ref-queue>i-counters high-packets-offered-count)

[Tree] (config>subscr-mgmt>acct-plcy>cr>queue>i-counters high-packets-offered-count)

Full Context

configure subscriber-mgmt radius-accounting-policy custom-record ref-queue i-counters high-packets-offered-count

configure subscriber-mgmt radius-accounting-policy custom-record queue i-counters high-packets-offered-count

Description

This command includes the high packets offered count.

The no form of this command excludes the high packets offered count.

Platforms

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

Context

[Tree] (config>log>acct-policy>cr>queue>i-counters high-packets-offered-count)

[Tree] (config>log>acct-policy>cr>ref-queue>i-counters high-packets-offered-count)

Full Context

configure log accounting-policy custom-record queue i-counters high-packets-offered-count

configure log accounting-policy custom-record ref-queue i-counters high-packets-offered-count

Description

This command includes the high packets offered count.

The no form of this command excludes the high packets offered count.

Default

no high-packets-offered-count

Platforms

All

Context

[Tree] (config>subscr-mgmt>sla-prof>ingress>qos>queue high-prio-only)

[Tree] (config>subscr-mgmt>sla-prof>egress>qos>queue high-prio-only)

Full Context

configure subscriber-mgmt sla-profile ingress qos queue high-prio-only

configure subscriber-mgmt sla-profile egress qos queue high-prio-only

Description

This command configures the value of the percentage of buffer space for the queue, used exclusively by high priority packets. The specified value overrides the default value for the context.

The priority of a packet can only be set in the SAP ingress QoS policy and is only applicable on the ingress queues for a SAP. The high-prio-only parameter is used to override the default value derived from the network-queue command.

The defined high-prio-only value cannot be greater than the MBS size of the queue. Attempting to change the MBS to a value smaller than the high priority reserve will generate an error and fail execution. Attempting to set the high-prio-only value larger than the current MBS size will also result in an error and fail execution.

The no form of this command returns high-prio-only to the size as configured in the QoS policy.

Parameters

percent

The percent parameter is the percentage reserved for high priority traffic on the queue. If a value of 10KBytes is desired, enter the value 10. A value of 0 specifies that none of the MBS of the queue is reserved for high priority traffic. This does not affect RED slope operation for packets attempting to be queued.

Values

0 to 100, default

Platforms

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

Context

[Tree] (config>qos>sap-egress>policer high-prio-only)

[Tree] (config>qos>sap-ingress>policer high-prio-only)

Full Context

configure qos sap-egress policer high-prio-only

configure qos sap-ingress policer high-prio-only

Description

This command is used to configure the percentage of the policer’s PIR leaky bucket's MBS (maximum burst size) that is reserved for high-priority traffic. While the mbs value defines the policer’s high-priority violate threshold, the percentage value defined is applied to the mbs value to derive the bucket’s low-priority violate threshold. See the mbs command details for information about which types of traffic are associated with each violate threshold.

Parameters

percent-of-mbs

The percent-of-mbs parameter is required when specifying high-prio-only and is expressed as a percentage.

Values

0 to 100

Default

10

Platforms

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

Context

[Tree] (config>qos>qgrps>ing>qgrp>policer high-prio-only)

[Tree] (config>qos>qgrps>egr>qgrp>policer high-prio-only)

Full Context

configure qos queue-group-templates ingress queue-group policer high-prio-only

configure qos queue-group-templates egress queue-group policer high-prio-only

Description

This command is used to configure the percentage of the policer’s PIR leaky bucket's MBS (maximum burst size) that is reserved for high-priority traffic. While the mbs value defines the policer’s high-priority violate threshold, the percentage value defined is applied to the mbs value to derive the bucket’s low-priority violate threshold. See the mbs command details for information on which types of traffic is associated with each violate threshold.

Parameters

percent-of-mbs

The percent-of-mbs parameter is required when specifying high-prio-only and is expressed as a percentage.

Values

0 to 100

Default

10

Platforms

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

Context

[Tree] (config>qos>adv-config-policy>child-control>offered-measurement high-rate-hold-time)

Full Context

configure qos adv-config-policy child-control offered-measurement high-rate-hold-time

Description

This command sets a time period that the current offered rate should be maintained for a child policer or queue when it is seen that the offered rate is decreasing. The offered measurement that triggers the hold time is used when the hold timer expires, unless a higher offered rate is seen in the interim. When a higher rate is observed, the hold timer is canceled and the higher offered rate is used immediately.

A possible reason to define a hold timer for an offered rate is to allow a child queue is to dampen the effects of a child with a fluctuating rate on the virtual scheduler. This works similar to the max-decrement in that the child holds on to bandwidth from the virtual scheduler in case it may be needed in the near future.

This parameter has no effect on an increase to the child’s offered rate. If the rate increase is above the change sensitivity, the new offered rate is immediately used.

When this command is not specified or removed, the virtual scheduler immediately reacts to measured decreases in offered load.

The no form of this command is used to remove any currently configured hold time for all child policers and queues associated with the policy. When the hold time is removed, any current hold timers for child policers are automatically canceled.

Parameters

seconds

The hold time configured must be specified in seconds. A value of 0 is equivalent to no high-rate-hold-time.

Default

0

Values

0 to 60

active-min-only

When this optional parameter is specified, the high-rate-hold-time command will accept the optional active-min-only parameter. Attempting to remove the active-min-only parameter from the add command, or removing the add command itself, will fail while active-min-only is enabled on the high-rate-hold-time command. When specified, the respective rate or percentage is treated as the minimum offered rate for a queue, only when the queue has an actual non-zero offered rate. This is intended to limit the artificial increase in offered rate to queues that are currently active. When a queue’s measured offered rate drops to zero, the system stops enforcing the minimum value.

Platforms

All

Context

[Tree] (config>qos>slope-policy high-slope)

Full Context

configure qos slope-policy high-slope

Description

The high-slope context contains the commands and parameters for defining the high Random Early Detection (RED) slope graph. Each buffer pool supports a high RED slope for managing access to the shared portion of the buffer pool for in-profile packets.

The high-slope parameters can be changed at any time and the affected buffer pool high RED slopes will be adjusted appropriately.

The no form of this command restores the high slope configuration commands to the default values. If the commands within high-slope are set to the default parameters, the high-slope node will not appear in save config and show config output unless the detail parameter is present.

Platforms

All

Context

[Tree] (config>app-assure>group>dns-ip-cache>ip-cache high-wmark)

Full Context

configure application-assurance group dns-ip-cache ip-cache high-wmark

Description

This command configures the high watermark value for the DNS IP cache. When the number of IP addresses stored in the cache crosses above this threshold, the system will generate a trap.

Default

high-wmark 90

Parameters

percent

Specifies the high watermark value, in percent.

Values

0 to 100

Default

90

Platforms

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

Context

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>gtp-in-gtp high-wmark)

[Tree] (config>app-assure>group>statistics>tca>sess-fltr>default-action high-wmark)

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>validate-sequence-number high-wmark)

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>missing>mandatory-ie high-wmark)

[Tree] (config>app-assure>group>statistics>tca>gtp-sanity-drop high-wmark)

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

[Tree] (config>app-assure>group>statistics>tca>fragment-drop-all high-wmark)

[Tree] (config>app-assure>group>statistics>tca>overload-drop high-wmark)

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>msg-gtpv2>entry high-wmark)

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>imsi-apn>default-action high-wmark)

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>max-payload-length high-wmark)

[Tree] (config>app-assure>group>statistics>tca>sctp-fltr>ppid>ppid-range high-wmark)

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>validate-src-ip-addr high-wmark)

[Tree] (config>app-assure>group>statistics>tca>fragment-drop-out-of-order high-wmark)

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>validate-gtp-tunnels high-wmark)

[Tree] (config>app-assure>group>statistics>tca>sctp-fltr>ppid>default-action high-wmark)

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>msg-gtpv2>default-action high-wmark)

[Tree] (config>app-assure>group>statistics>tca>policer high-wmark)

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>msg>default-action high-wmark)

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

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>msg>entry high-wmark)

[Tree] (config>app-assure>group>statistics>tca>sctp-fltr>ppid>entry high-wmark)

[Tree] (config>app-assure>group>statistics>tca>sctp-fltr>packet-sanity high-wmark)

[Tree] (config>app-assure>group>statistics>tca>error-drop high-wmark)

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>imsi-apn>entry high-wmark)

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>msg>header-sanity high-wmark)

[Tree] (config>app-assure>group>statistics>tca>sess-fltr>entry high-wmark)

[Tree] (config>app-assure>group>statistics>tca>gtp-fltr>default-gtp-tunnel-endpoint-limit high-wmark)

Full Context

configure application-assurance group statistics threshold-crossing-alert gtp-filter gtp-in-gtp high-wmark

configure application-assurance group statistics threshold-crossing-alert session-filter default-action high-wmark

configure application-assurance group statistics threshold-crossing-alert gtp-filter validate-sequence-number high-wmark

configure application-assurance group statistics threshold-crossing-alert gtp-filter missing-mandatory-ie high-wmark

configure application-assurance group statistics threshold-crossing-alert gtp-sanity-drop high-wmark

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

configure application-assurance group statistics threshold-crossing-alert fragment-drop-all high-wmark

configure application-assurance group statistics threshold-crossing-alert overload-drop high-wmark

configure application-assurance group statistics threshold-crossing-alert gtp-filter message-type-gtpv2 entry high-wmark

configure application-assurance group statistics threshold-crossing-alert gtp-filter imsi-apn default-action high-wmark

configure application-assurance group statistics threshold-crossing-alert gtp-filter max-payload-length high-wmark

configure application-assurance group statistics threshold-crossing-alert sctp-filter ppid-range high-wmark

configure application-assurance group statistics threshold-crossing-alert gtp-filter validate-src-ip-addr high-wmark

configure application-assurance group statistics threshold-crossing-alert fragment-drop-out-of-order high-wmark

configure application-assurance group statistics threshold-crossing-alert gtp-filter validate-gtp-tunnels high-wmark

configure application-assurance group statistics threshold-crossing-alert sctp-filter ppid default-action high-wmark

configure application-assurance group statistics threshold-crossing-alert gtp-filter message-type-gtpv2 default-action high-wmark

configure application-assurance group statistics threshold-crossing-alert policer high-wmark

configure application-assurance group statistics threshold-crossing-alert gtp-filter message-type default-action high-wmark

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

configure application-assurance group statistics threshold-crossing-alert gtp-filter message-type entry high-wmark

configure application-assurance group statistics threshold-crossing-alert sctp-filter ppid entry high-wmark

configure application-assurance group statistics threshold-crossing-alert sctp-filter packet-sanity high-wmark

configure application-assurance group statistics threshold-crossing-alert error-drop high-wmark

configure application-assurance group statistics threshold-crossing-alert gtp-filter imsi-apn entry high-wmark

configure application-assurance group statistics threshold-crossing-alert gtp-filter message-type header-sanity high-wmark

configure application-assurance group statistics threshold-crossing-alert session-filter entry high-wmark

configure application-assurance group statistics threshold-crossing-alert gtp-filter default-gtp-tunnel-endpoint-limit high-wmark

Description

This command configures the high watermark and low watermark thresholds for the specified TCA.

Default

high-wmark 4294967295 low-wmark 0

Parameters

high-watermark

Specifies the TCA high watermark.

Values

1 to 4294967295

Default

4294967295

low-watermark

Specifies the TCA low watermark.

Values

0 to 4294967294

Default

0

Platforms

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

Context

[Tree] (config>qos>sap-egress>queue>drop-tail highplus)

Full Context

configure qos sap-egress queue drop-tail highplus

Description

Commands in this context configure the queue highplus drop tail parameters. The highplus drop tail defines the queue depth beyond which inplus-profile packets will not be accepted into the queue and will be discarded.

Platforms

All

Context

[Tree] (cfg>qos>qgrps>egr>qgrp>queue>drop-tail highplus)

Full Context

configure qos queue-group-templates egress queue-group queue drop-tail highplus

Description

Commands in this context configure the queue highplus drop-tail parameters. The highplus drop tail defines the queue depth beyond which inplus-profile packets will not be accepted into the queue and will be discarded.

Platforms

All

Context

[Tree] (config>qos>slope-policy highplus-slope)

Full Context

configure qos slope-policy highplus-slope

Description

The highplus-slope context contains the commands and parameters for defining the highplus Random Early Detection (RED) slope graph. Each buffer pool supports a highplus RED slope for managing access to the shared portion of the buffer pool for inplus-profile packets.

The highplus-slope parameters can be changed at any time and the affected buffer pool highplus RED slopes will be adjusted appropriately.

The no form of this command restores the highplus slope configuration commands to the default values. If the commands within highplus-slope are set to the default parameters, the highplus-slope node will not appear in save config and show config output unless the detail parameter is present.

Platforms

All

Context

[Tree] (history)

Full Context

history

Description

This command lists the last 30 commands entered in this session.

Re-execute a command in the history with the !n command, where n is the line number associated with the command in the history output.

Example:

A:ALA-1# history
  68 info
  69 exit
  70 info
  71 filter
  72 exit all
  73 configure
  74 router
  75 info
  76 interface "test"
  77 exit
  78 reduced-prompt
  79 info
  80 interface "test"
  81 icmp unreachables exit all
  82 exit all
  83 reduced-prompt
  84 configure router
  85 interface
  86 info
  87 interface "test"
  88 info
  89 reduced-prompt
  90 exit all
  91 configure
  92 card 1
  93 card-type
  94 exit
  95 router
  96 exit
  97 history
A:ALA-1# !91
A:ALA-1# configure
A:ALA-1>config#

Platforms

All

Context

[Tree] (config>system>security>password history-size)

Full Context

configure system security password history-size

Description

Configure how many previous passwords a new password is matched against.

Default

history-size 0

Parameters

size

Specifies how many previous passwords a new password is matched against.

Values

0 to 20

Platforms

All

Context

[Tree] (config>oam-pm>session>ip>twamp-light>loss-events hli-event)

[Tree] (config>oam-pm>session>ethernet>lmm>loss-events hli-event)

[Tree] (config>oam-pm>session>ethernet>slm>loss-events hli-event)

Full Context

configure oam-pm session ip twamp-light loss-events hli-event

configure oam-pm session ethernet lmm loss-events hli-event

configure oam-pm session ethernet slm loss-events hli-event

Description

This command sets the high loss interval (HLI) threshold to be monitored and the associated thresholds using the counter of the specified direction. The aggregate is a function of summing forward and backward. This value is only used as a threshold mechanism and is not part of the stored statistics. If the optional clear clear-threshold parameter is not specified, the traffic crossing alarm is stateless. Stateless means the state is not carried forward to other measurement intervals. Each measurement interval is analyzed independently and regardless of any previous window. Each unique event can only be raised once within measurement interval. If the optional clear clear-threshold parameter is specified, the traffic crossing alarm uses stateful behavior. Stateful means each unique previous event state is carried forward to following measurement intervals. If a threshold crossing event is raised another is raised until a measurement interval completes and the clear threshold has not been exceeded. A clear event is raised under that condition.

The no form of this command removes the event threshold for frame loss ratio. The direction must be included with the no command.

Default

no hli-event forward

no hli-event backward

no hli-event aggregate

Parameters

forward

Specifies the threshold is applied to the forward direction count.

backward

Specifies the threshold is applied to the backward direction count.

aggregate

Specifies the threshold is applied to the aggregate count (sum of forward and backward).

raise-threshold

Specifies the rising threshold that determines when the event is to be generated, when the percentage of loss value is reached.

Values

1 to 864000

clear-threshold

Specifies an optional value used for stateful behavior that allows the operator to configure a percentage of loss value lower than the rising percentage to indicate when the clear event should be generated.

Values

0 to 863999

A value of zero means that the HLI counter must be 0.

Platforms

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

• configure oam-pm session ip twamp-light loss-events hli-event

All

• configure oam-pm session ethernet lmm loss-events hli-event
• configure oam-pm session ethernet slm loss-events hli-event

Context

[Tree] (config>oam-pm>session>ethernet>slm hli-force-count)

[Tree] (config>oam-pm>session>ethernet>lmm>availability hli-force-count)

Full Context

configure oam-pm session ethernet slm hli-force-count

configure oam-pm session ethernet lmm availability hli-force-count

Description

This command allows High Loss Interval (HLI) and Consecutive High Loss Interval (CHLI) counters to increment regardless of availability. Without this command, HLI and CHLI counters can only increment during times of availability, which includes undetermined availability. During times of complete packet loss, the forward direction HLI is marked as high loss. The backward direction is not marked as high loss during times of complete packet loss.

The no form of this command configures HLI and CHLI counters to increment during times of availability only.

Platforms

All

Context

[Tree] (config>oam-pm>session>ip>twamp-light>loss hli-force-count)

Full Context

configure oam-pm session ip twamp-light loss hli-force-count

Description

This command allows High Loss Interval (HLI) and Consecutive High Loss Interval (CHLI) counters to increment regardless of availability. Without this command, HLI and CHLI counters can only increment during times of availability, which includes undetermined availability. During times of complete packet loss, the forward direction HLI is marked as high loss. The backward direction is not marked as high loss during times of complete packet loss.

The no form of this command configures HLI and CHLI counters to increment during times of availability only.

Platforms

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

Context

[Tree] (config>vrrp>policy>priority-event>route-unknown hold-clear)

[Tree] (config>vrrp>policy>priority-event>host-unreachable hold-clear)

[Tree] (config>vrrp>policy>priority-event>lag-port-down hold-clear)

[Tree] (config>vrrp>policy>priority-event>mc-ipsec-non-forwarding hold-clear)

[Tree] (config>vrrp>policy>priority-event>port-down hold-clear)

Full Context

configure vrrp policy priority-event route-unknown hold-clear

configure vrrp policy priority-event host-unreachable hold-clear

configure vrrp policy priority-event lag-port-down hold-clear

configure vrrp policy priority-event mc-ipsec-non-forwarding hold-clear

configure vrrp policy priority-event port-down hold-clear

Description

This command configures the hold clear time for the event. The seconds parameter specifies the hold-clear time, the amount of time in seconds by which the effect of a cleared event on the associated virtual router instance is delayed.

The hold-clear time is used to prevent black hole conditions when a virtual router instance advertises itself as a master before other conditions associated with the cleared event have had a chance to enter a forwarding state.

Default

no hold-clear

Parameters

seconds

Specifies the amount of time in seconds by which the effect of a cleared event on the associated virtual router instance is delayed.

Values

0 to 86400

Platforms

All

• configure vrrp policy priority-event lag-port-down hold-clear
• configure vrrp policy priority-event route-unknown hold-clear
• configure vrrp policy priority-event host-unreachable hold-clear
• configure vrrp policy priority-event port-down hold-clear

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

• configure vrrp policy priority-event mc-ipsec-non-forwarding hold-clear

Context

[Tree] (config>service>template>vpls-template>stp hold-count)

[Tree] (config>service>vpls>stp hold-count)

Full Context

configure service template vpls-template stp hold-count

configure service vpls stp hold-count

Description

This command configures the peak number of BPDUs that can be transmitted in a period of one second.

The no form of this command returns the hold count to the default value

Default

hold-count 6

Parameters

BPDU tx hold count

The hold count for the STP instance in seconds

Values

1 to 10

Platforms

All

Context

[Tree] (config>subscr-mgmt>auth-plcy>radius-auth-server hold-down-time)

Full Context

configure subscriber-mgmt authentication-policy radius-authentication-server hold-down-time

Description

This command determines the interval during which no new communication attempts is made to a RADIUS server that is marked down to prevent immediately overloading the server when it is starting up. The only exception is when all servers in the authentication policy are marked down; in that case they will all be used again to prevent failures on new client connections.

The no form of this command reverts to the default.

Default

hold-down-time 30

Parameters

seconds

Specifies the hold time before re-using a RADIUS server that was down.

Values

30 to 900

Platforms

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

Context

[Tree] (config>aaa>radius-srv-plcy>servers hold-down-time)

Full Context

configure aaa radius-server-policy servers hold-down-time

Description

This command determines the interval during which no new communication attempts are made to a RADIUS server that is marked down to prevent immediately overloading the server when it is starting up. The only exception is when all servers in the authentication policy are marked down; in that case, they will all be used again to prevent failures on new client connections.

The no form of this command reverts to the default.

Default

hold-down-time sec 30

Parameters

days

Specifies the hold time in days before re-using a RADIUS server that was down.

Values

1 to 1

hours

Specifies the hold time in hours before re-using a RADIUS server that was down.

Values

1 to 23

minutes

Specifies the hold time in minutes before re-using a RADIUS server that was down.

Values

1 to 59

seconds

Specifies the hold time in seconds before re-using a RADIUS server that was down.

Values

1 to 59

Platforms

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

Context

[Tree] (config>service>sdp>keep-alive hold-down-time)

Full Context

configure service sdp keep-alive hold-down-time

Description

This command configures the minimum time period the SDP will remain in the operationally down state in response to SDP keepalive monitoring.

This parameter can be used to prevent the SDP operational state from "flapping” by rapidly transitioning between the operationally up and operationally down states based on keepalive messages.

When an SDP keepalive response is received that indicates an error condition or the max-drop-count keepalive messages receive no reply, the sdp-id will immediately be brought operationally down. If a keepalive response is received that indicates the error has cleared, the sdp-id will be eligible to be put into the operationally up state only after the hold-down-time interval has expired.

The no form of this command reverts the hold-down-time seconds value to the default setting.

Default

hold-down-time 10

Parameters

seconds

Specifies time, in seconds, expressed as a decimal integer. The SDP ID will remain in the operationally down state before it is eligible to enter the operationally up state. A value of 0 indicates that no hold-down-time will be enforced for SDP ID.

Values

0 to 3600

Platforms

All

Context

[Tree] (config>router>segment-routing>maintenance-policy hold-down-timer)

Full Context

configure router segment-routing maintenance-policy hold-down-timer

Description

This command configures the hold down timer for SR policy candidate paths.

This command is intended to prevent bouncing of the SR policy path state if one or more S-BFD sessions associated with segment lists flap and therefore cause the threshold to be repeatedly crossed in a short period of time. It is started when the number of up S-BFD sessions drops below the threshold. The SR policy path is not considered to be up again until the hold down timer has expired and the number of up S-BFD sessions equals or exceeds the threshold and the internal hold timer is not running.

The no form of this command reverts to the default.

Default

hold-down-timer 0

Parameters

hold-down-timer

Specifies the hold-down timer, in deciseconds, in 10ms steps.

Values

0 to 5000

Platforms

All

Context

[Tree] (config>service>vprn>gsmp hold-multiplier)

[Tree] (config>service>vpls>gsmp hold-multiplier)

Full Context

configure service vprn gsmp hold-multiplier

configure service vpls gsmp hold-multiplier

Description

This command configures the hold-multiplier for the GSMP connections in this group.

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

Parameters

multiplier

Specifies the GSMP hold multiplier value.

Values

1 to 100

Platforms

All

Context

[Tree] (config>service>vpls>gsmp>group hold-multiplier)

Full Context

configure service vpls gsmp group hold-multiplier

Description

This command configures the hold-multiplier for the GSMP connections in this group.

Parameters

multiplier

Specifies the GSMP hold multiplier value

Values

1 to 100

Platforms

All

Context

[Tree] (config>service>vprn>gsmp>group hold-multiplier)

Full Context

configure service vprn gsmp group hold-multiplier

Description

This command configures the hold-multiplier for the GSMP connections in this group.

The no form of this command removes the multiplier value from the configuration

Default

no hold-multiplier

Parameters

multiplier

Specifies the GSMP hold multiplier value.

Values

1 to 100

Platforms

All

Context

[Tree] (config>redundancy>multi-chassis>peer>mc-lag hold-on-neighbor-failure)

Full Context

configure redundancy multi-chassis peer mc-lag hold-on-neighbor-failure

Description

This command specifies the interval that the standby node will wait for packets from the active node before assuming a redundant-neighbor node failure. This delay in switch-over operation is required to accommodate different factors influencing node failure detection rate, such as IGP convergence, or HA switch-over times and to prevent the standby node to act prematurely.

The no form of this command reverts to the default.

Default

hold-on-neighbor-failure 3

Parameters

multiplier

Specifies the time interval that the standby node waits for packets from the active node before assuming a redundant-neighbor node failure.

Values

2 to 25

Platforms

All

Context

[Tree] (config>redundancy>multi-chassis>peer>mc-ep hold-on-neighbor-failure)

Full Context

configure redundancy multi-chassis peer mc-endpoint hold-on-neighbor-failure

Description

This command specifies the number of keep-alive intervals that the local node will wait for packets from the MC-EP peer before assuming failure. After this time interval passed the all the mc-endpoints configured under services will revert to single chassis behavior, activating the best local pseudowire.

The no form of this command sets the multiplier to default value

Default

no hold-on-neighbor-failure

Parameters

multiplier

Specifies the hold time applied on neighbor failure.

Values

2 to 25

Platforms

All

Context

[Tree] (config>redundancy>multi-chassis>peer>mc-ipsec hold-on-neighbor-failure)

Full Context

configure redundancy multi-chassis peer mc-ipsec hold-on-neighbor-failure

Description

This command specifies the number of keep-alive failures before the peer is considered to be down.

The no form of this command reverts to the default.

Default

hold-on-neighbor-failure 3

Parameters

multiplier

Specifies the hold time applied on the neighbor failure.

Values

2 to 25

Platforms

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

Context

[Tree] (config>vrrp>policy>priority-event>port-down hold-set)

[Tree] (config>vrrp>policy>priority-event>mc-ipsec-non-forwarding hold-set)

[Tree] (config>vrrp>policy>priority-event>lag-port-down hold-set)

[Tree] (config>vrrp>policy>priority-event>host-unreachable hold-set)

[Tree] (config>vrrp>policy>priority-event>route-unknown hold-set)

Full Context

configure vrrp policy priority-event port-down hold-set

configure vrrp policy priority-event mc-ipsec-non-forwarding hold-set

configure vrrp policy priority-event lag-port-down hold-set

configure vrrp policy priority-event host-unreachable hold-set

configure vrrp policy priority-event route-unknown hold-set

Description

This command specifies the amount of time that must pass before the set state for a VRRP priority control event can transition to the cleared state to dampen flapping events. A flapping event continually transitions between clear and set.

The hold-set command is used to dampen the effect of a flapping event. The hold-set value is loaded into a hold-set timer that prevents a set event from transitioning to the cleared state until it expires.

Each time an event transitions between cleared and set, the timer is loaded and begins a countdown to zero. When the timer reaches zero, the event is allowed to enter the cleared state. Entering the cleared state is dependent on the object controlling the event, conforming to the requirements defined in the event itself. It is possible, on some event types, to have another set action reload the hold-set timer. This extends the amount of time that must expire before entering the cleared state.

Once the hold-set timer expires and the event meets the cleared state requirements or is set to a lower threshold, the current set effect on the virtual router instances in-use priority can be removed. As with lag-port-down events, this may be a decrease in the set effect if the clearing amounts to a lower set threshold.

The hold-set command can be executed at any time. If the hold-set timer value is configured larger than the new seconds setting, the timer is loaded with the new hold-set value.

The no form of the command disables the hold timer so that event transitions are processed immediately.

Default

no hold-set

Parameters

seconds

The number of seconds that the hold-set timer waits after an event enters a set state or enters a higher threshold set state, depending on the event type.

The value of 0 disables the hold-set timer, preventing any delay in processing lower set thresholds or cleared events.

Values

0 to 86400

Platforms

All

• configure vrrp policy priority-event host-unreachable hold-set
• configure vrrp policy priority-event port-down hold-set
• configure vrrp policy priority-event lag-port-down hold-set
• configure vrrp policy priority-event route-unknown hold-set

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

• configure vrrp policy priority-event mc-ipsec-non-forwarding hold-set

Context

[Tree] (config>subscr-mgmt>bgp-prng-plcy hold-time)

Full Context

configure subscriber-mgmt bgp-peering-policy hold-time

Description

This command configures the BGP hold time, expressed in seconds.

The BGP hold time specifies the maximum time BGP waits between successive messages (either keepalive or update) from its peer, before closing the connection.

Even though the router OS implementation allows setting the keepalive time separately, the configured keepalive timer is overridden by the hold-time value under the following circumstances:

If the specified hold-time is less than the configured keepalive time, then the operational keepalive time is set to a third of the hold-time; the configured keepalive time is not changed.

If the hold-time is set to zero, then the operational value of the keepalive time is set to zero; the configured keepalive time is not changed. This means that the connection with the peer is up permanently and no keepalive packets are sent to the peer.

The no form of this command reverts to the default.

Parameters

seconds

Specifies the hold-time, in seconds, expressed as a decimal integer. A value of 0 indicates the connection to the peer is up permanently.

Values

0, 3 to 65535

Platforms

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

Context

[Tree] (config>subscr-mgmt>vrgw>brg>brg-profile hold-time)

Full Context

configure subscriber-mgmt vrgw brg brg-profile hold-time

Description

This command holds the BRG object for the specified time. This applies when the connectivity verification fails or when the last host is removed and no connectivity-verification is enabled. Hold time does not apply to an explicit removal via the radius or clear commands.

The no form of this command disables the hold time.

Parameters

seconds

Specifies the time, in seconds, to hold on to a BRG after the system considered it down.

Values

30 to 2592000

days

Specifies the hold-time in days.

Values

1 to 30

hrs

Specifies the hold-time in hours.

Values

1 to 23

min

Specifies the hold-time in minutes.

Values

1 to 59

sec

Specifies the hold-time in seconds.

Values

1 to 59

Platforms

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

Context

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

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

Full Context

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

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

Description

This command configures the minimum time that a UE is held down after a failed authentication attempt.

The no form of this command reverts to the default.

Default

hold-time sec 5

Parameters

hours

Specifies the minimum time that a user is held down in hours.

Values

1 to 1

minutes

Specifies the minimum time that a user is held down in minutes.

Values

1 to 59

seconds

Specifies the minimum time that a user is held down in seconds.

Values

0 to 59

Platforms

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

Context

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

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

Full Context

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

configure service vprn subscriber-interface group-interface wlan-gw egress hold-time

Description

This command configures the time for which egress shaping resources associated with a wlan-gw tunnel are held after the last subscriber on a tunnel is deleted.

Parameters

time

Specifies the time, in seconds, for which shaping resources are held in seconds after last subscriber is deleted.

Values

infinite to 1 to 86400

Platforms

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

Context

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

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

Full Context

configure service vprn subscriber-interface group-interface wlan-gw mobility hold-time

configure service ies subscriber-interface group-interface wlan-gw mobility hold-time

Description

This command configures the minimum time that a UE is held associated with its current Access Point (AP) before being associated with a new AP.

The hold time is used to prevent overwhelming the system with mobility triggers, by limiting the rate at which a UE can move from one AP to another while the system is very busy already.

Default

hold-time 5

Parameters

time

Specifies a hold-down time, in seconds, for handling of successive mobility triggers for a UE. It is the minimal time a UE stays associated with an AP.

Values

0 to 255

Platforms

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

Context

[Tree] (config>subscr-mgmt>sap-template hold-time)

Full Context

configure subscriber-mgmt sap-template hold-time

Description

This command configures the time for which an SAP is retained after the last session has been removed. Such SAPs can be forcefully removed using the idle-saps option in the clear>subscriber-mgmt>sap-template context.

The no form of this command reverts to the default.

Default

hold-time 30

Parameters

infinite

Keyword specifying to never automatically remove the SAP.

seconds

Specifies the time, in seconds, that the SAP is retained.

Values

30 to 2592000

Platforms

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

Context

[Tree] (config>port>aps hold-time)

Full Context

configure port aps hold-time

Description

This command specifies how much time can pass, in 100s of milliseconds, without receiving an advertise packet from the neighbor before the multi-chassis signaling link is considered not operational.

The hold-time is usually 3 times the value of the advertise-interval. The value of the advertise-interval is valid only for a multi-chassis APS as indicated by the value of neighbor IP address if it is not set to 0.0.0.0.

Parameters

hold-time

Specifies how long to wait for an APS advertisement packet before the peer in a Multi-Chassis APS group is considered operationally down.

Values

10 to 650

Platforms

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

Context

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

Full Context

configure port ethernet efm-oam hold-time

Description

This command configures efm-oam operational transition dampening timers which reduce the number of efm-oam state transitions reported to upper layers.

Default

no hold-time

Parameters

time-value

Indicates the number of seconds that the efm-oam protocol will wait before going back to the operational state after leaving the operational state. Note that the hold-time does not apply if efm-oam moved from operational to link-fault.

A hold-time value of zero indicates that there should be no delay in transitioning to the operational state. A non-zero value will cause the efm-oam protocol to attempt to negotiate with a peer if possible, but it will remain in the send-local-remote-ok state until the hold time has expired if negotiation is successful.

If efm-oam is administratively shutdown while it was in the operational state and then re-enabled when a non-zero hold time is configured, efm-oam will attempt transition to the operational state immediately.

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

Values

0 to 50

Default

0

Platforms

All

Context

[Tree] (config>port>ethernet hold-time)

Full Context

configure port ethernet hold-time

Description

This command configures port link dampening timers which reduce the number of link transitions reported to upper layer protocols. The hold-time value dampens interface transitions.

When an interface transitions from an up state to a down state, it is immediately advertised to the rest of the system if the hold-time down interval is zero, but if the hold-time down interval is greater than zero, interface down transitions are not advertised to upper layers until the hold-time down interval has expired. Likewise, an interface is immediately advertised as up to the rest of the system if the hold-time up interval is zero, but if the hold-time up interval is greater than zero, up transitions are not advertised until the hold-time up interval has expired.

For ESM SRRP setup, MCS synchronizes subscriber information between the two chassis. After a chassis recovers from a power reset/down, MCS immediately synchronizes all subscriber information at once. The longer the host list, the longer it will take to synchronize the chassis. In a fully populated chassis, it is recommended to allow at least 45 minutes for MCS synchronization. It is also recommended to hold the port down, facing the subscriber, on the recovering chassis for 45 minutes before it is allowed to forward traffic again.

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

Default

down 0 seconds — No port link down dampening is enabled; link down transitions are immediately reported to upper layer protocols.

up 0 seconds — No port link up dampening is enabled; link up transitions are immediately reported to upper layer protocols.

Parameters

hold-time-up

The delay, in seconds or centiseconds, after which to notify the upper layers when an interface transitions from a down state to an up state.

Values

0 to 36000 seconds, 0 or 10 to 3600000 centiseconds in 5 centisecond increments

The minimum non-zero hold-time-up interval on 10G or higher ports is 10 centiseconds with a granularity of 5 centiseconds. The granularity on 1G ports is 1 second. Centiseconds are not supported on 1G ports.

hold-time-down

The delay, in seconds or centiseconds, after which to notify the upper layers when an interface transitions from an up state to a down state.

Values

0 to 36000 seconds, 0 or 10 to 3600000 centiseconds in 5 centisecond increments

The minimum non-zero hold-time-down interval on 10G or higher ports is 10 centiseconds with a granularity of 5 centiseconds. The granularity on 1G ports is 1 second. Centiseconds are not supported on 1G ports.

seconds | centiseconds

Specifies the hold time units as seconds or centiseconds.

Platforms

All

Context

[Tree] (config>port>sonet-sdh hold-time)

Full Context

configure port sonet-sdh hold-time

Description

This command configures SONET link dampening timers in 100s of milliseconds. This guards against reporting excessive interface transitions. This is implemented by not advertising subsequent transitions of the interface to upper layer protocols until the configured timer has expired.

This command is supported by TDM satellite.

Default

no hold-time

Parameters

up hold-time-up

Configures the hold-timer for link up event dampening. A value of zero (0) indicates that an up transition is reported immediately.

Values

0 to 100

down hold-time-down

The hold-timer for link down event dampening. A value of zero (0) indicates that a down transition is reported immediately.

Values

0 to 100

Platforms

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

Context

[Tree] (config>port>tdm hold-time)

Full Context

configure port tdm hold-time

Description

This command configures link dampening timers in 100s of milliseconds. This guards against reporting excessive interface transitions. This is implemented by not advertising subsequent transitions of the interface to upper layer protocols until the configured timer has expired.

This command is only supported on the m4-chds3-as, m12-chds3-as, and c4-ds3 MDAs.

Default

no hold-time

Parameters

hold-time-up

Configures the hold-timer for link up event dampening. A value of zero (0) indicates that an up transition is reported immediately.

Values

0 to 100 in 100s of milliseconds (default 0)

hold-time-down

The hold-timer for link down event dampening. A value of zero (0) indicates that a down transition is reported immediately.

Values

0 to 100 in 100s of milliseconds (default 5)

Platforms

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

Context

[Tree] (config>lag hold-time)

Full Context

configure lag hold-time

Description

This command specifies the timer, in tenths of seconds, which controls the delay between detecting that a LAG is down (all active ports are down) and reporting it to the higher levels.

A non-zero value can be configured, for example, when active/standby signaling is used in a 1:1 fashion to avoid informing higher levels during the small time interval between detecting that the LAG is down and the time needed to activate the standby link.

Default

no hold-time

Parameters

hold-down-time

Specifies the hold-time for event reporting.

Values

0 to 2000

Platforms

All

Context

[Tree] (config>service>vpls>mrp>mvrp hold-time)

Full Context

configure service vpls mrp mvrp hold-time

Description

This command enables the dampening timer and applies to both types of provisioned SAPs – end-station and UNI. When a value is configured for the timer, it controls the delay between detecting that the last provisioned SAP in VPLS goes down and reporting it to the MVRP module. The CPM will wait for the time specified in the value parameter before reporting it to the MVRP module. If the SAP comes up before the hold-timer expires, the event will not be reported to MVRP module.

The non-zero hold-time does not apply for SAP transition from down to up, This kind of transition is reported immediately to MVRP module without waiting for hold-time expiration. Also this parameter applies only to the provisioned SAPs. It does not apply to the SAPs configured with the vpls-sap-template command. Also when end-station QinQ SAPs are present only the "no hold-time” configuration is allowed.

The no form of this command disables tracking of the operational status for the last active SAP in the VPLS. MVRP will stop declaring the VLAN only when the last provisioned customer (UNI) SAP associated locally with the service is deleted. Also MVRP will declare the associated VLAN attribute as soon as the first provisioned SAP is created in the associated VPLS instance, regardless of the operational state of the SAP.

Default

no hold-time

Parameters

value

Specifies the hold time in minutes

Values

1 to 30

Platforms

All

Context

[Tree] (config>service>vpls>pim-snooping hold-time)

Full Context

configure service vpls pim-snooping hold-time

Description

This command configures the duration that allows the PIM-snooping switch to snoop all the PIM states in the VPLS. During this duration, multicast traffic is flooded in the VPLS. At the end of this duration, multicast traffic is forwarded using the snooped states.

When PIM snooping is enabled in VPLS, there is a period of time when the PIM snooping switch may not have built complete snooping state. The switch cannot build states until the routers connected to the VPLS refresh their PIM messages.

This parameter is applicable only if PIM snooping is enabled.

Parameters

seconds

Specifies the PIM snooping hold time, in seconds.

Values

0 to 300

Default

90

Platforms

All

Context

[Tree] (config>service>vprn>subscriber-interface hold-time)

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

[Tree] (config>service>vpls>interface hold-time)

[Tree] (config>service>vprn>redundant-interface hold-time)

[Tree] (config>router>if hold-time)

[Tree] (config>service>ies>subscriber-interface hold-time)

[Tree] (config>service>ies>interface hold-time)

[Tree] (config>service>ies>redundant-interface hold-time)

[Tree] (config>service>vprn>interface hold-time)

Full Context

configure service vprn subscriber-interface hold-time

configure service vprn network-interface hold-time

configure service vpls interface hold-time

configure service vprn redundant-interface hold-time

configure router interface hold-time

configure service ies subscriber-interface hold-time

configure service ies interface hold-time

configure service ies redundant-interface hold-time

configure service vprn interface hold-time

Description

This command creates the CLI context to configure interface level hold-up and hold-down timers for the associated IP interface.

The up timer controls a delay for the associated IPv4 or IPv6 interface so that the system will delay the deactivation of the associated interface for the specified amount of time.

The down timer controls a delay for the associated IPv4 or IPv6 interface so that the system will delay the activation of the associated interface for the specified amount of time

Platforms

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

• configure service vprn subscriber-interface hold-time
• configure service ies subscriber-interface hold-time
• configure service vprn redundant-interface hold-time
• configure service ies redundant-interface hold-time

All

• configure service vpls interface hold-time
• configure service vprn network-interface hold-time
• configure service ies interface hold-time
• configure service vprn interface hold-time
• configure router interface hold-time

Context

[Tree] (config>service>vprn>bgp hold-time)

[Tree] (config>service>vprn>bgp>group hold-time)

[Tree] (config>service>vprn>bgp>group>neighbor hold-time)

Full Context

configure service vprn bgp hold-time

configure service vprn bgp group hold-time

configure service vprn bgp group neighbor hold-time

Description

This command configures the BGP hold time, expressed in seconds.

The BGP hold time specifies the maximum time BGP waits between successive messages (either keepalive or update) from its peer, before closing the connection. This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific value is used.

Even though the router OS implementation allows setting the keepalive (config>service>vprn>bgp keepalive, config>service>vprn>bgp>group keepalive, config>service>vprn>bgp>group>neighbor keepalive) time separately, the configured keepalive timer is overridden by the hold-time value under the following circumstances:

• If the specified hold-time is less than the configured keepalive time, then the operational keepalive time is set to a third of the hold-time; the configured keepalive time is not changed.

• If the hold-time is set to zero, then the operational value of the keepalive time is set to zero; the configured keepalive time is not changed. This means that the connection with the peer is up permanently and no keepalive packets are sent to the peer.

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

The no form of this command used at the group level reverts to the value defined at the global level.

The no form of this command used at the neighbor level reverts to the value defined at the group level.

Default

hold-time 90

Parameters

seconds

Specifies the hold-time, in seconds, expressed as a decimal integer. A value of 0 indicates the connection to the peer is up permanently.

Values

0, 3 to 65535

seconds2

Specifies the minimum hold-time that is accepted for the session. If the peer proposes a hold-time lower than this value the session attempt is rejected.

Platforms

All

Context

[Tree] (config>service>oper-group hold-time)

Full Context

configure service oper-group hold-time

Description

Commands in this context configure hold time information.

Platforms

All

Context

[Tree] (config>router>bgp>group>neighbor hold-time)

[Tree] (config>router>bgp hold-time)

[Tree] (config>router>bgp>group hold-time)

Full Context

configure router bgp group neighbor hold-time

configure router bgp hold-time

configure router bgp group hold-time

Description

This command configures the BGP hold time, expressed in seconds.

The BGP hold time specifies the maximum time BGP waits between successive messages (either keepalive or update) from its peer, before closing the connection. This configuration parameter can be set at three levels: global level (applies to all peers), group level (applies to all peers in group) or neighbor level (only applies to specified peer). The most specific value is used.

Even though the implementation allows setting the keepalive time separately, the configured keepalive timer is overridden by the hold-time value under the following circumstances:

• If the specified hold-time is less than the configured keepalive time, then the operational keepalive time is set to a third of the hold-time; the configured keepalive time is not changed.

• If the hold-time is set to zero, then the operational value of the keepalive time is set to zero; the configured keepalive time is not changed. This means that the connection with the peer is up permanently and no keepalive packets are sent to the peer.

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

The no form of this command used at the group level reverts to the value defined at the global level.

The no form of this command used at the neighbor level reverts to the value defined at the group level.

Default

hold-time 90

Parameters

seconds

Specifies the hold-time, in seconds, expressed as a decimal integer. A value of 0 indicates the connection to the peer is up permanently.

Values

0, 3 to 65535

min seconds2

Specifies the minimum hold-time that will be accepted for the session. If the peer proposes a hold-time lower than this value, the session attempt will be rejected.

Platforms

All

Context

[Tree] (config>port>aps hold-time-aps)

Full Context

configure port aps hold-time-aps

Description

This command configures hold-down timers to debounce signal failure conditions (lais, b2err-sf) and signal degrade conditions (b2err-sd) for Uni 1+1 Sig+Data APS switching mode (switching mode uni-1plus1).

The no version of this command resets the hold-down timer to the default value.

Default

0 (disabled)

Parameters

sf-time

Specifies an integer to define the signal failure hold-down time in milliseconds.

Values

1 to 100

sd-time

Specifies an integer to define the signal degrade hold-down time in milliseconds.

Values

1 to 100

Platforms

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

Context

[Tree] (config>router>mpls>mpls-tp>oam-template hold-time-down)

Full Context

configure router mpls mpls-tp oam-template hold-time-down

Description

This command configures the hold-down dampening timer. It is equivalent to a hold-off timer.

Default

hold-time-down 0

Parameters

interval

Specifies the hold-down dampening timer interval.

Values

0 to 5000 deciseconds in 10 ms increments

Platforms

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

Context

[Tree] (config>router>mpls>mpls-tp>oam-template hold-time-up)

Full Context

configure router mpls mpls-tp oam-template hold-time-up

Description

This command configures the hold-up dampening timer. This can be used to provide additional dampening to the state of proactive CC BFD sessions.

Default

hold-time-up 20

Parameters

interval

Specifies the hold-up dampening timer interval.

Values

0 to 500 deciseconds, in 100 ms increments

Platforms

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

Context

[Tree] (config>router>mpls hold-timer)

Full Context

configure router mpls hold-timer

Description

This command specifies the amount of time that the ingress node holds before programming its data plane and declaring the LSP up to the service module. This occurs anytime the ingress node brings up an LSP path or switches traffic from a working path to another working path of the same LSP.

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

Default

no hold-timer

Parameters

seconds

Specifies the time (in seconds), for which the ingress node holds before programming its data plane and declaring the LSP up to the service module.

Values

0 to 1000

Default

1

Platforms

All

Context

[Tree] (debug>router>rip holddown)

Full Context

debug router rip holddown

Description

This command enables debugging for RIP holddowns.

Parameters

ip-int-name | ip-address

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

Platforms

All

Context

[Tree] (debug>router>ripng holddown)

Full Context

debug router ripng holddown

Description

This command enables debugging for RIPng holddowns.

Parameters

ip-int-name| ipv6-address

Debugs the RIPng holddowns sent on the neighbor IP address or interface.

Platforms

All

Context

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

[Tree] (config>service>vprn>pim>rp>rp-candidate holdtime)

Full Context

configure service vprn pim rp ipv6 rp-candidate holdtime

configure service vprn pim rp rp-candidate holdtime

Description

This command specifies the length of time a neighbor considers the sending router to be operationally up.

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

Default

holdtime 150

Parameters

holdtime

Specifies the length of time, in seconds, that a neighbor should consider the sending router to be operational.

Values

5 to 255

Platforms

All

Context

[Tree] (config>router>pim>rp>rp-candidate holdtime)

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

Full Context

configure router pim rp rp-candidate holdtime

configure router pim rp ipv6 rp-candidate holdtime

Description

This command configures the length of time, in seconds, that neighbors should consider the sending router to be operationally up. A local RP cannot be configured on a logical router.

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

Default

holdtime 150

Parameters

holdtime

Specifies the hold time, in seconds.

Values

5 to 255

Platforms

All

Context

[Tree] (config>subscr-mgmt>gtp>peer-profile>charging home)

Full Context

configure subscriber-mgmt gtp peer-profile charging-characteristics home

Description

This command configures the charging characteristics for home UE.

Default

no home

Parameters

bit

Specifies up to 16 bits to set in the Charging Characteristics Information Element (IE) for home UE, if not known by other means such as RADIUS.

Values

bit0, bit1, bit2, bit3, bit4, bit5, bit6, bit7, bit8, bit9, bit10, bit11, bit12, bit13, bit14, bit15

Platforms

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

Context

[Tree] (config>system>security>user home-directory)

[Tree] (config>system>security>user-template home-directory)

Full Context

configure system security user home-directory

configure system security user-template home-directory

Description

This command configures the local home directory for the user for both console (file commands and '>' redirection) and FTP access.

If the URL or the specified URL/directory structure is not present, then a warning message is issued and the default is assumed.

The no form of this command removes the configured home directory.

Default

no home-directory

Parameters

local-url-prefix [directory] [directory/directory]

Specifies the user’s local home directory URL prefix and directory structure, up to 190 characters.

Platforms

All

Context

[Tree] (config>router>mpls>path hop)

Full Context

configure router mpls path hop

Description

This command specifies the hops that the LSP should traverse on its way to the egress router. When specified, the IP address can be the interface IP address, a loopback interface address, or the system IP address. If a loopback interface or the system IP address is specified then the LSP can choose the best available interface.

When an IPv6 hop is specified, the interface IP address must be a global unicast IPv6 address. A link-local address is not allowed and is rejected in the configuration if attempted.

Optionally, the LSP ingress and egress IP address can be included as the first and the last hop. A hop list can include the ingress interface IP address, the system IP address, and the egress IP address of any of the hops being specified.

When the sid-label parameter is specified, this command specifies an MPLS label value for a hop in the path of an SR-TE LSP. The label value implied by the SID is only used when the path is used by an SR-TE LSP.

The no form of this command deletes hop list entries for the path. All the LSPs currently using this path are affected. Additionally, all services actively using these LSPs are affected. The path must be shutdown first in order to delete the hop from the hop list. The no hop hop-index command will not result in any action except a warning message on the console indicating that the path is administratively up.

Parameters

hop-index

Specifies the hop index is used to order the hops specified. The LSP always traverses from the lowest hop index to the highest. The hop index does not need to be sequential.

Values

1 to 1024

ip-address

Specifies a loopback interface, the system or network interface IP address of the transit router. An interface IPv6 address must be a global unicast address.

Values

ipv4-address — a.b.c.d

ipv6-address — x:x:x:x:x:x:x:x (eight 16-bit pieces)

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

x — 0 to FFFF (hexadecimal)

d — 0 to 255 (decimal)

loose

This keyword specifies that the route taken by the LSP from the previous hop to this hop can traverse through other routers. Multiple hop entries with the same IP address are flagged as errors. Either the loose or strict keyword must be specified.

strict

This keyword specifies that the LSP must take a direct path from the previous hop router to this router. No transit routers between the previous router and this router are allowed. If the IP address specified is the interface address, then that is the interface the LSP must use. If there are direct parallel links between the previous router and this router and if system IP address is specified, then any one of the available interfaces can be used by the LSP. The user must ensure that the previous router and this router have a direct link. Multiple hop entries with the same IP address are flagged as errors. Either the loose or strict keyword must be specified.

sid-value

Specifies the SID value. The sid-value can be any valid MPLS/SR label value. It is not restricted by any locally-defined label ranges since these may be different on the remote node or adjacency for which the SID is defined.

Values

32 to 1048575

Platforms

All

Context

[Tree] (config>service>pw-routing>path hop)

Full Context

configure service pw-routing path hop

Description

This command configures each hop on an explicit path that can be used by one or more dynamic MS-PWs. It specifies the IP addresses of the hops that the MS-PE should traverse. These IP addresses can correspond to the system IP address of each S-PE, or the IP address on which the T-LDP session to a given S-PE terminates.

The no form of this command deletes hop list entries for the path. All the MS-PWs currently using this path are unaffected. Additionally, all services actively using these MS-PWs are unaffected. The path must be shutdown first in order to delete the hop from the hop list. The ' no hop hop-index’ command will not result in any action, except for a warning message on the console indicating that the path is administratively up.

Default

no hop

Parameters

hop-index

Specifies a locally significant numeric identifier for the hop. The hop index is used to order the hops specified. The LSP always traverses from the lowest hop index to the highest. The hop index does not need to be sequential.

Values

1 to 1024

ip-address

Specifies the system IP address or terminating IP address for the T-LDP session to the S-PE corresponding to this hop. For a given IP address on a hop, the system will choose the appropriate SDP to use.

Platforms

All

Context

[Tree] (config>filter>ipv6-filter>entry>match hop-by-hop-opt)

Full Context

configure filter ipv6-filter entry match hop-by-hop-opt

Description

This command enables match on existence of Hop-by-Hop Options Extension Header in the IPv6 filter policy.

The no form of this command ignores Hop-by-Hop Options Extension Header presence/absence in a packet when evaluating match criteria of a given filter policy entry.

Default

no hop-by-hop-opt

Parameters

true

Matches a packet with a Hop-by-Hop Options Extension header.

false

Matches a packet without a Hop-by-Hop Options Extension header.

Platforms

All

Context

[Tree] (cfg>sys>sec>cpm>ipv6-filter>entry>match hop-by-hop-opt)

Full Context

configure system security cpm-filter ipv6-filter entry match hop-by-hop-opt

Description

This command enables match on existence of Hop-by-Hop Options Extension Header in the IPv6 filter policy. This command applies to the 7750 SR and 7950 XRS.

The no form of this command ignores Hop-by-Hop Options Extension Header presence/absence in a packet when evaluating match criteria of a given filter policy entry.

Default

no hop-by-hop-opt

Parameters

true

Match if a packet contains Hop-by-Hop Options Extension Header.

false

Match if a packet does not contain Hop-by-Hop Options Extension Header.

Platforms

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

Context

[Tree] (config>router>mpls>lsp>fast-reroute hop-limit)

[Tree] (config>router>mpls>lsp-template>fast-reroute hop-limit)

Full Context

configure router mpls lsp fast-reroute hop-limit

configure router mpls lsp-template fast-reroute hop-limit

Description

For fast reroute, how many more routers a detour is allowed to traverse compared to the LSP itself. For example, if an LSP traverses four routers, any detour for the LSP can be no more than ten router hops, including the ingress and egress routers.

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

Default

hop-limit 16

Parameters

limit

Specify the maximum number of hops.

Values

0 to 255

Platforms

All

Context

[Tree] (config>router>mpls>lsp>primary-p2mp-instance hop-limit)

[Tree] (config>router>mpls>lsp hop-limit)

Full Context

configure router mpls lsp primary-p2mp-instance hop-limit

configure router mpls lsp hop-limit

Description

This command specifies the maximum number of hops that an LSP can traverse, including the ingress and egress routers. An LSP is not set up if the hop limit is exceeded. This value can be changed dynamically for an LSP that is already set up with the following implications.

If the new value is less than the current number of hops of the established LSP, the LSP is brought down. The software then tries to re-establish the LSP within the new hop-limit number. If the new value is equal to or greater than the current number hops of the established LSP, the LSP is not affected.

The config>router>mpls>lsp>primary-p2mp-instance> hop-limit command is not supported on the 7450 ESS.

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

Default

hop-limit 255

Parameters

number

Specifies the number of hops the LSP can traverse, expressed as an integer.

Values

2 to 255

Platforms

All

Context

[Tree] (config>router>mpls>lsp>secondary hop-limit)

[Tree] (config>router>mpls>lsp>primary hop-limit)

Full Context

configure router mpls lsp secondary hop-limit

configure router mpls lsp primary hop-limit

Description

This optional command overrides the config>router>mpls>lsp lsp-name>hop-limit command. This command specifies the total number of hops that an LSP traverses, including the ingress and egress routers.

This value can be changed dynamically for an LSP that is already set up with the following implications:

If the new value is less than the current hops of the established LSP, the LSP is brought down. MPLS then tries to re-establish the LSP within the new hop-limit number. If the new value is equal or more than the current hops of the established LSP then the LSP will be unaffected.

The no form of this command reverts the values defined under the LSP definition using the config>router>mpls>lsp lsp-name>hop-limit command.

Default

no hop-limit

Parameters

number

Specifies the number of hops the LSP can traverse, expressed as an integer.

Values

2 to 255

Platforms

All

Context

[Tree] (config>filter>ipv6-filter>entry>match hop-limit)

Full Context

configure filter ipv6-filter entry match hop-limit

Description

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

The no form of this command removes the configuration.

Default

no hop-limit

Parameters

lt

Specifies "less than”. The lt parameter cannot be used with the lowest possible numerical value for the parameter.

gt

Specifies "greater than”. The gt parameter cannot be used with the highest possible numerical value for the parameter.

eq

Specifies "equal to”.

hop-limit-value

Specifies the hop limit value for the rate limit action.

Values

0 to 255

Platforms

All

Context

[Tree] (config>subscr-mgmt>loc-user-db>ppp host)

[Tree] (config>subscr-mgmt>loc-user-db>ipoe host)

Full Context

configure subscriber-mgmt local-user-db ppp host

configure subscriber-mgmt local-user-db ipoe host

Description

This command creates an IPoE or PPP host entry in the local user database. A host entry in the local user database is matched based on the specified match-list criteria and an optional mask that is applied to the host-identification parameters.

A default host entry can be created without host-identification parameters which is used when no other host entries match. Note that creating a default host entry also requires a match-list to be specified.

The no form of this command removes the host entry from the local user database.

Parameters

host-name

Specifies a unique host name, up to 32 characters. The host-name default creates a special match-all host entry that should not have host-identification parameters and is used when no other host entries match.

create

Keyword used to create the host name. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

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

Context

[Tree] (debug>router>igmp host)

Full Context

debug router igmp host

Description

This command enables debugging for the IGMP host.

The no form of the command disables debugging.

Parameters

ip-address

Debugs the information associated with the specified IP address.

service-id

Debugs information associated with the service ID.

Values

service-id: 1 to 2148278386

svc-name: up to 64 characters.

group-interface ip-int-name

Debugs the information associated with the specified IP interface name.

Values

IP interface address

Platforms

All

Context

[Tree] (config>subscr-mgmt>acct-plcy host-accounting)

Full Context

configure subscriber-mgmt radius-accounting-policy host-accounting

Description

This command enables per-host accounting. In host accounting mode, the acct-session-id is generated per host. This acct-session-id is uniformly included in all accounting messages (START/INTERIM-UPDATE/STOP) and it can be included in RADIUS Access-Request message.

Accounting counters are based on the queue counters and as such are aggregated for all host sharing the queues within an sla-profile instance. CoA and LI is supported based on the acct-session-id of the host.

The no form of this command reverts to the default.

Parameters

interim-update

Specifies that no interim-update messages are sent for the related subscriber hosts when the session is deleted. Without this keyword, only START and STOP accounting messages are generated when the host is established or terminated. This is equivalent to a time-based accounting where only the duration of the session is required.

Platforms

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

Context

[Tree] (config>service>vpls host-connectivity-verify)

[Tree] (config>service>vpls>sap host-connectivity-verify)

Full Context

configure service vpls host-connectivity-verify

configure service vpls sap host-connectivity-verify

Description

This command enables subscriber host connectivity verification on a given VPLS SAP or within a VPLS service.

This tool will periodically scan all known hosts (from dhcp-state) and perform a UC ARP request. The subscriber host connectivity verification will maintain state (connected vs. not-connected) for all hosts.

The no form of this command reverts to the default.

Parameters

ip-address

Specifies an unused IP address in the same network for generation of subscriber host connectivity verification packets.

ieee-address

Specifies the source MAC address to be used for generation of subscriber host connectivity verification packets.

interval

The interval, in minutes, which specifies the time interval in which all known sources should be verified. The actual rate is then dependent on number of known hosts and interval.

Values

1 to 6000 Note that a zero value can be used by the SNMP agent to disable host-connectivity-verify.

action {remove | alarm}

Defines the action taken on a subscriber host connectivity verification failure for a given host. The remove keyword raises an alarm and removes the dhcp-state and releases all allocated resources (queues, table entries, and so on). A DHCP release is signaled to corresponding DHCP server. The static host is never removed. The alarm keyword raises an alarm indicating that the host is disconnected.

retry-timeout

Specifies the time, in seconds, to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled.

Values

0 to 120

count

Specifies the number of connectivity check retransmissions.

Values

10 to 60 seconds

Platforms

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

Context

[Tree] (config>service>ies>sub-if>grp-if host-connectivity-verify)

[Tree] (config>service>vprn>sub-if>grp-if host-connectivity-verify)

Full Context

configure service ies subscriber-interface group-interface host-connectivity-verify

configure service vprn subscriber-interface group-interface host-connectivity-verify

Description

This command enables subscriber host connectivity verification on a given SAP within a service. This tool periodically scans all known hosts (from dhcp-state) and perform UC ARP requests. The subscriber host connectivity verification maintains state (connected versus. not-connected) for all hosts.

The no form of this command reverts to the default.

Parameters

interval

Specifies the interval, in minutes, which specifies the time interval which all known sources should be verified. The actual rate is then dependent on the number of known hosts and interval.

Values

1 to 6000

A zero value can be used by the SNMP agent to disable host-connectivity-verify.

action {remove | alarm}

Defines the action taken on a subscriber host connectivity verification failure for a given host. The remove keyword raises an alarm and removes dhcp-state and releases all allocated resources (queues, table entries and so on). DHCP-RELEASE is signaled to corresponding DHCP server. Static hosts is never removed. The alarm keyword raises an alarm indicating that the host is disconnected.

retry-timeout

Specifies the retry timeout.

Values

10 to 60 seconds

count

Specifies the number of retry requests.

Values

2 to 29

family

Allows the host connectivity checks to be performed for IPv4 endpoint, IPv6 endpoint or both. With family IPv6 configured, host connectivity checks is performed on the global unicast address (assigned via SLAAC or DHCPv6 IA_NA) and link-local address of a Layer 3 RG or bridged hosts. In case of SLAAC assignment, host connectivity can only be performed if the /128 is known (via downstream ND). DHCPv6 PD assigned prefixes is removed if link-local address is determined to be unreachable via host connectivity check” Reachability checks for GUA and link-local address is done simultaneously.

Values

ipv4, ipv6, both

Platforms

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

Context

[Tree] (config>service>ies>if host-connectivity-verify)

[Tree] (config>service>vprn>if host-connectivity-verify)

Full Context

configure service ies interface host-connectivity-verify

configure service vprn interface host-connectivity-verify

Description

This command enables subscriber host connectivity verification for all hosts on this interface. This tool periodically scans all known hosts (from dhcp-state) and perform UC ARP requests. The subscriber host connectivity verification maintains state (connected vs. not-connected) for all hosts.

The no form of this command reverts to the default.

Parameters

source {vrrp | interface}

Specifies the source to be used for generation of subscriber host connectivity verification packets. The vrrp keyword specifies that the VRRP state should be used to select proper IP and MAC (active uses VRID, back-up uses interface addresses). The interface keyword forces the use of the interface mac and ip addresses.

Note:

There are up to 256 possible subnets on a given interface, therefore, the subscriber host connectivity verification tool always uses an address of the subnet to which the given host is pertaining. For group-interfaces, one of the parent subscriber interface subnets (depending on host's address) is used.

action {remove | alarm}

Defines the action taken on a subscriber host connectivity verification failure for a given host. The remove keyword raises an alarm and removes dhcp-state and releases all allocated resources (queues, table entries, and so on). The alarm keyword raises an alarm indicating that the host is disconnected.

interval

Specifies the interval, expressed in minutes, which specifies when all known sources should be verified. The actual rate is then dependent on number of known hosts and interval.

Values

1 to 6000

Note:

A zero value can be used by the SNMP agent to disable host-connectivity-verification.

retry-timeout

Specifies the timeout, in seconds, before a connectivity check retransmission.

Values

10 to 60

retry-count

Specifies the number of connectivity check retransmissions.

Values

2 to 29

Platforms

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

Context

[Tree] (debug>service>id host-connectivity-verify)

Full Context

debug service id host-connectivity-verify

Description

This command enables Subscriber Host Connectivity Verification (SHCV) debugging.

The no form of the command disables the SHCV debugging.

Platforms

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

Context

[Tree] (oam host-connectivity-verify)

Full Context

oam host-connectivity-verify

Description

This command triggers the host connectivity verification checks.

Parameters

service-id

Specifies the service ID to diagnose or manage.

Values

1 to 2147483647, service-name: up to 64 characters

sap-id

Specifies the physical port identifier portion of the SAP definition.

Values

null	port-id | bundle-id | bpgrp-id | lag-id | aps-id
dot1q	port-id | bundle-id | bpgrp-id | lag-id | aps-id | pw-id:[qtag1| cp-conn-prof-id]
qinq	port-id | bundle-id | bpgrp-id | lag-id | pw-id:[qtag1 cp-conn-prof-id].[qtag2 | cp-conn-prof-id]
	cp	keyword
	conn-prof-id	1 to 8000
cem	slot/mda/port.channel
ima-grp	bundle-id [:vpi/vci | vpi | vpi1.vpi2 | cp.conn-prof-id]
	cp	keyword
	conn-prof-id	1 to 8000
port-id	slot/mda/port[.channel] esat-id/slot/port pxc-id.sub-port
aps-id	aps-group-id[.channel]
	aps	keyword
	group-id	1 to 128
ccag-id	ccag-id.path-id[cc-type]:cc-id
	ccag	keyword
	id	1 to 8
	path-id	a | b
	cc-type	.sap-net | .net-sap
	cc-id	1 to 4094
eth-tunnel	eth-tunnel-id[:eth-tun-sap-id]
	id	1 to 1024
	eth-tun-sap-id	0 to 4094
lag-id	lag-id
	lag	keyword
	id	1 to 800
pw-id	pw-id
	pw	keyword
	id	1 to 10239
qtag1	* | 0 to 4094
qtag2	* | null | 0 to 4094
tunnel-id	tunnel-id.private | public:tag
	tunnel	keyword
	id	1 to 16
	tag	0 to 4094

sub-indent-string

Specifies an existing subscriber-id, up to 32 characters.

sla-profile-name

Specifies an existing SLA profile name, up to 32 characters. The SLA profile is configured in the config>subscr-mgmt>sla-profile context.

Platforms

All

Context

[Tree] (config>subscr-mgmt>loc-user-db>ppp>host host-identification)

[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host host-identification)

Full Context

configure subscriber-mgmt local-user-db ppp host host-identification

configure subscriber-mgmt local-user-db ipoe host host-identification

Description

Commands in this context configure host identification parameters.

Platforms

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

Context

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

Full Context

configure router policy-options policy-statement entry from host-ip

Description

This command specifies a prefix list host IP address as a match criterion for the route policy-statement entry.

Default

no host-ip

Parameters

prefix-list-name

Specifies the prefix-list name. Allowed values are any string up to 64 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

The prefix-list-name is defined in the config>router>policy-options>prefix-list context.

Platforms

All

Context

[Tree] (config>subscr-mgmt>host-lockout-plcy host-key)

Full Context

configure subscriber-mgmt host-lockout-policy host-key

Description

This command specifies the parameters used in host identification for lockout on a given SAP or capture SAP.

no host-key – include (MAC address, Circuit-Id, Remote-Id)

host-key mac – include MAC address only

"host-key mac” should be used in DHCPv4 scenarios where Circuit-Id and Remote-Id are changed with "dhcp option action replace” configuration: a host lockout context is created with the replaced Circuit-Id/Remote-Id; with the default host-key (including Circuit-Id and Remote-Id), lockout does not kick in on the original trigger packet when it is retransmitted by the client.

Changing the host-key to mac should be used with care: all hosts with the same MAC address on a given SAP or capture SAP are identified as a single host with respect to host-lockout.

This command cannot be changed when the host-lockout-policy is referenced (configured under a SAP context).

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

Parameters

mac

Specifies to use the MAC address only for host identification for lockout.

Platforms

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

Context

[Tree] (config>service>vpls>sap>arp-host host-limit)

[Tree] (config>subscr-mgmt>msap-policy>vpls-only>arp-host host-limit)

[Tree] (config>service>vprn>sub-if>grp-if>arp-host host-limit)

[Tree] (config>service>ies>sub-if>grp-if>arp-host host-limit)

Full Context

configure service vpls sap arp-host host-limit

configure subscriber-mgmt msap-policy vpls-only-sap-parameters arp-host host-limit

configure service vprn subscriber-interface group-interface arp-host host-limit

configure service ies subscriber-interface group-interface arp-host host-limit

Description

This command configures the maximum number of ARP hosts.

The no form of this command reverts to the default.

Default

host-limit 1

Parameters

max-num-hosts

Specifies the maximum number of ARP hosts allowed on this SAP.

Note:

The operational maximum value may be smaller due to equipped hardware dependencies.

Values

1 to 131071