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. Intel, Pentium, and Itanium are trademarks
or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The
Open Group.
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.
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 "Preliminary scripting information (on page 5)" for details
about running the scripting utility.
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 Receive-Side Scaling (RSS) parameters on an HP
multifunction adapter, 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, TOE, or
RSS, they are ignored.
•
If an adapter supports these multifunction parameters but the parameters are not assigned, the
existing settings are left unchanged.
Microsoft Scalable Networking Pack (SNP) is required when enabling TOE or RSS. For systems
running Windows Server 2003 (SP1) or Windows Server 2003 x64 (SP1), you must upgrade to
Windows Server 2003 Service Pack 2.
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
Scripting 5
intermediate drivers. Download article number KB92222 from the Microsoft
(http://www.microsoft.com) website for more information.
RSS support on PCIe gigabit server adapters
RSS is supported on NC110T, NC360T, and NC364T PCIe gigabit server adapters. Microsoft Scalable
Networking Pack (SNP) is required. For systems running Windows Server 2003 (SP1) or Windows Server
2003 x64 (SP1), you must upgrade to Windows Server 2003 Service Pack 2.
To transfer the RSS parameter on one of these adapters, the following conditions apply:
•
The adapter must be located in the same relative position on the target server as on the source
server.
•
If the RSS parameter is assigned to an adapter that does not support RSS, it is ignored.
•
If an adapter supports the RSS parameter but the parameter is not assigned, the existing settings are
left unchanged.
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.
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
Scripting 6
•
g
Windows Server 2008 x64 Editions
•
Windows Server 2003
•
Windows Server 2003 x64 Editions
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 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), refer to the documentation included
with SSST. The SSST can be downloaded from http://www.hp.com/servers/proliantessentials
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 confi
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.
uration option causes the source server configuration to be saved. The name of
Scripting 7
Loading...
+ 15 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.