HP Integrity Servers with Microsoft® Windows Server™ 2003 and Windows Server™ 2008 HP Networking Utilities User's Guide HP Part Number: 5992-4447 Published: April 2008
Legal Notices 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. The information contained herein is subject to change without notice.
Table of Contents About This Document.........................................................................................................7 Intended Audience.................................................................................................................................7 New and Changed Information in This Edition.....................................................................................7 Document Organization.....................................................................
List of Tables 1-1 2-1 SetLACState command line arguments......................................................................................9 cqniccmd command-line arguments...........................................................................................
About This Document This document describes some of the networking tools supported on HP Integrity servers running Microsoft® Windows® Server 2003 and Windows® Server 2008. The document printing date and part number indicate the document’s current edition. The printing date changes when a new edition is printed. Minor changes may be made at reprint without changing the printing date. The document part number changes when extensive changes are made.
A key sequence. A sequence such as Ctrl+x indicates that you must hold down the key labeled Ctrl while you press another key or mouse button. The contents are optional in command line syntax. If the contents are a list separated by |, you must choose one of the items. The contents are required in command line syntax. If the contents are a list separated by |, you must choose one of the items. The preceding element can be repeated an arbitrary number of times. Indicates the continuation of a code example.
1 SetLACState Utility If a server contains more than one server adapter, and at least one of those adapters is not connected, the server can display as failed on some network management consoles. SNMP traps can also be triggered. Use the SetLACState utility (SetLACState) to disable the Local Area Connection containing the unused adapter. This stops the server from displaying it as failed, and prevents undesired SNMP traps and error messages.
Both of these commands disable Local Area Connection 2. NOTE: Specifying enable for a connection that is already enabled or disable for a connection that is already disabled, does not generate an error.
2 Network Adapter Scripting Utility Use the Network Configuration Utility to configure network adapters (NICs) and teams of network adapters. The utility’s scripting feature lets you do this using a batch process. The scripting functionality also lets you configure target systems based on configuration information saved from a source server. When scripting runs, it uses the NIC properties specified in the data file from the source server to modify the configuration of the NICs on the target system.
• 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, then no teaming information is written to the data file, and configuration of the target system consists of configuring individual NICs only.
NOTE: If you want to use this tool in combination with the Smart Setup Scripting Toolkit (SSSTK), see the SSSTK documentation found on your Smart Setup CD. Command-line syntax Use the following format at the command line: cqniccmd [/F] [/C] [/D] [/L] [/P] [/S] [/?] NOTE: You can specify only one of the following configuration options at a time: /S, /D, /C, or /P You can use the /L option with any of the configuration options.
Example 2: /D cqniccmd /D Example 3: /C cqniccmd /Cc:\HP\teamcfg.xml cqniccmd /C c:\HP\teamcfg.xml cqniccmd /C”c:\HP\teamcfg.xml” Example 4: /P cqniccmd /Pc:\HP\teamcfg.xml cqniccmd /P c:\HP\teamcfg.xml cqniccmd /P”c:\HP\teamcfg.xml” Example 5: /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.
• • • VlanID — Specifies the VLAN identifier value for the device. VlanName — Specifies the descriptive name for the VLAN ID. Every VLAN must have a name assigned to it. Duplicate names are allowed if you want to use the same names for different VLAN IDs. NetworkAddress — Is written only for NICs that are not teamed. It allows the burned-in address to be overridden with a locally administered address.
— — — — — • • • • • • • • • • • • • 16 Community Probe IP Address, Community Probe MAC Address, and Use Default fields are used. EchoNodeProbeIPAddress — Determines the IP address to which the echo node responds. This is a reserved address that all teams on a subnet can use. This must be a valid unicast IP address and is enforced by scripting. This field is used only when both Active Path and Community Address ARP response mechanism are selected.
NOTE: RSS is supported on systems running Windows Server 2008 only. XML data file The XML data file contains the configuration properties for NICs and teams and consists of the following XML elements: • • • • — Brackets the entire data file and is required — Defines NIC properties — Defines teams and their properties — Defines VLANs and their properties The relnics attribute of the element lists the NICs to be configured on the team.
--> -->
When you run cqniccmd from a command line or a Windows command file, a completion code is written as an error-level code to both a log file and the screen. The Windows command file can use this error code to determine how to proceed. The error level codes are as follows: • Successful start of the action returns an error level zero (0). • Nonfatal errors return error-level one (1). • An invalid log file returns error-level two (2). • Other fatal errors return error-level three (3) or greater.
