HP DL1000 system?

[Les Mikesell-2]

I've been using a drbl/clonezilla (RPM-installed on Centos 5.x) to image
  IBM and other servers successfully, and now need to do some HP DL1000
servers.  These have 4 mostly independent systems in a 2U chassis
(probably not that relevant to the problem) and we are adding a 4-port
Intel gig NIC card to each.  The systems don't seem to PXE boot at all
on the internal NIC at least with the default settings, but will from
the Intel card.  However, after the tftp download the client cycles
through all the NICS and reports that it cannot obtain a DHCP address.
Has anyone seen this problem before? Booting with a recent
clonezilla-live CD seems to work and picks up a dhcp address so it can
connect to the server for image storage.

--
   Les Mikesell
    lesmikesell@...

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Drbl-user mailing list
Drbl-user@...
https://lists.sourceforge.net/lists/listinfo/drbl-user

[Steven Shiau]

Maybe the kernel from CentOS 5.x (I believe it's 2.6.18) is too old so
it does not support your NIC very well?

Steven.

Les Mikesell wrote:

> I've been using a drbl/clonezilla (RPM-installed on Centos 5.x) to image
>   IBM and other servers successfully, and now need to do some HP DL1000
> servers.  These have 4 mostly independent systems in a 2U chassis
> (probably not that relevant to the problem) and we are adding a 4-port
> Intel gig NIC card to each.  The systems don't seem to PXE boot at all
> on the internal NIC at least with the default settings, but will from
> the Intel card.  However, after the tftp download the client cycles
> through all the NICS and reports that it cannot obtain a DHCP address.
> Has anyone seen this problem before? Booting with a recent
> clonezilla-live CD seems to work and picks up a dhcp address so it can
> connect to the server for image storage.
>
>  

--
Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org>
National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw
Public Key Server PGP Key ID: 1024D/9762755A
Fingerprint: A2A1 08B7 C22C 3D06 34DB  F4BC 08B3 E3D7 9762 755A


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Drbl-user mailing list
Drbl-user@...
https://lists.sourceforge.net/lists/listinfo/drbl-user

[Les Mikesell-2]

Not sure about these 4-port intel cards - I haven't had trouble with any other
intel gig cards under CentOS, and RHEL/CentOS tend to backport drivers for
mainstream devices.  The kernel from 5.4 is out as an update now so I can try
that easily.  Is there a way to make the client boot something different than
the server runs if that doesn't help?


Steven Shiau wrote:

> Maybe the kernel from CentOS 5.x (I believe it's 2.6.18) is too old so
> it does not support your NIC very well?
>
> Steven.
>
> Les Mikesell wrote:
>> I've been using a drbl/clonezilla (RPM-installed on Centos 5.x) to
>> image   IBM and other servers successfully, and now need to do some HP
>> DL1000 servers.  These have 4 mostly independent systems in a 2U
>> chassis (probably not that relevant to the problem) and we are adding
>> a 4-port Intel gig NIC card to each.  The systems don't seem to PXE
>> boot at all on the internal NIC at least with the default settings,
>> but will from the Intel card.  However, after the tftp download the
>> client cycles through all the NICS and reports that it cannot obtain a
>> DHCP address. Has anyone seen this problem before? Booting with a
>> recent clonezilla-live CD seems to work and picks up a dhcp address so
>> it can connect to the server for image storage.
>>
>>  
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Drbl-user mailing list
Drbl-user@...
https://lists.sourceforge.net/lists/listinfo/drbl-user

[Les Mikesell-2]

After a little more testing: the kernel does recognize the NICs, but
they seem to take an exceptionally long time to negotiate with the
connected switch (which is probably doing spanning-tree at the time) and
the DHCP client times out before the network is ready.  Dropping a hub
between them works as a quick fix and maybe I'll be able to do something
to speed up the switch.

But, I ran into another problem:  I used a newer clonezilla-live CD to
save an image which it saw as /dev/sda and now that PXE boot works, the
older kernel being loaded sees this same (SATA) device as /dev/hda and
won't restore.  Is there an easier fix than editing the underlying files?

  -Les


Les Mikesell wrote:

> Not sure about these 4-port intel cards - I haven't had trouble with any other
> intel gig cards under CentOS, and RHEL/CentOS tend to backport drivers for
> mainstream devices.  The kernel from 5.4 is out as an update now so I can try
> that easily.  Is there a way to make the client boot something different than
> the server runs if that doesn't help?
>
>
> Steven Shiau wrote:
>> Maybe the kernel from CentOS 5.x (I believe it's 2.6.18) is too old so
>> it does not support your NIC very well?
>>
>> Steven.
>>
>> Les Mikesell wrote:
>>> I've been using a drbl/clonezilla (RPM-installed on Centos 5.x) to
>>> image   IBM and other servers successfully, and now need to do some HP
>>> DL1000 servers.  These have 4 mostly independent systems in a 2U
>>> chassis (probably not that relevant to the problem) and we are adding
>>> a 4-port Intel gig NIC card to each.  The systems don't seem to PXE
>>> boot at all on the internal NIC at least with the default settings,
>>> but will from the Intel card.  However, after the tftp download the
>>> client cycles through all the NICS and reports that it cannot obtain a
>>> DHCP address. Has anyone seen this problem before? Booting with a
>>> recent clonezilla-live CD seems to work and picks up a dhcp address so
>>> it can connect to the server for image storage.
>>>
>>>  
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Drbl-user mailing list
> Drbl-user@...
> https://lists.sourceforge.net/lists/listinfo/drbl-user

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Drbl-user mailing list
Drbl-user@...
https://lists.sourceforge.net/lists/listinfo/drbl-user

[Steven Shiau]

Hi Les,

Les Mikesell wrote:

> After a little more testing: the kernel does recognize the NICs, but
> they seem to take an exceptionally long time to negotiate with the
> connected switch (which is probably doing spanning-tree at the time) and
> the DHCP client times out before the network is ready.  Dropping a hub
> between them works as a quick fix and maybe I'll be able to do something
> to speed up the switch.
>
> But, I ran into another problem:  I used a newer clonezilla-live CD to
> save an image which it saw as /dev/sda and now that PXE boot works, the
> older kernel being loaded sees this same (SATA) device as /dev/hda and
> won't restore.  Is there an easier fix than editing the underlying files?
>  

There is one command available to convert that, i.e.
/opt/drbl/sbin/cnvt-ocs-dev.
E.g.
cnvt-ocs-dev -d /home/images NOMOREXP hda sda
For more info, please run:
/opt/drbl/sbin/cnvt-ocs-dev --help


Steven.

>   -Les
>
>
> Les Mikesell wrote:
>  
>> Not sure about these 4-port intel cards - I haven't had trouble with any other
>> intel gig cards under CentOS, and RHEL/CentOS tend to backport drivers for
>> mainstream devices.  The kernel from 5.4 is out as an update now so I can try
>> that easily.  Is there a way to make the client boot something different than
>> the server runs if that doesn't help?
>>
>>
>> Steven Shiau wrote:
>>    
>>> Maybe the kernel from CentOS 5.x (I believe it's 2.6.18) is too old so
>>> it does not support your NIC very well?
>>>
>>> Steven.
>>>
>>> Les Mikesell wrote:
>>>      
>>>> I've been using a drbl/clonezilla (RPM-installed on Centos 5.x) to
>>>> image   IBM and other servers successfully, and now need to do some HP
>>>> DL1000 servers.  These have 4 mostly independent systems in a 2U
>>>> chassis (probably not that relevant to the problem) and we are adding
>>>> a 4-port Intel gig NIC card to each.  The systems don't seem to PXE
>>>> boot at all on the internal NIC at least with the default settings,
>>>> but will from the Intel card.  However, after the tftp download the
>>>> client cycles through all the NICS and reports that it cannot obtain a
>>>> DHCP address. Has anyone seen this problem before? Booting with a
>>>> recent clonezilla-live CD seems to work and picks up a dhcp address so
>>>> it can connect to the server for image storage.
>>>>
>>>>  
>>>>        
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry® Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9-12, 2009. Register now!
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> Drbl-user mailing list
>> Drbl-user@...
>> https://lists.sourceforge.net/lists/listinfo/drbl-user
>>    
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Drbl-user mailing list
> Drbl-user@...
> https://lists.sourceforge.net/lists/listinfo/drbl-user
>  

--
Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org>
National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw
Public Key Server PGP Key ID: 1024D/9762755A
Fingerprint: A2A1 08B7 C22C 3D06 34DB  F4BC 08B3 E3D7 9762 755A


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Drbl-user mailing list
Drbl-user@...
https://lists.sourceforge.net/lists/listinfo/drbl-user