topic Re: Vlan tagging to connect OpenFlow switchs in Software Defined Networking

Vlan tagging to connect OpenFlow switchs

sbotkine — Tue, 06 May 2014 07:05:02 GMT

Hello,

For my first Openflow test, I connected 4 HP switches (2x3500 and 2x3800 image K.15.15.0006). I am using the HP VAN SDN Controller with Openflow 1.3.

In my fisrt test I was using only one OpenFlow VLAN. I've created one OpenFlow instance in a non aggregate mode (because I had only one VLAN).

On links between the switches, I used this VLAN in UNTAGGED mode.

Learning switch worked correctly, my computers could exchange correct traffic.

For my second test, I nned to use different OpenFlow VLAN. I then replaced my OpenFlow instance by an aggregate mode.

I've create 3 VLANs.

On links connection between switches, I am using now my 3 VLAN in TAGGED mode.

I am still using the Learning switch, my computer can exchange traffic, but I have full of LOGS Like:

[2014-05-06 08:39:17.799] WARN of-io-35-thread-4 hp.sdn.net.path DE0005I 10:00:f0:92:1c:21:a8:40 0x6 DNS - Path from 74:8e:f8:24:1a:00 to 00:18:8b:a8:55:4e is invalid!
[2014-05-06 08:39:17.983] ERROR of-io-35-thread-3 hp.sdn.net.topo DE0005I cluster()::No active running topology
[2014-05-06 08:39:17.984] ERROR of-io-35-thread-3 hp.sdn.net.topo DE0005I cluster()::No active running topology
[2014-05-06 08:39:17.984] WARN of-io-35-thread-3 hp.sdn.net.path DE0005I 10:00:c0:91:34:e7:b5:c0 0x5 ARP - Path from 00:1e:c2:02:8a:2c to 00:18:8b:a8:55:4e is invalid!
[2014-05-06 08:39:17.985] ERROR of-io-35-thread-2 hp.sdn.net.topo DE0005I cluster()::No active running topology
[2014-05-06 08:39:17.986] ERROR of-io-35-thread-2 hp.sdn.net.topo DE0005I cluster()::No active running topology
[2014-05-06 08:39:17.986] WARN of-io-35-thread-2 hp.sdn.net.path DE0005I 10:00:3c:4a:92:fa:cd:80 0x5 ARP - Path from 00:1e:c2:02:8a:2c to 00:18:8b:a8:55:4e is invalid!
[2014-05-06 08:39:17.987] ERROR of-io-35-thread-4 hp.sdn.net.topo DE0005I cluster()::No active running topology
[2014-05-06 08:39:17.987] ERROR of-io-35-thread-4 hp.sdn.net.topo DE0005I cluster()::No active running topology
[2014-05-06 08:39:17.987] WARN of-io-35-thread-4 hp.sdn.net.path DE0005I 10:00:f0:92:1c:21:a8:40 0x6 ARP - Path from 00:1e:c2:02:8a:2c to 00:18:8b:a8:55:4e is invalid!
[2014-05-06 08:39:17.991] ERROR of-io-35-thread-2 hp.sdn.net.topo DE0005I cluster()::No active running topology
[2014-05-06 08:39:17.991] ERROR of-io-35-thread-2 hp.sdn.net.topo DE0005I cluster()::No active running topology
[2014-05-06 08:39:17.991] WARN of-io-35-thread-2 hp.sdn.net.path DE0005I 10:00:3c:4a:92:fa:cd:80 0x6 UNKNOWN - Path from 00:18:8b:a8:55:4e to 00:1e:c2:02:8a:2c is invalid!
[2014-05-06 08:39:17.992] ERROR of-io-35-thread-3 hp.sdn.net.topo DE0005I cluster()::No active running topology
[2014-05-06 08:39:17.993] ERROR of-io-35-thread-3 hp.sdn.net.topo DE0005I cluster()::No active running topology
[2014-05-06 08:39:17.993] WARN of-io-35-thread-3 hp.sdn.net.path DE0005I 10:00:c0:91:34:e7:b5:c0 0x6 UNKNOWN - Path from 00:18:8b:a8:55:4e to 00:1e:c2:02:8a:2c is invalid!
[2014-05-06 08:39:17.994] ERROR of-io-35-thread-1 hp.sdn.net.topo DE0005I cluster()::No active running topology

The main message is "Path is invlaid".

Where is my error. Did the learning switch work correctly with VLAN tagging ?

Here is the config I have on my 4 switches:

Open Flow VLAN are 224, 136 and 20

Switch are cascaded from PORT 5, to PORT 6

Controller VLAN is 23

