HP BladeSystem Dual NC370i - Multifunction Network... User manual

HP ProLiant Network Adapter Scripting Utility
User Guide
Part Number 515635-003
September 2009 (Third Edition)

© Copyright 2008, 2009 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
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP
shall not be liable for technical or editorial errors or omissions contained herein.
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, and Windows Server are U.S. registered trademarks of Microsoft Corporation.
Intended audience
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 3
Contents
Overview..................................................................................................................................... 4
Network Configuration Utility and Scripting.................................................................................................. 4
Scripting functionality ................................................................................................................................ 4
Scripting...................................................................................................................................... 5
Preliminary scripting information ................................................................................................................. 5
Order of adapters on target systems .................................................................................................. 5
Multifunction parameters on target systems ......................................................................................... 5
Teams on target systems................................................................................................................... 6
Script conversion....................................................................................................................................... 8
Scripting application (CQNICCMD) ............................................................................................................ 8
Command line syntax ...................................................................................................................... 8
Command line arguments................................................................................................................. 9
Command line examples .................................................................................................................. 9
Configuration properties.............................................................................................................. 11
Adapter configuration properties for Windows Server 2008......................................................................... 11
Adapter configuration properties for Windows Server 2003......................................................................... 13
Team configuration properties................................................................................................................... 14
XML data file.............................................................................................................................. 16
XML elements and typical adapter teaming script ........................................................................................ 16
Error handling and reporting .................................................................................................................... 19
Error checking and completion code ................................................................................................ 19
Acronyms and abbreviations........................................................................................................ 20
Index......................................................................................................................................... 21

Overview 4
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
adapters.
Scripting functionality
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 (see "Preliminary scripting information (on page 5)" for details about
running the scripting utility).

Scripting 5
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.
Multifunction parameters on target systems
To transfer multifunction (TCP/IP Offload Engine and iSCSI) parameters the following conditions apply:
•The multifunction adapter must be located in the same relative position on the target server as on the
source server.
•If these multifunction parameters are assigned to an adapter that does not support iSCSI or TOE,
they are ignored.
•If an adapter supports multifunction parameters but the parameters are not assigned, the existing
settings are left unchanged.
•Some properties are not configurable if an adapter has FlexNIC enabled.
Multifunction adapter limitations
•For systems running Windows Server 2003 (SP1) or Windows Server 2003 x64 (SP1), you must
upgrade to Service Pack 2 or later.

