How to use Mesoscale OpenFlow VLAN (1750) between VMs on NW IG and Kettering IG?

[Fei Yeh]

Hello,

Since both NW and Kettering InstaGENI racks are connected to the Mesoscale OpenFlow VLAN (1750), is there a way to just use vlan 1750 to connect between the two VMs?

I have an openflow controller available and have done this but not getting a connection:

within a Slice "feislice1", using Flack, I have provisioned on each rack a VM (xen, Ubuntu12) with a link to a LAN that has the shared-vlan "mesoscale-openflow".  I then provisioned a sliver on the SL AM with the two ports (1 and 2) on vlan 1750 pointed at my controller.  The two VMs are not able to ping each other.

Fei

[Nicholas Bastin]

On Wed, May 21, 2014 at 4:55 PM, Fei Yeh <nufe...@gmail.com> wrote:

within a Slice "feislice1", using Flack, I have provisioned on each rack a VM (xen, Ubuntu12) with a link to a LAN that has the shared-vlan "mesoscale-openflow".  I then provisioned a sliver on the SL AM with the two ports (1 and 2) on vlan 1750 pointed at my controller.  The two VMs are not able to ping each other.

You need to also request a sliver from the FOAM aggregate at the NW and Kettering racks.

--

NIck 

[Nicholas Bastin]

Just to be clear your "AM topology" looks something like this:

NW PG -> NW FOAM -> SL FOAM -> Kettering FOAM -> Kettering PG

Getting your VMs to the shared mesoscale VLAN only gets your packets to the switch, then FOAM has to allocate you the flowspace on the rack switch so you can reach SL.

--

Nick 

[Sarah Edwards]

This exercise might be helpful in figuring out how to request resources from the FOAM OpenFlow aggregates:

http://groups.geni.net/geni/wiki/GENIExperimenter/ExperimentExample-OF

Unfortunately it's out of date, but the concepts are still sound.

--
GENI Users is a community supported mailing list, so please help by responding to questions you know the answer to.
 
If this is your first time posting a question to this list, please review http://groups.geni.net/geni/wiki/GENIExperimenter/CommunityMailingList
---
You received this message because you are subscribed to the Google Groups "GENI Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to geni-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

*******************************************************************************

Sarah Edwards

GENI Project Office

BBN Technologies

Cambridge, MA

phone:    (617) 873-2329

email:    sedw...@bbn.com

[Fei Yeh]

Hi Sarah,

Thanks for the pointer.  Few questions:

1. The example does not include any explicit flow rules.  Are the example switches expected to direct packets without any explicit flows?

2. I tried to use floodlight controller for all three intermediate switches (SL-AM, NU-IG, Kettering-IG), but FloodLight was complaining about the two IG rack switches.  Have the rack switches been tested with FloodLight?  If so, which version is preferred?

3. I'm now using NOX 0.9 instead, but I'm still not getting pings through..  No flows are created on the SL-AM switch nor the IG switches.  What's the best way to debug why my packets aren't leaving the rack switch?

[Nicholas Bastin]

On Thu, May 22, 2014 at 5:37 PM, Fei Yeh <nufe...@gmail.com> wrote:

1. The example does not include any explicit flow rules.  Are the example switches expected to direct packets without any explicit flows?

No, the example relies on a controller being used.

 

2. I tried to use floodlight controller for all three intermediate switches (SL-AM, NU-IG, Kettering-IG), but FloodLight was complaining about the two IG rack switches.  Have the rack switches been tested with FloodLight?  If so, which version is preferred?

What errors are you getting?

One thing I did notice is that your rspecs for the IG FOAMs are incorrect - they should not include VLAN 1750.  The IG rack switches are vlan-hybrid datapaths, so the dpid "06:d6:6c:3b:e5:68:00:00" at northwestern is already sliced as VLAN 1750.  If you change your rspecs to remove the VLAN match at the IG racks (and delete/recreate your slivers) things will likely work better.

--

Nick

[Fei Yeh]

I removed the VLAN match in the rspec and now it works!

Thank you!