The Custom Deployment Tool - HP AB500A - Integrated Lights-Out Advanced Configuration

Planning and configuration recommendations for integrated lights-out processors
Hide thumbs Also See for AB500A - Integrated Lights-Out Advanced:
Table of Contents

Advertisement

Create an autoexec.bat file that contains the following:
path=c:\;c:\net;c:\batch;a:\
c:
md c:\net
md c:\batch
copy a:\batch\*.* c:\batch\*.*
c:
a:\pkunzip -d a:\net.zip
REM Launch the process
c:\batch\cpqlodos /get_nicconfig > c:\batch\ilo.txt c:\batch\SETUPNET.EXE
c:\batch\mapping.txt C:\net c:\batch\ilo.txt c:\batch\ghst.bat >
c:\batch\setvars.bat
c:\batch\netstart
The process expands the entire net and batch directories (that come with making a diskette with
CPQIMAGE.EXE ) into the RAM drive. The SETUPNET.EXE is a 'C' executable that reads through the
mappng.txt file and creates a protocol.ini, system.ini ( which needs a unique NetBIOS computer
name, for example, TSXXXXXX where XXXXXX are the 6 'non-vendor' MAC address characters ) and
a batch file that maps a drive to the specified image location and launches GHOST with command
lines that fully automate the image upload. Then, GHSTWALK is run with command lines that change
the SID and computer name.
Below are a few lines from the mapping.txt file. This file is 'space' delimited. The first parameter is the
reversed MAC address so that it matches the output of CPQLODOS.EXE. The next parameter is the
computer name. The next parameters are: IP parameters, Drive letter to map, Share point, Image
Path, Citrix Farm, and Citrix Zone.
Only IP and Image info is used in the DOS portion. This same file is used once the OS is booted as
well, to set the IP, computer name, Citrix farm, and Citrix zone.
04:75:a2:02:08:00 SERVERNAME-A 192.168.0.10 255.255.255.0 10.91.197.1 R:
\\sharepoint-a\image$ \CPP\G2\CPP0001.GHO MPS MN-Zone1
34:6c:a2:02:08:00 SERVERNAME-B 192.168.0.11 255.255.255.0 10.91.197.1 R:
\\sharepoint-a\image$ \CPP\G2\CPP0001.GHO MPS MN-Zone1
78:54:ee:02:08:00 SERVERNAME-C 192.168.0.12 255.255.255.0 10.91.197.1 R:
\\sharepoint-b\image$ \CPP\G2\CPP0001.GHO MPS MN-Zone1
18:67:a2:02:08:00 SERVERNAME-D 192.168.0.13 255.255.255.0 10.91.197.1 R:
\\sharepoint-b\image$ \CPP\G2\CPP0001.GHO MPS MN-Zone1
fc:5e:ee:02:08:00 SERVERNAME-E 192.168.0.14 255.255.255.0 10.91.197.1 R:
\\sharepoint-c\image$ \CPP\G2\CPP0001.GHO MPS MN-Zone1
3e:72:ee:02:08:00 SERVERNAME-F 192.168.0.15 255.255.255.0 10.91.197.1 R:
\\sharepoint-c\image$ \CPP\G3\CPP0001.GHO MPS MN-Zone1
20:fe:f1:02:08:00 SERVERNAME-G 192.168.0.16 255.255.255.0 10.91.197.1 R:
\\sharepoint-d\image$ \CPP\G3\CPP0001.GHO MPS MN-Zone1

The custom deployment tool

In this example, a custom deployment tool named SETUPNET.EXE was created to handle the
installation parameter mapping for each individual deployed server. The main responsibility of the
SETUPNET.EXE is to use the server's MAC address (obtained via the CPQLODOS query) to index into
the mapping.txt file and pull the installation parameters that are unique to the specific server, and to
create protocol.ini and system.ini files on the RAM disk based on the obtained information. Once this
information has been written to the initialization files (protocol.ini and system.ini), the operating
system installation on this server can proceed.
37

Advertisement

Table of Contents
loading

Table of Contents