User`s guide

206 XgOS User’s Guide • September 2014
By using this example, the default Policer is disabled, but remains bound to the
vNIC. QoS is disabled for ingress traffic only, so egress traffic is not affected.
To disable the custom policer named “qostest/200” for egress traffic on a vNIC
named “foo”:
By using this example, the custom Policer is disabled, but remains bound to the
vNIC. QoS is disabled for egress traffic only, so ingress traffic is not affected.
As an alternative, to disable the custom policer named “qostest/200” for egress
traffic on a vNIC named “foo”:
By using this example, the custom Policer is disabled and removed from the vNIC.
QoS is disabled for egress traffic, so ingress traffic is not affected. To re-enable QoS
after using the keyword none, you must specify a Policer in the -policer option
plus set the state to “enable.” For example:
Application QoS With Ingress 802.1p and
IP Precedence Mapping
Ingress traffic can be mapped into specific queues by changing the bits in packets to
send the packets to one of eight queues supported per vNIC. The following table
defines the mapping of 802.1p and IP precedence/TOS values to queues on 10GigE
cards. The queue numbers in the table are relative to vNICs.
set vnic foo.bar egress-qos -policer=qostest/200 disable
set vnic foo.bar egress-qos -policer=none disable
set vnic foo.bar egress-qos -policer=qostest/200 enable
802.1p user priority IP Precedence/TOS Queue Number
Network Control, 7 Control, 7 7
Voice, 6 6 6
Video, 5 5 5
Control load, 4 4 4
Excellent Effort, 3 3 3