w Commands

Context

[Tree] (bof wait)

Full Context

bof wait

Description

This command configures a pause, in seconds, at the start of the boot process which allows system initialization to be interrupted at the console.

When system initialization is interrupted the operator is allowed to manually override the parameters defined in the boot option file (BOF).

Only one wait command can be defined in the BOF.

Default

wait 3

Parameters

seconds

Specifies the time to pause at the start of the boot process, in seconds.

Values

1 to10

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>nat>outside>pool watermarks)

[Tree] (config>service>vprn>nat>outside>pool watermarks)

Full Context

configure router nat outside pool watermarks

configure service vprn nat outside pool watermarks

Description

This command configures the watermarks for ports or port-block utilization in a NAT pool.

For CGN and L2-aware NAT, the port and port-block watermarks are used to monitor ports or port-block utilization in a NAT pool. High and low thresholds are configured in percentages of total available port-blocks or ports per protocol in a pool.

For LSN44 pools with flexible port allocation, the watermarks represent the port utilization per outside IP address if paired address pooling is enabled. If an arbitrary address pooling is enabled, then the watermarks represent the port utilization per pool.

For port-block based pools where flexible port allocation is disabled, the watermarks represent port-block occupancy per pool. These watermarks cover combined initial and extended port-blocks in a NAT pool. If the extended port blocks are not enabled in L2-aware NAT, then the L2-aware pool contains only the initial port-blocks.

For the system to generate those events, the NAT event ID is configured as follows:

• 2001 is enabled for L2-aware pools which do not use l2-aware port-block-extensions

• 2003 is enabled for port-blocks based LSN pools

• 2044 is enabled for L2-aware pools which use l2aware port-block-extension

• 2046 is enabled for port based LSN pools for flexible-port-allocation

Event IDs are enabled via log event control configuration.

Default

no watermarks

Parameters

high percentage-high

Specifies the high percentage.

Values

1 to 100

low percentage-low

Specifies the low percentage.

Values

0 to 99

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>nat>nat-policy>port-limits watermarks)

Full Context

configure service nat nat-policy port-limits watermarks

Description

This command configures the port usage watermarks for the NAT policy.

Default

no watermarks

Parameters

percentage-high

Specifies the high percentage.

Values

1 to 100

percentage-low

Specifies the low percentage.

Values

0 to 99

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>nat>nat-policy>session-limits watermarks)

Full Context

configure service nat nat-policy session-limits watermarks

Description

This command configures the session watermarks for the NAT or residential firewall policy.

Default

no watermarks

Parameters

percentage-high

Specifies the high percentage.

Values

1 to 100

percentage-low

Specifies the low percentage.

Values

0 to 99

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure system cron schedule weekday

Description

This command specifies which days of the week that the schedule will fire on. Multiple days of the week can be specified. When multiple days are configured, each of them will cause the schedule to occur. If a weekday is configured without configuring the month, weekday, day-of-month, and minute, the event will not execute.

Using the weekday command as well as the day-of month command will cause the script to run twice. For example, consider that today is Monday January 1. If Tuesday January 5 is configured, the script will run on Tuesday (tomorrow) as well as January 5 (Friday).

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

Default

no weekday

Parameters

weekday-number

Specifies a weekday number.

Values

1 to 7 (maximum 7 weekday-numbers)

day-name

Specifies a day by name.

Values

sunday, monday, tuesday, wednesday, thursday, friday, saturday (maximum 7 weekday names)

all

Specifies all days of the week.

Platforms

7705 SAR Gen 2

Context

[Tree] (conf>router>segment-routing>sr-policies>policy>seg-list weight)

Full Context

configure router segment-routing sr-policies static-policy segment-list weight

Description

This command associates a weight value with a segment list of a statically-defined segment routing policy to achieve weighted ECMP behavior. Weight is an optional parameter.

When any segment-list in the active policy has a weight greater than 1, traffic matching the policy is load-balanced across the segment lists according to their relative weight values.

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

Default

weight 1

Parameters

weight

Specifies the weight value.

Values

1 to 4294967295

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure vrrp policy priority-event lag-port-down weight-down

Description

