h Commands

half-life

half-life

Syntax

half-life half-life max-suppress-time max-time

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

half-life

Syntax

half-life minutes

no half-life

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

handler

handler

Syntax

[no] handler event-handler-name

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

handler

Syntax

handler name [create]

no handler name

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

hardware-timestamp

hardware-timestamp

Syntax

[no] hardware-timestamp

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

hash-algorithm

hash-algorithm

Syntax

hash-algorithm {hash | hash2 | custom| cleartext}

no hash-algorithm

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

hash-algorithm

Syntax

hash-algorithm algorithm

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

hash-label

hash-label

Syntax

hash-label

hash-label [signal-capability]

no hash-label

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

hash-label

Syntax

hash-label signal-capability

hash-label

no hash-label

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

hash-label

Syntax

hash-label [signal-capability]

no hash-label

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

hash-label

Syntax

hash-label

hash-label signal-capability

no hash-label

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

hash-mask-len

hash-mask-len

Syntax

hash-mask-len hash-mask-length

no hash-mask-len

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

hash-mask-len

Syntax

hash-mask-len hash-mask-length

no hash-mask-len

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

hash-mask-len

Syntax

hash-mask-len hash-mask-length

no hash-mask-len

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

hash-weight-threshold

hash-weight-threshold

Syntax

hash-weight-threshold weight [action action] [cost static-cost]

no hash-weight-threshold

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

hashing

hashing

Syntax

hashing {bcrypt | sha2-pbkdf2| sha3-pbkdf2}

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

hd

hd

Syntax

hd

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

head-end

head-end

Syntax

head-end local

head-end ipv4-address

no head-end

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

header

header

Syntax

header header-number [create]

no header header-number

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

header-sanity

header-sanity

Syntax

header-sanity direction direction [create]

no header-sanity direction direction

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

header-sequence

header-sequence

Syntax

header-sequence header-sequence

no header-sequence

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

health-check

health-check

Syntax

health-check

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

health-check

Syntax

[no] health-check [interval interval]

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

heartbeat

heartbeat

Syntax

heartbeat

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

hello

hello

Syntax

hello timeout factor

no hello

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.

Table 1. Hello Timeout Factors

Context

Timeout

Factor

config>router>ldp>if-params

15

3

config>router>ldp>targ-session

45

3

config>router>ldp>if-params>if

Inherits values from interface-parameters context.

config>router>ldp>targ-session>peer

Inherits values from targeted-session context.

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

hello

Syntax

hello [detail]

no hello

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

hello

Syntax

hello [detail]

no hello

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

hello-auth-keychain

hello-auth-keychain

Syntax

hello-auth-keychain name

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

hello-authentication

hello-authentication

Syntax

[no] hello-authentication

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

hello-authentication

Syntax

[no] hello-authentication

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

hello-authentication-key

hello-authentication-key

Syntax

hello-authentication-key {authentication-key | hash-key} [hash | hash2 | custom]

no hello-authentication-key

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

hello-authentication-key

Syntax

hello-authentication-key [authentication-key | hash-key] [ hash | hash2 | custom]

no hello-authentication-key

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

hello-authentication-type

hello-authentication-type

Syntax

hello-authentication-type {password | message-digest}

no hello-authentication-type

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

hello-authentication-type

Syntax

hello-authentication-type {password | message-digest}

no hello-authentication-type

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

hello-interval

hello-interval

Syntax

hello-interval hello-interval

hello-interval infinite

no hello-interval

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

hello-interval

Syntax

hello-interval seconds

no hello-interval

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

hello-interval

Syntax

hello-interval seconds

no hello-interval

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.

Note:

The neighbor hold time is (hello multiplier X hello interval) on non-designated intermediate system broadcast interfaces and point-to-point interfaces and is (hello multiplier X hello interval / 3) on designated intermediate system broadcast interfaces. Hello values can be adjusted for faster convergence, but the hold time should always be > 3 to reduce routing instability.

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

hello-interval

Syntax

hello-interval hello-interval

no hello-interval

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

hello-interval

Syntax

hello-interval seconds

no hello-interval

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

hello-interval

Syntax

hello-interval hello-interval

no hello-interval

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

hello-interval

Syntax

hello-interval milli-seconds

no hello-interval

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

hello-interval

Syntax

hello-interval hello-interval

no hello-interval

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

hello-interval

Syntax

hello-interval seconds

no hello-interval

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

hello-interval

Syntax

hello-interval number

no hello-interval

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

hello-multiplier

hello-multiplier

Syntax

hello-multiplier multiplier

no hello-multiplier

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

hello-multiplier

Syntax

hello-multiplier multiplier

no hello-multiplier

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.

Note:

The neighbor hold time is (hello multiplier X hello interval) on point-to-point interfaces, and (hello multiplier X hello interval / 3) on broadcast interfaces. Hello values can be adjusted for faster convergence, but the hold-time should always be > 3 to reduce routing instability.

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

hello-multiplier

Syntax

hello-multiplier deci-units

no hello-multiplier

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

hello-multiplier

Syntax

hello-multiplier deci-units

no hello-multiplier

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

hello-multiplier

Syntax

hello-multiplier deci-units

no hello-multiplier

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

hello-multiplier

Syntax

hello-multiplier multiplier

no hello-multiplier

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.

Note:

The neighbor hold time is (hello multiplier X hello interval) on non-designated intermediate system broadcast interfaces and point-to-point interfaces and is (hello multiplier X hello interval / 3) on designated intermediate system broadcast interfaces. Hello values can be adjusted for faster convergence, but the hold time should always be > 3 to reduce routing instability.

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

hello-padding

hello-padding

Syntax

hello-padding {none | adaptive | loose | strict}

no hello-padding

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

hello-padding

Syntax

[no] hello-padding {none | adaptive | loose | strict}

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

hello-reduction

hello-reduction

Syntax

hello-reduction {enable factor | disable}

no hello-reduction

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

hello-time

hello-time

Syntax

hello-time hello-time

no hello-time [hello-time]

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

hello-time

Syntax

[no] hello-time seconds

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

help

help

Syntax

help

help edit

help global

help special-characters

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

helper-disable

helper-disable

Syntax

[no] helper-disable

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.

Note:

This command is a historical command and should not be disabled. Configuring helper-disable has the effect of disabling graceful restart, because the router only supports helper mode.

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

Default

no helper-disable

Platforms

All

helper-disable

Syntax

[no] helper-disable

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.

Note:

This command is a historical command and should not be disabled. Configuring helper-disable has the effect of disabling graceful restart, because the router only supports helper mode.

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

Default

no helper-disable

Platforms

All

helper-disable

Syntax

[no] helper-disable

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.

Note:

This command is a historical command and should not be disabled. Configuring helper-disable has the effect of disabling graceful restart, because the router only supports helper mode.

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

Platforms

All

helper-disable

Syntax

[no] helper-disable

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.

Note:

This command is a historical command and should not be disabled. Configuring helper-disable has the effect of disabling graceful restart, because the router only supports helper mode.

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

Default

no helper-disable

Platforms

All

helper-override-restart-time

helper-override-restart-time

Syntax

helper-override-restart-time seconds

no helper-override-restart-time

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

helper-override-restart-time

Syntax

helper-override-restart-time seconds

no helper-override-restart-time

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

helper-override-stale-time

helper-override-stale-time

Syntax

helper-override-stale-time seconds

no helper-override-stale-time

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

helper-override-stale-time

Syntax

helper-override-stale-time seconds

no helper-override-stale-time

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

hi-bw-mcast-src

hi-bw-mcast-src

Syntax

hi-bw-mcast-src [alarm] [group group-id] [default-paths-only]

no hi-bw-mcast-src

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

high

high

Syntax

high

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

high

Syntax

high

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

high-availability

high-availability

Syntax

high-availability seconds

no high-availability

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

high-octets-discarded-count

high-octets-discarded-count

Syntax

[no] high-octets-discarded-count

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

high-octets-discarded-count

Syntax

[no] high-octets-discarded-count

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

high-octets-offered-count

high-octets-offered-count

Syntax

[no] high-octets-offered-count

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

high-octets-offered-count

Syntax

[no] high-octets-offered-count

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

high-packets-discarded-count

high-packets-discarded-count

Syntax

[no] high-packets-discarded-count

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

high-packets-discarded-count

Syntax

[no] high-packets-discarded-count

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

high-packets-offered-count

high-packets-offered-count

Syntax

[no] high-packets-offered-count

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

high-packets-offered-count

Syntax

[no] high-packets-offered-count

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

high-prio-only

high-prio-only

Syntax

high-prio-only percent

no high-prio-only

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

high-prio-only

Syntax

high-prio-only percent-of-mbs

no high-prio-only

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

high-prio-only

Syntax

high-prio-only percent-of-mbs

no high-prio-only

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

high-rate-hold-time

high-rate-hold-time

Syntax

high-rate-hold-time seconds [active-min-only]

no high-rate-hold-time

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

high-slope

high-slope

Syntax

[no] high-slope

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

high-wmark

high-wmark

Syntax

high-wmark percent

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

high-wmark

Syntax

high-wmark high-watermark low-wmark low-watermark

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

highplus

highplus

Syntax

highplus

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

highplus

Syntax

highplus

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

highplus-slope

highplus-slope

Syntax

[no] highplus-slope

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

history

history

Syntax

history

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

history-size

history-size

Syntax

history-size size

no history-size

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

hli-event

hli-event

Syntax

hli-event {forward | backward | aggregate} threshold raise-threshold [clear clear-threshold]

no hli-event {forward | backward | aggregate}

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

hli-force-count

hli-force-count

Syntax

[no] hli-force-count

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

hli-force-count

Syntax

[no] hli-force-count

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

hold-clear

hold-clear

Syntax

hold-clear seconds

no hold-clear

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

hold-count

hold-count

Syntax

hold-count BPDU tx hold count

no hold-count

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

hold-down-time

hold-down-time

Syntax

hold-down-time seconds

no hold-down-time

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

hold-down-time

Syntax

hold-down-time [sec seconds] [ min minutes] [hrs hours] [days days]

no hold-down-time

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

hold-down-time

Syntax

hold-down-time seconds

no hold-down-time

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

hold-down-timer

hold-down-timer

Syntax

hold-down-timer hold-down-timer

no hold-down-timer

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.

Note:

If the revert timer is also configured, the revert timer is not started until after the number of S-BFD sessions that are up ≥ threshold and the hold down timer for the primary candidate path has expired.

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

hold-multiplier

hold-multiplier

Syntax

hold-multiplier multiplier

no hold-multiplier

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

hold-multiplier

Syntax

hold-multiplier multiplier

no hold-multiplier

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

hold-multiplier

Syntax

hold-multiplier multiplier

no hold-multiplier

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

hold-on-neighbor-failure

hold-on-neighbor-failure

Syntax

hold-on-neighbor-failure multiplier

no hold-on-neighbor-failure

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

hold-on-neighbor-failure

Syntax

hold-on-neighbor-failure multiplier

no hold-on-neighbor-failure

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

hold-on-neighbor-failure

Syntax

hold-on-neighbor-failure multiplier

no hold-on-neighbor-failure

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

hold-set

hold-set

Syntax

hold-set seconds

no hold-set

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

hold-time

hold-time

Syntax

hold-time seconds

no hold-time

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

hold-time

Syntax

hold-time seconds

hold-time [days days] [ hrs hrs] [min min] [sec sec]

no hold-time

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

hold-time

Syntax

hold-time [hrs hours] [min minutes] [sec seconds]

no hold-time

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

hold-time

Syntax

hold-time infinite

hold-time [time]

no hold-time

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

hold-time

Syntax

hold-time time

no hold-time

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

hold-time

Syntax

hold-time infinite

hold-time seconds

no hold-time

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

hold-time

Syntax

hold-time hold-time

no hold-time

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

hold-time

Syntax

hold-time time-value

no hold-time

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

hold-time

Syntax

