                  ===========================
                  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, IA64 and AMD64)

          Copyright (c) 2000-2006 Broadcom Corporation
                     All rights reserved.

Version 6.1.24 September 7, 2006
--------------------------------
   Fixes:
   ======
   1. Problem: CQ22837: Multicast Filtering of the Standby Adapter Should Extend
               to Multi-Vendor Teams.
   
      Cause:   Multicast/broadcast frame filtering was only enabled on teams
               supporting advanced failover. Teams only support advanced
               failover only when all miniport drivers in the team support the
               Broadcom NIC Extensions (BNICE) interface. Since other vendor's
               miniport drivers don't support BNICE, Basp disables advanced
               failover and hence multicast filtering was also disabled when
               other vendors NICs were in the team.
                
      Change:  The fix was to assign one primary NIC in a team as the multicast
               NIC. The multicast NIC is the only NIC allowed to accept
               multicast frames; multicast frames will be filtered (dropped) on
               all other NICs in the team. If the multicast NIC fails (link
               loss, disabled, etc.), another primary NIC in the team is
               selected as the multicast NIC. If there are no primary NICs
               available, then a secondary NIC is selected. If a secondary NIC
               is the multicast NIC and a primary becomes available, then the
               new primary becomes the multicast NIC.
                
      Impact:  Multi-vendor teams should now only indicate one copy of
               multicast frame up to the stack, whereas previously, a copy of
               the multicast frame would be indicated by each NIC in the team.
      
               Also, any NIC in a team of Broadcom only NICs may be assigned to
               receive multicast frames. Previously, the NIC assigned as the
               current primary NIC (the one with the team's MAC address) would

   2. Problem: CQ25241: Failover not working properly on 5704-based blade [when
               running Microsoft Virtual Server]

      Cause:   Each virtual machine is assigned a new MAC address when it's
               created. The VM is bound to Basp and will use this address when
               sending and receiving data through BASP. 

               When a failover event occurs, Basp sends a CTP frame to notify
               the switch that the team's MAC address is now connected to
               another port on the switch. All frames sent to Basp's team
               address are now forwarded through the new port. 

               Since no CTP was sent using the VM's MAC address, it remains
               associated with disconnected switch port. This prevents all
               frames sent to the VM from reaching it until a frame is sent from
               the VM that causes the switch to reassociate its MAC address with
               the new port.
             
       Change: Basp now snoops the MAC source address in the ethernet header of
               all ARP frames it transmits, and caches all the source MAC
               addresses it sees in an interal cache. Using the cache, Basp now
               sends a CTP frame for each entry in the cache when a failover
               event occurs.
                                
      Impact:  Basp supports MSVS only on teams that have one primary and one
               secondary nic. Basp supports a maximum of 32 virtual machines.
               Basp requires each VM to send an ARP request or reply frame at
               least once before the first failover.

 Version 6.1.23 July 10, 2006
----------------------------
   Fixes:
   ======
   1. Problem: CQ25558: Bugcheck encountered while running 1c_InitTime NDIS
               test script on SLB team

      Cause:   Basp was trying to send a frame using a NIC that had just been
               un-bound from the team.
      
      Change:  Basp now checks if the NIC is bound and ready before sending 
               frames that are generated internally.
      
      Impact:  This bug has been in basp for a long time, but was only
               uncovered by change 1. in version 6.2.12. This problem only
               occurs when a team with more than one NIC is deleted using
               basp v6.2.12.

Version 6.1.22 June 23, 2006
----------------------------
   Fixes:
   ======
   1. Problem: CQ24182: Groucho: After BASP SLB team fail-over, remote ping
               takes several minutes to resume

      Cause:   When failing back to the primary adapter because the link status
               has changed from down to up, basp sends CTP frames to notify
               neighboring and downstream switches that primary adpater has
               switched ports. Some switches (in this case the ESM) will
               indicate the link is up before they are able to accept or pass
               traffic when first powering up, causing them to miss the CTP
               frame and not detect that the primary MAC address has switched
               ports. Once the switch has finished booting, it does not forward
               traffic to the primary adapter until a packet is sent on the
               primary adapter to a remote station.

      Change:  Basp was modified to send a CTP frames every five seconds for a
               period of 135 seconds when the primary NIC changes. This gives
               switches sufficent time to initialize and begin accepting
               traffic, and correctly detect which port the primary is connected
               to. 

      Impact:  This change impacts teams with two Broadcom NICS configured has a
               primary and secondary and a failback occurs when a switch basp is
               connected to is powered up. Note that this problem does not occur
               when LiveLink is enabled.

 Version 6.1.21 April 7, 2006
-----------------------------
   Fixes:
   ======
   1. Problem: CQ23272: Unable to ping SLB team after disabling
               one adapter in team.

      Cause:   When there are multiple primary adapters in a team only one of
               the primary adapters is allowed to accept broadcast or multicast
               packets. All other primary adapters in the team filter these
               packets to prevent the virtual adapter from indicating multiple
               copies of these packets to the protocol stack. If the NIC
               responsible for indicating broadcast packets is fails or is
               disabled, another NIC in the team must be reconfigured to
               indicate broadcast packets (such as ARP frames).

               There was a bug in the driver where the NIC responsible for
               indicating broadcast packets was not enabling another NIC in the
               team to indicated broadcast packets when it was disabled.

      Change:  Modified the driver to give the responsibility of indicating 
               broadcast or multicast packets to the protocol stack to another
               NIC in the team that has a valid link.  

      Impact:  This fix applies to all OS's supported by Basp. 

   2. Problem: CQ24182: Groucho: After BASP SLB team fail-over, remote ping
               takes several minutes to resume

      Cause:   Basp was modified to not transmit an ARP frame when there is a
	       single active NIC in the team. This change was made to fix the
	       problem described in CQ13112. Not sending the ARP causes some
	       switches to not immediately detect when the primary has changed
	       from one NIC to another.

      Change:  Basp was changed to send a CTP frame when the primary NIC changes
               changes and the team is configured with a single primary and
               single secondary NIC. Sending a CTP frame instead of an ARP
               frame, fixes both this problem and CQ13112.

      Impact:  This change only impacts teams that are configured with two
               Broadcom NICs, 1 as the primary and 1 as the secondary. This
               change does not apply to other teaming configurations or to a
               multi-vendor team.

Version 6.1.20 Jan 19, 2006
---------------------------------
   Fixes:
   ======
   1. Problem:
              CQ22826 :Driver Ver dates in incorrect format.
      Cause:
              Month in .inf should use two digits
      Change:
              Changed the .infs.
      Impact:
              None.

Version 6.1.19 Jan 17, 2006
---------------------------------
   Fixes:
   ======
   1. Problem:
              CQ22765:Teaming with 3rd party will not pass traffic to standby when 
              the primary link is broken.
      Cause:
              The load balancing algorithm must always run whenever there is a 
              non-broadcom NIC in the team. Otherwise, connection can be interrupted 
              during failover. The logic added to support MSFT Virtual Server should 
              not disable load balancing for the one standby/one active configuration 
              when there are non-broadcom NICs in the team. This error was corrected 
              once before, but crept back in the last version
      Change:
              Enable the load balancing algorithm whenever there is a non-broadcom
              NIC present in the team.
      Impact:
              This means MSFT Virtual Server is not supported with non-broadcom
              NICs.

   2. Problem:
              CQ14018, CQ 22622: The Basp intermediate driver indicates duplicate
              multicast packets to the OS.
      Cause:
              The previous Basp versions did not attempt to filter multicast
              packets the NICs in the team receive. This led to duplicate indication
              to the OS.
      Change:
              In this version, Basp only indicates multicast packets received on
              its primary NIC (For SLB teams, this is the NIC programmed with the 
              team's MAC address).
      Impact:
              This fix applies only to SLB teams, and the problem still exists when 
              there are non Broadcom NICs present in the SLB team.
              
Version 6.1.18 November 30, 2005
---------------------------------

   Fixes:
   ======
   1. Problem:
              CQ21470: Errors during failover on SLB teams.
              CQ22276: BASP: SLB-LoadBalance does not send out direct ARPs when 
                       adapter fails.
      Cause:
              Due to a bug in the Basp code, directed ARPs are not always sent.
              As a result, network connectivity can be lost for an extended
              period of time during failover.
      Change:
              There is optimization code in Basp which avoids sending directed ARPs
              when one was sent recently. But there are cases when the directed
              ARP must be sent reguardless of what was sent previously. In this 
              version, this optimization is disabled. 
      Impact:
              Duplicate ARP messages may be sent to hosts, which is harmless.

Version 6.1.17 October 13, 2005
---------------------------------

   Fixes:
   ======
   1. Problem:
              CQ14345 creating / deleting team  will cause BSOD when Driver Verifier is turned 
              on.
      Cause:
              Called passive level NDIS API at dispatch level.

      Change:
              Make the call at passive level as required.
      Impact:
              None.

Version 6.1.16 September 29, 2005
---------------------------------

   Fixes:
   ======
   1. Problem:
              CQ14219 Need to remove DbgPrint calls from BASP 6.1.15.
      Cause:
              One debug print was left in the code.

      Change:
              Removed the debug print.
      Impact:
              None.


Version 6.1.15 September 22, 2005
---------------------------------

   Fixes:
   ======
   1. Problem:
              CQ13809 SLB team (Intel NIC + 5708/5751) fails to pass traffic when adapter 
              is brought down. Fail over not working.
      Cause:
              The code added to support MSFT Virtual Server is causing this problem.
              The load balancing algorithm should execute for non advanced_failover teams, 
              even if there is only one active NIC in the team. Since NIC MAC addresses 
              are not changed for these teams, the packet must always be tweaked to contain 
              the intended source/destination MAC address.

      Change:
              Restored the old logic when a non Broadcom NIC is present in the team.
      Impact:
              MSFT Virtual Server is _not_ supported when there are non Broadcom NICs in 
              the team.


   2. Problem:
              CQ14068 using 3rd party adapter as standby in the team, clients no longer able 
              to connect after fail over.
      Cause:
              This problem is caused by a fix introduced back in July 2003 (CQ8153). 
              Basp caches information about IP conversations between the host (where Basp 
              is running) and remote computers. Code was added back then to clear this cache 
              
              when an IP address is being deleted on the host. Without this fix, customers 
              complained that Basp would continuously send ARPs about IP addresses no longer 
              active on the host. When the cache is cleared, Basp no longer sends directed 
              ARPs to remote hosts to redirect inbound traffic among the NICs in the team. 
 
              When the TCP/IP6 stack is loaded on the host, Basp receives unexpected 
              notifications that IP6 addresses are being removed and wrongly clears this cache 
              (I did not investigate why these notifications occurs since Basp does not support 
              IP6 yet). Clearing the cache in turn disables the code which sends ARP 
              notifications during failover. This introduces random failures to send these ARPs 
              when they are required.
      Change:
              To fix this problem, I enable the CQ8153 fix for IPV4 address removal notifications
              only
      Impact:
              None.


Version 6.1.14 September 13, 2005
---------------------------------

   Fixes:
   ======
   1. Problem:
              CQ13940 Basp does not block multicast packets.
      Cause:
              Packets received from standby adapter(s) (while assuming the standby role)
              are submitted to the OS. This causes packet duplication, and confuses the
              application layer.

      Change:
              Added code to filter packets received by the standby adapter(s). Packets from
              one of the stanby adapters is allowed through in failover mode.
      Impact:
              The problem reported still exists for teams with more than one
              active NIC. A better solution will be implemented in future
              Basp releases.



Version 6.1.13 August 30, 2005
------------------------------

   Fixes:
   ======
   1. Problem:
              CQ13246 References to Whistler in the driver properties.
      Cause:
              xp32 and xp64 drivers should have the same description.

      Change:
              xp32 and xp64 drivers now have the same description.
      Impact:
              None.

   Fixes:
   ======
   2. Problem:
              CQ13109 Probe retries counter in BACS 8.22 for Basp 6.1.1 does not
              reflect accurate probe retries.
      Cause:
              Previous fix does not work for all cases. Specifically, the probe
              retried counters now goes up and down.

      Change:
              Maintain a separate counter for probe missed, rather than calculate
              the number of probe missed by subtracting the number of probes received
              from the number of probe sent.
      Impact:
              None.

   Fixes:
   ======
   3. Problem:
              CQ13548 LSO support should also be enabled for an SLB (Auto Fallback
              Disabled).
      Cause:
              LSO processing was run for SLB teams only. The fix advertised in 6.1.12
              was not in the release.

      Change:
              Allow LSO processing for SLB (Auto Fallback Disabled) teams.
      Impact:
              None.

   Fixes:
   ======
   4. Problem:
              CQ13154 Dynamic ARP cache reset feature for LiveLink team member
              should be immediate.
      Cause:
              Previous fix for this problem broke LiveLink. Probe targets can no
              longer be pinged.

      Change:
              Forward ARP responses from the probe target to the OS. The previous fix
              broke this functionality.

      Impact:
              See 6.1.12.

Version 6.1.12 August 15, 2005
------------------------------

   Fixes:
   ======
   1. Problem:
              CQ13149 Add Basp failover compatibe with MSFT Virtual Server.
      Cause:
              MAC address fields are corrupted in all sent and received packets.
              Also, ARP cache entries are corrupted on the hosts.

      Change:
              When the team contains a single active NIC, Basp only performs
              fail over. All load balancing related processing is disabled.
      Impact:
              This only works when there is a single active (passing traffic)
              NIC in the team. Normal Basp behavior resumes as soon as there
              are more than one active NIC.

   Fixes:
   ======
   2. Problem:
              CQ13246 References to Whistler in the driver properties.
      Cause:
              There are reference to old Windows builds in the Basp codes.

      Change:
              Removed the stale references.
      Impact:
              None.

   Fixes:
   ======
   3. Problem:
              CQ13109 Probe retries counter in BACS 8.22 for Basp 6.1.1 does not
              reflect accurate probe retries.
      Cause:
              The counter should be checked against limits to make sure bogus values
              are not reported.  This could happen for example if a probe request
              generates multiple responses from a probe target.

      Change:
              Add code to clamp the counters to values greater than zero.
      Impact:
              None.

   Fixes:
   ======
   4. Problem:
              CQ13548 LSO support should also be enabled for an SLB (Auto Fallback
              Disabled).
      Cause:
              LSO processing was run for SLB teams only.

      Change:
              Allow LSO processing for SLB (Auto Fallback Disabled) teams.
      Impact:
              None.

   Fixes:
   ======
   5. Problem:
              CQ13154 Dynamic ARP cache reset feature for LiveLink team member
              should be immediate.
      Cause:
              In prior LiveLink implementations, the probe targets were managed
              with a single state machine per NIC instance. As a result, keeping track
              of the status of all probe targets became convoluted and difficult to
              extend.

      Change:
              In this implementation, each NIC instance dedicates a state machine to
              manage each probe target (for a maximum total of 4 state machines per NIC).

      Impact:
              The code changes to implement this feature are significant, so testing
              should be done accordingly.

   Fixes:
   ======
   6. Problem:
              CQ13490 Removing VLAN on port 1 of 5704C failed.
      Cause:
              The error message of concern is logged into the event log by design, and
              should not be removed. The error message is non fatal, and is merely the
              byproduct of the technique used to create VLAN type teams.

      Change:
              The error message severity is reduced to Warning.

      Impact:
              None.

   Fixes:
   ======
   7. Problem:
              Probe packets should have a user defined VLAN tag.
      Cause:
              In prior implementations, all LiveLink probe packets were untagged.

      Change:
              The user can optionally associate a VLAN tag to each probe packets. The
              tag is specified with a special (Basp private) key in the registry.

      Impact:
              The special registry key is an interim solution, in the future the tag
              will be modified with the BACS GUI.


   Fixes:
   ======
   8. Problem:
              Under some scenario, Basp may not indicate some packets to the OS.
      Cause:
              There is a coding error in the previous version. Some received packets
              are not submitted to the OS.

      Change:
              Submit all received packets to the OS.
      Impact:
              This bug fix was not documented when 6.1.12 was released. This
              entry in the readme.txt file has been added while releasing 6.1.18.


Version 6.1.11 June 9, 2005
------------------------------

   Fixes:
   ======
   1. Problem:
              CQ12393 BASP Poor performance throughput with BASP SLB.
      Cause:
              This features were advertised in 6.1.10 but were not included.

      Change:
              Added the following,
                 1) Batch receive indication to NDIS
                 2) Use NDIS 5.1 packet stacking on receive
      Impact:
              None.

   Fixes:
   ======
   2. Problem:
              CQ11590 The Link for a BASP Team Is Established Based on the Probe Interval Time in the
              LiveLink Configuration.
      Cause:
              The probe interval is used while determining the probe target mac addresses.

      Change:
              Use a fixed value of 1s while sending probes to resolve the probe target mac addresses.

      Impact:
              None.

   Enhancement:
   ===========

   1. Problem: OEM has requested the addition of link up/down statistics
               counters (see release 8.2 MRD).

      Change: Added the statistics counters.

      Impact: Requires BACS 8.2.2 or later.