This command creates a context to configure an event set threshold within a lag-port-down priority control event. The weight-down command defines a sub-node within the lag-port-down event and is uniquely identified with the lag-ports-down-weight parameter. Each weight-down node within the same lag-port-down event node must have a unique lag-ports-down-weight value. Each weight-down node has its own priority command that takes effect whenever that node represents the current threshold. A single LAG can use either weight-based (weight-down) or port-based (number-down) thresholds. The weight-based thresholds are required for correct operation on mixed port-speed LAGs, but can be used for non mixed port-speed LAGs as well. The weights for the weight-down node are normalized from the hash-weight values of the LAG member ports to fit a 1 to 64 range for 64-link capable LAGs and a 1 to 32 range for other LAGs.

The total number of sub-nodes (uniquely identified by the lag-ports-down-weight parameter) allowed in the system is 2048.

A weight-down node is not required for each possible number of ports that could be down. The active threshold is always the closest lower threshold.

The no form of the command deletes the event set threshold. The threshold may be removed at any time. If the removed threshold is the current active threshold, the event set thresholds must be re-evaluated after removal.

Default

no weight-down

Parameters

lag-ports-down-weight

The total weight of LAG ports down to create a set event threshold. This is the active threshold when the weight of down ports in the LAG equals or exceeds lag-ports-down-weight, but does not equal or exceed the next highest configured lag-ports-down-weight.

Values

1 to 64 (for 64-link capable LAGs)

1 to 32 (for other LAGs)

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>bgp-ipvpn>mpls>auto-bind-tunnel weighted-ecmp)

[Tree] (config>service>epipe>bgp-evpn>mpls>auto-bind-tunnel weighted-ecmp)

[Tree] (config>service>vpls>bgp-evpn>mpls>auto-bind-tunnel weighted-ecmp)

Full Context

configure service vprn bgp-ipvpn mpls auto-bind-tunnel weighted-ecmp

configure service epipe bgp-evpn mpls auto-bind-tunnel weighted-ecmp

configure service vpls bgp-evpn mpls auto-bind-tunnel weighted-ecmp

Description

This command enables weighted ECMP for packets using tunnels that a VPRN, VPLS, or Epipe automatically binds to. When weighted ECMP is enabled, packets are sprayed across LSPs in the ECMP according to the outcome of the hash algorithm and the configured load balancing weight of each LSP.

The no form of this command disables weighted ECMP for next hop tunnel selection.

Default

no weighted-ecmp

Platforms

7705 SAR Gen 2

Context

[Tree] (configure>service>vpls>bgp-evpn>ip-route-link-bw weighted-ecmp)

[Tree] (configure>service>vprn>bgp-evpn>mpls>evpn-link-bw weighted-ecmp)

Full Context

configure service vpls bgp-evpn ip-route-link-bandwidth weighted-ecmp

configure service vprn bgp-evpn mpls evpn-link-bandwidth weighted-ecmp

Description

This command enables the processing of the EVPN link bandwidth extended community when installing an ECMP set for an EVPN IP prefix route in the VPRN route table.

Flows to an IP prefix received with a weight and a zero ESI value are sprayed according to the weight. If the EVPN IP prefix route received with the weight has a non-zero ESI, the weight is divided into the number of PEs attached to the Ethernet Segment (and rounded up if the result is not an integer).

This command also enables the weighted ECMP functionality for BGP CEs where the weight is configured with the evpn-link-bandwidth add-to-received-bgp command.

The no form of this command disables EVPN link bandwidth extended community.

Default

no weighted-ecmp

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn weighted-ecmp)

Full Context

configure service vprn weighted-ecmp

Description

This command enables weighted load-balancing for IS-IS, OSPF, and static ECMP routes in the VPRN instance. Weighted ECMP can be performed when all next hops are configured with non-zero load-balancing weights. Weighted ECMP support for IS-IS, OSPF, and static ECMP routes applies to both IPv4 and IPv6.

The no form of this command restores regular ECMP spraying of packets to IS-IS, OSPF and static route destinations.

Default

no weighted-ecmp

Parameters

strict

Enables strict enforcement for a load balancing weight to be configured on each interface withing a wECMP interface bundle before the interface is taken into wECMP operation. However, when strict enforcement is not enabled, then, when load-balancing-weight is not configured on one or more interfaces within the wECMP interface bundle, the wECMP load-balancing falls back to classic ECMP operation and equally share the traffic load across the ECMP interface bundle. A special case is when none of the available paths or next-hops have a load balancing weight associated. Then, the load balancing falls back to classic ECMP.

Strict load balancing is only applied on IS-IS, OSPF, and static route entries.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn weighted-ecmp)

