Software Defined Networking
1828411 Members
3477 Online
109977 Solutions
New Discussion

HP Switch E3500yl not matching packets.

 
SOLVED
Go to solution
PedroH90
Occasional Visitor

HP Switch E3500yl not matching packets.

Hi guys, I hope everybody are fine.


I'm having a problem with the HP-E3500yl switch. Basically, I'm connecting one physical host on port 9 of the HP Switch and another physical host on port 11 of the same switch.
Similar to this:


H1(10.0.0.100) ----- (Port 9) HP(10.0.0.5) (Port 11) ----- H2 (10.0.0.101)

 

In each physical host, I'm using Mininet to create a topology and I want that all the virtual hosts created by Mininet uses the network address and mask 10.0.20.0/24. After the creation, I'm "bridging" one virtual switch created by Mininet and then the virtual hosts can communicate with the rest of the network.

 

Example:


Virtual Host1(10.0.20.10) --- Virtual Switch --- (Port 9)HP Switch(Port 11) --- Virtual Switch ---Virtual Host2 (10.0.20.11)

 

Well, I'm using the Floodlight controller, and H1can ping H2 without problem, and no flows are created in HP, I think the traffic is just passing on the default vlan (vlan 1).

 

Ok, now comes the problem...

I want that Virtual Host 1 and Virtual Host 2 belong to Vlan 2 and for this, the controller is inserting the tag with id 2 on each Virtual Switch, I mean, the packet enters the virtual switch, matches a flow and the action will be put the Vlan Tag 2 on the packet and then sends to the HP Switch. When the packet arrives on HP Switch, I don't know what HP switch is doing with it, because teorically it should occur a match, but nothing is happening (no match and no statistics increment) and the packet doesn't exit HP switch. I used wireshark and I could confirm that the packet is entering the HP Switch with Tag ID 2, but it's not exiting the switch.


Just to add, I'm inserting the flows on HP Switch statically and is indeed there, when I type the "show openflow instance floodlight flows", I can see all flows that I've created.

 

Since  I'm acessing the physical machines H1 and H2 remotely, I need to let H1 and H2 on vlan 1 and both ports connecting them should be untagged, otherwise I lose the communication between my host and them. I let all the interfaces on VLAN 2 tagged. I also can't ping my HP VLAN 2 ip address.

 

This is my configuration:

 

Running configuration:
; J9310A Configuration Editor; Created on release #K.15.13.0005
; Ver #05:08.6f.ff.3f.ef:4d
hostname "HP-E3500yl"
module 1 type j93xxa
sflow 1 destination 10.0.0.7
sflow 1 polling 1-24 20
sflow 1 sampling 1-24 50
ip default-gateway 10.0.0.2
ip routing
snmp-server community "public" unrestricted
openflow
          enable
          controller-id 100 ip 10.0.0.7 controller-interface vlan 1
          instance "floodlight"
                   listen-port
                   member vlan 2
                   controller-id 100
                   limit software-rate 10000
                   enable
                   exit
           exit
vlan 1
        name "DEFAULT_VLAN"
        untagged 1-24
        ip address 10.0.0.5 255.255.255.0
exit

vlan 2
        name "VLAN2"
        tagged 9,11
        ip address 10.0.20.1 255.255.255.0
exit

 

Thank you so much for your attention.

2 REPLIES 2
sdnindia
Trusted Contributor

Re: HP Switch E3500yl not matching packets.

Hello PedroH90,

Thanks for your query.

Could you please provide the following?

1)    Verify whether packet counters for ports 9/11 are incremented by the traffic on VLAN 2.  
2)    Flows that are programmed in HP switch.
3)    In case of 1.0 instance, if packet doesn’t match with any flows in the switch, behavior is to send a packet-in message to controller.
a.    Does Floodlight controller receive any packet in messages? Can we get a Wireshark capture at controller side?
4)    Finally RMON/debug logs from switch side while traffic is being send.


Thanks,
HP SDN Team

PedroH90
Occasional Visitor
Solution

Re: HP Switch E3500yl not matching packets.

Hi sdnindia.

After some tests here, I decided to modificate some things on my topology, changed both interfaces to untagged and now it seems to be working.

 

Thank you.