SD-WAN

If I set up my application to create flows for Ethernet Type LLDP and then attempt to view the flow list in the controller UI via the Openflow Monitor component (sdn/ui/app/index#ofmon-dp-flows,{dpid}), I get promopted with a generic error code 500 message.

Looking at the logs, these messages appear when I attempted to view the flows, this is just the last three, there are many more:

[2013-04-16 13:05:33.903] WARN  of-io-38-thread-3            hp.of.msglib                                                     DE0005I Parse FAILED: hdr=[V_1_0,MULTIPART_REPLY,492,2174], bytes=[011101ec0000087e00010000006002000010000ffffe0000000000000000000000000000000088cc00000000000000000000000000000000000001cd390aa9400064038407080000000000000000000000000000000000000000000f00000000000007da00000008fffa000000600200003020cbfffe0023df9606060000000000000000000008000001000000000000c0a86e01000000000000003e014fb1807e2c007800b400000000000000000000000000000000000000000008000000000000033000000008fffa000000600200003020cbfffe0023df9606060000000000000000000008000001000000000000c0a80106000000000000003111c31e807e2c007800b40000000000000000000000000000000000000000002f00000000000012ba00000008fffa000000600000003000cffffe00000000000000000000000000000000080000010000c0a80106c0a86e3c00000000000000310660b0c07e2c007800b40000000000000000000000000000000000000000002a000000000000000000000008fffa000000600000003000cffffe00000000000000000000000000000000080000010000c0a86e01c0a86e3c000000000000003d314b04c07e2c007800b400000000000000000000000000000000000000000008000000000000000000000008fffa0000] 
[2013-04-16 13:11:12.380] WARN  of-io-38-thread-3            hp.of.msglib                                                     DE0005I Parse FAILED: hdr=[V_1_0,MULTIPART_REPLY,300,2250], bytes=[0111012c000008ca00010000006002000010000ffffe0000000000000000000000000000000088cc000000000000000000000000000000000000032019de50800064038407080000000000000000000000000000000000000000001a0000000000000d9c00000008fffa000000600200003020cbfffe0023df9606060000000000000000000008000001000000000000c0a801060000000000000019252239c07e2c001e001e00000000000000000000000000000000000000000009000000000000039600000008fffa000000600000003000cffffe00000000000000000000000000000000080000010000c0a80106c0a86e3c00000000000000191945ba007e2c001e001e00000000000000000000000000000000000000000009000000000000000000000008fffa0000] 
[2013-04-16 13:19:38.670] WARN  of-io-38-thread-3            hp.of.msglib                                                     DE0005I Parse FAILED: hdr=[V_1_0,MULTIPART_REPLY,396,2368], bytes=[0111018c000009400001000000600000003820effffe00000000000000000000000000000000080600000000000000000000000000000000000000722489a34000640384070800000000000000000000000000000000000000000006000000000000000000000008fffa0000006002000010000ffffe0000000000000000000000000000000088cc00000000000000000000000000000000000001782cd29c0000640384070800000000000000000000000000000000000000000008000000000000043000000008fffa000000600200003020cbfffe0023df9606060000000000000000000008000001000000000000c0a80106000000000000001a00b71b007e2c007800b400000000000000000000000000000000000000000006000000000000026400000008fffa000000600000003000cffffe00000000000000000000000000000000080000010000c0a80106c0a86e3c0000000000000019307565407e2c007800b400000000000000000000000000000000000000000006000000000000000000000008fffa0000] 

Attempting to retrieve a list of flows using the API (/of/datapaths/{dpid}/flows) returns the following error message:

{
  "error": "java.lang.IllegalStateException",
  "message": "Timed-out waiting for response"
}

I am however able to view the flows without any problems using the command "(config)# show openflow instance aggregate flows" on a HP 3800 switch with image version KA.15.10.0009.

It is noteworthy that when I try to view the flows on the switch, the Ethernet Type for other protocols are labeled specificly with their short name such as ARP or IP, while the same field for LLDP flows contains 0x88CC and not the short name.

Is this an expected behaviour?

Hello Sepbot

Thanks fur posting your query. We are currently looking into the query, in the meantime would you be able to give us the following

Could you please share the exact JSON that you used for adding the LLDP flow and the Flow as well on the switch.

Is the error intermittent? Do you see the same error when you try to view the Flow from Controller UI?

Is the Flow added successfully?

Thanks,

HP SDN Team

Hello Sepbot,

The issue you mentioned was a known issue that was affecting HP VAN SDN Controller Release 2.0 operations .This has been fixed with our new Firmware  release K/KA/WB.15.15.0006. (For 3800, the KA version must be used). The Web released software can be accessed from this link www.hp.com/networking/support

Enter a product # or description – e.g 5406” check the box for the 5406

Click on “display selected”

Click on the link “software downloads”->It will take you to: 

https://h10145.www1.hp.com/downloads/SoftwareReleases.aspx?ProductNumber=J9642A

Sign in with a passport account to dowload the software( specifically that mentions "Early Avaialbility")  

EA –  Early Availability – should be evaluated prior to moving it to a production environment

GA – General Availability – considered production ready. 

Please download the firmware and keep us posted on the status.

Thanks

Sudha.