============================
R E L E A S E N O T E S
============================
Broadcom Ethernet Controller WMI provider for Windows
Copyright (c) 2010 Broadcom Corporation
All rights reserved.
March 5, 2010
Version 12.2.15 (March 5, 2010)
---------------------------------
Fixes:
=====
1. Problem: Cont00046227 - Updating account information will
not appear on the remote mgmt system after
applying WMI provision scripts.
Cause:
A bug caused CIM class objects not refreshed as
supposed.
Change:
Fixed bug to refresh.
Impact:
DASH Management.
Version 12.2.14 (February 12, 2010)
---------------------------------
Fixes:
=====
1. Problem: CQ45704
Firmware Upgrade can't upgrade ASF firmware for
BCM57765 NIC.
Cause:
Firmware Upgrade did not check the device type correctly
for the BCM57765 NIC when upgrading the ASF firmware.
Change:
Firmware Upgrade checks the device type correctly for
the BCM57765 NIC when upgrading the ASF firmware.
Impact:
Firmware Upgrade for BCM57765 NIC.
2. Problem: CQ45727
Firmware Upgrade can't program/upgrade OTP bootcode for
BCM57780 NIC.
Cause:
The revision of the OTP image file was not retrieved
correctly and Firmware Upgrade does not allow the
operation to continue.
Change:
The revision of the OTP image file is now retrieved
correctly and the command can be completed.
Impact:
Firmware Upgrade OTP bootcode for BCM57780.
Version 12.2.13 (February 5, 2010)
---------------------------------
Enhancements:
=============
1. Request:
Support firmware upgrade to
BCM57761/65/81/85/91/95 NICs.
Change:
Added support to BCM57761/65/81/85/91/95 NICs.
Impact:
Firmware upgrade.
Note: BMAPI v7.17.17 is required for BCM57761/65/81/85/91/95
NICs support.
Version 12.2.12 (December 31, 2009)
---------------------------------
Enhancements:
=============
1. Request: Ability to modify DASH settings when DASH firmware
is disabled.
Change:
Removed check for firmware enabled to show instances
of OOB Settings.
Impact:
OOB management.
Fixes:
=====
1. Problem: OOBManagement8021xSetting.Identity is empty after
modifying the instance.
Cause:
typo in setting username and password field caused
identity field to be wiped out.
Change:
corrected the typo.
Impact:
BRCM_OOBManagement8021xSetting.
Version 12.2.11 (October 7, 2009)
---------------------------------
Enhancements:
=============
1. Request: New properties for BRCM_OOBManagement8021xSetting.
Change:
Added EAP_MSCHAPv2Enabled and UserName properties.
Impact:
BRCM_OOBManagement8021xSetting.
Fixes:
=====
1. Problem: Cont00043914
Console hangs when creating account.
Cause:
Variables were previously changed from uint32 to
uint64 type, causing the returned CIM_Account
object path to have missing key property.
Change:
Make sure string format was handled properly.
Impact:
BRCM_RoleBasedAuthorizationService
2. Problem: Missing association between new setting instances and
BRCM_OOBManagementService.
Cause:
Did not populate association for the new setting
instances.
Change:
Added the association instances.
Impact:
CIM_ElementSettingData
Version 12.2.10 (October 6, 2009)
---------------------------------
Enhancements:
=============
1. Request: Support for 802.1X Authentication configuration
property stream and certificate records.
Change:
Added BRCM_OOBManagement8021xSetting,
BRCM_OOBManagementHTTPClientSetting, and
BRCM_OOBManagementHTTPSClientSetting class.
Impact:
DASH management.
Fixes:
=====
1. Problem: Cont00043939
Executing ClearLog method does not remove all
log entries.
Cause:
Missing "implemented" keyword in MOF file.
Change:
corrected MOF file.
Impact:
CIM_DiagnosticsLog
2. Problem: Cont00043914
Unable to assign roles from the Accounts tab .
Cause:
Variables were previously changed from uint32 to
uint64 type, causing parse error.
Change:
Use the correct method to parse uint64 numbers.
Impact:
BRCM_RoleBasedAuthorizationService
Version 12.2.9 (September 3, 2009)
---------------------------------
Enhancements:
=============
1. Request: CQ43161
The Combo MBA firmware file with UEFI driver inside
should not be device specific.
Change:
FwUpg will generate the device specific ID according
to the underneath NIC and use it for the device ID
of the UEFI driver.
Impact:
MBA firmware upgrade.
Fixes:
=====
2. Problem: CQ42295
Failed to upgrade Combo MBA firmware file that
contained only UEFI driver or FCODE.
Cause:
FwUpg expected the Combo MBA firmware file always
contained the MBA firmware as the first component.
Change:
FwUpg will handle the Combo MBA firmware file that
contained any combination of MBA firmware, UEFI
driver, or FCODE.
Impact:
MBA firmware upgrade for BCM57710 adapters
Version 12.2.8 (August 27, 2009)
---------------------------------
Fixes:
=====
1. Problem: Cont00043296 WMI 5761: Diagnostic test will hang on
LED test .
Cause:
When Broadcom agent is running, it competes against
WMI Provider with BMAPI resources, which can cause
failure to initialize diag.
Change:
Retry a few times if diag failed to initialize.
Impact:
CIM_DiagnosticTest.
Version 12.2.7 (August 19, 2009)
---------------------------------
Fixes:
=====
1. Problem: Diagnostic tests are not applicable to 5785 which are
not Broadcom PHY.
Cause:
Did not filter out non-applicable 5785.
Change:
Do not run diagnostic test on 5785 which are not
Broadcom PHY.
Impact:
CIM_DiagnosticTest.
Version 12.2.6 (August 11, 2009)
---------------------------------
Fixes:
=====
1. Problem: Newly created CIM_Account is associated to an
CIM_OpaqueManagementData instance by CIM_AssignedPrivilege,
if this CIM_OpaqueManagementData instance was associated
to a previouly deleted CIM_Account.
Cause:
Did not reset the privilege of CIM_OpaqueManagementData
when deleting the account.
Change:
Reset the privilege of CIM_OpaqueManagementData
when deleting the account.
Impact:
CIM_OpaqueManagementData.
Version 12.2.5 (August 4, 2009)
---------------------------------
Fixes:
=====
1. Problem: Running installer on Vista / Win2k8 using a non-admin
account in the administrator group failed to modify
registry.
Cause:
New restriction from Vista / Win2K8.
Change:
Work around by writing registry in CIM Provider.
Impact:
Installer.
Version 12.2.4 (July 27, 2009)
---------------------------------
Fixes:
=====
1. Problem: When running pagackage DiagnosticTest overnight with
DASHMgmtCon, DiagTest was terminated before completed.
Cause:
A design flaw caused data to be unloaded unexpectedly
when running diagnostics immediately after loading
DASHMgmtCon. The unexpected unloading of data
terminated all job in progress.
Change:
Fixed the design flaw so data will not unload
unexpectedly.
Impact:
All.
Version 12.2.3 (July 24, 2009)
---------------------------------
Enhancements:
=============
1. Request:
Change BRCM_OOBManagementADSetting.Password from
string[] octet string type to string type.
Change:
Changed according to request.
Impact:
BRCM_OOBManagementADSetting.
Fixes:
=====
1. Problem: Read() and Write() methods of
CIM_OpaqueManagementDataService handles buffer of
uint8[] octet string as encoded, which is not
consistent with DSP0004.
Cause:
Mistakenly followed DSP0230 which specifies runtime
conversion at the WS-Management layer of Uint8[]
OctetStrings as base 64 encoded.
Change:
Removed encoding/decoding of buffer.
Impact:
CIM_OpaqueManagementDataService.
2. Problem: Provider expecting uint8[] octet string to be
base64 encoded, which is not consistent with
DSP0004.
Cause:
Previous fix for Cont00040546 was not correct.
uint8[] octet string should not be encoded.
Change:
Revert back to not decoding uint8[] octet string.
Impact:
BRCM_OOBManagementSecureRMCPSetting.
Version 12.2.2 (July 17, 2009)
---------------------------------
Fixes:
=====
1. Problem: Cont00042660 - Unable to enumerate instances after
installing version 12.2.1.
Cause:
BMAPI version mismatch between provider and bmctrl,
causing crash when structure of the wrong version
was passed down.
Change:
Work around by not passing structure to API.
Impact:
All.
2. Problem: Cont00042535 - BRCM_OOBManagementWebserverSetting
does not have the correct naming convention
Cause:
Class name in MOF file did not conform to
naming convention.
Change:
Updated MOF file to refect correct naming convention.
Impact:
BRCM_OOBManagementWebServerSetting.
Version 12.2.1 (July 13, 2009)
---------------------------------
Fixes:
=====
1. Problem: CIM_SoftwareIdentity instance for WMI Provider
reports incorrect version number.
Cause:
version file was not updated in the last release.
Change:
Updated version file.
Impact:
CIM_SoftwareIdentity.
Version 12.2.0 (July 11, 2009)
---------------------------------
Enhancements:
=============
1. Request:
Add support for active directory modeling.
Change:
Support added.
Impact:
Opaque data management and active directory modeling.
2. Request:
Add validation logic to match the software identites,
firmware image file and the device before performing
firware upgrade/downgrade operations.
Change:
Support added.
Impact:
Different upgrade operations on NX1 and NX2 devices
with combination of matching/mis-matching firmware image
files.
Fixes:
=====
1. Problem: CQ41825
Extended directory is corrupted after upgrading
to the bootcode that is larger than
the current one.
Cause:
The function that used for upgrade bootcode didn't
support the extended directory entries.
Change:
Added the extended directory support in the function.
Impact:
BCM5761 NIC upgrade with extended directory entry.
Version 11.0.37 (June 26, 2009)
---------------------------------
Enhancements:
=============
1. Request:
Add support for BCM5785 firmware upgrade.
Change:
Added 5785 support.
Impact:
upgrade firmware for BCM5785.
Fixes:
=====
1. Problem: iSCSI bootcode upgrade for NX1 failed.
Cause:
Extra space in parameter caused parsing
to fail.
Change:
removed extra space.
Impact:
upgrade iSCSI firmware for NX1 adapters.
Version 11.0.36 (June 19, 2009)
---------------------------------
Enhancements:
=============
1. Request:
NX1: Added support to upgrade iSCSI bootcode
with Ipv4, IPv6, or both.
Change:
Added support to upgrade iSCSI bootcode with
Ipv4, IPv6, or both.
Same rule of calling InstallFromURI() as
specified earlier for NX2 applies to NX1.
Impact:
upgrade iSCSI firmware for NX1 adapters.
Fixes:
=====
1. Problem: CQ42097
FwUpg was not able to upgrade the MBA firmware
without the "Force" option.
Cause:
FwUpg has a bug when it tries to get the MBA
version from NVRAM for a comparison to the MBA version
in the file.
Change:
The bug is fixed and FwUpg can get the MBA version
from the NVRAM and compare it to the version of
the file.
Impact:
upgrade MBA firmware for NX2 adapters.
Version 11.0.35 (June 5, 2009)
---------------------------------
Enhancements:
=============
1. Request: Added support for upgrading iSCSI firmware with
ipv4/ipv6/ipv4n6 options for NX2.
Change:
When calling InstallFromURI() method to upgrade
iSCSI firmware, the InstallOptions parameter array
must contain value 32769, and the corresponding
InstallOptionsValues entry must contain either
one of "ipv4", "ipv6", or "ipv4n6" to specify
the desired iscsi configuration. If this option
is not specified when upgrading iscsi firmware,
InstallFromURI() method will return error.
Impact:
Firmware upgrade for NX2 iscsi.
Fixes:
======
1. Problem: Firmware upgrade for NX2 devices with the wrong
image file will corrupt the device
Cause:
Did not verify image before doing fwupg.
Change:
Check image and make sure it is the correct type
before performing firmware upgrade.
Impact:
Firmware upgrade for NetXtreme II.
Version 11.0.34 (May 29, 2009)
---------------------------------
Fixes:
======
1. Problem: Cont00040637 BRCM_NetworkController does not
have property value on B57780/B57790
Cause:
Windows WMI handles uint16 properties as signed
VT_I4 variant.
Change:
Use VT_I4 variant to set uint16 properties.
Impact:
BRCM_NetworkController.
2. Problem: Cont00041511 The FwUpg tool can't prg/upg OTP
under Windows 7 64-bit system.
Cause:
FwUpg has a bug when trying to release
an allocated buffer during prg/upg OTP content.
Change:
FwUpg can now release the allocated buffer
correctly.
Impact:
FwUpg for OTP.
Version 11.0.33 (May 22, 2009)
---------------------------------
Enhancements:
=============
1. Request: After deleting an instance of CIM_Account, any
CIM_OpaqueManagementData instances owned by the
account should be set to unassigned.
Change:
Clear the owner field if the account does not
exist.
Impact:
CIM_OpaqueManagementData
2. Request: Audit privilege support for RecordLog Profile.
Change:
Added audit privilege for RecordLog Profile.
Impact:
CIM_Privilege
Fixes:
======
1. Problem: Cont00040658 Unable to upgrade/downgrade
5761S bootcode
Cause:
Firmware Upgrade did not support 5761S.
Change:
Added 5761S firmware upgrade support.
Impact:
firmware upgrade.
Version 11.0.32 (May 8, 2009)
---------------------------------
Fixes:
======
1. Problem: Cont00040290 Dashmgmtcon: Failed to Create
account with WMI(In-Band) after using bmcc
to delete account.
Cause:
Once the DASH data is loaded, provider does
not periodically synchronize with firmware
for any updates made outside.
Change:
Implement an expiration machanism so that
provider will refresh the data if it has been
a while after the last refresh.
Impact:
All classes related to the following profiles:
BRCM_OOBManagementService,
Role Based Authorization,
Simple Identity Management,
Opaque Management Data.
2. Problem: Cont00040540 WMI: Unable to change Role name.
Cause:
ModifyInstance of CIM_Role was not implemented.
Change:
Implement ModifyInstance.
Impact:
CIM_Role.
3. Problem: Cont00040541 - WMI: Unable to add/remove
privileges from default Roles.
Cause:
There are 2 parts of problem in this CQ:
DashMgmtCon and WMIProvider.
For WMIProvider, a bug in ModifyRole() of
RoleBasedAuthorizationService causing it to
fail before it updates the privileges.
Change:
Fixed the bug in ModifyRole. This CQ will
be resolved after DashMgmtCon has a new
release to fix the problem.
Impact:
RoleBasedAuthorizationService.ModifyRole.
4. Problem: Cont00040542 WMI: Unable to remove all the
Roles from Accounts tab.
Cause:
Bug in utility funcation returning failure
if an array was empty.
Change:
Fixed the function so that it supports empty
array.
Impact:
RoleBasedAuthorizationService.AssignRoles.
5. Problem: Cont00040546 WMI: Modify the AdministratorKey
by WMI,the key value is inconsistency between
dashmgmtcon and bmcc.
Cause:
Did not decode octet string before setting
the key.
Change:
Decode octet string.
Impact:
BRCM_OOBManagementSecureRMCPSetting.
6. Problem: Cont00040613 WMI: Unable to enable Account
instances.
Cause:
Did not handle EnabledState property in
CIM_Account.ModifyInstance.
Change:
Set EnabledState in ModifyInstance.
Impact:
CIM_Account.
7. Problem: Cont00040637 (CIM test) BRCM_NetworkController
does not have property value on B57780/B57790.
Cause:
Used wrong type and caused value overflow.
Change:
Changed to use the correct type.
Impact:
BRCM_NetworkController.
Version 11.0.31 (April 10, 2009)
---------------------------------
Fixes:
======
1. Problem: Upgrade OPT firmware using WMI provider may
fail/crash.
Cause:
Buffer handling problem when trying to backup
NVRAM content before upgrade.
Change:
Fixed the buffer issue.
Impact:
All OTP upgrade on BCM57760/80/90.
Version 11.0.30 (April 9, 2009)
---------------------------------
Fixes:
======
1. Problem: Cont00040028 DASH: WMI : CIM_SNMPTrapTarget property
values change will fail.
Cause:
Did not implement ModifyInstance on this class.
Change:
Added ModifyInstance support.
Impact:
CIM_SNMPTrapTarget
2. Problem: Cont00040205 WMI:
CIM_SoftwareInstallationServiceCapabilities does not
have property value.
Cause:
InstallFromURI() method was originally implemented as a
synchronous function, so SupportedAsynchronousActions
property was populated but not SupportedSynchronousActions.
When InstallFromURI() was changed to be a synchronous
method, forgot to change the capabilities.
Change:
Changed from SupportedSynchronousActions to
SupportedAsynchronousActions.
Impact:
CIM_SoftwareInstallationServiceCapabilities
3. Problem: Cont00040253 Get incorrect driver version with
WMI/WinRM(In_Band).
Cause:
Driver information was obtained from BMAPI, which does
not support the new 4 part driver version format.
Change:
Get the version from the driver file instead of BMAPI.
Impact:
CIM_SoftwareIdentity
4. Problem: Missing instances of CIM_Privilege.
Cause:
Did not sync up with additional profile privileges.
Change:
Updated with additional profile privileges.
Impact:
CIM_Privilege
5. Problem: Running firmware upgrade from CIMStudio caused deadlock.
Cause:
An object was kept open, blocking other access.
Change:
Changed to use static function so there's no need to
keep the object open.
Impact:
CIM_SoftwareInstallationService
Version 11.0.29 (March 13, 2009)
---------------------------------
Fixes:
======
1. Problem: After deleting an instance of CIM_OpaqueManagementData,
more instances disappeared.
Cause:
There was a bug when provider gathers the data. If there
is an unused record in between, it stops looking further
for more records.
Change:
Skip the unused record and continue with the rest of
the records.
Impact:
CIM_OpaqueManagementData
2. Problem: No associations existed for unassigned CIM_Privilege instances.
Cause:
Not implemented.
Change:
Associate privileges to CIM_RoleBasedAuthourizationService.
Impact:
CIM_RoleBasedAuthorizationService / CIM_Privilege
3. Problem: Missing CIM_ServiceServiceDependency association between
BRCM_OOBManagementService and it's dependent service classes.
Cause:
Not implemented.
Change:
Associate BRCM_OOBManagementService to
RoleBasedAuthourizationService, AccountManagementService,
and OpaqueManagementDataService.
Impact:
BRCM_OOBManagementService, RoleBasedAuthourizationService,
AccountManagementService, OpaqueManagementDataService
4. Problem: Firmware upgrade allows incorrect selfboot image file
to be upgraded for 57790.
Cause:
Did not validate device ID in image file against the device.
Change:
Validate device ID in image file against the device.
Impact:
Firmware upgrade
5. Problem: Firmware upgrade fails to upgrade MBA firmware for
57710/57711/57712 adapters in 64-bit system.
Cause:
The 64-bit pointer was not handled correctly when upgrading
the combined MBA firmware.
Change:
The 64-bit pointer is handled correctly when upgrading
the combined MBA firmware.
Impact:
Firmware upgrade
Version 11.0.28 (March 6, 2009)
---------------------------------
Enhancements:
=============
1. Request: Support for Opaque Data Management Profile.
Change:
Added Support for Opaque Data Management Profile.
Impact:
All
2. Request: FwUpgrade Support for 57760/57780/57790
Change:
Added new chip support. BMAPI version requirement
is upgraded to 7.16.0.
Impact:
Firmware upgrade
Version 11.0.27 (February 19, 2009)
---------------------------------
Fixes:
======
1. Problem: When an instance of DiagnosticRecord is deleted,
the associations to the record were left dangling.
Cause:
Did not remove the corresponding association.
Change:
Delete associations when DiagnosticRecord instances
are deleted.
Impact:
Diagnostics
2. Problem: RoleBasedAuthorizationService.ShowRoles() returns failure
if the subject does not have any assigned roles.
Cause:
Implementation error.
Change:
Returns empty array of roles if the subject does not have
any assigned roles.
Impact:
RoleBasedAuthorizationService
Version 11.0.26 (January 20, 2009)
---------------------------------
Fixes:
======
1. Problem: When running Diagnostics, no DiagnosticCompletionRecord
if device driver is not loaded.
Cause:
Did not generate records if test cannot be started.
Change:
Generate record if concrete job is returned by
InvokeMethod() with return code 4096.
Impact:
Diagnostics
Version 11.0.25 (January 14, 2009)
---------------------------------
Fixes:
======
1. Problem: Provider hung while unloading.
Cause:
Provider was waiting on an event which was never set
if UpgradeFW was never run.
Change:
The event was used for a thread which is now obsolete
as a result of optimization, and so it is now removed
and no need to wait for such event.
Impact:
All
2. Problem: DiagnosticTest cannot be terminated for package test
and looped test.
Cause:
Terminate was not updated with the added support of
package test and looped test.
Change:
Check if there is a terminate request before executing
each diagnostic.
Impact:
CIM_DiagnosticTest
3. Problem: CIM_ConcreteJob.PercentComplete remains 0 when
DiagnosticTest failed.
Cause:
Progress was not updated in case of exception.
Change:
Update job progress when exception occurs.
Impact:
CIM_DiagnosticTest
Enhancements:
=============
1. Request: Support for simultaneous diagnostic test on different
port.
Change:
Added Support for simultaneous diagnostic test on
different port.
Impact:
CIM_DiagnosticTest
Version 11.0.24 (December 8, 2008)
---------------------------------
Enhancements:
=============
1. Request: Change CIM_ConcreteJob.JobStatus to contain
informative information about current job status.
Change:
CIM_ConcreteJob.JobStatus to contain the number of
loops passed / failed in the current diagnostic test.
Impact:
CIM_ConcreteJob
Version 11.0.23 (December 3, 2008)
---------------------------------
Fixes:
======
1. Problem: Provider crashed after a diagnostic test failed.
Cause:
Test result data structure was unintentionally
corrupted during initialization.
Change:
Properly initialize data structure.
Impact:
CIM_DiagnosticTest
Version 11.0.22 (December 1, 2008)
---------------------------------
Fixes:
======
1. Problem: CIM_ConcreteJob.JobStatus grows with number of
loops in diagnostic test.
Cause:
All the status in each loop is appended.
Change:
JobStatus only shows the status in current loop.
Impact:
CIM_ConcreteJob.
Enhancements:
=============
1. Request: Check if suspend driver is needed and return error
when condition is not met in the functions that
calls the diagnostic test.
Change:
Added suspend driver check.
Impact:
CIM_DiagnosticTest
Version 11.0.21 (November 26, 2008)
---------------------------------
Fixes:
======
1. Problem: DiagnosticTest on NetXtreme II devices failed.
Cause:
Previous code optimization introduced a bug
that caused NDIS handles being used for diag.
Change:
Fixed error to use the correct VBD handle for
NetXtreme II devices.
Impact:
CIM_DiagnosticTest / BRCM_NetworkController.
Enhancements:
=============
1. Request: Support Diagnostic Package Test and test Looping.
Change:
New instance of CIM_DiagnosticTest is added to
perform package test. All available diagnostic
tests to the specified device will be executed.
Looping is supported by CIM_DiagnosticSetting.
The LoopControl property of CIM_DiagnosticSetting
indicates the loop control machanism, and currently
only "Loop Count" (3) is supported. The
array-positional corresponding entry in
LoopControlParameter indicates the number of times
the diagnostic test will be performed. The default
loop count is 1, and can be overriden by passing an
instance of CIM_DiagnosticSetting which contains
a different value in LoopControlParameter.
Impact:
CIM_DiagnosticTest, CIM_DiagnosticSetting
Version 11.0.20 (October 29, 2008)
---------------------------------
Fixes:
======
1. Problem: Firmware upgrade for NX2 failed when image path
contains spaces.
Cause:
White spaces in file path breaks Tcl parsing.
Change:
Use quotes around file path.
Impact:
CIM_SoftwareInstallationService.
Enhancements:
=============
1. Request: InstallFromURI() to return CIM_ConcreteJob instead
of being hung during firmware upgrade.
Change:
Upon successful parsing of parameters,
InstallFromURI() will return immediately with a
reference of CIM_ConcreteJob. User can then check
for the JobStatus of the CIM_ConcreteJob.
JobStatus 7 indicates success, while JobStatus 10
indicates failure.
Currently only one firmware upgrade can be performed
by the provider at a time.
Impact:
CIM_SoftwareInstallationService
Version 11.0.19 (October 19, 2008)
---------------------------------
Fixes:
======
1. Problem: Upgrade NX2 firmware does not work if done
immediately after a successful update.
Cause:
A depending TCL library does not work if
being initialized more than once.
Change:
Create new thread to use TCL library so that
TCL is only initialized once..
Impact:
CIM_SoftwareInstallationService.
Enhancements:
=============
1. Request: Support upgrading of L2 device Firmware for
Xinan.
Change:
Added L2 firmware instances in CIM_SoftwareIdentity.
Support passing of such SoftwareIdentity to
InstallFromURI method.
Impact:
CIM_SoftwareInstallationService
2. Request: Support TFTP as URI for InstallFromURI() method
Change:
Added support of downloading firmware image from
given TFTP URI.
Impact:
CIM_SoftwareInstallationService
3. Request: Support iSCSI Firmware upgrade options
Change:
Added new supported InstallOptionsValues
"-c", "-p", "-cp}.
Impact:
iSCSI firmware upgrade
Version 11.0.18 (October 12, 2008)
---------------------------------
Enhancements:
=============
1. Request: Support Software Update Profile
Change:
Added CIM_SoftwareInstallationService and
CIM_SoftwareInstallationServiceCapability.
Implemented InstallFromURI() method to
perform firmware upgrade.
Currently only supports URI as local file.
Impact:
none
Version 11.0.17 (September 26, 2008)
---------------------------------
Fixes:
======
1. Problem: Cont00037538 - WMI: BRCM_OOB Data does not match
with DASHManCon
Cause:
Some properties are expected to be different;
CurrentDateTime was set incorrectly.
Change:
Fixed CurrentDateTime.
Impact:
BRCM_OOBManagementService.
2. Problem: Cont00037540 - CIM_RedundancySet class instance fails
and WMI CIM studio reports error message .
Cause:
A previous attempt to optimize the code caused
problem during memory deallocation.
Change:
Use an alternative way so that memory can be
deallocated properly.
Impact:
CIM_RedundancySet.
3. Problem: Error occured when trying to get associations from
a non-broadcom ethernet port.
Cause:
Function that checks if adapter participates a team
returned failure for 3rd party adapter.
Change:
If the adapter is not Broadcom, continue as a
3rd party adapter.
Impact:
Associations to EthernetPort.
Version 11.0.16 (September 22, 2008)
---------------------------------
Enhancements:
=============
1. Request: Build with Broadcom TruManage SDK v1.10.0.
Change:
Build with Broadcom TruManage SDK v1.10.0.
Impact:
none
Version 11.0.15 (September 19, 2008)
---------------------------------
Enhancements:
=============
1. Request: CIM_ExtraCapacityGroup is deprecated in the current
CIM schema. Need to update teaming implementation
with current CIM classes.
Change:
CIM_RedundancySet is used instead to represent a
Broadcom Team, conforming to Broadcom's Ethernet Port
Extension Profile. BRCM_EthernetPort represents both
Broadcom and 3rd party NICs.
Impact:
Ethernet Port / Teaming
2. Request: User account management capability.
Change:
Implement Simple Identity Management Profile and
Role Based Authorization Profile.
CIM Schema upgraded to 2.19
Impact:
New classes introduced by the new profiles.
3. Request: Add new property WSIdentifyOnly to
BRCM_OOBManagementHTTPSetting class.
Change:
Added new writable property.
Impact:
BRCM_OOBManagementHTTPSetting
Version 11.0.14 (August 1, 2008)
---------------------------------
Fixes:
======
1. Problem: No instance of CIM_OOBAlertService for Soledad.
Cause:
Instances were created based on legacy NIC with ASF.
Change:
Handle both legacy and Soledad.
Impact:
Soledad / CIM_OOBAlertService.
2. Problem: CIM_OOBAlertService has wrong values in properties
MessageFormat, RetryCount, PresenceHeartbeatCapable,
and EnablePresenceHeartbeats.
Cause:
Those properties were hard coded with the wrong value.
Change:
Changed to the appropriate values.
Impact:
CIM_OOBAlertService.
3. Problem: Change of EnablePresenceHeartbeats property in
CIM_OOBAlertService cannot be saved.
Cause:
Value was hard coded.
Change:
Save the new value.
Impact:
CIM_OOBAlertService.
Version 11.0.13 (July 14, 2008)
---------------------------------
Fixes:
======
1. Problem: Cont00036312 - DASH - Broadcom wmi provider -
wmitools application hang when trying to change
value of BRCM_OOBManagementSecureRMCP.OperatorRights.
Cause:
Deadlock when trying to open object for read while it
is already opened for write.
Change:
Use scope so that object is closed before opening it
again.
Impact:
DASH BRCM_OOBManagementSecureRMCP.
2. Problem: AdministratorKey, OperatorKey, and IntegrityKey cannot
be saved.
Cause:
Legacy conversion function was used to handle the keys.
The function does not apply in the current WMI Provider.
Change:
Set the key as is entered from CIM studio.
Impact:
DASH BRCM_OOBManagementSecureRMCP.
3. Problem: Cont00036315 - DASH - Cannot send ws-man enumerate
command after using WMI provider to change
BRCM_OOBManagementHTTPSSetting.port value
Cause:
Some flags were unintentionally cleared when saving
DASH settings.
Change:
Set the flags correctly.
Impact:
DASH
Version 11.0.12 (July 2, 2008)
---------------------------------
Fixes:
======
1. Problem: Changes in DASH settings are lost after Provider is
reloaded.
Cause:
Changes were not written to NVRAM when saving.
Change:
Write to NVRAM when changes are saved.
Impact:
DASH.
Version 11.0.11 (June 20, 2008)
---------------------------------
Fixes:
======
1. Problem: Cont00035990 - CIM test: IP address, Gateway,
DNS and Subnet does not show in BRCM_OOB..IPv4Setting
and IPv6Setting of WMI CIM Studio. But it works fine
in BACS.
Cause:
getnameinfo() used to format IPv4 and IPv6 address
returned error because WSAStartup() was not called.
Change:
Added WSAStartup() and WSACleanup().
Impact:
BRCM_OOBManagementIPv4Setting and
BRCM_OOBManagementIPv6Setting.
Version 11.0.10 (June 19, 2008)
---------------------------------
Fixes:
======
1. Problem: Cont00035971 - DASH - In band instance for
BRCM_OOBManagementIPv6Setting contains incorrect
address
Cause:
IPv6 address was read as IPv4 address.
Change:
Format string as IPv6 address.
Impact:
BRCM_OOBManagementIPv6Setting.
Version 11.0.9 (June 11, 2008)
---------------------------------
Enhancements:
=============
1. Request: Remove Broadcom Ethernet Port Extension Profile.
Change:
Revert back to use CIM_ExtraCapacityGroup for teaming.
Impact:
all
Version 11.0.8 (June 8, 2008)
---------------------------------
Enhancements:
=============
1. Request: Cont00035747 - DASH - Add WMI support on Soledad.
Change:
Upgraded to CIM schema 2.18.
Conform to Profile Registration Profile.
Conform to Software Inventory Profile.
Conform to Ethernet Port Profile.
Conform to Broadcom OOB Management Profile.
Conform to Broadcom Ethernet Port Extension Profile.
Impact:
all
Version 11.0.7 (April 23, 2008)
---------------------------------
Enhancements:
=============
1. Request: Support 57710 with external PHY.
Change:
Added 57710 support with external PHY.
Impact:
all
Version 11.0.6 (December 21, 2007)
---------------------------------
Fixes:
======
1. Problem: Cont00033200 - Able to run diagnostics while logged in as
a non-admin user
Cause:
Did not check for administrator access.
Change:
Added check for administrator access.
Impact:
all.
Version 11.0.5 (December 17, 2007)
---------------------------------
Enhancements:
=============
1. Request: Support 57710.
Change:
Added 57710 support.
Impact:
all
Fixes:
======
1. Problem: Cont00032869 - wmi application hangs when saving changes of
BRCM_ASFOOBAlertService class with CIM 11.0.4.
Cause:
Last fix included unnecessary code which opens an object
the second time for write, causing deadlock.
Change:
Remove unnecessary code which caused deadlock.
Impact:
all.
Version 11.0.4 (December 7, 2007)
---------------------------------
Fixes:
======
1. Problem: Cont00032611 - The RedundancyStatus property is not showing
the right value.
Cause:
Algorithm to determine RedundancyStatus was wrong.
Change:
Corrected algorithm to determine RedundancyStatus.
Impact:
all.
2. Problem: Cont00032869 - Unable to save changes to values with
CIM 11.0.3 to BRCM_ASFOOBAlertService class.
Cause:
Certain properties were not handled during ModifyInstance.
Change:
Save all properties.
Impact:
all.
Version 11.0.3 (November 30, 2007)
---------------------------------
Enhancements:
=============
1. Request: Support customized DiagnosticSetting when calling RunDiagnostic
on BRCM_DiagnosticTest.
Change:
Implemented CreateInstance, ModifyInstance and DeleteInstance
for DiagnosticSetting class according to CDM Profile 1.0.0b.
Implemented option to write resulted class instances to file.
Implemented record filtering using LogOptions property of
DiagnosticSetting.
Impact:
all
Fixes:
======
1. Problem: Cont00032611 - The RedundancyStatus property is filled in
with a status of 2, but does not change when disconnect
adapters in team.
Cause:
Function that determines the RedundancyStatus value was
checking the wrong field against the wrong flag.
Change:
Check the correct field against the correct flag.
Impact:
all.
2. Problem: Cont00032779 - Different values when comparing CIM 6.3.2
with CIM 11.0.1 for BRCM_ASFOOBAlertService.
Cause:
Some values needed byte swapping.
Change:
Added byte swapping to the appropriate property values.
Impact:
all.
Version 11.0.2 (November 21, 2007)
---------------------------------
Enhancements:
=============
1. Request: Conform to CDM Profile 1.0.0b (CIM 2.9 schema).
Change:
Changed implementation to CDM Profile 1.0.0b with
CIM 2.9 schema.
Impact:
all
Fixes:
======
1. Problem: Cont00032611 - WMI/CIM: Redundancy Field says <empty>,
when it should say either 2, 3, or 4 when a team is present
Cause:
Property was not populated.
Change:
Fill in the RedundancyStatus property.
Impact:
all.
Version 11.0.1 (November 9, 2007)
---------------------------------
Enhancements:
=============
1. Request: New Broadcom WMI Provider conforming CIM 2.11 schema.
Change:
Initial release of BRCM_WmiProvider.
Requires BMAPI 7.6.12 (included in the package).
Impact:
all
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.