Reset Search
 

 

Article

Configuring QOS profiles and verify QOS is working on EXOS

« Go Back

Information

 
TitleConfiguring QOS profiles and verify QOS is working on EXOS
Objective
Configuring QOS profiles and verify QOS is working.
This article focuses on the prioritization based on ToS (Diffserv) and CoS (dot1p. )
Environment
  • EXOS All
  • Summit
  • BlackDiamond
Procedure
Listed below are the steps for creating the qosprofile, configuring the DSCP/dot1p profile mapping for ingress traffic, configuring the DSCP/dot1p replacement, and configuring the qosprofile for specified VLANs and/or ports.
  • Create a QoS profile.
    • create qosprofile <QP1 | QP2 | QP3 | QP4 | QP5 | QP6 | QP7>
  • Configure the default ingress DiffServ code point (DSCP) and/or ingress dot1p QoS profile mapping if the traffic is set to ingress with a value already set.
    • configure diffserv examination code-point <CODE_POINT_VALUE> qosprofile <QOSPROFILE>
    • configure dot1p type <DOT1P_PRIORITY_VALUE> qosprofile <QOSPROFILE>
  • Configure the qosprofile in which a particular port or VLAN will be handled on ingress if the traffic is not set to ingress with a value already set.
    • configure ports <PORT_LIST> qosprofile <QOSPROFILE>
    • configure vlan <VLAN_NAME> qosprofile <QOSPROFILE>
  • Configure the DSCP or dot1p value the traffic will egress with based upon the qosprofile in which the traffic was handled.
    • configure diffserv replacement [qosprofile <QOS_PROFILE> | priority <PRIORITY_VALUE>] code-point <CODE_POINT_VALUE>

Listed below are show commands that can be used to confirm the configuration listed above.
  • show qosprofile
  • show dot1p
  • show dot1p replacement
  • show diffserv examination
  • show diffserv replacement
Additional notes
  • If traffic is expected to ingress with a DSCP or dot1p value, examination will need to be enabled on the port
  • If the traffic is not expected to ingress with a DSCP or dot1p value already set, ensure examination is disabled and the value is set via VLAN or port
  • Diffserv and dot1p replacement is used to set the DSCP or dot1p value on egress based upon the qosprofile in which the traffic was handled
  • show port <port#> qosmonitor will show which QoS queues traffic is taking on egress
  • On 1G ports, when Diffserv examination is turned on, dot1p replacement is also turned on as well
  • When traffic ingresses with both a Dot1p and a DSCP value, the Dot1p value takes precedence
  • In a stack, traffic ingressing with dot1p value of 6 will be moved to QP7.  However, because QP7 is for control traffic, data traffic arriving in QP7 is further moved to QP1.  In order to ensure that dot1p labelled traffic egresses in the expected queue, the command configure dot1p type <value> <qosprofile> must be used to explicitly place the traffic in the respective queue


For additional information on this topic visit The HUB conversation:   
https://community.extremenetworks.com/extreme/topics/qos-802-1p-mapping-on-ingress-port

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255