Release Notes
=============
Broadcom ASF Management Console
For Win32
Copyright (c) 2000-2005 Broadcom Corporation
All rights reserved.
Version 1.22 (March 25, 2005)
-----------------------------
Enhancements:
=============
1. Change:
The right-click "pop-up" menu on the Events tab now includes menu items
for copying the selected event or all events to the Windows clipboard.
Useful for pasting PET events into bug reports or support e-mails.
2. Change:
Log all error message details (even if the "Log" checkbox is unchecked).
When stressing an ASF adapter, the "Log" checkbox is often unchecked
for performance reasons and errors were not always logged in this case.
3. Change:
Created a separate column in the Events tab for the Event Sensor "Type"
and "Description". Previously, both the hexadecimal sensor "Type" value
and textual description were in the same column, causing some OEM
confusion.
Version 1.21 (September 1, 2004)
-------------------------------
Fixes:
======
1. Problem:
The "Beep" check-box on the Events tab doesn't work on Windows XP
(no audible beep is heard upon received event messages).
Change:
Changed the Beep API call to specify a frequency and duration rather
than relying on Windows to use the MessageBeep API to play the
"OK" sound.
2. Problem: (CQ 10826)
Secure RMCP acknowledgement RSP headers contained the session ID of
and sequence numbers from the originally received RSP header.
Change:
Secure RMCP acknowledgement RSP headers now contain the session ID
of the "destination entity" (the client) and the appropriate
(incremented) sequence number, rather than just a copy of the received
RSP header.
3. Problem: (CQ 10854)
The Management Console did not verify the DWORD-alignment of the
"integrity data" field in received secure RMCP messages (responses).
Change:
VerifyRspTrailer() now verifies the DWORD-alignment of integrity-
protected data in secure RMCP responses (catches CQ 10854).
Impact:
RMCP "Close Session Response" packets received from ASF Firmware v6.21
and earlier will fail the RSP integrity check.
Version 1.20 (August 16, 2004)
------------------------------
Fixes:
======
1. Problem:
Management console's RSP sequence number was not being incremented
*before* being included in RSP headers (for secure RMCP packets).
This would cause a sequence number of 0 to be used for the first
secure packet (following session establishment), which is a protocol
violation.
ASF managed clients that verify the RSP sequence number (e.g.
Broadcom ASF 2.0 Firmware v6.20) will ignore the first packet.
Change:
Increment the RSP sequence number *before* including in RSP headers
for outbound secure RMCP messages. Additionally, the sequence number
is only incremented for packets transmitted over non-Bypass (secure)
sessions.
2. Problem:
Management console did not verify session ID or sequence number of
secure RMCP response packets, which is a protocol violation.
Change:
RMCP response packets with invalid session ID or sequence numbers are
logged and ignored.
Impact:
Must use Broadcom ASF 2.0 Firmware v6.20 or later. Previous versions
included the *client* RSP session ID in the RSP header. Interactions
with older firmware will only work if both the management console and
managed client's session IDs are the same value.
Enhancements:
=============
1. Change:
Version information displayed is read from the version resource
embedded in the .exe, making the displayed version more accurate.
2. Change:
Additional RMCP command/response packet parsing/debug output.
e.g. Now parsed and displayed from RMCP responses:
- System state
- System capabilities
- Firmware capabilities
- Supported interactions
- Supported entities
- Supported special commands
Version 1.13 (April 21, 2004)
-----------------------------
Fixes:
======
1. Problem:
When viewing PET event details, some event entity descriptions were
wrong.
Cause:
PET event entity descriptions were based on IPMI PET 1.0 specification.
Entity values 19-38 were re-defined by the ASF specification.
Change:
Use descriptions of IPMI Entity IDs from ASF specification, sections
A.7 and A.8.
2. Problem:
When viewing PET event details, the event and trap source descriptions
were wrong.
Cause:
Event and trap source descriptions were based on wrong offsets in SNMP
message.
Change:
Use correct offsets for source description table lookup.
Enhancements:
=============
1. Change:
Moved "Secure Management (ASF 2.0)" button to "Manage" tab sheet
to make toggling between secure and insecure ASF more easy.
The "Security" tab sheet now disappears and reappears based on
this checkbox (rather than disabling/graying the controls).
2. Change:
Added toolbar button to the "Manage" tab to open and authenticate
a secure session, or close an open session.
3. Change:
Display PET Event Sensor Type in hexadecimal along with description.
4. Change:
Added hints ("tool-tips") for PET Event Details dialog to clarify
displayed values, including indications of "decimal" or "hexadecimal"
notation.
5. Change:
The following PET Event Details values are now displayed in
hexadecimal notation: event severity, sensor dev (SMBus address) and
sensor number.
Version 1.12 (April 12, 2004)
-----------------------------
Fixes:
======
1. Problem:
Entering a security key byte value of hexadecimal FF and toggling
between Hex and ASCII representation would expand the string beyond
the key buffer bounds, eventually crashing the application.
Cause:
The FF value was being sign-extended to a 32-bit negative value.
Change:
Convert hexadecimal byte values to unsigned 8-bit value before
converting to ASCII.
Enhancements:
=============
1. Change:
Added a toolbar with a set of buttons for quickly and conveniently
sending a single remote management command: Ping, Capabilities
Request, System State Request, Reset, Power Up, Power Down, and
Power Reset.
2. Change:
Terminology of some text labels updated to more closely match the
new ASF Configuration Control Panel Applet and documentation.
Version 1.11 (March 4, 2004)
----------------------------
Enhancements:
=============
1. Change:
Added support for security keys in hexadecimal notation. ASF 2.0
RMCP security keys are not restricted to ASCII text. This feature
allows an operator or administrator to authenticate a secure
session with an ASF client using security keys that contain
non-ASCII characters. You must use b57diag v7.21 or later to
configure hexadecimal security keys on a Broadcom network adapter.
Version 1.10 (February 18, 2004)
--------------------------------
Fixes:
======
1. Problem: (CQ 9415)
Leaving the Management Console unattended while RMCP stressing a
client and/or receiving event packets from clients could consume
unlimited amounts of system memory and take a long time (and 100%
CPU utilization) to clear the PET event log.
Cause:
There was no limit imposed on the number of trapped PET events added
to the Events log or RMCP transmit/receive information added to the
Management log.
Change:
Added configurable limits for the number of Management log lines and
PET events before older lines/events are automatically deleted.
Impact:
If a user needs to review a large number of Management log lines or
PET events, they may need to increase the limits for these logs
(under the "Settings" tab).
Enhancements:
=============
1. Request: (CQ 9318)
Display verbose translation of trapped PET event codes.
Change:
PET Events log now displays Trap, Event and Sensor source descriptions
as well as numeric values of event type and offset in place of the
Enterprise string (always the same).
Impact:
User must display Event details to see Enterprise string.
2. Change:
Support unattended RMCP stress testing with RMCP "Stress" checkbox
which causes repeated sending of RMCP commands to continue without
interruption even if no RMCP ACKs or expected responses are
received.
3. Change:
Support configurable RMCP timeout (while waiting for RMCP ACK or
expected response).
4. Change:
Support RMCP command retries (configurable) when no valid RMCP ACK
is received after sending an RMCP command.
5. Change:
Display (and allow the editing of) the Secure Session ID (on the
"Security" tab).
6. Change:
Added "Abort Session" button to "Security" tab to allow the Management
Console to abandon an open session (by changing the current Secure
Session ID to "0") without closing it. This allows testing of ASF
firmware session ID allocation/reuse without running multiple
Management Consoles.
7. Change:
Added "Mask Keys" checkbox to "Security" tab to hide key values
(secrets) in edit boxes.
8. Change:
All configurable settings are now saved-to and restored-from the
Windows Registry when the application is closed and run.
Version 1.00 (December 11, 2003)
-------------------------------
Initial release. See readme.txt for documentation.
Fixes:
======
None.
Enhancements:
=============
None.
/* End of File */
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.