Red Hat Bugzilla – Bug 461113
[RHEL5.2] LCS problem during installation while loading ramdisk
Last modified: 2008-09-18 02:51:08 EDT
Anupama B. Nagaraj <firstname.lastname@example.org> - 2008-09-01 08:28 EDT
Problem with LCS devices grouped and made online during installation .
After installation completes the LCS interfaces doesn't come up .
Provide output from "uname -a", if possible:
Linux xxx 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:58 EDT 2008 s390x s390x
Is this reproducible?
If so, how long does it (did it) take to reproduce it? yes
Describe the steps:
1) DOWNLOAD THE INITIAL RAMDISK IMAGES
2) Load the RAMDisk
3) Give LCS details and proceed with the installation
4) After the installtion , ipl the dasd
If not, describe how the bug was encountered:
After ipl dasd , eth0 which is lcs interface doesn't come up on boot.
When we check , ifcfg-eth0 scripts in //etc/sysconfig/network-scripts arp=no
, so the interface is not coming up on boot.
Ursula Braun <email@example.com> - 2008-09-03 03:48 EDT
This problem cannot be fixed within the lcs-driver. It is a RHEL5-install
problem. When using an lcs-device for installing, the final
/etc/sysconfig/network-script/ifcfg-eth0 configuration file must not contain the
line "ARP=no". With "ARP=no" the lcs-interface eth0 comes up with NOARP set. In
this case networking based on the lcs-device is broken.
Sorry. This was mirrored here by mistake and was not intended for action here. So closing this bug.