-
Type: Bug
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.10.0
-
Component/s: None
-
Labels:None
Issue described in https://groups.google.com/a/onosproject.org/forum/#!topic/onos-dev/1U1vXEbOLDs
Highlighting it again here:
I am attempting to add an MPLS_POP flow via rest and I am noticing a
disconnect between what I am sending and what I am seeing via
ovs-ofctl dump-flows. I am setting the new ethtype to IPv4 but
ovs-ofctl is showing setting it to unicast MPLS. I am using ONOs
1.9.0 and OVS 2.6.1
Tom
Rule that I am posting:
{
"priority": 1333,
"timeout": 0,
"isPermanent": true,
"deviceId": "of:99000000000000b1",
"treatment": {
"instructions": [
,
{ "type": "OUTPUT", "port": "2" } ]
},
"selector": {
"criteria": [
,
,
{ "type": "MPLS_LABEL", "label": "30" } ]
}
}
Rule showing up via ovs-ofctl dump-flows:
cookie=0x68000020d57c43, duration=31.331s, table=0, n_packets=0,
n_bytes=0, idle_age=31, priority=1333,mpls,in_port=1,mpls_label=30
actions=pop_mpls:0x8847,output:2