Full Context

configure service vprn weighted-ecmp

Description

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>ldp weighted-ecmp)

Full Context

configure router ldp weighted-ecmp

Description

This command enables weighted ECMP on LDP using RSVP LSPs or SR-TE LSPs. LDP labeled packets are sprayed across the RSVP or SR-TE LSP ECMP in proportion to the configured load-balancing-weight of LSPs.

The no form of this command removes weighted ECMP.

Default

no weighted-ecmp

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router weighted-ecmp)

Full Context

configure router weighted-ecmp

Description

This command enables the weighted load-balancing, or weighted ECMP, over MPLS LSP.

When this command is enabled, packets of IGP, BGP, and static route prefixes resolved to a set of ECMP tunnel next-hops are sprayed proportionally to the weights configured for each MPLS LSP in the ECMP set.

Weighted load-balancing over MPLS LSP is supported in the following forwarding contexts:

• IGP prefix resolved to IGP shortcuts in RTM (igp-shortcut or advertise-tunnel-link enabled in the IGP instance).

• BGP prefix with the BGP next-hop resolved to IGP shortcuts in RTM (igp-shortcut or advertise-tunnel-link enabled in the IGP instance).

• Static route prefix resolved to an indirect next-hop, which itself is resolved to a set of equal-metric MPLS LSPs in TTM. The user can allow automatic selection or specify the names of the equal-metric MPLS LSPs in TTM to be used in the ECMP set.

• Static route prefix resolved to an indirect next-hop, which is resolved to IGP shortcuts in RTM.

• BGP prefix with a BGP next-hop resolved to a static route, which resolves to a set of tunnel next-hops toward an indirect next-hop in RTM or TTM.

• BGP prefix resolving to another BGP prefix, whose next-hop is resolved to a set of ECMP tunnel next-hops with a static route in RTM or TTM or to IGP shortcuts in RTM.

IGP computes the normalized weight for each prefix tunnel next-hop. IGP updates the route in RTM with the set of tunnel next-hops and normalized weights. RTM downloads the information to IOM for inclusion in the FIB.

If one or more LSPs in the ECMP set of a prefix do not have a weight configured, the regular ECMP spraying for the prefix will be performed.

The weight assigned to an LSP impacts only the forwarding decision, not the routing decision. In other words, it does not change the selection of the set of ECMP tunnel next-hops of a prefix when more next-hops exist than the value of the router ecmp option. Once the set of tunnel next-hops is selected, the LSP weight is used to modulate the amount of packets forwarded over each next-hop. It also does not change the hash routine, but only the spraying of the flows over the tunnel next-hops is modified to reflect the normalized weight of each tunnel next-hop.

The no form of this command resumes regular ECMP spraying of packets of IGP, BGP, and static route prefixes over MPLS LSP.

Default

no weighted-ecmp

Parameters

strict

Enables strict enforcement for a load balancing weight to be configured on each interface withing a wECMP interface bundle before the interface is taken into wECMP operation. However, when strict enforcement is not enabled, then, when load-balancing-weight is not configured on one or more interfaces within the wECMP interface bundle, the wECMP load-balancing falls back to classic ECMP operation and equally share the traffic load across the ECMP interface bundle. A special case is when none of the available paths or next-hops have a load balancing weight associated. Then, the load balancing falls back to classic ECMP.

Strict load balancing is only applied on IS-IS, OSPF, and static route entries.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>sdp weighted-ecmp)

Full Context

configure service sdp weighted-ecmp

Description

This command enables weighted ECMP on an SDP. When weighted ECMP is enabled, packets from services using the SDP are sprayed across LSPs in the ECMP set to the SDP far end according to the outcome of the hash algorithm and the configured load-balancing weight of each LSP.

The no version of this command disables weighted ECMP for next-hop tunnel selection.

Default

no weighted-ecmp

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>bgp>next-hop-res weighted-ecmp)

Full Context

configure router bgp next-hop-resolution weighted-ecmp

Description

This command enables weighted ECMP for next-hop tunnel selection for 6PE. When weighted ECMP is enabled, the RSVP-TE tunnel used to forward 6PE packets to the ECMP next hop is chosen according to the outcome of the hash on the packet at the normalized load-balancing weight of the tunnel.

The no version of this command disables weighted ECMP for next-hop tunnel selection for 6PE.

Default

no weighted-ecmp

Platforms

