Dear experts,
I am trying the networking-sfc with NSH support in the all-in-one Openstack deploying from devstack. But in my environment, the OVS always can not accept the NSH related flow rules from SFC driver. The following are the corresponding flows and the received error.
For table 5, I got:
"hard_timeout=0,idle_timeout=0,priority=0,cookie=18389747003163845,table=5,dl_dst=fa:16:3e:d3:ad:66,eth_type=2048,actions=encap(hdr=nsh,prop(class=nsh,type=md_type,val=1)),set_field:0x1->nsh_spi,set_field:0xff->nsh_si,encap(hdr=ethernet),mod_vlan_vid:16,,resubmit(,10)" -O openflow13
We got Encap header nsh not support
For table 10, I got:
hard_timeout=0,idle_timeout=0,priority=1,cookie=1291058868797254279,nsh_spi=1,nsh_mdtype=1,eth_type=35151,table=10,dl_dst=fa:16:3e:c8:ed:35,dl_vlan=17,nsh_si=255,actions=strip_vlan,move:NXM_OF_ETH_DST->OXM_OF_PKT_REG[0..47],decap(),decap(),move:OXM_OF_PKT_REG[0..47]->NXM_OF_ETH_DST,output:40; Stdout: ; Stderr: ovs-ofctl: -:1: OXM_OF_PKT_REG[0..47]: unknown field `OXM_OF_PKT_REG'
I saw the bug log of https://bugs.launchpad.net/networking-sfc/+bug/1753349. All of the corresponding rules can be well inserted. I have tried the OVS from 2.8.1 to 2.9.0 by installing via apt-get or building from source. The result is the same. I would lie to ask if any further configuration need to set on (1) OVS or (2) Neutron? Thanks in advance.
Blessings
Alan JW Chang