hold-time {[up hold-time- up] [down hold-time-down] [seconds | centiseconds]}

no hold-time

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

hold-time

Syntax

hold-time {[up hold-time- up] [down hold-time-down]}

no hold-time

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.

Note:

For APS configurations, the hold-time down and up default values are 100 ms and 500 ms respectively. If there is a large communication delay (time to exchange K1/K2 bytes) between the APS Controllers of the two endpoints of an APS link, it is highly suggested to increase the default hold-time down timer on the APS group port accordingly with the communication delay. See the config>port aps command for more information.

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

hold-time

Syntax

hold-time {[up hold-time-up] [ down hold-time-down]}

no hold-time

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

hold-time

Syntax

hold-time down hold-down-time

no hold-time

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

hold-time

Syntax

hold-time value

no hold-time

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

hold-time

Syntax

hold-time seconds

no hold-time

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

hold-time

Syntax

hold-time

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

hold-time

Syntax

hold-time seconds [min seconds2]

no 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

hold-time

Syntax

hold-time

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

hold-time

Syntax

hold-time seconds [min seconds]

no hold-time

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

hold-time-aps

hold-time-aps

Syntax

hold-time-aps [lsignal-failure sf-time] [ lsignal-degrade sd-time]

no hold-time-aps

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

hold-time-down

hold-time-down

Syntax

hold-time-down timer

no hold-time-down

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

hold-time-up

hold-time-up

Syntax

hold-time-up timer

no hold-time-up

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

hold-timer

hold-timer

Syntax

hold-timer seconds

no hold-timer

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

holddown

holddown

Syntax

[no] holddown [neighbor ip-int-name | ip-address]

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

holddown

Syntax

[no] holddown [neighbor ip-int-name | ipv6-address]

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

holdtime

holdtime

Syntax

holdtime holdtime

no holdtime

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

holdtime

Syntax

holdtime holdtime

no holdtime

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

home

home

Syntax

home bit [bit]

no home

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

home-directory

home-directory

Syntax

home-directory url-prefix [directory] [directory/directory]

no home-directory

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

Note:

If restricted-to-home has been configured no file access is granted and no home-directory is created. If restricted-to-home is not applied then root becomes the user’s 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

hop

hop

Syntax

hop hop-index ip-address {strict | loose}

hop hop-index sid-label sid-value

no hop hop-index

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

hop

Syntax

hop hop-index ip-address

no hop hop-index

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

hop-by-hop-opt

hop-by-hop-opt

Syntax

hop-by-hop-opt {true | false}

no hop-by-hop-opt

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

hop-by-hop-opt

Syntax

hop-by-hop-opt {true | false}

no hop-by-hop-opt

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

hop-limit

hop-limit

Syntax

hop-limit limit

no hop-limit

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

hop-limit

Syntax

hop-limit number

no hop-limit

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

hop-limit

Syntax

hop-limit number

no hop-limit

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

hop-limit

Syntax

hop-limit {lt | gt | eq} hop-limit-value

hop-limit range hop-limit-value hop-limit-value

no hop-limit

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

host

host

Syntax

host host-name [create]

no host host-name

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

host

Syntax

[no] host [ip-address]

[no] host [fwd-service service-id] group-interface ip-int-name

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

host-accounting

host-accounting

Syntax

[no] host-accounting [interim-update]

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

host-connectivity-verify

host-connectivity-verify

Syntax

host-connectivity-verify source-ip ip-address [ source-mac ieee-address] [interval interval] [ action {remove | alarm}] [timeout retry-timeout] [retry-count count]

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

host-connectivity-verify

Syntax

host-connectivity-verify [interval interval] [ action {remove | alarm}] [timeout retry-timeout] [retry-count count] [family family]

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

host-connectivity-verify

Syntax

host-connectivity-verify [source {vrrp | interface}] [interval interval] [action { remove | alarm}] [timeout retry-timeout] [retry-count retry-count]

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

host-connectivity-verify

Syntax

[no] host-connectivity-verify

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

host-connectivity-verify

Syntax

host-connectivity-verify service service-id [ sap sap-id]

host-connectivity-verify subscriber sub-ident-string [ sla-profile sla-profile-name]

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

host-identification

host-identification

Syntax

host-identification

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

host-ip

host-ip

Syntax

host-ip prefix-list-name

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

host-key

host-key

Syntax

host-key {mac}

no host-key

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

host-limit

host-limit

Syntax

host-limit max-num-hosts

no host-limit

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

Platforms

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

host-limit

Syntax

host-limit max-num-hosts

no host-limit

Context

[Tree] (config>service>ies>sub-if>grp-if host-limit)

Full Context

configure service ies subscriber-interface group-interface host-limit

Description

This command configures the maximum number of ARP hosts.

Parameters

max-num-hosts

Specifies the maximum number of ARP hosts.

Values

1 to 32767

Platforms

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

host-limits

host-limits

Syntax

[no] no host-limits

Context

[Tree] (config>subscr-mgmt>sla-profile host-limits)

[Tree] (config>subscr-mgmt>sub-profile host-limits)

Full Context

configure subscriber-mgmt sla-profile host-limits

configure subscriber-mgmt sub-profile host-limits

Description

Commands in this context configure host limits per SLA profile instance or per subscriber.

The no form of this command removes the host limit configuration.

Platforms

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

host-lockout-policy

host-lockout-policy

Syntax

host-lockout-policy policy-name

no host-lockout-policy

Context

[Tree] (config>service>vprn>if>sap host-lockout-policy)

[Tree] (config>service>vprn>sub-if>grp-if>sap host-lockout-policy)

[Tree] (config>service>ies>if>sap host-lockout-policy)

[Tree] (config>service>vpls>sap host-lockout-policy)

[Tree] (config>service>ies>sub-if>grp-if>sap host-lockout-policy)

Full Context

configure service vprn interface sap host-lockout-policy

configure service vprn subscriber-interface group-interface sap host-lockout-policy

configure service ies interface sap host-lockout-policy

configure service vpls sap host-lockout-policy

configure service ies subscriber-interface group-interface sap host-lockout-policy

Description

This command selects an existing host lockout policy. The host-lockout-policy policy-name is created in the config>subscr-mgmt context.

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

Parameters

policy-name

Specifies an existing host lockout policy, up to 32 characters, to associate with the SAP.

Platforms

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

host-lockout-policy

Syntax

host-lockout-policy policy-name [create]

no host-lockout-policy policy-name

Context

[Tree] (config>subscr-mgmt host-lockout-policy)

Full Context

configure subscriber-mgmt host-lockout-policy

Description

This command creates a host lockout policy. The policy contains set of host lockout configuration parameters. It is applied to SAP or MSAPs (by a MSAP-policy). Any change does not impact existing locked-out hosts, but only new incoming hosts that enter lockout.

The no form of this command removes the policy name from the configuration. The policy must not be associated with any entity.

Parameters

policy-name

Specifies an existing host lockout policy to associate with the SAP.

create

Specifies the keyword required to create the host lockout policy. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

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

host-match

host-match

Syntax

host-match dest destination-string [create]

no host-match dest destination-string

Context

[Tree] (config>port>ethernet>access>egr>qgrp host-match)

Full Context

configure port ethernet access egress queue-group host-match

Description

This command configures host matching for the Ethernet port egress queue-group.

The no form of this command removes the destination string from the configuration.

Parameters

destination-string

Specify a host match destination string up to 32 characters.

create

Keyword used to create the host match. The create keyword requirement can be enabled or disabled in the environment>create context.

Platforms

All

host-match

Syntax

host-match dest description-string [create]

no host-match dest destination-string

Context

[Tree] (config>port>ethernet>access>egress>vport host-match)

Full Context

configure port ethernet access egress vport host-match

Description

This command specifies the destination and organization strings to be used for matching subscriber hosts with this Vport.

The parent Vport of a subscriber host queue, which has the port-parent option enabled, is determined by matching the destination string dest string associated with the subscriber and the organization string org string associated with the subscriber host with the strings defined under a Vport on the port associated with the subscriber.

If a given subscriber host queue does not have the port-parent option enabled, it will be foster-parented to the Vport used by this subscriber and which is based on matching the dest string and org string. If the subscriber could not be matched with a Vport on the egress port, the host queue will not be bandwidth controlled and will compete for bandwidth directly based on its own PIR and CIR parameters.

By default, a subscriber host queue with the port-parent option enabled is scheduled within the context of the port’s port scheduler policy.

Parameters

description-string

The destination character string. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

Platforms

All

host-port

host-port

Syntax

[no] host-port port-id

Context

[Tree] (config>esa host-port)

Full Context

configure esa host-port

Description

This command configures an Ethernet port associated to the ESA instance.

The no form of this command removes the host-port.

Parameters

port-id

Specifies the port identifier of any valid Ethernet port on a supported IOM.

Values

slot/mda/port

Platforms

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

host-port

Syntax

host-port port-id

no host-port

Context

[Tree] (config>esa>vm host-port)

Full Context

configure esa vm host-port

Description

This command configures an Ethernet port associated to an ESA-VM instance. The port-id used must be the same as the port associated with the ESA context on which the ESA-VM is configured.

The no form of this command removes the specified host-port for the ESA-VM instance.

Parameters

port-id

Specifies the port identifier of any valid Ethernet port ID on the supported IOM.

Values

slot/mda/port

Platforms

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

host-shutdown

host-shutdown

Syntax

[no] host-shutdown

Context

[Tree] (config>service>ies>if>sap host-shutdown)

Full Context

configure service ies interface sap host-shutdown

Description

This command administratively enables host creation on this SAP.

Platforms

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

host-shutdown

Syntax

[no] host-shutdown

Context

[Tree] (config>service>vprn>if>sap host-shutdown)

Full Context

configure service vprn interface sap host-shutdown

Description

This command administratively enables host creation on this SAP.

Platforms

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

host-tracking-policy

host-tracking-policy

Syntax

host-tracking-policy policy-name [create]

no host-tracking-policy policy-name

Context

[Tree] (config>subscr-mgmt>sub-prof host-tracking-policy)

[Tree] (config>subscr-mgmt host-tracking-policy)

Full Context

configure subscriber-mgmt sub-profile host-tracking-policy

configure subscriber-mgmt host-tracking-policy

Description

This command configures a host tracking policy. IGMP host tracking is an option in the subscriber profile that allows the factoring in of a subscriber’s (multicast) video traffic by reducing the unicast operational egress aggregate rate or the rate of the scheduler specified in the ANCP policy to account for a subscriber’s multicast traffic. If no ANCP policy is defined, the egress aggregate rate configured in the subscriber profile is reduced. If an ANCP policy is defined, the rate-modify command in the policy specifies whether the egress aggregate rate or the rate of the egress policer specified in the policy is to be reduced to account for the subscriber’s multicast traffic.

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

Parameters

policy-name

Specifies a host tracking policy name up to 32 characters.

Platforms

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

host-unreachable

host-unreachable

Syntax

[no] host-unreachable ip-address

[no] host-unreachable ipv6-address

Context

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

Full Context

configure vrrp policy priority-event host-unreachable

Description

This command creates the context to configure a host unreachable priority control event to monitor the ability to receive ICMP echo reply packets from an IP host address.

A host unreachable priority event creates a continuous ICMP echo request (ping) probe to the specified ip-address. If a ping fails, the event is considered to be set. If a ping is successful, the event is considered to be cleared.

Multiple unique (different ip-address) host-unreachable event nodes can be configured within the priority-event node to a maximum of 32 events.

The host-unreachable command can reference any valid local or remote IP address. The ability to ARP a local IP address or find a remote IP address within a route prefix in the route table is considered part of the monitoring procedure. The host-unreachable priority event operational state tracks ARP or route table entries dynamically appearing and disappearing from the system. The operational state of the host-unreachable event are listed in Host Unreachable Operational States.

Table 2. Host Unreachable Operational States

Host Unreachable Operational State

Description

Set – no ARP

No ARP address found for ip-addr for drop-count consecutive attempts; only applies when IP address is considered local

