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

ManualsBrandsHP ManualsSoftwareHP Insight Rapid Deployment 1 Server Software License

Using ProLiant Essentials Rapid Deployment Pack for

scripted blade-based switch configuration

HOWTO

Abstract.............................................................................................................................................. 2

Introduction......................................................................................................................................... 2

Reader requirements......................................................................................................................... 2

Acronyms in text .............................................................................................................................. 2

Text conventions .............................................................................................................................. 3

Problem description ............................................................................................................................. 3

Solution summary ................................................................................................................................ 6

Solution details.................................................................................................................................... 8

Acquisition List................................................................................................................................. 8

Code description ............................................................................................................................. 8

Implementation steps ........................................................................................................................ 8

Step 1: Copy and rename one of the server blade Windows scripted install jobs................................. 8

Step 2: Copy the files from the appendices to the specified directory on the RDP server...................... 10

Step 3: Modify the data file to match your environment................................................................... 10

Step 4: Add a server-side script task with the provided code and properties...................................... 10

Step 5: Use the newly created job by dragging and dropping it onto a server blade.......................... 13

Customizing the solution..................................................................................................................... 14

Understanding the supplied code..................................................................................................... 14

Using an alternative to Perl.............................................................................................................. 15

Changing properties other than VLAN .............................................................................................. 16

Using server-side scripts outside of the RDP environment ..................................................................... 16

Code appendix ................................................................................................................................. 17

SwitchConfig.pl.......................................................................................................................... 17

SwitchInfo.txt ............................................................................................................................. 18

GetSwitchInfo.pm ....................................................................................................................... 18

pGbE.pm (Switch specific code for p-Class GbE Interconnnect Switch).............................................. 19

pGbE2.pm (Switch specific code for p-Class GbE2 Interconnect Switch) ........................................... 20

e-Gbe.pm (Switch specific code for e-Class GbE Interconnect Switch) ............................................... 21

For more information.......................................................................................................................... 23

Call to action .................................................................................................................................... 23

Summary of content (23 pages)

