Foundry NetIron M2404C and M2404F Metro Access Switches
Configuring HQoS (Rev.03)
Configuration
© 2008 Foundry Networks, Inc.
Page 69 of 98
Command
Description
shaper-profile
(in HQoS Configuration mode)
Creates a shaper profile.
shaper-profile
(in Scheduler configuration mode)
Assigns a shaping profile to a scheduler.
shaper-profile
(in Network queue configuration
mode)
Assigns a shaping profile to a network queue.
wred-profile
(in HQoS configuration mode)
Defines the WRED profiles.
green
Configures WRED parameters for green traffic.
yellow
Configures WRED parameters for yellow traffic.
wred-profile
(in Queue configuration mode)
Applies a WRED profile to service ingress/service
egress/network queue.
Configuring WFQ Scheduling Profiles
WFQ scheduling profiles are configured for:
•
service ingress/egress L2 schedulers (scheduler-wfq-profiles)
•
network queues (network-wfq-profiles)
•
service queues (service-wfq-profiles).
WFQ scheduling profiles are used for assigning scheduling weight values to in-profile and out-of-
profile traffic. WFQ profiles are configured in HQoS Configuration mode. Service WFQ profiles
contain just one weight (applied to both in-profile and out-of-profile traffic). Rounding can be
applied to the configured value. Other WFQ profiles, scheduler and network WFQ profiles, contain
two weights for committed and excess traffic and the full range of values from 1 to 220 is
accepted.
NOTE
Weight assigned to service queues can be rounded to the nearest value accepted by
the underlying hardware. Users will receive notification of the real value
configured in hardware.
Traffic is classified as committed or excessive depending on the shaper that is
applied to the respective entity.
The
scheduler-wfq-profile
command, in HQoS Configuration mode, creates a WFQ profile that
can be assigned to a scheduler.
The
no
form of this command removes the WFQ profile.
Command Syntax
device-name
(config hqos)#
scheduler-wfq-profile
{
ingress
|
egress
}
<scheduler-wfq-profile-id> weight <weight> cir-weight <cir-weight>
device-name
(config hqos)#
no
scheduler-wfq-profile
{
ingress
|
egress
}
<scheduler-wfq-profile-id>