WB 15.15

OFPERR_OFPBMC_BAD_FIELD (Bad or unsupported match parameter in the flow)

OFPERR_OFPBAC_BAD_TYPE (Bad or unsupported action in the flow)

OFPERR_OFPBIC_BAD_TABLE_ID

OFPERR_OFPFMFC_UNKNOWN (Any internal system error)

Policy engine table restrictions

Error conditions for Table 100, 101, or 102 may result from the following:

• In Aggregate mode, an Output-Port action is allowed only if the flow has VLAN as a match

field or has as a Modify-VLAN action specified.

• Modify VLAN-PCP and P-ToS are the only Set—field actions allowed along with

Output:NORMAL action.

OpenFlow v1.0 instance

OpenFlow 1.0 exposes a single table to the controller. The action of the default

table-miss rule for such an instance is "Goto Controller".

OpenFlow 1.3 instance

OpenFlow 1.3 instance exposes a multi-table model. For every table, the action of

the default table-miss rule is “DROP”. For traffic to traverse the multi-table pipeline,

the table-miss rule for every table must be modified appropriately by the controller.

Example

Consider the table model in standard mode comprised of tables 0, 100,

200-201-202-203:

• If a rule is programed into table 200 that permits traffic, then unless the default

“table-miss rule” for table 100 is modified, traffic will not pass to table 200.

• If the default table-miss rule of table 100 is modified with the action given as

“Gototable 200”, traffic will proceed to table 200. A table-miss rule would

have to be programmed similarly for table 200 and so on.

NOTE: A table-miss rule is a flow with priority of 0 and all match fields

wild-carded.

Flows go missing after addition

Verify the idle-timeout/hard-timeout of the flow.

• Table 50 supports only 12 seconds as the minimum hardware refresh rate. Flows programmed

in this table should have at least an idle-timeout of twice that, or 24 seconds.

• Tables 100/101/102 support a configurable hardware refresh rate. If the “policy-engine-table

refresh-interval” is configured for 5 seconds, then minimum idle-timeout supported would be

10 seconds (double the time configured.)

Missing line rate performance after flows are successfully installed

If an instance is running OpenFlow v1.0 and the flow cannot be accommodated in the hardware

or a higher priority overlapping rule is present in software or we have reached the policy engine

usage limit configured, then . the flow will be housed in the software table. This is verified by the

show openflow instance [instance-name] flows command.

If the flow is programmed in software, line rate performance will not be seen in packet forwarding.

To know which flows will be accommodated in hardware, see the Flow classification section of

this document.

60 Troubleshooting OpenFlow