Wired Intelligent Edge (Campus Switching and Routing)

Reply
Contributor I

Re: DSCP to COS map

Hi TcoloT-AdolfoZameza, 

 

the commands I mentioned are exclusive to ArubaOS-CX gear. 2930 has an entire different OS (ArubaOS).

 

Will the 2930 be routing on your scenario? I ask this because I believe it can mark DSCP packets even though it has no IP address on that vlan but I can't assure it.

 

The commands would be.

 

For a class that matches any origin with UDP port 5060 to any destination:

class ipv4 "SIP-traffic"
    10 match udp 0.0.0.0 255.255.255.255 eq 5060 0.0.0.0 255.255.255.255
exit

 

Then the policy marking EF on DSCP:

policy qos "EF-marking"
    10 class ipv4 "SIP-traffic" action dscp ef
exit

 

Then apply that policy in the vlan where the traffic is being originated (from client to MPLS):

vlan X service-policy EF-marking in

 

If you want it to apply that policy to the outgoing vlan (the vlan that aggregates all traffic into MPLS)

vlan X service-policy EF-marking out

 

 

Hope this helps!

 

Best regards,

 

Aarón

Highlighted
Contributor I

Re: DSCP to COS map

Thank you so much for your answer.

 

No, there is no routing intended, the primary function of the 2930 sw is ToR Switch for the IVR app server.

 

I belived as the manual implies, the 2900 family can remark QoS  L2/L3 Fields witout routing, but also the manual display some limitations. I have fowarded this dub to my local presales team to confirm.

--------------------

Aruba 2930F / 2930M Advanced Traffic Management Guide for ArubaOS-Switch 16.08, Page 214

 

Restrictions

Traffic policing comes with the following restrictions:

  • Does not support MAC classes.
  • Cannot configure burst size even though RFC 2698 allows you to specify committed burst size and peak burst size. Incorrect burst sizes can either lead to excessive traffic loss, or poor rate-limiting thus reducing the performance.
  • Cannot configure rates in packets-per-second.
  • Exceeded commit-rate packets are only DSCP remarked.
  • Operates only in color blind mode.
  • Applicable only for QoS policies and not PBR or mirror policies.
  • Cannot configure using Next Gen WEBUI or switch menu.
  • QoS policy containing a two rate meter can only be applied on individual physical interfaces, and not on logical interfaces (VLANs or LAG).
  • The Egress ACLs do not support DSCP remarking. As DSCP remarking is the only supported action for commit-rate violation, traffic policing cannot be enabled on an outward interface.
  • If you apply CoS through QoS ACL on the same port as two rate meter, the meter has a higher precedence over ACLs. The CoS value of the packet is set to zero as CIR/PIR DSCP is applied through a meter.

-----------------

so lets assume it can do it. Next part seems pretty straight forward:

 

class ipv4 "SIP-traffic"
    10 match udp 0.0.0.0 255.255.255.255 eq 5060 0.0.0.0 255.255.255.255
exit



Then the policy marking EF on DSCP:

policy qos "EF-marking"
    10 class ipv4 "SIP-traffic" action dscp ef
exit

In my intended configuration i guess i could do

 

interface 1/1/1
apply policy EF-marking in

interface 1/1/24
apply policy EF-marking out

on each server port and in the mpls uplink port (in this example port 24) or simply i can do this last one.

 

whats your opinion? I guess it is only needed to try in a test bed.

 

 

 

Re: DSCP to COS map

Hi community,

In this link we can find commands that maps DSCP values directly to CoS values for HPE Procurve Switches.
https://support.hpe.com/hpsc/doc/public/display?docId=mmr_sf-EN_US000005132
Is there a way to do this mapping using Aruba OS-CX?
Any input will be appreciated.
Regards


PS: If you feel this information is useful and solved your question or problem, please do not forget to mark it as a solution and give me some kudos.

Re: DSCP to COS map

Here is on CX the default dscp to local-priority (cos) mapping:

8320-4(config)# show qos dscp-map
code_point local_priority color name
---------- -------------- ------- ----
0 1 green CS0
1 1 green
2 1 green
3 1 green
4 1 green
5 1 green
6 1 green
7 1 green
8 0 green CS1
9 0 green
10 0 green AF11
11 0 green
12 0 yellow AF12
13 0 green
14 0 red AF13
15 0 green
16 2 green CS2
17 2 green
18 2 green AF21
19 2 green
20 2 yellow AF22
21 2 green
22 2 red AF23
23 2 green
24 3 green CS3
25 3 green
26 3 green AF31
27 3 green
28 3 yellow AF32
29 3 green
30 3 red AF33
31 3 green
32 4 green CS4
33 4 green
34 4 green AF41
35 4 green
36 4 yellow AF42
37 4 green
38 4 red AF43
39 4 green
40 5 green CS5
41 5 green
42 5 green
43 5 green
44 5 green
45 5 green
46 5 green EF
47 5 green
48 6 green CS6
49 6 green
50 6 green
51 6 green
52 6 green
53 6 green
54 6 green
55 6 green
56 7 green CS7
57 7 green
58 7 green
59 7 green
60 7 green
61 7 green
62 7 green
63 7 green

 

This can be tuned with command:

8320-4(config)# qos dscp-map 41 local-priority 5

 

 

 

Re: DSCP to COS map

Hi Vincent,

Do you mean that the local priority in the switch is in fact the CoS code point ?

 

switch# show qos cos-map default
code_point local_priority color name
---------- -------------- ------- ----
0 1 green Best_Effort
1 0 green Background
2 2 green Excellent_Effort
3 3 green Critical_Applications
4 4 green Video
5 5 green Voice
6 6 green Internetwork_Control
7 7 green Network_Control

 

Regards


PS: If you feel this information is useful and solved your question or problem, please do not forget to mark it as a solution and give me some kudos.

Re: DSCP to COS map

Not exactly. When you map, you map to the local-priority,

as the document you refer to in your first message. The DSCP field in IP header or COS field in ethernet hearder is un-touched (unlike marking).

This is the local definition of the priority that is changed by the mapping. That mapping has a default value. So you can see what is the default association COS <-> local and then tune as you want what should be the priority locally set to the ingress packet by mapping the DCSP to a different local-priority than the default.

 

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: