- Community Home
- >
- Networking
- >
- Software Defined Networking
- >
- Re: Meter remark DSCP value not reflected in queue...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2017 04:52 AM
02-16-2017 04:52 AM
Meter remark DSCP value not reflected in queue selection
Hi,
I am using 2930F switch/16.03 firmware and I have a simple topology of two hosts and one controller.
I have 2-queue configuration with the default mapping:
sh qos queue-config Egress Queue Configuration Number of Queues : 2 802.1p Queue Priorities ----- ---------- 1 0-3 2 4-7
sh qos dscp-map
DSCP Policies
DSCP CodePoint DSCP Value 802.1p tag DSCP Policy name
-------------- ---------- ----------- --------------------------------
000000 0 0 cs0
000001 1 0
000010 2 0
000011 3 0
000100 4 0
000101 5 0
000110 6 0
000111 7 0
001000 8 1 cs1
001001 9 1
001010 10 1 af11
001011 11 1
001100 12 1 af12
001101 13 1
001110 14 1 af13
001111 15 1
010000 16 2 cs2
010001 17 2
010010 18 2 af21
010011 19 2
010100 20 2 af22
010101 21 2
010110 22 2 af23
010111 23 2
011000 24 3 cs3
011001 25 3
011010 26 3 af31
011011 27 3
011100 28 3 af32
011101 29 3
011110 30 3 af33
011111 31 3
100000 32 4 cs4
100001 33 4
100010 34 4 af41
100011 35 4
100100 36 4 af42
100101 37 4
100110 38 4 af43
100111 39 4
101000 40 5 cs5
101001 41 5
101010 42 5
101011 43 5
101100 44 5
101101 45 5
101110 46 7 ef
101111 47 5
110000 48 6 cs6
110001 49 6
110010 50 6
110011 51 6
110100 52 6
110101 53 6
110110 54 6
110111 55 6
111000 56 7 cs7
111001 57 7
111010 58 7
111011 59 7
111100 60 7
111101 61 7
111110 62 7
111111 63 7
Host 1 is sending UDP packets to host 2 at rate 10mbps. I first try to test the DSCP-queue mapping without using meters. I monitor the queues using sh interface queue <num>.
I send the UDP packets with DSCP mark =40 (101000). The packets are correctly mapped to queue 2.
I send the UDP packets with DSCP mark =5 (000101). The packets are correctly mapped to queue 1.
Now, I send the UDP packets with DSCP mark =40 (101000) at 10mbps rate, however, I set a meter with DSCP remark of rate == 1mbps (so almost all packets will be remarked). and I install a flow entry that maps all UDP packets to this meter. The packets are correctly going into the meter, and at the receiver side the Wireshark capture shows that the DSCP was indeed remarked and set to =24 (011000) instead of 40 (101000), however, the packets are still mapped to queue 2!!
it seems that the new DSCP mark is not taken into account and the original one is still used for the queue selection.
Have you tested the DSCP-queue-mapping when using meters ??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2017 06:11 AM
02-16-2017 06:11 AM
Re: Meter remark DSCP value not reflected in queue selection
Hi Enas,
For completeness (and so that we can replicate your environment) would you mind posting the output of the following commands while this behavior is occurring?
show openflow instance X show openflow instance X meters show openflow instance X meters <your-meter-id> show openflow instance X flows
Shaun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2017 04:23 AM
02-17-2017 04:23 AM
Re: Meter remark DSCP value not reflected in queue selection
Hi Shaun,
Sure. Here you go:
Aruba-2930F-24G-PoEP-4SFP(of-inst-aggregate)# sh openflow inst agg
Configured OF Version : 1.3 only
Negotiated OF Version : 1.3
Instance Name : aggregate
Data-path Description : aggregate
Administrator Status : Enabled
Member List : VLAN 2
Pipeline Model : Custom Pipeline
Listen Port : None
Operational Status : Up
Operational Status Reason : NA
Datapath ID : 0002e0071bc4c7e0
Mode : Active
Flow Location : Hardware Only
No. of Hardware Flows : 3
No. of Software Flows : 0
Hardware Rate Limit : 0 kbps
Software Rate Limit : 100 pps
Conn. Interrupt Mode : Fail-Secure
Maximum Backoff Interval : 60 seconds
Probe Interval : 10 seconds
Hardware Table Miss Count : NA
No. of Software Flow Tables : NA
Egress Only Ports : None
Table Model : Custom Pipeline
Source MAC Group Table : Disabled
Destination MAC Group Table : Disabled
Default Miss Action : Drop
Packet-In VLAN Tagging : Default
Controller Id Connection Status Connection State Secure Role
------------- ----------------- ---------------- ------ ------
1 Connected Active No Master I have two tables. Table one just forwards packets to table 2 (Flow 2). Table two (in Flow 3) directs my UDP packets into meter 3.
Aruba-2930F-24G-PoEP-4SFP(of-inst-aggregate)# sh openflow inst agg flows
OpenFlow Flow Table
Flow 1
Match
Incoming Port : Any Ethernet Type : IP
Source MAC : Any Destination MAC : Any
Source MAC Mask : 000000-000000
Destination MAC Mask : 000000-000000
VLAN ID : Any VLAN Priority : Any
Source IP Address : Any
Destination IP Address : Any
IP Protocol : UDP
IP ECN : Any IP DSCP : Any
Source Port : Any Destination Port : 9999
Source Port Range : NA
Destination Port Range : NA
TCP Flags : NA
Custom Match One : 0x31335444453839303631343336383730
Custom Match One Mask : 0xffffffffffffffffffffffffffffffff
Custom Match Two : Any
Custom Match Two Mask : Any
Custom Match Three : Any
Custom Match Three Mask : Any
Custom Match Four : Any
Custom Match Four Mask : Any
Attributes
Priority : 200 Duration : 74 seconds
Hard Timeout : 0 seconds Idle Timeout : 0 seconds
Byte Count : 0 Packet Count : 0
Flow Table ID : 0 Controller ID : 1
Cookie : 0x0
Hardware Index: NA
Instructions
Drop
Flow 2
Match
Incoming Port : Any Ethernet Type : Any
Source MAC : Any Destination MAC : Any
Source MAC Mask : 000000-000000
Destination MAC Mask : 000000-000000
VLAN ID : Any VLAN Priority : Any
Source IP Address : Any
Destination IP Address : Any
IP Protocol : Any
IP ECN : Any IP DSCP : Any
Source Port : Any Destination Port : Any
Source Port Range : NA
Destination Port Range : NA
TCP Flags : NA
Custom Match One : Any
Custom Match One Mask : Any
Custom Match Two : Any
Custom Match Two Mask : Any
Custom Match Three : Any
Custom Match Three Mask : Any
Custom Match Four : Any
Custom Match Four Mask : Any
Attributes
Priority : 0 Duration : 74 seconds
Hard Timeout : 0 seconds Idle Timeout : 0 seconds
Byte Count : 8983947 Packet Count : 6101
Flow Table ID : 0 Controller ID : 1
Cookie : 0x0
Hardware Index: NA
Instructions
Goto Table ID : 1
Flow 3
Match
Incoming Port : 2 Ethernet Type : IP
Source MAC : Any Destination MAC : Any
Source MAC Mask : 000000-000000
Destination MAC Mask : 000000-000000
VLAN ID : Any VLAN Priority : Any
Source IP Address : Any
Destination IP Address : Any
IP Protocol : UDP
IP ECN : Any IP DSCP : Any
Source Port : Any Destination Port : 9999
Source Port Range : NA
Destination Port Range : NA
TCP Flags : NA
Custom Match One : Any
Custom Match One Mask : Any
Custom Match Two : Any
Custom Match Two Mask : Any
Custom Match Three : Any
Custom Match Three Mask : Any
Custom Match Four : Any
Custom Match Four Mask : Any
Attributes
Priority : 300 Duration : 58 seconds
Hard Timeout : 0 seconds Idle Timeout : 0 seconds
Byte Count : 8972043 Packet Count : 6091
Flow Table ID : 1 Controller ID : 1
Cookie : 0x0
Hardware Index: NA
Instructions
Meter ID : 3
Apply Actions
Output : 3
Flow 4
Match
Incoming Port : 3 Ethernet Type : ARP
Source MAC : Any Destination MAC : Any
Source MAC Mask : 000000-000000
Destination MAC Mask : 000000-000000
VLAN ID : Any VLAN Priority : Any
Source Protocol Address : Any
Target Protocol Address : Any
Source Hardware Address : Any
Source Hardware Address Mask : 000000-000000
Target Hardware Address : Any
Target Hardware Address Mask : 000000-000000
ARP Opcode : Any
IP ECN : Any IP DSCP : Any
Source Port : Any Destination Port : Any
Source Port Range : NA
Destination Port Range : NA
TCP Flags : NA
Custom Match One : Any
Custom Match One Mask : Any
Custom Match Two : Any
Custom Match Two Mask : Any
Custom Match Three : Any
Custom Match Three Mask : Any
Custom Match Four : Any
Custom Match Four Mask : Any
Attributes
Priority : 1 Duration : 58 seconds
Hard Timeout : 0 seconds Idle Timeout : 0 seconds
Byte Count : 0 Packet Count : 0
Flow Table ID : 1 Controller ID : 1
Cookie : 0x20000000000000
Hardware Index: NA
Instructions
Apply Actions
Output : 2
Flow 5
Match
Incoming Port : 2 Ethernet Type : IP
Source MAC : Any Destination MAC : Any
Source MAC Mask : 000000-000000
Destination MAC Mask : 000000-000000
VLAN ID : Any VLAN Priority : Any
Source IP Address : 10.0.0.4/255.255.255.255
Destination IP Address : 10.0.0.3/255.255.255.255
IP Protocol : Any
IP ECN : Any IP DSCP : Any
Source Port : Any Destination Port : Any
Source Port Range : NA
Destination Port Range : NA
TCP Flags : NA
Custom Match One : Any
Custom Match One Mask : Any
Custom Match Two : Any
Custom Match Two Mask : Any
Custom Match Three : Any
Custom Match Three Mask : Any
Custom Match Four : Any
Custom Match Four Mask : Any
Attributes
Priority : 1 Duration : 58 seconds
Hard Timeout : 0 seconds Idle Timeout : 0 seconds
Byte Count : 0 Packet Count : 0
Flow Table ID : 1 Controller ID : 1
Cookie : 0x20000000000000
Hardware Index: NA
Instructions
Apply Actions
Output : 3
Flow 6
Match
Incoming Port : Any Ethernet Type : Any
Source MAC : Any Destination MAC : Any
Source MAC Mask : 000000-000000
Destination MAC Mask : 000000-000000
VLAN ID : Any VLAN Priority : Any
Source IP Address : Any
Destination IP Address : Any
IP Protocol : Any
IP ECN : Any IP DSCP : Any
Source Port : Any Destination Port : Any
Source Port Range : NA
Destination Port Range : NA
TCP Flags : NA
Custom Match One : Any
Custom Match One Mask : Any
Custom Match Two : Any
Custom Match Two Mask : Any
Custom Match Three : Any
Custom Match Three Mask : Any
Custom Match Four : Any
Custom Match Four Mask : Any
Attributes
Priority : 0 Duration : 74 seconds
Hard Timeout : 0 seconds Idle Timeout : 0 seconds
Byte Count : 11904 Packet Count : 10
Flow Table ID : 1 Controller ID : 1
Cookie : 0x0
Hardware Index: NA
Instructions
Apply Actions
Controller Port
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2017 04:28 AM
02-17-2017 04:28 AM
Re: Meter remark DSCP value not reflected in queue selection
(I had to split the post into two due to the character limit)
Aruba-2930F-24G-PoEP-4SFP(of-inst-aggregate)# sh openflow inst agg meters
OpenFlow Instance Meters
Meter ID : 3
Flow Count : 1
Input Packet Count : 6091
Input Byte Count : 8886769
Duration : 142
Precedence Packet/Byte
Band Type Rate Level Count
--------- ---------------- ---------- ------------------------
Mark 1000 kbps 0 7875682 Aruba-2930F-24G-PoEP-4SFP(of-inst-aggregate)# sh openflow inst agg meter 3
OpenFlow Instance Meters
Meter ID : 3
Flow Count : 1
Input Packet Count : 6091
Input Byte Count : 8886769
Duration : 167
Precedence Packet/Byte
Band Type Rate Level Count
--------- ---------------- ---------- ------------------------
Mark 1000 kbps 0 7875682 Showing the queues before the transmission
sh interface queue 3
Status and Counters - Port Counters for port 3
Name :
MAC Address : e0071b-c4c7fd
Link Status : Up
Port Enabled : Yes
Port Totals (Since boot or last clear) :
Rx Packets : 45 Tx Packets : 28
Rx Bytes : 10,320 Tx Bytes : 3,488
Rx Drop Packets : 0 Tx Drop Packets : 0
Rx Drop Bytes : 0 Tx Drop Bytes : 0
Egress Queue Totals (Since boot or last clear) :
Tx Packets Dropped Packets Tx Bytes Dropped Bytes
Q1 24 0 2,320 0
Q2 4 0 1,168 0 Showing the queues After the transmission. Packets still went into queue 2 althought the DSCP is remarked to 24 (0x18)
sh interface queue 3
Status and Counters - Port Counters for port 3
Name :
MAC Address : e0071b-c4c7fd
Link Status : Up
Port Enabled : Yes
Port Totals (Since boot or last clear) :
Rx Packets : 50 Tx Packets : 6,141
Rx Bytes : 11,264 Tx Bytes : 8,988,878
Rx Drop Packets : 0 Tx Drop Packets : 0
Rx Drop Bytes : 0 Tx Drop Bytes : 0
Egress Queue Totals (Since boot or last clear) :
Tx Packets Dropped Packets Tx Bytes Dropped Bytes
Q1 43 0 14,998 0
Q2 6,098 0 8,973,880 0 I have also attached a pcap file from the receiver that proves that the majority of the UDP packets have their DSCP remarked to 24 (0x18) instead of 40 (0x28).
If you can please just perform a simple test that has a meter that remarks the DSCP and see if that new mark is reflected on the queue selection?
Thanks!
Enas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2017 12:34 PM
02-20-2017 12:34 PM
Re: Meter remark DSCP value not reflected in queue selection
Hi Enas,
Using the data you've posted, we confirmed that we're seeing the same behavior on prior revisions of firmware as well. Would you be able to open a support ticket for this issue? Then we'd be able to prioritize a resolution into our ongoing development efforts. The data you've provided thusfar should be sufficient for the support ticket, so please submit it alongside the description of the issue (your writeup above will suffice).
Shaun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-22-2017 01:04 AM
02-22-2017 01:04 AM
Re: Meter remark DSCP value not reflected in queue selection
Thanks Shaun for your reply,
I am trying to open a support case and it keeps failing. I get this message after I fill all the info and click on create a case: (I have tried several times using two browsers)
We're very sorry!
The page you requested can not be found or displayed at this time.
- If you typed the URL yourself, please make sure that the spelling is correct.
- If you clicked on a link to get here, there may be a problem with the link.
- Try using your browser's "back" button or the "return to previous page" link below to choose a different link on that page.
- Periodically we need to perform routine maintenance on our site, this usually takes from 3-5 minutes during which our pages are unavailable.
- If this is a technical problem then we will be alerted and will resolve the issue as quickly as possible.
Can you guide me on how to successfully create a support ticket? Can't this thread be used to solve the issue?
What is the estimation to get this bug solved? It is very urgent for us since the entire feature of remark meters does not work!! and It is the main feature we bought the switches for! (in addition to the custom fields with mask which is also not working, I have another thread opened for it and is still not resolved).
I appreciate any help you can provide us.
Enas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2017 10:08 AM
02-23-2017 10:08 AM
Re: Meter remark DSCP value not reflected in queue selection
Hi Enas,
I apologize that the support ticket filing process has added frustration. According to my contacts, you'll need to call 800-633-3600 and open a case with the SDN TEAM. Both the VAN controller and firmware are involved in your solution, but this looks to be an issue with firmware on the switches (not the VAN controller).
I realize that it's not optimal to re-describe the issue when filing a ticket, but we funnel all support issues through our ticketing system so that they can be properly analyzed, reproduced, and prioritized relative to eachother and to new product development.
Shaun