Re: [CentOS] eth0 killed when adding virtual interface and multiple NICs are present

2009-05-01 Thread JohnS

On Thu, 2009-04-30 at 13:31 +0200, Kai Schaetzl wrote:
 JohnS wrote on Thu, 30 Apr 2009 02:17:13 -0400:
 
  Kai, I read the Xen list and the way your doing it (the last option)
  looks like something I may try for testing in VMs.
 
 It works fine, I'm converting all my setups to that now.
 
  Indeed also I when I installed Xen I had to manually take out peth0 when
  I uninstalled it.
 
 How did you manually take it down? The problem seems to be that peth0 is 
 the physical interface now. But I'm not able to take it down as a bridge 
 nor as a physical interface. And not without breaking the network 
 connection, anyway.
 
 Kai

Correction, the install above should be uninstalled. Typo error sorry.
But that is right peth0 becomes the interface.

JohnStanley

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] eth0 killed when adding virtual interface and multiple NICs are present

2009-04-30 Thread JohnS

On Tue, 2009-04-28 at 23:31 +0200, Kai Schaetzl wrote:
 JohnS wrote on Mon, 27 Apr 2009 11:09:56 -0400:
 
  If you don't mind when you come to an answer would you please let me
  know. I am interested to know.
 
 I could not find a real solution. I had to go to another way of creating 
 the network setup for this machine (and maybe others, I will see) and 
 disable the network-bridge script from xen. That new solution is 
 documented on the xen-users mailing-list.
 
 Kai
---
Kai, I read the Xen list and the way your doing it (the last option)
looks like something I may try for testing in VMs. Although I do want to
say Virtual Box does that very same behavior that you first described in
your post.
When you start up Virtual Box it takes out my eth1 and I am left with
eth0. Makes eth1 Brigded if that makes sense to you like Xen was doing.
I have to say it really seems like a better solution the way your doing
it now. In fact I am going to give it a try also. It may be a little
more effort into doing it but the approach is much better.

Indeed also I when I installed Xen I had to manually take out peth0 when
I uninstalled it.

JohnStanley

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] eth0 killed when adding virtual interface and multiple NICs are present

2009-04-30 Thread Kai Schaetzl
JohnS wrote on Thu, 30 Apr 2009 02:17:13 -0400:

 Kai, I read the Xen list and the way your doing it (the last option)
 looks like something I may try for testing in VMs.

It works fine, I'm converting all my setups to that now.

 Indeed also I when I installed Xen I had to manually take out peth0 when
 I uninstalled it.

How did you manually take it down? The problem seems to be that peth0 is 
the physical interface now. But I'm not able to take it down as a bridge 
nor as a physical interface. And not without breaking the network 
connection, anyway.

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] eth0 killed when adding virtual interface and multiple NICs are present

2009-04-30 Thread Ross Walker

On Apr 30, 2009, at 7:31 AM, Kai Schaetzl mailli...@conactive.com  
wrote:

 JohnS wrote on Thu, 30 Apr 2009 02:17:13 -0400:

 Kai, I read the Xen list and the way your doing it (the last option)
 looks like something I may try for testing in VMs.

 It works fine, I'm converting all my setups to that now.

 Indeed also I when I installed Xen I had to manually take out peth0  
 when
 I uninstalled it.

 How did you manually take it down? The problem seems to be that  
 peth0 is
 the physical interface now. But I'm not able to take it down as a  
 bridge
 nor as a physical interface. And not without breaking the network
 connection, anyway.

The problem with Xen's network scripts are they assume a bare bones  
default network setup. If you have anything more then that then I  
recommend disabling the automated network setup in xend.sxp and  
manually setting up your bridges which sounds like the conclusion you  
came to after much discussion.

-Ross

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] eth0 killed when adding virtual interface and multiple NICs are present

2009-04-25 Thread JohnS

On Sat, 2009-04-25 at 20:33 +0200, Kai Schaetzl wrote:
 I have a strange problem on one machine where eth0 gets killed when I add 
 a virtual interface. It's got something to do with the NIC ordering or 
 with the xen network script having a problem with multiple NICs and 
 virtual interfaces. I could need some help/comments on this.
 
 Some history:
 I added a NIC (chip identifies as Realtek Semiconductor Co., Ltd. 
 RTL8111/8168B PCI Express Gigabit Ethernet) to a Dell R200 server.
 CentOS 5.3 with Xen 3.3.1 (gitco repo). 

see this:
http://linux.dell.com/files/whitepapers/nic-enum-whitepaper-v3.pdf

This is a known issue with all Poweredge Servers. It will give you an
explanation and workaround for it.

