[VTN-96] Flowfilter actions "VTNSetPortSrcAction" and "VTNSetPortDstAction" is not listed in the flow entries installed to the switch Created: 09/Jan/16  Updated: 19/Oct/17  Resolved: 10/Feb/16

Status: Resolved
Project: vtn
Component/s: VTN Manager
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Karthik Sivasamy 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

Attachments: Text File setport.log    
External issue ID: 4915

 Description   

I observed when i create flowfilter by setting VTNSetPortSrcAction and VTNSetPortSrcAction. It is created and ping success.

While giving dumpflow in mininet it is not listed.
In log it says Flow action was ignored.

Below are the test configurations, with mininet dumpflow and attached log.

How to reproduce issue:
configuration:

Created VTN, VBR Interfaces
if1 portmapping - "tenant-name":"vtn1", "bridge-name":"vbr1", "interface-name":"if1", "node":"openflow:2", "port-name":"s2-eth1"
if2 portmapping - "tenant-name":"vtn1", "bridge-name":"vbr1", "interface-name":"if1", "node":"openflow:2", "port-name":"s2-eth1"

Flowcondition:
curl --user "admin":"admin" -H "Content-type: application/json" -X POST http://localhost:8181/restconf/operations/vtn-flow-condition:set-flow-condition -d '{"input":{"operation":"SET","present":"false","name":"cond_1","vtn-flow-match":[{"vtn-ether-match":{},"vtn-inet-match":

{"source-network":"10.0.0.1/32","destination-network":"10.0.0.3/32"}

,"index":"1"}]}}'

Flowfilter:
curl -v --user "admin":"admin" -H "Accept: application/json" -H "Content-type: application/json" -X POST http://localhost:8181/restconf/operations/vtn-flow-filter:set-flow-filter -d '{"input": { "tenant-name": "vtn1", "bridge-name": "vbr1", "interface-name": "if1", "vtn-flow-filter": [{"condition": "cond_1","index": "10", "vtn-pass-filter": {}, "vtn-flow-action": [{"order":1,"vtn-set-port-src-action":{"port":1}},{"order":2,"vtn-set-port-dst-action":{"port":3}}]}]}}'

Mininet ping between host h1 and h3:
mininet> h1 ping h3
PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data.
64 bytes from 10.0.0.3: icmp_seq=1 ttl=64 time=22.9 ms
64 bytes from 10.0.0.3: icmp_seq=2 ttl=64 time=0.776 ms

Dumpflow:

mininet> dpctl dump-flows

      • s1 ------------------------------------------------------------------------
        NXST_FLOW reply (xid=0x4):
        cookie=0x7f5600000000000f, duration=8.022s, table=0, n_packets=7, n_bytes=630, idle_age=2, priority=10,in_port=2,vlan_tci=0x0000,dl_src=5a:1a:e5:19:5d:68,dl_dst=8e:f4:bd:ac:60:73 actions=output:1
        cookie=0x7f56000000000010, duration=3.012s, table=0, n_packets=0, n_bytes=0, idle_age=3, priority=11,arp,in_port=1,vlan_tci=0x0000,dl_src=8e:f4:bd:ac:60:73,dl_dst=5a:1a:e5:19:5d:68 actions=output:2
        cookie=0x7f5600000000000e, duration=8.039s, table=0, n_packets=6, n_bytes=588, idle_age=2, priority=13,ip,in_port=1,vlan_tci=0x0000,dl_src=8e:f4:bd:ac:60:73,dl_dst=5a:1a:e5:19:5d:68,nw_src=10.0.0.1,nw_dst=10.0.0.3 actions=output:2
      • s2 ------------------------------------------------------------------------
        NXST_FLOW reply (xid=0x4):
        cookie=0x7f5600000000000f, duration=8.031s, table=0, n_packets=7, n_bytes=630, idle_age=2, priority=10,in_port=3,vlan_tci=0x0000,dl_src=5a:1a:e5:19:5d:68,dl_dst=8e:f4:bd:ac:60:73 actions=output:1
        cookie=0x7f56000000000010, duration=3.018s, table=0, n_packets=0, n_bytes=0, idle_timeout=300, idle_age=3, priority=11,arp,in_port=1,vlan_tci=0x0000,dl_src=8e:f4:bd:ac:60:73,dl_dst=5a:1a:e5:19:5d:68 actions=output:3
        cookie=0x7f5600000000000e, duration=8.043s, table=0, n_packets=6, n_bytes=588, idle_timeout=300, idle_age=2, priority=13,ip,in_port=1,vlan_tci=0x0000,dl_src=8e:f4:bd:ac:60:73,dl_dst=5a:1a:e5:19:5d:68,nw_src=10.0.0.1,nw_dst=10.0.0.3 actions=output:3
      • s3 ------------------------------------------------------------------------
        NXST_FLOW reply (xid=0x4):
        cookie=0x7f5600000000000f, duration=8.038s, table=0, n_packets=7, n_bytes=630, idle_timeout=300, idle_age=2, priority=10,in_port=1,vlan_tci=0x0000,dl_src=5a:1a:e5:19:5d:68,dl_dst=8e:f4:bd:ac:60:73 actions=output:3
        cookie=0x7f56000000000010, duration=3.03s, table=0, n_packets=0, n_bytes=0, idle_age=3, priority=11,arp,in_port=3,vlan_tci=0x0000,dl_src=8e:f4:bd:ac:60:73,dl_dst=5a:1a:e5:19:5d:68 actions=output:1
        cookie=0x7f5600000000000e, duration=8.057s, table=0, n_packets=6, n_bytes=588, idle_age=2, priority=13,ip,in_port=3,vlan_tci=0x0000,dl_src=8e:f4:bd:ac:60:73,dl_dst=5a:1a:e5:19:5d:68,nw_src=10.0.0.1,nw_dst=10.0.0.3 actions=output:1

 Comments   
Comment by Karthik Sivasamy [ 09/Jan/16 ]

Attachment setport.log has been added with description: Karaf log enabled TRACE for setport action

Comment by Hideyuki Tai [ 15/Jan/16 ]

I think it is not a bug.

As the YANG model file explains, the `vtn-set-port-dst-action' and `vtn-set-port-src-action' actions only affect TCP or UDP packets on IPv4.

FYI: https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-filter.html

However, it seems to me that you just sent ICMP packets which were not TCP or UDP packets.

I think if you send TCP or UDP packets into your virtual bridge, you would see flow entries which have an action which changes TCP or UDP port number.

So could you check your scenario again?

Comment by Karthik Sivasamy [ 10/Feb/16 ]

This is not a bug.

Verified when TCP packet is genreated in mininet and TCP is send into virtual bridge, port number is set in FLowentries.
i.e., actions "VTNSetPortSrcAction" and "VTNSetPortSrcAction" is listed in Flowentries.

Hence closing the bug.

Generated at Wed Feb 07 20:48:01 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.