[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] VLAN help


  • To: "Emil Palm" <empa@xxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "James Alspach" <jalspach@xxxxxxxxxxxxx>
  • Date: Thu, 5 Jun 2008 09:24:04 -0700
  • Delivery-date: Thu, 05 Jun 2008 09:24:41 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcjG3q8PR4m+iBKURHKTI+6zCbeWtwARLZBQ
  • Thread-topic: [Xen-users] VLAN help

Emil –

Thank you! This gives me another avenue to explore. 

So what you are saying is that one does not have to explicitly create the new interface on the VLAN by making changes in /etc/sysconfig/network-scripts/ ?  By configuring the vlan in vconfig it builds the new interface automagically?  Will this setup survive a reboot or should I build a script to set this up each time?

In my case I have bonded two NICs (well actually two ports on the same NIC but no need to split hairs) so I would imagine I would replace eth0 in your example with bond0.

The host OS I am using is, I believe, CentOS.  I am using the Xen Enterprise version installed right off of the CD which uses some RedHat derived distro.

 

Thank you for your help

James

 

 

 

James Alspach

Systems Analyst II
Shasta County Office of Education


From: Emil Palm [mailto:empa@xxxxxxxxxx]
Sent: Thursday, June 05, 2008 12:35 AM
To: James Alspach; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] VLAN help

 

Hi!

 

I'v just recently set that kind of eviroment up. What Host OS are you running becouse i wrote 2 diffrent howtos for Red Hat and one for SuSe.

 

But in theory you just have 1 interface for ex: eth0

then you do vconfig add eth0 VLANID

 

when that is done you create a bridge something like this:
brctl addbr brVLANID

brctl addif brVLANID eth0.VLANDID

 

when that is setup you should change "network-script=network-bridge" to "network-script=network-dummy" within your xend-config.sxp so Xend doesnt screw up your real physical interface.

 

When that is done just put: vif=["mac=XX:XX:XX:XX:XX:XX,bridge=brVLANID",] in your domU configuration file.

 

If you want more info just give me a mail and i will help you as the best as i can.

 

Emil Palm

Cardium AB

Sweden
 

-----Original message-----
From: James Alspach <jalspach@xxxxxxxxxxxxx>
Sent: Wed 06/04/08 19:56:40
To: xen-users@xxxxxxxxxxxxxxxxxxx;
Subject: [Xen-users] VLAN help

We are in the process of setting up a few Xensource servers whose initial function will be to run Exchange 2007.  As part of this (and for future VM’s) I need to be able to provide access to various VLANS to the various DOM’s.

In theory this sounds fairly straight forward: DOM0 gets a PIF for each VLAN.  This PIF connects to a VLAN specific bridge and then, for each DOM that needs one, a VIF is created and connected to the bridge.

Does this sound correct?

If so, my question is how to specify the VLAN for a PIF.  I can list it but I am not able to set it since it is read only.

 

How do virtual networks fit into the above and how is a virtual network different from a virtual bridge?

 

Any help or pointers to information are greatly appreciated.

 

Thank you for your help;

James

 

 

 

 

 

 

 

James Alspach
Systems Analyst II

Shasta County Office of Education

1644 Magnolia avenue

Redding, California

96003
jalspach@xxxxxxxxxxxxx
(530) 225-0293

 

IT Hotline: 225-0279

hotline@xxxxxxxxxxxxx

 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.