User manual HP PROCURVE 2510-48G

[. . . ] VLAN configuration can be accomplished using the scriptable command line interface included with each interconnect switch. The intended audience for this paper is engineers and system administrators familiar with ProLiant BL interconnect switches and deploying servers using RDP Windows Edition on ProLiant BL systems. The paper will be of particular interest to readers who want to automate the configuration of interconnect switch ports as part of server blade deployment. 40 server-side scripts 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. [. . . ] The Perl script must be executed from this directory. see Step 4 for additional changes if an alternate directory is used. Step 3: Modify the data file to match your environment In order for the code in the appendix to work in your environment, you will need to modify the code to reflect the appropriate configuration settings for that environment. The code in the appendices corresponds to the environment described in the Problem description section, and may not be appropriate for your environment. Step 4: Add a server-side script task with the provided code and properties To add a Run Script task: Paste the rack location and switch configuration call into the Run this script box. 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. The code reads the rack location of the server being deployed from the RDP database and writes them into environmental variables. The last line executes a Perl script that uses this rack location to properly configure a VLAN for the interconnect switch port on both the left and right switch. the number10 is passed into the Perl script as the VLAN to be configured. The Perl script must be executed from the directory where it resides, so the server-side script has to change directory (cd) before executing the Perl switch configuration program. scripted Telnet is script execution to a remote device via a telnet connection to that device. In the example solution Perl based Telnet scripting is used because it is easily configured and accessible to most IT professionals. Using the rack and server blade enclosure identifiers from the previously created environmental variables, the program obtains access information for the left and right interconnect switches from a database created for this solution. In order to connect with each interconnect switch, the switch IP and login information must be known. The mechanism used in the example is to create a text file which relates a rack/enclosure combination to the left and right interconnect switch host, user, and password information. This text file needs to be generated prior to server deployment. If this mechanism is used, set the access information for this text file to limit access to everything except the interconnect switch configuration program. Next, the program finds the interconnect switch port numbers associated with the server being deployed from the server blade enclosure bay number. Depending on which NICs need to be placed on specific VLANs, the bay number needs to be mapped into the appropriate interconnect switch port numbers. Bay to port mapping varies: eClass interconnect switches have a different bay to port mapping than p-Class systems. The program then logs onto the left interconnect switch using scripted Telnet. [. . . ] This will be a no-operation if already in CLI mode # and will switch to CLI if in menu mode as "switch to CLI" # is the first item in the menu. $ok = $telnet->print(""); $ok = $telnet->waitfor(Match => $prompt); # Set paging mode off so the CLI is not looking for interactive commands. @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). Sub GetPortNumbers { local(%switch_ports); local($slot) = @_[0]; # Get passed in slot number 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; 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. [. . . ]