==========================
R E L E A S E N O T E S
==========================
Broadcom ASF IP Monitor
for Windows and Linux
Copyright (c) 2000-2005 Broadcom Corporation
All rights reserved.
Version 7.1.2 (April 06, 2005)
------------------------------
Fixes:
======
1. Problem (CQ 12589):
If a system has more than one Broadcom network adapter installed
with ASF firmware and configuration tables in each adapter's NVRAM,
ASFIpMon will only attempt to synchronize the IP configuration
of the first such adapter (which is normal, as-designed behavior).
Disabling ASF operation for the adapter or unloading the device driver
for the adapter would not prevent ASFIpMon from selecting it as the
adapter to use for IP configuration synchronization.
If the device driver of the first such adapter was not loaded,
ASFIpMon would fail with an error of "!ERROR 20 getting ASF
configuration table". Error 20 is the BMAPI "Driver not loaded"
result code returned from BmapiGetASFTable().
This makes it difficult for QA engineers to test ASFIpMon functionality
on systems with multiple ASF-capable Broadcom network adapters.
Cause:
ASFIpMon did not skip an ASF-capable adapter if BmapiGetASFTable()
returned BMAPI_DRIVER_NOT_LOADED (as happens when the adapter is
disabled in Windows), and it did not skip adapters lacking the
"ASF enabled" bit in the ASF configuration table enable flags.
Change:
ASFIpMon now skips ASF-disabled adapters or adapters that do not have
their corresponding device driver loaded.
Impact:
ASF-disabled network adapters will no longer have their IP
configuration settings automatically synchronized by ASFIpMon.
Version 7.1.1-Windows (March 08, 2005)
--------------------------------------
Fixes:
======
1. Problem (CQ 12361):
AsfIpMon would hang while loading during system boot.
The Windows Service Control Manager (SCM) would timeout after 2
minutes waiting for the service to start, create an event log
entry stating "The Broadcom ASF IP Monitor service hung on
starting.", continue loading other services at this point, and then
AsfIpMon would start successfully.
Cause:
During start-up, AsfIpMon calls BmapiInitializeEx().
BmapiInitializeEx (from BMAPI v7.2.11) would block on a call to
the Win32 API CreateService function, which would wait indefinitely
for the SCM database to become unlocked. After a 2 minute timeout,
the SCM would continue to load the other services and then release
the lock, allowing BmapiInitializeEx() to complete and AsfIpMon to
continue starting.
Change:
AsfIpMon now sets the service status to "running" if BmapiInitializeEx
returns BMAPI_SCM_LOCKED (or BMAPI_CAN_NOT_LOCK_NETCFG) before retrying
after 10 seconds. This allows the Windows SCM to continue loading
services immediately and release the SCM database lock, thus allowing
BmapiInitializeEx() to complete successfully.
Impact:
Requires BMAPI v7.2.13 or later for this fix.
Version 7.1.0-Windows (December 15, 2004)
-----------------------------------------
This release is a complete re-write of "BAsfIpM" (now known as simply
"AsfIpMon") and shares the same source code as AsfIpMon-Linux. It includes
the following enhancements (over BAsfIpM):
1. Greatly simplified operation should provide a much higher level of
reliability and compatibility.
2. May be run manually and interactively from the command-line, or as a
background system (NT) service.
3. Configurable log levels provides easy debugging and error reporting
(to the console, system debug log, or NT event log).
4 When run as an NT service with the "-notice" log level option,
initialization and termination events are logged to the NT event log, along
with any IP configuration change events detected (CQ enhancement request
11317).
5. Configurable scanning interval (defaults to 60 minutes) - much longer
than AsfIpMon-Linux due to the facilities provided on Windows to detect
IP setting and ASF configuration changes immediately. An infinite (-1)
interval timeout may be optionally used.
6. Using Windows IP Helper API and BMAPI-Windows AsfConfigChangeCallback
for immediate detection of IP/ASF configuration changes without waiting
for an interval timeout.
7. The adapter's PCI device number may be specified for use on systems with
multiple ASF-capable Broadcom network adapters.
Version 7.1.0-Linux (December 15, 2004)
---------------------------------------
Fixes:
======
1. Problem:
If the IP settings were changed, it could take 30 seconds (or more
depending on the configured scan interval) for the new IP settings
to be detected after initialization of AsfIpMon.
If the IP settings were changed and the system was shutdown before
the scan interval timeout, the new IP settings would not be propagated
to the adapter's NVRAM for use by the ASF firmware.
Cause:
Did not scan for IP changes immediately upon initialization or during
termination/shutdown.
Change:
AsfIpMon now scans for IP settings changes immediately after
initialization and when terminating/shutting-down.
2. Problem:
It was possible for AsfIpMon to set the IP address to 169.254.*.*
(a "link local" IP address per RFC 3330) if the IP setting change was
detected while DHCP was in progress or after a failed DHCP attempt.
Cause:
There was no verification that the IP address was not a "link local"
address.
Change:
Do not use the IP address returned from BMAPI if it is a "link local"
address.
Note:
BAsfIpM-Windows already treated "link local" IP addresses as invalid.
This problem had not actually been reported in AsfIpMon-Linux (yet).
Enhancements:
=============
1. Change:
When IP setting changes are detected and propagated to the adapter,
the corresponding log entry includes the IP setting details (both old
and new).
Version 7.0.1 (November 2, 2004)
--------------------------------
Fixes:
======
1. Problem: (CQ 11160)
Init script and RPM issues on SUSE Linux 9.
Cause:
SUSE Linux uses the SUSE/LSB (Linux Standards Base) init style, so it
stores system service run scripts in /etc/init.d (not /etc/rc.d/init.d)
and run scripts must use "rc.status" functions for starting daemons,
checking/saving status, etc.
Change:
Changed init.d/asfipmon to auto-detect SUSE/LSB init style and use the
appropriate directories and rc functions (e.g. startproc, checkproc,
rc_status, etc.).
Impact:
ASF IP Monitor RPM should now install and run on SUSE Linux systems.
Enhancements:
=============
1. Change:
Init script (init.d/asfipmon) now supports passing command-line
arguments to the daemon (e.g. "service asfipmon start -debug").
Impact:
Passing additional configuration information to the daemon no longer
requires editing of the run script (init.d/asfipmon).
2. Change:
Treat BMAPI errors while scanning for ASF configuration changes as
non-fatal (but logged) errors.
Impact:
If there is a BMAPI error while scanning for IP configuration changes
or saving changes to the adapter's ASF configuration table, the daemon
will not be terminated.
3. Change:
If inet_addr() fails to parse the IP address, subnet mask, or default
gateway from the BMAPI adapter info structure (returns INADDR_NONE),
don't use the parsed value.
Impact:
If BMAPI or the driver ever returns an invalid IP address in one of
these fields, the value will not be propagated to the adapter's ASF
configuration table.
4. Change:
When IP configuration changes are detected, use a lower syslog level
(LOG_NOTICE) which *is* printed to the log by default.
Impact:
This allows easier debugging of (normally infrequent) IP configuration
changes without forcing the daemon to log text with "verbose"
(i.e. LOG_INFO) or "debug" (LOG_DEBUG) log levels.
Version 7.0.0 (October 25, 2004)
--------------------------------
This release is a complete re-write of "basfipmlnxd" (now known as simply
"asfipmon"). It includes the following enhancements:
1. Greatly simplified operation should provide a much higher level of
reliability and compatibility.
2. May be run manually and interactively from the command-line, or as a
background system service (daemon) using the supplied run script.
3. Configurable log levels provides easy debugging (either to the console
or system log).
4. Configurable scanning interval (defaults to 30 seconds).
5. Handles the reload (HUP) signal correctly, forcing an immediate re-scan
of the adapter's IP settings.
6. The adapter's PCI device number may be specified for use on systems with
multiple ASF-capable Broadcom network adapters.
7. Completely portable for future use with other Linux distributions and
other UNIX and UNIX-like operating systems (dependant on BMAPI support).
8. Includes support for both manual and RPM-based installation.
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.