[GENIUS-35] Incorrect Service Binding handling for tunnel interfaces when more than 1 service Created: 11/Nov/16  Updated: 19/Oct/17  Resolved: 17/Nov/16

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

Type: Bug
Reporter: Maria Merida Assignee: Unassigned
Resolution: Cannot Reproduce 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: 7152

 Description   

Create Service Binding creates entry in table=0 with a service-priority+1. Is this the expected behaviour?

Version: Boron SR1

Steps to reproduce the issue:

1) Create Service Binding (POST http://localhost:8181/restconf/config/interface-service-bindings:service-bindings/)

{
"services-info": [
{
"interface-name": "tun999a999a9a9",
"service-mode" : "service-mode-ingress",
"bound-services": [
{
"service-name": "ELAN",
"service-type": "interface-service-bindings:service-type-flow-based",
"service-priority": 5,
"flow-priority":10,
"flow-cookie": 134479800,
"instruction": [
{
"order": 1,
"go-to-table":

{ "table_id": 50 }

}
]
}
]
}
]
}

2) Check a new entry is populated in table=0 as follows:

cookie=0x803ffb8, duration=10.943s, table=0, n_packets=0, n_bytes=0, priority=10,in_port=1 actions=write_metadata:0xc000090000000000/0xffffff0000000001,goto_table:50

To have Service Index = 6 (110) in write_metadata actions, "service-priority" should be equal to "5" in json (= target SI - 1).


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