Allied Telesis AT-2973T User Manual
Chapter 11: Troubleshooting
148
When configuring a team of NetXtreme II network adapters on a Hyper-V
system, be aware of the following:
system, be aware of the following:
Create the team prior to binding the team to the Hyper-V virtual
network
network
Create a team only with an adapter that is not already assigned to a
Hyper-V virtual network.
Hyper-V virtual network.
A TOE-enabled team that is bound to a Hyper-V virtual network
reports TOE as an offload capability in BACS; however, TOE does not
work. This is a limitation of Hyper-V because this system does not
support TOE.
reports TOE as an offload capability in BACS; however, TOE does not
work. This is a limitation of Hyper-V because this system does not
support TOE.
In an IPv6 network, a team that supports Checksum Offload (CO) and
Large Send Offload (LSO) and is bound to a Hyper-V virtual network
reports CO and LSO as an offload capability in BACS. Also, in an IPv6
network, a team that supports CO or LSO and is bound to a Hyper-V
virtual network reports CO or LSO as an offload capability in BACS.
However, in both instances CO and LSO do not work. This is a
limitation of Hyper-V because this system does not support CO and
LSO in an IPv6 network.
Large Send Offload (LSO) and is bound to a Hyper-V virtual network
reports CO and LSO as an offload capability in BACS. Also, in an IPv6
network, a team that supports CO or LSO and is bound to a Hyper-V
virtual network reports CO or LSO as an offload capability in BACS.
However, in both instances CO and LSO do not work. This is a
limitation of Hyper-V because this system does not support CO and
LSO in an IPv6 network.
To successfully perform VLAN tagging for both the host (parent
partition) and the guest (child partition) with the BASP teaming
software, you must configure the team for tagging. Unlike VLAN
tagging with a single adapter, tagging cannot be managed by Hyper-V
when using BASP software.
partition) and the guest (child partition) with the BASP teaming
software, you must configure the team for tagging. Unlike VLAN
tagging with a single adapter, tagging cannot be managed by Hyper-V
when using BASP software.
Removing the
Device Drivers
Uninstall the Broadcom NetXtreme II device drivers from your system only
through the InstallShield wizard. Uninstalling the device drivers with
Device Manager or any other means may not provide a clean uninstall
which, in turn, may cause the system to become unstable. For information
on uninstalling Broadcom NetXtreme II device drivers, see “Removing the
Device Drivers” on page 97.
through the InstallShield wizard. Uninstalling the device drivers with
Device Manager or any other means may not provide a clean uninstall
which, in turn, may cause the system to become unstable. For information
on uninstalling Broadcom NetXtreme II device drivers, see “Removing the
Device Drivers” on page 97.
Upgrading from
Windows Server
2000 to Windows
Server 2003
When a Broadcom NetXtreme II adapter is installed in your system, Allied
Telesis recommends that you uninstall the adapter's driver before
performing an OS upgrade from the Windows Server 2000 Operating
System to the Windows Server 2003 Operating System. This ensures that
no errors are encountered in the installation of the Windows Server 2003
drivers for the NetXtreme II adapters. There are individual device drivers
for Windows Server 2000 and Windows Server 2003. As a result, you
must install the Windows Server 2003 drivers after the OS upgrade is
completed.
Telesis recommends that you uninstall the adapter's driver before
performing an OS upgrade from the Windows Server 2000 Operating
System to the Windows Server 2003 Operating System. This ensures that
no errors are encountered in the installation of the Windows Server 2003
drivers for the NetXtreme II adapters. There are individual device drivers
for Windows Server 2000 and Windows Server 2003. As a result, you
must install the Windows Server 2003 drivers after the OS upgrade is
completed.
Preparing an
Answer File
When creating an answer file for an unattended installation or for the
System Preparation Tool (Sysprep) utility, the following lines must be
included under the [Unattend] section:
System Preparation Tool (Sysprep) utility, the following lines must be
included under the [Unattend] section:
OemPreinstall=Yes
OemPnpDriversPath=Drivers\NIC
OemPnpDriversPath=Drivers\NIC