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
ows Server 2003 x64 (SP1).
2).
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 Microsoft (
http://www.microsoft.com
) website to download
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
the
he
oft hotfixes are required only for Windows Server 2003
tr
•
pter must be located in the same relative position on the target server as on the source
•
ports the RSS parameter but the parameter is not assigned, the existing settings are
•
on
t
information is saved in the data file, and adapters 3 and 5 are teamed on the target
•
d if
•
•
d from
ile
•
If no teams are configured on the source server, no teaming information is written to the data file
target system consists only of configuring individual adapters.
Scrip
recommends that you
ating modes in scripts generated with
(SP1) and Windows Server 2003 x64 (SP1).
To ansfer the RSS parameter on one of these adapters, the following conditions apply:
The ada
server.
•
If the RSS parameter is assigned to an adapter that does not support RSS, it is ignored.
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.
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.
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.
and configuration of the
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:
Scripting 6
