Release Notes
=============
Broadcom Manageability Configuration and Control Utility
Copyright (c) 2008 Broadcom Corporation
All rights reserved.
------------------------------
Version 1.00.0 - June 28, 2008
------------------------------
Fixes:
======
1. Problem with "bmcc sync" command:
When propagating the IPv4 configuration changes to a the controller's
NVRAM, if either the primary or second name server string returned by
Windows was invalid, the name server IP address in the configuration
would be set to 255.255.255.255.
Cause:
The inet_addr() function used to convert the name server IP address
string to a binary format returns -1 (0xffffffff) on failure.
Change:
If inet_addr() returns -1, leave the name server IP address as 0.0.0.0.
Enhancements:
=============
1. "bmcc edit"
Do not allow more than 32 user accounts or roles to be created.
2. "bmcc create"
Default RSP configuration record now grants the Administrator role the
rights to execute all remote control commands (that are supported by the
system).
3. "bmcc edit"
Friendlier / correction descriptions of the following options:
a. RMCP Ping Only
b. Management Console Address
------------------------------
Version 0.99.0 - June 20, 2008
------------------------------
Fixes:
======
1. Problem: (CQ 35986)
"bmcc edit" display incorrect/corrupted IPv6 addresses.
Cause:
Build (compile/link) issue with dependant libraries.
Change:
Clean build.
Impact:
IPv6-enabled configurations only.
2. Problem:
Some sequences of commands could create configuration records with an
attribute value of 0xff.
Cause:
The BMCFG library API uses this value (BMCFG_API_ATTR_NO_CHANGE) to
indicate "no change should be made" to the attribute value of records
that already exist. The bmcfgGetRecordForUpdate() function was not
initializing the attribute value (to 0x00) when the record did not
already exist.
Change:
bmcfgGetRecordForUpdate() now creates the record with no attribute
flags (value of 0x00) if called with an attr parameter value of 0xff
(BMCFG_API_ATTR_NO_CHANGE).
Impact:
Advanced configuration record set editing commands only.
Enhancements:
=============
1. When importing OMDATA_STORAGE record into NVRAM, create the APE_DATA
directory content lengths to the record length (evenly divisible by 16),
not the record's data length (potentially any value).
2. The "ocreate" command now creates the OMDATA_STORAGE configuration
record with a data_length value of 0 (does not round up specified length
to nearest value evenly divisible by 4 bytes) and passes the specified
storage length as the record padding value (which is automatically
rounded up to the nearest evenly divisible by 16 byte value).
3. "bmcc view-asf" and "bmcc view-asfcfg":
a. DO NOT byte-swap the SystemID value (it is in host byte order).
b. Display the Mfg IANA number as a decimal value (network byte order).
4. "bmcc web":
Now skips (does not import) thumbs.db files.
5. Importing/exporting offline Web Data and Opaque Management Data:
Various fixes and improvements (speed, robustness) related to importing
and exporting offline web and opaque management data to/from NVRAM.
6. "bmcc edit" OMData support:
a. Total storage size for Opaque Management Data may now be easily
adjusted from the [O] Opaque Management Data menu.
b. Storage and instance max_size values are sanity checked against
each other.
------------------------------
Version 0.98.0 - June 13, 2008
------------------------------
Fixes:
======
1. Problem: (CQ 35801)
"bmcc delete" command does not delete web and opaque management data
from NVRAM.
Cause:
The APE_DATA and APE_WEB_DATA NVRAM directory entries cannot be removed
via Windows applications (using BMAPI).
Change:
Having "bmcc remove" truncate (set the length to 0) of the APE_DATA and
APE_WEB_DATA NVRAM directory entries (using the appropriate BMAPI
functions) when the corresponding configuration records do not exist.
Until such time as there are BMAPI functions create to remove these
NVRAM directory entries, this is the best we can do.
Impact:
Use "bmcc remove" instead of "bmcc delete" when deleting Opaque
Management Data or Web Data storage records from the configuration
record set.
2. Problem: (CQ 35815)
"bmcc ocreate" command returns error when value is not multiples of 4.
Cause:
NVRAM directory content lengths must be evenly divisible by 4 bytes
and the Opaque Management Data storage is contained in its own separate
NVRAM directory entry (APE_DATA).
Change:
"bmcc ocreate" command rounds-up the specified length as needed to be
evenly divisible by 4-bytes.
Enhancements:
=============
1. Maintains .cfg file length:
When modify a configuration file (with any of the bmcc commands that
make changes to the configuration record set), does not truncate
the configuration file (make smaller) unless the new "-truncate"
option is used.
2. Support padded .cfg files:
The "bmcc create" and "bmcc edit" commands support specifying a minimum
length (in kilobytes) of the configuration file to be created or
modified with the "bmcc create=<size>" and "bmcc edit=<size>" usage.
3. NVRAM usage details:
"bmcc status" command now displays configuration/web/OM data storage
NVRAM used (in bytes).
-----------------------------
Version 0.97.0 - June 6, 2008
-----------------------------
Fixes:
======
1. Problem: (CQ 35423)
The "remove" command does not completely remove a configuration record.
Cause:
This was designed behavior, the "remove" command just changed the
record type to "NULL" (deleted) and zeroed-out it's data, leaving
the bytes in the configuration record set which could then be
reused by a newly-added or re-sized configuration record.
Change:
The "remove" command now removes the record header and data bytes
from the configuration record set.
The "delete" command was added to perform the function of the old
"remove" command.
2. Problem:
Configuration records in a configuration file could be encrypted,
but if the resulting configuration file was then imported into a
network controller's NVRAM, the configuration records (most likely)
could not be decrypted (and used) by the management firmware.
Cause:
The device's encryption keys are not read or used by BMCC when
reading or writing a configuration file, so the encryption keys used
to perform the encryption were invalid (all zeroes) and thus probably
do not match the encryption keys of the device.
Change:
The "encrypt" and "decrypt" commands will display an error message when
attempted to be used against a configuration file (rather than a
network controller's NVRAM).
Enhancements:
=============
1. APE_WEB_DATA NVRAM directory import/export:
The "offline" web data stored in the network controller's NVRAM
APE_WEB_DATA directory entry may now be imported to/from configuration
files and directly initialized with the "web" command.
2. NVRAM write optimization:
Only the valid configuration records in the NVRAM image are written back
to the device's NVRAM (terminator records, if they exist, are not
re-written to NVRAM unnecessarily).
3. Added "verify" command:
"bmcc verify" may now be used to check the validity of a configuration
set (configuration file or NVRAM contents).
4. Automatic configuration set verification:
When configuration record sets are read-from or written-to a
configuration file or NVRAM, the contents are automatically verified
unless the (new) '-noverify' option is specified on the command-line.
5. Added "view-asfcfg" command:
"bmcc view-asfcfg" may now be used to display all the ASF SDT records in
the configuration record set.
/* 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.