Windows NT4 Network Adapter Scripting User Guide May 2003 (First Edition) Part Number 334274-00A
© 2002, 2003 Hewlett-Packard Development Company, L.P. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the U.S. and other countries. Intel, Pentium, and Itanium are trademarks of Intel Corporation in the U.S. and other countries. UNIX is a trademark of The Open Group in the U.S. and other countries. Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein.
Contents Abstract ............................................................................................................................... 5 Audience Assumptions...................................................................................................... 5 Overview.............................................................................................................................. 5 Introduction.........................................................................................
Abstract This guide provides information about the scripting feature of the HP Network Teaming and Configuration Utility for Microsoft Windows NT4. Audience Assumptions This guide is for the person who administers, configures and troubleshoots networks. HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards in products with hazardous energy levels.
Example 1: Assume that the source server (A) has four installed NICs, and the target server (B) has two installed and two uninstalled NICs, the relative NIC order would be as follows: Table 1: Relative NIC Order Server Relative Order Installation State Bus Slot A NIC 1 Installed 0 1 A NIC 2 Installed 1 2 A NIC 3 Installed 1 3 A NIC 4 Installed 1 4 B NIC 1 Installed 1 3 B NIC 2 Installed 1 4 B NIC 3 Uninstalled 0 1 B NIC 4 Uninstalled 1 2 Although the bus and slo
When teams are configured on the target system, the team properties will be 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) will be configured using their default settings. If no teams were configured on the source server, no teaming information will be written to the data file and configuration of the target system will consist only of configuring individual NICs.
/P The following options may be specified with any of the configuration options. /L /F /N Command Line Arguments /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 Compaq Network Teaming Configuration user interface.
/F This option causes all errors, including those errors normally treated as non-fatal errors, to be treated as fatal errors. This option applies only to the /C option. /N This option causes DHCP to be enabled on all NICs that are installed as a result of the configuration. This is intended to be used as part of an unattended installation since this keeps the TCP/IP settings property page from appearing after the binding engine runs. See the “Unattended Installation” section for more information.
1. Refer to Microsoft’s documentation regarding unattended setup, and follow the steps provided. 2. Revise UNATTEND.TXT to install the NICs in your system, and optionally to configure TCP/IP parameters. 3. Create a script file with the desired speed and duplex settings. HP recommends that you use the HP Network and Teaming Configuration Utility (CPQNTAC) to create this script file. Click the Save button on the main page of the utility to create TEAMCFG.
• PreferredPrimaryNIC—establishes the Initial Primary NIC for Manual, FailOnFault, and TransmitLoadBalancing or the Preferred Primary NIC for SmartSwitch. This configuration property is not applicable to Switch-Assisted Load Balancing teams. The value must be a non-zero integer that corresponds to one of the NICS on the team. • TeamNetworkAddress—establishes the MAC address for the NIC team. A null value will always be written to the XML data file.
Error Handling and Reporting Errors can occur for a variety of reasons including differences between the source and target system NICs or because of errors introduced by editing the XML data file. The software performs extensive error checking as the XML data file is read and processed. When invalid property values are detected, a WARNING error message will be written to a log file and configuration will continue with either default or existing values.
