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

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.

Note:

Due to the nature of the OS installation task, RDP executes the next task

without waiting for the installation to complete. This execution allows

interconnect switch configuration to start while the server OS is in the

process of being installed. Care should be taken if the actions within the

server-side script could interfere with the completion of OS installation.

Using server-side scripts outside of the RDP environment

While the configuration scripts provided in this HOWTO describe how to integrate interconnect

switch configuration in RDP for Windows server deployment, interconnect switch configuration can

also be scripted without RDP. This can be executed using the scriptable command line interface (CLI)

provided with each interconnect switch.

Without RDP Windows Edition integration, the script still needs to determine the interconnect switch

the rack location as command line options to the interconnect switch configuration program, instead

of obtaining them through the environmental variables.

For example:

local($enclosure) = @_[1];

local($rack) = @_[2];

local($slot) = @_[3];

Any valid interconnect switch command line can be executed. Therefore, a complete or partial

interconnect switch configuration can be accomplished through the scripting mechanism.

The entire interconnect switch configuration can also be captured into an editable file using the

interconnect switch configuration file capture and restore capability. On p-Class GbE2 Interconnect

Switches, the command to save the complete configuration file is:

/cfg/dump

/cfg/ptcfg <TFTP server> <filename>

The command to restore the switch configuration file is:

/cfg/gtcfg <TFTP server> <filename>

apply

Equivalent configuration file save and restore commands exist for p-Class GbE and e-Class GbE

Interconnect Switches; the command to save the complete configuration file is:

tftp upload type cfg [path <path_filename>] [ip <ip_addr>] [port <port_num>]

The command to restore the switch configuration file is:

tftp download type cfg [ip <ip_addr>] [port <port_num>]

cfg save

For more information on using the interconnect switch CLI, refer to the user documentation supplied

with the interconnect switch.