Version 6.1.10 May 9, 2005
------------------------------

   Fixes:
   ======
   1. Problem:
              CQ12393 BASP Poor performance throughput with BASP SLB.
      Cause:
              Basp 6.0.x did not provide support for task offload.

      Change:
              The 8.2 MRD requires a Basp for Windows performance level comparable to Basp for Linux.
              This requirement is aready met in 6.1.x. This version contains additional enhancements
              to improve performance further in some configuration (chariot benchmarks collected on
              FSC-TX600 platform show a 30% improvement in performance when compared to 6.1.9). Basp
              6.1.9 in turn shows a 70% improvement in performance when compared to 6.0.12.
              The enhancements in this version are,
                 1) Batch receive indication to NDIS
                 2) Use NDIS 5.1 packet stacking on receive
      Impact:
              None.


Version 6.1.9 March 11, 2005
------------------------------

   Fixes:
   ======
   1. Problem:
              CQ12393 BASP SLB team send out directed unicast ARP contains old IP address.
              This is a a reincarnation of CQ8153.
      Cause:
              BASP caches the old IP address, then uses this information to send the directed arps.
              The fix was not applied to the IA64 architecture.

      Change:
              Trap IP address change notifications from the protocols, and use this info to flush
              BASP cache. Apply this fix to the IA64 and AMD64 as well.

      Impact:
              None.


Version 6.1.8 March 4, 2005
------------------------------

   Fixes:
   ======
   1. Problem:
              CQ12315 BASP AMD64 sending mismatched data while running
              2c_OffloadLargeSend test.
      Cause:
              5705 and later devices only support the unspecified and 802.3
              task offload encapsulation. Basp was advertising all encapsulations
              to the test suite.
      Change:
              Only advertise the two encapsulations supported by the 5705 and later
              chips.
      Impact:
              The 2c_OffloadLargeSend executes as it would with 5705 and later chips
              (the test terminates quickly).

Version 6.1.7 March 2, 2005
------------------------------

   Fixes:
   ======
   1. Problem:
              CQ12178 Running RAW UDP packet smaller than 40 bytes causes BSOD.
      Cause:
              The driver attempts to use a null mdl while scanning packets to
              transmit.

      Change:
              If a null mdl is seen, the packet is submitted to the default nic
              for transmit.

      Impact:
              None.


   2. Problem:
              CQ12250 Need symbol file for BASP AMD64.
      Cause:
              The driver was compiled with an old ddk.

      Change:
              The driver is recompiled with ddk 3790 build 1433.

      Impact:
              None.

Version 6.1.6 Dec 14, 2004
------------------------------

   Fixes:
   ======
   1. Problem:
              CQ11541 BSOD during disable/enable of primary team members.
      Cause:
              Uninitialized variable content is used in the Basp code. This problem
              was introduced in 6.1.x.

      Change:
              Initialized the variable properly.

      Impact:
              None.


   2. Problem:
              CQ11638 System hang during enable/disable if primary team members.
      Cause:
              Improper use of NDIS spinlocks can lead to hang condition when NICs
              are enabled/disabled.

      Change:
              Use the NDIS spinlock properly.

      Impact:
              None.


Version 6.1.5 Dec 7, 2004
------------------------------

   Fixes:
   ======
   1. Problem:
              CQ11544 After configuring LiveLink, the team stays disconnected.
      Cause:
              The interface change between the application and the driver was not
              implemented properly in the intermediate driver. In particular, the
              IP addresses byte ordering has been reversed in 6.1.4 and later.

      Change:
              Implemented the change properly.

      Impact:
              None.


Version 6.1.4 Dec 6, 2004
------------------------------

   Fixes:
   ======
   1. Problem:
              CQ11511 BSOD upon resuming from hibernate.
      Cause:
              A bug in the code causes Basp to report LSO supported when the machine
              boots, then reports LSO not supported when the machine resumes
              from hibernate. This causes inconsistencies within the IP stack and
              BSODs. These inconsistencies can also occur whitout suspending the
              machine.

      Change:
              Fixed the code to be consistent in reporting task offload features.

      Impact:
              None.

   2. Problem:
             The team configuration parameters (task offload and LiveLink) are not
             always read properly from the registry. Also added better protection
             against invalid parameters. There is no CQ entry for this issue.

      Change:
             Fixed the code to read the parameters properly.

      Impact:
             None.


   3. enhancement:
             The probe interval is now received in the unit of millisecond from the application.
             In prior basp versions, the units were seconds which limited the resolution.

      Change:
             The intermediate driver now receives its probe interval in milliseconds

      Impact:
             Requires BACS 7.7.2 or later.



Version 6.1.3 Nov 24, 2004
------------------------------
   Fixes:
   ======
   1. Problem:
              CQ11413 Team goes down with certain Live Link parameters.
      Cause:
              The team does not report link if the number of retries is set to 1.
              The code checking the number of retries is off by 1.

      Change:
              Fixed the code.

      Impact:
              None.


   2. Problem:
              CQ11403 Basp 6.1.2 .inf version info is incorrect.
      Cause:
              Released the wrong .inf.

      Change:
              Corrected the .inf.

      Impact:
              None.


   3. Problem:
              CQ11404 System gets blue screen while configuring team.
      Cause:
              Did not check the return value from one of the Ndis calls, and
              attempted to set the fields of a non existant NDIS packet. This
              bug was introduced while fixing CQ11388.

      Change:
              Fixed the code to check for NDIS return error code.

      Impact:
              None.


Version 6.1.2 Nov 19, 2004
------------------------------
   Fixes:
   ======
   1. Problem:
              CQ11388 BAsp 6.1.0 fails 2c_OffloadChecksum NDIS test script.
              The test also fails with Basp 6.1.1.
      Cause:
              Basp needs to propagate the extension fields of ndis packet on
              packet received. This extension contain the checksum info and is
              used by the HCT to verify that the NIC/miniport driver calculated
              checksums properly.

      Change:
              Propagate the extension fields on NDIS packet received.

      Impact:
              None.



Version 6.1.1 Nov 18, 2004
------------------------------
   Fixes:
   ======
   1. Problem:
              CQ11371:When we configure live link, the team stays disconnected.
      Cause:
              Logic error in the live link code. If the probe target is not
              resolved after the first broadcast, basp incorrectly sends all
              subsequent probes to the null MAC address.

      Change:
              Fixed the logic error.

      Impact:
              None.


   2. Problem:
              Task Offload is not working correctly (this bug is not in clearquest).
      Cause:
              Error in reading and decoding the team task offload capabilities in
              the registry.

      Change:
              The team task offload capabilities are now processed correctly.

      Impact:
              None.


Version 6.1.0 Nov 12, 2004
------------------------------
   Fixes:
   ======
   1. Problem:
              CQ10668:BASP Remove calls to MmMapLockedPage in win2k basp.
      Cause:
              6.2.11 only addressed winxp. This version addresses w2k and
              later.

      Change:
              Removed call for win2k and xp-64.

      Impact:
              No NT4.

   1. Enhancement:
              Support for Live Link

      Impact:
              New version of bmapi and control suite required. No NT4

   2. Enhancement:
              Support for task offload

      Impact:
              New version of bmapi and control suite required. No NT4


Version 6.0.11 July 12, 2004
------------------------------
   Fixes:
   ======
   1. Problem:
              CQ10564:BASP v6.0.10 fails 1c_SetMulticast and 2c_RecvMulticast NDIS Test.
      Cause:
              Error in the new multicast list handling code
              (off by one in max list size check).

      Change:
              Fixed the new multicast list handling code.

      Impact:
              None.

   2. Enhancement:
              Created single .infs and installation executables for win2k and winXP

      Impact:
              The win2k directory has been removed from this distribution. All the files
              for win2k are now in the xp32 directory.

Version 6.0.10 July 1, 2004
------------------------------
   Fixes:
   ======
   1. Problem:
              Multicast is not supported with VLANs.
      Cause:
              BASP maintains a single multicast list for the team.

      Change:
              A multicast list is assigned to each virtual NIC, the physical NIC is given
              the union of all virtual NIC multicast entries.

      Impact:
              None.


Version 6.0.9 Feb 4, 2004
------------------------------
   Fixes:
   ======
   1. Problem:
              CQ9254 Intermittent network failure. This problem was reported by several
              OEMs.
      Cause:
              BASP is running out of receive buffers and can no longer receive packets

      Change:
              Instruct the OS to return the receive buffers ASAP.

      Impact:
              None.

   Enhancement:
   ============
   1. Problem:
              Add support for AMD64.
      Change:
              AMD64 support added.

      Impact:
              None

Version 6.0.8 October 16, 2003
------------------------------
   Fixes:
   ======
   1. Problem:
              CQ8660 unable to pass traffic after secondary members loose link
              (auto fallback disable mode).

      Cause:
              With the new mode, BASP was reporting link down to the OS when it should
              not have.

      Change:
              Do not report link down to the OS if there are at least one NIC with link.

      Impact:
              None.

   2. Problem:
              CQ8659 BASP not reporting correct speed of team when a member fails
              (all modes).

      Cause:
              BASP is using the highest speed reported by the team members. A NIC with
              no link reports a speed of 1G. Note: this problem can be found in all
              versions prior to 6.0.8.

      Change:
              Only use the team members with link when reporting the speed. If all the
              NICs are down, report a don't care value of 100Mbs.

      Impact:
              Need to run all HCT tests to make sure there are no side effects

Version 6.0.7 October 13, 2003
-------------------------
   Enhancement:
   ============
   1. Problem:
              CQ6410 Provide ability to disable auto fallback when primary port recovers.
      Change:
              Implemented new auto fallback disable mode.

      Impact:
              The new mode is not supported in NT4


Version 6.0.6 September 26, 2003
-------------------------
   Fixes:
   =======
   1. Problem:
              CQ8523 BASP vlan tags don't work in NT4.

      Cause:
              This feature was broken in version 6.03 while adding support for
              802.1p. Some of the #ifdef to disable this new feature for NT4 are
              incorrect.


      Change:
              Fixed the #ifdefs


      Impact:
              None


Version 6.0.5 July 22, 2003
-------------------------
   Fixes:
   =======
   1. Problem:
              CQ8173 BASP 6.0.4 fails 1c_KernelCalls NDIS Test.

      Cause:
              Calls to DbgPrint() are not allowed for WHQL


      Change:
              Removed calls to DbgPrint()


      Impact:
              None

   2. Problem:
             CQ7847, Windows: Driver Verifier on BASP causes Blue Screen

      cause:
             This problem is due to a check detected by driver verifier, in
             which driver verifier ensures the "Cancel routine" is being zero
             before the request is completed. Having "cancel routine" un-zero
             does not affect functionality nor performance. It's a sanity
             type checking.

      Change:
             Ensure the "Cancel routine" is zero before completing the request.

      Impact:
             None


Version 6.0.4 July 9, 2003
-------------------------
   Fixes:
   =======
   1. Problem:
              BASP SLB team sends out directed unicast ARP containing old IP address (CQ8153)

      Cause:
              BASP caches the old IP address, then uses this information to send the directed arps.

      Change:
              Trap IP address change notifications from the protocols, and use this info to flush
              BASP cache.

      Impact:
              Does not work with NT4. Is not implemented for IA64.


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.