openflow
controller-id 1 ip 130.223.23.100 controller-interface vlan 23
instance aggregate
controller-id 1
software-flow-table 4
version 1.3
enable
exit
enable
exit
oobm
ip address 130.223.38.9 255.255.252.0
ip default-gateway 130.223.36.1
exit
vlan 1
name "DEFAULT_VLAN"
no untagged 1-2,5-24
untagged 3-4,25-26
ip address dhcp-bootp
exit
vlan 20
name "sdn-client"
untagged 7-23
tagged 5-6
no ip address
exit
vlan 23
name "sdn-cnt"
untagged 24
tagged 1-2
ip address 130.223.23.102 255.255.255.0
exit
vlan 136
name "wlmm"
tagged 5-6
no ip address
exit
vlan 224
name "wls1"
tagged 5-6
no ip address
exit

Do you see a problem ?

Re: Vlan tagging to connect OpenFlow switchs

Gerhard Roets — Mon, 19 May 2014 15:51:43 GMT

Hi Sbotkine

Is there a seperate OpenFLow management network ?, or does it share the links that the OpenFlow controlled traffic will run on ?

Thanks in advance

Gerhard

Re: Vlan tagging to connect OpenFlow switchs

sbotkine — Tue, 20 May 2014 12:12:34 GMT

No I am using the vlan 23 for the management vlan and this vlan use the it's own physical interface (port 1 and 2, as you can see on the configuration in my first message.

Trafic (vlan 20, 136 and 224) use physical interface 5 and 6 on each switch.

Re: Vlan tagging to connect OpenFlow switchs

sdnindia — Tue, 20 May 2014 14:57:11 GMT

Hello sbotkine,

As per the HP VAN SDN Controller release notes [ page 4-5]

" Tagged link between two devices is not discovered (CR138547)—If a link exists between a pair of ports tagged to two different VLAN instances in Aggregate mode in

OpenFlow, links are discovered correctly in the HP VAN SDN Controller between only one of the VLAN instances.

The link between the other VLAN instances is not discovered. This issue does not occur in Virtualized mode."

Also from the configuration shared by you, there are three VLAN ( i.e. Open Flow VLAN are 224, 136 and 20) in tagged mode ,switches are cascaded from PORT 5 to PORT 6 and these ports are tagged to different VLANs.

Also we suggest to use KA version firmware for 3800.

Thanks,

HP SDN Team

Re: Vlan tagging to connect OpenFlow switchs

sbotkine — Wed, 21 May 2014 05:31:19 GMT

Hello,

Thanks for your answer.

Is the CR138547 a normal issue or an issue that is suppose to be corrected in the future HP VAN SDN version ?

That means for the moment it is not possible to use differents VLAN between different switchs by using only one pair of port (one link) betwen switchs ?

Moreover, what is the difference betwen KA and K version ? And why KA version would be more interesting for my problem ?

Regards,

Serge

Re: Vlan tagging to connect OpenFlow switchs

sdnindia — Tue, 03 Jun 2014 17:12:22 GMT

Hello sbotkine,

CR 138547 was found to be a problem with the switch software. As long as the controller being used is version 2.0 or later and the switch software being used is KA.15.14.0003, K.15.14.0003, or WB.15.14.0002 or later, CR 138547 should not be an issue. Only one VLAN can be added as a member of an OpenFlow instance in virtualization mode. An aggregate instance includes all VLANs except the management VLAN and the OpenFlow controller VLANs.

The difference between K and KA switch software is that K software is for the 3500, 5400, 6200, 6600, and 8200 series switches. KA software is for the 3800 switches only.

Thanks,

HP SDN Team

Re: Vlan tagging to connect OpenFlow switchs

sbotkine — Thu, 05 Jun 2014 09:02:35 GMT

Hello,

" As long as the controller being used is version 2.0 or later and the switch software being used is KA.15.14.0003, K.15.14.0003, or WB.15.14.0002 or later, CR 138547 should not be an issue."

I am using the version KA.15.15.0006 on my switchs but still the same type of errors:

...

[2014-06-05 10:59:36.015] ERROR of-io-35-thread-1 hp.sdn.net.topo DE0005I cluster()::No active running topology
[2014-06-05 10:59:36.015] WARN of-io-35-thread-1 hp.sdn.net.path DE0005I 10:00:f0:92:1c:21:fa:c0 0x6 ICMP - Path from 00:18:8b:a8:55:4e to 74:8e:f8:24:1a:00 is invalid!
[2014-06-05 10:59:36.018] ERROR of-io-35-thread-2 hp.sdn.net.topo DE0005I cluster()::No active running topology
[2014-06-05 10:59:36.018] ERROR of-io-35-thread-2 hp.sdn.net.topo DE0005I cluster()::No active running topology
[2014-06-05 10:59:36.028] WARN of-io-35-thread-2 hp.sdn.net.path DE0005I 10:00:f0:92:1c:21:a8:40 0x5 ICMP - Path from 74:8e:f8:24:1a:00 to 00:18:8b:a8:55:4e is invalid!

...

Do I have to decrease to KA.15.14.0003 to make it working with VLAN tagging ???

Regards,

Serge

