w Commands
wa-shared-high-wmark
wa-shared-high-wmark
Syntax
wa-shared-high-wmark percent
no wa-shared-high-wmark
Context
[Tree] (config>isa>aa-grp>qos>egress>from-sub wa-shared-high-wmark)
[Tree] (config>isa>aa-grp>qos>egress>to-sub wa-shared-high-wmark)
Full Context
configure isa application-assurance-group qos egress from-subscriber wa-shared-high-wmark
configure isa application-assurance-group qos egress to-subscriber wa-shared-high-wmark
Description
This command configures the high watermark for the weighted average utilization of the shared buffer space in the from-subscriber buffer pool for each ISA. When a buffer pool is not in the overload state and the wa-shared buffer utilization for an ISA crosses above the high watermark value in the ISA from-subscriber buffer pool enters an overload state and an overload notification is raised.
The no form of this command reverts to the default.
Default
wa-shared-high-wmark max
Parameters
- percent
Specifies the weighted average shared buffer utilization high watermark.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
wa-shared-low-wmark
wa-shared-low-wmark
Syntax
wa-shared-low-wmark percent
no wa-shared-low-wmark
Context
[Tree] (config>isa>aa-grp>qos>egress>from-sub wa-shared-low-wmark)
[Tree] (config>isa>aa-grp>qos>egress>to-sub wa-shared-low-wmark)
Full Context
configure isa application-assurance-group qos egress from-subscriber wa-shared-low-wmark
configure isa application-assurance-group qos egress to-subscriber wa-shared-low-wmark
Description
This command configures the low watermark for the weighted average utilization of the shared buffer space in the from-subscriber buffer pool. When a buffer pool is in an overloaded state and the wa-shared buffer utilization for an ISA drops below low watermark value ISA from-subscriber buffer pool leaves the overload state and a is sent to indicate the overload state has cleared.
The no form of this command reverts to the default.
Default
wa-shared-low-wmark 0
Parameters
- percent
Specifies the weighted average shared buffer utilization low watermark.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
wait
wait
Syntax
wait seconds
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.
Platforms
All
wait-for-up-timer
wait-for-up-timer
Syntax
wait-for-up-timer seconds
no wait-for-up-timer
Context
[Tree] (config>router>mpls>lsp-template>bfd wait-for-up-timer)
[Tree] (config>router>mpls>lsp>secondary>bfd wait-for-up-timer)
[Tree] (config>router>mpls>lsp>primary>bfd wait-for-up-timer)
[Tree] (config>router>mpls>lsp>bfd wait-for-up-timer)
Full Context
configure router mpls lsp-template bfd wait-for-up-timer
configure router mpls lsp secondary bfd wait-for-up-timer
configure router mpls lsp primary bfd wait-for-up-timer
configure router mpls lsp bfd wait-for-up-timer
Description
This command configures the time to wait for a BFD to come up in seconds. This timer is applicable to SR-TE LSPs, including auto-LSPs and PCE-initiated LSPs, as well as RSVP-TE LSPs. In case of SR-TE LSPs, this timer takes effect if BFD does not come up, or BFD goes from up to down. The timer is started when BFD is first enabled on a path or BFD transitions from up to down. When the timer expires if BFD is not yet come up, then the path is torn down by removing it from the TTM and the IOM and the retry timer is started.
In case of RSVP-TE LSPs, the timer controls the following:
a path undergoing MBB when BFD is up on the original path
the initial administrative enable of an LSP
signaling retry of non-standby secondary paths
The no form of this command sets the timer to its default value.
Default
no wait-for-up-timer
Parameters
- seconds
Specifies the BFD wait for up timer in seconds.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
- configure router mpls lsp-template bfd wait-for-up-timer
All
- configure router mpls lsp secondary bfd wait-for-up-timer
- configure router mpls lsp primary bfd wait-for-up-timer
- configure router mpls lsp bfd wait-for-up-timer
wait-for-up-timer
Syntax
wait-for-up-timer seconds
no wait-for-up-timer
Context
[Tree] (config>service>epipe>spoke-sdp>bfd wait-for-up-timer)
[Tree] (config>service>vprn>interface>spoke-sdp>bfd wait-for-up-timer)
[Tree] (config>service>ies>interface>spoke-sdp>bfd wait-for-up-timer)
[Tree] (config>service>vpls>spoke-sdp>bfd wait-for-up-timer)
Full Context
configure service epipe spoke-sdp bfd wait-for-up-timer
configure service vprn interface spoke-sdp bfd wait-for-up-timer
configure service ies interface spoke-sdp bfd wait-for-up-timer
configure service vpls spoke-sdp bfd wait-for-up-timer
Description
This command configures the time interval, in seconds, that is used to wait for a BFD session to come up.
This command is triggered when a spoke-SDP is first administratively enabled and a VCCV BFD session transitions from up to down. The command is required to allow time for BFD sessions to come up, and for BFD to settle before selecting the active spoke-SDP to use in a redundant set. In the case where a VCCV BFD session is bouncing, the timer prevents excessive flapping of the operational state of a spoke-SDP.
The no form of this command disables the timer.
Default
no wait-for-up-timer
Parameters
- seconds
Specifies the wait interval, in seconds, for the BFD up timer.
Platforms
All
wait-to-restore
wait-to-restore
Syntax
wait-to-restore interval
no wait-to-restore
Context
[Tree] (config>router>mpls>mpls-tp>protection-template wait-to-restore)
Full Context
configure router mpls mpls-tp protection-template wait-to-restore
Description
This command configures the WTR timer. It determines how long to wait until the active path of an MPLS-TP LSP is restored to the working path following the clearing of a defect on the working path. It is applicable to revertive mode, only.
Default
wait-to-restore 300
Parameters
- interval
Specifies the WTR timer interval in 1 second increments.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
wait-to-restore
Syntax
wait-to-restore minutes
no wait-to-restore
Context
[Tree] (config>system>sync-if-timing wait-to-restore)
Full Context
configure system sync-if-timing wait-to-restore
Description
This command configures the time for the Wait to Restore timer. A previously failed input reference must be valid for the time specified before it is used for either the BITSout or the central clock input reference.
The no form of this command disables the timer.
Default
no wait-to-restore
Parameters
- minutes
Specifies a value representing the number of minutes for the wait to restore timeout.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
wap1x
wap1x
Syntax
wap1x
Context
[Tree] (config>app-assure>group wap1x)
Full Context
configure application-assurance group wap1x
Description
This command configures the Wireless Application Protocol (WAP) 1.X.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
warm-standby
warm-standby
Syntax
warm-standby
Context
[Tree] (config>redundancy>multi-chassis>peer warm-standby)
Full Context
configure redundancy multi-chassis peer warm-standby
Description
This command enables Oversubscribed Multi-Chassis Redundancy (OMCR) model where subscriber hosts are synchronized between the two chassis only in the control plane and are kept there (as part of the Multi-Chassis Synchronization (MCS) state) until the switchover occurs. Link or nodal failure will trigger the switchover at which point the subscriber hosts are being fully instantiated in the control and the forwarding plane. This approach allows oversubscription of the resources in the central standby (or protecting) node that is backing-up several active nodes. The total number of protected subscribers in the OMCR cluster exceeds the forwarding capacity of the protecting node. This is achievable by not fully occupying the resources for the subscriber hosts until the failure occurs.
The restoration times depend on the amount of the subscriber hosts that are affected by the switchover and it is related to the time needed for the full instantiation of the subscribers in the forwarding plane.
Although this command is configured on a peer level, the warm-standby property is a nodal characteristic. In other words, mixing of N:1 and 1:1 (hot standby) mode in the central standby node is not supported. Consequently all peers on the central standby node must be configured for warm-standby (N:1), or all peers must be configured for hot-standby (1:1) by omitting the warm-standby keyword from the configuration.
The peer of the central backup node is not aware of the redundancy model supported. In in other words, the peer of the central-backup node does not know whether it peers with a warm-standby peer or host-standby-peer.
Platforms
7750 SR
warnings
warnings
Syntax
[no] warnings
Context
[Tree] (debug>dynsvc>scripts>inst>event warnings)
[Tree] (debug>dynsvc>scripts>script>event warnings)
[Tree] (debug>dynsvc>scripts>event warnings)
Full Context
debug dynamic-services scripts instance event warnings
debug dynamic-services scripts script event warnings
debug dynamic-services scripts event warnings
Description
This command enables/disables the generation of a specific dynamic data service script debugging event output: warnings.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
warnings
Syntax
[no] warnings
Context
[Tree] (debug>vsd>scripts>event warnings)
[Tree] (debug>vsd>scripts>instance>event warnings)
Full Context
debug vsd scripts event warnings
debug vsd scripts instance event warnings
Description
This command enables/disables the generation of a specific script debugging event output: warnings.
Platforms
All
watchdog-timer
watchdog-timer
Syntax
watchdog-timer seconds
no watchdog-timer
Context
[Tree] (config>aaa>diam-peer-plcy>peer watchdog-timer)
[Tree] (config>aaa>diam-peer-plcy watchdog-timer)
Full Context
configure aaa diameter-peer-policy peer watchdog-timer
configure aaa diameter-peer-policy watchdog-timer
Description
This command configures the interval between consecutive watchdog messages. On the first timeout of the DWR, the SR OS node will resend the DWR message. The peer is still operational during this time. On the second timeout, the peer transitions into a suspended mode and the peer-failover procedure is initiated (if the peer-failover is enabled by configuration). In this state the peer is not used for new transactions. At the same time, the cooldown procedure is started which means that it would take three successful DWR/DWA message exchanges to reinstate the peer in a fully operation state.
On the third timeout, the peer is removed and its connection is closed.
This command is applicable only to legacy implementations of Diameter base in the SR OS.
The no form of this command reverts to the default.
Default
watchdog-timer 30
Parameters
- seconds
Specifies the device watchdog timer, in seconds, used by this policy peer.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
watchdog-timer
Syntax
watchdog-timer seconds
no watchdog-timer
Context
[Tree] (config>aaa>diam>node>peer watchdog-timer)
Full Context
configure aaa diameter node peer watchdog-timer
Description
Watchdog messages are used to verify liveliness of a Diameter peer. A single watchdog messages will be sent to a peer in case that no traffic is received from it within a configured watchdog-timer. This watchdog request message will solicit a watchdog answer message from the peer. If no traffic (watchdog answer or otherwise) is received from the peer in response to watchdog request while the watchdog timer is running, the peer will be put in suspicious state and a peer failover routine will be triggered.
The peer will be closed after it has been in suspicious mode for the duration of one more watchdog-timer interval without receiving any traffic from it.
Once the peer is recovered, it will take 3 successful exchanges of diameter watchdog messages (DWR/DWA) for the peer to becomes used again in Diameter forwarding. This behavior is described in RFC 3539, §3.4.1, Authentication, Authorization and Accounting (AAA) Transport Profile).
This command is not applicable to legacy implementations of Diameter base in the SR OS.
The no form of this command removes the watchdog timer value from the configuration.
Default
watchdog-timer 30
Parameters
- seconds
Specifies the device watchdog timer, in seconds, used on all connections by this peer.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
watermark
watermark
Syntax
watermark
Context
[Tree] (config>isa>video-group watermark)
Full Context
configure isa video-group watermark
Description
Commands in this context configure watermark parameters.
Platforms
7450 ESS, 7750 SR-1, 7750 SR-7/12/12e, 7750 SR-1s, 7750 SR-2s, 7750 SR-7s, 7750 SR-14s
watermarks
watermarks
Syntax
watermarks
Context
[Tree] (config>isa>wlan-gw-group watermarks)
Full Context
configure isa wlan-gw-group watermarks
Description
Commands in this context configure ISA watermark notifications.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
watermarks
Syntax
watermarks high high-percentage low low-percentage
no watermarks
Context
[Tree] (config>service>ies>sub-if>wlan-gw>pool-manager watermarks)
[Tree] (config>service>vprn>sub-if>wlan-gw>pool-manager watermarks)
Full Context
configure service ies subscriber-interface wlan-gw pool-manager watermarks
configure service vprn subscriber-interface wlan-gw pool-manager watermarks
Description
This command configures the watermarks used to determine if a new prefix should be allocated or an old prefix should be removed. A new prefix is allocated when the total usage level for the ISA reaches the high watermark. A prefix is freed if no addresses are currently in use and the usage level without this prefix would be below the low watermark.
The no form of this command resets the watermarks to its default values of 95% high and 90% low.
Default
watermarks high 95 low 90
Parameters
- high-percentage
Specifies the high watermark.
- low-percentage
Specifies the low watermark. The value must be lower than the high percentage value.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
watermarks
Syntax
watermarks high percentage-high low percentage-low
no watermarks
Context
[Tree] (config>service>vprn>nat>outside>pool watermarks)
[Tree] (config>router>nat>outside>pool watermarks)
Full Context
configure service vprn nat outside pool watermarks
configure router nat outside pool watermarks
Description
This command configures the watermarks for this NAT pool.
Default
no watermarks
Parameters
- high percentage-high
Specifies the high percentage.
- low percentage-low
Specifies the low percentage.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
watermarks
Syntax
watermarks high percentage low percentage
no watermarks
Context
[Tree] (config>isa>wlan-gw-group>nat>session-limits watermarks)
[Tree] (config>isa>nat-group>session-limits watermarks)
[Tree] (config>service>nat watermarks)
Full Context
configure isa wlan-gw-group nat session-limits watermarks
configure isa nat-group session-limits watermarks
configure service nat watermarks
Description
This command configures the ISA NAT or WLAN-GW group watermarks.
Default
no watermarks
Parameters
- high percentage
Specifies the high watermark of the number of sessions for each MDA in this NAT ISA or WLAN-GW group.
- low percentage
Specifies the low watermark of the number of sessions for each MDA in this NAT ISA or WLAN-GW group.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure isa wlan-gw-group nat session-limits watermarks
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat watermarks
- configure isa nat-group session-limits watermarks
watermarks
Syntax
watermarks high percentage-high low percentage-low
no watermarks
Context
[Tree] (config>service>nat>nat-policy>port-limits watermarks)
[Tree] (config>service>nat>up-nat-policy>port-limits watermarks)
Full Context
configure service nat nat-policy port-limits watermarks
configure service nat up-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.
- percentage-low
Specifies the low percentage.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
watermarks
Syntax
watermarks high percentage-high low percentage-low
no watermarks
Context
[Tree] (config>service>nat>up-nat-policy>session-limits watermarks)
[Tree] (config>service>nat>firewall-policy>session-limits watermarks)
[Tree] (config>service>nat>nat-policy>session-limits watermarks)
Full Context
configure service nat up-nat-policy session-limits watermarks
configure service nat firewall-policy session-limits watermarks
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.
- percentage-low
Specifies the low percentage.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat up-nat-policy session-limits watermarks
- configure service nat nat-policy session-limits watermarks
7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure service nat firewall-policy session-limits watermarks
web-service
web-service
Syntax
web-service
Context
[Tree] (config>app-assure>group>url-filter web-service)
Full Context
configure application-assurance group url-filter web-service
Description
Commands in this context configure the URL filter policy using web-service filtering. The operator must configure the web service, host name, DNS server to use, the AA interface VLAN ID, and provision the category profiles.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
web-service-url-filter
web-service-url-filter
Syntax
web-service-url-filter size
Context
[Tree] (config>isa>aa-grp>shared-resources web-service-url-filter)
Full Context
configure isa application-assurance-group shared-resources web-service-url-filter
Description
This command configures the amount of shared memory to be used by the web service URL filter cache.
Default
web-service-url-filter 100
Parameters
- size
Specifies the amount of shared memory as a percentage.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
weekday
weekday
Syntax
weekday {weekday-number [..weekday-number] | day-name [..day-name] | all}
no weekday
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.
- day-name
Specifies a day by name.
- all
Specifies all days of the week.
Platforms
All
weight
weight
Syntax
weight initial-weight-percentage weight-change-percentage
no weight
Context
[Tree] (config>subscr-mgmt>sla-profile>egress>bonding-selection weight)
Full Context
configure subscriber-mgmt sla-profile egress bonding-selection weight
Description
This command configures the initial (and also the maximum) weight of the preferred connection and the value with which it can change.
The no form of this command resets the weight to the default.
Default
weight 100 5
Parameters
- initial-weight-percentage
Specifies the initial or maximum weight, as a percentage of the offered weight.
- weight-change-percentage
Specifies the weight change, as a percentage.
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
weight
Syntax
weight weight-value
no weight
Context
[Tree] (config>qos>mlppp-profile-egress>class weight)
Full Context
configure qos mlppp-profile-egress class weight
Description
This command configures the WRR weight scheduling parameter for each MLPPP class queue for this profile.
Parameters
- weight-value
Specifies the weight scheduling parameter.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
weight
Syntax
weight weight
no weight
Context
[Tree] (config>qos>mc-fr-profile-egress>class weight)
Full Context
configure qos mc-fr-profile-egress class weight
Description
This command configures the WRR weight scheduling parameter for each Frame Relay scheduling class queue for this profile.
The weight parameter is not applicable to class 0 because the class 0 queue is serviced by the scheduler with the highest priority all the time over all other class queues.
After Class 0 queue packets are serviced, Class 1 queue packets are the next priority up to a rate of MIR. Beyond MIR, Class1, Class2, and Class 3 queues are serviced in proportion to the configured weights.
Parameters
- weight
Specifies the weight schedule.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
weight
Syntax
weight weight
no weight
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 in order 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 will be 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.
Platforms
All
weight-down
weight-down
Syntax
[no] weight-down lag-ports-down-weight
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-threshold or port threshold. The command is required for correct operation on mixed port-speed LAGs and can be used for non-mixed port-speed LAGs as well.
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.
Platforms
All
weight-threshold
weight-threshold
Syntax
weight-threshold value [action { dynamic-cost | static-cost | down}] [ cost static-cost]
no weight-threshold
Context
[Tree] (config>lag weight-threshold)
Full Context
configure lag weight-threshold
Description
This command configures the behavior for the Link Aggregation Group (LAG) if the total weight of operational links is equal to or below the configured threshold level. The command can be used for mixed port-speed LAGs and for LAGs with all ports of equal speed.
The no form of this command disables the weight-threshold operation in LAG.
Default
weight-threshold 0 action down
Parameters
- value
The decimal integer threshold number of operational links for the LAG at or below which the configured action will be invoked. If the number of operational links exceeds the weight-threshold value, any action taken for being below the threshold value will cease.
- action
Specifies the action to take if the number of active links in the LAG is at or below the threshold value.
- dynamic-cost
Specifies that dynamic costing is activated. As a result the LAG remains operationally up with a cost relative to the number of operational links. The link is only regarded as operationally down when all links in the LAG are down.
- static-cost
Specifies that static costing will be activated. As a result, the LAG will remain operationally up with the configured cost, regardless of the number of operational links. The link will only be regarded as operationally down when all links in the LAG are down.
- down
Specifies the LAG is brought operationally down if the number of operational links is equal to or less than the configured threshold value. The LAG is only regarded as up once the number of operational links exceeds the configured threshold value.
- static-cost
The decimal integer static cost of the LAG.
Platforms
All
weighted-ecmp
weighted-ecmp
Syntax
[no] weighted-ecmp
Context
[Tree] (config>service>vpls>bgp-evpn>mpls>auto-bind-tunnel weighted-ecmp)
[Tree] (config>service>vprn>bgp-evpn>mpls>auto-bind-tunnel weighted-ecmp)
[Tree] (config>service>epipe>bgp-evpn>mpls>auto-bind-tunnel weighted-ecmp)
[Tree] (config>service>vprn>bgp-ipvpn>mpls>auto-bind-tunnel weighted-ecmp)
Full Context
configure service vpls bgp-evpn mpls auto-bind-tunnel weighted-ecmp
configure service vprn bgp-evpn mpls auto-bind-tunnel weighted-ecmp
configure service epipe bgp-evpn mpls auto-bind-tunnel weighted-ecmp
configure service vprn bgp-ipvpn 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
All
weighted-ecmp
Syntax
[no] weighted-ecmp
Context
[Tree] (configure>service>vpls>bgp-evpn>ip-route-link-bw weighted-ecmp)
[Tree] (configure>service>vprn>bgp-evpn>mpls>evpn>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 that are configured with an evpn-link-bandwidth add-to-received-bgp weight.
The no form of this command disables EVPN link bandwidth extended community.
Default
no weighted-ecmp
Platforms
All
weighted-ecmp
Syntax
weighted-ecmp [strict]
no weighted-ecmp
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
All
weighted-ecmp
Syntax
[no] weighted-ecmp
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
All
weighted-ecmp
Syntax
weighted-ecmp [strict]
no weighted-ecmp
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
All
weighted-ecmp
Syntax
[no] weighted-ecmp
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
All
weighted-ecmp
Syntax
[no] weighted-ecmp
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
All
wide-metrics-only
wide-metrics-only
Syntax
[no] wide-metrics-only
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
All
wide-metrics-only
Syntax
[no] wide-metrics-only
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
All
width
width
Syntax
width width
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.
Platforms
All
width
Syntax
width width
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.
Platforms
All
wifi-num-attached-ues
wifi-num-attached-ues
Syntax
[no] wifi-num-attached-ues
Context
[Tree] (config>subscr-mgmt>acct-plcy>include wifi-num-attached-ues)
[Tree] (config>subscr-mgmt>auth-plcy>include wifi-num-attached-ues)
Full Context
configure subscriber-mgmt radius-accounting-policy include-radius-attribute wifi-num-attached-ues
configure subscriber-mgmt authentication-policy include-radius-attribute wifi-num-attached-ues
Description
When enabled, this command indicates the number of UEs connected to the tunnel to which the radius message applies to. For session/host accounting this is the tunnel of the associated UE. For queue-instance accounting this attribute will not be included.
The no form of this command disables including the RADIUS Alc-Num-Attached-UEs VSA.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
wifi-rssi
wifi-rssi
Syntax
[no] wifi-rssi
Context
[Tree] (config>subscr-mgmt>acct-plcy>include-radius-attribute wifi-rssi)
Full Context
configure subscriber-mgmt radius-accounting-policy include-radius-attribute wifi-rssi
Description
This command enables the inclusion of the 802.11 Received Signal Strength Indication attribute.
The no form of this command reverts to the default.
Default
no wifi-rssi
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
wifi-rssi
Syntax
[no] wifi-rssi
Context
[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes wifi-rssi)
Full Context
configure aaa isa-radius-policy acct-include-attributes wifi-rssi
Description
This command enables including the Alc-RSSI.
Default
no wifi-rssi
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
wifi-ssid-vlan
wifi-ssid-vlan
Syntax
[no] wifi-ssid-vlan
Context
[Tree] (config>aaa>isa-radius-plcy>acct-include-attributes wifi-ssid-vlan)
[Tree] (config>subscr-mgmt>auth-plcy>include wifi-ssid-vlan)
[Tree] (config>subscr-mgmt>acct-plcy>include wifi-ssid-vlan)
[Tree] (config>aaa>isa-radius-plcy>auth-include-attributes wifi-ssid-vlan)
Full Context
configure aaa isa-radius-policy acct-include-attributes wifi-ssid-vlan
configure subscriber-mgmt authentication-policy include-radius-attribute wifi-ssid-vlan
configure subscriber-mgmt radius-accounting-policy include-radius-attribute wifi-ssid-vlan
configure aaa isa-radius-policy auth-include-attributes wifi-ssid-vlan
Description
This command enables including the per-SSID VLAN ID in a Alc-Wlan-SSID-VLAN VSA.
The no form of this command disables including the per-SSID VLAN ID in Alc-Wlan-SSID-VLAN VSA.
Default
no wifi-ssid-vlan
Platforms
7450 ESS, 7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure aaa isa-radius-policy acct-include-attributes wifi-ssid-vlan
- configure aaa isa-radius-policy auth-include-attributes wifi-ssid-vlan
7750 SR, 7750 SR-e, 7750 SR-s, VSR
- configure subscriber-mgmt radius-accounting-policy include-radius-attribute wifi-ssid-vlan
- configure subscriber-mgmt authentication-policy include-radius-attribute wifi-ssid-vlan
wildcard-spmsi
wildcard-spmsi
Syntax
wildcard-spmsi
no wildcard-spmsi
Context
[Tree] (config>service>vprn>mvpn>pt>inclusive wildcard-spmsi)
Full Context
configure service vprn mvpn provider-tunnel inclusive wildcard-spmsi
Description
This command enables RFC 6625 (C-*, C-*) S-PMSI functionality for NG-MVPN. When enabled, (C-*, C-*) S-PMSI is used instead of I-PMSI for this MVPN. Wildcard S-PMSI uses the I-PMSI LSP template.
auto-rp-discovery cannot be enabled together with mdt-type sender-only or mdt-type receiver-only, or wildcard-spmsi configurations.
The no form disables the (C-*, C-*) S-PMSI functionality.
Default
no wildcard-spmsi
Platforms
All
window
window
Syntax
window minutes
Context
[Tree] (config>card>mda>egress-xpl window)
Full Context
configure card mda egress-xpl window
Description
This command configures the Error Window value used by the fail-on-error feature.
Default
window 60
Parameters
- minutes
Specifies the time, in minutes, that the MDA can experience frequent Egress XPL Errors. When fail-on-error is enabled, if more than xpl-errors Egress XPL errors per minute occur on the MDA for the specified number of consecutive minutes, the MDA will be put in the failed state.
The window value cannot be changed while fail-on-error is enabled for this MDA.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
window
Syntax
window minutes
Context
[Tree] (config>card>mda>ingress-xpl window)
Full Context
configure card mda ingress-xpl window
Description
This command configures the Error Window value used by the fail-on-error feature.
Default
window 60
Parameters
- minutes
Specifies the time, in minutes, that the MDA can experience frequent Ingress XPL Errors. When fail-on-error is enabled, if more than xpl-errors Ingress XPL errors per minute occur on the MDA for the specified number of consecutive minutes, the MDA will be put in the failed state.
The window value cannot be changed while fail-on-error is enabled for this MDA.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
window
Syntax
window deciseconds
Context
[Tree] (config>port>ethernet>efm-oam>link-mon>errored-frame window)
Full Context
configure port ethernet efm-oam link-monitoring errored-frame window
Description
This command defines the size of the window using a 100ms base deciseconds. Errors are accumulated until the end of the window. At the end of the window the actual errors are compared to the thresholds to determine if a threshold has been crossed. There is no mid-window threshold checking. The window represents a unique non-overlapping period of time.
Default
window 10
Parameters
- deciseconds
The number of 100ms increments. Must be specified in increments of 10 (full seconds).
Platforms
All
window
Syntax
window packets
Context
[Tree] (config>port>ethernet>efm-oam>link-mon>errored-frame-period window)
Full Context
configure port ethernet efm-oam link-monitoring errored-frame-period window
Description
This command defines the size of the window based on a packet receive rate. The minimum serviceable rate is the number of minimum size packets that can be received in one second. The window receive count value will be polled at a minimum one second intervals to see if the window size has been reached. Errors are accumulated until the end of the window. At the end of the window the actual errors are compared to the thresholds to determine if a threshold has been crossed. There is no mid-window threshold checking. The window represents a unique non-overlapping period of time.
Parameters
- packets
Specifies the number of received packets in one second.
Platforms
All
window
Syntax
window deciseconds
Context
[Tree] (config>port>ethernet>efm-oam>link-mon>errored-frame-seconds window)
Full Context
configure port ethernet efm-oam link-monitoring errored-frame-seconds window
Description
This command defines the size of the window using a 100ms base deciseconds. Errored seconds are accumulated until the end of the window. At the end of the window, the actual errors are compared to the thresholds to determine if a threshold has been crossed. There is no mid-window threshold checking. The window represents a unique non-overlapping period of time.
Parameters
- deciseconds
Specifies the number of 100 ms increments. Must be specified in increments of 10 (full seconds).
Platforms
All
window
Syntax
window deciseconds
Context
[Tree] (config>port>ethernet>efm-oam>link-mon>errored-symbols window)
Full Context
configure port ethernet efm-oam link-monitoring errored-symbols window
Description
This command defines the size of the window using a 100ms base deciseconds. The time value is converted to a number of symbols for the underlying medium. Errors are accumulated until the end of the window. At the end of the window, the actual errors are compared to the thresholds to determine if a threshold has been crossed. There is no mid-window threshold checking. The window represents a unique non-overlapping period of time.
Parameters
- deciseconds
Specifies the number of 100ms increments in increments of 10 (full seconds).
Platforms
All
window-integrity
window-integrity
Syntax
window-integrity percentage
no window-integrity
Context
[Tree] (config>oam-pm>streaming>delay-template window-integrity)
Full Context
configure oam-pm streaming delay-template window-integrity
Description
This command specifies the integrity of the sample window. A percentage value that suggests the measurement has enough samples (integrity) to be considered representative for that sample window. The configured percentage considers the interval of the test PDUs, and the length of the sample window to determine the number of packets required in the sample.
(((window-integrity %) x (sample-window length (s) x pps per test (interval)).
Ensure that the percentage and the combination of sample window and packet per second per test interval produces the desired results.
If the number of samples in the sample window are equal to or greater than the computed number of required samples, then the value has integrity and the suspect flag is set to false for that streamed result.
If the count is less than the computed number of required samples, then the suspect flag is set to true for that streamed result.
Regardless of the integrity, the average values are streamed. It is up to the higher level systems to interrogate the suspect flag and determine if the value that is set should be used, discarded, or reported separately.
The no form of this command reverts to the default.
Default
window-integrity 50
Parameters
- percentage
Specifies the window integrity percentage.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
window-integrity
Syntax
window-integrity percent
no window-integrity
Context
[Tree] (config>test-oam>link-meas>template>asw window-integrity)
Full Context
configure test-oam link-measurement measurement-template aggregate-sample-window window-integrity
Description
This command determines whether the aggregate sample window is integral based on the number of samples received from the sample window, comparing the number of samples to the percentage configured.
The configured percentage translates to a required sample window count that must be included in the aggregate sample window. The range is from 0 to 100. The number of samples is computed as follows:
(window-integrity (%)) x (((aggregate-sample-window length (s)) / (sample-window length (s)))
For an aggregate sample window that does not reach the integrity, the value is not considered as representative and is used for threshold comparison.
If the number of samples in the aggregate sample window are equal to or greater than the computed number of required samples, the sample window has integrity and the aggregate sample window result is compared to configured sample window thresholds.
If the count is less than the computed number of required samples, the aggregate sample window does not have integrity and the aggregate sample window results are compared to configured sample window thresholds.
If this parameter is not configured, integrity checking is disabled and all results are compared to the configured thresholds.
The no form of this command disables integrity checking.
Default
window-integrity 0
Parameters
- percent
Specifies the percentage of successful sent and received request-response pairs.
Zero indicates any amount of integrity is acceptable for report to the routing engine.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
window-integrity
Syntax
window-integrity percent
no window-integrity
Context
[Tree] (config>test-oam>link-meas>template>sw window-integrity)
Full Context
configure test-oam link-measurement measurement-template sample-window window-integrity
Description
This command specifies the integrity of the sample window. A percentage value indicates when the sample window has enough samples to be considered representative for that window (integrity). The configured percentage considers the interval of probes and the length of the sample window to determine the number of packets required in the sample:
(window-integrity (%)) x (((sample-window length (s)) / pps per test (interval)))
Ensure that the percentage and the combination of sample window and the packet-per- second per test interval produces the desired results.
If the number of samples in the sample window are equal to or greater than the computed number of required samples, the sample window has integrity and the sample window result is compared to the configured sample window thresholds.
If the count is less than the computed number of required samples, the sample window does not have integrity and the sample window results are not compared to configured sample window thresholds.
If this parameter is not configured, integrity checking is disabled and all results are compared to the configured thresholds.
The no form of this command disables integrity checking.
Default
window-integrity 0
Parameters
- percent
Specifies the percentage of successful sent and received request-response pairs.
A value of 0 indicates any amount of integrity acceptable for report to the routing engine.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
window-size
window-size
Syntax
window-size seconds
no window-size
Context
[Tree] (config>port>ethernet>sym-mon window-size)
Full Context
configure port ethernet symbol-monitor window-size
Description
This command specifies sliding window size over which the symbols are sampled to detect signal failure or signal degraded conditions.
Default
window-size 10
Parameters
- seconds
Specifies the size of the sliding window in seconds over which the errors are measured.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
window-size
Syntax
window-size seconds
no window-size
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.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
wlan-gw
wlan-gw
Syntax
wlan-gw
Context
[Tree] (config>router>radius-proxy>server wlan-gw)
[Tree] (config>service>vprn wlan-gw)
[Tree] (config>service>ies>sub-if>grp-if wlan-gw)
[Tree] (config>router wlan-gw)
[Tree] (config>service>vprn>sub-if>grp-if wlan-gw)
[Tree] (config>service>vpls wlan-gw)
[Tree] (config>subscr-mgmt wlan-gw)
[Tree] (config>service>vprn>radius-proxy>server wlan-gw)
Full Context
configure router radius-proxy server wlan-gw
configure service vprn wlan-gw
configure service ies subscriber-interface group-interface wlan-gw
configure router wlan-gw
configure service vprn subscriber-interface group-interface wlan-gw
configure service vpls wlan-gw
configure subscriber-mgmt wlan-gw
configure service vprn radius-proxy server wlan-gw
Description
Commands in this context configure WLAN GW parameters.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
wlan-gw
Syntax
[no] wlan-gw
Context
[Tree] (debug wlan-gw)
Full Context
debug wlan-gw
Description
This node contains all the parameters to set up specific call-trace debug sessions for WLAN-GW. The no form of this command will stop all configured WLAN-GW traces.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
wlan-gw
Syntax
wlan-gw
Context
[Tree] (config>li>li-source wlan-gw)
Full Context
configure li li-source wlan-gw
Description
This command enables the wlan-gw context to configure li-source related parameters.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
wlan-gw-group
wlan-gw-group
Syntax
wlan-gw-group nat-group-id
no wlan-gw-group
Context
[Tree] (config>service>vprn>wlan-gw>xconnect wlan-gw-group)
[Tree] (config>router>wlan-gw>xconnect wlan-gw-group)
Full Context
configure service vprn wlan-gw xconnect wlan-gw-group
configure router wlan-gw xconnect wlan-gw-group
Description
This command configures the identifier of the WLAN Gateway ISA group that processes the cross-connect.
The no form of this command removes the NAT group IP from the cross-connect configuration.
Parameters
- nat-group-id
Specifies the identifier of the ISA group.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
wlan-gw-group
Syntax
wlan-gw-group group-id
no wlan-gw-group
Context
[Tree] (config>router>vrgw>lanext wlan-gw-group)
Full Context
configure router vrgw lanext wlan-gw-group
Description
This command specifies the WLAN GW group that is used for HLE services.
The no form of this command removes the group from the configuration.
Parameters
- group-id
Specifies the WLAN GW group ID.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
wlan-gw-group
Syntax
wlan-gw-group wlan-gw-group-id [member member-id]
no wlan-gw-group
Context
[Tree] (config>subscr-mgmt>wlan-gw>ue-query wlan-gw-group)
Full Context
configure subscriber-mgmt wlan-gw ue-query wlan-gw-group
Description
This command enables matching on UEs, based on the WLAN-GW group ID and, optionally, the specific ISA member they are installed on.
The no form of this command disables matching on the WLAN-GW group.
Default
no wlan-gw-group
Parameters
- wlan-gw-group-id
Specifies the WLAN-GW group ID.
- member-id
Specifies the ISA member ID within the group.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
wlan-gw-group
Syntax
wlan-gw-group group-id [create] [ redundancy unit]
no wlan-gw-group group-id
Context
[Tree] (config>isa wlan-gw-group)
Full Context
configure isa wlan-gw-group
Description
This command creates a WLAN GW group that contains a set of ISAs to be used in WLAN-GW functionality. A WLAN-GW group can also be used where a NAT group is expected. The WLAN-GW group ID shares the same number space with the NAT group.
At most, one WLAN-GW group may be configured.
The optional redundancy parameter determines the provisioning and redundancy mode.
IOM mode
A whole IOM is added to the group. The IOM must be fully provisioned with BB ISA modules. In IOM mode, when a single ISA fails, the entire IOM is considered to have failed and all subscribers are recovered on a backup IOM.
ISA mode
BB ISA modules are added separately with no restriction put on other MDAs in the IOM. When a single ISA fails, a backup ISA will try to recover as many subscribers as possible but may run out of resources (for example, queues, policers, host entries) during the recovery process. It is recommended to pair ISAs with MDAs and services that do not consume many IOM resources.
The no form of this command removes the group.
Parameters
- group-id
Specifies WLAN Gateway Integrated Service Adaptor (ISA) Groups.
- unit
Specifies the provisioning and redundancy mode.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
wlan-gw-group
Syntax
wlan-gw-group group-id
no wlan-gw-group
Context
[Tree] (config>service>ies>sub-if>grp-if>wlan-gw wlan-gw-group)
[Tree] (config>service>vprn>sub-if>grp-if>wlan-gw wlan-gw-group)
Full Context
configure service ies subscriber-interface group-interface wlan-gw wlan-gw-group
configure service vprn subscriber-interface group-interface wlan-gw wlan-gw-group
Description
This command specifies the ID of the wlan-gw-group that the wlan-gw gateway binds to.
The no form of this command removes the value from the wlan-gw configuration.
Parameters
- group-id
Specifies the ISA WLAN-GW group.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
wlan-gw-group
Syntax
wlan-gw-group nat-group-id
no wlan-gw-group
Context
[Tree] (config>service>ies>sub-if>wlan-gw>pool-manager wlan-gw-group)
[Tree] (config>service>vprn>sub-if>wlan-gw>pool-manager wlan-gw-group)
Full Context
configure service ies subscriber-interface wlan-gw pool-manager wlan-gw-group
configure service vprn subscriber-interface wlan-gw pool-manager wlan-gw-group
Description
This command specifies the ISA WLAN gateway group.
Parameters
- nat-group-id
Specifies the identifier of the WLAN gateway group.
Platforms
7750 SR, 7750 SR-e, 7750 SR-s, VSR
working-bundle
working-bundle
Syntax
[no] working-bundle bundle-id
Context
[Tree] (config>port>multilink-bundle working-bundle)
Full Context
configure port multilink-bundle working-bundle
Description
This command configures a working bundle that is part of this BPGrp.
Parameters
- bundle-id
Specifies the working multilink bundle in the bundle protection group. The command syntax must be configured as follows:
Platforms
7450 ESS, 7750 SR-7/12/12e
working-circuit
working-circuit
Syntax
working-circuit port-id [number number]
no work-circuit [number number]
Context
[Tree] (config>port>aps working-circuit)
Full Context
configure port aps working-circuit
Description
This command configures a physical port that will act as the working circuit for this APS group. The working circuit port must contain only the default configuration and cannot be part of another APS group. The working circuit must be created before the protection circuit.
When a port is a working circuit of an APS group, the configuration available under config>port port-id context (including submenus) is not allowed for that port unless it is a part of the noted exceptions.
When a port is being configured as a working circuit of an APS group, all common configuration as described above and all service configurations related to the APS port is operationally inherited by the working circuit from the aps- group-id. If the working circuit cannot inherit that configuration, for example, due to resource limitations, the configuration attempt fails and an error is returned to the user.
Before a working circuit can be removed from an APS group, the working circuit port must be shutdown. The inherited configuration for the circuit and APS operational commands for that circuit are not preserved when the circuit is removed from the APS group.
Note that all configurations for aps-group-id under the config>port context and its submenus and all configuration for services that use this aps- group-id is preserved as a non-activated configuration since the APS group no longer has any physical circuits assigned.
The no form of this command removes the working-circuit. The working circuit can only be removed from the configuration after the protect circuit has been removed.
Parameters
- port-id
Specifies the physical port that will act as the working circuit for this APS group in the following format:
port-id
slot/mda/port
eth-sat-id
esat-id/slot/port
esat
keyword
id
1 to 20
pxc-id
pxc-id.sub-port
pxc
keyword
id
1 to 64
sub-port
a, b
- number
Specifies the APS channel number; value is 1 or 2.
Modifying Hold-Down Timer Values
Note that for APS configurations, the config>port>sonet-sdh hold-time down and config>port>sonet-sdh hold-time up default values are 100 ms and 500 ms respectively. But, if there is a large difference in the transmission delay between the APS working () and protect line ( config>port>aps protect-circuit), it is highly recommended that you increase the default timer on the working line accordingly with the transmission delay present on the protect line.
The following output shows an example of the timers on POS interfaces.
A:NS044050253# show port aps-1 =============================================================================== SONET/SDH Interface =============================================================================== Description : APS Group Interface : aps-1 Speed : oc3 Admin Status : up Oper Status : up Physical Link : Yes Loopback Mode : none Single Fiber Mode : No Clock Source : node Framing : sonet Last State Change : 04/11/2007 13:53:01 Port IfIndex : 1358987264 J0 String : 2/1/5 7750-SR-7 Section Trace Mode : string Rx S1 Byte : 0x00 (stu) Rx K1/K2 Byte : 0x00/0x00 Tx S1 Byte : 0x0f (dnu) Tx DUS/DNU : disabled Rx J0 String (Hex) : 81 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Cfg Alarm : loc lais lrdi ss1f lb2er-sd lb2er-sf slof slos lrei Alarm Status : Hold time up : 500 milliseconds Hold time down : 100 milliseconds =============================================================================== Port Statistics =============================================================================== Input Output ------------------------------------------------------------------------------- Packets 6670498 3804661 Discards 0 0 Unknown Proto Discards 0 =============================================================================== A:NS044050253# For unprotected port these timer are different: A:NS044050253# show port 2/2/2 =============================================================================== SONET/SDH Interface =============================================================================== Description : OC-48 SONET/SDH Interface : 2/2/2 Speed : oc48 Admin Status : up Oper Status : up Physical Link : Yes Loopback Mode : none Single Fiber Mode : No APS Group : none APS Role : none Clock Source : loop Framing : sonet Last State Change : 04/11/2007 14:53:53 Port IfIndex : 37814272 J0 String : 0x01 Section Trace Mode : byte Rx S1 Byte : 0x00 (stu) Rx K1/K2 Byte : 0x00/0x00 Tx S1 Byte : 0x0f (dnu) Tx DUS/DNU : disabled Rx J0 String (Hex) : af 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Cfg Alarm : loc lrdi lb2er-sf slof slos Alarm Status : Hold time up : 500 milliseconds Hold time down : 0 milliseconds Transceiver Data Transceiver Type : SFP Model Number : SFP-OC48-SR1 Transceiver Code : OC48 SR Laser Wavelength : 1310 Diag Capable : yes Connector Code : LC Vendor OUI : 00:01:9c Manufacture date : 2004/08/20 00:00:00 Media : SONET/SDH Serial Number : 6331000705 Part Number : CT2-MS1LBTD32Z2 Optical Compliance*: 00:01:00:00:00:00:00:00 Link Len 9u : 2 kms Link Len Cu : 0 m Link Len 9u : 20 * 100m Link Len 62.5u : 0 * 10m Link Len 50u : 0 * 10m =============================================================================== Port Statistics =============================================================================== Input Output ------------------------------------------------------------------------------- Packets 3870094 6656408 Discards 0 0 Unknown Proto Discards 0 =============================================================================== A:NS044050253#
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e
working-path
working-path
Syntax
working-path path-name
no working-path
Context
[Tree] (config>router>gmpls>lsp working-path)
Full Context
configure router gmpls lsp working-path
Description
This command specifies the working path for a GMPLS LSP. One working path must be specified for each GMPLS LSP. The path-name parameter must correspond to a path defined under config>router>gmpls>path.
The no form of the command removes the working-path definition.
Default
no working-path
Parameters
- path-name
Specifies the name of the path used by the working path.
Platforms
7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
working-tp-path
working-tp-path
Syntax
[no] working-tp-path
Context
[Tree] (config>router>mpls>lsp working-tp-path)
Full Context
configure router mpls lsp working-tp-path
Description
This command creates or edits the working path for an MPLS-TP LSP. At least one working path (but not more than one working path) must be created for an MPLS-TP LSP. If MPLS-TP linear protection is also configured, then this is the path that is used as the default working path for the LSP, and it must be created prior to the protect path. The working-tp-path can only be deleted if no protect-tp-path exists for the LSP.
The following commands are applicable to the working-tp-path: lsp-num, in-label, out-label, mep, shutdown.
Default
no working-tp-path
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
wpp
wpp
Syntax
wpp
Context
[Tree] (config>subscr-mgmt>loc-user-db>ipoe>host wpp)
Full Context
configure subscriber-mgmt local-user-db ipoe host wpp
Description
Commands in this context configure WPP parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
wpp
Syntax
wpp
no wpp
Context
[Tree] (config>service>vprn>sub-if>grp-if wpp)
[Tree] (config>aaa wpp)
[Tree] (config>service>ies>sub-if>grp-if wpp)
Full Context
configure service vprn subscriber-interface group-interface wpp
configure aaa wpp
configure service ies subscriber-interface group-interface wpp
Description
Commands in this context configure Wireless Portal Protocol (WPP) parameters.
The no form of the command removes configuration under WPP.
Default
no wpp
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
wpp
Syntax
[no] wpp
Context
[Tree] (debug>router wpp)
Full Context
debug router wpp
Description
Commands in this context configure WPP debugging parameters.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, VSR
wrap-around
wrap-around
Syntax
[no] wrap-around
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
All
wred-queue
wred-queue
Syntax
wred-queue [policy slope-policy-name] [mode mode] [slope-usage slope-usage]
no wred-queue
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.
- slope-usage
Specifies congestion control to be used.
Platforms
All
wred-queue
Syntax
wred-queue [policy slope-policy-name] [ mode {native | pool-per-queue}] [ slope-usage {default | exceed-low}]
no wred-queue
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.
- slope-usage {default | exceed-low}
Specifies the type of congestion control to be used.
Platforms
All
wred-queue-control
wred-queue-control
Syntax
wred-queue-control
Context
[Tree] (config>card>fp>egress wred-queue-control)
Full Context
configure card fp egress wred-queue-control
Description
Commands in this context configure the aggregate WRED queue parameters for all WRED queues on an egress forwarding plane.
Platforms
7450 ESS, 7750 SR, 7750 SR-a, 7750 SR-e, 7750 SR-s, 7950 XRS
writable-running
writable-running
Syntax
[no] writable-running
Context
[Tree] (config>system>netconf>capabilities writable-running)
Full Context
configure system netconf capabilities writable-running
Description
This command allows the SR OS NETCONF server to access the running configuration datastore.
When configure system management-interface configuration-mode is set to model-driven, the writable-running capability is disabled, even if this command is configured.
The no form of the command disables the SR OS NETCONF server from accessing the running datastore. Requests that reference the running datastore as a target return an error. When a NETCONF client establishes a new session, the writable-running capability is not advertised in the SR OS NETCONF Hello message.
Default
no writable-running
Platforms
All
write
write
Syntax
write {user-name | broadcast} message
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.
- 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 (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
Platforms
All
write-algorithm
write-algorithm
Syntax
write-algorithm {hash | hash2 | custom | cleartext}
no write-algorithm
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
All
wrr-group
wrr-group
Syntax
wrr-group group-id sched-class class-id
wrr-group group-id unattached
no wrr-group group-id
Context
[Tree] (config>qos>hs-attachment-policy wrr-group)
Full Context
configure qos hs-attachment-policy wrr-group
Description
This command defines how the specified group ID is attached to the scheduler. A WRR group may have one of two attachment states:
directly attached to a scheduler class
unattached
A WRR group provides a weighted scheduling context for its member queues, collapsing the queues into a single scheduling class.
The following WRR membership restrictions apply:
Two groups are supported: WRR-group 1 and WRR-group 2.
Up to six of the eight queues can become members of WRR groups (the sum of the membership of both groups cannot exceed six queues). All six queues can be placed in a single WRR group or they can be spread between the two groups.
All queues within a group must have contiguous queue IDs.
When both groups are configured to have queue members, the queue IDs in group 1 must be lower than the queue IDs in group 2.
The queue queue-id attachment command is used to define WRR group membership.
The no form of the command reverts to the default unattached attachment state for the group ID.
Default
wrr-group group-id unattached
Parameters
- group-id
Specifies the WRR group identifier. The group-id parameter is required when executing the wrr-group attachment command.
- sched-class
Specifies a direct attachment between the WRR group and one of the six scheduling classes. The sched-class and unattached keywords are mutually exclusive. One of the keywords must be specified when the wrr-group attachment command is executed.
- class-id
Specifies the scheduling class associated with this WRR group. The sched-class keyword specifies the attachment between the group ID and one of the six scheduling classes. A value of 1 through 6 must accompany the sched-class keyword representing the WRR group’s attached scheduling class. Only one queue or WRR group can be attached to a given scheduling class. If another queue or a WRR group is currently attached to the specified scheduling class, the wrr-group attachment command fails and the current attachment for the group-id is unchanged.
- unattached
Indicates that the group ID is not attached to any scheduling class or WRR group. Queues that are members of the unattached WRR group do not forward any packets. The sched-class and unattached keywords are mutually exclusive. One of the keywords must be specified when the wrr-group attachment command is executed.
Platforms
7750 SR-7/12/12e
wtr-annexb
wtr-annexb
Syntax
wtr-annexb minutes
Context
[Tree] (config>port>aps wtr-annexb)
Full Context
configure port aps wtr-annexb
Description
This command waits to restore for Annex B mode operation. The delay after which the newly active section becomes the primary section after a switch-over from the primary section to the secondary section occurs and the switch request clears normally.
Parameters
- minutes
Specifies the time, in minutes, to wait to restore for Annex B mode operation.
Platforms
7450 ESS, 7750 SR-7/12/12e, 7750 SR-a, 7750 SR-e