QoS Policy Commands
OmniSwitch CLI Reference Guide November 2009 page 39-199
Examples
-> show active policy rule
Policy  From  Prec Enab  Act Refl Log Trap Save Matches Green Yellow Red
R1       cli    0  Yes   Yes   No  No  Yes  Yes  6000  3000 2000  1000
(L2/3):                  c1 -> a1
 R2  cli  0  Yes   Yes   No  No  Yes  Yes 0 0 0 0
  (L2/3):                               C2 -> QoS_Action1
 R3  cli  0  Yes   Yes   No  No  Yes  Yes  0 0 0 0
  (L2/3):                               C3 -> QoS_Action1 
output definitions
Policy The name of the policy rule, configured through the policy rule com-
mand. A plus sign (+) preceding a policy rule name indicates that the 
policy rule has been modified or has been created since the last qos 
apply.
From Where the rule originated.
Prec The precedence of the rule. Precedence determines the order in which 
the switch will apply rules.
Enab Whether or not the rule is administratively enabled. (By default, rules 
are enabled.)
Act Whether or not the rule is enforceable by the switch (e.g., qos is 
enabled, rule is valid and enabled, validity period is active). 
Refl Whether the rule is reflexive or not.
Log Whether or not the switch will log messages about specific flows com-
ing into the switch that match this policy rule. Configured through the 
policy rule command.
Trap Whether or not traps are enabled for the rule. Configured through the 
policy rule command. A trap is sent when a port is administratively 
disabled through a port disable action or a UserPort shutdown function
Save Whether the rule will be captured in an ASCII text file (using the 
configuration snapshot command), saved to the working directory 
after the write memory command or copy running-config working 
command is entered, or saved after a reboot. Configured through the 
policy rule command. 
Matches The number of flows matching this rule. Note that for ingress maxi-
mum bandwidth policies, the value in this field indicates the number of 
packets that exceed the bandwidth limit, not the packets that match the 
rule.
Green, Yellow, Red Tri-Color Marking (TCM) statistics; the number of packets/bytes that 
are marked Green (low drop precedence), Yellow (high drop prece-
dence) , and Red (always drop). Configured through the policy action 
cir command.
{L2/3} The condition and the action associated with the rule; configured 
through the policy condition and policy action commands respec-
tively.