JohnStanley

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] eth0 killed when adding virtual interface and multiple NICs are present

2009-04-25 Thread Les Mikesell
JohnS wrote:
 On Sat, 2009-04-25 at 20:33 +0200, Kai Schaetzl wrote:
 I have a strange problem on one machine where eth0 gets killed when I add 
 a virtual interface. It's got something to do with the NIC ordering or 
 with the xen network script having a problem with multiple NICs and 
 virtual interfaces. I could need some help/comments on this.

 Some history:
 I added a NIC (chip identifies as Realtek Semiconductor Co., Ltd. 
 RTL8111/8168B PCI Express Gigabit Ethernet) to a Dell R200 server.
 CentOS 5.3 with Xen 3.3.1 (gitco repo). 
 
 see this:
 http://linux.dell.com/files/whitepapers/nic-enum-whitepaper-v3.pdf
 
 This is a known issue with all Poweredge Servers. It will give you an
 explanation and workaround for it.

I don't think there is anything unique to Dells about this.  The kernel 
essentially randomizes device naming on everything.  Dell just took the 
trouble to document it.

-- 
   Les Mikesell
lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] eth0 killed when adding virtual interface and multiple NICs are present

2009-04-25 Thread JohnS

On Sat, 2009-04-25 at 14:52 -0500, Les Mikesell wrote:
 JohnS wrote:
  On Sat, 2009-04-25 at 20:33 +0200, Kai Schaetzl wrote:
  I have a strange problem on one machine where eth0 gets killed when I add 
  a virtual interface. It's got something to do with the NIC ordering or 
  with the xen network script having a problem with multiple NICs and 
  virtual interfaces. I could need some help/comments on this.
 
  Some history:
  I added a NIC (chip identifies as Realtek Semiconductor Co., Ltd. 
  RTL8111/8168B PCI Express Gigabit Ethernet) to a Dell R200 server.
  CentOS 5.3 with Xen 3.3.1 (gitco repo). 
  
  see this:
  http://linux.dell.com/files/whitepapers/nic-enum-whitepaper-v3.pdf
  
  This is a known issue with all Poweredge Servers. It will give you an
  explanation and workaround for it.
 
 I don't think there is anything unique to Dells about this.  The kernel 
 essentially randomizes device naming on everything.  Dell just took the 
 trouble to document it.

From what I understand this was only with dell hardware that this was
happening and they submitted a patch to red hat. Also it is the only
hardware I have encountered with the problem also. There could be
others.

What's more is Kai says he's running 5.3 but the fix should be in that
kernel. What I do wonder is if when the centos kernel was built, was it
included? Maybe the CentOS Kernel builder could let us know? 

2.6.19-rc3 and higher are supposed to have the fix?

It is however a strange thing when you encounter it. I pulled my hair
for a long time.

Last thing is he has this problem on a R200 and from memory those were
not a problem. Could be this is something new? He could check for a BIOS
Revision if there is one.

JohnStanley

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] eth0 killed when adding virtual interface and multiple NICs are present

2009-04-25 Thread JohnS

On Sat, 2009-04-25 at 14:52 -0500, Les Mikesell wrote:
 JohnS wrote:
  On Sat, 2009-04-25 at 20:33 +0200, Kai Schaetzl wrote:
  I have a strange problem on one machine where eth0 gets killed when I add 
  a virtual interface. It's got something to do with the NIC ordering or 
  with the xen network script having a problem with multiple NICs and 
  virtual interfaces. I could need some help/comments on this.
 
  Some history:
  I added a NIC (chip identifies as Realtek Semiconductor Co., Ltd. 
  RTL8111/8168B PCI Express Gigabit Ethernet) to a Dell R200 server.
  CentOS 5.3 with Xen 3.3.1 (gitco repo). 
  
  see this:
  http://linux.dell.com/files/whitepapers/nic-enum-whitepaper-v3.pdf
  
  This is a known issue with all Poweredge Servers. It will give you an
  explanation and workaround for it.
 
 I don't think there is anything unique to Dells about this.  The kernel 
 essentially randomizes device naming on everything.  Dell just took the 
 trouble to document it.
---

Also: https://bugzilla.redhat.com/show_bug.cgi?id=491432
Seems to apply to Kais case.

You *must* specify the HWADDR field in the ifcfg-* files in order to
have persistent ethernet naming. Was the way I done it on dell hardware
and it states that on the Bug Report.

JohnStanley


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] eth0 killed when adding virtual interface and multiple NICs are present

