[GENIUS-34] Create tunnel-type-gre interface via IFM generates wrong table=0 entry Created: 11/Nov/16  Updated: 06/Jun/17  Resolved: 06/Jun/17

Status: Resolved
Project: genius
Component/s: General
Affects Version/s: (unspecified)
Fix Version/s: None

Type: Bug
Reporter: Maria Merida Assignee: Faseela K
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 7151

 Description   

Creating a tunnel-type-gre interface via IFM should generate a table=0 entry which goes to Ingress Service Dispatcher Table, right now it goes to table=18 (which is only valid for vxlan tunnels).

Version: Boron SR1

Steps to reproduce this bug:

POST http://localhost:8181/restconf/config/ietf-interfaces:interfaces/

{ "interface": [

{ "name": "tun999a999a9a9", "type": "iana-if-type:tunnel", "odl-interface:tunnel-interface-type": "odl-interface:tunnel-type-gre", "odl-interface:datapath-node-identifier": "75356950704695", "odl-interface:tunnel-source": "172.0.22.11", "odl-interface:tunnel-destination": "192.168.3.140", "enabled": true }

]
}

Entry created in pipeline:

cookie=0x8000001, duration=9.189s, table=0, n_packets=0, n_bytes=0, priority=5,in_port=2 actions=write_metadata:0x90000000001/0x1fffff0000000001,goto_table:18

I think it should go to table=17 instead, and I don't know if the last bit in metadata is properly set.

 Comments   
Comment by Faseela K [ 07/Apr/17 ]

Hi Maria,
As far as I remember, you have used the service-binding on tunnels to make this to work. If so, can I close this TR?
Thanks,
Faseela

Comment by Jose Antonio Baena Cobos [ 10/Apr/17 ]

Hi Faseela,

Yes, we made it work using the service-binding on tunnels:
1) curl -u admin:admin -H 'Content-Type:application/json' -X POST --data "$content" http://192.168.0.50:8181/restconf/config/ietf-interfaces:interfaces/

2) curl -u admin:admin -H 'Content-Type:application/json' -X POST --data "$content" http://192.168.0.50:8181/restconf/config/elan:elan-interfaces/

As there is a feature for Nitrogen, where all service-bindings will goto table 17, this enhancement will be covered then, so you can close this bug

Thanks

Generated at Wed Feb 07 19:59:45 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.