                  ===========================
                  R E L E A S E    N O T E S
                  ===========================

          Broadcom Advanced Server Program (BASP) Driver 
                             for
           Windows XP (x86 and IA64), 2000, NT 4.0 and 
                    .NET beta (x86 and IA64)
                        Version 6.0.1

          Copyright (c) 2000-2003 Broadcom Corporation
                     All rights reserved.
                        Feb. 5, 2003

CHANGES in v6.0.1
-----------------
- 6827: User specified team name won't bind to virtual 
  adapter when creating BASP teams. The problem happened 
  when QoS is installed, the team/vlan name in 'Network 
  Connections' page is not set properly. The solution is 
  to get around the problem by setting the name later, 
  raising the 'Network Connections' page to foreground 
  and send 'F5' to force the 'Network Connections' page 
  to refresh after team/vlan name are set.

  =====================================================
  ATTENTION: Sometimes the 'Network Connections' did 
  not refresh properly. Users may need to manually hit 
  'F5' to refresh.
  =====================================================

CHANGES in v3.0.21
------------------
- Fixed the loss of connectivity problem when creating a 
  802.3ad team on Windows 2003 Server.

CHANGES in v3.0.20
------------------
- Fixed the binding problem of QoS packet scheduler to the
  BASP virtual adapter. 

CHANGES in v3.0.19
------------------
- 6073: Unable to unbind protocol when BASP is installed.

CHANGES in v3.0.18
------------------
- 5484: Support Microsoft Network Load Balancing.

CHANGES in v3.0.17
------------------
- 5568: W2K BASP App can add a  turbo team into a BASP team.
- 5264: BASP v3.0.16 Should not be loaded in IA-64 system.


CHANGES in v3.0.16
------------------
- Changed to use differnt APIs to accomodate the new WHQL 
  requirements.
- Added support of additional Broadcom NetXtreme based NICs
  and LOMs.

CHANGES in v3.0.15
------------------
- Added support of additional Broadcom NetXtreme based NICs 
  and LOMs.

CHANGES in v3.0.14
------------------
- Added support of additional Broadcom NetXtreme based NICs 
  and LOMs.

CHANGES in v3.0.13
------------------
- Fixed Prod00004015: System bugcheck after created 802.3ad team
  on a .NET IA64 system.

CHANGES in v3.0.11
------------------
- Fixed Prod00003790: fails 2c_PMHibernate NDIS test on XP32.

CHANGES in v3.0.10
------------------
- Fixed Prod00003745: fails 1c_reset NDIS test on W2K.

CHANGES in v3.0.9
-----------------
- Fixed Prod00003665: fails 1c_reset NDIS test on XP32.

CHANGES in v3.0.8
-----------------
- Fixed Prod00003609: fails 1c_kernelcalls test.
- Fixed Prod00003666: fails to add multiple cards with identical 
  names into the teams.

CHANGES in v3.0.7
-----------------
- Fixed 2c_Simultaneous test script failure with BASP on XP32.

CHANGES in v3.0.6
-----------------
- Fixed Prod00003600: Windows XP Professional BASP teaming does 
  not WOL from ping

CHANGES in v3.0.5
-----------------
- Fixed Prod00003107: Load balancing does not occur on multiple
  hot-standby adapters.
- Fixed signability errors with INF files.

CHANGES in v3.0.4
-----------------
- Fixed few minor IEEE 802.3ad interoperability issues.

CHANGES in v3.0.3
-----------------
- Enhance event notification mechanism.
- Fixed system crash with the IEEE 802.3ad team in NT 4.0.
- Add Trouble-shooting section to document known issues.

CHANGES in v3.0.2
-----------------
- Fixed second port blocking problem in the IEEE 802.3ad team.

CHANGES in v3.0.1
-----------------
- Support IEEE 802.3ad link aggregation.

CHANGES in v2.0.6
-----------------
- Minor textual changes in INF and DLL.

CHANGES in v2.0.5
-----------------
- Fixed Prod00002106: System Crashes after Deleting Vlan with 
  ID 0 and another Vlan.

CHANGES in v2.0.4
-----------------
- Fixed Prod00001753: loss of static IP address problem when 
  disconnect all the NICs in a team and then only connect 
  the hot-standy NIC.
- Fixed Prod00001694: the BASP installer does not indicate the 
  if the BASP already installed.
- Fixed Prod00001779: BASP installation process is asking for 
  BASPXPI.EXE while running BASPI64I.EXE install program.

CHANGES in v2.0.3
-----------------
- Minor fix in installation and configuration GUI.

CHANGES in v2.0.2
-----------------
- Enhanced installation and configuration GUI.

CHANGES in v2.0.1
-----------------
- Updated teaming configuration.
- Improved error reporting when configuring more than 8 physical 
  NICs in a team.

CHANGES in v1.3.3
-----------------
- Fixed the driver update issue on NT 4.0. This issue was introduced 
  by v1.3.2.

CHANGES in v1.3.2
-----------------
- Improved the reset operation on the virtual miniport instances.

CHANGES in v1.3.1
-----------------
- Added support of IA-64 version of Windows.NET Beta 2. 

CHANGES in v1.3.0
-----------------
- Improved Windows 2000 userability by reducing traffic interruption in
  reconfiguring the team. In case of HotSwap, users can simply remove the
  adapter without reconfiguring the team if the replacement adapter carry the
  plug and play ID and the replaced adapter will not plug into network again.
  In case of HotRemove, users can remove the adapter without changing team
  configuration if the removed adapter will not plug into network. Team
  configuration will automatically adjusted when team configuration software
  launched.

CHANGES in v1.2.11
------------------
- Fix: error in re-installing BASP for Windows 2000. 
  In version 1.2.10, the first time installation works fine without 
  any error. However, if the BASP is removed and then re-installed again,
  a message box will be poped up during installation and display
  following message:
		"Unknown Installation Error". 
  Despite this message, BASP is still installed properly. To configure 
  the teaming, the user is required to manually bring up the BASP 
  configuration dialog.

- Fix: removal of a NIC from a Generic Trunking team may result duplicated 
  MAC addresses on a network.

CHANGES in v1.2.10
------------------
- Fix: unable to resume from hibernation on Windows 2000.

CHANGES in v1.2.9
-----------------
- Fix the failure in re-enabling the virtual miniport instances on 
  Windows 2000.

CHANGES in v1.2.8
-----------------
- Fix: loss of network connectivity when performance monitor is monitoring
  VLAN network segment.

CHANGES in v1.2.7
-----------------
- Improved SNMP trap support in the BASP driver.

CHANGES in v1.2.6
-----------------
- Fix: Individual adapters maintain team MAC address after a FEC/GEC team
  is removed on Windows 2000. [0798]
- Fix: Description on virtual adapter is shown incorrectly when running
  ipconfig /all on Windows NT 4.0. [0803]

CHANGES in v1.2.5
-----------------
- Fix: BASP W2K configuration GUI allows up to 39 characters for a team name.
  [0795].
- Fix: BASP W2K configuration GUI is updated to allow all 64 VLANs properly
  configured and functional. [0780]

CHANGES in v1.2.4
-----------------
- Fix: Intermitten recovery failure with fiber network adapters. [0093]

CHANGES in v1.2.3
-----------------
- Fix W2K INF files to pass signability test.

CHANGES in v1.2.2
-----------------
- BASP is enhanced to work better with multiple protocols. [0608], [0671]
- Fix: system bugcheck when NetXray is executed. [0305]

CHANGES in v1.2.1
-----------------
- Added support of SNMP trap in the BASP driver.
- Fix: Installing both BASP and PPTP on NT 4.0 causes "Exception error". 
  [0573]
- Rename the driver and DLLs files with BASP prefix. [0559], [0557], [0550]
- Minor changes in configuration GUI dialog. [0529], [0250]
- New upgrade procedure for Windows 2000: [0050], [0040]
  BASP in W2k can not be updated as the 'Description' section. Users need to
  save the original configuration through the driver configuration page,
  uninstall BASP, reboot machine, install new BASP and restore the origial
  team configuration.

  There are two new buttons added to the configuration GUI. One is to save
  configuration and the other is to restore configuration previously saved.
  There are some limitations/rules for the upgrade procedure.

  1. The protocol related information like IP address will not be saved and
  restored. users need to reconfigured again after teams restored.

  2. The physical NICs on the system should not be changed during the upgrade
  procedure. If any NIC can not matched during restoration, the NIC will be
  dropped.

  3. If any team configuration can not be parsed, the restoration procedeure
  will be aborted.

  The format of the saved configuration is as following:
  a. The team configuration key word 'Load Balance Team Configuration' has to
  be at the start of a line followed by 0x0D and 0x0A (line break).

  b. Next line should contain the key word 'Team Name : ' followed by the team
  name which followed by  0x0D and 0x0A. Note that the spaces in the key word
  are expected and this rule will apply to other key words too. Team name can
  not be empty.

  c. Next line should contain key word 'Team type : ' followed by team type.
  The supported team types are 'Smart Load Balance and Fail Over' and 'Generic
  Trunking (FEC/ GEC)'. Team type will be followed 0x0D and 0x0A. Team type
  can not be empty.

  d. Next line should contain key word 'Load Balance Member : ' or 'Stand By
  Member : ' followed by the NIC name. NIC name has to match a NIC on the
  system, otherwise it will be dropped. NIC name will be followed by 0x0D and
  0x0A.

  e. Next line should either repeat the same format as description for team
  member/stand by NIC or 0x0D 0x0A to end the team member/stand by section.

  f. After team member/stand by section, next line should contain key word
  'VLAN Member : ' followed by VLAN name or  0x0D 0x0A if the team does not
  have VLAN configured. If VLAN name exists, it should be ended by 0x0D 0x0A.

  g. Next line should contain key word 'VLAN ID : ' followed by VLAN tag (a
  number) or 0 if no VLAN configured. the line should be ended by 0x0D 0x0A.

  h. Next line should be the beginning of another VLAN confuration (with key  
  word 'VLAN Member : ') or 0x0D 0x0A to end the VLAN configuration.

  i. Next line should be the beginning of another team configuration (with key
  word 'Team Name : ') or 0x0D 0x0A to end 'Load Balance Team Configuration'
  section.

  4. All team configuration rules will apply to the parsed configuration. Any
  disqualified team configuration will be dropped. Users should always check
  the parsed configuration and modify if they want.

  5. If no valid team configuration parsed, the original configuration should
  remain.


