HP OpenFlow 1.3 Administrator Guide Wired Switches K/KA/KB/WB 15.15

Actions
Controller Port
DUT matches and processes incoming untagged packets for VLAN id
For certain flows with a match on the VLAN ID, even untagged packets are matched. This happens
on untagged ports only. The existing behavior exists because L2 hardware adds the VLAN id and
VLAN priority meta-information irrespective of whether the packet came in tagged or untagged.
Flows which can be accelerated into hardware are put into hardware whereas flows which cannot
be accelerated in hardware are put into software. The observed behavior is observed for hardware
flows. For software flows, the match happens for packets which come with a VLAN tag only and
with proper VLAN id.
Events that change the Operational Status of the OpenFlow instance
The Oper. Status field indicates the operational status of the instance and can be either up or
down. The operational status will be down when either the member VLAN of the OpenFlow instance
does not exist on the switch or the controller VLAN of the OpenFlow instance does not exist on the
switch. In the case when multiple controllers connect over multiple controller VLANs, the operational
status will be down when none of the controller VLANs exist on the switch. When the member
VLAN is down - all ports on the member VLAN are down.
For example, the show openflow instance displays all the OpenFlow instance related
information as follows:
show openflow instance <test>
NOTE: Note that for purposes of this example the instance <test> has been created.
Instance Name : Test
Admin. Status : Enabled
Member List : VLAN 3
Listen Port : 6633
Oper. Status : Down
Datapath ID : 00030026f1212000
Mode : Active
Flow Location : Hardware and Software
No. of Hw Flows : 0
No. of Sw Flows : 0
Hw. Rate Limit : 0 kbps
Sw. Rate Limit : 100 pps
Conn. Interrupt Mode : Fail-Secure
Maximum Backoff Interval : 60 seconds
Controller Id Connection Status Connection State
------------- ----------------- ----------------
2 Disconnected Backoff
OpenFlow's influence on CPU generated packets
In some cases, the CPU generated packets will be effected by the TCAM rules. OpenFlow
Specification 1.0.0. does not clearly outline the behavior for CPU generated packets. One example
of such a case is when a rule is in place with the in_portas a wild-card but has a SRC IP address
that matches the IP address configured on the switch.
OpenFlow supports IP address masking
OpenFlow supports IP subnet mask. Controllers can specify the subnet mask associated with an IP
address and sent to the OpenFlow switch. The switch accepts the IP address with the subnet mask
and associates any packets coming with the subnet mask with the rule.
For example the K.15.10. OpenFlow implementation supports the ability to match on IP address
and subnet mask when the OpenFlow controller programs such flows. Consider this example where
the ovs-ofctl utility is used to add a flow that matches on a network source address of 1.1.1.1 with
DUT matches and processes incoming untagged packets for VLAN id 73