Broadcom Manageability Configuration and Control (BMCC) Utility
===============================================================
Version 1.54.0
July, 2012
Background:
----------
This utility provides command-line based control and configuration of
Broadcom's TruManage standards-based (e.g. ASF, DASH, PMCI) management
controllers embedded in enterprise-class NetXtreme Gigabit Ethernet
network controllers (e.g. BCM5761).
This utility replaces the functionality of Broadcom's ASFSilentConfig
(ASFSCfg) for TruManage-enabled NetXtreme devices (e.g. BCM5761). This utility
may be enhanced to support the manageability configuration and control of
legacy (i.e. ASF-only) NetXtreme devices in the future, but currently the
support is limited to BCM5761 devices.
Use/Distribution:
----------------
BMCC is intended for use by PC OEMs and enterprise IT administrators and not
(usually) by end users. The Broadcom NetXtreme WMI Provider is the recommended
method for IT administrators to provision/configure the Broadcom TruManage
management controller.
Platforms:
---------
Windows (x86 and x64) and Linux (x86 and x64) operating systems are supported.
Dependencies:
------------
The Windows version requires:
* BMAPI.DLL (or BMAPIa.DLL for Win-x64) v7.17.12 or later and
* NDIS5 driver (e.g. b57xp32.sys) v10.83 or later or
* NDIS6 driver (i.e. b57nd60x.sys) v10.97 or later
The Linux version requires:
* BMAPI-Linux v6.7.1 or later
Usage summary
=============
usage: bmcc <cmd> [[-option] [-option] [...]] [cfgfilename]
control commands:
enable enable the management controller
disable disable the management controller
status query management controller status
sync synchronize OS/network/driver information and settings
ping determine if the management controller is alive
reset reset the management controller
shutdown shutdown the management controller
recycle recycle brcmMgmtAgent (if running)
log=<text> add text to Event Log (or Audit Log when used with -audit)
clearlog clear Event Log (or Audit Log when used with -audit)
information commands:
version display program version details
view-asf display ASF System Description Table from system memory
configuration commands:
create create a new configuration record set with default values
create=[length] -record=<type> to create a record [of specified length]
verify verify headers and data of configuration record set
view display one or more configuration records
view-asfcfg display ASF System Description Table configuration records
dump display one or more configuration records (in hex/ASCII)
clear clear the data of one or more configuration records
remove remove one or more configuration records
delete delete (do not remove) one or more configuration records
encrypt encrypt one or more configuration records
decrypt decrypt one or more configuration records
edit modify existing configuration records
compress remove unused records and data from configuration image
import=<file> import a configuration set or record from specified file
export=<file> export a configuration set or record to specified file
add=<file> add records from specified configuration file
merge=<file> merge records from specified configuration file
replace=<file> replace records from specified configuration file
asf import ASF System Description Table from system memory
smbios import SMBIOS structure tables from system memory
web=<dir> import Web files from specified directory (recursively)
web=<file> import Web files from specified configuration file
prop<id>=<val> add or modify property with specified property ID (in hex)
update update all instances of one or more prop-stream records
scrub prepare configuration record set for duplication
opaque management data commands:
ostatus display status of one or all OMData instances
ocreate=[args] create OMData storage and instance records
args=<number of OMData instances>,<total storage bytes>
oalloc=[args] allocate an OMData instance with the specified properties
args=<length>,<owner account>,<data format>,<element name>
oread display contents of one or all OMData instances
owrite write to one OMData instance
oclear clear contents of one or all OMData instances
ofree free one or all OMData instances
configuration options:
-record=<type> specify record type [e.g. in hex] (default type is "any")
-attr=<value> specify record attributes (default value is "none")
-instance=<num> specify record instance (default instance is "any")
-ordinal=<num> specify record ordinal (default ordinal is "any")
-noverify disable automatic configuration record set verification
-truncate truncate output file to minimum bytes required for records
-create create a new configuration file (truncate if exists)
-type=<value> specify property type: str|int|add|or|not|ipv4|ipv6|hex
-length=<value> specify property value length (bytes, in decimal)
-scan scan for configuration record set in specified cfgfilename
-base64 base64 decode imported configuration record
-decrypt decrypt encrypted records before viewing and exporting
control options:
-audit operate on the Audit Log instead of the Event Log
-nocfgchevent do not assert a configuration change event
general options:
-quiet suppress console output
-verbose enable more detailed output
Usage notes:
-----------
* Only one command may be specified per invocation of this utility
* Multiple options may be specified per invocation of this utility
* A configuration file (e.g. dashfw.cfg) is optional for most commands
* Optional arguments are shown in square brackets ([ and ])
* Required arguments are shown in angle brackets (< and >)
* Run "bmcc" from a command prompt to display a list of currently supported
commands and options for the version of bmcc that you have
Input and Output
================
This utility can read configuration information from the following sources:
* NVRAM
- NetXtreme Network Controller non-volatile random access memory
- Typically Flash Memory
* CFG File
- Configuration file
- Binary contents closely matching format of NVRAM contents
- May be created or edited with this utility (e.g. "bmcc edit filename.cfg")
- May contain one or more configuration records
- May contain "virtual" configuration records for web and management data
- Usually with a ".cfg" file extension/suffix
* INI File
- Initialization file
- Text contents may be created or edited with any ASCII text editor
- May contain one or more configuration records
- May contain "virtual" configuration records for web and management data
- Always with a ".ini" file extension/suffix
* PEM File
- Privacy-enhanced Electronic Mail encoded file
- Contains X.509 Certificate or RSA private key
- Only applicable to specific record types (certs and RSA keys)
- Contains a single configuration record data
- Always with a ".pem" file extension/suffix
* Data File
- Raw binary or ASCII/UTF-8 text data
- Optionally Base64-decoded (with '-base64' option)
- Contains a single configuration record data
* Web Files
- HTML and supplemental files for optional Web/HTML user interface
* ASF System Description Table
- ACPI System Description Table
- AKA "ASF!" Table
- Contains platform-internal management parameters
- Imported from system memory into controller's NVRAM
- Split into multiple configuration records
* SMBIOS Structure Table
- Contains platform component details
- Imported from binary file or system memory into controller's NVRAM
- Imported into the SMBIOS_META and SMBIOS_STRUCTS configuration records
This utility can create and/or modify configuration information in the
following targets:
* NVRAM
* CFG File
* INI File
* Data File
* Web Files
Basic commands
==============
"bmcc"
------
Display the version number and usage syntax summary (a.k.a. "help").
"bmcc version"
--------------
Display detailed version information about bmcc and its associated libraries.
"bmcc enable"
-------------
Enable the management controller if it has not already been enabled, and
start the management controller firmware if it has not already been started.
The enable state is persistent across system power-loss. This command is the
equivalent of the b57diag "setman -e" command followed-by a conditional
"apectl -R" command.
"bmcc disable"
--------------
Disable the management controller if it has not already been disabled,
and stop the management controller firmware if it is currently running.
The disable state is persistent across system power-loss. This command is the
equivalent of the b57diag "setman -d" command followed-by a conditional
"apectl -r" command.
"bmcc status"
-------------
Display the current persistent (e.g. Enabled State) and dynamic status of the
management controller.
When used with the '-verbose' option, the entire APE shared memory segment
will be dumped in 32-bit hexadecimal values.
This command is similar to the b57diag "apeinfo -m" command.
"bmcc ping"
-----------
Query the management controller firmware to test if it is capable of
responding to "events".
This command is the equivalent of the b57diag "apectl -n" command.
"bmcc edit"
-----------
View and (optionally) modify the management controller configuration values
using a text-based interactive menu system.
If a [cfgfilename] is specified on the command-line (e.g. dashfw.cfg), then
configuration records will be read-from and written-to that file. If no
[cfgfilename] is specified on the command-line, then a management-capable
NetXtreme network controller must be discovered in the system and the
configuration records will be read-from and written-to its NVRAM.
This command is the equivalent of the b57diag "mancfg" command.
"bmcc view"
-----------
View the information (headers) for configuration records contained in the
management configuration record set.
This command is similar to the b57diag "mancfg -v" command.
When used with the '-verbose' option, details about the contents of the
record will be displayed, when available (equivalent of the "mancfg -V"
command).
"bmcc verify"
-------------
Check the validity of the configuration record set. This command performs
additional sanity-checks that are not performed by the automatic verification
(which may be disabled with the '-noverify' option).
"bmcc update [-record=<type>]"
------------------------------
Set record header ordinal values, if unspecified and read and re-write all
property-stream records of the specified record type (or all property-stream
record types if no record type is specified).
This effectively upgrades a configuration record set from a previous version
to the current version, potentially eliminating many "bmcc verify" warnings
displayed when verifying an older configuration record set.
If the current record set was created or modified by a recent version of
B57diag or BMCC, then it is possible (and likely) that no actual changes to
the configuration record set will be made when using this command.
"bmcc scrub"
------------
Prepares a configuration record set for distribution or duplication by
removing all system-specific information (e.g. SMBIOS structure table) and
clearing all sensitive data (e.g. passwords, keys).
Any encrypted records with data are also decrypted so they may be imported
and used with other controllers.
Use of this command may be preferable to restoring a configuration record set
completely to default values if there are platform-specific elements which you
wish to preserve.
This command may also be used as part of the unprovisioning process for a
managed system/controller.
Advanced commands
=================
"bmcc sync"
-----------
Synchronizes the configuration file (if specified) or management controller's
NVRAM configuration settings with the current host operating system and
network stack settings.
This command provides functionality similar to that of the BrcmMgmtAgent.
"bmcc reset"
------------
Requests a graceful reset of the management controller and if that fails,
performs a hard reset.
This command is the equivalent of the b57diag "apectl -r" command.
"bmcc shutdown"
---------------
Requests a graceful shutdown of the management controller. This command does
not change the persistent Enabled State.
This command is the equivalent of the b57diag "apectl -h" command.
"bmcc [-audit] log=<text>"
--------------------------
Issues a request to the management controller to add the specified text string
(up to 20 characters) to the management controller's Event Log or Audit Log
(if one exists). If the '-audit' option is specified, the Audit Log is
operated on instead of the Event Log. The log and its entries may be remotely
queried and viewed using the DMTF Record Log CIM profile.
Note: When logging more than one word of text (i.e. separated by spaces), you
must enclose the entire command in quotes. For example:
> bmcc "log=my text to log"
This command is the equivalent of the b57diag "apelog [-a] -l<text>" command.
"bmcc [-audit] clearlog"
------------------------
Issues a request to the management controller to clear the management
controller's Event Log or Audit Log (if one exists). If the '-audit' option
is specified, the Audit Log is operated on instead of the Event Log. The
log and its entries may be remotely queried and viewed using the DMTF Record
Log CIM profile.
This command is the equivalent of the b57diag "apelog [-a] -C" command.
"bmcc create"
-------------
"bmcc create=length"
--------------------
"bmcc create[=length] -record=<type> [-attr=<value>]"
-----------------------------------------------------
Creates a default configuration set in the [cfgfilename] if specified or
the management controller's NVRAM. All existing configuration records will
be overwritten by this command.
This command is the equivalent of the b57diag "mancfg -c" command with the
exception that the APE_CFG NVRAM directory entry must already exist.
If the "create=<length>" syntax is used to create a default configuration
file, the length (in kilobytes) may be used to specify the *minimum* size of
the file to be created. i.e. "bmcc create=64 default.cfg" will create a
default.cfg file with the default configuration record set and padded with
terminator records (if necessary) to generate at least 65536 bytes in length.
If the "-record=<type>" option is specified, this command will create a single
configuration record of the specified type. The "attribute" value of the new
configuration record will be 0x00 unless a different value was specified with
the "-attr=<value>" option. The record length will be the "default" length
for the specified record type, unless the length was specified with
"bmcc create=<length>".
This command should not be confused with the '-create' option.
"bmcc dump"
-----------
View the contents (in hexadecimal and ASCII) of configuration records
contained in the management configuration reset set. Similar to the
"bmcc view -verbose" command.
"bmcc clear -record=<type>"
---------------------------
Clear the data of one or more configuration records of the specified record
type from the management configuration record set.
The "-record=<type>" option must be specified.
If the instance is not specified with the '-instance' or '-ordinal' option,
all instances of the specified record type will be cleared.
"bmcc remove -record=<type>"
----------------------------
Remove one or more configuration records of the specified record type from
the management configuration record set.
The "-record=<type>" option must be specified.
If the instance is not specified with the '-instance' or '-ordinal' option,
all instances of the specified record type will be removed.
"bmcc delete -record=<type>"
----------------------------
Nullify one or more configuration records of the specified record type from
the management configuration record set. The record header and data will be
cleared (zeroed) out, but not removed from the configuration set, so the
space may be used by a newly added or re-sized configuration record.
The "-record=<type>" option must be specified.
If the instance is not specified with the '-instance' or '-ordinal' option,
all instances of the specified record type will be deleted.
"bmcc encrypt -record=<type>"
-----------------------------
Encrypt one or more configuration records in the management configuration
record set. This command cannot not be used to encrypt records in a
configuration file.
If the instance is not specified with the '-instance' or '-ordinal' option,
all instances of the specified record type will be encrypted.
The management firmware does not support the encryption of all record
types. See TruManagementConfiguration.pdf for a current list of record types
that may be encrypted.
"bmcc decrypt -record=<type>"
-----------------------------
Decrypt one or more configuration records in the management configuration
record set. This command cannot not be used to encrypt records in a
configuration file.
If the instance is not specified with the '-instance' or '-ordinal' option,
all instances of the specified record type will be decrypted.
This command should not be confused with the '-decrypt' option, which may
be used in combination with other commands (e.g. export, view, dump).
"bmcc compress"
---------------
Reduces configuration record lengths to the minimum length required to
store the current record data and removes configuration records with no data
(including Null/Deleted records).
Normal use of this command is not recommended as it can inhibit upgrading
the configuration record set to support the capabilities of future
management firmware versions.
"bmcc add=<file.cfg|file.ini>"
------------------------------
"bmcc merge=<file.cfg|file.ini>"
--------------------------------
"bmcc replace=<file.cfg|file.ini>"
----------------------------------
These commands take a source configuration or initialization (.ini) file as an
argument. If the "-record=<type>" option is specified, one (if the '-instance'
or '-ordinal' option is specified) or all records of the specified type will
be imported into the target configuration record set.
If the "-record=<type>" option is not specified, then all records
(except for the VERSION record) will be imported into the target
configuration record set.
If the "bmcc add=<file>" command is used, then the imported records will
be added to the target configuration record set (no existing
records in the target configuration record set will be removed or
overwritten*).
If the "bmcc merge=<file>" command is used, then record instances that exist
in both the source and the target configuration record set will be
overwritten in the target. If there are more instances of a common record
type in the target than there are in the source configuration record set,
those instances in the target will not be removed or overwritten*.
If the "bmcc replace=<file>" command is used, then record types that exist in
both the source and the target configuration record set will be overwritten
in the target. If there are more instances of a common record
type in the target than there are in the source configuration record set,
those instances in the target will be removed.
The target configuration record set may exist either in NVRAM or in
a configuration file.
* An exception to these statements exists: If importing a record from a .ini
file which includes a specified ordinal value, the existing record of that
type and ordinal in the target configuration record set (if it exists) WILL
be overwritten with these commands.
Note: The "bmcc merge" command available in older versions of BMCC (used for
combining NULL/deleted records) has now been deprecated and removed.
"bmcc import=<file.cfg|file.ini>"
---------------------------------
The "import" command is used to import one or more records from a source
configuration, initialization or data file into a target configuration record
set.
If the "-record=<type>" option is *not* specified, the target configuration
record set will be completely overwritten with the records read from the
specified configuration (.cfg) or initialization (.ini) file being imported.
Any existing records in the target configuration record set will be deleted
or overwritten.
Examples:
"bmcc import=dashfw.cfg"
"bmcc import=dashfw.ini"
If you wish to import records from a configuration or initialization file
without completely overwriting the target configuration record set, consider
using the "add", "merge" or "replace" commands instead.
"bmcc import=<file.ini> -record=<type>"
---------------------------------------
This variant of the "import" command will import one or more instances of the
specified record type from the specified initialization (.ini) file into a
target configuration record set. Existing, overlapping instances of the
specified record type will be overwritten in the target configuration record
set. If you wish to import records from an initialization file without
overwriting any existing records in the target configuration record set,
consider using the "add" command instead.
Example:
"bmcc import=dashfw.ini -record=account"
"bmcc import=<file.pem> -record=<type>"
---------------------------------------
If the "-record=<type>" option is specified and the specified import filename
contains a ".pem" suffix/extension, then the contents will assume to be a
Privacy-enhanced Electronic Mail (PEM) encoded X.509 Certificate or RSA
private key and will be decoded accordingly.
Example:
"bmcc import=private_key.pem -record=private_key"
"bmcc import=<file> -record=<type> [-base64]"
---------------------------------------------
If the "-record=<type>" option is specified and the specified import filename
does not contain a recognized extension/suffix (i.e. ".ini" or ".pem"),
the file contents will be imported into the record as raw binary data.
Example:
"bmcc import=private.key -record=private_key"
If the file is base64-encoded, using the "-base64" option will instruct
BMCC to base64-decode the file contents before importing into the
configuration record.
Example:
"bmcc import=file.b64 -record=99 -base64"
If the "-attr=<value>" option is specified, a newly created configuration
record will use that attribute value instead of the default (0x00 - "none").
If the record already exists and the "-attr=<value>" option is not specified,
the existing attributes value is left intact.
If the "-record=smbios" option is specified, the source file will assume to
be a combination SMBIOS EPS and Structure Table binary dump file and be
imported into the two appropriate configuration records (SMBIOS_META and
SMBIOS_STRUCTS) accordingly.
"bmcc export=<file.cfg>"
------------------------
The "export" command is used to export one or more configuration records from
a configuration record set into a file or set of files.
If the specified export filename does not contain a ".ini" extension/suffix,
and the "-record=<type>" option was not specified, the complete configuration
record set will be exported into a configuration file.
Example:
"bmcc export=dashfw.cfg"
If any of the records being exported are encrypted and the '-decrypt' option
was not specified, the target file will contain the encrypted data and may
only be useful when re-imported into the same device.
"bmcc export=<file.ini> [-record=<type>]"
-----------------------------------------
This variant of the "export" command will export one or more records of the
specified record type (or all record types if the '-record' option is not
specified) into an initialization (.ini) text file suitable for editing with
a text editor and possible reimporting into a configuration record set.
Example:
"bmcc export=dashfw.ini"
"bmcc export=<file.dat> -record=<type>"
---------------------------------------
If the "-record=<type>" option is specified and the specified export filename
does not contain a ".ini" suffix/extension, this command will export the
specified configuration record from the management configuration record set
to the specified file.
Example:
"bmcc export=private.key -decrypt -record=private_key"
If the "-record=smbios" option is specified, then the SMBIOS Meta Data
and Structure Table records will be exported to a combined SMBIOS EPS and
Structure Table binary dump file.
"bmcc export=<dir> -record=webdata"
-----------------------------------
The "bmcc export=<dir> -record=webdata" command is a special use of the
'export' command to extract web data files (WEBDATA and WEBFILE records) from
a configuration record set (in NVRAM or a file) and create the files in a
directory on the local disk. '<dir>' must specify an existing directory.
"bmcc view-asf"
---------------
View the system's ASF System Description Table (ADT, a.k.a. "ASF! Table").
"bmcc view-asfcfg"
-----------------
View the stored ASF System Description Table configuration records.
"bmcc asf"
----------
Import the system's ASF System Description Table into the management
configuration record set.
"bmcc smbios"
-------------
Import the system's SMBIOS Structure Table into the management configuration
record set.
"bmcc web=<path>"
-----------------
Import a directory tree of web files (content) for the web/HTML
user interface. This command deletes any existing WEBFILE or WEBDATA
configuration records before importing the specified web content.
Example:
"bmcc web=c:\webpages\"
See Also: "bmcc export=<dir> -record=webdata" command.
"bmcc web=<file.cfg>"
---------------------
Import WEBFILE and WEBDATA configuration records from a configuration file.
This command deletes any existing WEBFILE or WEBDATA configuration records
before importing the specified web content.
Example:
"bmcc web=c:\dashfw.cfg"
"bmcc ostatus"
--------------
Display the status of the Opaque Management Data configuration records.
The Opaque Management Data records exist in support of the DMTF Opaque
Management Data CIM Profile.
"bmcc ocreate=<number of OMData instances>,<total storage bytes>"
-----------------------------------------------------------------
Create the Opaque Management Data (OMData) configuration records to support
the specified number of OMData instances and total storage bytes.
If the <total storage bytes> value is not evenly divisible by 4, it will
be rounded up to the nearest value evenly divisible by 4.
"bmcc oalloc=<length>,[owner account],[data format],[element name]"
-------------------------------------------------------------------
Allocate the next available Opaque Management Data (OMData) instance based
on the specified data length. The owner account, data format, and element
name values are optional.
"bmcc oread"
------------
Read data contained in one or all OMData instances.
"bmcc owrite"
-------------
Write data (from stdin) into the specified OMData instance.
"bmcc oclear"
-------------
Clear (zero-out) data associated with one or all OMData instances and set
the data length value(s) to 0.
"bmcc ofree"
------------
Release one or more OMData instances to the pool of available OMData instances
that may be allocated (e.g. with "bmcc oalloc") from.
"bmcc prop<id>=<val> [-type=<type>] [-length=<length>] -record=<type>"
----------------------------------------------------------------------
Modify or create a property value in a property stream record.
The '-record' option must be specified and the specified record type must
correspond to one or more existing property stream records in the record set.
If neither the '-instance' nor '-ordinal' option is specified, all existing
records of the specified record type will be modified.
Only one property ID may be modified or created per command invocation.
The <id> portion of the command must be the hexadecimal property ID
corresponding with the property to be modified or created in the specified
record (see bmcfg_defs.h in the TruManage SDK or the TruManage Configuration
documentation for reference).
The <val> portion of the command is the value to use for the modification or
creation of the property.
If the '-type' option is not specified, the default property type is string
(str). The property type may be specified with the '-type' option as follows:
[-type=str]
Property value is a text string.
The entire "-prop<id>=<value>" command should be enclosed in quotes to
retain any white-space within the string.
[-type=int]
Property value is an integer (decimal, by default).
Use the "0x" prefix to specify integer values in hexadecimal notation.
[-type=hex]
Property value is a sequence of bytes, specified in pairs of hexadecimal
digits.
[-type=add]
Property value is a non-zero integer to be added to the current value.
Use a negative property value to subtract from the current value.
Use the "0x" prefix to specify integer values in hexadecimal notation.
[-type=or]
Property value is a non-zero integer to be bit-wise OR'd into the current
value.
Use the "0x" prefix to specify integer values in hexadecimal notation.
[-type=not]
Property value is a non-zero integer to be bit-wise NAND'd out of (removed
from) the current value.
Use the "0x" prefix to specify integer values in hexadecimal notation.
[-type=ipv4]
Property value is a 'dotted-decimal' IPv4 address or netmask.
[-type=ipv6]
Property value is a valid IPv6 address.
If the '-length' option is not specified, the current property length is used.
If the property does not already exist in the record and the '-length' option
is not specified, the property will not be created.
Integer values are limited to 32-bits (4-bytes).
Advanced options
================
"-quiet"
--------
Display nothing on the standard output stream (stdout). Error messages will
still be sent to the standard error stream (stderr).
This option applies to all commands.
"-record=<type>[:<ordinal>]"
----------------------------
If the "-record=<type>" option is specified, only records matching the
specified record type will be acted upon. The record type may be the
hexadecimal value of the record type or one of the following record type
names:
Name Multi Prop Description
---- ----- ---- -----------
null Yes No Null/Deleted record
ver No No Version information
comment Yes No Comment text
banner No No Console redirection (Telnet/SSH) banner text
watermark No No Watermark used to detect proper decryption
smbios_meta No Yes System Management BIOS EPS and other metadata
smbios No No System Management BIOS structure table
bios_meta No Yes PLDM for BIOS metadata
bios_str No No PLDM for BIOS strings table
bios_attr No No PLDM for BIOS attribute table
bios_attr_val No No PLDM for BIOS attribute value table
bios_pend_val No No PLDM for BIOS pending value table
asf_info No No ASF System Description Table ASF_INFO record
asf_alrt No No ASF System Description Table ASF_ALRT record
asf_rctl No No ASF System Description Table ASF_RCTL record
asf_rmcp No No ASF System Description Table ASF_RMCP record
asf_addr No No ASF System Description Table ASF_ADDR record
state_sensor Yes Yes PLDM State Sensor
state_set Yes Yes PLDM State Sensor eventState to string map
state_msg Yes Yes PLDM State Sensor eventState to PlatMsgReg map
mgmt No Yes Remote Management configuration
ipv4 No Yes IPv4 configuration
ipv6 No Yes IPv6 configuration
pet No Yes Platform Event Trap (ASF Alert) configuration
rsp No Yes RMCP Security Protocol-extensions (ASF 2.0)
conredir No Yes Text Console Redirection configuration
usbredir No Yes USB Media Redirection configuration
smbus Yes Yes System Management Bus interface configuration
account Yes Yes CIM_Account instance
role Yes Yes CIM_Role instance
wsevent_sub Yes Yes WS-Eventing subscription record
wsevent_ref Yes No WS-Eventing subscription reference parameters
private_key No No Private RSA Key (for TLS and SSH)
server_cert No No TLS Server Certificate
server_ca_cert No No TLS Server Certificate Authority (unused)
client_ca_cert No No TLS Client Certificate Authority
ad No Yes Active Directory configuration
webfile Yes Yes Web/HTML user interface file
webdata No No Web file data (for all web files)
os_info No Yes Operating System information
sw_info No Yes Broadcom Software version information
omdata Yes Yes Opaque Management Data instance record
omdata_storage No No Opaque Management Data storage
802.1x No Yes 802.1X supplicant configuration
802.1x_cert No No 802.1X authentication server root certificate
Tip:
If an invalid record type name is given or "-record=?" is given, then a
list of supported record types (hex and name values) will be displayed.
Note:
Record types with a "Multi" indicator of "Yes" are multiple-instance records
where the management controller will support more than instance of that
record type. For other record types, only the first instance (instance 0,
ordinal 1) will be used by the management firmware.
Note:
Record types with a "Prop" indicator of "Yes" are property stream records.
Property stream records are different from records that contain raw binary
or text data and support different BMCC commands and options.
Optionally, a record ordinal may be specified by appending ":<ordinal>" after
the record <type> where <ordinal> is a 1-based decimal number indicating the
ordinal of the record that you wish to operate on. Example:
"bmcc view -record=role:1"
is the equivalent of:
"bmcc view -record=role -ordinal=1"
"-instance=<num>"
-----------------
If this option is specified (with a 0-based decimal instance number), only the
specified instance of the specified record type will be operated on
(e.g. displayed or modified). Otherwise, all instances of the specified record
type will be operated on (unless the '-ordinal' option is specified).
Instance 0 refers to the first occurrence of a specified record type within a
record stream (the instance with the lowest byte offset), instance 1 refers to
the second occurrence, and so on.
Use of the '-instance' option is mutually exclusive with the '-ordinal' option
(only use one or the other, they cannot be used together).
This option applies to the following commands:
view, dump, remove, encrypt, decrypt, import, export,
oread, owrite, oclear, ofree, prop
"-ordinal=<num>"
----------------
If this option is specified (with a 1-based decimal ordinal number), only the
specified instance of the specified record type will be operated on
(e.g. displayed or modified). Otherwise, all instances of the specified record
type will be operated on.
This option applies to the following commands:
view, dump, remove, encrypt, decrypt, import, export,
oread, owrite, oclear, ofree, prop
This option is mutually exclusive with the '-instance' option (specifying
both options is not supported).
Ordinals differ from instances in that ordinal values will not change even
when a record must be relocated (and potentially reordered) in the record
stream (e.g. due to upgrading).
Note: You can also use the '-record' option with the
"-record=<type>:<ordinal>" syntax to specify both the record type and
ordinal without using the '-ordinal' option.
"-attr=<value>"
---------------
This option is used to specify the attribute value used when creating a new
configuration record. The value may be specified in hexadecimal, or the value
strings "none", "prop" (for property stream records), "enc" (for encrypted
records), or "badcksum" (for records with an ignored checksum value) may be
specified.
To specify more than one attribute flag, use the hexadecimal notation or use
multiple instances of the "-attr" option.
Example: "bmcc create -record=99 -attr=5"
Example: "bmcc create -record=99 -attr=enc -attr=prop"
This option applies to the following commands:
create, import, ocreate
"-base64"
---------
See the "import" command for details.
"-noverify"
-----------
This option is used to disable the automatic configuration record set
validity checking that is performed when the configuration record data is
read (from NVRAM or file) and before it is written (to NVRAM or file).
"-nocfgchevent"
---------------
Use of this option prevents BMCC from notifying the management controller
that a configuration change has occurred. For advanced uses only.
"-truncate"
-----------
This option may be used when creating or modifying a .cfg file to force the
output file size to the minimum number of bytes required to store the
configuration record set (by excluding terminator records).
"-create"
---------
When specifying a configuration file on the command-line, that configuration
file normally must already exist or the command will fail. When specifying the
'-create' option, the file will be created (or overwritten if it already
exists).
Examples:
"bmcc web=c:\webpages\ -create web.cfg"
"bmcc asf -create asf.cfg"
"bmcc smbios -create smbios.cfg"
"-audit"
--------
See the "log=<text>" and "clearlog" commands for details.
"-type"
-------
See the "prop<id>=<value>" command for details.
"-length"
---------
See the "prop<id>=<value>" command for details.
"-scan"
-------
Search the specified configuration filename for a valid configuration record
set. This option is useful for verifying or displaying a configuration record
or record set embedded in an NVRAM image (e.g. ".bin") file.
Note: Do not use this option to attempt to edit a configuration record
embedded in an NVRAM image file.
"-decrypt"
----------
This option will instruct specific BMCC commands to attempt to decrypt any
encrypted records before viewing or exporting them. Any records that are
decrypted during export (to a configuration file) will then be automatically
re-encrypted if/when that file is then imported into a controller's NVRAM.
Configuration records that have been decrypted in this manner will have the
"DEC" attribute flag set in their configuration record header (e.g. when
viewed in the configuration file).
This option applies to the following commands:
view, dump, export
/* 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.