Set – no route

No route exists for ip-addr for drop-count consecutive attempts; only when IP address is considered remote

Set – host unreachable

ICMP host unreachable message received for drop-count consecutive attempts

Set – no reply

ICMP echo request timed out for drop-count consecutive attempts

Set – reply received

Last ICMP echo request attempt received an echo reply but historically not able to clear the event

Cleared – no ARP

No ARP address found for ip-addr - not enough failed attempts to set the event

Cleared – no route

No route exists for ip-addr - not enough failed attempts to set the event

Cleared – host unreachable

ICMP host unreachable message received - not enough failed attempts to set the event

Cleared – no reply

ICMP echo request timed out - not enough failed attempts to set the event

Cleared – reply received

Event is cleared - last ICMP echo request received an echo reply

Unlike other priority event types, the host-unreachable priority event monitors a repetitive task. A historical evaluation is performed on the success rate of receiving ICMP echo reply messages. The operational state takes its cleared and set orientation from the historical success rate. The informational portion of the operational state is derived from the last attempt’s result. It is possible for the previous attempt to fail while the operational state is still cleared due to an insufficient number of failures to cause it to become set. It is also possible for the state to be set while the previous attempt was successful.

When an event transitions from clear to set, the set is processed immediately and must be reflected in the associated virtual router instances in-use priority value. As the event transitions from clear to set, a hold-set timer is loaded with the value configured by the events hold-set command. This timer prevents the event from clearing until it expires, damping the effect of event flapping. If the event clears and becomes set again before the hold-set timer expires, the timer is reset to the hold-set value, extending the time before another clear can take effect.

The hold-set timer be expired and the historical success rate must be met prior to the event operational state becoming cleared.

The no form of the command deletes the specific IP host monitoring event. The event may be deleted at any time. When the event is deleted, the in-use priority of all associated virtual router instances must be reevaluated. The event’s hold-set timer has no effect on the removal procedure.

Default

no host-unreachable — No host unreachable priority events are created.

Parameters

ip-address

The IP address of the host for which the specific event will monitor connectivity. The ip-addr can only be monitored by a single event in this policy. The IP address can be monitored by multiple VRRP priority control policies. The IP address can be used in one or multiple ping requests. Each VRRP priority control host-unreachable and ping destined to the same ip-addr is uniquely identified on a per message basis. Each session originates a unique identifier value for the ICMP echo request messages it generates. This allows received ICMP echo reply messages to be directed to the appropriate sending application.

Values

The following values apply to the 7450 ESS:

ipv4-address: a.b.c.d

Values

The following values apply to the 7750 SR and 7950 XRS:

ipv4-address:

a.b.c.d

ipv6-address:

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

x:

[0..FFFF]H

interface:

32 chars maximum, mandatory for link local addresses

The link-local IPv6 address must have an interface name specified. The global IPv6 address must not have an interface name specified.

Platforms

All

host-unsolicited-na-flood-evpn

host-unsolicited-na-flood-evpn

Syntax

[no] host-unsolicited-na-flood-evpn

Context

[Tree] (config>service>vpls>proxy-nd host-unsolicited-na-flood-evpn)

Full Context

configure service vpls proxy-nd host-unsolicited-na-flood-evpn

Description

This command controls whether the system floods host unsolicited Neighbor Advertisements to the EVPN. The NA messages impacted by this command are NA messages with the following flags: S=0 and R=0.

The no form of the command will only flood to local SAPs/binds but not to the EVPN destinations. This is only recommended in networks where CEs are routers that are directly connected to the PEs. Networks using aggregation switches between the host/routers and the PEs should flood unsolicited NA messages in the EVPN to ensure that the remote caches are updated and the BGP does not miss the advertisement of these entries.

Default

host-unsolicited-na-flood-evpn

Platforms

All

hour

hour

Syntax

hour hour-number [..hour-number] | all}

no hour

Context

[Tree] (config>system>cron>sched hour)

Full Context

configure system cron schedule hour

Description

This command specifies which hour to schedule a command. Multiple hours of the day can be specified. When multiple hours are configured, each of them will cause the schedule to trigger. Day-of-month or weekday must also be specified. All days of the month or weekdays can be specified. If an hour is configured without configuring month, weekday, day-of-month, and minute, the event will not execute.

The no form of this command removes the specified hour from the configuration.

Default

no hour

Parameters

hour-number

Specifies the hour to schedule a command.

Values

0 to 23 (maximum 24 hour-numbers)

all

Specifies all hours.

Platforms

All

hqos-algorithm

hqos-algorithm

Syntax

hqos-algorithm {default | above-offered-allowance-control}

no hqos-algorithm

Context

[Tree] (config>qos>port-scheduler-policy hqos-algorithm)

Full Context

configure qos port-scheduler-policy hqos-algorithm

Description

This command configures the port scheduler H-QoS algorithm used to calculate the operational rates for the children connected to the port scheduler. The algorithm can be changed on the fly.

Default

default

Parameters

default

Specifies that the default H-QoS algorithm is used by the port scheduler.

above-offered-allowance-control

Enables the control of the amount of bandwidth in excess of the offered rate to be given to a queue or scheduler. This algorithm is supported when only queues and schedulers are parented to the port scheduler on Ethernet Vports or Ethernet physical ports.

Platforms

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

hqos-mode

hqos-mode

Syntax

hqos-mode {port-scheduler | hw-agg-shaping}

Context

[Tree] (config>qos>fp-resource-policy>ports hqos-mode)

Full Context

configure qos fp-resource-policy ports hqos-mode

Description

This command configures the default HQoS mode for ports on the specified FP.

Default

hqos-mode port-scheduler

Parameters

port-scheduler

Specifies that the default HQoS mode is port scheduler.

hw-agg-shaping

Specifies that the default HQoS mode is hardware aggregate shaping.

Platforms

7750 SR-1, 7750 SR-s

hs-agg-rate-limit

hs-agg-rate-limit

Syntax

hs-agg-rate-limit kilobits-per-second

no hs-agg-rate-limit

Context

[Tree] (config>subscr-mgmt>sla-profile>egress hs-agg-rate-limit)

Full Context

configure subscriber-mgmt sla-profile egress hs-agg-rate-limit

Description

This command configures high scale (HS) aggregate rate limit of the SLA profile instance (SPI) associated with the subscriber in expanded SLA mode. The aggregate rate of the subscriber (the primary shaper) is configured in the config>subscr-mgmt>sub-profile>egress>hs-agg-rate-limit context.

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

Parameters

kilobits-per-second

Specifies the HS egress aggregate rate limit.

Values

1 to 100000000

Platforms

7750 SR-7/12/12e

hs-agg-rate-limit

Syntax

hs-agg-rate-limit kilobits-per-second [min-resv-bw min-rate]

hs-agg-rate-limit max [min-resv-bw min-rate]

no hs-agg-rate-limit

Context

[Tree] (config>subscr-mgmt>sub-profile>egress hs-agg-rate-limit)

Full Context

configure subscriber-mgmt sub-profile egress hs-agg-rate-limit

Description

This command configures the HS aggregate rate limit for the subscriber in single SLA mode. In single SLA mode, the hs-aggregate-rate-limit command under the config>subscr-mgmt>sla-profile context should not be configured.

When both, sub-profile>egress>hs-agg-rate-limit and sla-profile>egress>hs-agg-rate-limit are configured, the system takes the minimum of the two to program the subscriber’s aggregate rate.

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

Parameters

kilobits-per-second

Specifies the HS egress aggregate rate limit.

Values

1 to 100000000

min-rate

Specifies the minimum rate of the minimum reserved bandwidth for unicast data traffic. Since minimum rate can oversubscribe subscriber bandwidth to guarantee a minimum bandwidth for unicast traffic, care must be taken in QoS provisioning to prioritize packets accordingly (downstream network elements such as the access node or aggregation nodes) when congestion occurs.

Values

0 to 100000000

max

Specifies that the egress aggregate rate limit for the subscriber is unlimited. Scheduling for the subscriber queues will only be governed by the individual queue parameters and any congestion on the port relative to each queues scheduling priority.

Platforms

7750 SR-7/12/12e

hs-alt-port-class-pool

hs-alt-port-class-pool

Syntax

[no] hs-alt-port-class-pool

Context

[Tree] (config>qos>network-queue>queue hs-alt-port-class-pool)

Full Context

configure qos network-queue queue hs-alt-port-class-pool

Description

This command specifies that the HSQ queue group queues use buffers from the HS alternate port class buffer pool.

The no form of the command reverts to the HSQ queue group queues using buffers from HS standard port class pools.

Platforms

7750 SR-7/12/12e

hs-alt-port-class-pool

Syntax

[no] hs-alt-port-class-pool

Context

[Tree] (config>qos>sap-egress>queue hs-alt-port-class-pool)

Full Context

configure qos sap-egress queue hs-alt-port-class-pool

Description

This command specifies that the HSQ queue group queues use buffers from the HS alternate port class buffer pool.

The no form of the command reverts to the HSQ queue group queues using buffers from HS standard port class pools.

Platforms

7750 SR-7/12/12e

hs-alt-port-class-pool

Syntax

[no] hs-alt-port-class-pool

Context

[Tree] (config>qos>qgrps>egr>qgrp>queue hs-alt-port-class-pool)

Full Context

configure qos queue-group-templates egress queue-group queue hs-alt-port-class-pool

Description

This command specifies that the HSQ queue group queues use the class buffers from the HS alternate port class buffer pools.

The no form of the command reverts to the HSQ queue group queues using buffers from HS standard port class pools.

Platforms

7750 SR-7/12/12e

hs-attachment-policy

hs-attachment-policy

Syntax

hs-attachment-policy policy-name [create]

no hs-attachment-policy policy-name

Context

[Tree] (config>qos hs-attachment-policy)

Full Context

configure qos hs-attachment-policy

Description

This command specifies how the queues within an HSQ queue group associated with the SAP egress policy instance, egress queue group instance, or egress network queue policy instance attaches to the HSQ scheduling classes managed by the port scheduler. On the HSQ IOM, eight queues are allocated per egress SAP or subscriber SLA profile instance (SPI), or per egress (access or network) queue group instance, or per egress network port, numbered 1 through 8. The port scheduler maintains six scheduling classes numbered from 1 through 6 (6 being the highest relative priority and 1 being the lowest). The set of eight queues may also be placed into one of two local Weighted Round Robin (WRR) groups which collapse the member queues into a single scheduling class while providing a weighted fair distribution of scheduling opportunities per member. The attachment policy contains the attachment commands that map the queue IDs and WRR groups to the scheduling classes. The attachment policy also defines the mapping of the scheduling classes to the queue’s aggregate shapers low and high burst limit thresholds.

The no form of the command deletes the HS attachment policy from the system, which is only possible if the policy is not being referenced.

Parameters

policy-name

Specifies an existing attachment policy, up to 32 characters. Each HS attachment policy must be uniquely named within the system.

create

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

Platforms

7750 SR-7/12/12e

hs-attachment-policy

Syntax

hs-attachment-policy policy-name

no hs-attachment-policy

Context

[Tree] (config>qos>network-queue hs-attachment-policy)

Full Context

configure qos network-queue hs-attachment-policy

Description

This command associates an existing HS attachment policy with the network queue QoS policy. The HS attachment policy controls how the network queues are attached to scheduler classes or WRR groups, and how WRR groups are attached to the scheduler classes. It also defines the mapping of the scheduling classes to the queues' aggregate shaper's low and high burst limit thresholds.

Only one HS attachment policy can be associated with a network queue policy.

The no form of the command removes the policy name from the configuration and reapplies the default HS attachment policy.

Parameters

policy-name

Specifies an existing attachment policy up, to 32 characters. Each HSQ attachment policy must be uniquely named within the system.

Platforms

7750 SR-7/12/12e

hs-attachment-policy

Syntax

hs-attachment-policy policy-name

no hs-attachment-policy

Context

