Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
HP.com home

HP Insight Control server deployment

Knowledge base
» 

Server management

» Insight Control server deployment Knowledge Base
Resources
» Evaluation license
» Training
» Altiris
» Unified Infrastructure Management
» HP Systems Insight Manager
» HP BladeSystem Management
» HP Insight Software
» Storage Essentials
Related products
» ProLiant servers
» ProLiant clusters
» Insight Software services
» ProLiant services
» New products
» Retired products
» ProLiant IT consolidation
» Special promotions
» Site map
announcing new products
Limited Time Offer: FREE SLES High Availability Extensions with SLES Subscriptions sold with HP Support
 
Content starts here
How To Add An Oracle Enterprise Linux Scripted Install job

Article: 199

Applies to: Releases 3.81 through 3.83

IMPORTANT: The ProLiant Bundle for Oracle Enterprise Linux (OEL) does not contain an integrated automated installer. You will have to manually install or update the drivers and agents from the bundle to take advantage of them. Step 9d provides an example on how to install drivers and agents as part of the job.

IMPORTANT: The hp-health package is required to install the one-time boot to PXE functionality on the production operating system. If this package is not installed, the target will not automatically boot PXE after the operating system is installed.

To create a Linux scripted install job to install OEL 5.2 or greater on a server:

1. On the Deployment Server for the Linux boot files, create a new directory in the .\lib\osdist directory for the specific version and update. For example, for OEL 5.2 create .\lib\osdist\oel52.
2. Copy the entire contents of each distribution DVD or CD into this new directory.
3. For the kickstart file, create a new directory in the .\lib\osconfig directory with the same name as the directory created in step 1.
4. Copy the corresponding Red Hat Linux version kickstart file to this new directory. For example, copy the files from .\lib\osconfig\rhel52 to .\lib\osconfig\oel52.
5. Using a Linux compatible editor, edit the kickstart file to modify the line
./altiris-adlagent*.bin 1>>$InstallLog 2>>$InstallLog
to
./altiris-adlagent*.bin --install-as=redhat 1>>$InstallLog 2>>$InstallLog
6. Create a new directory in the .\lib\software directory for the specific ProLiant bundle version. For example, for Oracle EL 5.2 create .lib\software\ProLiant Support Pack 1.0.0 for Oracle EL 5.2.
7. Copy and extract the downloaded bundle to the corresponding directory created in step 6.
8. At the Deployment Server console, copy the corresponding Red Hat Linux scripted install job and rename it. For example, from the Server Deployment folder, copy the Deploy ProLiant ML/DL/BL + Red Hat EL 5.2 for x86 + PSP {LinuxPE} job and rename it to Deploy ProLiant ML/DL/BL + Oracle EL 5.2 for x86 + PSP {LinuxPE}.
9. Edit the new job with the following changes:
a. In the Run Script - Create Boot Environment task, locate the # replacetokens .\lib\osconfig\yyyy\default.cfg .\lib\osconfig\yyyy\%ID%.cfg line and replace the yyyy value with the directory name created in step 3. For example, change the line to # replacetokens .\lib\osconfig\rhel52\default.cfg .\lib\osconfig\oel52\%ID%.cfg.
b. In the Run Script - Create Boot Environment task, locate the export dist= line and replace the value with the directory in step 1. For example, change the line to export dist=oel52.
c. In the Copy file to task, change the source path to point to the corresponding bundle directory created in step 6.
d. In the Run Script - Install ProLiant Support Pack task, remove the following lines as there is no installer available for ProLiant Bundle:
dos2unix -n rdpinstall.sh rdpinstall.sh
dos2unix -n rdpinstall.dat rdpinstall.dat
./rdpinstall.sh


and to install individual components from the bundle, add commands to extract the component and install using rpm. For example, to install the health agent, add the following command to the task:
rpm -ivh hp-health*.rpm >> /root/install.rdp.log

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2012 Hewlett-Packard Development Company, L.P.