kytos-ng / telemetry_int

Kytos Telemetry Napp
MIT License
0 stars 2 forks source link

bug: when creating an EPL, table 2 on NoviFlow pipeline resulted in `BadMatchCode.OFPBMC_BAD_WILDCARDS` #43

Closed viniarck closed 8 months ago

viniarck commented 10 months ago

This flow resulted in BadMatchCode.OFPBMC_BAD_WILDCARDS. It's a pipeline configuration issue, so the application is pushing what was described on EP031, but the pipeline on NoviFlow configuration wasn't supporting it, so this is a bug/reminder to make sure that the augmented EP031 will specify a new table, or network engineers will also change the config of table 2 to be flexible enough (which was what the spec was assuming so far), so this is a reminder to augment or review that part.

{
    "flows": [
        {
            "owner": "telemetry_int",
            "cookie": 12112347931636285000,
            "match": {
                "in_port": 15
            },
            "table_id": 2,
            "table_group": "base",
            "priority": 10000,
            "instructions": [
                {
                    "instruction_type": "apply_actions",
                    "actions": [
                        {
                            "action_type": "add_int_metadata"
                        },
                        {
                            "action_type": "output",
                            "port": 17
                        }
                    ]
                }
            ]
        }
    ]
}
+--------------+
    | Table id: 2  |
    +--------------+
    Flowtable Type:           Exactmatch
    Max Entries:              4000
    Matchfields:
      OFPXMT_OFB_IN_PORT
      OFPXMT_OFB_VLAN_VID