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

a subnet mask of /24. Note that 10.10.10.1 here is the IP address of the switch which has an
OpenFlow listen port open on port 6633.
openflow@openflow-ubuntu-08:~$ ovs-ofctl add-flow
tcp:10.10.0.1:6633 ip,nw_src=1.1.1.1/24,actions=output:1
To verify that this flow has been installed on the switch, we run the ovs-ofctl command and
verify the output.
openflow@openflow-ubuntu-08:~$ ovs-ofctl dump-flows tcp:10.10.0.1:6633
NXST_FLOW reply (xid=0x4): cookie=0x0, duration=13.535s, table=0,
n_packets=0, n_bytes=0, ip,nw_src=1.1.0.0/24 actions=output:1
The show openflow instance t1 flows command when executed on the HP switch displays
the following:
Example
HP-3500yl-48G-PoEP(of-inst-t1)# show openflow instance t1
Configured OF Version : 1.3
Negotiated OF Version : 1.3
Instance Name : t1
Admin. Status : Enabled
Member List : VLAN 3
Listen Port : None
Oper. Status : Up
Oper. Status Reason : NA
Datapath ID : 0003b499ba86bf80
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
Probe Interval : 10 seconds
Hw. Table Miss Count : NA
No. of Sw Flow Tables : 1
Egress Only Ports : None
Table Model : Policy Engine and Software
Controller Id Connection Status Connection State Secure Role
------------- ----------------- ---------------- ------ ------
1 Connected Active Yes Equal
Virtualization mode verses Aggregation mode — VLAN tags in packet_in
messages
There is a difference in the packet_in messages that are sent to the OpenFlow controller by the
switch based on the mode that the OpenFlow instance is operating in. In Virtualization mode, no
VLAN tags are sent in packet_in messages sent to the OpenFlow controller. Even if the packets
that came in to the switch on the OpenFlow instance had VLAN tags, they will get removed by the
switch in packet_in messages sent to the controller. Flows that match on VLAN PCP or modify
VLAN PCP are not supported in Virtualization mode. Any tagged packets that are received in
Virtualization mode may have their PCP modified to default. VLAN PCP isn’t matched because tag
is always stripped in Virtualization mode.
In Aggregate mode, VLAN tags are always sent by the switch in packet_in messages sent to
the OpenFlow controller. Even if the packets that came in to the switch on the OpenFlow instance
did not have VLAN tags, they will be added by the switch in packet_in messages sent to the
controller. The switch adds a VLAN tag either based on the tag that the packet already carried
74 Implementation notes