On Mon, Apr 12, 2010 at 9:33 AM, Pasi Kärkkäinen <pasik@xxxxxx> 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.
>
> -- Pasi
 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users