Scripting 6
•TOE will not work with the following features enabled: Windows Firewall; Internet Protocol security
(IPsec); Internet Protocol Network Address Translation (IPNAT); third-party firewalls; and NDIS 5.1
intermediate drivers. Download article number KB912222
(http://support.microsoft.com/kb/912222/en-us) from the Microsoft website for more information.
•TOE and RSS are incompatible on NetXen adapters. If RSS is already enabled and then you enable
TOE, RSS is automatically disabled even though it may appear to be enabled. Likewise, if you
enable TOE after RSS, RSS becomes disabled.
•TOE is disabled system wide by default in the operating system. TOE must be enabled system-wide
for it to work on the adapter itself. To enable TOE in the Windows Server 2008 operating system,
execute the "netsh int tcp set global chimney=enabled" command.
•Some HP NC-Series NetXen adapters require a TOE license. See the NCDE Release Notes for
installation instructions and a list of adapters that require a TOE license.
•Some properties are not configurable if an adapter has FlexNIC enabled.
Teams on target systems
The target system is configured with the same number of teams that were present on the source server.
•Teams are created on the target system consisting of the same relative adapters that were teamed on
the source server. For example, if adapters 3 and 5 were teamed on the source server, then that
teaming information is saved in the data file, and adapters 3 and 5 are teamed on the target
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 and if
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.
•When teams are configured on the target system, the team properties are set to the values read from
the data file for the corresponding team on the source server. Properties not specified in the data file
(and properties specified with invalid data values) are configured using their default settings.
•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.
Teaming limitations
•Only the following team types are supported on FlexNIC-enabled NC522m adapters.
oNetwork Fault Tolerance (NFT)
oNetwork Fault Tolerance with Preference Order (NFT-PO)
oTransmit Load Balancing with Fault Tolerance (TLB)
oTransmit Load Balancing with Fault Tolerance and Preference Order (TLB-PO)
•The NCU supports two or more FlexNIC-enabled adapters on the same port to be members of the
same team.

Scripting 7
•Any changes to a teaming configuration that has an iSCSI-booted device present requires a system
reboot.
•In Transmit Load Balancing, Switch-assisted Load Balancing, and 802.3ad with Fault Tolerance
teams, the adapters must be capable of a common speed. If you try to add an adapter to one of
these existing team types and that adapter is not capable of a common speed with the other
adapters in the team then the team option is disabled.
•All server adapters in a team must be on the same broadcast domain.
•To ensure proper network functioning, be sure the protocol information for each teamed server
adapter is complete. Do not depend on a DHCP server to assign an IP Address as the results may be
undependable. Be sure that you have properly configured the protocols for the Virtual Miniport that
represents the team. To do this on Windows systems, go to Network Connections to select the Virtual
Miniport and then select File>Properties.
•If the properties of the server adapters are not supported by all team members, those properties may
be disabled for all the adapters in the team. The NCU displays a message listing the properties that
have been disabled.
TOE teaming limitations
The following are limitations for a TOE-enabled team:
•TOE and RSS teaming are not supported on Windows Server 2008 and Windows Server 2008 x64
in this release.
•For systems running Windows Server 2003 (SP1) or Windows Server 2003 x64 (SP1), you must
upgrade to Service Pack 2 or later.
•TOE teaming performance is reduced if a switch or network device is configured with the round
robin aggregation load balancing method. Configure the aggregation load balancing method on
the switch or network device to something else other than round robin and then re-start the team
(disable the team and enable the team for all VLANs).
•TOE will not work with the following features enabled: Windows Firewall; Internet Protocol security
(IPsec); Internet Protocol Network Address Translation (IPNAT); third-party firewalls; and NDIS 5.1
intermediate drivers. Download article number KB912222
(http://support.microsoft.com/kb/912222/en-us) from the Microsoft website for more information.
RSS teaming limitations
The following are limitations for a TOE-enabled team:
•TOE and RSS teaming are not supported on Windows Server 2008 and Windows Server 2008 x64
in this release.
•For systems running Windows Server 2003 (SP1) or Windows Server 2003 x64 (SP1), you must
upgrade to Service Pack 2 or later.
iSCSI teaming limitations
•The following team types are not supported for iSCSI-enabled adapters. Disable iSCSI on the
adapter or team before changing to any of the incompatible team types.
oAutomatic
o802.3ad Dynamic with Fault Tolerance
oSwitch-assisted Load Balancing with Fault Tolerance (SLB)
•HP NC-Series Intel adapters that have been iSCSI-booted do not support teaming.

Scripting 8
Script conversion
Scripts created with previous versions of the NCU are supported; however, HP recommends that you
recreate the script using the latest version of the NCU.
Scripting application (CQNICCMD)
CQNICCMD is a Windows utility that processes a network adapter configuration script file to duplicate
the adapter teaming configuration of a source ProLiant BL/ML/DL server on a target server.
This utility is supported on the following Windows operating systems:
•Windows Server 2008 SP2
•Windows Server 2008 R2
•Windows Server 2008
•Windows Server 2008 x64
•Windows Server 2003
•Windows Server 2003 x64
Run the utility from the command line in a Command Prompt window, from the Run option on the
Windows Start menu, or from a Windows command file. To execute the CQNICCMD utility from the
command line, the HP Network Configuration Utility (NCU) must be closed.
HP recommends that you use this application as part of the SmartStart Scripting Toolkit (SSST)
deployment. However, the application can be used outside of this environment. Follow these steps when
using the scripting application.
1. Configure adapter teaming on the source server.
2. Generate a script file on the source server by clicking Save in the HP NCU user interface or by
running CQNICCMD /S<filename> in the Command Line utility.
3. Modify the script file as necessary.
If you modify the script file, HP recommends that you run CQNICCMD/ P to check the syntax of the
modified file and check the log file for errors and warnings. The default location of the log file is
\cpqsystem\log\cpqteam.log on the system drive. The syntax of the /P option is cqniccmd
/p<filename>
4. Install the HP NCU on the target system.
5. Run the Command Line utility with the following syntax.
cqniccmd /c<filename>
6. Check the log file for errors and warnings. The default location of the log file is
\cpqsystem\log\cpqteam.log on the system drive.
For use of this utility with the SmartStart Scripting Toolkit (SSST), see the documentation included with
SSST, which can be downloaded from the HP website
(http://h18013.www1.hp.com/products/servers/management/toolkit/index.html).
Command line syntax
CQNICCMD [[F/] /C<filename>] [/D] [/L <filename>] [/P <filename>]
[/S<filename>] [/?]

Scripting 9
Only one of the following configuration options can be specified at a time:
/S
/D
/C
/P
The /L argument can be used with any of the configuration options. The /F argument can only be used
with the /C configuration option.
Command line arguments
Argument Description
/S This configuration option causes the source server configuration to be saved. The name of
the XML configuration data file must be specified and the path to the data file must exist.
This option is identical to saving the source server configuration by clicking Save in the
Network Teaming Configuration user interface.
/D This configuration option causes all teams on the target server to be dissolved, all VLANs
to be removed, and 802.1p/q Packet Tagging to be disabled for all adapters that had
no VLANs. No additional arguments are required or allowed with this option.
/C This configuration option applies the configuration specified in the data file to the target
system. An existing XML configuration data file must be specified following the target
switch. A space following the switch is optional. Any teams that exist on the target server
will be dissolved before the configuration is applied, all VLANs will be removed, and
802.1p/q Packet Tagging will be disabled.
/P This option is identical to the /C option, except that the configuration options are not
applied to the target system. This is useful for syntax checking the XML data file.
/L This option can be used to change the name and location of the cpqteam.log default log
file that is created in \cpqsystem\log on the system drive. The supplied path must exist.
An invalid log file name will cause the configuration to terminate with no changes. HP
recommends this option only in batch files.
/F This option causes all errors, including those errors normally treated as non-fatal errors, to
be treated as fatal errors. This argument can be used only with the /C option.
/? This option displays usage information.
Command line examples
/S
cqniccmd /Sc:\HP\teamcfg.xml
cqniccmd /S c:\HP\teamcfg.xml
cqniccmd /S"c:\HP\teamcfg.xml"
/D
cqniccmd /D
/C
cqniccmd /Cc:\HP\teamcfg.xml
cqniccmd /C c:\HP\teamcfg.xml
cqniccmd /C"c:\HP\teamcfg.xml"
/P
cqniccmd /Pc:\HP\teamcfg.xml
cqniccmd /P c:\HP\teamcfg.xml
cqniccmd /P"c:\HP\teamcfg.xml"

Scripting 10
/L
cqniccmd /Cc:\HP\teamcfg.xml /Lc:\HP\config.log
cqniccmd /C c:\HP\teamcfg.xml /L c:\HP\config.log
cqniccmd /C"c:\HP\teamcfg.xml" /L" c:\HP\config.log"
/F
cqniccmd /F /C c:\HP\teamcfg.xml