===========================
R E L E A S E N O T E S
===========================
BASP sub-agent for Windows SNMP Service
for Windows 2000, Windows XP, Windows Server 2003,
Windows Vista, Windows Server 2008
Copyright (c) 2000 - 2009 Broadcom Corporation
All rights reserved.
Version 7.1.6 (Nov 23, 2009)
--------------------------------
Enhancements:
=============
1. Request: CQ42192
Provide the failover trap caused by the LiveLink informatoin.
Change:
A failover trap is generated when the physical NIC of the team
is active/inactive due to LiveLink information.
Impact:
Failover trap caused by LiveLink information of the physical NIC.
Fixes:
======
1. Problem: CQ34231
The BASP MIB trap for failover does not match with Event Log.
Cause:
The BASP MIB trap for failover is INFORMATIONAL and the one
for Event Log is WARNING.
Change:
Change the BASP MIB trap for failoever to be WARNING in
baspTrap.mib.
Impact:
baspTrap.mib MIB file.
2. Problem: CQ41249
The baspCfg.mib got errors/warnings when it was validated
by tool provided in www.muonics.com.
Cause:
The baspCfg.mib did not meet the SMI compliance.
Change:
Modified the baspCfg.mib to meet the SMI compliance.
Impact:
baspCfg.mib MIB file.
3. Problem: CQ41250
The baspStat.mib got errors/warnings when it was validated
by tool provided in www.muonics.com.
Cause:
The baspStat.mib did not meet the SMI compliance.
Change:
Modified the baspStat.mib to meet the SMI compliance.
Impact:
baspStat.mib MIB file.
4. Problem: CQ41251
The baspTrap.mib got errors/warnings when it was validated
by tool provided in www.muonics.com.
Cause:
The baspTrap.mib did not meet the SMI compliance.
Change:
Modified the baspTrap.mib to meet the SMI compliance.
Impact:
baspTrap.mib MIB file.
Version 7.1.5a (Oct 22, 2008)
--------------------------------
Fixes:
======
1. Problem: (CQ 37316)
Typo in the basptrap.mib.
Cause:
The "Brcm-BASPTrap-MIB" was misspelled to "Brcm-BSAPTrap-MIB"
in basptrap.mib.
Change:
The misspelling is corrected.
Impact:
No binary files are changed.
Version 7.1.5 (July 23, 2008)
--------------------------------
Fixes:
======
1. Problem: (CQ 36061)
The latest information of the Team Configuration was not updated
by the BASP sub-agent in Windows Vista/Server 2008 system.
Cause:
The BASP sub-agent did not instruct BMAPI to update the information
because it did not receive the notification of Team Configuration
Change from Windows Vista/Server 2008 system.
Change:
Modified the procedure to register the notification of Device Change
Event. The notification is now received by the BASP sub-agent and
the information of the Team Configuration is updated.
Impact:
Query of Team Configuration information after a Team is added/deleted.
Version 7.1.4 (February 5, 2007)
--------------------------------
Fixes:
======
1. Problem: (CQ 22576)
The SNMP service would stop after modification to Team Configuration
or Failover in a 64-bit Windows system.
Cause:
The BASP sub-agent corrupted the memory used by the Microsoft SNMP
service when processing the trap events from BMAPI.
Change:
The processing of trap events from BMAPI was redesigned to make sure
the SNMP extension agent worked within its own structure boundary.
Version 7.1.3 (August 8, 2005)
------------------------------
Fixes:
======
1. Problem: (CQ 13360)
When the Windows SNMP service would start during system startup, the
Broadcom SNMP agent would not load.
Cause:
As of BMAPI v7.2.13, BmapiInitialize(Ex) returns BMAPI_SCM_LOCKED if the
Windows NT Service Control Manager is locked at that time.
The application is expected to retry the initialization after a short
delay.
Change:
If BmapiInitializeEx() returns BMAPI_SCM_LOCKED or
BMAPI_CAN_NOT_LOCK_NETCFG, retry the BmapiInitializeEx() call after a
2 second delay. It keeps retrying until it gets either a successful
initialization or BMAPI returns a different error value.
Version 7.1.2 (Mar. 29, 2005)
---------------------------------
Enhancements:
=============
1. Request: CQ12366
32-bit Broadcom SNMP Extension Agent causes SNMP
service to hang in WS03 x64
Change:
Generate binary for x86-64 processors.
Impact:
x86-64 Windows
2. Request: CQ12420
Add SEVERITY category to our baspTrap.mib file
Change:
Add SEVERITY to the MIB for trap.
Impact:
Trap for BASP.
Version 7.1.1 (Mar. 11, 2005)
---------------------------------
Enhancements:
=============
1. Request:
Enhance the performance
Change:
Instead of calling BmapiRefreshData() in every query,
only call BmapiRefreshData() when necessary while
data are still upadted properly.
Impact:
All
Fixes:
======
1. Request:
baspTrap.mib can not be compiled under MG-SOFT mib
compiler.
Cause:
The compiler will error out when compile the trap
mib.
Change:
Correct the problem.
Impact:
Trap for BASP.
Version 7.1.0 (Mar. 10, 2005)
---------------------------------
Enhancements:
=============
1. Request:
Support LiveLink feature.
Change:
Add LiveLink configuration and statistics to MIB and
enhance codes to support LiveLink feature.
Impact:
All
2. Request:
Add IP address for virtual adapter.
Change:
Add more configuration information for virtual
adapter.
Impact:
Virtual adapter configuration.
3. Request:
Be able to install the agent to its own directory
instead of installing in system directory
Change:
Change from static binding to BMAPI to dynamic
binding and loading of BMAPI library.
Impact:
All
Fixes:
======
1. Request:
'btspAdapterDesc' is not shown.
Cause:
The codes is not implement properly.
Change:
Correct the implementation problem.
Impact:
Data of 'btspAdapterDesc' field.
Version 7.00 (June 2, 2004)
---------------------------
Fixes:
======
1. Problem: (CQ 8790)
Incorrect version number for baspmgnt.dll.
Cause:
Resource file contained the incorrect version number.
Change:
Updated the version/copyright information in the resource file.
2. Problem: (CQ 8735)
Reports the wrong team type for SLB (Auto-Fallback Disable) teams.
Cause:
MIB file (BaspCfg.mib) did not contain description for this team
type value (104, aka SLB-AFD).
Change:
Added SLB-AFD (104) team-type value to MIB file.
3. Problem: (CQ 9850 and 10082)
Information Returned by SNMP is Static.
SNMP Query Returns No Team Info Without Restart.
Cause:
SNMP agent would copy team information from BMAPI.DLL when the
agent was initially loaded and would not dynamically update the
information during run-time.
Change:
Call BmapiRefreshData() and rebuild internal data tables upon each
call to SnmpExtensionQuery().
Overview
--------
The BASP sub-agent, baspmgnt.dll, is designed for the Windows 2000 and
Windows NT SNMP Service. It is required to install the SNMP service
before installing BASP sub-agent.
The BASP sub-agent allows an SNMP manager software to actively
monitor the configurations and performance of the Broadcom
Advanced Server features. The sub-agent also provides an alarm
trap to an SNMP manager to inform the manager of any changes to
the conditions of the BASP component.
The BASP sub-agent allows monitoring of the configurations and
statistics for the BASP teams, the physical NIC adapters participating
in a team, and the virtual NIC adapters created as the result of teaming.
The BASP configuration data includes information such as team IDs,
physical/virtual/VLAN/team adapter IDs, physical/virtual/VLAN/team/ adapter
descriptions, and MAC addresses of the adapters.
The statistics include detailed information such as data packets
transmitted and received for the physical/virtual/VLAN/team adapters.
The alarm trap sends back to an SNMP manager information about the changes
in configuration of the physical adapters participating in a team, such as
physical adapter link up/down, and adapter installed/removed events.
To monitor this information, an SNMP manager needs to load the Broadcom
BASP MIB database files to allow monitoring of the information described
above. These files shown below, are included with the Broadcom installation CD:
baspconfig.mib
baspstat.mib
basptrap.mib
The monitored system running BASP requires installation of the BASP
SNMP sub-agent component and either the Microsoft Windows 2000 or
Windows NT 4.0 SNMP service to be installed. Installation of this
component should be done through the BASCS setup application.
See the Broadcom Advanced Server Control Suite section in the User Guide for
detailed information on this installation.
Manual Installation
-------------------
(1) Make sure Microsoft SNMP Service is installed.
(2) Use registry editor to add following keys:
(a) Go to
"HKLM\System\CurrentControlSet\Services\SNMP\Parameters\ExtensionAgent"
sub-key.
(b) Locate the highest number shown under this sub-tree and create
a new string value with the name as one plus the highest number, e.g. if
the highest number shown is 5, create a DWORD value key with name "6"
and the value as "SOFTWARE\Broadcom\BASPAgent\CurrentVersion".
(c) Go to "HKLM\Software".
(d) Create three sub-keys underneath this tree as
"Broadcom\BASPAgent\CurrentVersion".
(e) Go to "HKLM\Software\Broadcom\BASPAgent\CurrentVersion".
(f) Create a STRING key with the name "pathname" and the value as
the installed directory for the MIB agent.
(3) Open a command prompt and enter "net stop SNMP" to stop
the current running instance of the SNMP service.
(4) Enter "net start snmp" to restart the SNMP service.
Changes
-------
v1.0.7: Fixed SNMP config MIB syntax.
v1.0.6: Added SNMP TRAP support for Failover events.
v1.0.5: Fixed zero value problem of btsvPacketSend object.
v1.0.4: Fixed "Get Request Failed error when try to get btsvPacketRecv object."
Fixed "Both BASPConfig and BASPStat mib files do not display name
correctly in the Mib Browser."
Changed the description of "btTeamIndex" object in the mib files.
Fixed compilation error of mib files with MG-SOFT MIB compiler v1.0.
v1.0.3: Fixed "no such name error" in GET request on scalar variables,
such as btTeamNumber.
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.