7705 SAR Gen 2

Context

[Tree] (config>service>vprn>isis>level wide-metrics-only)

Full Context

configure service vprn isis level wide-metrics-only

Description

This command enables the exclusive use of wide metrics in the LSPs for the level number. Narrow metrics can have values between 1 and 63. IS-IS can generate two TLVs, one for the adjacency and one for the IP prefix. In order to support traffic engineering, wider metrics are required. When wide metrics are used, a second pair of TLVs are added, again, one for the adjacency and one for the IP prefix.

By default, both sets of TLVs are generated. When wide-metrics-only is configured, IS-IS only generates the pair of TLVs with wide metrics for that level.

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

Platforms

7705 SAR Gen 2

Context

[Tree] (config>router>isis>level wide-metrics-only)

Full Context

configure router isis level wide-metrics-only

Description

This command enables the exclusive use of wide metrics in the LSPs for the level number. Narrow metrics can have values between 1 and 63. IS-IS can generate two TLVs, one for the adjacency and one for the IP prefix. In order to support traffic engineering, wider metrics are required. When wide metrics are used, a second pair of TLVs are added, again, one for the adjacency and one for the IP prefix.

By default, both sets of TLVs are generated. When wide-metrics-only is configured, IS-IS only generates the pair of TLVs with wide metrics for that level.

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

Default

no wide-metrics-only

Platforms

7705 SAR Gen 2

Context

[Tree] (environment>terminal width)

Full Context

environment terminal width

Description

This command determines display terminal width.

Default

width 80

Parameters

width

Sets the width of the display terminal.

Values

1 to 512

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>management-interface>cli>md-cli>environment>console width)

Full Context

configure system management-interface cli md-cli environment console width

Description

This command configures the set number of columns displayed on the console.

Default

width 80

Parameters

width

Specifies the number of columns displayed in the console window.

Values

80 to 512

Platforms

7705 SAR Gen 2

Context

[Tree] (config>port>ethernet>crc-monitor window-size)

Full Context

configure port ethernet crc-monitor window-size

Description

This command specifies sliding window size over which the Ethernet frames are sampled to detect signal fail or signal degrade conditions. The command is used jointly with the sf-threshold and the sd-threshold to configure the sliding window size.

The no version of this command reverts to the default value of 10 seconds.

Default

no window-size

Parameters

seconds

The size of the sliding window in seconds over which the errors are measured.

Values

5 to 60

Platforms

7705 SAR Gen 2

Context

[Tree] (config>filter>log wrap-around)

Full Context

configure filter log wrap-around

Description

This command configures a memory filter log to log until full or to store the most recent log entries (circular buffer).

Specifying wrap-around configures the memory filter log to store the most recent filter log entries (circular buffer). When the log is full, the oldest filter log entries are overwritten with new entries.

The no form of the command configures the memory filter log to accept filter log entries until full. When the memory filter log is full, filter logging for the log filter ID ceases.

Default

wrap-around

Platforms

7705 SAR Gen 2

Context

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

Full Context

configure qos sap-egress queue wred-queue

Description

This command allows the configuration of WRED per queue with the following options:

• Native hardware WRED

  This uses the hardware per queue WRED capabilities of FP3- and higher-based hardware and is configured with the native keyword.

• Pool per queue WRED

  This implements each queue in its own pool and uses the WRED capabilities of the pool to provide WRED per queue. This is configured with the pool-per-queue keyword.

Native Hardware WRED

When the wred-queue mode native command is configured, the queue uses the WRED capabilities of FP3- and higher-based hardware. In this case, the out-of-profile and exceed-profile traffic map to the low and exceed WRED slopes specified within the slope policy, and the inplus-profile and in-profile traffic uses the MBS drop tail; this requires the slope-usage to be configured as exceed-low. The instantaneous queue depth is compared against the low and exceed slopes so the time average factor in the slope policy is ignored.

When a policy is not explicitly defined, the default slope policy is used.

When native mode is enabled for a queue, the pool and drop-tail commands are ignored; traffic mapped to a slope that is shut down will use the MBS drop tail.

This is only supported on FP3 hardware.

The no form of this command restores the queue default congestion control behavior to the queue.

Pool-per-queue WRED

When the wred-queue mode pool-per-queue command is defined and the queue ID is created, a buffer pool is created specifically for the queue and the queue obtains all buffers from that pool. The size of the pool is the same as the size of the queue. In this manner, the WRED slopes that operate based on the pool’s buffer utilization are also reacting to the congestion depth of the queue.

