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@shastacoe.org <mailto:jalspach@shastacoe.org> (530) 225-0293 IT Hotline: 225-0279 hotline@shastacoe.org <mailto:hotline@shastacoe.org> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Here's what I do: 1) Set up tagged VLAN interface and bring all VLANs in on single interface or on trunk (bond0). 2) Set up VLAN interfaces in dom0. In RH-type distributions this will be something like eth0.1, eth0.2, etc., or bond0.1, bond0.2, etc. In SuSE-type distros, they are vlan1, vlan2, etc. 3) Set up bridges for each of the VLANs. So, if I have vlan1 and vlan2, I set up xenbr1 and xenbr2 as bridges where xenbr1 has vlan1 as a bridge member and xenbr2 has vlan2 as a bridge member. Also, if you want dom0 to have an IP address assigned on any of the VLANs, assign it on the bridge for the VLAN and not the VLAN interface itself. 4) Configure my domUs with bridge=xenbr1 for VLAN1, bridge=xenbr2 for VLAN2, etc. I've pretty well settled on this as a standard and it works fairly well - it provides a consistent setup on all of my XEN servers so that moving domUs between them works w/o having to reconfigure. -Nick>>> On Wed, Jun 4, 2008 at 12:55 PM, "James Alspach"<jalspach@shastacoe.org> wrote: 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@shastacoe.org (530) 225-0293 IT Hotline: 225-0279 hotline@shastacoe.org This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Great! That sounds like what I was thinking. I have bond0 setup on the physical NIC which is connected to the trunked switch interface. So to set up the interfaces in dom0 I just need to create them using iface.vlan? Is this configured using a Xensource tool or by directly editing the /etc/sysconfig/network-scripts/? Thanks; James PS Thank you for such a fast reply! James Alspach Systems Analyst II Shasta County Office of Education ________________________________ From: Nick Couchman [mailto:Nick.Couchman@seakr.com] Sent: Wednesday, June 04, 2008 12:14 PM To: xen-users@lists.xensource.com; James Alspach Subject: Re: [Xen-users] VLAN help Here''s what I do: 1) Set up tagged VLAN interface and bring all VLANs in on single interface or on trunk (bond0). 2) Set up VLAN interfaces in dom0. In RH-type distributions this will be something like eth0.1, eth0.2, etc., or bond0.1, bond0.2, etc. In SuSE-type distros, they are vlan1, vlan2, etc. 3) Set up bridges for each of the VLANs. So, if I have vlan1 and vlan2, I set up xenbr1 and xenbr2 as bridges where xenbr1 has vlan1 as a bridge member and xenbr2 has vlan2 as a bridge member. Also, if you want dom0 to have an IP address assigned on any of the VLANs, assign it on the bridge for the VLAN and not the VLAN interface itself. 4) Configure my domUs with bridge=xenbr1 for VLAN1, bridge=xenbr2 for VLAN2, etc. I''ve pretty well settled on this as a standard and it works fairly well - it provides a consistent setup on all of my XEN servers so that moving domUs between them works w/o having to reconfigure. -Nick>>> On Wed, Jun 4, 2008 at 12:55 PM, "James Alspach"<jalspach@shastacoe.org> wrote: 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@shastacoe.org (530) 225-0293 IT Hotline: 225-0279 hotline@shastacoe.org ________________________________ This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James, I do the setup using the dom0's vlan tools, so in SuSE (which is what I use most of the time), I have /etc/sysconfig/network/ifcfg-vlan1 and /etc/sysconfig/network/ifcfg-xenbr1 to set up the vlan and bridge, respectively. In RH-style, it would be something like /etc/sysconfig/network-scripts/ifcfg-bond0.1 and I can't remember what the bridge stuff is like in the RH-style ones. -Nick>>> On Wed, Jun 4, 2008 at 1:21 PM, "James Alspach"<jalspach@shastacoe.org> wrote: Great! That sounds like what I was thinking. I have bond0 setup on the physical NIC which is connected to the trunked switch interface. So to set up the interfaces in dom0 I just need to create them using iface.vlan? Is this configured using a Xensource tool or by directly editing the /etc/sysconfig/network-scripts/? Thanks; James PS Thank you for such a fast reply! James Alspach Systems Analyst II Shasta County Office of Education From: Nick Couchman [mailto:Nick.Couchman@seakr.com] Sent: Wednesday, June 04, 2008 12:14 PM To: xen-users@lists.xensource.com; James Alspach Subject: Re: [Xen-users] VLAN help Here's what I do: 1) Set up tagged VLAN interface and bring all VLANs in on single interface or on trunk (bond0). 2) Set up VLAN interfaces in dom0. In RH-type distributions this will be something like eth0.1, eth0.2, etc., or bond0.1, bond0.2, etc. In SuSE-type distros, they are vlan1, vlan2, etc. 3) Set up bridges for each of the VLANs. So, if I have vlan1 and vlan2, I set up xenbr1 and xenbr2 as bridges where xenbr1 has vlan1 as a bridge member and xenbr2 has vlan2 as a bridge member. Also, if you want dom0 to have an IP address assigned on any of the VLANs, assign it on the bridge for the VLAN and not the VLAN interface itself. 4) Configure my domUs with bridge=xenbr1 for VLAN1, bridge=xenbr2 for VLAN2, etc. I've pretty well settled on this as a standard and it works fairly well - it provides a consistent setup on all of my XEN servers so that moving domUs between them works w/o having to reconfigure. -Nick>>> On Wed, Jun 4, 2008 at 12:55 PM, "James Alspach"<jalspach@shastacoe.org> wrote: 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@shastacoe.org (530) 225-0293 IT Hotline: 225-0279 hotline@shastacoe.org This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello! Debian stile would be: in /etc/network/interfaces ===================auto bond0 iface bond0 inet static auto vlan1 iface vlan1 inet manual vlan-raw-device bond0 auto vlan2 iface vlan2 inet manual vlan-raw-device bond0 auto xenbr0 iface xenbr0 inet static address 192.168.0.13 netmask 255.255.255.0 gateway 192.168.0.1 bridge-ports vlan1 auto xenbr1 iface xenbr1 inet static bridge-ports vlan2 ==================== and setting in /etc/xen/xend-config.sxp (network-script network-dummy) Andrej On 4.6.2008, at 21:25, Nick Couchman wrote:> James, > I do the setup using the dom0''s vlan tools, so in SuSE (which is > what I use most of the time), I have /etc/sysconfig/network/ifcfg- > vlan1 and /etc/sysconfig/network/ifcfg-xenbr1 to set up the vlan and > bridge, respectively. In RH-style, it would be something like /etc/ > sysconfig/network-scripts/ifcfg-bond0.1 and I can''t remember what > the bridge stuff is like in the RH-style ones. > > -Nick > > >>> On Wed, Jun 4, 2008 at 1:21 PM, "James Alspach" <jalspach@shastacoe.org > > wrote: > > Great! That sounds like what I was thinking. > > I have bond0 setup on the physical NIC which is connected to the > trunked switch interface. > > So to set up the interfaces in dom0 I just need to create them using > iface.vlan? Is this configured using a Xensource tool or by > directly editing the /etc/sysconfig/network-scripts/? > > > > Thanks; > > James > > > > PS > Thank you for such a fast reply! > > > > > > > > James Alspach > > Systems Analyst II > > Shasta > County > Office of Education > > From: > Nick Couchman [mailto:Nick.Couchman@seakr.com] > Sent: > Wednesday, June 04, 2008 12:14 PM > To: > xen-users@lists.xensource.com; James Alspach > Subject: > Re: [Xen-users] VLAN help > > > > Here''s what I do: > > 1) Set up tagged VLAN interface and bring all VLANs in on single > interface or on trunk (bond0). > > 2) Set up VLAN interfaces in dom0. In RH-type distributions this > will be something like eth0.1, eth0.2, etc., or bond0.1, bond0.2, > etc. In SuSE-type distros, they are vlan1, vlan2, etc. > > 3) Set up bridges for each of the VLANs. So, if I have vlan1 and > vlan2, I set up xenbr1 and xenbr2 as bridges where xenbr1 has vlan1 > as a bridge member and xenbr2 has vlan2 as a bridge member. Also, > if you want dom0 to have an IP address assigned on any of the VLANs, > assign it on the bridge for the VLAN and not the VLAN interface > itself. > > 4) Configure my domUs with bridge=xenbr1 for VLAN1, bridge=xenbr2 > for VLAN2, etc. > > > > I''ve pretty well settled on this as a standard and it works fairly > well - it provides a consistent setup on all of my XEN servers so > that moving domUs between them works w/o having to reconfigure. > > > > -Nick > > > >>> On Wed, Jun 4, 2008 at 12:55 PM, "James Alspach" <jalspach@shastacoe.org > > wrote: > > > > 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@shastacoe.org > > > > (530) 225-0293 > > > > > > > IT Hotline: 225-0279 > > > > > hotline@shastacoe.org > > > > This e-mail may contain confidential and privileged material for the > sole use of the intended recipient. If this email is not intended > for you, or you are not responsible for the delivery of this message > to the intended recipient, please note that this message may contain > SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In > such a case, you are strictly prohibited from downloading, > photocopying, distributing or otherwise using this message, its > contents or attachments in any way. If you have received this > message in error, please notify us immediately by replying to this e- > mail and delete the message from your mailbox. Information contained > in this message that does not relate to the business of SEAKR is > neither endorsed by nor attributable to SEAKR. > This e-mail may contain confidential and privileged material for the > sole use of the intended recipient. If this email is not intended > for you, or you are not responsible for the delivery of this message > to the intended recipient, please note that this message may contain > SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In > such a case, you are strictly prohibited from downloading, > photocopying, distributing or otherwise using this message, its > contents or attachments in any way. If you have received this > message in error, please notify us immediately by replying to this e- > mail and delete the message from your mailbox. Information contained > in this message that does not relate to the business of SEAKR is > neither endorsed by nor attributable to SEAKR. > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thank you so much for your help. I was able to get the link up and working (I can ping the router on the network from DOM0) but after 30 seconds or so, it goes away. Even during a continuous ping the network will eventually just disappear. If I ifup the bridge and the bond, it is great again for a short while before it goes away. This has me stumped. However, between what you told me and the Networking part of the Wiki (http://wiki.xensource.com/xenwiki/XenNetworking) I feel confident that there is an answer to this. My other concern now is how this will all play in a resource pool? Will it be automatically propagated as I add machines to the pool or will I have to reconfigure for each machine? It is not too bad if I have to do it on each machine; I only have a small handful of VLANS I need access to. I just need to make sure that I do them all the same so that Xenmotion will still work. James James Alspach Systems Analyst II Shasta County Office of Education ________________________________ From: Nick Couchman [mailto:Nick.Couchman@seakr.com] Sent: Wednesday, June 04, 2008 12:26 PM To: xen-users@lists.xensource.com; James Alspach Subject: RE: [Xen-users] VLAN help James, I do the setup using the dom0''s vlan tools, so in SuSE (which is what I use most of the time), I have /etc/sysconfig/network/ifcfg-vlan1 and /etc/sysconfig/network/ifcfg-xenbr1 to set up the vlan and bridge, respectively. In RH-style, it would be something like /etc/sysconfig/network-scripts/ifcfg-bond0.1 and I can''t remember what the bridge stuff is like in the RH-style ones. -Nick>>> On Wed, Jun 4, 2008 at 1:21 PM, "James Alspach"<jalspach@shastacoe.org> wrote: Great! That sounds like what I was thinking. I have bond0 setup on the physical NIC which is connected to the trunked switch interface. So to set up the interfaces in dom0 I just need to create them using iface.vlan? Is this configured using a Xensource tool or by directly editing the /etc/sysconfig/network-scripts/? Thanks; James PS Thank you for such a fast reply! James Alspach Systems Analyst II Shasta County Office of Education ________________________________ size=2 width="100%" align=center tabindex=-1> From: Nick Couchman [mailto:Nick.Couchman@seakr.com] Sent: Wednesday, June 04, 2008 12:14 PM To: xen-users@lists.xensource.com; James Alspach Subject: Re: [Xen-users] VLAN help Here''s what I do: 1) Set up tagged VLAN interface and bring all VLANs in on single interface or on trunk (bond0). 2) Set up VLAN interfaces in dom0. In RH-type distributions this will be something like eth0.1, eth0.2, etc., or bond0.1, bond0.2, etc. In SuSE-type distros, they are vlan1, vlan2, etc. 3) Set up bridges for each of the VLANs. So, if I have vlan1 and vlan2, I set up xenbr1 and xenbr2 as bridges where xenbr1 has vlan1 as a bridge member and xenbr2 has vlan2 as a bridge member. Also, if you want dom0 to have an IP address assigned on any of the VLANs, assign it on the bridge for the VLAN and not the VLAN interface itself. 4) Configure my domUs with bridge=xenbr1 for VLAN1, bridge=xenbr2 for VLAN2, etc. I''ve pretty well settled on this as a standard and it works fairly well - it provides a consistent setup on all of my XEN servers so that moving domUs between them works w/o having to reconfigure. -Nick>>> On Wed, Jun 4, 2008 at 12:55 PM, "James Alspach"<jalspach@shastacoe.org> wrote: 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@shastacoe.org (530) 225-0293 IT Hotline: 225-0279 hotline@shastacoe.org ________________________________ This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. ________________________________ This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wednesday June 04 2008 08:33:22 pm James Alspach wrote:> I was able to get the link up and working (I can ping the router on the > network from DOM0) but after 30 seconds or so, it goes away. Even during a > continuous ping the network will eventually just disappear. If I ifup the > bridge and the bond, it is great again for a short while before it goes > away. This has me stumped. However, between what you told me and the > Networking part of the Wiki > (http://wiki.xensource.com/xenwiki/XenNetworking) I feel confident that > there is an answer to this.This sounds like a symptom of two nodes having the same MAC address. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@cardium.se] Sent: Thursday, June 05, 2008 12:35 AM To: James Alspach; xen-users@lists.xensource.com 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@shastacoe.org> Sent: Wed 06/04/08 19:56:40 To: xen-users@lists.xensource.com; 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@shastacoe.org <mailto:jalspach@shastacoe.org> (530) 225-0293 IT Hotline: 225-0279 hotline@shastacoe.org <mailto:hotline@shastacoe.org> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thank you. I will look into this as a possible issue. I did not configure the MAC address so that could very well be the issue. Thanks again; James James Alspach Systems Analyst II Shasta County Office of Education> -----Original Message----- > From: xen-users-bounces@lists.xensource.com [mailto:xen-users- > bounces@lists.xensource.com] On Behalf Of jim burns > Sent: Wednesday, June 04, 2008 6:18 PM > To: xen-users@lists.xensource.com > Subject: Re: [Xen-users] VLAN help > > On Wednesday June 04 2008 08:33:22 pm James Alspach wrote: > > I was able to get the link up and working (I can ping the router on the > > network from DOM0) but after 30 seconds or so, it goes away. Even > during a > > continuous ping the network will eventually just disappear. If I ifup > the > > bridge and the bond, it is great again for a short while before it goes > > away. This has me stumped. However, between what you told me and the > > Networking part of the Wiki > > (http://wiki.xensource.com/xenwiki/XenNetworking) I feel confident that > > there is an answer to this. > > This sounds like a symptom of two nodes having the same MAC address. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users