[VTN-166] vtn-inet-match protocol and dscp values not mapped from VTN Coordinator to VTN manager Created: 28/Sep/17 Updated: 30/Oct/17 |
|
| Status: | Verified |
| Project: | vtn |
| Component/s: | ODC Driver |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Y Ananth | Assignee: | Y Ananth |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 9224 |
| Description |
|
Issue Scenario : The dscp,protocol values from the Coordinator flowlistentry are not mapped in the VTN Manager Reproduce the Bug: set-up for vtn manager and coordinator using the example: In the flowlistentry command give the ipdscp,protocol attributes as given below:
The Request body in the Coordinator logs : http://10.106.138.150:8181/restconf/operations/vtn-flow-condition:set-flow-condition-match Url formed ] } } ] } } The below mentioned is from the VTN Manager obtained by GET command :
{"vtn-flow-condition":[{"name":"flowlist1","vtn-flow-match":[ {"index":1}]}]} The below mentioned is from the VTN Coordinator obtained by GET command :
{"flowlistentry":{"ipdscp":"23","seqnum":"1","ipproto":"6"}} THE IPDSCP and IPPROTO Values are present in VTN Coordinator but not mapped to VTN manager. Occurrence of the issue : Occurs every time during creation of flowlistentries with the ipdscp,protocol attributes |
| Comments |
| Comment by Y Ananth [ 25/Oct/17 ] |
|
Issue resolved and patch for the bug has been merged in: stable/carbon: stable/nitrogen: |