WB 15.15

Flow modification

Add/Modify/Delete flow

When a request to add, modify or delete a flow mod is rejected by the switch, use the following

command.

Syntax

show openflow instance [instance-name]message-statistics

Example

HP-Stack-3800(config-class)# show openflow instance test

message-statistics

OpenFlow

Message Type Received Rejected

---------------- --------------- --------

OFPT_FLOW_MOD 0 0

OFPT_PORT_MOD 0 0

OFPT_GROUP_MOD 0 0

OFPT_METER_MOD 0 0

Verifying flows

The flow can be verified at the switch by using the following command.

Syntax

show openflow instance [instance-name]flows

Enable debug openflow at the switch. Run the command and observe the debug output for more

specific rejection reasons why the flow is rejected by the switch.

NOTE: Similar troubleshooting techniques can be employed for port-modification,

meter-modification and group-modification issues.

Programming flow errors

When programming flows via a controller, error messages may be returned based on

implementation restrictions in the OpenFlow switch. Examples relevant to OpenFlow 1.3 include:

• Table 0 restrictions

• Table 0, a read-only table, in the OpenFLow 1.3 multiple pipeline represents the start of the

pipeline.

IP control table restrictions

Error conditions for Table 50 may be caused by the following.

• Table-miss rule is read-only.

• Only unicast IP addresses can be used as match parameters in a flow.

• Only “Goto” instruction is supported by this table.

• Flow with invalid VLAN match parameter is not allowed. A VLAN that

does not exist on the switch is considered invalid.

Possible errors returned to the controller:

OFPERR_OFPMFC_EPERM

OFPERR_OFPFMFC_TABLE_FULL

Error messages 59