Loader

DSCP Configuration

The system allows configuration of DSCP Profiles and associating them with Uplink LAGs.  This allows the system to perform marking of L2 Pbits based on the L3 DSCP Marking.  This allows enforcement of the L3 DSCP marking within the system.

The configuration of DSCP is defined as follows:

   

Attribute  Values  Default  Required Description
Dscp-profile-name <profile name> N/A N Name of the DSCP Profile to utilize. If no profile is specified, traffic QoS is strictly based on L2 pbit markings.

 

 
Note: * = required parameter
  • Command Path – tolt>interfaces>net>config>
  • Module – tolt
  • Container – interfaces
  • Container – net 
  • Container – config
  • Styles  
    • *aid  The name of the current LAG, values are NET1 through NET12
    • Dscp-profile-name – Name of the DSCP Profile to utilize. If no profile is specified, traffic QoS is strictly based on L2 pbit markings. 
      • string

DSCP Configuration Example 

The following example will assign a dscp profile named ucr-downstream to the NET1 LAG. The traffic is all queued and QoS enforced based on the L2 pbit markings. This allows mapping the L3 DSCP to the proper L2 pbit marking for proper QoS treatment when the L2 pbits are not set correctly. 

  • Command Path – tolt>interfaces>net>config>
  • Module – tolt
  • Container – interfaces
  • Container – net 
  • Container – config
  • Styles  Example Parameters
    • *aid  NET1
    • Dscp-profile-name ucr-downstream 

  

  1. From the MDS1-ESUA<Config># command line, input tolt interfaces net config NET1 dscp-profile-name ucr-downstream, press Enter. Output similar to the following is displayed:
MDS1-ESUA<Config># tolt interfaces net config NET1 dscp-profile-name ucr-downstream <enter>
MDS1-ESUA<Config># commit <enter>
Commit complete.
MDS1-ESUA<Config>#_

 

 

 

 

 

FEEDBACK: Are you happy with this material?