The size of the buffer pool is dictated by the queue’s MBS parameter. The size of the reserved CBS portion of the buffer pool is dictated by the queue’s CBS parameter. The provisioning characteristics of the mbs and cbs commands are not changed.

In the case where this is applied with WRED queue support shutdown (config>card>fp>egress>wred-queue-control>shutdown), the queue will continue to map to its default pool. If the no shutdown command is executed in the wred-queue-control context, the queue is automatically moved to its own WRED pool.

Each pool created for a queue using the wred-queue command shares buffers with all other wred-queue enabled queues on the same forwarding plane. The WRED pool buffer management behavior is defined within the config>card>fp>egress>wred-queue-control CLI context.

The WRED slopes within the pool are defined by the slope policy associated with the queue. When a policy is not explicitly defined, the default slope policy is used. The slope policy enables, disables, and defines the relative geometry of the highplus, high, low, and exceed WRED slopes in the pool. The policy also specifies the time average factor used by the pool when calculating the weighted average pool depth.

As packets attempt to enter the egress queue, they are associated with the highplus, high, low, or exceed WRED slope based on the packet’s profile. If the packet is inplus-profile, the highplus slope is used. If the packet is in-profile, the high slope is used. If the packet is out-of-profile, the low slope is used. If the packet is exceed-profile, the exceed slope is used. This mapping of packet profile to slope is enabled using the slope-usage default parameter. Each WRED slope performs a probability discard based on the current weighted average pool depth.

When wred-queue is enabled for a SAP egress queue, the queue pool and drop-tail commands are ignored; traffic mapped to a slope that is shut down will use the MBS drop tail.

The resource usage for the WRED queue pool-per-queue per forwarding plane can be seen in the tools dump resource-usage card [ slot-num] fp [fp-number] output under Dynamic Q2 Wred Pools.

The no form of this command restores the generic buffer pool behavior to the queue. The WRED pool is removed from the system. The queue will be moved to the default buffer pool. The queue then uses the default congestion control behavior.

Default

no wred-queue

Parameters

slope-policy-name

Specifies an existing slope policy that is used to override the default WRED slope policy.

mode

Specifies whether the WRED per queue is using the native FP3- and higher-based hardware WRED capabilities or pool per queue.

Values

native — uses the hardware per queue WRED capabilities of the FP3- and higher-based hardware and requires slope-usage exceed-low.

pool-per-queue — each queue uses its own pool and the WRED capabilities of the pool to provide WRED per queue. This is supported on both FP2- and higher-based hardware and requires slope-usage default.

Default

native

slope-usage

Specifies congestion control to be used.

Values

default — maps the inplus, in, out, and exceed-profile traffic to the highplus, high, low, and exceed WRED slopes, respectively; this is only supported for pool-per-queue mode.

exceed-low — maps the out and exceed-profile traffic to the low and exceed WRED slopes with the inplus and in-profile traffic using the MBS drop tail. This is only supported for native mode.

Default

exceed-low

Platforms

7705 SAR Gen 2

Context

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

Full Context

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

Description

This command allows the configuration of WRED per queue with the following options:

• Native hardware WRED

  This uses the hardware per queue WRED capabilities of FP3- and higher-based hardware and is configured with the native keyword.

• Pool per queue WRED

  This implements each queue in its own pool and uses the WRED capabilities of the pool to provide WRED per queue. This is configured with the pool-per-queue keyword.

Native Hardware WRED

When the wred-queue mode native command is configured, the queue uses the WRED capabilities of FP3- and higher-based hardware. In this case, the out and exceed-profile traffic map to the low and exceed WRED slopes specified within the slope policy, and the inplus and in-profile traffic uses the MBS drop tail; this requires the slope-usage to be configured as exceed-low. The instantaneous queue depth is compared against the low and exceed slopes so the time average factor in the slope policy is ignored.

When a policy is not explicitly defined, the default slope policy is used.

When native mode is enabled for a queue, the drop-tail commands are ignored; traffic mapped to a slope that is shut down will use the MBS drop tail.

Native hardware WRED is supported on FP3- and higher-based hardware and is ignored on FP2 hardware.

The no form of this command restores the queue default congestion control behavior to the queue.

Pool-per-queue WRED

