SDN v2.0 Switch 5400 Openflow V1.0 Voice VLAN test

[Durken]

Hi

SDN contrl V2.0

HP 5412 K15.12.0012 openflow v1.0

We are trying to do the openflow on voice vlan for Lync testing. Data VLAN is untagged and Voice VLAN untagged on the ports. Also the voice VLAN have the "voice" command on.

I have the SDN controller in VLAN 10 Server VLAN and the switch only has a management IP on VLAN 13. We are testing on an edge switch.

Everytime we enable openflow on the switch the phones stop working and try to access lync again but fails.

So I want to clarify a command "controller-id ip 10.2.254.9 controller-interface VLAN 13"

Do I have to use VLAN 10 for the controller-interface or VLAN 13 as it has the IP and default route to the core switch?

We have tried this with VLAN 1 and VLAN 10 with no success.

openflow
controller-id 1 ip 10.2.254.9 controller-interface vlan 10
instance "opfl_lync_test"
member vlan 22
controller-id 1
enable

[Durken]

Just have to add that we get this error.

Server Error – 500: Internal Server Error
Type: error

URL: /sdn/ui/ctl/app/rs/of/datapaths/00:16:f0:92:1c:30:85:00/flows

View ID: oftrace

[Gerhard Roets]

Hi Durken

I would start small with the test and then build up. So the first thing would be to get the infrastrucutre ready then I would proceed to the phase of playing with lync.

So looking at your configuration I would say the following

Step 1. - Can you ping the controller IP from the switch

Step 2. - COnfiguration

controller-id 1 ip 10.2.254.9 controller-interface vlan 10

Observation : vlan 10 implies you will use the IP interface of vlan 10 to reach the controller. This does nto look correct based on what you supplied. You need to change this to vlan 13 since this is where you have the management ip. Also be sure you did not configure this vlan as a management vlan with the management-vlan command; since this will not permit data to be routed in this vlan.

instance "opfl_lync_test"
member vlan 22
controller-id 1
enable

Observation : Here you are saying that vlan 22 will be under the control of openflow. I *assume* this is your voice vlan. I do have one observation if you are planning to use Path Daemon for the establishment of the connection it might introduce a tiny bit of latency.

Presonally I would start by creating a dummy vlan and stick a pc or three in there and first play with that to get it going and see how to get it started and to play a bit with gui and REST and familiarize myself with the controller.

I would suggest you have a look at  K.15.14  since there is numerous openflow fixes and you will have access to the openflow 1.3 protocol which has numerous enhancements  and new possiblities. I would like to stress that this is early availibility and not meant for production use, but I did want to mention it to you as you are starting testing and investigation.

HTH

Gerhard

[sdnindia · Accepted solution]

Hello Durken,

Did you try as per Gerhard’s suggestion?

Doing a follow up to check if you need any further assistance with respect to the query posted. If you feel you query is answered please do let us know by marking the post as an accepted solution.

In case you have more questions on the same topic please do reply on the same thread or open a new post if new topic.

Thanks

 HP SDN Team

[Durken]

Hi All

Firmware update and update controller to 2.1 and all is working fine now. We can see the traffic flows without any errors. Now to start the Lync APP testing.