connectivity problem provision-comware in openflow-only mode (NOT hybrid)

Martin Cerveny — Sat, 02 Aug 2014 11:55:58 GMT

Hello.

I waited for new version of VAN SDN ver. 2.3, but i am still not able to successfully connect provision and comware in openflow-only mode (hybrid.mode = false).

There is my simple setup:

host - (port2) - provision 3800 (KA.15.15.0006) - (port 4) - (port 4) - comware 5500EI (5.20.99 R2221P02) - (port 2) - host

1) 5500 is successfully registered after attach (see cp_1.png)

2) controller begins discovery (PACKET_OUT) over 3800 and 5500 (see cp_2.png time 12:04:*)

- over 3800 send over 2 "live" ports (2 and 4) 2 packets (both LLDP one with destination LLDP_Multicast (01:80:c2:00:00:0e) and one with HP_proprietary_multicast (01:1b:78:e9:7b:cd)

- over 5500 do the same thing

3) controller receives unhandled packet (PACKET_IN)

- over 3800 both packed comes

- over 5500 ONLY one packet is received (with destination HP_proprietary_multicast (01:1b:78:e9:7b:cd)), I suppose that comware due to firmware error process LLDP_Multicast packet (on both switches is LLDP disabled).

4) controller controller probably decides that link is not "up" in both direction. I continues sending in periodic interval discovery on both port 2 (host connectivity) AND on port 4 on 3800. (see cp_2.png time 12:05:*).

5) the state is stable, bud there is no connectivity between hosts. If host on 3800 send ARP-broadcast, it is delivered from 3800 to controller (PACKET_IN), send by FLOOD on 3800 (PACKET_OUT), received on 5500 (PACKET_IN) and dropped by controller (expecting FLOOD on 5500). (see arp_err.png time 13:00:27).

Question part:

1) Why actual firmware on 5500 consume LLDP packet even is LLDP disabled ?

2) Why controller does not recognize received LLDP packet (with HP_proprietary_multicast destination) as successful link establishment ?

3) How to solve the problem ?

3.1) Will be some newer firmware for 5500EI ?

3.2) Will be VAN SDN controller patched to work correctly ?

3.3) Did I miss something in setup (on controller or on 5500) ?

Thanks, Martin Cerveny

PS: with 2x 3800 it is working as expected (see pp_2.png (link establishment) and pp_3.png periodic link discovery (without port 4)).

Re: connectivity problem provision-comware in openflow-only mode (NOT hybrid)

sdnindia — Fri, 08 Aug 2014 19:07:48 GMT

Hello Martin Cerveny,

Thanks for your query.
We will get back to you shortly.

Thanks,
HP SDN Team

Re: connectivity problem provision-comware in openflow-only mode (NOT hybrid)

sdnindia — Thu, 18 Sep 2014 16:51:23 GMT

Hello Martin Cerveny,

Apologies for the delay. We had to coordinate with different team to get the response, so it took some time.

This problem is resolved in release R221P05, which will be available on the external HP Support site soon.

Resolved problems in A5500EI-CMW520-R2221P05

201407110331

Symptom: In an OpenFlow application, BDDP packets cannot be sent to the controller.
Condition: This symptom can be seen when the following conditions exist:

The switch has a flow table that can send BDDP packets to the controller.

BDDP packets with destination MAC address 0180-C200-000E and EtherType 0x8999 enter the switch through an OpenFlow port.

Thanks,

HP SDN Team

topic Re: connectivity problem provision-comware in openflow-only mode (NOT hybrid) in Software Defined Networking

connectivity problem provision-comware in openflow-only mode (NOT hybrid)

Re: connectivity problem provision-comware in openflow-only mode (NOT hybrid)

Re: connectivity problem provision-comware in openflow-only mode (NOT hybrid)