HP 289166-40B User Manual

HP ProLiant Network Adapter Scripting Utility User Guide

Part Number 289166-40B March 2008 (Twentieth Edition)
© Copyright 2006, 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.
Microsoft, Windows, Windows Server 2003 and Windows Server 2008 are U.S. registered trademarks of Microsoft Corporation.
Audience assumptions
This document is for the person who installs, administers, and troubleshoots servers and storage systems. HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.

Contents

Overview..................................................................................................................................... 4
Network Configuration Utility and Scripting.................................................................................................. 4
Scripting functionality ................................................................................................................................ 4
Scripting...................................................................................................................................... 5
Preliminary scripting information .................................................................................................................5
Script conversion....................................................................................................................................... 6
Scripting application (CQNICCMD) ............................................................................................................ 7
Command line syntax ...................................................................................................................... 7
Command line arguments................................................................................................................. 8
Command line examples .................................................................................................................. 8
Command line help .........................................................................................................................9
Configuration properties.............................................................................................................. 10
Adapter configuration properties............................................................................................................... 10
HP Multifunction adapter properties........................................................................................................... 10
Team configuration properties................................................................................................................... 12
XML data file.............................................................................................................................. 14
XML elements and typical adapter teaming script ........................................................................................14
Error handling and reporting........................................................................................................ 17
Error checking and completion code.......................................................................................................... 17
Acronyms and abbreviations........................................................................................................ 18
Index......................................................................................................................................... 19
Contents 3

Overview

Network Configuration Utility and Scripting

The HP Network Configuration Utility (NCU) enables configuration of network adapters and teams of network adapters. The scripting feature of the utility provides the ability to perform adapter configuration using a batch process.
This guide provides information about using the HP Network Adapter Scripting Utility to configure HP

Scripting functionality

adapters.
Scripting functionality provides the capability to configure a target system based on configuration information saved from a source server. The target system is not required to be identical to the source server. The configuration of the source server may not be duplicated in its entirety on the target system.
Both adapters and teams of adapters can be configured on the target system. When scripting is run, the adapter properties specified in the data file from the source server are used to modify the configuration of the adapters on the target system. Refer to " about running the scripting utility.
Preliminary scripting information (on page 5)" for details
Overview 4

Scripting

Preliminary scripting information

When using scripting to configure target systems, adapters are identified by their relative order in the system.
The relative order is determined by the following properties.
Slot and port order for adapters in non-HP BladeSystem configurations
Enclosure switch bay number and switch port order for adapters in HP BladeSystem configurations
Adapters embedded on the system board are assigned the lowest numbers, followed by adapters ordered by their slot or switch bay number with the lowest slot or switch bay number first. Multiport adapters are ordered by ascending port or switch port number within each slot.
Order of adapters on target systems
Adapters on the target system are configured to match the corresponding adapter number on the source server.
The first adapter on the target system is configured using data from the first adapter on the source
server.
The second adapter on the target system is configured using data from the second adapter on the
source server, and so on.
If the target system has more adapters than the source server, then the extra adapters retain their
current settings.
If the target system has fewer adapters than the source server, data for additional adapters on the
source server is ignored.
HP Multifunction adapters on target systems
To transfer iSCSI, TCP/IP Offload Engine (TOE), or Rec
ltifu
mu nction adapter, the following conditions apply:
n adapter must be located in the same relative position on the target server as on the
The multifunctio source server.
ameters are assigned to an adapter that does not support iSCSI, TOE, or
If these multifunction par RSS, they are ignored.
eive-Side Scaling (RSS) parameters on an HP
tion parameters but the parameters are not assigned, the
If an adapter supports these multifunc existing settings are left unchanged.
Microsoft Scalable Networking Pack (SNP) is required when enabling TOE or RSS and is included on systems running Windows Server 2003 (SP2) and Windows Server 2003 x64 (SP2). SNP also is supported, but not included, on systems running Windows Server 2003 (SP1) and Windows Server 2003 x64 (SP1). To enable TOE or RSS adapter functionality on a system running Windows Server 2003 (SP1) or Windows Server 2003 x64 (SP1), you must download SNP and required Microsof hotfixes and install them on the system. See the
Microsoft (http://www.microsoft.com) website to
Scripting 5
t
download the latest version of the Microsoft Windows Server 2003 Scalable Networking Pack (SNP) and required Microsoft Windows Server 2003 (SP1) hotfixes in article numbers 921136, 919948, and 923187 of the Microsoft Knowledge Base (KB). These Microsoft hotfixes are required only for
Windows Server 2003 (SP1) and Wind RSS support on PCIe gigabit server adapters RSS is supported on NC110T, NC360T, and NC364T PCIe gigabit server adapters running Microsoft
Scalable Networking Pack (SNP) on Windows Server 2003 (SP2) and Windows Server 2003 x64 (SP These adapters also support RSS running SNP on Windows Server 2003 (SP1) and Windows Server 2003 x64 (SP1); however, SNP is not included with SP1 and must be downloaded and installed along with required Microsoft hotfixes. See the latest version of the Microsoft Windows Server 2003 Scalable Networking Pack (SNP) and required Microsoft Windows Server 2003 (SP1) hotfixes in article numbers 921136, 919948, and 923187 of t Microsoft Knowledge Base (KB). These Micros (SP1) and Windows Server 2003 x64 (SP1).
tr
To ansfer the RSS parameter on one of these adapters, the following conditions apply:
pter must be located in the same relative position on the target server as on the source
The ada
server.
ows Server 2003 x64 (SP1).
Microsoft (http://www.microsoft.com) website to download
oft hotfixes are required only for Windows Server 2003
the
If the RSS parameter is assigned to an adapter that does not support RSS, it is ignored.
2).
he
ports the RSS parameter but the parameter is not assigned, the existing settings are
If an adapter sup
left unchanged. Teams on target systems The target system is configured with the same number of teams that were present on the source server.
on
Teams are created on the target system consisting of the same relative adapters that were teamed
the source server. For example, if adapters 3 and 5 were teamed on the source server, then tha
teaming
system.
In general, the adapters on the team on the target system do not have to be the same type of
adapters that were teamed on the source server. However, some adapters cannot be teamed an
an attempt is made to form a team with invalid combinations of adapters an error occurs. For
example, teams with different speed capabilities cannot be teamed on a load balancing team.
An error occurs in the configuration if the adapters forming the team on the source server are not
present on the target system. For example, if adapters 3 and 5 are teamed on the source server, but
the target system has only four adapters, an error is reported and the configuration is not applied.
d from
When teams are configured on the target system, the team properties are set to the values rea
the data file for the corresponding team on the source server. Properties not specified in the data f
(and properties specified with invalid data values) are configured using their default settings.
information is saved in the data file, and adapters 3 and 5 are teamed on the target
t
d if
ile
If no teams are configured on the source server, no teaming information is written to the data file
and configuration of the
target system consists only of configuring individual adapters.
Scrip
t conversion
Scripts created with previous versions of the NCU are supported; however, HP recreate the script using the latest version of the NCU. Several oper NCU versions 7.7x and earlier have changed and are converted as follows:
ating modes in scripts generated with
recommends that you
Scripting 6
Loading...
+ 13 hidden pages