I have a pool with two xen servers connected to the same switch. At the pool level I have created an external network named VLAN3 with a tag id of 3. I have two Windows XP guest VMs running one on each host. I have attached both VMs to VLAN3 on each server. The problem is that both VMs cannot see each other over this VLAN. If I move both to one host server, then they do see each other. Why can''t the VLAN span across a pool of servers. Do I need some special switch that can handle vlan tagged traffic? I just have an old 10/100 NetGear ProSafe 16 (FS-116) switch. If my switch is capable of tagged traffic will the vlan work across the pool? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, Apr 11, 2010 at 07:37:34PM -0700, Faraz Khan wrote:> I have a pool with two xen servers connected to the same switch. At the > pool level I have created an external network named VLAN3 with a tag id of > 3. I have two Windows XP guest VMs running one on each host. I have > attached both VMs to VLAN3 on each server. The problem is that both VMs > cannot see each other over this VLAN. If I move both to one host server, > then they do see each other. > > > > Why can''t the VLAN span across a pool of servers. Do I need some special > switch that can handle vlan tagged traffic? I just have an old 10/100 > NetGear ProSafe 16 (FS-116) switch. > > > > If my switch is capable of tagged traffic will the vlan work across the > pool?Yeah, you need to have a VLAN capable physical switch, and you need to set up all the VLANS as tagged in the switch. So in this case you need to create a vlan with id 3 in the switch, and configure it as tagged to all the xen-host ports. -- Pasi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Apr 12, 2010 at 9:33 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Sun, Apr 11, 2010 at 07:37:34PM -0700, Faraz Khan wrote: >> I have a pool with two xen servers connected to the same switch. At the >> pool level I have created an external network named VLAN3 with a tag id of >> 3. I have two Windows XP guest VMs running one on each host. I have >> attached both VMs to VLAN3 on each server. The problem is that both VMs >> cannot see each other over this VLAN. If I move both to one host server, >> then they do see each other. >> >> >> >> Why can''t the VLAN span across a pool of servers. Do I need some special >> switch that can handle vlan tagged traffic? I just have an old 10/100 >> NetGear ProSafe 16 (FS-116) switch. >> >> >> >> If my switch is capable of tagged traffic will the vlan work across the >> pool? > > Yeah, you need to have a VLAN capable physical switch, and you need to set up > all the VLANS as tagged in the switch. So in this case you need to create a vlan > with id 3 in the switch, and configure it as tagged to all the xen-host ports. > > -- PasiFrom what I remember I was part of a network constructed only with cheap switches (I''m 100% they were not VLAN aware), and VLAN worked just perfectly without any "hardware" support. (Of course there was no isolation based on VLAN id, which is one of the main features of using VLAN''s). (This was not Xen related.) I would say that the problem is from your Dom0''s... When you put the DomU''s on the same machine do you still use VLAN? Or better said is the WindowsXP aware of the VLAN''s or the VLAN''s are handled by the Dom0? How did you setup the VLAN''s? Ciprian. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I created a Network in XenCenter at the pool level. The type I selected was
"External Network". I gave it a VLAN id of 3. Then I attached this
new network to my guest VMs. Inside the guests I gave each NIC an IP address
such as 10.0.1.x/255.255.0.0. Then from one VM I pinged 10.0.1.x. The ping get
a response only if the two VMs are running on the same Xen Host. If they are
running on separate hosts but in the same pool and physically connected to a
switch then the ping does not get any response.
In a sense Windows XP are aware of the VLAN because I gave them a proper IP
address within the correct range, e.g. 10.0.1.5 and 10.0.1.6 with a subnet mask
of 255.255.0.0. But the real purpose of creating a VLAN is that if a 3rd
Windows XP had an IP of 10.0.1.7 it should not be able to ping to the other two,
because they are in a logically seperated vlan.
-----Original Message-----
From: Ciprian Dorin, Craciun [mailto:ciprian.craciun@gmail.com]
Sent: Sunday, April 11, 2010 11:56 PM
To: Pasi Kärkkäinen
Cc: Faraz Khan; xen-users@lists.xensource.com
Subject: Re: [Xen-users] VLAN in a Pool
On Mon, Apr 12, 2010 at 9:33 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
From what I remember I was part of a network constructed only with
cheap switches (I'm 100% they were not VLAN aware), and VLAN worked
just perfectly without any "hardware" support. (Of course there was no
isolation based on VLAN id, which is one of the main features of using
VLAN's). (This was not Xen related.)
I would say that the problem is from your Dom0's... When you put
the DomU's on the same machine do you still use VLAN? Or better said
is the WindowsXP aware of the VLAN's or the VLAN's are handled by the
Dom0? How did you setup the VLAN's?
Ciprian.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
>> If they are running on separate hosts but in the same pool and physically connected to a switch then the ping does not get any response.Enable IP Forwarding in Dom0 echo 1 > /proc/sys/net/ipv4/ip_forward and in /etc/sysctl.conf you will find a variable net.ipv4.ip_forward=1 enable it or change value to 1. Then in DomU''s make sure the Gateway is your Dom0 i.e. for DomU your Dom0 is behaving like gateway. DNS will be same as the DNS on Dom0.Test if you have bridged network setup. Check in your /etc/xen/xend-config.sxp (network-script ''network-bridge netdev=eth1'') Should point to your default ethernet device and line is to be uncommented. Similary check the entry (vif-script vif-bridge) It should be uncommented. Have you configured IPTABLES or routing. If yes then tell about the configuration a bit here. -- Tapas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2010/4/12 Faraz Khan <Faraz.Khan@asu.edu>:> I created a Network in XenCenter at the pool level. The type I selected was "External Network". I gave it a VLAN id of 3. Then I attached this new network to my guest VMs. Inside the guests I gave each NIC an IP address such as 10.0.1.x/255.255.0.0. Then from one VM I pinged 10.0.1.x. The ping get a response only if the two VMs are running on the same Xen Host. If they are running on separate hosts but in the same pool and physically connected to a switch then the ping does not get any response.Unfortunately I''m unaware of XenCenter. (I use the "raw" Xen, in the sense I configure it by using /etc/xen/xend-config.spx, and other configuration files...) Sorry, Ciprian.> In a sense Windows XP are aware of the VLAN because I gave them a proper IP address within the correct range, e.g. 10.0.1.5 and 10.0.1.6 with a subnet mask of 255.255.0.0. But the real purpose of creating a VLAN is that if a 3rd Windows XP had an IP of 10.0.1.7 it should not be able to ping to the other two, because they are in a logically seperated vlan. > > -----Original Message----- > From: Ciprian Dorin, Craciun [mailto:ciprian.craciun@gmail.com] > Sent: Sunday, April 11, 2010 11:56 PM > To: Pasi Kärkkäinen > Cc: Faraz Khan; xen-users@lists.xensource.com > Subject: Re: [Xen-users] VLAN in a Pool > > On Mon, Apr 12, 2010 at 9:33 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > From what I remember I was part of a network constructed only with > cheap switches (I''m 100% they were not VLAN aware), and VLAN worked > just perfectly without any "hardware" support. (Of course there was no > isolation based on VLAN id, which is one of the main features of using > VLAN''s). (This was not Xen related.) > > I would say that the problem is from your Dom0''s... When you put > the DomU''s on the same machine do you still use VLAN? Or better said > is the WindowsXP aware of the VLAN''s or the VLAN''s are handled by the > Dom0? How did you setup the VLAN''s? > > Ciprian._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users