Several ProLiant Target Servers Are Unable To Obtain An IP Address At Various Stages Of A VMware Or Linux Scripted Install
Article: 173
Applies to: Releases 3.00 through 3.60
When the target server is connected to the deployment network using a single physical network
connection, it may fail to obtain an IP address at various stages of a VMware or Linux scripted install.
The various stages impacted and where the target server may exhibit this failure are while
booting from the installation kernel, the first production operating system boot, or
after installation of the Linux ProLiant Support Pack.
The servers impacted are
| • |
ProLiant BL20p G3 |
| • |
ProLiant BL20p G4 |
| • |
ProLiant BL25p G2 |
| • |
ProLiant BL45p G2 |
| • |
ProLiant BL460c |
| • |
ProLiant BL465c |
| • |
ProLiant BL480c |
| • |
ProLiant BL680c |
| • |
ProLiant BL685c |
The operating systems impacted are
| • |
VMware ESX Server 3.0.x |
| • |
Red Hat Enterprise Linux AS/ES 3 for AMD64 and Intel EM64T |
| • |
Red Hat Enterprise Linux AS/ES 4 for x86 |
| • |
Red Hat Enterprise Linux AS/ES 4 for AMD64 and Intel EM64T |
| • |
Red Hat Enterprise Linux 5 for x86 |
| • |
Red Hat Enterprise Linux 5 for AMD64 and Intel EM64T |
| • |
SUSE LINUX Enterprise Server 9 for x86 |
| • |
SUSE LINUX Enterprise Server 9 for AMD64 and Intel EM64T |
| • |
SUSE LINUX Enterprise Server 10 for x86 |
| • |
SUSE LINUX Enterprise Server 10 for AMD64 and Intel EM64T |
To resolve this issue, connect all available network ports to the deployment
network while performing a scripted install. This will work for all
operating systems and target servers affected.
|
Printable version
