release.txt Driver File Contents (

                              Release Notes

         Broadcom Manageability Configuration and Control Utility
                 Copyright (c) 2012 Broadcom Corporation
                          All rights reserved.

Version 1.54.1 - August 2, 2012
   1. Problem (CQ 64895):
      When run on Windows XP (or Windows Server 2003) or older unsupported
      versions of Windows, the application would fail with the error message:
      "The procedure entry point inet_pton could not be located in the dynamic
       link library WS2_32.DLL"

      The previous release (1.54.0) for Windows was built using the latest
      Microsoft development tools which target Windows Vista+ by default,
      which includes a version of WS2_32.DLL that has the "inet_pton"
      function. Older versions of Windows include a version of WS2_32.DLL
      which does not have the "inet_pton" function, so the dependency cannot
      be met and the application fails on those older versions of Windows.

      Use our own implementation of the "inet_pton" function as we did in
      releases prior to 1.54.0.

      Windows XP/2003 and older versions of Windows.

Version 1.54.0 - July 17, 2012
   1. Problem (CQ 64149):
      The "sync" command on Windows 8 systems running in UEFI BIOS Mode would
      fail to read the system's SMBIOS EPS and Structure Table and report the
      following error:
      !Error 1 getting system firmware table (retval=0) from 00000000000E0000

      Microsoft has removed support for the "raw firmware table provider"
      in Windows 8, when running in UEFI BIOS Mode.

      Change (BMCFG Library revision 156):
      Eliminate the use of the Microsoft "raw firmware table provider" to
      obtain the system's SMBIOS EPS (Entry Point Structure) and instead 
      formulate the SMBIOS metadata (e.g. version, total structs, max struct
      size), previously obtained via the EPS, from the data provided by the
      Microsoft "raw SMBIOS firmware table provider".

      Windows running in UEFI BIOS Mode.

   2. Problem (CQ 64581):
      The "view -v -record=smbios" will crash if the SMBIOS record is empty.

      Failure to check result of SMBIOS library initialization function (which
      fails when passed an empty table) before calling the SMBIOS library
      function to display the table contents verbosely.

      Check the SMBIOS library initialization function result and if it fails,
      do/display nothing.

   3. Problem:
      The "sync" command would not populate the cim_compsys_element_name and 
      cim_compsys_primary_ower_name configuration properties, as the
      BrcmMgmtAgent does.

      Code was inadvertently excluded from build.

      Include the code which mimics the behavior of BrcmMgmtAgent on Windows.

      Windows only.

   4. Problem:
      The embedded file description resource (in bmcc.exe) had the wrong text:
      "Broadcom Management Configuration and Control Utility" instead of
      "Broadcom Manageability Configuration and Control Utility".

      Windows only.

   5. Problem (CQ 63374):
      When using the "sync" command on systems running the Microsoft Windows
      NT 6.2-based operating systems (i.e. Windows 8 and Windows Server 2012),
      the CIM_OperatingSystem.OSType property value would not be initialized
      (e.g. would be left with previously correct OSType value or 0).

      The CIM_OperatingSystem.OSType value for Windows NT 6.2-based
      operating systems was not yet defined by the DMTF at the date of the
      previous release.

      If Windows NT 6.2 Workstation (Windows 8) is detected, set the reported
      OSType value to the appropriate value (i.e. 114 for 32-bit or 115
      for 64-bit). If Windows NT 6.2 Server is detected, set the reported
      OSType value to 113 (Windows Server 2012) and if the detected Windows
      version does not have a known DMTF-defined value, then the value 18
      (WINNT) is used for the reported OSType value.
      Windows 8 and Windows Server 2012.

   1. The Windows version of this program is now dependent on the Microsoft
      Visual C++ 2010 run-time library file: MSVCR100.DLL.

      The Broadcom MgmtApps Installer for the NetXtreme 15.4 release for
      Windows is expected to install this file on the system automatically if
      it is not already present (CQ 64630).

      Windows only.

   1. The "sync" command will no longer fail because configuration records
      (e.g. IPv6) don't already exist - same behavior as BrcmMgmtAgent.

Version 1.52.0 - February 22, 2012
   1. The "import=filename -record=smbios" command now imports a combined
      SMBIOS structure table/EPS into the correct records (the opposite of 
      the "export=filename -record=smbios" command).
      The "smbios=filename" command is still supported, but now undocumented
      and deprecated.

   2. Added "scrub" command (similar to the new B57diag 'mancfg -S' command)
      which can be used to prepare a configuration record set for duplication
      (removes all sensitive and system-specific information).

Version 1.50.0 - November 30, 2011
   1. Problem (CQ 59936):
      If the platform's SMBIOS structure table exceeds 5004 bytes in size,
      the application may crash while importing the SMBIOS structure table.

      BMCFG library SMBIOS import function contained a bug which would
      corrupt memory if the SMBIOS structure table to be imported (from
      system memory or file) exceeded the pre-allocated storage (5004 bytes)
      in the management configuration record set.

      Use new BMCFG library (revision 151) which includes the fix
      (initially for CQ 59543) to build the application.

      Platforms whose SMBIOS structure table exceeds 5004 bytes in size.

   1. Added support for exporting the SMBIOS structure table and meta data
      from a configuration record set to a SMBIOS binary file (with pseudo EPS
      suitable for importing with BMCC) using the command-line:
          "bmcc export=smbios.bin -record=smbios"

Version 1.48.1 - June 10, 2011
   1. Problem (CQ 55711):
      Linux BMCC returns:
      "!BMAPI ERROR 255 Finding Broadcom Management/Network Controller"
      for most commands.

      Linux version was accidentally built with Windows BMAPI.h, so the
      BMCC version 1.48.0 CQ 55626 part 2 fix was not applied because
      BMAPI_DEVICE_IS_NOT_UP is not defined in the Windows BMAPI.h file.

      Complied with the Linux version of BMAPI.h file instead of the Windows

      Impact: Linux only.

      Note: BMAPI-Linux v6.10.1 must be used (or an "ERROR 51" is returned).

Version 1.48.0 - May 18, 2011
   1. CQ 55626 part 1:
      Occasional failure of "status", "verify" and other potential commands
      with "ERROR 63".

      The enhancement introduced in the previous release did not entirely
      eliminate the possibility of certain BMAPI functions failing due to
      conflict with another process (e.g. BrcmMgmtAgent) having the controller
      locked for exclusive access.

      Added finite retries of *all* BMAPI function calls which can return
      error 63 (BMAPI_LOCK_NIC_FAILED) upon conflict with another process using

   2. CQ 55626 part 2:
      When used in a Linux system with multiple Broadcom controllers, if one of
      them was "down", all commands would fail with an error:
      "BMAPI ERROR 255 Finding Broadcom Management/Network Controller".

      The enhancement introduced in the previous release did not retry upon
      BmapiGetFirmwareInfo() returning the error 255 (BMAPI_DEVICE_IS_NOT_UP)
      whereas previous versions would.

      When any BMAPI operation on a controller returns error 255
      (BMAPI_DEVICE_IS_NOT_UP), the controller will be skipped in the search
      for the relevant management controller.

      Impact: Linux only.

Version 1.46.1 - May 11, 2011
   1. Added a finite retry mechanism (up to 5 seconds) for situations where
      another process has the NIC/management controller locked for exclusive
      access (e.g. NVRAM reads and writes).

      This enhancement should greatly reduce the likelihood of this program
      returning error 51 (BMAPI_NIC_NOT_FOUND), when in fact there is a
      capable/configured management/network controller present in the system.

Version 1.46.0 - January 14, 2011
   1. CQ 51879:
      Added support for viewing/editing of Locally Administered ("soft") MAC
      address in "edit" Advanced sub-menu.

Version 1.43.2 - September 20, 2010
   1. "view -instance=1" now displays all instances (since no record type was
      specified, the specified instance value is ignored). The previous
      behavior was unintended.

   1. Added support for importing from and exporting to ".ini" files:
      - Text files in Windows ".ini" file format which may be created or
        modified using ASCII text editors (e.g. notepad).
      - Supports configuration data, web files, and opaque management data.
      - Primarily used for importing OEM State Set(s) for PLDM State Sensor
      - May be used instead of binary ".cfg" files when desirable.

   2. "verify" command enhancements:
      A. Display a warning if the configuration data consumes all allocated
      B. Verify Web Data and Opaque Management Data storage and configuration
      C. New warnings displayed for "unrecognized record types" and
         "duplicate property IDs" in configuration data.

   3. "status" command enhancements:
      A. If firmware is not enabled, still display NVRAM usage details.
      B. Display more details about NVRAM usage (config data used, opaque
         management data used, web files, etc.)

   4. Added "-debug" option to display all BMCFG library call results.

   5. "view -verbose" command will now display encrypted property stream
      records when used with "-decrypt" option.

Version 1.42.2 - May 27, 2010
   1. When using the "edit" command, typing '5' (with no parameter value) at
      the User Role Settings prompt would cause the program to crash.

   1. Restored the "recycle" command, used to force the BrmcMgmtAgent (v1.42.2
      if running) to immediately synchronize the configuration between host
      and management firmware.

      Requires BrcmMgmtAgent v1.42.2 (for Linux or Windows) to function.
   2. The "sync" command now more closely mimics the behavior of BrcmMgmtAgent
      in that it will enable or disable IPv4 or IPv6 if enabled/disabled in
      the host OS network configuration.

Version 1.42.1 - April 23, 2010
   1. Problem (CQ 47259):
      The management configuration does not get the system's configured
      DNS name servers (primary and secondary) from the configuration
      (they remain at their previously configured values).

      Error parsing the /etc/resolv.conf file. Not zeroing out the name server
      addresses before attempting to read them.

      Fixed parsing of the /etc/resolv.conf file. Zero-out name server
      addresses before attempting to read them from the /etc/resolv.conf file.

      "sync" command on Linux only. "brcmMgmtAgent" also affected.

   2. Problem (CQ 47061):
      CIM_OperatingSystem.OSType value is incorrect for 64-bit Linux systems
      e.g. SLES11 SP1 x64 will show the OSType as 84 when it should be 85
      and Red Hat 5.5 x64 will show the OSType as 79 when it should be 80.

      64-bit variants of Linux operating systems were not detected correctly.

      Fixed detection of 64-bit Linux variants.

      "sync" command on Linux-x64 only. "brcmMgmtAgent" also affected.

   1. Propagate the Linux DHCPv6 client DUID value to the IPv6 configuration
      record so we can use the same value in the firmware DHCPv6 client.

      "sync" command on Linux only.

Version 1.42.0 - April 2, 2010
   1. Problem:
      If an imported record set file (e.g. dashfw.cfg) contained encrypted
      records, the record stream would not be successfully verified
      (e.g. "Invalid Watermark").

      Device crypt keys were not used with the import-from-file commands.

      add, merge, replace, and web commands.

   1. Display the adapter's configured MTU along with the MAC and IP address.

   2. Added support for exporting web data files from NVRAM or configuration
      file to a local directory. Example: "bmcc export=<dir> -record=webdata".

      Currently limited to a single directory depth (no sub-directories).

   3. Added support for Linux x86 and x64 (requires BMAPI-Linux, v6.7.0+).

Version 1.40.0 - February 3, 2010
   No Changes.

Version 1.39.0 - January 12, 2010

   1. Fix "-scan" option fix #2 in v1.24.2:
      Would not always locate configuration record set in file.

   1. Support "verify -verbose" to display record headers.

   2. Display record ordinals ("type:ordinal") in more output.

   3. "Verify" command now verifies encrypted property stream records
      (in NVRAM, not files).

   4. Change clear/remove/delete/encrypt/decrypt commands to display what's

   5. Display warning when exporting encrypted records with "export" command.
      (and not using the -decrypt option).

   6. Verify checksum of VERSION record to stop false-positives when using
      '-scan' option.

Version 1.24.5 - November 6, 2009

   1. Problem (CQ 44319):
      Unable to import files under some conditions with error message:
      "bmcfgImportRecord returned -5"

      Some older configuration record sets may contain deleted (null) records
      with stale header values (e.g. non-zero attr value). When importing
      a non-property stream into a deleted record that had a stale attr
      value that indicated it was a property stream record, the property
      stream validation would fail and the import would be aborted with error

      When configuration records are marked deleted (converted to null
      records), the headers are normally zeroed-out, but older BMCFG library
      revisions did not do this. The BMCFG library now handles this situation
      gracefully if/when it reuses such records for newly created/imported

      Updated "verify" command to display warnings when deleted (null) records
      with non-zero record header fields are detected. 

   1. Detection of incorrectly encrypted configuration record sets using a new
      "watermark" configuration record.

      If a configuration record set with encrypted records is exported to a
      file and then imported into a different network/management controller,
      the record set will fail verification and newer B57diag and BMCC
      versions will disallow the importation (rather than just silently
      reverting encrypted records back to their default or auto-generated
      states as would previously happen). The management firmware will also
      detect an invalid watermark and report/log an error.

   2. Including a resources in the .exe file to identify the publisher
      (Broadcom), version, etc., but most importantly to include a manifest
      which prevents the program from being executed on Windows Vista+ by a
      user without administrator privileges.

   3. The "status -verbose" command will now display the contents of the 
      APE debug log which may be used for advanced on-site debugging
      capability (equivalent of the B57diag 'apeinfo -l' command).
   4. Added "-decrypt" option they may be used in combination with the
      view (-v), dump, and export commands.

      Encrypted records that are exported with the "-decrypt" option will have
      the new "DEC" (decrypted) attribute flag set indicating that the record
      should be re-encrypted when imported (with the import, add, merge,
      or replace commands).

      The "DEC" attribute should not normally be set on records contained in
      NVRAM and the "verify" command will display a warning under such

      Using the "export" command without the "-decrypt" option will display
      warnings for any encrypted records found.

   5. The "import" command no longer exports/imports web data (faster import).

   6. Display record headers when the create, import, or export commands are
      used with "-verbose" option.

   7. The "verify" command will now display warnings for unexpected or invalid
      attribute combinations.

   8. The "verify" command will now display warnings if the VERSION or
      WATERMARK records are not included in the record set.

Version 1.24.4 - October 23, 2009

   1. Problem:
      When using the "create -record=xx" command line, Opaque Management Data
      and Web Data storage directory entries would be removed from the
      controller's NVRAM.

   1. Added meaningful (US-English only) descriptions of BMCFG library
      function return values to the numeric error values already displayed and
      indicate when numeric error values are BMAPI errors (with no

Version 1.24.3 - October 19, 2009

   1. Problem:
      When using the "edit" command to edit the 802.1X configuration, the
      username value would be truncated (at 2 characters) and garbage would
      be displayed following the first 2 characters of the username value.

      Build file dependency problem caused older/smaller 802.1X configuration
      record structure to be used for storage of configuration parameters.

      Updated file dependency mapping and performed clean rebuild.

Version 1.24.2 - October 16, 2009

   1. Problem:
      If a configuration record had to be enlarged (e.g. to accommodate a
      newly added property), and the record could be enlarged without moving
      it (changing its offset in the configuration record set) due to adjacent
      null/deleted records, the record length in the record header would not
      be updated to the new larger size required for the new data.

      Most configurations do not normally include null records, so sightings
      of this problem would not be common.

   2. Problem:
      Using -scan option with a configuration record set that was located in
      the NVRAM image at a byte offset that was not evenly divisible by 16
      would fail to locate the configuration record set.

      Broadcom Manageability Configuration and Control Utility v1.24.1
      Reading configuration records from \NVRAM.BIN
      File size: 1048576 bytes
      Configuration record set not found in \NVRAM.BIN

      "APE Config" directory entry is not always at an NVRAM address (byte
      offset) that is evenly divisible by 16.

      Look for a BMCFG "version" record every 4 bytes rather than every 16
      bytes in the passed file (e.g. NVRAM image).

Version 1.24.1 - October 9, 2009

   1. Problem (CQ 43969):
      Attempting to import a 2MB file (using the "import" command) will cause
      BMCC to crash.

      If bmcfgImportRecord() was called with length of greater than 1MB or so,
      a stack overflow condition could occur causing application to crash.

      In BMCFG Library bmcfgImportRecord() function:
      Allocate heap memory rather than stack memory for imported file content

   1. Updated "802.1X Authentication" configuration menu to add support for
      EAP-MSCHAPv2 toggle option and "username" field (for use with EAP-TTLS).

   2. Added support for optional configuration record type 0x03 
      (BMCFG_RECORD_BANNER) for text console redirection (Telnet or SSH)
      banner text.

Version 1.24.0 - September 24, 2009

   1. Added "802.1X Authentication" configuration menu to enable and configure
      the management firmware's 802.1X authentication feature and added
      support for importing/exporting/viewing/dumping the 802.1x and
      802.1x_cert configuration records.

   2. Added "-nocfgchevent" option to prevent BMCC from asserting an APE 
      "config change event" upon saving the configuration record set to NVRAM.
      This option is useful for preventing the firmware from automatically
      regenerating a private key/certificate pair upon detecting a mismatch
      when importing a private_key (50) or server_cert (51) configuration
      record in 2 BMCC operations.

      Example: bmcc import=cfr_pkey.der -record=private_key -nocfgchevent
               bmcc import=cfr_cert.der -record=server_cert

   3. When using the "import" command to import the private_key or any of the
      certificate configuration records, if the filename being imported has a
      ".pem" suffix/extension, then the contents will be PEM-decoded
      (in Privacy-enhanced Electronic Mail format).

   4. Added "-base64" option for importing configuration records from Base64
      encoded files.

      This option has no effect when importing .PEM files as they are always

   5. Default record attribute value (if no "-attr" option is specified) is
      now "no change to existing value" instead of "no attributes". When
      creating a new record and no "-attr" option has been specified, then
      "no attributes" will be applied to the newly created record (same as

   6. Support multiple occurrences  of the '-attr' option to specify multiple
      attribute flags by name (e.g. "-attr=enc -attr=prop" is the equivalent
      of "-attr=5").

Version 1.23.2 - August 26, 2009

   1. When modifying multiple-instance configuration records
      (i.e. accounts, roles, event subscriptions, OMData instances, and SMBus
      interfaces) with the "edit" command, records are access by ordinal
      rather than by instance number which resolves potential issues and
      confusion when editing configuration record sets with "holes" in the
      ordinal sequences or when record instances are re-ordered (e.g. due to
      size increase) when writing modified records back to the record set.

   2. When using the "edit" command to modify multiple-instance configuration
      records, the "Delete a ... record" and "Add a ... record" menu items are
      now automatically removed/disabled when there are no records of the
      relevant type or too many of the relevant type in the record set

   3. Linked with bmcfgLib revision 123 which includes more "record by
      ordinal" creation, retrieval, and modification improvements.

Version 1.23.1 - August 11, 2009

   1. Problem (CQ 40372):
      Error "!bmcfgImportSMBIOS returned 20" or 
      "!bmcfgImportSystemSMBIOS returned 20" when used on Windows Vista.

      Dependant device driver file BASFND.SYS is no longer being installed
      on Windows Vista due to a Windows Logo certification issue.

      Use Vista API to read system SMBIOS EPS and structure tables instead
      of BmapiGetBIOS() function.

   1. Added '-scan' option to search a file (e.g. NVRAM image file) for a
      valid configuration record set to verify or display.

Version 1.23.0 - July 10, 2009

   Linked with TruManage SDK (v1.23.0).
   This version should be used in combination with BMCC v1.23.0 and BCM5761
   management firmware v1.23.x.x.

   1. Problem (CQ 40452):
      Log command will return successful when there is no log in NVRAM.

      No method available to pass low level success or failure result back
      to host application (e.g. in this case, BMCC).

      New BMCTRL Library and management firmware (v1.23.x.x) adds support
      for event results that can be checked for success or failure. The
      "log" and "clearlog" commands now check this result (when used with
      firmware v1.23.x.x or later) and display "success" or "failure".

   1. Added support for "-ordinal" option and "-record=<type>:<ordinal>"

   2. "verify" command improvements:
      Displays a warning if it detects a header with no ordinal specified.
      Checks Account and Role record ordinal property values against header
      ordinal value.

   3. "status" command improvements:
      Added parsing and display of APE Firmware Build Flags.
      Added parsing and display of APE Event Result and Result Count fields.

   4. Added support for configurable PLDM/MCTP sensor aggregator SMBus
      Address (for PLDM "GetSensorReading" support over MTCP).

   5. Added support for Active Directory Role/Identities to owners of and
      have read/write permissions to Opaque Management Data instances
      (not yet supported in management firmware).

Version 1.22.0 - June 12, 2009
   1. Problem (CQ 42008):
      Importing a smaller SMBIOS structure table into a configuration record
      set would result in a configuration that would trigger a warning
      message when the 'bmcc verify' command was used to verify the
      configuration record set.
      !Warning: Record type 11 @00070: unused byte 07DF is non-zero (4A)

      A portion of the pre-existing, larger, SMBIOS structure table was left
      in the configuration record (not zeroed-out).

      In the BMCFG library bmcfgPutSMBIOSStructsRecord function:
      Zero-out unused portion of SMBIOS structure table configuration record
      when writing an SMBIOS structure table to the configuration record set.

Version 1.21.0 - May 27, 2009
   1. Added support for creating or modifying property values (contained
      in existing property stream records) on the command-line using the
      new "prop" command. See readme.txt for details.

Version 1.20.5 - April 29, 2009
   1. Problem (CQ 40649):
      "sync" command does not import any data when run on Windows XP.

      Windows XP does normally support IPv6, so it does not normally have the
      HKLM/System/CurrentControlSet/Services/Tcpip6 registry key.

      If the Tcpip6 registry key is not present, do not report error and

   1. CQ 40784
      Added support for web .sjs files (for dynamic/server-parsed JavaScript
      files) to help address this problem in OEM's web data.

   2. SMBIOS dumps now include the "description" field for structure type 27
      (Cooling Device).

Version 1.20.4 - April 17, 2009
   1. Problem (CQ 40638):
      When updating property stream records, if the existing property stream
      length was larger than the length required to store the properties
      supported, existing property values may be truncated and some properties
      not written or updated in in the record. This causes the newly updated
      bmcfgVerifyBuf() routine to report an error with the effected record.

      BMCFG library did not handle the updating of larger than required
      property stream records. This caused backward and forward compatibility
      issues (e.g. the minimum os_info record size shrank from TruManage 1.1
      to 1.2).

      Change (in BMCFG library):
      The data length of updated property stream records is dynamically
      calculated based on the requirements of existing and added or updated

   2. Problem:
      When updating encrypted records or shrinking existing record data,
      non-zero unused data bytes would be created.

      Change (in BMCFG library):
      When updating records, unused data bytes were not zeroed-out. If the
      new data length was smaller than the existing data length, then the
      stale (previously used) data byte values would remain.

      BMCC "verify" command will display warnings when non-zero unused data
      bytes are detected in records (as of v1.20.3).

   1. "sync" command may now be run against a configuration file.
      Note: IPv4, IPv6, and sw_info records and current date/time not updated.

   2. "verify" command will now display warnings for unencrypted property
      stream records whose data length does match the calculated length
      required for the properties in the record.

Version 1.20.3 - April 16, 2009
   1. Problem:
      If the IPv6 configuration record was encrypted, the "sync" command would
      revert the record to non-encrypted.

      BMCC was inadvertently stripping the "encrypted" configuration record
      header attribute flag when saving changes made to the ipv6 record via
      use of the "sync" command.

      Make no changes to the ipv6 configuration record header attribute value 
      when updating the configuration record in NVRAM.

   2. Problem:
      Updating corrupted property stream records could cause corruption of
      adjacent configuration records.

      The BMCFG library did not sufficiently validate the length of
      properties to be updated in property stream records before updating
      their values, so updating the properties of corrupted (e.g. falsely
      decrypted) property stream could cause adjacent records to be

      The BMCFG library now validates the lengths of properties before
      updating their values in configuration records thus preventing
      corrupted property stream records from causing the corruption of
      adjacent records (headers and data) in the configuration record set.

   1. When using the "view" or "dump" commands, the record header information
      is now displayed in a more human-friendly format, consistent with the
      updated B57diag 'mancfg -v' command output format.

   2. The "verify" command now displays a warning when unused record data
      bytes are non-zero, indicating likely record set corruption.

Version 1.20.2 - April 1, 2009
   1. Problem:
      "create" command would import the current Operating System information
      (type, version, total physical memory, time zone) into the configuration
      record set. Often this configuration record set would be stored in a
      file that would then be installed in management controllers in other
      systems where the OS and time zone values were not necessarily correct.

      The "create" command no longer calls bmcfgImportOsInfo().

      Use the "sync" command after the "create" command if you wish the record
      set to include the current Operating System information.

   2. Problem:
      "sync" command did not import system's current SMBIOS structure table
      and ASF system description table into the configuration record set.

      The "sync" command now calls bmcfgImportSystemSMBIOS() and

      Normally the BrcmMgmtAgent is used for this function, but for testing,
      it is best to have this command perform as closely to the same as
      BrcmMgmtAgent as possible.

   3. Problem:
      "recycle" command does not work (reports an error) when running
      BrcmMgmtAgent as an NT service.

      Deprecated the command and removed it from the help display and
      readme.txt file.

      This command is not really needed as there are other methods available
      to externally trigger a BrcmMgmtAgent cycle (e.g. pause and continue the

   1. Added "log=<text>" and "clearlog" commands (with "-audit option") to
      perform host-generated Event Log and APE Event Message testing.
      See updated readme.txt for details.

      Intended for help with verifying CQ 40241.

   2. Added APE shared memory "HOST" segment details in BMCC "status" command
      output when the "-verbose" option is used.

      Intended for help with verifying CQ 40241.

Version 1.20.1 - March 27, 2009
   1. Problem:
      "sync" and "settime" commands would set the time zone name property
      value to "PST" or "PDT" always (regardless of the system's time zone)
      and would apply a one hour Daylight Savings Time bias when daylight
      savings time was in effect, regardless of the correct DST bias for the
      system's time zone.

      The method for querying the system's time zone name was flawed. This
      property is not used in the management controller for any purpose and
      has now been deprecated.

      If the C 'daylight' variable was non-zero then the one hour was added
      to the current time zone bias regardless of the actual correct time
      zone daylight savings time bias.

      1. The current system time zone is now queried from Windows whenever the
         current system (local time) is propagated to the management
         controller (using the new bmctrlGetSystemTime() function of the
         BMCTRL library).
      2. The BMCTRL and BMCFG library routines no longer recognize or populate
         the "tz_name" property of the "os_info" configuration record.

Version 1.20.0 - March 12, 2009
   1. Added Active Directory configuration options to User Account Management
      and Web-based Management sub-menus in the "edit" command.

      Requires BCM5761 Management Firmware v1.19.10 or later to utilize.

   2. "sync" command now support IPv6 network settings propagation.

   3. Added VAUX "Lowest Speed Advertised" option to advanced "edit" menu.

   4. Create an "Auditor" account record in the default configuration record
      set (with the "create" command).

Version 1.19.0 - February 13, 2009
   1. Option to disable support for anonymous WS-Identify requests on the
      /wsman URI (to avoid warning in DMTF DASH CTS).

      Enabling this option prevents some DASH management consoles from being
      able to discover the MAP.
      Requires firmware v1.19 or later.

   2. Added Event Log and Audit Log configuration settings.

      Requires firmware v1.19 or later.

   3. Added support for "receive all IP fragments" advanced option
      (default: disabled).

   4. Added support for new DHCPv6 configuration settings (e.g. DUID, Vendor
      enterprise number and class).

Version 1.11.0 - December 1, 2008
   1. Problem (CQ 38700):
      BMCC 'view -v -record=smbios' command displays first 3 fields of
      GUID/UUID value in the incorrect byte order.

      First 3 fields of GUID are stored in native (little endian) byte
      order and this must be accounted for when displaying as hexadecimal.

      Treat SMBIOS UUID field as a special multi-field type rather than a
      byte array. Display the UUID in DCE format (i.e. with braces and

   1. New "BMCC edit -> Advanced" menu option to instruct the management
      firmware to "Receive ALL packets when OS-absent".

      This option defaults to "Disabled" and should only be enabled for
      specific debugging and testing purposes.

   2. Default CIM_ComputerSystem.ElementName value is now "Computer System".

   3. Default "Operator" and "Read Only" Role privileges are now set

   4. Display repeating CIM_Role privilege bytes as '*' and allow the '*' on
      input to specify that the previous privilege byte repeats to the end
      of the privilege byte array.

Version 1.10.1 - October 3, 2008
   1. "Monitor DTR" Console Redirection option now defaults to "Disabled".

   2. DTR timeout (when monitored) is now configurable (in milliseconds) in
      the Console Redirection "edit" menu. The default DTR timeout value is
      5000 (5 seconds).

      A remote power-reset may take as long as 20 seconds, with DTR low the
      entire time, so this feature ("Monitor DTR") should normally be

   3. "Automatic Register Repair" Advanced Setting now defaults to "Enabled".

      Some network drivers may leave the network controller's registers in
      a state that does not allow out-of-band management traffic to be
      received by the management controller, so this feature should normally
      be enabled.

   4. Added "-create" option to allow empty configuration files (with only a
      version record) to be created with the various import commands.

                bmcc web=c:\webpages\ -create web.cfg
                bmcc asf -create asf.cfg
                bmcc smbios -create smbios.cfg

   5. Added add=<file>, merge=<file>, replace=<file>, and web=<file> commands
      to import one or more records from a source configuration file into a
      target configuration record set (in a file or NVRAM).

      Old merge command (for merging null/deleted records) has been deprecated
      and removed.

   6. Terminology update to user account management menus.
      Display created/offline status in user account record listing.

Version 1.10.0 - September 23, 2008
   1. When an invalid record name (or '?') is given with the "-record=<type>"
      option, a list of supported record types with their corresponding names
      is displayed.


        C:\>bmcc -record=?
        Broadcom Manageability Configuration and Control Utility v1.10.0

        Supported record types:

        Hex Name
        --- ------------------
        ff  any
        00  null
        01  ver
        02  comment
        10  smbios_meta
        11  smbios
        14  bios_meta
        15  bios_str
        16  bios_attr
        17  bios_attr_val
        18  bios_pend_val
        20  asf_info
        21  asf_alrt
        22  asf_rctl
        23  asf_rmcp
        24  asf_addr
        30  mgmt
        31  ipv4
        32  ipv6
        33  pet
        34  rsp
        35  conredir
        36  usbredir
        38  smbus
        40  account
        41  role
        48  wsevent_sub
        49  wsevent_ref
        50  private_key
        51  server_cert
        52  server_ca_cert
        53  client_ca_cert
        60  webfile
        61  webdata
        70  os_info
        71  sw_info
        80  omdata
        81  omdata_storage

   2. Terminology updates to "bmcc edit" menus for User Account Management
      and Web/HTTPS/HTTPS/WS-Eventing/Indications settings.

      Some menus no longer match existing documentation (e.g.

   3. New "Advanced Settings" menu option to Enable and Disable Zero-Touch
      Provisioning support.

Version 1.09.5 - September 16, 2008
   1. Problem (CQ 37380):
      Encrypted property-stream configuration records (e.g. user accounts)
      could not be modified. Symptoms include corrupted property values,
      property values reverting to default values, and corrupted adjacent
      records whenever such records are modified (locally or remotely).

      BMCFG library fix (in revision 79) for potential forward compatibility
      problems (older applications modifying property-streams created by newer
      applications) introduced problems with updating existing encrypted
      property-stream records. The record corruption was a side-effect of this
      bug due to improper bounds-checking in a property value update routine.

      BMCFG library fix (in revision 81).
      Requires updates to management firmware, BMCC, B57Diag, and 

   1. Added record type names for client and server CA certificate records.

Version 1.09.1 - September 12, 2008
   1. Cosmetic issues with WS-Eventing subscription edit sub-menu.

   1. Added WS-Identify Only option for HTTP connections.

   2. The "view -verbose" command will now display PLDM BIOS records (if they
      exist) in a human-readable form.

Version 1.09.0 - September 05, 2008
   1. Fix problem when no length is specified with "create -record=<type>"

   2. Problem (CQ 36572):
      The decrypt command resets account record to default settings.

      Require the -record option with the encrypt and decrypt commands.

   3. Problem:
      Could not set SMBus MCTP Endpoint ID to all legal values.

   1. (CQ 36654)
      Validate -record=<type> value and display error if an invalid record 
      type "name" is specified.

   2. Added record type names for all record types (see readme.txt).

   3. Support the -instance option with the view and dump commands.

   4. If "bmcc reset" fails (e.g. due to APE firmware hang or shutdown), 
      automatically fall-through to hard reset.

   5. Added USB Media Redirection menu (TruManage v1.1 feature).

   6. (CQ36668)
      Mask ASF RSP Keys when configuration record is encrypted.

Version 1.00.0 - June 28, 2008
   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

      The inet_addr() function used to convert the name server IP address
      string to a binary format returns -1 (0xffffffff) on failure.

      If inet_addr() returns -1, leave the name server IP address as

   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

   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

   1. Problem: (CQ 35986)
      "bmcc edit" display incorrect/corrupted IPv6 addresses.

      Build (compile/link) issue with dependant libraries.

      Clean build.

      IPv6-enabled configurations only.

   2. Problem:
      Some sequences of commands could create configuration records with an
      attribute value of 0xff.

      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.

      bmcfgGetRecordForUpdate() now creates the record with no attribute
      flags (value of 0x00) if called with an attr parameter value of 0xff

      Advanced configuration record set editing commands only.

   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

   1. Problem: (CQ 35801)
      "bmcc delete" command does not delete web and opaque management data
      from NVRAM.

      The APE_DATA and APE_WEB_DATA NVRAM directory entries cannot be removed
      via Windows applications (using BMAPI).

      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.

      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.

      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).

      "bmcc ocreate" command rounds-up the specified length as needed to be
      evenly divisible by 4-bytes.

   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

   1. Problem: (CQ 35423)
      The "remove" command does not completely remove a configuration record.

      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.
      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.

      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.

      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).

   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

How To Update Drivers Manually

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.

server: ftp, load: 1.73