Re: Vlan tagging to connect OpenFlow switchs

sdnindia — Fri, 20 Jun 2014 09:01:29 GMT

Hello sbotkine,

The cause for the error/warning in the log is because the PathDeamon component has not found a valid path between the two devices and this is because a topology has not formed as the links are not discovered between them using LLDP.Traffic may still be flowing between the devices because the PathDeamon, when not able to pave the path, will flood the packets if the port can broadcast. There may be no flows to direct traffic using OpenFlow, however.

To confirm this, we need to see if there is any link between the devices. To do this, please share the output from /net/links REST API. This is under /links from the main RSdoc page on the controller.

Thanks,

HP SDN Team

Re: Vlan tagging to connect OpenFlow switchs

sdnindia — Mon, 30 Jun 2014 17:46:21 GMT

Hello sbotkine,

Doing a follow up to check if you need any further assistance with respect to the query posted.

Please do let us know if your problem is solved.

If 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

Re: Vlan tagging to connect OpenFlow switchs

sbotkine — Wed, 16 Jul 2014 13:22:19 GMT

Hello,

Here is the

If I connect my two switch from port 5 to port 6 with the following configuration (I am in an aggregate mode)

On switch 1:

vlan 20
name "sdn-client"
untagged 5
no ip address
exit

On switch 2:

vlan 20

name "sdn-client"
untagged 6
no ip address
exit

Here is the following RSDOC rest command result:

GET /net/links => https://130.223.16.128:8443/sdn/v2.0/net/links

{
"links": [
{
"src_dpid": "10:00:f0:92:1c:21:a8:40",
"src_port": 5,
"dst_dpid": "10:00:f0:92:1c:21:fa:c0",
"dst_port": 6,
"info": {
"link_type": "directLink",
"src_port_state": [
"live"
],
"dst_port_state": [
"live"
]
}
},
{
"src_dpid": "10:00:f0:92:1c:21:fa:c0",
"src_port": 6,
"dst_dpid": "10:00:f0:92:1c:21:a8:40",
"dst_port": 5,
"info": {
"link_type": "directLink",
"src_port_state": [
"live"
],
"dst_port_state": [
"live"
]
}
}
]
}

Now if I change the configuration on my two switchs by tagging the ports:

vlan 20
name "sdn-client"
tag 5
no ip address
exit

On switch 2:

vlan 20
name "sdn-client"
tag 6
no ip address
exit

Here is the following RSDOC rest command result:

GET /net/links => https://130.223.16.128:8443/sdn/v2.0/net/links

{
"links": []
}

The links doesn't exist !!!!!! Even after a lot of disable/enable of the ports.

Re: Vlan tagging to connect OpenFlow switchs

sdnindia — Thu, 24 Jul 2014 17:12:32 GMT

Hello sbotkine,

Could you please let us know the controller version?

Thanks,

HP SDN Team

Re: Vlan tagging to connect OpenFlow switchs

sbotkine — Tue, 29 Jul 2014 07:55:40 GMT

yes, this is the version 2.0

Re: Vlan tagging to connect OpenFlow switchs

sdnindia — Fri, 08 Aug 2014 18:36:22 GMT

Hello sbotkine,

Please upgrade to version 2.2.5 and let us know if you still face any issue.

Thanks,

HP SDN Team

Re: Vlan tagging to connect OpenFlow switchs

cmaxwell — Wed, 30 Jul 2014 16:31:11 GMT

sdnindia meant to say version 2.2. You can download that version here: https://h10145.www1.hp.com/downloads/DownloadSoftware.aspx?SoftwareReleaseUId=10970&ProductNumber=J9863AAE&lang=&cc=&prodSeriesId=&SerialNumber=&PurchaseDate=

Re: Vlan tagging to connect OpenFlow switchs

Chethan_R — Fri, 27 Mar 2015 13:10:07 GMT

Hi ,

I have configured Openflow in aggregate mode and established the connection between openflow switch and controller

Below is my setup details:

SRC host (VLAN 600) <--> (VLAN 600) Openflow Switch (VLAN 600) <--> (VLAN 600) DST host

When the openflow is disabled, ping from source to destination via openflow switch is successful whereas when the openflow is enabled, ping is getting failed as the VLAN 600 is memeber of openflow instance.

Note: ports which connected to Source and Destination are in tagged mode to VLAN 600

I have added flows (have added 2 flows for to and fro data traffic) in this openflow switch in Software table via controller by using Curl command. I could see the flows getting added in switch. But, it is not getting effected as the "Packets" and "Bytes" fields shows zero even with data traffic in place.

It seems I am missing some configuration in switch to make the added flows get effected.

Note: I have tried by enabling as well disabling the egress-only-ports. But, didn't see any difference in output.

I have attached the screenshot of flow table entries of switch which captured from controller. Kindly take a look for reference.

Kindly let me know your suggestion to resolve this issue.

Regards

Chethan