<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Ath,<br>
<br>
yes, the network devices are connected and working.<br>
no, i can't and don't want to make a dvd based kickstart, because i
need the network install for more than 1 Blade<br>
<br>
my main problem is the strange behavior while installing rhel5 using
spacewalk<br>
<br>
during my tests i came across the following scenarios:<br>
<br>
- in Kickstart File network parameter without "--device"<br>
<br>
- defining system in cobbler with eth network devices:<br>
<br>
PXE works but system can't download Kickstart file with
message no network device found for kickstart<br>
<br>
- defining system in cobbler with em network devices:<br>
<br>
PXE works fine, system finds Kickstart file and Install
works, but installed system has no Network afterwards because em
Devices do not exist in rhel5<br>
<br>
- in Kickstart File network parameter with "--device=eth0"<br>
<br>
- defining system in cobbler with em network devices:<br>
<br>
install runs fine, system has afterwards no network<br>
<br>
- defining system in cobbler with eth network devices:<br>
<br>
install runs fine and system has network as specified in
cobbler.<br>
<br>
When installing rhel6 the "--device" parameter is not required.<br>
i already found the solution to my problem ("--device=eth0"
parameter in network definition in Spacewalk required).<br>
I was only wondering about the behavior <br>
<br>
Regards<br>
Frank<br>
<br>
<div class="moz-cite-prefix">On 07/09/2014 04:44 PM, ATH KEBEI
wrote:<br>
</div>
<blockquote
cite="mid:1404917069.22356.YahooMailNeo@web164004.mail.gq1.yahoo.com"
type="cite">
<div style="color:#000; background-color:#fff; font-family:times
new roman, new york, times, serif;font-size:14pt">
<div style="" class=""><span style="" class="">Frank,</span></div>
<div class="" style="color: rgb(0, 0, 0); font-size: 18.6667px;
font-family: times new roman,new york,times,serif;
background-color: transparent; font-style: normal;"><span
style="" class="">On your cmc (chassis management
controller), after logging in, click on chassis overview,
and then on the blade (Slot) you want to install rhel 5 on,
once the GUI is open, on the left side, scroll to hardware,
Network Devices, click on Integrated NIC 1, under ports and
Partitioned Ports check Link status (up/down)? Down means
you have to physically make the connections with cabling and
then allow the NIC to communicate with your network by
opening the ports you need (80,443?)</span></div>
<div class="" style="color: rgb(0, 0, 0); font-size: 18.6667px;
font-family: times new roman,new york,times,serif;
background-color: transparent; font-style: normal;"><span
style="" class="">Why dont you just create a dvd-based
kickstart? <br style="" class="">
</span></div>
<div class="" style="color: rgb(0, 0, 0); font-size: 18.6667px;
font-family: times new roman,new york,times,serif;
background-color: transparent; font-style: normal;"><span
style="" class="">1. mkdir /rheliso<br style="" class="">
</span></div>
<div class="" style="color: rgb(0, 0, 0); font-size: 18.6667px;
font-family: times new roman,new york,times,serif;
background-color: transparent; font-style: normal;"><span
style="" class="">2. mount the base iso: mount /dev/cdrom
/mnt/ -o loop</span></div>
<div class="" style="color: rgb(0, 0, 0); font-size: 18.6667px;
font-family: times new roman,new york,times,serif;
background-color: transparent; font-style: normal;"><span
style="" class="">3.</span>shopt -s dotglob</div>
<div class="" style="color: rgb(0, 0, 0); font-size: 18.6667px;
font-family: times new roman,new york,times,serif;
background-color: transparent; font-style: normal;">4. cp -ri
/mnt/* /rheliso<br style="" class="">
</div>
5. create or you already have a ks.cfg file: cp ks.cfg /rheliso<br
style="" class="">
7. cd /rheliso<br style="" class="">
8. cd isolinux<br style="" class="">
9. vim isolinux.cfg : Under <span class="" style="font-style:
italic;">label linux </span><br style="" class="">
change:<span class="" style="font-style: italic;"> <br style=""
class="">
append initrd=initrd.img</span> <br style="" class="">
to <span class="" style="font-style: italic;"><br style=""
class="">
append initrd=initrd.img ks=cdrom:/ks.cfg<br style="" class="">
</span><br>
10. cd /rheliso<br>
11. mkisofs -o /tmp/myksiso -b isolinux/isolinux.bin -c
isolinux/boot.cat --no-emul-boot --boot-load-size 4
--boot-info-table -J -R -V disks .<br>
N.B. This is one command and it has to be exact except for where
you want your new iso created if not /tmp.<br style="" class="">
<span style="" class=""><span style="font-family: Courier New;">12.
Go to /tmp and use winscp to get your new kickstart iso</span>
over to the virtual console of the Dell. map it and at the
boot prompt:<br>
linux ks=cdrom:/ks.cfg ip=x.x.x.x<br style="" class="">
</span>
<div style="" class=""> </div>
<div style="" class=""><font style="" class="" color="#0000ff"
face="comic sans ms" size="4"><i style="" class="">Oh yes,
you can make today a great day! Thanks.<br style=""
class="">
<span style="" class=""></span><br style="" class="">
<span style="" class=""></span>Very Respectfully,<br
style="" class="">
<span style="" class=""></span>A. C. Kebei</i></font></div>
<div style="" class=""><font style="" class="" color="#0000ff"
face="Comic Sans MS" size="4"><i style="" class=""><br
style="" class="">
<span style="" class=""></span>Always, Very Committed to
Excellence and the fair treatment of all.</i></font></div>
<div style="" class=""><br style="" class="">
</div>
<div class="" style="font-family: times new roman, new york,
times, serif; font-size: 14pt;">
<div class="" style="font-family: HelveticaNeue, Helvetica
Neue, Helvetica, Arial, Lucida Grande, sans-serif;
font-size: 12pt;">
<div style="" class="" dir="ltr">
<hr style="" class="" size="1"> <font style="" class=""
face="Arial" size="2"> <b style="" class=""><span
class="" style="font-weight:bold;">From:</span></b>
Frank Paulick <a class="moz-txt-link-rfc2396E" href="mailto:frank.paulick@baaderbank.de"><frank.paulick@baaderbank.de></a><br
style="" class="">
<b style="" class=""><span class="" style="font-weight:
bold;">To:</span></b> <a class="moz-txt-link-abbreviated" href="mailto:spacewalk-list@redhat.com">spacewalk-list@redhat.com</a> <br
style="" class="">
<b style="" class=""><span class="" style="font-weight:
bold;">Sent:</span></b> Wednesday, July 9, 2014 3:18
AM<br style="" class="">
<b style="" class=""><span class="" style="font-weight:
bold;">Subject:</span></b> Re: [Spacewalk-list]
Problem installing RHEL5 on Dell M620<br style=""
class="">
</font> </div>
<div style="" class=""><br style="" class="">
Hi Chris,<br style="" class="" clear="none">
<br style="" class="" clear="none">
you were right.<br style="" class="" clear="none">
i thougt that the renaming from eth0 to em1 was introduced
in <br style="" class="" clear="none">
rhel6(together with dell afaik)<br style="" class=""
clear="none">
looks like i was wrong there.<br style="" class=""
clear="none">
<br style="" class="" clear="none">
Thanks for helping<br style="" class="" clear="none">
Regards<br style="" class="" clear="none">
Frank<br style="" class="" clear="none">
<br style="" class="" clear="none">
On 07/08/2014 06:21 PM, Chris Balcum wrote:<br style=""
class="" clear="none">
> Could it be your network device names? For example,
using em1,2,3 instead<br style="" class="" clear="none">
> of eth0,1,2,3.<br style="" class="" clear="none">
><br style="" class="" clear="none">
><br style="" class="" clear="none">
><br style="" class="" clear="none">
><br style="" class="" clear="none">
> On 7/8/14, 11:04 AM, "Frank Paulick" <<a
moz-do-not-send="true" style="" class="" shape="rect"
ymailto="mailto:frank.paulick@baaderbank.de"
href="mailto:frank.paulick@baaderbank.de">frank.paulick@baaderbank.de</a>>
wrote:<br style="" class="" clear="none">
><br style="" class="" clear="none">
>> Hi,<br style="" class="" clear="none">
>><br style="" class="" clear="none">
>> i have a running spacewalk 2.1 installation.<br
style="" class="" clear="none">
>> Installing rhel6 works like a charme.<br style=""
class="" clear="none">
>> today i created a new kickstart for rhel5 using
the first install cd as<br style="" class="" clear="none">
>> source for the kickstart tree.<br style=""
class="" clear="none">
>><br style="" class="" clear="none">
>> the system i want to install is a Dell M620 Blade
which has the<br style="" class="" clear="none">
>> following network adapter:<br style="" class=""
clear="none">
>><br style="" class="" clear="none">
>> Ethernet controller: Broadcom Corporation
NetXtreme II BCM57810 10<br style="" class="" clear="none">
>> Gigabit Ethernet (rev 10)<br style="" class=""
clear="none">
>><br style="" class="" clear="none">
>> this adapter is normally using the bnx2x driver.<br
style="" class="" clear="none">
>> when trying to install the system, pxe works
fine, but the install stops<br style="" class=""
clear="none">
>> saying "Unable to download Kickstart file"<br
style="" class="" clear="none">
>> using the url in the message i can open the file
in a browser from<br style="" class="" clear="none">
>> another system.<br style="" class="" clear="none">
>> on console 3 (ALT-F3) i see the following error
messages:<br style="" class="" clear="none">
>><br style="" class="" clear="none">
>> no network device in choose network device!<br
style="" class="" clear="none">
>> no network drivers for doing kickstart<br
style="" class="" clear="none">
>> unable to bring up network<br style="" class=""
clear="none">
>><br style="" class="" clear="none">
>> After this i booted the system from the install
cd into rescue mode.<br style="" class="" clear="none">
>> there i had no problem activating the network
device.<br style="" class="" clear="none">
>> i also checked the bnx2x driver in the initrd
file for pxe.<br style="" class="" clear="none">
>> the driver is @version:<br style="" class=""
clear="none">
>><br style="" class="" clear="none">
>> filename: 2.6.18-371.el5/x86_64/bnx2x.ko<br
style="" class="" clear="none">
>> version: 1.72.51-0<br style="" class=""
clear="none">
>><br style="" class="" clear="none">
>> this is the same version as with RHEL6:<br
style="" class="" clear="none">
>><br style="" class="" clear="none">
>> filename:<br style="" class="" clear="none">
>>
/lib/modules/2.6.32-358.el6.x86_64/kernel/drivers/net/bnx2x/bnx2x.ko<br
style="" class="" clear="none">
>> firmware: bnx2x/bnx2x-e2-7.2.51.0.fw<br
style="" class="" clear="none">
>> firmware: bnx2x/bnx2x-e1h-7.2.51.0.fw<br
style="" class="" clear="none">
>> firmware: bnx2x/bnx2x-e1-7.2.51.0.fw<br
style="" class="" clear="none">
>> version: 1.72.51-0<br style="" class=""
clear="none">
>><br style="" class="" clear="none">
>> Installing rhel6 on this system works without any
problem.<br style="" class="" clear="none">
>><br style="" class="" clear="none">
>> anyone got an idea what could be wrong ?<br
style="" class="" clear="none">
>> is it possible that the driver, when loaded after
pxe needs the firmware<br style="" class="" clear="none">
>> files which are maybe missing ?<br style=""
class="" clear="none">
>><br style="" class="" clear="none">
>> Regards<br style="" class="" clear="none">
>> Frank<br style="" class="" clear="none">
>><br style="" class="" clear="none">
>> -- <br style="" class="" clear="none">
>> beste Grüße,<br style="" class="" clear="none">
>> Frank Paulick<br style="" class="" clear="none">
>><br style="" class="" clear="none">
>> Baader Bank AG<br style="" class="" clear="none">
>> Weihenstephaner Str. 4<br style="" class=""
clear="none">
>> 85716 Unterschleißheim<br style="" class=""
clear="none">
>> Deutschland<br style="" class="" clear="none">
>><br style="" class="" clear="none">
>> Telefon: +49-89/5150-1522<br style="" class=""
clear="none">
>> Telefax: +49-89/5150-2421<br style="" class=""
clear="none">
>><br style="" class="" clear="none">
>> Email: <a moz-do-not-send="true" style=""
class="" shape="rect"
ymailto="mailto:frank.paulick@baaderbank.de"
href="mailto:frank.paulick@baaderbank.de">frank.paulick@baaderbank.de</a><br
style="" class="" clear="none">
>> Internet: <a moz-do-not-send="true" style=""
class="" shape="rect" href="http://www.baaderbank.de/"
target="_blank">http://www.baaderbank.de</a><br style=""
class="" clear="none">
>> <a moz-do-not-send="true" style=""
class="" shape="rect" href="http://www.bondboard.de/"
target="_blank">http://www.bondboard.de</a><br style=""
class="" clear="none">
>>
**************************************************************************<br
style="" class="" clear="none">
>> ****************************<br style="" class=""
clear="none">
>> Baader Bank AG: Vorstand: Uto Baader (Vors.),
Nico Baader, Dieter<br style="" class="" clear="none">
>> Brichmann; Vorsitzender des Aufsichtsrates: Dr.
Horst Schiessl;<br style="" class="" clear="none">
>> Amtsgericht München HRB 121537; Sitz der
Gesellschaft: Unterschleissheim;<br style="" class=""
clear="none">
>> StNr. 143/100/10066; USt-IdNr. DE114123893.<br
style="" class="" clear="none">
>>
**************************************************************************<br
style="" class="" clear="none">
>> ****************************<br style="" class=""
clear="none">
>> Diese Email enthält vertrauliche Informationen.
Sollten Sie diese Email<br style="" class="" clear="none">
>> irrtümlich erhalten, machen wir Sie darauf
aufmerksam, dass jegliche<br style="" class=""
clear="none">
>> Verwendung strikt untersagt ist. Bitte
informieren Sie uns gegebenenfalls<br style="" class=""
clear="none">
>> unverzüglich und vernichten Sie das Original. Das
unerlaubte Kopieren<br style="" class="" clear="none">
>> sowie die unbefugte Weitergabe dieser Email ist
nicht gestattet.<br style="" class="" clear="none">
>> Wir haben alle verkehrsüblichen Maßnahmen
unternommen, um das Risiko der<br style="" class=""
clear="none">
>> Verbreitung virenbefallener Software oder Emails
zu minimieren, dennoch<br style="" class="" clear="none">
>> raten wir Ihnen, Ihre eigenen Virenkontrollen auf
alle Anhänge an dieser<br style="" class="" clear="none">
>> Nachricht durchzuführen. Wir schließen außer für
den Fall von Vorsatz die<br style="" class="" clear="none">
>> Haftung für jeglichen Verlust oder Schäden durch
virenbefallene Software<br style="" class="" clear="none">
>> oder Emails aus.<br style="" class=""
clear="none">
>><br style="" class="" clear="none">
>> _______________________________________________<br
style="" class="" clear="none">
>> Spacewalk-list mailing list<br style="" class=""
clear="none">
>> <a moz-do-not-send="true" style="" class=""
shape="rect" ymailto="mailto:Spacewalk-list@redhat.com"
href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a><br
style="" class="" clear="none">
>> <a moz-do-not-send="true" style="" class=""
shape="rect"
href="https://www.redhat.com/mailman/listinfo/spacewalk-list"
target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a><br
style="" class="" clear="none">
><br style="" class="" clear="none">
> _______________________________________________<br
style="" class="" clear="none">
> Spacewalk-list mailing list<br style="" class=""
clear="none">
> <a moz-do-not-send="true" style="" class=""
shape="rect" ymailto="mailto:Spacewalk-list@redhat.com"
href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a><br
style="" class="" clear="none">
> <a moz-do-not-send="true" style="" class=""
shape="rect"
href="https://www.redhat.com/mailman/listinfo/spacewalk-list"
target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a>
<div style="" class="" id="yqtfd56900"><br style=""
class="" clear="none">
<br style="" class="" clear="none">
-- <br style="" class="" clear="none">
beste Grüße,<br style="" class="" clear="none">
Frank Paulick<br style="" class="" clear="none">
<br style="" class="" clear="none">
Baader Bank AG<br style="" class="" clear="none">
Weihenstephaner Str. 4<br style="" class="" clear="none">
85716 Unterschleißheim<br style="" class="" clear="none">
Deutschland<br style="" class="" clear="none">
<br style="" class="" clear="none">
Telefon: +49-89/5150-1522<br style="" class=""
clear="none">
Telefax: +49-89/5150-2421<br style="" class=""
clear="none">
<br style="" class="" clear="none">
Email: <a moz-do-not-send="true" style="" class=""
shape="rect"
ymailto="mailto:frank.paulick@baaderbank.de"
href="mailto:frank.paulick@baaderbank.de">frank.paulick@baaderbank.de</a><br
style="" class="" clear="none">
Internet: <a moz-do-not-send="true" style="" class=""
shape="rect" href="http://www.baaderbank.de/"
target="_blank">http://www.baaderbank.de</a><br
style="" class="" clear="none">
<a moz-do-not-send="true" style="" class=""
shape="rect" href="http://www.bondboard.de/"
target="_blank">http://www.bondboard.de</a><br
style="" class="" clear="none">
******************************************************************************************************<br
style="" class="" clear="none">
Baader Bank AG: Vorstand: Uto Baader (Vors.), Nico
Baader, Dieter Brichmann; Vorsitzender des
Aufsichtsrates: Dr. Horst Schiessl; Amtsgericht München
HRB 121537; Sitz der Gesellschaft: Unterschleissheim;
StNr. 143/100/10066; USt-IdNr. DE114123893.<br style=""
class="" clear="none">
******************************************************************************************************<br
style="" class="" clear="none">
Diese Email enthält vertrauliche Informationen. Sollten
Sie diese Email irrtümlich erhalten, machen wir Sie
darauf aufmerksam, dass jegliche Verwendung strikt
untersagt ist. Bitte informieren Sie uns gegebenenfalls
unverzüglich und vernichten Sie das Original. Das
unerlaubte Kopieren sowie die unbefugte Weitergabe
dieser Email ist nicht gestattet.<br style="" class=""
clear="none">
Wir haben alle verkehrsüblichen Maßnahmen unternommen,
um das Risiko der Verbreitung virenbefallener Software
oder Emails zu minimieren, dennoch raten wir Ihnen, Ihre
eigenen Virenkontrollen auf alle Anhänge an dieser
Nachricht durchzuführen. Wir schließen außer für den
Fall von Vorsatz die Haftung für jeglichen Verlust oder
Schäden durch virenbefallene Software oder Emails aus.<br
style="" class="" clear="none">
<br style="" class="" clear="none">
_______________________________________________<br
style="" class="" clear="none">
Spacewalk-list mailing list<br style="" class=""
clear="none">
<a moz-do-not-send="true" style="" class="" shape="rect"
ymailto="mailto:Spacewalk-list@redhat.com"
href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a><br
style="" class="" clear="none">
<a moz-do-not-send="true" style="" class="" shape="rect"
href="https://www.redhat.com/mailman/listinfo/spacewalk-list"
target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a></div>
<br style="" class="">
<br style="" class="">
</div>
</div>
</div>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
beste Grüße,
Frank Paulick
Baader Bank AG
Weihenstephaner Str. 4
85716 Unterschleißheim
Deutschland
Telefon: +49-89/5150-1522
Telefax: +49-89/5150-2421
Email: <a class="moz-txt-link-abbreviated" href="mailto:frank.paulick@baaderbank.de">frank.paulick@baaderbank.de</a>
Internet: <a class="moz-txt-link-freetext" href="http://www.baaderbank.de">http://www.baaderbank.de</a>
<a class="moz-txt-link-freetext" href="http://www.bondboard.de">http://www.bondboard.de</a>
******************************************************************************************************
Baader Bank AG: Vorstand: Uto Baader (Vors.), Nico Baader, Dieter Brichmann; Vorsitzender des Aufsichtsrates: Dr. Horst Schiessl; Amtsgericht München HRB 121537; Sitz der Gesellschaft: Unterschleissheim; StNr. 143/100/10066; USt-IdNr. DE114123893.
******************************************************************************************************
Diese Email enthält vertrauliche Informationen. Sollten Sie diese Email irrtümlich erhalten, machen wir Sie darauf aufmerksam, dass jegliche Verwendung strikt untersagt ist. Bitte informieren Sie uns gegebenenfalls unverzüglich und vernichten Sie das Original. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Email ist nicht gestattet.
Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der Verbreitung virenbefallener Software oder Emails zu minimieren, dennoch raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz die Haftung für jeglichen Verlust oder Schäden durch virenbefallene Software oder Emails aus.
</pre>
</body>
</html>