When the wred-queue mode pool-per-queue command is defined and the queue ID is created, a buffer pool is created specifically for the queue and the queue obtains all buffers from that pool. The size of the pool is the same as the size of the queue. In this manner, the WRED slopes that operate based on the pool’s buffer utilization are also reacting to the congestion depth of the queue.

The size of the buffer pool is dictated by the queue’s mbs parameter. The size of the reserved CBS portion of the buffer pool is dictated by the queue’s cbs parameter. The provisioning characteristics of the mbs and cbs commands are not changed.

In the case where this is applied with WRED queue support shut down (config>card>fp>egress>wred-queue-control>shutdown), the queue will continue to map to its default pool. If the no shutdown command is executed in the wred-queue-control context, the queue will be automatically moved to its own WRED pool.

Each pool created for a queue using the wred-queue command shares buffers with all other wred-queue enabled queues on the same forwarding plane. The WRED pool buffer management behavior is defined within the config>card>fp>egress>wred-queue-control CLI context.

The WRED slopes within the pool are defined by the slope policy associated with the queue. When a policy is not explicitly defined, the default slope policy is used. The slope policy enables, disables, and defines the relative geometry of the highplus, high, low, and exceed WRED slopes in the pool. The policy also specifies the time average factor used by the pool when calculating the weighted average pool depth.

As packets attempt to enter the egress queue, they are associated with the highplus, high, low, or exceed WRED slope based on the packet’s profile. If the packet is inplus-profile, the highplus slope is used. If the packet is in-profile, the high slope is used. If the packet is out-of-profile, the low slope is used, and if the packet is exceed-profile, the exceed slope is used. This mapping of packet profile to slope is enabled using the slope-usage default parameter. Each WRED slope performs a probability discard based on the current weighted average pool depth.

When wred-queue is enabled for an egress queue group queue, the queue pool and drop-tail commands are ignored; traffic mapped to a slope that is shut down will use the MBS drop tail.

The resource usage for the wred-queue pool-per-queue per forwarding plane can be seen in the tools dump resource-usage card [ slot-num] fp [fp-number] output under Dynamic Q2 Wred Pools.

The no form of this command restores the generic buffer pool behavior to the queue. The WRED pool is removed from the system. The queue will be moved to the default buffer pool. The queue then uses the default congestion control behavior.

Default

no wred-queue

Parameters

slope-policy-name

Specifies an existing slope policy that is used to override the default WRED slope policy.

mode {native | pool-per-queue}

Specifies whether the WRED per queue is using the native FP3- and higher-based hardware WRED capabilities or pool per queue.

Values

native - Each queue uses the hardware per queue WRED capabilities of the FP3- and higher-based hardware and requires slope-usage exceed-low.

pool-per-queue - Each queue uses its own pool and the WRED capabilities of the pool to provide WRED per queue. This requires slope-usage default.

Default

native

slope-usage {default | exceed-low}

Specifies the type of congestion control to be used.

Values

default - Maps the inplus-profile, in-profile, out-of-profile, and exceed-profile traffic to the highplus, high, low, and exceed WRED slopes, respectively; this is only supported for pool-per-queue mode.

exceed-low - Maps the out-of-profile and exceed-profile traffic to the low and exceed WRED slopes, with the inplus-profile and in-profile traffic using the MBS drop tail. This option is only supported for native mode.

Default

exceed-low

Platforms

7705 SAR Gen 2

Context

[Tree] (write)

Full Context

write

Description

This command sends a console message to a specific user or to all users with active console sessions.

Parameters

user-name

Specifies the name of a user, up to 32 characters, with an active console session to which to send a console message.

Values

any valid CLI username

broadcast

Sends the message-string to all users logged into the router.

message

Specifies the message string to send. Allowed values are any string, up to 256 characters, composed of printable, 7-bit ASCII characters. If the string contains special characters (#, ?, space), the entire string must be enclosed within double quotes.

Platforms

7705 SAR Gen 2

Context

[Tree] (config>system>security>management-interface>classic-cli write-algorithm)

Full Context

configure system security management-interface classic-cli write-algorithm

Description

This command specifies how encrypted configuration secrets are output from the system. For example, how encrypted secrets are displayed in the output of the info command, and how they are written to the saved configuration file.

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

Default

write-algorithm hash2

Parameters

hash

Specifies hash. Use this option to transport a phrase between modules and nodes. In this case the read-algorithm should be hash as well.

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

7705 SAR Gen 2