CHANGES in v1.1.10
------------------
- Fix: Unnecessary dialog box in team configuration. [0443]

CHANGES in v1.1.9
-----------------
- New feature: Support protocol independent failover on Broadcom 5700 only 
  team. For team which contains not only Broadcom 5700 adapters, there is
  still IP protocol failover as existed in previous release. No user
  configuration is required to activate this feature.
- Fix: System crash when primary adapter is either disabled (on W2K) or
  removed (on NT 4.0 and W2K), AND after system reboots. [0046], [0098],
  [0106], [0120].
- Fix: Netmon stops capturing after disconnect the cable of the primary NIC.
  [0053].
- Fix: Not all 64 VLAN are working. [0245], [0269]

CHANGES in v1.1.8
-----------------
- Fix: Update the BASF driver with older version caused error. [0096]
- Fix: FEC/GEC Property dialog does not show MAC address after reboot. [0270]
- Fix: The standby adapter of FEC/GEC team receives inbound traffic from
  switch. [0297]
- Fix: VLANs are not functional with BCM5700 A1 boards. [0298]
- Fix: Failover does not occur to hot-standby adpater after all load-balancing
  adapters are removed and system reboots. [0046], [0098], [0106], [0120]
- Fix: Recovery does not occur to load-balancing adapters when there is hot-
  standby adapter in the team. [0055], [0093]
- Fix: System crash when NetXRay is run. [0305]

CHANGES in v1.1.7
-----------------
- Fix: Unable to configure a FEC/GEC team with Tigon 2 and third party
  adapters.
- Fix: Grammatical error of the message displayed during FEC/GEC team 
  configuration.

CHANGES in v1.1.6
-----------------
- Various fixes to address UI, installation and software update issues.
- Support up to 64 VLAN per team.

CHANGES in v1.1.5
-----------------
- Fix: NT 4.0 bugchecks with multiple Tigon 2 adapters on a Multi-Processor 
  system.

CHANGES in v1.1.4
-----------------
- Fix: BASF NT 4.0 driver bugchecks with multiple network adapters in a
  team during system boot.

CHANGES in v1.1.3
-----------------
- Added 15 VLAN support per team.
- Added Generic Trunking/FEC/GEC load balancing support.
- Fixed a problem in distributing traffic to the network adapters that
  recover from link loss.

CHANGES DETAILS in v1.1.3
-------------------------
- VLAN
  Starting from this release (v1.1.3), VLAN support is added to BASF 
  driver. In each team, up to 15 VLAN can be added. Each added VLAN
  will result in a virtual adapter appearing in the protocol stack.
  In the case of TCP/IP, each VLAN corresponds to a network interface.
  
  VLAN support is orthogonal to the existing load balancing and failover 
  features, which means customers who want VLAN will enjoy the same
  Smart Load Balancing <tm> and newly added Generic Trunking support.

  VLAN support is only available with following network adapters
  (1) BCM5700 gigabit adapter 
  (2) Alteon Tigon 2 gigabit adapter 
  
  VLAN addition will fail if an unlisted network adapter is added to 
  the team. 

- Generic Trunking/FEC/GEC
  In addition to the original switch-independent Smart Load Balancing
  algorithm, a switch dependent load balancing algorithm, Generic 
  Trunking or Cisco FEC/GEC compatible, is added. 
  
  To properly configuring Generic Trunking, an unique MAC address is 
  required. During Generic Trunking configuration, BASF will query 
  one of the network adapter in the team and present its MAC address 
  to the user for modification. The resultant MAC address will be 
  written to the NDIS "NetworkAddress" registry key of all network 
  adapters which belong to the team. A reboot is required to make 
  this change effective. However, since the NDIS "NetworkAddress"
  registry key support is not a mandatory feature of NDIS driver, 
  it is possible that some network adapters do not support. Most of
  the popular network adapters, as we verified, support this feature.
  When there is any question, please consult the corresponding
  network adapter vendors for details.

  Generic Trunking also REQUIRES network switches to support Cisco 
  FEC/GEC and to be PROPERLY configured. Consult the switch documentation
  for setting up trunking.
  

TROUBLE SHOOTING SECTION
------------------------
(1) 802.3ad team member links disconnect and reconnect continuously when
connects to the HP2524 switch.

  This is a 3rd party issue.  It is seen only when configuring an 802.3ad 
  team with greater than 2 members on the server and connecting an HP2524 
  switch, with lacp enabled as passive or active. The HP switch will show 
  an lacp channel being brought up successfully with only 2 members.  
  All other member's links will disconnect and reconnect. This does not occur 
  with a Cisco Catalyst 6500.
