Re: [portal-help] Two Virtual Connections

5 views
Skip to first unread message

Sarah Edwards

unread,
Apr 14, 2014, 10:24:17 AM4/14/14
to geni-...@googlegroups.com, Sarah Edwards, Allan Overstreet
[Adding geni-...@googlegroups.com back to the thread so the answer will get captured or posterity.]

Hi Allan,

This is a good question.  There is a subtle issue that if you use xen VMs (instead of OpenVZ) you need to use "egre-tunnel" for the link_type instead of "gre-tunnel". [1]

Let me know if that doesn't work for you,
Sarah


On Apr 11, 2014, at 5:20 PM, Allan Overstreet <allanov...@mail.overnetwork.org> wrote:

Ms. Edwards,

Thank you for your help. I was able to create the network in the Flack by editing the RSpec file, and have attached this file to this email. I am having another issue with the two VMs that are acting as the gateways in this network. When I ssh into VM-0 and VM-1 and run the ifconfig command on both machines I can't see the interfaces that are supposed to be connected to gre-tunnel0 and gre-tunnel1. Do you know what would be causing this to happen? Again thank you very much for your help.

The results from the ifconfig command for VM-0 are shown below,

eth0      Link encap:Ethernet  HWaddr 02:eb:b0:a2:9c:81  
          inet addr:172.17.3.30  Bcast:172.31.255.255  Mask:255.240.0.0
          inet6 addr: fe80::eb:b0ff:fea2:9c81/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:298 errors:0 dropped:0 overruns:0 frame:0
          TX packets:334 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:40864 (40.8 KB)  TX bytes:35098 (35.0 KB)
          Interrupt:25

eth1      Link encap:Ethernet  HWaddr 02:dd:d3:41:ae:1e  
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::dd:d3ff:fe41:ae1e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:592 (592.0 B)  TX bytes:888 (888.0 B)
          Interrupt:26

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:260 (260.0 B)  TX bytes:260 (260.0 B)

The ifconfig command results for VM-1 are listed below,

eth0      Link encap:Ethernet  HWaddr 02:8a:10:23:64:bc  
          inet addr:172.17.5.35  Bcast:172.31.255.255  Mask:255.240.0.0
          inet6 addr: fe80::8a:10ff:fe23:64bc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:849 errors:0 dropped:0 overruns:0 frame:0
          TX packets:826 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:85521 (85.5 KB)  TX bytes:90575 (90.5 KB)
          Interrupt:25

eth1      Link encap:Ethernet  HWaddr 02:59:f6:8b:6e:cf  
          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::59:f6ff:fe8b:6ecf/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:134 errors:0 dropped:0 overruns:0 frame:0
          TX packets:68 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7152 (7.1 KB)  TX bytes:6052 (6.0 KB)
          Interrupt:26

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:932 (932.0 B)  TX bytes:932 (932.0 B)

Sincerely,

Allan Overstreet

From: "Sarah Edwards" <sedw...@bbn.com>
To: "Allan Overstreet" <allanov...@mail.overnetwork.org>
Cc: "Sarah Edwards" <sedw...@bbn.com>, geni-...@googlegroups.com
Sent: Thursday, April 3, 2014 3:14:18 PM
Subject: Re: [portal-help] Two Virtual Connections

[Forwarding to geni-...@googlegroups.com. You can sign up to get replies from: https://groups.google.com/forum/#!forum/geni-users]

Hi Allan,

It turns out this works, but the answer is slightly tricky.

The issue is that Flack doesn't currently let you draw the topology but the individual aggregates support making the reservation.

This question has been answered before [1] but there is a lot of debugging in that thread which obscures the answer.  Below is a summary of what you need to do.

 (1) Draw the topology you want in Flack but with the second path between VM and VM-1 missing.
 (2) Save the RSpec in a text file (View -> Preview Request Documents -> Save to File)
 (3) In a text editor, edit the RSpec by adding a second link between the two VMs being sure to modify the IP addresses and names of the interfaces appropriately.  (I've attached an example I did.  I made each link have it's own subnet and each interface has a unique name.)
 (4) Use omni [2] (or I think you can do the same with the Portal) to make separate reservations at each of the two aggregates specified (but using the same RSpec both times).  See [3] for more info on specifying the aggregate.
For example, with the attached RSpec I made the following calls [3]:
omni.py createsliver test2 gretunnel_fulltopo.xml -a clemson-ig
omni.py createsliver test2 gretunnel_fulltopo.xml -a illinois-ig

Note that if you import the attached RSpec into Flack, you seem to be able to make some edits and save it again for use with omni (without losing the second GRE tunnel).  For the non-GRE links, you will want to specify the IP subnets used on all of the links so that you don't accidentally get the same autoassigned subnet at each AM.

Let us know if you need more help,
Sarah Edwards, GPO





On Apr 3, 2014, at 1:44 PM, Allan Overstreet <allanov...@mail.overnetwork.org> wrote:

I am trying to create a network configuration that would have two connections from the virtual machine VM and the virtual machine VM-1 similar to the figure below. Although the flack will not allow a second tunnel between VM and VM-1, is there another way to do this?
<febeehhj.png>

Thanks for your help.

Sincerely,

Allan Overstreet

*******************************************************************************
Sarah Edwards
GENI Project Office

BBN Technologies
Cambridge, MA
phone:    (617) 873-2329
email:    sedw...@bbn.com






<18.png><Working.xml>

*******************************************************************************
Sarah Edwards
GENI Project Office

BBN Technologies
Cambridge, MA
phone:    (617) 873-2329
email:    sedw...@bbn.com





Reply all
Reply to author
Forward
0 new messages