
Configuring Global QoS Parameters Configuring QoS
page 26-14 OmniSwitch 6800/6850/9000 Network Configuration Guide June 2006
Setting the Global Default Servicing Mode
The servicing mode refers to the queuing scheme used to shape traffic on destination (egress) ports. There
are three schemes available: one strict priority and two weighted fair queueing (WFQ) options. By default
all switch ports are set to use strict priority queuing.
The qos default servicing mode command is used to set the default queuing scheme for all switch ports.
For example, the following command selects wrr—a WFQ scheme that uses 8 weighted round robin
(WRR) queues—as the default servicing mode:
-> qos default servicing mode wrr
For more information about the available queuing schemes and configuring the servicing mode for indi-
vidual ports, see “Prioritizing and Queue Mapping” on page 26-19.
Using the QoS Log
The QoS software in the switch creates its own log for QoS-specific events. You may modify the number
of lines in the log or change the level of detail given in the log. The PolicyView application, which is used
to create QoS policies stored on an LDAP server, may query the switch for log events; or log events can be
immediately available to the PolicyView application via a CLI command. Log events may also be
forwarded to the console in real time.
What Kind of Information Is Logged
The debug qos command controls what kind of information will be displayed in the log. The qos log level
command determines how specific the log messages will be. See “Log Detail Level” on page 26-15.
By default, only the most basic QoS information is logged. The types of information that may be logged
includes rules, Layer 2 and Layer 3 information, etc. For a detailed explanation about the types of informa-
tion that may be logged, see the OmniSwitch CLI Reference Guide. A brief summary of the available
keywords is given here:
To display information about any QoS rules on the switch, enter debug qos rule:
-> debug qos rules
To change the type of debugging, use no with the relevant type of information that you want to remove.
For example:
-> debug qos no rule
debug qos keywords
info
config
rule
main
route
hre
port
msg
sl
mem
cam
mapper
flows
queue
slot
l2
l3
classifier
sem
pm
ingress
egress
nimsg
Comentarios a estos manuales