loaded OVS to nodes-- nodes not pinging

[Sanghamitra De]

Hi,

I installed OVS in one emulab node, got the node image id as per:

https://wiki.emulab.net/wiki/Tutorial#section-24

and after making changes to the NS file got the image of the node (with OVS installed in it) loaded onto every other emulab node that i am using.

after this whenever i'm swapping-in the expt-- it is getting swapped-in successfully BUT...  the nodes fail to ping to each other-- which gets displayed as a routing error.

Why is this happening?? Is this where OVS configuration is required????

Please note that so far the nodes only have OVS installed onto them-- configuration of OVS is not yet done.

Thanks!!!!

[Eric Eide]

Sanghamitra De <sangham...@gmail.com> writes:

> I installed OVS in one emulab node, got the node image id as per:
> https://wiki.emulab.net/wiki/Tutorial#section-24
> and after making changes to the NS file got the image of the node (with OVS
> installed in it) loaded onto every other emulab node that i am using.

Note: You only need to install OVS on nodes that are acting as switches. For
example, in the topology shown below, if only the central node is doing any
switching, then OVS only needs to be installed on the central node:

O
|
O--O--O
|
O

> after this whenever i'm swapping-in the expt-- it is getting swapped-in
> successfully BUT... the nodes fail to ping to each other-- which gets
> displayed as a routing error. Why is this happening?? Is this where OVS
> configuration is required????

To diagnose this problem, you'll need to provide more detail. The more
important detail is the NS file that you are using! Please follow-up and
include the NS file that you are using to set up your experiment.

Best wishes ---

Eric.

--
-------------------------------------------------------------------------------
Eric Eide <ee...@cs.utah.edu> . University of Utah School of Computing
http://www.cs.utah.edu/~eeide/ . +1 (801) 585-5512 voice, +1 (801) 581-5843 FAX

[Sanghamitra De]

OK so I would have OVS installed only in the nodes which will be the switches (those in turn will talk to the other nodes). The other nodes meanwhile will have the usual Ubuntu OS without any OVS installed in them.

I've attached the ns file attached with this post.

Kindly let me know why the nodes dont ping to each other any more. Will configuring the OVS in the switch nodes & uninstalling the OVS from the nodes which will not be working as switches help? The image id used is ovsinstalled for all the nodes (irrespective of whether they'll function as switches or not)

Thank You

Sanghamitra

[Eric Eide]

Sanghamitra De <sangham...@gmail.com> writes:

> I've attached the ns file attached with this post. Kindly let me know why
> the nodes dont ping to each other any more. Will configuring the OVS in the
> switch nodes & uninstalling the OVS from the nodes which will not be working
> as switches help?

I wasn't able to investigate this tonight; sorry. I'll try to look at it
tomorrow. (Maybe somebody else at Utah will beat me to it.)

My guess is that there is something odd about the disk image you have created.
I don't know why merely *installing* OVS would cause the behavior you are
reporting.

[Sanghamitra De]

I'm thinking that as well. Will anyone just run this/load this image "ovsinstalled" in a node and let me know if this image is doing this.

in that case.. i might as well redo the thing ..... build a fresh image.

Thank You!!!

[Eric Eide]

Sanghamitra De <sangham...@gmail.com> writes:

> I installed OVS in one emulab node, got the node image id as per:
>
> https://wiki.emulab.net/wiki/Tutorial#section-24
>
> and after making changes to the NS file got the image of the node (with OVS
> installed in it) loaded onto every other emulab node that i am using.
>
> after this whenever i'm swapping-in the expt-- it is getting swapped-in
> successfully BUT... the nodes fail to ping to each other-- which gets
> displayed as a routing error. Why is this happening?? Is this where OVS
> configuration is required????

I don't have access to your disk image, so I simply tried to replicate your
result. I couldn't replicate the behavior that you are seeing, which leads me
to believe that you did something odd when you created your disk image.

I made my own disk image with OVS installed by loading a Utah Emulab node with
UBUNTU14-64-STD and running the commands at the bottom of this message. Then I
used the Emulab web interface to create a new disk image from the node that I
had configured.

Then I created a new, multi-node experiment, with my new disk image loaded on
all of the nodes. I tried a basic ping-connectivity test, and it ran fine.

So, my advice is to try making a new image with OVS installed. Try using the
commands below to install OVS. Note that they *only* install OVS on the node,
which is all that you want/need. The commands below do not start OVS running,
nor do they further configure OVS.

Good luck, and best wishes ---

Eric.

-----
## Eric's little script to install OVS on UBUNTU14-64-STD.

## Create a local work directory.
sudo mkdir /work
sudo chown `whoami` /work
cd /work

## Download, configure, compile, and install Open vSwitch.
wget http://openvswitch.org/releases/openvswitch-2.3.0.tar.gz
tar zxf openvswitch-2.3.0.tar.gz
cd openvswitch-2.3.0
./configure
make
sudo make install

## Clean up.
cd /
sudo rm -rf /work

## Logout, use Emulab web interface to make a disk image.

[Sanghamitra De]

Thank You. I will re-install and use the script You've send. Thank You once again.

Regards & Best Wishes

Sanghamitra

--
You received this message because you are subscribed to a topic in the Google Groups "emulab-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/emulab-users/p8SmaVx6pmQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to emulab-users...@googlegroups.com.
To post to this group, send email to emulab...@googlegroups.com.
Visit this group at http://groups.google.com/group/emulab-users.
For more options, visit https://groups.google.com/d/optout.

[Sanghamitra De]

Hi,

I tried to reinstall OVs 2.3.0 onto node with Ubuntu image (UBUNTU14-64-STD)

./configure on executing ends with something like:

config.status: executing utilities/bugtool/dummy commands

It stays like that forever without returning to #prompt. One has to forcibly press an enter to return to the # prompt. Why is that so?

Also doesn’t Ubuntu allow scrolling when the command has executed so that I can see what happened. All I can see is the last line.!!!!

Thanks

Sanghamitra

[Eric Eide]

Sanghamitra De <sangham...@gmail.com> writes:

> I tried to reinstall OVs 2.3.0 onto node with Ubuntu image (UBUNTU14-64-STD)
>
> ./configure on executing ends with something like:
>
> config.status: executing utilities/bugtool/dummy commands
>
> It stays like that forever without returning to #prompt. One has to forcibly
> press an enter to return to the # prompt. Why is that so?

My guess is that you have a program in your path that is interfering with some
program that the configure script wants to run. A common problem is having a
program named "test" in some non-system directory in your path.

The file "config.log" should give you some hints about what the configure
script is trying to do. Look at the end of the log to investiagte why the
script might be getting stuck.

If looking at the "config.log" file does help you to debug the problem, try:

+ removing all of the non-sytem directories from your shell's command search
path

+ looking through the "configure" script to figure what what the script is
trying to do, and why that thing might not be working

Good luck! ---

Eric.

[Sanghamitra De]

I would be trying this soon. Failed to do so-- for the past few days. Thank You.

Regards & Best Wishes

Sanghamitra