cancel
Showing results for 
Search instead for 
Did you mean: 

Derive CoS values from DSCP values / QoS Questions

Derive CoS values from DSCP values / QoS Questions

dirk
New Contributor II
Hey Folks!

today i was working with classifying / marking traffic on the A2/A4/B3/B5 Platforms (latest Firmware).

Basically i want my QoS Setup based on DSCP values, because its end to end.

As far as i could figure out, ETS switching does its priority internally on CoS values.
Does anyone of you know, if this is correct?
So that means somehow the CoS values must be set.

I found that this configuration is pretty doing this job (B5 Plattform):

set policy profile 1 name "QoS" cos 0 cos-status enable
set policy rule 1 iptos 32 mask 8 cos 1 forward
set policy rule 1 iptos 40 mask 8 cos 1 forward
set policy rule 1 iptos 64 mask 8 cos 2 forward
set policy rule 1 iptos 72 mask 8 cos 2 forward
set policy rule 1 iptos 96 mask 8 cos 3 forward
set policy rule 1 iptos 104 mask 8 cos 3 forward
set policy rule 1 iptos 128 mask 8 cos 4 forward
set policy rule 1 iptos 136 mask 8 cos 4 forward
set policy rule 1 iptos 184 mask 8 cos 5 forward
set policy rule 1 iptos 192 mask 8 cos 6 forward
set policy rule 1 iptos 224 mask 8 cos 7 forward
set policy port *.*.* 1

But the last two rules will never set cos 6 or cos 7, they set always cos to 5. Does anyone has an explaination for this?

Ok, this config does its job on untagged ports before a tag is imposed.
We have here also a couple router (firewall) on a stick scenarios; (CoS) marked tagged frames are going to the firewall, but they coming (CoS) unmarked and tagged back.

How do i derive CoS values from the DSCP values on tagged ports?

The A2 switch does not support the syntax of the b5 (i guess through the legacy device).
But anyway is there a option to do the same thing on the B5 platform?

any help would be great guys

8 REPLIES 8

dirk
New Contributor II
I just want to let you know i did the test on the A2 platform.

I created a diffserv policy - a bit senseless but just to do something, to work with that traffic.

set diffserv class create all DSCPEF
set diffserv class match iptos DSCPEF B8 FF
set diffserv policy create DSCP in
set diffserv policy class add DSCP DSCPEF
set diffserv policy mark ipdscp DSCP DSCPEF ef
set diffserv service add in fe.1.1 DSCP
set diffserv service add in fe.1.2 DSCP

Testtraffic marked with dscp 46 (doesnt matter if access or trunk ports), are forwarded with cos 0.

I will follow up with the GTAC as you suggested.

dirk

Paul_Poyant
New Contributor III
You're welcome.

With benefit of hindsight it's possible that the remaining issue here is Policy being applied to a LAG Aggregator (with underlying physical ports). Though typically a LAG in its role as an InterSwitch Link is VLAN-tagged, these two attributes (LAG, VLAN Tagging) are in fact independent and each has its own functional expectations.

dirk
New Contributor II
Yes that was the command i tried already since my very first posting here.

Thanks Paul, for clarifiing some Enterasys internal stuff to me.

I think i will raise a GTAC call next week.

Thanks!

Paul_Poyant
New Contributor III
A ToS byte value of 192 (DSCP 48) should hit on this rule in your sample config:
'set policy rule 1 iptos 192 mask 8 cos 6 forward'.
As discussedd, with current firmware this should yield priority 5, for either tagged or unntagged traffic.
If it does not, then I'd get a GTAC Support case open to dig into that further.

The auto-queue-bump logic only applies to ef/46 traffic.

On the stackables, using the 'set policy port ' command it is not supported to port-assign a static policy to a LAG aggregator port either by direct reference (lag.x.y) or by implied reference via wild card (lag.*.* or *.*.*). I'm offhand not aware of any such restriction for the diffserv command set (A2-Series).
GTM-P2G8KFN