Not able to Connect VAN SDN Controller to HP Altoline 6940

[Lokesh9356]

I am not able to connect to VAN SDN Controller , below are the packet traces . 

2016-07-13T16:59:55.164Z

CkPt

Recording started [10s]

2016-07-13T16:59:55.439Z

Conn

d1:11:48:0f:cf:af:47:7f

2016-07-13T16:59:55.440Z

Rx

d1:11:48:0f:cf:af:47:7f

{ofm:[V_1_3,HELLO,8,8614]}

2016-07-13T16:59:55.440Z

Tx

d1:11:48:0f:cf:af:47:7f

{ofm:[V_1_3,HELLO,16,8614],elems=VERSION_BITMAP}

2016-07-13T16:59:55.440Z

Tx

d1:11:48:0f:cf:af:47:7f

{ofm:[V_1_3,FEATURES_REQUEST,8,144246]}

2016-07-13T16:59:55.441Z

Rx

d1:11:48:0f:cf:af:47:7f

{ofm:[V_1_3,FEATURES_REPLY,32,144246],dpid=d1:11:48:0f:cf:af:47:7f,#buf=256,#tab=254,aux=0,cap=[flowStats, tableStats, portStats, groupStats]}

2016-07-13T16:59:55.441Z

Tx

d1:11:48:0f:cf:af:47:7f

{ofm:[V_1_3,SET_CONFIG,12,144247],flags=[fragReasm],msLen=65535}

2016-07-13T16:59:55.441Z

Tx

d1:11:48:0f:cf:af:47:7f

{ofm:[V_1_3,MULTIPART_REQUEST,16,144248],DESC,flgs=null,body=(no body)}

2016-07-13T16:59:55.442Z

Tx

d1:11:48:0f:cf:af:47:7f

{ofm:[V_1_3,MULTIPART_REQUEST,16,144249],PORT_DESC,flgs=null,body=(no body)}

2016-07-13T16:59:55.442Z

Tx

d1:11:48:0f:cf:af:47:7f

{ofm:[V_1_3,MULTIPART_REQUEST,16,144250],TABLE_FEATURES,flgs=null,body={TableFeats: count=0}}

2016-07-13T16:59:55.442Z

Rx

d1:11:48:0f:cf:af:47:7f

{ofm:[V_1_3,ERROR,24,144247],SWITCH_CONFIG_FAILED/EPERM,#dataBytes=12,OFM-cause:[V_1_3,SET_CONFIG,12,144247]}

2016-07-13T16:59:55.443Z

Rx

d1:11:48:0f:cf:af:47:7f

{ofm:[V_1_3,MULTIPART_REPLY,1072,144248],DESC,flgs=[],body={mfr:Pica8, Inc.,hw=HP5712,sw=PicOS 2.7.1,...}}

2016-07-13T16:59:55.443Z

Rx

d1:11:48:0f:cf:af:47:7f

{ofm:[V_1_3,MULTIPART_REPLY,144,144249],PORT_DESC,flgs=[],body={Array::Ports: count=2}}

2016-07-13T16:59:55.465Z

Rx

d1:11:48:0f:cf:af:47:7f

{ofm:[V_1_3,MULTIPART_REPLY,64000,144250],TABLE_FEATURES,flgs=[replyMore],body={TableFeats: count=38}}

The same works with and ODL controller.

Am i missing some configurations ?

[Scott_Koster]

Unfortunately the Altoline switches are not currently supported on the VAN SDN Controller.

For future reference, please see the VAN SDN Controller Application and Support Matrix for the list of switches supported in the 2.7.10 version of the VAN SDN Controller.  Look on pages 13-18.  The Support matrix can be found on the link below.

VAN SDN Controller Documents

[ShaunWackerly]

Would you be able to upload a packet trace (.pcap file) of the OpenFlow conversation? The pieces of the conversation shown are messages between the altoline switch and controller, but they don't show any indication of a failure. Also we can't dig into the details of the conversation, since what's pasted is only a summary version.

The common reason why a switch isn't able to connect to the VAN controller is that the switch rejects some flows that VAN pushes during the initialization phase. Since VAN is unable to initialize the device, it disconnects it.

A common workaround is to use hybrid.mode=false, because it minimizes the number of flows pushed during initialization. However, this approach has its drawbacks because then the VAN controller will need to make the forwarding decision for every packet flowing through the datapath, rather than just the packets it has requested (ARP/DHCP/etc).