https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/SFC-165 sfc <p>When creating an RSP and providing the name, the NSP number does not match the actual number renderd into SFC flows. For example, if I create an RSP with a name and the RSP chooses 36 for the ID, the flows will be configured to match on some other NSP like 6.</p> <p>Operating System: All<br/> Platform: All</p> SFC-165

RSP NSP (SPI) does not match NSP in flows when specifying RSP name

Bug Resolved Cannot Reproduce Brady Johnson Tim Rozet Mon, 3 Oct 2016 20:51:05 +0000 Thu, 19 Oct 2017 16:58:58 +0000 Tue, 4 Oct 2016 09:23:47 +0000 unspecified General 0 1 <p>Please let me know if you need more details about it. In my setup, i just have one chain with one SF in it. I am making the same call that tacker demo makes, but the only difference was that i was setting the name of rsp to the name of SFP.</p> <p>Investigating...</p> <p>I cant reproduce this.</p> <p>I just pulled ODL Carbon master on October 4, 2016 and did the following:</p> <p>1. Create 1 SF and 1 SFF</p> <p>2. Create the following SFC:</p> <p>{<br/> "service-function-chains": {<br/> "service-function-chain": [<br/> {<br/> "name": "sfc-chain-1sf1sff",<br/> "symmetric": true,<br/> "sfc-service-function": [</p> { "name": "hdr-enrich-abstract1", "type": "http-header-enrichment" } <p> ]<br/> }<br/> ]<br/> }<br/> }</p> <p>3. Create the following SFP:</p> <p>{<br/> "service-function-paths": {<br/> "service-function-path": [</p> { "name": "sfc-path-1sf1sff", "service-chain-name": "sfc-chain-1sf1sff", "transport-type": "service-locator:vxlan-gpe", "symmetric": true } <p> ]<br/> }<br/> }</p> <p>4. Create the following RSP:</p> <p>{<br/> "input": </p> { "name": "sfc-path-1sf1sff", "parent-service-function-path": "sfc-path-1sf1sff", "symmetric": true } <p>}</p> <p>5. Dump the flows:</p> <p>ebrjohn@colorado:~$ sudo ovs-ofctl -O OpenFlow13 dump-flows br-int | awk '</p> {print $1, $3, $6, $7} <p>'<br/> OFPST_FLOW (OF1.3) <br/> cookie=0x14, table=0, priority=5 actions=goto_table:1<br/> cookie=0x14, table=1, priority=300,udp,nw_dst=10.0.0.10,tp_dst=6633 actions=output:0<br/> cookie=0x14, table=1, priority=300,udp,in_port=0,tp_dst=6633 actions=LOCAL<br/> cookie=0x14, table=1, priority=250,nsp=28 actions=goto_table:4<br/> cookie=0x14, table=1, priority=250,nsp=8388636 actions=goto_table:4<br/> cookie=0x14, table=1, priority=5 actions=drop<br/> cookie=0x14, table=2, priority=5 actions=goto_table:3<br/> cookie=0x14, table=3, priority=5 actions=goto_table:4<br/> cookie=0x14, table=4, priority=550,nsi=255,nsp=28 actions=load:0xa00000a-&gt;NXM_NX_TUN_IPV4_DST[],goto_table:10<br/> cookie=0x14, table=4, priority=550,nsi=255,nsp=8388636 actions=load:0xa00000a-&gt;NXM_NX_TUN_IPV4_DST[],goto_table:10<br/> cookie=0x14, table=4, priority=5 actions=goto_table:10<br/> cookie=0xba5eba1100000102, table=10, priority=660,nsi=254,nsp=28,nshc1=0 actions=IN_PORT<br/> cookie=0xba5eba1100000102, table=10, priority=660,nsi=254,nsp=8388636,nshc1=0 actions=IN_PORT<br/> &lt;... skipping the rest of the flows for brevity ...&gt;</p> <p>6. Query the RSP from the data store:</p> <p>HTTP GET operational/rendered-service-path:rendered-service-paths/<br/> result: 200<br/> {<br/> "rendered-service-paths": {<br/> "rendered-service-path": [<br/> {<br/> "name": "sfc-path-1sf1sff",<br/> "starting-index": 255,<br/> "service-chain-name": "sfc-chain-1sf1sff",<br/> "sfc-encapsulation": "service-locator:nsh",<br/> "symmetric-path-id": 8388636,<br/> "rendered-service-path-hop": [</p> { "service-function-name": "sf1", "service-function-forwarder": "sff1", "hop-number": 0, "service-function-forwarder-locator": "vxgpe", "service-index": 255 } <p> ],<br/> "parent-service-function-path": "sfc-path-1sf1sff",<br/> "path-id": 28,<br/> "transport-type": "service-locator:vxlan-gpe"<br/> },<br/> {<br/> "name": "sfc-path-1sf1sff-Reverse",<br/> "starting-index": 255,<br/> "service-chain-name": "sfc-chain-1sf1sff",<br/> "sfc-encapsulation": "service-locator:nsh",<br/> "symmetric-path-id": 28,<br/> "rendered-service-path-hop": [</p> { "service-function-name": "sf1", "service-function-forwarder": "sff1", "hop-number": 0, "service-function-forwarder-locator": "vxgpe", "service-index": 255 } <p> ],<br/> "parent-service-function-path": "sfc-path-1sf1sff",<br/> "path-id": 8388636,<br/> "transport-type": "service-locator:vxlan-gpe"<br/> }<br/> ]<br/> }<br/> }</p> <p>As you can see from the results above, the NSP/path-id is the same in both the OpenFlow flows and the RSP.</p> <p>Brady</p> Development External issue ID 6850 External issue URL Rank 0|i02fgf: