OS10 Enterprise Edition User Guide Release 10.4.0E(R3)


ETS configuration notes

  • ETS is supported on L2 802.1p priority (dot1p 0 to 7) and L3 DSCP (0 to 63) traffic. FCoE traffic uses dot1p priority 3 — iSCSI storage traffic uses dot1p priority 4.
  • Apply these maps and policies on interfaces:
    • Trust maps — OS10 interfaces do not honor the L2 and L3 priority fields in ingress traffic by default. Create a trust map to honor dot1p and DSCP classes of lossless traffic. A trust map does not change ingress dot1p and DSCP values in egress flows. In a trust map, assign a qos-group (traffic class) to trusted dot1p/DSCP values. A qos-group number is used only internally to schedule classes of ingress traffic.
    • QoS map — Create a QoS map to assign trusted dot1p and DSCP traffic classes to lossless queues.
    • Ingress trust policy — Configure a service policy to trust dot1p values in ingress traffic.
    • Egress queuing policy — Configure ETS for egress traffic by assigning bandwidth to matching lossless queues in queuing class and policy maps.
  • Apply both PFC network-qos (input) and ETS queuing (output) policies on an interface to ensure lossless transmission.
  • An ETS-enabled interface operates with dynamic weighted round robin (DWRR) or strict priority scheduling.
  • OS10 control traffic is sent to control queues, which have a strict priority that is higher than data traffic queues. ETS-allocated bandwidth is not supported on a strict priority queue. A strict priority queue receives bandwidth only from DCBX TLVs.
  • The CEE/IEEE2.5 versions of ETS TLVs are supported. ETS configurations are received in a TLV from a peer.

Rate this content

Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\