[Tree] (config>qos>sap-egress hs-attachment-policy)

Full Context

configure qos sap-egress hs-attachment-policy

Description

This command associates an existing HS attachment policy with the SAP egress QoS policy. The HS attachment policy controls how the SAP egress queues are attached to scheduler classes or WRR groups, and how WRR groups are attached to the scheduler classes. It also defines the mapping of the scheduling classes to the queues' aggregate shaper's low and high burst limit thresholds.

Only one HS attachment policy can be associated with a SAP egress policy.

The no form of the command removes the policy name from the configuration and reapplies the default HS attachment policy.

Parameters

policy-name

Specifies an existing attachment policy up, to 32 characters. Each HSQ attachment policy must be uniquely named within the system.

Platforms

7750 SR-7/12/12e

hs-attachment-policy

Syntax

hs-attachment-policy policy-name

no hs-attachment-policy

Context

[Tree] (config>qos>qgrps>egr>qgrp hs-attachment-policy)

Full Context

configure qos queue-group-templates egress queue-group hs-attachment-policy

Description

This command associates an existing HS attachment policy with the egress queue group template. The HS attachment policy controls how the egress queue group instance queues are attached to scheduler classes or WRR groups, and how WRR groups are attached to the scheduler classes. It also defines the mapping of the scheduling classes to the queues' aggregate shaper's low and high burst limit thresholds.

Only one HS attachment policy can be associated with an egress queue group template.

The no form of the command removes the policy name from the configuration and reapplies the default HS attachment policy.

Parameters

policy-name

Specifies an existing attachment policy, up to 32 characters. Each HS attachment policy must be uniquely named within the system.

Platforms

7750 SR-7/12/12e

hs-attachment-policy

Syntax

hs-attachment-policy src-name dst-name [ overwrite]

Context

[Tree] (config>qos>copy hs-attachment-policy)

Full Context

configure qos copy hs-attachment-policy

Description

This command copies existing QoS policy entries for a QoS policy ID to another QoS policy ID.

The copy command is a configuration-level maintenance tool used to create new policies using existing policies. It also allows bulk modifications to an existing policy with the use of the overwrite keyword.

Parameters

src-name dst-name

Indicates that the source policy ID and the destination policy ID are HS policy IDs. Specify the source policy ID that the copy command attempts to copy from and specify the destination policy ID to which the command copies a duplicate of the policy.

overwrite

Specifies to replace the existing destination policy. Everything in the existing destination policy is overwritten with the contents of the source policy. If overwrite is not specified, an error occurs if the destination policy ID exists.

Example:
    — SR>config>qos# copy hs-pool-policy policy1 policy2
    — MINOR: CLI Destination "policy2" exists use {overwrite}.
    — SR>config>qos# copy hs-pool-policy policy1 policy2 overwrite

Platforms

7750 SR-7/12/12e

hs-class-weight

hs-class-weight

Syntax

hs-class-weight weight

no hs-class-weight

Context

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

[Tree] (config>subscr-mgmt>sla-prof>egress>qos>queue hs-class-weight)

Full Context

configure subscriber-mgmt sla-profile egress qos hs-wrr-group hs-class-weight

configure subscriber-mgmt sla-profile egress qos queue hs-class-weight

Description

This command configures the class-weight override for expanded egress HS queues or the WRR group.

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

Parameters

weight

Specifies the weight of the scheduling class.

Values

1, 2, 4, 8

Platforms

7750 SR-7/12/12e

hs-class-weight

Syntax

hs-class-weight weight

no hs-class-weight

Context

[Tree] (config>service>epipe>sap>egress>queue-override>queue hs-class-weight)

[Tree] (config>service>ipipe>sap>egress>queue-override>queue hs-class-weight)

Full Context

configure service epipe sap egress queue-override queue hs-class-weight

configure service ipipe sap egress queue-override queue hs-class-weight

Description

This command overrides the class weight of this queue at its parent primary shaper, relative to the other queues and WRR groups in different HSQ queue groups in the same scheduling class.

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

Parameters

weight

Specifies the weight of the queue.

Values

1, 2, 4, 8

Platforms

7750 SR-7/12/12e

hs-class-weight

Syntax

hs-class-weight weight

no hs-class-weight

Context

[Tree] (config>service>vpls>sap>egress>queue-override>queue hs-class-weight)

Full Context

configure service vpls sap egress queue-override queue hs-class-weight

Description

This command overrides the class weight of this queue at its parent primary shaper, relative to the other queues and WRR groups in different HSQ queue groups in the same scheduling class.

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

Parameters

weight

Specifies the weight of the queue.

Values

1, 2, 4, 8

Platforms

7750 SR-7/12/12e

hs-class-weight

Syntax

hs-class-weight weight

no hs-class-weight

Context

[Tree] (config>service>ies>if>sap>egress>queue-override>queue hs-class-weight)

Full Context

configure service ies interface sap egress queue-override queue hs-class-weight

Description

This command overrides the class weight of this queue at its parent primary shaper, relative to the other queues and WRR groups in different HSQ queue groups in the same scheduling class.

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

Parameters

weight

Specifies the weight of the queue.

Values

1, 2, 4, 8

Platforms

7750 SR-7/12/12e

hs-class-weight

Syntax

hs-class-weight weight

no hs-class-weight

Context

[Tree] (config>service>vprn>if>sap>egress>queue-override>queue hs-class-weight)

Full Context

configure service vprn interface sap egress queue-override queue hs-class-weight

Description

This command overrides the class weight of this queue at its parent primary shaper, relative to the other queues and WRR groups in different HSQ queue groups in the same scheduling class.

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

Parameters

weight

Specifies the weight of the queue.

Values

1, 2, 4, 8

Platforms

7750 SR-7/12/12e

hs-class-weight

Syntax

hs-class-weight weight

no hs-class-weight

Context

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

Full Context

configure qos network-queue hs-wrr-group hs-class-weight

Description

This command specifies the class weight of this WRR group at its parent primary shaper, relative to the other queues and WRR groups in different HSQ queue groups in the same scheduling class. This allows the capacity available at the primary shaper scheduling class to be shared in a WRR manner between the HSQ queue group queues and WRR groups attached to that scheduling class. The hs-class-weight weight can be used to give unequal shares of the available capacity to different types of service offerings.

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

Default

hs-class-weight 1

Parameters

weight

Specifies the class weight of the HS WRR group.

Values

1, 2, 4, 8

Platforms

7750 SR-7/12/12e

hs-class-weight

Syntax

hs-class-weight weight

no hs-class-weight

Context

[Tree] (config>qos>network-queue>queue hs-class-weight)

Full Context

configure qos network-queue queue hs-class-weight

Description

This command specifies the class weight of this queue at its parent primary shaper, relative to the other queues and WRR groups in different HSQ queue groups in the same scheduling class. This allows the capacity available at the primary shaper scheduling class to be shared in a WRR manner between the HSQ queue group queues and WRR groups attached to that scheduling class. The hs-class-weight weight parameter can be used to give unequal shares of the available capacity to different types of service offerings. This command is ignored for egress HSQ queue group queues that are attached to an HS WRR group within an associated HS attachment policy. In this case, the configuration of the hs-class-weight is performed under the hs-wrr-group within the network queue policy.

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

Default

hs-class-weight 1

Parameters

weight

Specifies class weight of the queue.

Values

1, 2, 4, 8

Platforms

7750 SR-7/12/12e

hs-class-weight

Syntax

hs-class-weight weight

no hs-class-weight

Context

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

Full Context

configure qos sap-egress hs-wrr-group hs-class-weight

Description

This command specifies the class weight of this WRR group at its parent primary shaper, relative to the other queues and WRR groups in different HSQ queue groups in the same scheduling class. This allows the capacity available at the primary shaper scheduling class to be shared in a WRR manner between the HSQ queue group queues and WRR groups attached to that scheduling class. The hs-class-weight parameter can be used to give unequal shares of the available capacity to different types of service offerings.

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

Default

hs-class-weight 1

Parameters

weight

Specifies the class weight of the HS WRR group.

Values

1, 2, 4, 8

Platforms

7750 SR-7/12/12e

hs-class-weight

Syntax

hs-class-weight weight

no hs-class-weight

Context

[Tree] (config>qos>sap-egress>queue hs-class-weight)

Full Context

configure qos sap-egress queue hs-class-weight

Description

This command specifies the class weight of this queue at its parent primary shaper, relative to the other queues and WRR groups in different HSQ queue groups in the same scheduling class. This allows the capacity available at the primary shaper scheduling class to be shared in a WRR manner between the HSQ queue group queues and WRR groups attached to that scheduling class. The hs-class-weight weight parameter can be used to give unequal shares of the available capacity to different types of service offerings. This command is ignored for egress HSQ queue group queues, which are attached to an HS WRR group within an associated HS attachment policy. In this case, the configuration of the hs-class-weight is performed under the hs-wrr-group within the network queue policy.

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

Default

hs-class-weight 1

Parameters

weight

Specifies class weight of the queue.

Values

1, 2, 4, 8

Platforms

7750 SR-7/12/12e

hs-class-weight

Syntax

hs-class-weight weight

no hs-class-weight

Context

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

Full Context

configure qos queue-group-templates egress queue-group hs-wrr-group hs-class-weight

Description

This command specifies the class weight of this WRR group at its parent primary shaper, relative to the other queues and WRR groups in different HSQ queue groups in the same scheduling class. This allows the capacity available at the primary shaper scheduling class to be shared in a WRR manner between the HSQ queue group queues and WRR groups attached to that scheduling class. The hs-class-weight parameter can be used to give unequal shares of the available capacity to different types of service offerings.

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

Default

hs-class-weight 1

Parameters

weight

Specifies the class weight of the HS WRR group.

Values

1, 2, 4, 8

Platforms

7750 SR-7/12/12e

hs-class-weight

Syntax

hs-class-weight weight

no hs-class-weight

Context

[Tree] (config>qos>qgrps>egr>qgrp>queue hs-class-weight)

Full Context

configure qos queue-group-templates egress queue-group queue hs-class-weight

Description

This command specifies the class weight of this queue at its parent primary shaper, relative to the other queues and WRR groups in different HSQ queue groups in the same scheduling class. This allows the capacity available at the primary shaper scheduling class to be shared in a WRR manner between the HSQ queue group queues and WRR groups attached to that scheduling class. The hs-class-weight parameter can be used to give unequal shares of the available capacity to different types of service offerings.

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

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

Default

hs-class-weight 1

Parameters

weight

Specifies the class weight of the queue.

Values

1, 2, 4, 8

Platforms

7750 SR-7/12/12e

hs-fixed-high-thresh-delta

hs-fixed-high-thresh-delta

Syntax

hs-fixed-high-thresh-delta size-in-bytes

no hs-fixed-high-thresh-delta

Context

[Tree] (config>card>fp>egress hs-fixed-high-thresh-delta)

Full Context

configure card fp egress hs-fixed-high-thresh-delta

Description

This command specifies the egress aggregate shaper high burst limit threshold delta for this HSQ IOM FP. An aggregate rate can be applied to each egress HSQ queue group, HS secondary shaper and (for subscribers configured with HS SLA expanded mode) primary shaper which manages the maximum burst limit over a specified shaping rate. Each aggregate shaper supports two thresholds which are used in conjunction with the low burst class setting. The system utilizes the lowest value attainable for each low threshold aggregate burst limit without causing shaper under run conditions. The high burst limit threshold is determined by adding the configured value of this command to the aggregate’s low burst limit threshold value. This configured value should be set to at least two times the maximum frame size to prevent lower threshold class forwarding from also affecting the higher threshold classes when forwarding larger packet sizes. An insufficient high threshold delta defeats the intended purpose of mapping classes to the higher threshold.

The configured value for this command can be changed at any time. Modifying the setting causes all aggregate shapers on this FP to reconfigure the low and high burst limit thresholds to reflect the new value.

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

Default

hs-fixed-high-thresh-delta 4000

Parameters

size-in-bytes

Specifies high threshold data in bytes.

Values

0 to 65536

Platforms

7750 SR-7/12/12e

hs-low-burst-max-class

hs-low-burst-max-class

Syntax

hs-low-burst-max-class class

no hs-low-burst-max-class

Context

[Tree] (config>subscr-mgmt>sub-prof>egress hs-low-burst-max-class)

Full Context

configure subscriber-mgmt sub-profile egress hs-low-burst-max-class

Description

This command specifies which scheduling classes map to the low burst limit threshold of an egress HS primary shaper. The HS primary shaper is used to manage aggregate bandwidth of the subscriber with multiple SLA profile instances (expanded SLA mode).

Each HS primary shaper supports two burst thresholds, a low burst limit threshold and a high burst limit threshold. The two thresholds allow separation of burstiness between low and high scheduling classes.

When the low burst threshold of the HS primary shaper is reached, the lower scheduling classes, up to the scheduling class configured by this command, stops being served. Traffic on higher scheduling classes still goes through until the high burst threshold is reached. When the high burst threshold is exceeded, all scheduling classes associated with the HS primary shaper and stops being serve, which effectively shuts off the traffic flow.

Typically, the queues associated with higher scheduling classes are individually rate-limited so that their aggregate allowed throughput is less than the configured rate of the HS primary shaper. Determining the hs-low-burst-max-class class value involves anticipating the proper dividing line between the low and high scheduling classes by evaluating the forwarding behavior and SLA enforcement of each class.

By default, all scheduling classes are mapped to the low burst limit threshold. When mapping scheduling classes to the high burst limit threshold, an adequate value for the config>card>fp>egress>hs-fixed-high-thresh-delta should be specified (by default, it is set to 4000 bytes). This is because the queues associated with the lower scheduling classes may burst over the lower threshold during normal operation due to the scheduler forwarding whole packets. The hs-fixed-high-thresh-delta value should be set to at least two times the maximum frame size to prevent lower threshold class forwarding from also affecting the higher threshold classes when forwarding larger packet sizes. An insufficient high threshold delta defeats the intended purpose of mapping classes to the higher threshold.

The system uses the lowest value attainable for each low threshold aggregate burst limit without causing shaper underrun conditions. The high burst limit threshold is determined by adding the hs-fixed-high-thresh-delta value to the aggregate low burst limit threshold value.

The hs-low-burst-max-class value for HS primary shaper can be changed at any time in the subscriber profile (sub-profile).

The no form of this command restores the low burst limit threshold of the scheduling classes to the default value. This causes all scheduling classes associated with the HS primary shaper to be mapped to the low burst limit threshold.

Default

hs-low-burst-max-class 6

Parameters

class

Specifies the highest scheduling class that is associated with the low burst limit threshold of the HS primary shaper. Scheduling classes that are higher than the scheduling class ID are associated with the high burst limit threshold.

Values

1 to 6

Platforms

7750 SR-7/12/12e

hs-mbs

hs-mbs

Syntax

hs-mbs percent-of-queue-rate

no hs-mbs

Context

[Tree] (config>qos>network-queue>queue hs-mbs)

Full Context

configure qos network-queue queue hs-mbs

Description

This command configures the queue size of an HSQ queue group network queue. Its value is calculated based on the specified percentage of one second of the queue PIR converted to bytes (the regular mbs parameter is ignored in the network queue policy).

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

Default

hs-mbs 100

Parameters

percent-of-queue-rate

Specifies the buffer space for the queue as a percentage of its PIR (in bytes).

Values

0.00 to 100.0

Platforms

7750 SR-7/12/12e

hs-pool-policy

hs-pool-policy

Syntax

hs-pool-policy name

no hs-pool-policy

Context

[Tree] (config>card>fp>egress hs-pool-policy)

Full Context

configure card fp egress hs-pool-policy

Description

This command specifies the HS pool policy for this FP.

An HS pool policy contains the required parameters to create and size root and mid-tier buffer pools on an HSQ IOM, and apply a slope policy to each.

A single HS pool policy is supported per port FP. This command is only applicable to the HSQ IOM (iom4-e-hs) and will fail if configured on all other card types.

The no form of this command removes the policy and reapplies the default policy.

Default

hs-pool-policy default

Parameters

name

Specifies the HS pool policy name, up to 32 characters.

Platforms

7750 SR-7/12/12e

hs-pool-policy

Syntax

hs-pool-policy policy-name [create]

no hs-pool-policy policy-name

Context

[Tree] (config>qos hs-pool-policy)

Full Context

configure qos hs-pool-policy

Description

Commands in this context create HS pool policy parameters. The policy can be assigned to an egress forwarding plane of an HSQ IOM. The policy contains the required parameters to create and size root and mid-tier buffer pools on an HSQ IOM, and apply a slope policy to each. The HS pool policy can be applied using the hs-pool-policy command within the config>card>fp fp-number egress context.

The system supports 63 HS pool policies including the default HS pool policy.

  • HSQ IOM System Reserved Buffers — The HSQ IOM maintains two types of queues; provisioned queues and system reserved queues. The HSQ IOM ensures that provisioned queues cannot consume buffers that must be available for internal system queues required for correct operating behavior. To prevent buffer starvation between the two types of queues, the system divides the available buffers into two portions. The first portion is given to system root pools and is allocated to HSQ queues reserved for internal functions. The second portion is given to the provisioned or user-defined root pools and is available for egress service queues, network queues, queue-group queues or subscriber queues. By default, 5% of the total buffers available are given to the system root pools leaving 95% for the provisioned root pools.

    The default separation between the system and the provisioned root pools can be overridden using the system-reserve command.

  • Root Pools — Root pools are the buffer pools at the bottom of the buffer allocation hierarchy. Two sets of root pools exist: the system root pools and the provisioned root pools. The system root pools cannot be managed by the HS pool policy; only the total number of buffers given to the system root pools can be adjusted by using the system-reserve command.

    The HS pool policy manages sixteen provisioned root pools defined under the root-tier context and specified as root-pool 1 through 16. Each root pool accepts a weight command that defines the relative quantity of buffers that are allocated to each root pool. Root pools are deactivated by defining a weight equal to 0. Root pools with a non-zero weight are sized based on the pool’s weight divided by the sum of all root pool weights, multiplied by the available buffer space. In this manner, all buffers not reserved for system use are distributed between the provisioned root pools without oversubscription. The lack of oversubscription prevents buffer starvation between the root pools allowing root pools, to act as protected buffer space between different types of traffic (best-effort, expedited, or real-time). Root pools allocate buffers to the FP-level mid-tier pools.

  • Mid-Tier Pools — Mid-tier pools are the buffer pools that act as aggregators for port-class pools. Multiple mid-tier pools can be mapped to a single root pool and each mid-tier pool is assigned a percentage of that root pool’s buffer space. The sum of the percentages may exceed 100%, allowing for oversubscription of the root pool’s buffer space. Due to statistical multiplexing principles, oversubscribing the root pool’s buffer allocation may allow more efficient use of the available buffers as not all mid-tier pools are expected to use their fair share simultaneously. Examples of a multiple mid-tier pool application are multiple assured forwarding (AF) or best-effort classes being grouped together in the same root pool. The HS pool policy manages the sixteen mid-tier pools on an HSQ IOM, defined under the mid-tier context and specified as mid-pool 1 through 16.

  • Port Class Pools — The HSQ IOM maintains two sets of scheduler class pools per port: a standard (or default) set and an alternate set. Each set contains six pools, one for each scheduler class serviced by the HSQ IOM port scheduler. Each queue or WRR group is mapped to a scheduling class based on the HS attachment policy defined within the policy or template used to create the queue. Within the SAP egress policy, network queue policy and egress queue group template, an alt-port-class-pool command specifies whether the queues created through the policy use the standard or alternate set of port class pools on the physical port. Further, the scheduling class servicing the queue defines which port-class pool (1 through 6) within the set allocate buffers to the queue.

    Port-class pools are defined within the hs-port-pool-policy, which is applied to each physical port. Further information on HSQ IOM port-class pools is contained in the HS port pool policy section.

  • HSQ Stable Pool Sizing Equivalency — Stable pool sizing is a feature supported on ingress and on non-HSQ egress forwarding planes. By default, the system tries to make all buffers available to active ports (provisioned and equipped). This leads to a condition where an IOM may have only a single MDA populated and the users on that MDA receive all available buffers. At a later date, the second MDA can be populated, causing the buffer space to be fragmented between the users on each MDA. The users on the earlier populated MDA may perceive a degradation in service based on the change in available buffers. The stable pool sizing feature mitigates this potential issue by segregating the buffer space per MDA.

    The HSQ IOM can be made to operate in this stable buffer allocation mechanism by utilizing per-MDA buffer pools. This is accomplished by performing the following steps:

    1. Create two sets of root-pools and two sets of mid-pools in the hs-pool-policy applied to the IOM’s FP egress CLI context. The first set of mid-pools should be parented to the first set of root-pools. The second set of mid-pools should be parented to the second set of root-pools.

    2. Create two distinct HS port pool policies. One is applied to the ports on the first MDA and has the port-class pools parented to the first set of mid-tier pools from the FP level policy. The second HS port pool policy is applied to the ports on the second MDA (when it is provisioned) and has the port-class pools parented to the second set of mid-tier pools from the FP level policy. This provides deterministic pool sizing independent of MDA equipping events.

    3. Configure further control at the port-class level by utilizing explicit-percent based port-class pool sizing, which eliminates the effect of changing port states, including bandwidth changes.

  • HSQ Queue Buffer Allocation — As each packet arrives at an HSQ queue, the queue must obtain buffers to admit the packet on the queue. The queue first checks the depth of the queue relative to the packet’s congestion priority (based on the in, out, or exceed profile) to determine if the packet should be discarded based on early congestion detection or based on the MBS threshold. If the packet is allowed into the queue, the HSQ IOM continues to determine buffer availability using checks to the queue’s port-class pool, the port-class pool’s mid-tier pool, and the mid-tier pool’s root pool. The same RED slope type used at the queue (high, low, or exceed) is used within each buffer pool. If a buffer is available, the buffer can be allocated, and given to the queue.

  • Default HSQ Pool Policy — An HSQ pool policy with the name default always exists on the system and does not need to be created. The default pool policy cannot be changed and is used by all HSQ IOMs within the system unless an explicitly created hs-pool-policy is associated with a forwarding plane.

    The default policy contains the following parameters:

    system-reserve: 5%

    root-pool 1

    allocation-weight: 75

    slope-policy: _tmnx_hs_default

    root-pool 2

    allocation-weight: 25

    slope-policy: _tmnx_hs_default

    root-pool 3 to 16

    allocation-weight: 0

    slope-policy: _tmnx_hs_default

    mid-pool 1

    parent-root-pool: 1

    allocation-percent: 40%

    slope-policy: _tmnx_hs_default

    mid-pool 2

    parent-root-pool: 1

    allocation-percent: 35%

    slope-policy: _tmnx_hs_default

    mid-pool 3

    parent-root-pool: 1

    allocation-percent: 30%

    slope-policy: _tmnx_hs_default

    mid-pool 4

    parent-root-pool: 1

    allocation-percent: 25%

    slope-policy: _tmnx_hs_default

    mid-pool 5

    parent-root-pool: 2

    allocation-percent: 80%

    slope-policy: _tmnx_hs_default

    mid-pool 6

    parent-root-pool: 2

    allocation-percent: 20%

    slope-policy: _tmnx_hs_default

    mid-pool 7 to 16

    parent-root-pool: None

    allocation-percent: 1%

    slope-policy: _tmnx_hs_default

The no form of the command removes the HS pool policy from the system. If the HS pool policy is currently associated with a forwarding plane, the command fails.

Parameters

policy-name

Specifies pool policy name, up to 32 characters. Each HS pool policy must be uniquely named within the system.

create

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

Platforms

7750 SR-7/12/12e

hs-pool-policy

Syntax

