I believe the header does include all four of these fields:
https://github.com/floodlight/loxigen/blob/master/openflow_input/standard-1.3#L1172
as defined on page 70 of the spec here:
https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow/openflow-spec-v1.3.1.pdf
There is an error parsing a valid meter config stats reply from a switch. The reply is defined on page 87 of the spec and includes the header which should have 4 fields.
There is an ongoing issue in Floodlight where the controller has difficulty parsing a meter config stats reply (but does fine parsing plain meter and meter features replies). I think this meter band header is the root of the problem, but I haven't had a chance to look into it deep enough yet.
I believe the header does include all four of these fields:
https://github.com/floodlight/loxigen/blob/master/openflow_input/standard-1.3#L1172
as defined on page 70 of the spec here:
https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow/openflow-spec-v1.3.1.pdf
There is an error parsing a valid meter config stats reply from a switch. The reply is defined on page 87 of the spec and includes the header which should have 4 fields.
There is an ongoing issue in Floodlight where the controller has difficulty parsing a meter config stats reply (but does fine parsing plain meter and meter features replies). I think this meter band header is the root of the problem, but I haven't had a chance to look into it deep enough yet.