PAGE 1
Using ProLiant Essentials Rapid Deployment Pack for scripted blade-based switch configuration HOWTO Abstract.............................................................................................................................................. 2 Introduction......................................................................................................................................... 2 Reader requirements.......................................................................................
PAGE 2
Abstract This HOWTO describes how to use the HP ProLiant Essentials Rapid Deployment Pack (RDP) Windows Edition v1.40 to integrate ProLiant BL interconnect switch Virtual LAN (VLAN) configuration within server deployment. RDP Windows Edition v1.40 introduces a new feature called server-side scripts. This feature gives IT administrators the ability to create a script task that executes on the RDP deployment server and integrates with other tasks within a deployment job. Using RDP Windows Edition v1.
PAGE 3
Text conventions This HOWTO uses the following conventions to distinguish elements of text: Menu options, Command names, Dialog box names, Screen names These elements appear in initial capital letters and may appear in boldface for emphasis. User input (commands to be typed) User input appears in a different typeface and is highlighted in gray. Scripts and files The content of the scripts and files appears in a different typeface and is highlighted in gray with a border around it.
PAGE 4
Figure 1. Initial interconnect switch configuration RDP Server Red VLAN Client Blue VLAN Client Second Level Swit ch NIC 3 NIC 2 10 iLO NIC 3 8 NIC 2 iLO 7 Switch A 9 NIC 1 9 8 10 7 NIC 1 BL20p Bay 4 BL20p Bay 5 Switch B In Figure 2, the configuration is the same as in Figure 1, except the servers have now been deployed with a new configuration. • For the server in bay 4, the new configuration specifies that NICs 2 and 3 are to be placed on the blue VLAN network (VID=10).
PAGE 5
Figure 2. Updated switch configuration after the servers have been deployed RDP Server Red VLAN Client Blue VLAN Client Network Infrastructure NIC 3 NIC 2 10 iLO NIC 3 8 NIC 2 iLO 7 Switch A 9 NIC 1 9 8 10 7 NIC 1 BL20p Bay 4 BL20p Bay 5 Switch B As in this example, to deploy servers into a ProLiant BL system with the interconnect switch, the required approach had previously consisted of two main steps: 1.
PAGE 6
Solution summary The supplied solution is designed to use RDP server-side scripts to automate the VLAN switch configuration of the interconnect switch as part of deploying an OS to an associated ProLiant BL server. The solution involves adding a server-side script task that configures the associated interconnect switches to an existing RDP deployment job.
PAGE 7
Figure 3. Solution architecture using server-side scripts RDP Server Rapid Deployment Pack RDP Database (Rack Locations) Deployment Event Server-Side Script Retrieves the server Rack Location from the RDP database and calls switch configuration program Remote Script Remote Script is transferred to the server being deployed.
PAGE 8
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.
PAGE 9
In Figure 4, ProLiant BL20p Scripted Install for Microsoft Windows 2000 is the deployment job that will be copied for the example solution. Figure 4. Installation job to modify is selected In Figure 5, ProLiant BL20p Scripted Install for Microsoft Windows 2000 job has been copied and pasted into the Install and Config folder, and then renamed to ProLiant BL20p Scripted Win2000 Install & move switch to vlan10.
PAGE 10
Figure 5. Renamed job in new folder. Step 2: Copy the files from the appendices to the specified directory on the RDP server In order to perform the VLAN interconnect switch configuration, the appropriate code must be copied to a directory on the RDP server. The example in this paper uses c:\SwitchVlanConfig, but the directory can be changed to suit your needs. All Perl files and the text switch access information file must reside in the same local directory on the RDP server.
PAGE 11
7. Select Locally on the Deployment Server. 8. Click OK. Rack location and switch configuration call: (The set slot, set enclosure, and set rack paragraphs within the code are three lines, not three paragraphs. A simple cut/paste will not work; cut and paste each paragraph onto one line within the Run this script box.) set slot=%#*"SELECT physical_bay.real_name FROM computer INNER JOIN physical_bay ON computer.computer_id = physical_bay.computer_id INNER JOIN physical_enclosure ON physical_bay.
PAGE 12
Figure 6.
PAGE 13
Figure 7. Advanced Script Options set to execute locally on the deployment server Step 5: Use the newly created job by dragging and dropping it onto a server blade The new job can be used by dragging and dropping onto a server blade within the environment as illustrated in Figure 8.
PAGE 14
Figure 8. The new event is dragged and dropped onto server BL 1234 to execute VLAN interconnect switch configuration during server deployment Customizing the solution Understanding the supplied code For our example solution, we add a final operation that configures both interconnect switches using server-side scripts. Normally, a RDP Windows Edition script executes on the server being deployed, but server-side scripts are executed locally on the RDP server.
PAGE 15
When the RDP Windows Edition boot image is downloaded onto the server being deployed, it returns the server’s rack, server blade enclosure, and bay ID to the RDP server. The RDP server stores that data in its database. The location information can be retrieved from within a server-side script by executing a specific set of commands.
PAGE 16
Changing properties other than VLAN Server-side scripts can be used to accomplish more than VLAN interconnect switch configuration. As users become comfortable with this feature, server-side script tasks can be created to operate with other tasks within an RDP for Windows deployment job and automate otherwise manually performed functions. For example, a newly deployed server can be added into membership with your load balance.
PAGE 17
Code appendix This section includes sample scripts as a reference for examples provided throughout the HOWTO. SwitchConfig.pl SwitchConfig.pl is a Perl based interconnect switch configuration program that configures the interconnect switch ports for the proper VLAN connectivity. # Load the p-GbE2 specific telnet module. use pGbe2; # Module to communicate with the switch using telnet. using p-GbE or e-GbE, change the use line to the accurate module. use GetSwitchInfo; # Used to get switch details.
PAGE 18
SwitchInfo.txt SwitchInfo.txt is an example text based database file containing the interconnect switch address and access information. # The following record represents switch login information. # Lines not beginning with the switch location are ignored # including blank lines. # Each line is of the following form: # EnclosureName-RackName-switchAorB:SwitchType:NameOrIP:User:Password. # Rack name is rack1, enclosure name is enclosure0. # IP address is 192.168.10.15. User name is root, password is admin.
PAGE 19
pGbE.pm (Switch specific code for p-Class GbE Interconnnect Switch) Note: Change the use line in switchconfing.pl to match the module used. use Net::Telnet; # Connect to the switch using the passed in switch access information # configure the port specified by the passed in port number to the passed # in vlan ID.
PAGE 20
if($slot > 0 && $slot <= 8){ #Insure a slot number was passed in $switch_ports{'nic_0-1'} = (2 * $slot) - 1; $switch_ports{'nic_2-3'} = (2 * $slot); } else { die "Invalid slot number $slot\n"; } return %switch_ports; } 1; pGbE2.pm (Switch specific code for p-Class GbE2 Interconnect Switch) Note: Change the use line in switchconfing.pl to match the module used.
PAGE 21
$switch_ports{'nic_i0-1'} = (2 * $slot) - 1; $switch_ports{'nic_2-3'} = (2 * $slot); } else { die "Invalid slot number $slot\n"; } return %switch_ports; } 1; e-Gbe.pm (Switch specific code for e-Class GbE Interconnect Switch) Note: Change the use line in switchconfing.pl to match the module used. use Net::Telnet; # Connect to the switch using the passed in switch access information # configure the port specified by the passed in port number to the passed ID.
PAGE 22
@tmp = $telnet->cmd("cfg save"); push(@lines, @tmp); $ok = $telnet->print("logout"); $telnet->close(); return @lines; } # # # # Using the passed in slot number, calculate the switch port numbers assigned to: iLO (Right Switch) or PxE (Left Switch). This is nic_0-1. NIC3 (Right Switch) or NIC2 (Left Switch). This is nic_2-3. # Using the passed in slot number, calculate the switch port numbers # assigned to: # Data(Right Switch) or PxE (Left Switch). This is nic_0-1.
PAGE 23
For more information For additional information, refer to the resources detailed below. Table 3. Web resources Resource description Web address ProLiant Essentials Rapid Deployment Pack www.hp.com/servers/rdp e-Class GbE Interconnect Switch http://h18004.www1.hp.com/products/servers/proliant-bl/eclass/interconnect-switch.html p-Class GbE Interconnect Switch http://h18004.www1.hp.com/products/servers/proliant-bl/pclass/20p/bl-p-interconnect-switch.html p-Class GbE2 Interconnect Switch http://h18004.