Hi,
I have tried both "ifconfig of0 10.0.0.5" and "secchan nl:0
tcp:10.0.2.2:975" on vigil2 too, but the behavior is still the same.
I.e., after 45 seconds, the switch tables start to contain active flows
and forward end host traffic, but still with error messages "Could not
connect to controller, failing open".
However, I found out that, on the nox_core side, warning messages "(dhcp
parse) warning DHCP packet data too short to parse header: data len 86"
keep popping up. Was this the reason for such behavior? If so, any
suggestions on how to solve this issue?
(BTW I used the latest NOX version, downloaded the kernel.bin and
openflow_mod.so and secchan from noxrepo.org. I used in-band control,
ran nox_core with the "pyswitch" application. I added the nl:0 dp, and
all eth interfaces to the dp except the one connecting the host, on both
vigil1 and vigil2)
Thanks a million,
-Zheng
Martin Casado wrote:
To support inand control (on vigil2) you probably have to bring up of0
and give it an IP address.
e.g.
ifconfig of0 10.0.0.5
let us know if that doesn't work.
cheers,
.martin
I have tried this:
nox
|
end1 --- vigil1 --- vigil2 --- end2
I ran "secchan nl:0 tcp:10.0.2.2:975" on vigil1, ran "secchan nl:0"
on vigil2. At the beginning neither end1 nor end2 could ping each
other. After 45 seconds, I got the error message on vigil2:
fail_open|WARN|Could not connect to controller for 45 seconds,
failing open. But right from then on, end1 and end2 could ping each
other.
Is this the right behavior? If not, what are the things I have done
wrong?
Thanks again for your help,
-Zheng
Zheng Cai wrote:
Following on this thread, in this 2 switches 2 hosts setup, are
there two separate connections from both vigil1 and vigil2 to the
host machine (by s1_SLIRP and s2_SLIRP)? Also, does this mean that
we need to use secchan to connect to the nox_core on the host
machine, from both vigil1 and vigil2?
Then, what if I only setup one secure channel between vigil1 and the
host nox using secchan? Will vigil1 and vigil2 form a spanning tree,
and vigil1 will forward control messages for vigil2? I am a little
confused here.
Thank you so much,
-Zheng Cai
Keith Amidon wrote:
The number of VMs and their connectivity are specified in the
vms.conf file. As an example, here is a file with four VMs total,
two acting as switches (vigil1 & vigil2) and two acting as regular
machines (end1 and end2), one connected to each switch. To add
more VMs, just add new names to the VMS line. The "SWITCHES"
provide the connectivity for the VMs connected to them using the
*_NETS lines as a regular (non-openflow) switch would.
--- Keith
SWITCHESKeith Amidon <[email protected]>="s1 s2 s3 s4 s5"
s1_SLIRP=yes
s2_SLIRP=yes
VMS="vigil1 vigil2 end1 end2"
end1_NETS="s4"
vigil1_NETS="s1 s3 s4"
end2_NETS="s5"
vigil2_NETS="s2 s3 s5"
On Thu, 2009-04-02 at 06:34 -0400, Surabhi Diwan wrote:
Hi All,
I did the virtual test environment setup using NOX with 1
controller, 1 switch and 2 virtual QEMU machines as suggested in
the wiki.
I want to build upwards from this configuration and have more
nodes and switches under the purview of the NOX controller.
Could you please suggest what would be the best way to emulate
more complicated (close to real life networks) using the NOX
controller.
Thanks a lot!
Regards,
Surabhi
_______________________________________________
nox-dev mailing list
[email protected] <mailto:[email protected]>
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
------------------------------------------------------------------------
_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.orMartin Casado
<[email protected]>g/mailman/listinfo/nox-dev_noxrepo.org
_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
