problem matching vlan-id on HP Procurve 3500 switch (OpenFlow)

[progloverfan]

Hi all. We're students from the University of Concepción, Chile and recently arrived 2 OpenFlow-aware switches, Procurve 3500yl-24G model. For months we have been interacting with the OF protocol in a simulated mode without the possibility of testing in real environment. Now, that at last the devices has arrived we wanted to do some tests on it.

We prefer to use the virtualization mode because it permit the creation of some switches with different DPID with an one underlying physical switch in order to create complex topologies. For this case we have created two switches, named “sw1” and “sw2”, using two OF instances.

We wanted to create a VLAN that permit the communication between pc1 y pc2 using the FloodLight API. The logic is as follows: packets entering in port 14 on “sw1” are tagged with the VLAN identification (VID=100), the same occurs in “sw2” but for packets entering in port 18. Therefore the link between the 2 switches (“sw1” and “sw2”) must support packets tagged (VID=100) as shown in the figure above.

This programming logic was implemented successfully on Mininet, however when the script was inserted in the switches “sw1” and “sw2”, virtualized over a real switch, the flows with the match code “vlan-id” weren't interpreted by these devices.

We like to know if is possible that the switches created from the physical switch can match the VLAN-ID from instances that have other VLAN members. For example that “sw2” can make match “vlan-id=100” even if VLAN5 is a member of the instance on “sw2”. The same for the case on sw1.

In this project we have determined that the switches are able to tag the packets with the VID=100 and forward it through a desired port (see flow1 and flow3), but they aren't able to match the VID=100 and forward it through a desired port (see flow2 and flow4) (the flows just don't get inserted on the controller).

We have managed, using the debug command in HP switches, to capture the flows that weren't pushed successfully with their respective error messages, as well as those flows that were pushed successfully.

The show running config is copy below:

openflow                                                                      

   enable                                                                      

   controller-id 1 ip 192.168.2.11
controller-interface vlan 3                  

   instance "ins1"                                                             

      member vlan 4                                                            

      controller-id 1                                                          

      enable                                                                   

      exit                                                                     

   instance "ins2"                                                             

      member vlan 5                                                            

      controller-id 1                                                          

      enable                                                                   

      exit                                                                     

   exit                                                                        

.

.

.                                                              

vlan 3                                                                         

   name "Controller"                                                          

   untagged 3                                                                  

   ip address 192.168.2.10
255.255.255.0                                        

   exit                                                                        

vlan 4                                                                         

   name "VLAN4"                                                                

   untagged 14-15                                                              

   no ip address                                                               

   exit                                                                        

vlan 5                                                                         

   name "VLAN5"                                                                

   untagged 17-18                                                              

   no ip address                                                               

   exit 

We hope that someone could help us!. Thanks.