hs-pool-policy src-name dst-name [overwrite]

Context

[Tree] (config>qos>copy hs-pool-policy)

Full Context

configure qos copy hs-pool-policy

Description

This command copies existing QoS policy entries for a QoS policy ID to another QoS policy ID.

The copy command is a configuration-level maintenance tool used to create new policies using existing policies. It also allows bulk modifications to an existing policy with the use of the overwrite keyword.

Parameters

src-name dst-name

Indicates that the source policy ID and the destination policy ID are HS policy IDs. Specify the source policy ID that the copy command attempts to copy from and specify the destination policy ID to which the command copies a duplicate of the policy.

overwrite

Specifies to replace the existing destination policy. Everything in the existing destination policy is overwritten with the contents of the source policy. If overwrite is not specified, an error occurs if the destination policy ID exists.

Example:
    — SR>config>qos# copy hs-pool-policy policy1 policy2
    — MINOR: CLI Destination "policy2" exists use {overwrite}.
    — SR>config>qos# copy hs-pool-policy policy1 policy2 overwrite

Platforms

7750 SR-7/12/12e

hs-port-pool-policy

hs-port-pool-policy

Syntax

hs-port-pool-policy policy-name

no hs-port-pool-policy

Context

[Tree] (config>port>ethernet>egress hs-port-pool-policy)

Full Context

configure port ethernet egress hs-port-pool-policy

Description

This command specifies an HS port pool policy to associate with the port egress.

An HS port buffer pool policy defines and sizes the port-class buffer pools on an HSQ IOM egress port.

A single HS port pool policy is supported per port egress. This command is only applicable to the HSQ IOM (iom4-e-hs) and will fail if configured on all other card types.

The no form of this command removes the policy and reapplies the default policy.

Default

hs-port-pool-policy default

Parameters

policy-name

Specifies the HS port pool policy up to 32 characters.

Platforms

7750 SR-7/12/12e

hs-port-pool-policy

Syntax

hs-port-pool-policy policy-name [create]

no hs-port-pool-policy policy-name

Context

[Tree] (config>qos hs-port-pool-policy)

Full Context

configure qos hs-port-pool-policy

Description

This command creates an HS port buffer pool policy. The policy can be assigned to an egress port on an HSQ IOM. The policy contains the required commands to define and size port-class buffer pools on an HSQ IOM. The policy can be applied using the hs-port-pool-policy command within the config>port>ethernet>egress context.

SR OS supports 2047 HS port pool policies including the default HS port pool policy.

HSQ IOM port buffer pools provide buffer control for queues based on the queue’s scheduling class. Two sets of scheduling class pools exist per port: a standard (or default) set and an alternative set. The SAP egress policy, network queue policy, and egress queue group template have a parameter ( alt-port-class-pool) that specifies that the queues created by the policy or template uses the alternate port-class pools, as opposed to the default standard port-class pools. Each set has six pools, one for each scheduling class. Based on the alt-port-class-pool setting and the queue’s scheduling class (based on the HS attachment policy configuration), each queue is mapped to a specific port-class pool.

The HS port pool policy defines how each of these pools are parented (mapped) to an FP level mid-pool and how each pool is sized.

The system allows two separate mechanisms to size each port-class pool:

  • dynamic sizing based on port bandwidth, relative to bandwidth of other ports

  • explicit sizing based on a percentage of the port-class pool’s parent mid-pool

Dynamic Port-Class Pool Sizing — Dynamic port-class pool sizing is a mechanism that provides a fair share of a mid-pool’s size to each of the port-class pools based on the potential bandwidth represented by each port. To understand port-class pool sizing, consider the following:

  • Each port’s bandwidth is the minimum of the port’s line rate, the port’s configured egress-rate, and the port’s hs-scheduler-policy max-rate.

  • The port’s bandwidth can be further modified by the port’s egr-percentage-of-rate command, which increases or decreases the port’s bandwidth derived by the specified percent. This parameter allows the port to have a higher or lower bandwidth-derived weight based on how the port is actually being used instead of bandwidth alone.

  • Because the port-class pools are user mapped to the mid-pools, not every port has a port-class pool associated with a mid-pool, requiring that the system perform the relative bandwidth calculations separately per mid-pool.

  • Each port’s portion of a specified mid-pool’s size is calculated based on:

    Port_Portion = (Port_Adj_Bw / Sigma_Mid_Pool_Ports_Adj_Bw) * Mid_Pool_Size

    where Sigma_Mid_Pool_Ports_Adj_Bw is the sum of the adjusted bandwidths for all ports with port-class pools mapped to the mid-pool that are not sized using explicit-percent.

  • A port without any port-class pools associated with a given mid-pool has a port portion of zero for that mid-pool.

  • Multiple port-class pools on the same port can be mapped to the same mid-pool, requiring a mechanism to distribute the portion of the mid-pool given to the port between multiple port-class pools. Each mid-pool’s port-bw-weight parameter is used to determine how much of the port’s mid-pool portion is given to each port-class pool associated with mid-pool. Port-class pools sized using an explicit-percent value instead of port bandwidth are assumed to have a port-bw-weight equal to 0, causing those port-class pools to not participate in the port portion distribution. It is expected (but not required) that one of port bandwidth-based sizing or explicit percent-based sizing is used and any concurrent use of both mechanisms is transitory in nature.

  • The port bandwidth weighting mechanism allocates 100% of the mid-pool size to the associated port-class pools. To allow the port-class pools to oversubscribe the parent mid-pool, a mid-pool port-bw-oversub-factor parameter is supported that allows the port-class pools sized by dynamic port bandwidth to increase in size by the specified oversubscription factor. This oversubscription factor can provide a more efficient use of the mid-pool’s available buffers because it is not expected that all port-class pools are utilizing their allotted size simultaneously.

Explicit Port-Class Pool Sizing — The port-class pool’s allocation explicit-percent percent-of-parent-pool command is used to override the dynamic pool sizing mechanism for a given mid-pool. The specified percentage value is applied to the port-class’s parent mid-pool’s size to derive the port-class pool size.

Explicit and Dynamic Sizing from the Same Mid-Pool Parent — If explicit and dynamic pool sizing are used simultaneously for port-class pools parented to the same mid-pool, unexpected contention or underutilization of the mid-pool’s available buffers may result. While this is not a proscribed condition, it is expected most instances of dual-sizing mechanisms are transitory, based on moving between the two mechanisms.

Port-Class Pool Slope Policy Association — The HS port pool policy also provides the ability to specify a slope policy on each port-class pool. The slope policy is used to define the high, low, and exceed slope parameters used to manage contention within the port-class pool.

Default HS Port Pool Policy — An HS port pool policy with the name default always exists on the system and does not need to be created. The default port pool policy cannot be changed and is used by all HSQ IOMs within the system unless an explicitly created hs-port-pool-policy is associated with an HSQ egress port.

The default policy contains the following parameters:

Standard Port-Class Pools

Port-Class-Pool 1

Parent: Mid-Pool 1

Port-Class-Pool 2

Parent: Mid-Pool 2

Port-Class-Pool 3

Parent: Mid-Pool 3

Port-Class-Pool 4

Parent: Mid-Pool 4

Port-Class-Pool 5

Parent: Mid-Pool 5

Port-Class-Pool 6

Parent: Mid-Pool 6

Port-Class-Pool 1 to 6

Port-Bw-Weight: 1

Slope-Policy: _tmnx_hs_default

Alternate Port-Class Pools

Port-Class-Pool 1 to 6

Parent: None

Port-Bw-Weight: 1

Slope-Policy: _tmnx_hs_default

Parameters

policy-name

Specifies an HS port pool policy name up to 32 characters.

create

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

Platforms

7750 SR-7/12/12e

hs-port-pool-policy

Syntax

hs-port-pool-policy src-name dst-name [overwrite]

Context

[Tree] (config>qos>copy hs-port-pool-policy)

Full Context

configure qos copy hs-port-pool-policy

Description

This command copies existing QoS policy entries for a QoS policy ID to another QoS policy ID.

The copy command is a configuration-level maintenance tool used to create new policies using existing policies. It also allows bulk modifications to an existing policy with the use of the overwrite keyword.

Parameters

src-name dst-name

Indicates that the source policy ID and the destination policy ID are HS policy IDs. Specify the source policy ID that the copy command attempts to copy from and specify the destination policy ID to which the command copies a duplicate of the policy.

overwrite

Specifies to replace the existing destination policy. Everything in the existing destination policy is overwritten with the contents of the source policy. If overwrite is not specified, an error occurs if the destination policy ID exists.

Example:
    — SR>config>qos# copy hs-pool-policy policy1 policy2
    — MINOR: CLI Destination "policy2" exists use {overwrite}.
    — SR>config>qos# copy hs-pool-policy policy1 policy2 overwrite

Platforms

7750 SR-7/12/12e

hs-queue-stat-mode

hs-queue-stat-mode

Syntax

hs-queue-stat-mode mode

no hs-queue-stat-mode

Context

[Tree] (config>subscr-mgmt>sla-prof>egress>qos hs-queue-stat-mode)

Full Context

configure subscriber-mgmt sla-profile egress qos hs-queue-stat-mode

Description

This command configures the mode of statistics collected for all the HS queues.

The no form of this command reverts to the default.

Default

hs-queue-stat-mode no-override

Parameters

mode

Specifies the egress HS queue stats mode.

Values

no-override — Indicates no overrides are used.

v4-v6 — Indicates separate counters are collected for IPv4 and IPv6 instead of the normal queue statistics.

Platforms

7750 SR-7/12/12e

hs-scheduler-overrides

hs-scheduler-overrides

Syntax

hs-scheduler-overrides [create]

no hs-scheduler-overrides

Context

[Tree] (config>port>ethernet>egress hs-scheduler-overrides)

Full Context

configure port ethernet egress hs-scheduler-overrides

Description

Commands in this context configure HS scheduler overrides which override parameters in the applied HS scheduler policy. This command is only applicable to the HSQ IOM (iom4-e-hs) and will fail if configured on all other card types.

Parameters

create

Keyword used to create HS scheduler overrides. This keyword is requirement and can be enabled or disabled in the environment>create context.

Platforms

7750 SR-7/12/12e

hs-scheduler-policy

hs-scheduler-policy

Syntax

hs-scheduler-policy policy-name

no hs-scheduler-policy

Context

[Tree] (config>port>ethernet>egress hs-scheduler-policy)

Full Context

configure port ethernet egress hs-scheduler-policy

Description

This command specifies an HS scheduler policy to associate with the port egress which provisions the scheduling behavior of the HSQ scheduler classes.

A single HS scheduler policy is supported per port egress. This command is only applicable to the HSQ IOM (iom4-e-hs) and will fail if configured on all other card types.

The no form of this command removes the policy and reapplies the default policy.

Default

hs-scheduler-policy default

Parameters

policy-name

Specifies the policy name up to 32 characters.

Platforms

7750 SR-7/12/12e

hs-scheduler-policy

Syntax

hs-scheduler-policy policy-name [create]

no hs-scheduler-policy policy-name

Context

[Tree] (config>qos hs-scheduler-policy)

Full Context

configure qos hs-scheduler-policy

Description

This command configures an HS scheduler policy. The HS scheduler policies are applied to egress HSQ ports in the config>port>ethernet>egress context. The policy contains the required commands to provision the scheduling behavior of the HSQ scheduler classes. When assigned to an HSQ egress port, the policy is used to define the scheduling behavior for all queues associated with the egress port. The values defined in the policy can be overridden on each scheduler instance using the config>port>ethernet>egress>hs-scheduler-overrides command.

HSQ Queue Groups — A fundamental concept on an HSQ IOM is the queue group. Queue groups are not directly managed by the provisioning. Instead, they are indirectly assigned when creating SAPs or subscribers on an HSQ port. A queue group has eight queue members, numbered from 1 through 8. When creating a SAP or subscriber associated on an HSQ egress port, a queue group is allocated to the object. Within the SAP egress policy, network queue policy and egress queue group template, provisioned queue IDs 1 through 8 correspond directly to queue group queue IDs 1 through 8. Each group also allows each queue to be dynamically placed in a scheduling class or on one of two WRR groups local to the queue group.

