Using ProLiant Essentials Rapid Deployment Pack for scripted blade based switch configuration

Solution details
Acquisition List
You need the following to execute the supplied example solution:
RDP Windows Edition v1.40 (or later) deployment server
ProLiant BL e-Class or p-Class system with associated interconnect switch option
Perl version 5.6 (or later) with the telnet module installed on the deployment server
Code from the appendix of this document
Code description
The scripts used in this example are partitioned into five parts.
1. Server-Side Script: DOS script code that obtains the rack location from the RDP database and
executes the Perl based interconnect switch configuration program
2. SwitchConfig.pl: A Perl based interconnect switch configuration program that will configure the
interconnect switch ports for the proper VLAN connectivity.
3. GetSwitchInfo.pm: A Perl module loaded by the interconnect switch configuration program
(SwitchConfig.pl). This module contains code that is not specific to any particular interconnect
switch. This module contains a single sub-function called GetSwitchInfo(). This sub-function uses
passed-in rack location information as a key and searches the interconnect switch information data
file (SwitchInfo.txt) to return the interconect switch address and login information.
4. *GbE*.pm: A Perl module loaded by the interconnect switch configuration program. This module
contains code that is specific to the interconnect switch used in the enclosure. A version of this
module is provided for each switch (pGbE.pm
, pGbE2.pm, and eGbE.pm), for the p-Class GbE, p-
Class GbE2, and e-Class GbE Interconnect Switches, respectively. Each version of this module
contains two sub-functions:
GetPortNumbers(): Maps the server blade enclosure bay number to the corresponding
interconnect switch port numbers.
ConfigVlan(): Connects to the interconnect switch and performs the VLAN configuration.
SwitchInfo.txt: An example text based database file that contains the interconnect switch address
and access information.
5.
Implementation steps
Copy and rename one of the server blade Windows scripted install jobs 1.
Copy the files from the appendices to the specified directory on the RDP server 2.
Modify the data file to match your environment 3.
Add a server-side script task with the provided code and properties 4.
Use the newly created RDP job by dragging and dropping it onto a server blade 5.
Step 1: Copy and rename one of the server blade Windows scripted install jobs
To copy a job:
1. Select the deployment job to copy.
2. Right click and select the copy operation.
3. Select the folder where the new job will be placed.
4. Right click and select Paste.
5. Select the new job.
6. Right click and select Rename.
7. Type the name for the newly created job.
8