Bug 1663648
| Summary: | [RHOS14][OpenDaylight] DSCP validation failed while increase the TOS value more than 100 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Pradipta Kumar Sahoo <psahoo> | ||||
| Component: | opendaylight | Assignee: | lpeer <lpeer> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Noam Manos <nmanos> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14.0 (Rocky) | CC: | mkolesni, trozet | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-03-06 16:15:30 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Pradipta Kumar Sahoo
2019-01-06 04:04:51 UTC
Created attachment 1518742 [details]
OSP-Tenant-VM-Creation Details
(In reply to Pradipta Kumar Sahoo from comment #0) > ii) Tried to ping with following DSCP tos values which threw the exception > **Invalid tcclass**. Reference link > http://conceptsfortheroad.com/2016/01/01/using-linux-to-verify-dscp/ > DSCP 26 (011010) <==> ToS 104 (01101000) > DSCP 46 (101110) <==> ToS 184 (10111000) > DSCP 48 (110000) <==> ToS 192 (11000000) > > [root@instance2 ~]# ping 192.168.1.18 -Q 104 > ping: Invalid tclass 104 > [root@instance2 ~]# ping 192.168.1.18 -Q 184 > ping: Invalid tclass 184 > [root@instance2 ~]# ping 192.168.1.18 -Q 192 > ping: Invalid tclass 192 I think this is some bug with ping and using decimal. I also get it on F28. However if you use hex it seems to work: [trozet@localhost apex]$ ping 127.0.0.1 -4 -Q 104 ping: Invalid tclass 104 [trozet@localhost apex]$ ping 127.0.0.1 -Q 0x68 PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.030 ms > iii) Referring to following OpenDaylight DSCP verification. It has mentioned > that the valid DSCP value ranges are 0-63. which is currently working in > RHOSP14 OpenDaylight environment. > > https://wiki.opendaylight.org/view/Network_Intent_Composition: > Beryllium_Planning:QoS_Attribute_Mapping > From: > [root@instance2 ~]# ping -c 2 192.168.1.18 -Q 0 > PING 192.168.1.18 (192.168.1.18) 56(84) bytes of data. > 64 bytes from 192.168.1.18: icmp_seq=1 ttl=64 time=2.41 ms > 64 bytes from 192.168.1.18: icmp_seq=2 ttl=64 time=1.60 ms > > --- 192.168.1.18 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 1001ms > rtt min/avg/max/mdev = 1.605/2.009/2.413/0.404 ms > > To: > [root@instance2 ~]# ping -c 2 192.168.1.18 -Q 63 > PING 192.168.1.18 (192.168.1.18) 56(84) bytes of data. > 64 bytes from 192.168.1.18: icmp_seq=1 ttl=64 time=2.49 ms > 64 bytes from 192.168.1.18: icmp_seq=2 ttl=64 time=1.64 ms > > --- 192.168.1.18 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 1001ms > rtt min/avg/max/mdev = 1.642/2.070/2.498/0.428 ms > That link is for Network Intent project and does not relate to Netvirt which we use. For the purpose of vxlan inheritance I don't think there should be any limit to which DSCP bits will be copied between the inner and outer header. > iv) Also, noticed I can test E-W traffic with DSCP tos value till 99. But > when I increase tos value more than 100, it throwing Invalid tclass which > indicate that it is not supported on rhel. > The DSCP theory says DSCP header uses 1 byte (or 8-bits) which I assume > a limitation to use the tos value 99 not more than that. > > ** Could you please let us know the limitation of DSCP tos values in > OpenDaylight and how we can overcome the limitation OVS south bound devices? > ** > > [root@instance2 ~]# ping -c 2 192.168.1.18 -Q 99 > PING 192.168.1.18 (192.168.1.18) 56(84) bytes of data. > 64 bytes from 192.168.1.18: icmp_seq=1 ttl=64 time=2.45 ms > 64 bytes from 192.168.1.18: icmp_seq=2 ttl=64 time=1.66 ms > > --- 192.168.1.18 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 1001ms > rtt min/avg/max/mdev = 1.666/2.060/2.455/0.397 ms > > @instance2 ~]# ping -c 2 192.168.1.18 -Q 100 > ping: Invalid tclass 100 > > > v) Based on theory in ODL env, br-int is the default endpoint of VXLAN > tunneling on each compute and we assume there should be **mod_nw_tos** > action in br-int flows. But we didn't found any tos entries while dumping > the integration bridge. It looks like the flow modification should be > handled neutron northbound API with using **odl-qos** notification driver. > Please correct if I was mistaken and kindly suggest the additional details > which need to configure and validate TOS details from OVS southbound devices. > The ODL/Neutron QoS feature is different from the inheritance feature. The inheritance feature is inheritance of TOS for tenant instance traffic which already contains set TOS on packets, which is now supported. The ODL/Neutron QoS is about being able to set QoS on Neutron networks, meaning that when a tenant VM would send an unmarked packet into the network, the packet would be marked by the SDN and QoS would be applied throughout the network based on those DSCP markings. This latter feature is unsupported right now. > @compute-0 ~]# ovs-ofctl -O OpenFlow13 dump-flows br-int|grep -i tos > > Expected results: > How DSCP get works more than 100 TOS values? > > Additional info: > https://docs.opendaylight.org/projects/netvirt/en/stable-oxygen/specs/qos. > html As per depreciation notice [1], closing this bug. Please reopen if relevant for RHOSP13, as this is the only version shipping ODL. [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14/html-single/release_notes/index#deprecated_functionality As per depreciation notice [1], closing this bug. Please reopen if relevant for RHOSP13, as this is the only version shipping ODL. [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14/html-single/release_notes/index#deprecated_functionality |