Each queue within the group has three RED slopes (managed by associating a slope policy to the queue), an MBS defined in bytes, a packet byte offset parameter used to add or subtract bytes to or from each packet handled by the queue for accounting purposes, and a PIR shaper used to rate limit the queue. An HSQ attachment policy associated with the queue group defines how each queue maps either directly to a scheduling class or one of the WRR groups within the queue group. The attachment policy also defines the scheduling class attachments for the WRR groups.

The queue group supports an aggregate shaper used to manage an aggregate rate limit for all queues within the group. Scheduling for queues within the queue group is stopped and started based on the rate set on the shaper.

Scheduling Classes and Scheduling Priorities — HSQ supports six scheduler classes (1 through 6). The scheduler class should not be confused with a QoS policy forwarding class. Forwarding classes within the system are used between the ingress and egress forwarding complexes and help the system to map a packet to per-hop and per-domain behavior. Scheduling classes are slices of scheduling opportunity within a port-scheduling context. Each port scheduler maintains six strict priority levels, where 6 is the highest priority and 1 is the lowest. As a rule, the scheduler services all active queues associated with priority level 6 before moving to queues on priority level 5. This strict behavior continues through priority level 1. Scheduling classes are mapped either to their corresponding scheduling priority level (scheduling class 1 mapped to priority level 1 through scheduling class 6 mapped to priority level 6) or to a single port level WRR group. The WRR group allows collapsing up to 6 of the scheduling classes into a single scheduling priority. The WRR group provides a weighted fair scheduling behavior for its member scheduling classes at that strict priority level.

Strict Priority Level PIR — The scheduler supports a strict scheduling level PIR that limits the amount of bandwidth allowed for the level. The rate is defined in increments of megabits per second and can be set to max (the default setting) which disables the shaping function. The scheduler includes the full Ethernet frame encapsulation overhead when updating the priority level PIR, including the 12-byte inter-frame gap and the 8-byte preamble.

Scheduler Maximum Rate — A maximum scheduling rate can be defined for the scheduler. The rate is specified in megabits per second and the default rate is max which allows the scheduler to operate without a set limit. When the HS scheduling policy is applied to an egress port, the maximum scheduling rate can be used to define a rate less than the available line rate of the port. The scheduler includes the full Ethernet frame encapsulation overhead when updating the scheduler level PIR, including the 12-byte inter-frame gap and the 8-byte preamble.

HS Scheduler Policy Overrides — After an HS scheduler is applied to an egress port, the various parameters can be overridden, allowing an HS scheduler policy to be adapted to changing needs on a port without requiring a new policy to be created.

Default HS Scheduling Policy — An HS scheduling policy with the name default always exists on the system and does not need to be created. The default policy cannot be modified or deleted.

The default policy contains the following parameters:

Table 3. HS Scheduler Policy Parameter Defaults

Parameter

Sub-Parameter

Default

max-rate

max

scheduling-class 1 through 6

rate

max

group

weight

group 1

rate

max

Default

The no form of the command removes an HS scheduler policy from the system. If the HS scheduler policy is currently associated with an egress port, the command fails.

Parameters

policy-name

Specifies the HS scheduler policy up to 32 characters. Each HS scheduler policy must be uniquely named within the system.

create

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

Platforms

7750 SR-7/12/12e

hs-scheduler-policy

Syntax

hs-scheduler-policy src-name dst-name [overwrite]

Context

[Tree] (config>qos>copy hs-scheduler-policy)

Full Context

configure qos copy hs-scheduler-policy

Description

This command copies existing QoS policy entries for a QoS policy ID to another QoS policy ID.

The copy command is a configuration-level maintenance tool used to create new policies using existing policies. It also allows bulk modifications to an existing policy with the use of the overwrite keyword.

Parameters

src-name dst-name

Indicates that the source policy ID and the destination policy ID are HS policy IDs. Specify the source policy ID that the copy command attempts to copy from and specify the destination policy ID to which the command copies a duplicate of the policy.

overwrite

Specifies to replace the existing destination policy. Everything in the existing destination policy is overwritten with the contents of the source policy. If overwrite is not specified, an error occurs if the destination policy ID exists.

Example:
    — SR>config>qos# copy hs-pool-policy policy1 policy2
    — MINOR: CLI Destination "policy2" exists use {overwrite}.
    — SR>config>qos# copy hs-pool-policy policy1 policy2 overwrite

Platforms

7750 SR-7/12/12e

hs-secondary-shaper

hs-secondary-shaper

Syntax

hs-secondary-shaper secondary-shaper-name [ create]

no hs-secondary-shaper secondary-shaper-name

Context

[Tree] (config>port>ethernet>egress hs-secondary-shaper)

Full Context

configure port ethernet egress hs-secondary-shaper

Description

This command specifies an HS secondary shaper on the port egress. HS secondary shapers are used to apply an aggregate rate and per-scheduling class rates to the set of SAP egress HSQ queue groups which reference them using the SAP egress queue-override hs-secondary-shaper command.

By default, the hs-secondary-shaper default is applied to each port egress on all HSQ ports and the settings under it can be modified.

Multiple HS secondary shapers are supported per port egress, up to the number supported per-HSQ FP, which is 4096 HS secondary shapers. The number of HS secondary shapers allocated on an HSQ FP can be seen using the tools dump resource-usage card slot-number fp fp-number command.

Non-default HS secondary shapers are only configurable on access or hybrid mode ports.

This command is only applicable to the HSQ IOM (iom4-e-hs) and will fail if configured on all other card types.

The no form of this command removes the HS secondary shaper from the port egress configuration. An HS scheduler policy cannot be removed when HS scheduler overrides exist on the port egress.

Default

hs-secondary-shaper default

Parameters

secondary-shaper-name

Specifies the secondary shaper name up to 32 characters.

Platforms

7750 SR-7/12/12e

hs-secondary-shaper

Syntax

hs-secondary-shaper policy-name

no hs-secondary-shaper

Context

[Tree] (config>service>epipe>sap>egress>queue-override hs-secondary-shaper)

[Tree] (config>service>ipipe>sap>egress>queue-override hs-secondary-shaper)

Full Context

configure service epipe sap egress queue-override hs-secondary-shaper

configure service ipipe sap egress queue-override hs-secondary-shaper

Description

This command configures the HS secondary shaper to be used to apply an aggregate rate and per-scheduling class rates to the SAP egress HSQ queue group.

The no form of this command removes the HS secondary shaper override from the configuration, reverting the SAP egress HSQ queue group to the default HS secondary shaper on that port.

Parameters

policy-name

Specifies the secondary shaper name, up to 32 characters.

Platforms

7750 SR-7/12/12e

hs-secondary-shaper

Syntax

hs-secondary-shaper policy-name

no hs-secondary-shaper

Context

[Tree] (config>service>vprn>sap>queue-override hs-secondary-shaper)

Full Context

configure service vprn sap queue-override hs-secondary-shaper

Description

This command configures the HS secondary shaper to be used to apply an aggregate rate and per-scheduling class rates to the SAP egress HSQ queue group.

The no form of this command removes the HS secondary shaper override from the configuration, reverting the SAP egress HSQ queue group to the default HS secondary shaper on that port.

Parameters

policy-name

Specifies the secondary shaper name, up to 32 characters.

hs-secondary-shaper

Syntax

hs-secondary-shaper policy-name

no hs-secondary-shaper

Context

[Tree] (config>service>ies>if>sap>egress>queue-override hs-secondary-shaper)

Full Context

configure service ies interface sap egress queue-override hs-secondary-shaper

Description

This command configures the HS secondary shaper to be used to apply an aggregate rate and per-scheduling class rates to the SAP egress HSQ queue group.

The no form of this command removes the HS secondary shaper override from the configuration returning the SAP egress HSQ queue group to the default HS secondary shaper on that port.

Parameters

policy-name

Specifies the secondary shaper name, up to 32 characters.

Platforms

7750 SR-7/12/12e

hs-secondary-shaper

Syntax

hs-secondary-shaper policy-name

no hs-secondary-shaper

Context

[Tree] (config>service>vprn>if>sap>egress>queue-override hs-secondary-shaper)

Full Context

configure service vprn interface sap egress queue-override hs-secondary-shaper

Description

This command configures the HS secondary shaper to be used to apply an aggregate rate and per-scheduling class rates to the SAP egress HSQ queue group.

The no form of this command removes the HS secondary shaper override from the configuration, returning the SAP egress HSQ queue group to the default HS secondary shaper on that port.

Parameters

policy-name

Specifies the secondary shaper name, up to 32 characters.

Platforms

7750 SR-7/12/12e

hs-sla-mode

hs-sla-mode

Syntax

hs-sla-mode {expanded | single}

no hs-sla-mode

Context

[Tree] (config>subscr-mgmt>sub-prof hs-sla-mode)

Full Context

configure subscriber-mgmt sub-profile hs-sla-mode

Description

This command specifies the SLA profile handling mode for the subscriber if on an HS board.

The no form of this command reverts to the default.

Parameters

expanded

Specifies the expanded SLA profile handling mode for the subscriber if on an HS board.

single

Specifies a single SLA profile handling mode for the subscriber if on an HS board.

Platforms

7750 SR-7/12/12e

hs-turbo

hs-turbo

Syntax

[no] hs-turbo

Context

[Tree] (config>port>ethernet>network>egress>queue-group hs-turbo)

[Tree] (config>port>ethernet>access>egress>queue-group hs-turbo)

Full Context

configure port ethernet network egress queue-group hs-turbo

configure port ethernet access egress queue-group hs-turbo

Description

This command enables HS turbo queues which allows the corresponding HSQ queue group queues to achieve a higher throughput. The hs-turbo command is not applicable to 10G ports and is ignored when configured under a queue group instance on a 10G port.

This command is only applicable to the HSQ IOM (iom4-e-hs) and will fail if configured on all other card types.

The no form of this command disables the command.

Platforms

7750 SR-7/12/12e

hs-wred-queue

hs-wred-queue

Syntax

hs-wred-queue policy slope-policy-name

no hs-wred-queue

Context

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

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

Full Context

configure service epipe sap egress queue-override queue hs-wred-queue

configure service ipipe sap egress queue-override queue hs-wred-queue

Description

This command overrides the slope policy applied to the HSQ queue group queue.

The no form of this command removes the WRED queue policy override value from the configuration.

Parameters

slope-policy-name

Specifies an existing slope policy name to apply to this HSQ queue group queue, up to 32 characters.

Platforms

7750 SR-7/12/12e

hs-wred-queue

Syntax

hs-wred-queue policy slope-policy-name

no hs-wred-queue

Context

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

Full Context

configure service vpls sap egress queue-override queue hs-wred-queue

Description

This command overrides the slope policy applied to the HSQ queue group queue.

The no form of this command removes the WRED queue policy override value from the configuration.

Parameters

slope-policy-name

Specifies an existing slope policy name to apply to this HSQ queue group queue.

Platforms

7750 SR-7/12/12e

hs-wred-queue

Syntax

hs-wred-queue policy slope-policy-name

no hs-wred-queue

Context

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

Full Context

configure service ies interface sap egress queue-override queue hs-wred-queue

Description

This command overrides the slope policy applied to the HSQ queue group queue.

The no form of this command removes the WRED queue policy override value from the configuration.

Parameters

slope-policy-name

Specifies an existing slope policy name to apply to this HSQ queue group queue.

Platforms

7750 SR-7/12/12e

hs-wred-queue

Syntax

hs-wred-queue policy slope-policy-name

no hs-wred-queue

Context

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

Full Context

configure service vprn interface sap egress queue-override queue hs-wred-queue

Description

This command overrides the slope policy applied to the HSQ queue group queue.

The no form of this command removes the WRED queue policy override value from the configuration.

Parameters

slope-policy-name

Specifies an existing slope policy name to apply to this HSQ queue group queue.

Platforms

7750 SR-7/12/12e

hs-wred-queue

Syntax

hs-wred-queue [policy slope-policy-name]

no hs-wred-queue

Context

[Tree] (config>qos>network-queue>queue hs-wred-queue)

Full Context

configure qos network-queue queue hs-wred-queue

Description

This command reverts the slope policy applied to the HSQ queue group queue to the default policy. Specifying an existing slope policy applies the named slope policy to the queue.

The no form of the command reverts to the default slope policy.

Default

hs-wred-queue policy "_tmnx_hs_default"

Parameters

slope-policy-name

Specifies an existing slope policy to apply to this HSQ queue group queue.

Platforms

7750 SR-7/12/12e

hs-wred-queue

Syntax

hs-wred-queue [policy slope-policy-name]

no hs-wred-queue

Context

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

Full Context

configure qos sap-egress queue hs-wred-queue

Description

This command reverts the slope policy applied to the HSQ queue group queue to the default policy. Specifying an existing slope policy applies the named slope policy to the queue.

The no form of the command reverts to the default slope policy.

Default

hs-wred-queue policy "_tmnx_hs_default"

Parameters

slope-policy-name

Specifies an existing slope policy to apply to this HSQ queue group queue.

Platforms

7750 SR-7/12/12e

hs-wred-queue

Syntax

hs-wred-queue [policy slope-policy-name]

no hs-wred-queue

Context

[Tree] (config>qos>qgrps>egr>qgrp>queue hs-wred-queue)

Full Context

configure qos queue-group-templates egress queue-group queue hs-wred-queue

Description

This command reverts the slope policy applied to the HSQ queue group queue to the default policy. Specifying an existing slope policy applies the named slope policy to the queue.

The no form of the command reverts to the default slope policy.

Default

hs-wred-queue policy "_tmnx_hs_default"

Parameters

slope-policy-name

Specifies an existing slope policy name to apply to this HSQ queue group queue.

Platforms

7750 SR-7/12/12e

hs-wred-queue-policy

hs-wred-queue-policy

Syntax

hs-wred-queue-policy name

no hs-wred-queue-policy

Context

[Tree] (config>subscr-mgmt>sla-prof>egress>qos>queue hs-wred-queue-policy)

Full Context

configure subscriber-mgmt sla-profile egress qos queue hs-wred-queue-policy

Description

This command specifies the name of the slope-policy override to be applied for the HS queue of this SLA profile instance.

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

Parameters

name

Specifies the policy name up to 32 characters.

Platforms

7750 SR-7/12/12e

hs-wrr-group

hs-wrr-group

Syntax

[no] hs-wrr-group group-id

Context

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

Full Context

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

Description

This command configures the egress HS WRR group override parameters.

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

Parameters

group-id

Specifies the HS WRR group ID to override in the QoS policy table.

Values

1, 2

Platforms

7750 SR-7/12/12e

hs-wrr-group

Syntax

hs-wrr-group group-id [create]

no hs-wrr-group group-id

Context

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

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

Full Context

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

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

Description

This command configures the egress HS WRR group override parameters.

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

Parameters

group-id

Specifies the HS WRR group ID to override.

Values

1, 2

create

Keyword used to create an HSS WRR group. The create keyword requirement can be enabled/disabled in the environment>create context.

Platforms

7750 SR-7/12/12e

hs-wrr-group

Syntax

hs-wrr-group group-id [create]

no hs-wrr-group group-id

Context

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

Full Context

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

Description

This command configures the egress HS WRR group override parameters.

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

Parameters

group-id

Specifies the HS WRR group ID to override.

Values

1, 2

create

Keyword used to create an HSS WRR group. The create keyword requirement can be enabled/disabled in the environment>create context.

Platforms

7750 SR-7/12/12e

hs-wrr-group

Syntax

hs-wrr-group group-id [create]

hs-wrr-group group-id

Context

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

Full Context

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

Description

This command configures the egress HS WRR group override parameters.

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

Parameters

group-id

Specifies the HS WRR group ID to override.

Values

1, 2

Platforms

7750 SR-7/12/12e

hs-wrr-group

Syntax

hs-wrr-group group-id [create]

no hs-wrr-group group-id

Context

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

Full Context

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

Description

This command configures the egress HS WRR group override parameters.

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

Parameters

group-id

Specifies the HS WRR group ID to override.

Values

1, 2

create

Keyword used to create the HS WRR group override instance.

Platforms

7750 SR-7/12/12e

hs-wrr-group

Syntax

[no] hs-wrr-group group-id

Context

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

Full Context

configure qos network-queue hs-wrr-group

Description

Commands in this context configure HS WRR group information in the network queue policy. This command provisions the rate and class weight of each of the two WRR scheduling groups that can be utilized by the egress queue-group instance HSQ queues.

The no form of the command reverts the HS WRR group parameters to their default values.

Parameters

group-id

Specifies the HS WRR group identifier. WRR group ID 1 or 2 must be specified when executing the hs-wrr-group command. The specified group ID identifies which WRR group context is entered for editing.

Values

1, 2

Platforms

7750 SR-7/12/12e

hs-wrr-group

Syntax

hs-wrr-group group-id

no hs-wrr-group

Context

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

Full Context

configure qos sap-egress hs-wrr-group

Description

Commands in this context configure HS WRR group information in the SAP egress QoS policy. The hs-wrr-group command is used to provision the rate and class weight of each of the two WRR scheduling groups that can be utilized by the SAP egress HSQ queues.

The no form of the command resets the HS WRR group parameters to their default values.

Parameters

group-id

Specifies the HS WRR group identifier. WRR group ID 1 or 2 must be specified when executing the hs-wrr-group command. The specified group ID identifies which WRR group context is entered for editing.

Values

1, 2

Platforms

7750 SR-7/12/12e

hs-wrr-group

Syntax

[no] hs-wrr-group group-id

Context

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

Full Context

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

Description

Commands in this context configure HS WRR group information in the egress queue group template. The hs-wrr-group command is used to provision the rate and class weight of each of the two WRR scheduling groups that can be utilized by the egress queue group instance HSQ queues.

The no form of the command resets the HS WRR group parameters to their default values.

Parameters

group-id

Specifies the HS WRR group identifier. WRR group ID 1 or 2 must be specified when executing the hs-wrr-group command. The specified group ID identifies which WRR group context is entered for editing.

Values

1, 2

Platforms

7750 SR-7/12/12e

hs-wrr-weight

hs-wrr-weight

Syntax

hs-wrr-weight weight

no hs-wrr-weight

Context

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

Full Context

configure subscriber-mgmt sla-profile egress qos queue hs-wrr-weight

Description

This command configures the SLA profile instance WRR weight override for the HS queue. When a weight value is not specified, there is no override, meaning, the WRR weight is taken from the sap-egress policy.

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

Parameters

weight

Specifies the class-weight override for expanded egress HS queues.

Values

1 to 127

Platforms

7750 SR-7/12/12e

hs-wrr-weight

Syntax

hs-wrr-weight weight

no hs-wrr-weight

Context

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

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

Full Context

configure service epipe sap egress queue-override queue hs-wrr-weight

configure service ipipe sap egress queue-override queue hs-wrr-weight

Description

This command overrides the WRR relative weight as defined within the associated HS attachment policy.

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

Parameters

weight

Specifies the HS WRR group queue weight.

Values

1 to 127

Platforms

7750 SR-7/12/12e

hs-wrr-weight

Syntax

hs-wrr-weight weight

no hs-wrr-weight

Context

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

Full Context

configure service vpls sap egress queue-override queue hs-wrr-weight

Description

This command overrides the WRR relative weight with which this queue should parent into an HSQ WRR group defined within the associated HS attachment policy.

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

Parameters

weight

Specifies the HS WRR group queue weight.

Values

1 to 127

Platforms

7750 SR-7/12/12e

hs-wrr-weight

Syntax

hs-wrr-weight weight

no hs-wrr-weight

Context

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

Full Context

configure service ies interface sap egress queue-override queue hs-wrr-weight

Description

This command overrides the Weighted Round Robin (WRR) relative weight with which this queue should parent into an HSQ WRR group defined within the associated HS attachment policy.

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

Parameters

weight

Specifies the HS WRR group queue weight.

Values

1 to 127

Platforms

7750 SR-7/12/12e

hs-wrr-weight

Syntax

hs-wrr-weight weight

no hs-wrr-weight

Context

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

Full Context

configure service vprn interface sap egress queue-override queue hs-wrr-weight

Description

This command overrides the WRR relative weight with which this queue should parent into an HSQ Weighted Round Robin (WRR) group defined within the associated HS attachment policy.

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

Parameters

weight

Specifies the HS WRR group queue weight.

Values

1 to 127

Platforms

7750 SR-7/12/12e

hs-wrr-weight

Syntax

hs-wrr-weight weight

no hs-wrr-weight

Context

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

Full Context

configure qos network-queue queue hs-wrr-weight

Description

This command specifies the WRR relative weight, with which this queue should parent into an HSQ WRR group defined within the associated HS attachment policy. The weight of each queue determines how much bandwidth that queue gets out of the total rate for the HSQ WRR group.

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

Default

hs-wrr-weight 1

Parameters

weight

Specifies the HS WRR group queue weight.

Values

1 to 127

Platforms

7750 SR-7/12/12e

hs-wrr-weight

Syntax

hs-wrr-weight weight

no hs-wrr-weight

Context

[Tree] (config>qos>sap-egress>queue hs-wrr-weight)

Full Context

configure qos sap-egress queue hs-wrr-weight

Description

This command specifies the WRR relative weight, with which this queue should parent into an HSQ WRR group defined within the associated HS attachment policy. The weight of each queue determines how much bandwidth that queue gets out of the total rate for the HSQ WRR group.

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

Default

hs-wrr-weight 1

Parameters

weight

Specifies the HS WRR group queue weight.

Values

1 to 127

Platforms

7750 SR-7/12/12e

hs-wrr-weight

Syntax

hs-wrr-weight weight

no hs-wrr-weight

Context

[Tree] (config>qos>qgrps>egr>qgrp>queue hs-wrr-weight)

Full Context

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

Description

This command specifies the WRR relative weight, with which this queue should parent into an HSQ WRR group defined within the associated HS attachment policy. The weight of each queue determines how much bandwidth that queue gets out of the total rate for the HSQ WRR group.

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

Default

hs-wrr-weight 1

Parameters

weight

Specifies HS WRR group queue weight.

Values

1 to 127

Platforms

7750 SR-7/12/12e

http-auth

http-auth

Syntax

http-auth password password [hash | hash2]

http-auth username user-name

http-auth username user-name password password [hash | hash2]

no http-auth

Context

[Tree] (config>system>security>pki>est-profile http-auth)

Full Context

configure system security pki est-profile http-auth

Description

This command configures HTTP authentication parameters. HTTP authentication is used by a client when requested by the server. When disabled, there is no HTTP-level client authentication.

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

Default

no http-auth

Parameters

password

Specifies a text string containing the password. Allowed values are any string up to 64 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

user-name

Specifies the name of the user to authenticate, up to 32 characters.

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.

Platforms

All

http-connections

http-connections

Syntax

http-connections [ip-address/prefix-length]

http-connections any

http-connections [ipv6-address/prefix-length]

no http-connections

Context

[Tree] (debug>system http-connections)

Full Context

debug system http-connections

Description

This command displays HTTP connections debug information.

Parameters

ip-address/prefix-length

Displays information for the specified host IP address and prefix length.

Values

ip-address: a.b.c.d

prefix-length: 0 to 32

any

Specifies that any address can be used.

ipv6-address/prefix-length

Displays information for the specified host IPv6 address and prefix length.

Values

ipv6-address:

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

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

  • x [0 to FFFFF] H

  • d [0 to 255] D

prefix-length: 0 to 128

Platforms

All

http-enrich