2009-04-25 Thread Les Mikesell
JohnS wrote:
 On Sat, 2009-04-25 at 14:52 -0500, Les Mikesell wrote:
 JohnS wrote:
 On Sat, 2009-04-25 at 20:33 +0200, Kai Schaetzl wrote:
 I have a strange problem on one machine where eth0 gets killed when I add 
 a virtual interface. It's got something to do with the NIC ordering or 
 with the xen network script having a problem with multiple NICs and 
 virtual interfaces. I could need some help/comments on this.

 Some history:
 I added a NIC (chip identifies as Realtek Semiconductor Co., Ltd. 
 RTL8111/8168B PCI Express Gigabit Ethernet) to a Dell R200 server.
 CentOS 5.3 with Xen 3.3.1 (gitco repo). 
 
 see this:
 http://linux.dell.com/files/whitepapers/nic-enum-whitepaper-v3.pdf

 This is a known issue with all Poweredge Servers. It will give you an
 explanation and workaround for it.
 I don't think there is anything unique to Dells about this.  The kernel 
 essentially randomizes device naming on everything.  Dell just took the 
 trouble to document it.
 ---
 
 Also: https://bugzilla.redhat.com/show_bug.cgi?id=491432
 Seems to apply to Kais case.
 
 You *must* specify the HWADDR field in the ifcfg-* files in order to
 have persistent ethernet naming. Was the way I done it on dell hardware
 and it states that on the Bug Report.

I've had my ifcfg-* files renamed to ifcfg-*.bak files and ignored 
completely when moving drives, even among identical hardware.  It's no 
fun when shipping to remote locations where the on-site people don't 
know much about linux.

-- 
   Les Mikesell
lesmikes...@gmail.com




___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] eth0 killed when adding virtual interface and multiple NICs are present

2009-04-25 Thread Robert Heller
At Sat, 25 Apr 2009 16:32:06 -0400 CentOS mailing list centos@centos.org 
wrote:

 
 
 On Sat, 2009-04-25 at 14:52 -0500, Les Mikesell wrote:
  JohnS wrote:
   On Sat, 2009-04-25 at 20:33 +0200, Kai Schaetzl wrote:
   I have a strange problem on one machine where eth0 gets killed when I 
   add 
   a virtual interface. It's got something to do with the NIC ordering or 
   with the xen network script having a problem with multiple NICs and 
   virtual interfaces. I could need some help/comments on this.
  
   Some history:
   I added a NIC (chip identifies as Realtek Semiconductor Co., Ltd. 
   RTL8111/8168B PCI Express Gigabit Ethernet) to a Dell R200 server.
   CentOS 5.3 with Xen 3.3.1 (gitco repo). 
   
   see this:
   http://linux.dell.com/files/whitepapers/nic-enum-whitepaper-v3.pdf
   
   This is a known issue with all Poweredge Servers. It will give you an
   explanation and workaround for it.
  
  I don't think there is anything unique to Dells about this.  The kernel 
  essentially randomizes device naming on everything.  Dell just took the 
  trouble to document it.
 ---
 
 Also: https://bugzilla.redhat.com/show_bug.cgi?id=491432
 Seems to apply to Kais case.
 
 You *must* specify the HWADDR field in the ifcfg-* files in order to
 have persistent ethernet naming. Was the way I done it on dell hardware
 and it states that on the Bug Report.

On ALL RedHat flavored distros (even eith 2.4 kernels), I *always*
specificed the HWADDR field in the ifcfg-* files.  I *think* the RedHat
installers generally always set this field during installation as well.
At least as early as RH 7.mumble or RH 9, which would be when I first
was dealing with machines with more than one NIC.

 
 JohnStanley
 
 
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos
 
   

-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Download the Model Railroad System
http://www.deepsoft.com/  -- Binaries for Linux and MS-Windows
hel...@deepsoft.com   -- http://www.deepsoft.com/ModelRailroadSystem/
   
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] eth0 killed when adding virtual interface and multiple NICs are present

2009-04-25 Thread Kai Schaetzl
JohnS wrote on Sat, 25 Apr 2009 16:32:06 -0400:

 You *must* specify the HWADDR field in the ifcfg-* files in order to
 have persistent ethernet naming.

And that is what I always do. Never done it another way.
You may have overlooked that part in my message where I state that it 
works without a problem despite this juggling around until I add a virtual 
interface to eth0. I'll try tomorrow adding HWADDR to eth0:1 as well, but 
I think this will fail.
I guess I will have to turn off in the BIOS or remove eth2 and maybe eth1 
as well tomorrow and run some more tests with just one adapter and then 
add to it. I hope I can switch off eth2 in the BIOS somehow. I would hate 
to remove it as it is below the SAS adapter and the many SATA cables.

Thanks for the answers so far. At least confirms that the simple juggling 
around of the main network interfaces is normal and to be expected.

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos