==========================
R E L E A S E N O T E S
==========================
Broadcom BASP Silent Configuration Program
Copyright (c) 2003-2007 Broadcom Corporation
All rights reserved.
April 11, 2007
History
=======
Version 6.1.9 (April 11, 2007)
----------------------------------
Enhancements:
=============
1. Request: CQ28514
Team to be created requires at least one Broadcom NIC.
Change:
Check if Broadcom NIC is included before creating a Team.
Impact:
Create Team functionality
2. Request: CQ28917
BaspSCfg document needs updating.
Change:
Both ReadMe.txt and BaspSCfg.pdf were updated with
information to preserve the Teaming Configuration.
Impact:
None
Fixes:
=====
1. Problem: CQ28508
BASPSCFG version is not displayed correctly.
Cause:
The version string was not updated.
Change:
The version string is updated to 6.1.9.
Impact:
BASPSCFG version is displayed correctly.
Version 6.1.8 (August 31, 2006)
----------------------------------
Enhancements:
=============
1. Request:
Add privilege for Windows Vista to run only under
Administrator privilege
Change:
Added privilege for Windows Vista to run only under
administrator
Impact:
Non-admin user unable to run this application
Version 6.1.7 (July 26, 2006)
----------------------------------
Fixes:
=====
1. Problem: CQ25705
BaspSCfg flags error when restore 8 nic memeber SLB team.
Cause:
Previous version returned an error when total number of
physical adapters in the team was >= 8.
Change:
Corrected the related function to return an error only
when the total number of physical adapters in the team
is > 8.
Impact:
The maximum number of physical adapters allowed for a
team is 8.
Version 6.1.6 (April 25, 2006)
----------------------------------
Enhancements:
=============
1. Request:
To add live link VLAN ID to the team configuration
for live link.
Change:
Added optional parameter -livelink_vid to the team
configuration for live link.
Impact:
Team configuration for live link.
Fixes:
=====
1. Problem: CQ23296
BaspSCfg did not allow duplicate DNS and WINS IP
addresses.
Cause:
Previous version required all IPs to be unique
within each team configuration.
Change:
Modified internal algorithm to relax the IP address
checking.
Impact:
DNS and WINS IPs are allowed to be the same.
2. Problem: CQ23874
BaspSCfg failed to add an INTELL NIC for teaming.
Cause:
Wrong handle was passed to BmapiGetPhyNic().
Change:
Fixed the coding error.
Impact:
All supported NICs including non-broadcom NICs are
qualified to be in the SLB team without VLAN.
3. Problem: CQ24344
Windows error dialog box was seen while running BaspSCfg
from command line without parameters.
Cause:
This was caused by a NULL pointer along the program flow.
Change:
Fixed the coding error.
Impact:
Running BaspSCfg from command line without parameters should
not cause the above problem.
Version 6.1.5 (September 22, 2005)
----------------------------------
Enhancements:
=============
1. Request:
To support the teton based adapters in the teaming
configuration.
Change:
Added support for the teton based adapters as
requested.
Impact:
The teton based adapters are allowed in the teaming
configuration.
2. Request:
To require administrator privilege for changing the
teaming configuration.
Change:
Only allow users with administrator privilege to create,
change/remove the team configurations.
Impact:
The administrator privilege is required for changing
the team configurations but not required for the '-save'
and '-help' commands.
Version 6.1.4 (May 11, 2005)
----------------------------------
Fixes:
=====
1. Problem: CQ12888
BaspSCfg.exe properties showed incorrect file
version.
Cause:
FILEVERSION and PRODUCTVERSION in BaspSCfg.rc
were not updated to include the correct release
number and the copyright label.
Change:
Updated the required fields in BaspSCfg.rc.
Impact:
BaspSCfg.exe properties should show correct
version and copyright information.
Version 6.1.3 (May 6, 2005)
----------------------------------
Fixes:
=====
1. Problem: CQ12872
BACS does not show -freq entered by BaspSCfg.
Cause:
BaspSCfg v6.1.2 accepts the input units for -freq
and -retry_freq in seconds while BMAPI expects
them in milliseconds.
Change:
Changed input units for -freq and -retry_freq from
seconds to milliseconds.
Impact:
-freq and -retry_freq parameters for the live link
support.
Version 6.1.2 (April 14, 2005)
----------------------------------
Enhancements:
=============
1. Request:
To modify the command syntax for live link support.
Change:
Re-worked the command syntax as suggested by PQA.
Impact:
The command syntax for the live link feature is
modified.
Fixes:
======
1. Request:
DNS, WSP, WSS, and gateway should be sharable
among teams.
Cause:
The program reports errors if any ip address is
not unique among all teams.
Change:
Allow the above ip addresses to be sharable
among teams.
Impact:
DNS, WSP, WSS, and gateway ip addresses should
be sharable among all teams.
2. Request:
Failed to create a team when no IP_CFG or
VLAN_CFG is specified.
Cause:
The program did to request one virtual
adapter to be created with the above
configuration.
Change:
Allow one virtual adapter to be created when
no IP_CFG or VLAN_CFG is specified.
Impact:
A team with one virtual adapter should be
created when no IP_CFG or VLAN_CFG is specified.
Version 6.1.1 (April 7, 2005)
----------------------------------
Fixes:
=====
1. Problem:
Live link only supports SLB team type 0.
Cause:
The implementation accepted team type 0
and 4 for the live link support.
Change:
Removed team type 4 from the live link support.
Impact:
Live link should only support SLB team type 0.
Version 6.1.0 (April 4, 2005)
----------------------------------
Enhancements:
=============
1. Request:
To implement the live link feature.
Change:
Added the live link feature..
Impact:
The live link feature is now available.
Version 6.0.12 (October 04, 2004)
---------------------------------
(Require BMAPI version 6.5.3 or above)
Fixes:
=====
1. Problem: (CQ #11046)
baspSCfg 6.0.11 does not save or restore IP
configuration correctly
Cause:
Windows CIM providers return NULL for WINS
Primary and Secondary on W2K3 instead of
127.0.0.0 on W2K when there is no setting for
WINS Primary and Secondary.
Change:
The save logic does not handle the NULL situation
correctly. Correct the code and fix the issue.
Impact:
None.
Version 6.0.11 (September 30, 2004)
-----------------------------------
(Require BMAPI version 6.5.3 or above)
Fixes:
=====
1. Problem: (CQ #11039)
baspSCfg does NOT save all info using -save option
Cause:
Saving IP information logic is broken for multiple
teams and VLANs.
Change:
Fix codes to handle multiple teams and VLANs IP
information saving.
Impact:
None.
Version 6.0.10 (September 28, 2004)
-----------------------------------
(Require BMAPI version 6.5.3 or above)
Fixes:
=====
1. Problem: (CQ #11015)
baspSCfg needs .PDF revised
Cause:
BaspSCfg.pdf file does not have a correct
information.
Change:
Modify the requirements section with a correct
text.
Impact:
None.
2. Problem: (CQ #11016)
baspSCfg does not show 5 IPs in adv network
properties but shows in ipconfig.
Cause:
System does not get enough time to configure.
Change:
There is a timing issue when trying to configure
multiple teams with mulitiple IP, Gateway, DNS,
and WINS addresses. The system needs more time
to complete the process. Give system more time
and the problem is resolved.
Impact:
None.
Version 6.0.9 (September 22, 2004)
----------------------------------
(Require BMAPI version 6.5.3 or above)
Enhancements:
============
1. Problem: (CQ #10850)
Add a few functionality into BASP Silent Config tool
Change:
Add three new options: -restore, -remove, and -save
per OEM request.
Impact:
None
Version 6.0.8 (September 17, 2004)
----------------------------------
Enhancements:
============
1. Problem: (CQ #10754)
OEM requests BASP Silent Config utility adds 3 DNS
entry support
Change:
BASPSCfg version 6.0.8 allows to set multiple DNS.
Impact:
None
2. Problem: (CQ #10861)
Enhancement request for BaspSCfg to support up to 5
IP addresses per team
Change:
BASPSCfg version 6.0.8 allows to setup multiple IP
addresses per team.
Impact:
None
3. Problem: (CQ #10882)
Request BASPScfg supports silent configure VLAN with
multiple IP addresses
Change:
BASPSCfg version 6.0.8 allows VLAN to setup mulitple
IP addresses.
Impact:
None
Fixes:
=====
1. Problem: (CQ #10839)
BASPScfg Succeeds but reports Error 508 - the IP
address is not set correctly
Cause:
BASPSCfg does not return a correct code.
Change:
Enhance the return code logic to return a correct
code.
Impact:
None.
Version 6.0.7 (March 18, 2004)
------------------------------
Fixes:
=====
1. Problem: (CQ #9438)
BASPSCFG missing descriptive error codes.
Cause:
Does not check for duplicate VLAN ID before create
team(s).
Change:
Add code to check for duplicate VLAN ID and a new
return code for duplicate VLAN ID.
Impact:
None.
Version 6.0.6 (February 02, 2004)
---------------------------------
Fixes:
=====
1. Problem:
Duplicate team name error when create a new team
if team is already existed.
Cause:
Program checks for duplicate team name against the
existed team list.
Change:
Remove the unneccessary duplicate team name check
because this program will remove the existed team(s)
and create the new one(s).
Impact:
None.
2. Problem:
The program does not setup IP adddress for gateway, DNS,
and WINS server correctly when creating multiple virtual
adapters.
Cause:
Does not parse the options correctly.
Change:
Fix the code.
Impact:
None.
Version 6.0.5 (January 23, 2004)
--------------------------------
Enhancements:
============
1. Problem: (CQ #8809)
OEM requests add BASP silent configure option - WINS.
Change:
Per OEM request, Broadcom added two new options: -wsp
and -wss. These new options allow to setup IP
addresses for Primary (-wsp) and Secondary (-wss)
WINS Servers.
Impact:
None
Version 6.04 (October 16, 2003)
-------------------------------
(Require BMAPI version 6.3.1 or above and BASP version 6.0.7 or above)
Enhancements:
============
1. Problem: (CQ #8443)
BASPScfg silently configure DNS and Gateway IP.
Change:
Add two new -gw and -dns options for default gateway
IP address and DNS IP address.
Impact:
None
2. Problem:
Support SLB (Auto-Fallback Disable) team type.
Change:
Allow end users to configure the SLB (Auto-Fallback
Disable) team type.
Impact:
None
CHANGES in 6.03
---------------
(Require BMAPI version 6.0.0 or above)
Allow end users to see the program version from file properties.
CHANGES in 6.02
---------------
(Require BMAPI version 6.0.0 or above)
Add new -snic option to support the standby physical adapter.
Not allow to create FEC/GEC or 802.3ad team with a standby physical adapter.
Only support Broadcom certified adapters for VLANs.
- Resolved ClearQuest ID:
6914: Incorrect behavior when creating teams where team name already exists.
BaspSCfg version 6.02 will check for duplicate or already existed team
name when end users create team(s).
6915: incorrect error when teamname starts with "&...."
BaspSCfg version 6.02 will check the invalid character '&' in the team name.
CHANGES in 6.01
---------------
(Require BMAPI version 6.0.0 or above)
- Resolved ClearQuest ID:
6884: Request baspscfg default to use all teamable nics during custom config
Make -pnic option flag as optional from command line. All teamable NICs
on the system will be automatically added to new team if -pnic omitted.
6890: BaspSCfg: Change naming convention in release.txt
Update the release.txt file with correct OS support and year in BaspSCfg
version 6.01 release.
CHANGES in 6.00
---------------
(Require BMAPI version 6.0.0 or above)
- First release.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.