===========
R E A D M E
===========
Broadcom Ethernet Controller WMI provider
Copyright (c) 2010 Broadcom Corporation
All rights reserved.
Table of Contents
-----------------
1. Overview
2. Limitation
3. Files
4. Dependency
5. Implementation
6. Known Limitations
7. Troubleshooting
8. Third Party Software License
1. Overview
-----------
Broadcom ethernet controller WMI provider implements various DMTF
profiles to provide information about the device, and methods to
perform diagnostic tests, firmware update, as well as device
configuration. The provider currently conforms to the following
standards defined by DMTF:
Standard Version
------------------------------------------------
Profile Registration Profile 1.0.0c
Ethernet Port Profile 1.0.0
Diagnostic Profile 1.0.0b
Host LAN Network Port Profile 1.0.0
Software Inventory Profile 1.0.0
Software Update Profile 1.0.0
DASH Standard 1.1
Simple Identity Management Profile 1.0.0
Role Based Authorization Profile 1.0.0
Opaque Management Data Profile 1.0.0
2. Limitation
-------------
The provider supports i386 architecture based CPU. The following is
the list of supported OS:
Windows 2000 Server/Workstation GA-SP4
Windows 2003 GA-SP1 (32 bit and 64 bit)
Windows 2003 R2 (32 bit and 64 bit)
Windows XP GA-SP2 (32 bit and 64 bit)
Windows Vista (32 bit and 64 bit)
Please also refer to 'Dependency' section for more information.
3. Files
--------
BnxWmiProvider.<version>.dll BRCM CIM provider library
BrcmUtils.dll BRCM CIM provider library
BmapiObjServices.dll BRCM CIM provider library
bmapi.dll BMAPI share library
libeasy32.dll OpenSSL share library
tcl83.dll TCL library
tcldde83.dll TCL library
tclpip83.dll TCL library
tclreg83.dll TCL library
BnxAdapter.mof MOF file for Broadcom derived adapter related classes
BnxCDM.mof MOF file for Broadcom derived classes for Diagnostic Profile
BnxWmiProvier.mof MOF file for class registration for W2K3, XP, and above
BnxWmiProvierW2K.mof MOF file for class registration for W2K
CIM_Core.mof MOF file for CIM Classes from DMTF
CIM_Device.mof MOF file for CIM Classes from DMTF
CIM_Interop.mof MOF file for CIM Classes from DMTF
CIM_Network.mof MOF file for CIM Classes from DMTF
CIM_Physical.mof MOF file for CIM Classes from DMTF
CIM_System.mof MOF file for CIM Classes from DMTF
CIM_System_Device.mof MOF file for CIM Classes from DMTF
CIM_User.mof MOF file for CIM Classes from DMTF
readme.txt this file
release.txt release information
4. Dependency
------------------
a. Broadcom network adapters running the following driver versions:
For 4401 devices: driver version 3.46.
For NetXtreme devices: NDIS driver version >= 6.34.
For NetXtremeII devices: VBD driver version >= 2.5.2.
Please refer to README.TXT of the target driver for installation
instruction.
b. BMAPI
bmapi version >= 7.16.0.
c. OpenSSL
Refer to license information below.
d. TCL libraries
e. CIM Studio
This provider package is tested with CIM Studio.
5. Implementation
--------------------
5.1 Profile Registration Profile
For each implemented profile, there is an instance of RegisteredProfile describing
the profile name and version. The RegisteredProfile instance is associated to the
corresponding ManagedElement through ElementConformsToProfile. RegisteredProfile
instances are instantiated in root/InterOp namespace in order to advertise the
availability of a conformant implementation of a profile. The rest of the class
instances are implemented in root/BrcmBnxNS namespace.
5.2 Ethernet Port Profile / Host LAN Network Port Profile
The provider implements Ethernet Port Profile (derived from Host LAN Network Port
Profile) to model Broadcom adapter information.
5.3 Diagnostic Profile
The following Diagnostic tests are available:
Control Registers
MII Registers
EEPROM
Internal Memory
Interrupt
Loopback MAC
Loopback PHY
LEDs
CPU
Package Test
Some diagnostic may not be available to certain devices due to hardware limitation.
CIM_DiagnosticTest.RunDiagnostic() method is implemented to perform diagnostic on
the device represented by a BRCM_NetworkController instance referenced by the
ManagedElement parameter.
5.4 Software Inventory Profile
Broadcom device firmware, drivers, installers, management software, etc. are
represented by instances of CIM_SoftwareIdentity.
5.5 Software Update Profile
CIM_SoftwareInstallationService.InstallFromURI() method is implemented to support
firmware upgrade for Broadcom Ethernet Controllers. This function takes the
following parameters:
1. URI - the URI corresponding to the new firmware image to be used.
2. Target - reference to the CIM_SoftwareIdentity corresponding to the
device and firmware to be upgraded.
3. InstallOptions - supports options "defer reset" (2), "force" (3),
"update" (5), "reboot" (7) and Broadcom specific
values 32768 and 32769.
4. InstallOptionsValues - if Broadcom specific values 32768 or 32769 are used in
InstallOptions array, there should be an entry in
InstallOptionValues array with the same index of the Broadcom
specific value in the InstallOptions array.
e.g. if the 2nd entry of InstallOptions contains 32768, then
the 2nd entry of InstallOptionsValue should contain an option
string accordingly.
"-p" to upgrade iSCSI configuration program along with iSCSI
firmware.
For iscsi firmware upgrade, the following 2 entries in InstallOptions/InstallOptionsValues
are supported:
InstallOptions InstallOptionsValues Required Purpose
-----------------------------------------------------------------------------------------------
1. 32768 "-p" No upgrade iscsi config program
along with iscsi firmware
2. 32769 "ipv4", "ipv6", or "ipv4n6" Yes specify the iscsi configuration
for the upgrade
If option 32769 and the corresponding value is not specified when upgrading iscsi firmware,
InstallFromURI() method will return error.
5.6 DASH Standard 1.1
The provider conforms to DASH Standard 1.1 and implements Broadcom OOB Management
Service Profile is to manage DASH enabled devices, and supports IPv4/IPv6 setting info,
configuration of 802.1x, Active Directory, HTTP, HTTPS, HTTPS Client, RMCP, Secure RMCP,
and Web Server.
5.7 Role Based Authorization Profile
For DASH enabled devices, Role Based Authorization Profile is implemented to support
show roles, show access, assign roles and modify role.
5.8 Simple Identity Management Profile
For DASH enabled devices, Simple Identity Management Profile is implemented to support
create account, modify account, delete account, and enable/disable account.
5.9 Opaque Management Data Profile
For DASH enabled devices, Opaque Management Data Profile is implemented to support
create data, read/write data, assign access, and reassign ownership.
6. Known Limitations
----------------------
No known limitation.
7. Troubleshooting
-------------------
Problem: Cannot enumerate any BRCM classes
Possible cause: Provider software is not installed properly.
Solution: Reinstall provider software and make sure the BnxWmiProvider,
BmapiObjServices, and BrcmUtil libraries are in the library
search path.
Possible cause: Bmapi library is not in the library search path, or the wrong
version of Bmapi library is installed.
Solution: Make sure a supported version of Bmapi library is in the library
search path. Refer to Dependency section for supported versions
of Bmapi.
Problem: No Broadcom devices are enumerated.
Possible cause: Device driver of supported version is not installed or not loaded.
Solution: Make sure the device driver is installed and loaded properly.
Ethtool should be able to enumerate the device if driver is installed.
Refer to Dependency section for supported versions of device drivers.
Problem: Only loopback tests fail while other tests pass.
Possible cause: Fad.sys and fadxp32.sys are required for MAC and physical loopback
tests. These files are required to be in the search path.
Solution: Make sure these 2 files provided in the installation are in the
search path.
Problem: RunDiagnostic failed
Possible cause: Ran out of disk/memory space.
Solution: Free up disk/memory space and try again.
Possible cause: No admin privileges to run the tests.
Solution: Login as administrator and try again.
Possible cause: Device is already in diagnostic state.
Solution: Wait until the current diagnostic to finish and try again.
If the problem can't be solved by any of the above, and it is persistent,
try using a different version of driver or software and repeat the test to
rule out the possibility of faulty software.
If the problem still persists, contact support personnel and ask for support.
8. Third Party Software License
--------------------------------
Portions of this software contain third party code subject to the following conditions:
OpenSSL
/* ====================================================================
* Copyright (c) 1998-2007 The OpenSSL Project. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
*
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
*
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in
* the documentation and/or other materials provided with the
* distribution.
*
* 3. All advertising materials mentioning features or use of this
* software must display the following acknowledgment:
* "This product includes software developed by the OpenSSL Project
* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
*
* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
* endorse or promote products derived from this software without
* prior written permission. For written permission, please contact
* openssl-core@openssl.org.
*
* 5. Products derived from this software may not be called "OpenSSL"
* nor may "OpenSSL" appear in their names without prior written
* permission of the OpenSSL Project.
*
* 6. Redistributions of any form whatsoever must retain the following
* acknowledgment:
* "This product includes software developed by the OpenSSL Project
* for use in the OpenSSL Toolkit (http://www.openssl.org/)"
*
* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR
* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
* OF THE POSSIBILITY OF SUCH DAMAGE.
* ====================================================================
*
* This product includes cryptographic software written by Eric Young
* (eay@cryptsoft.com). This product includes software written by Tim
* Hudson (tjh@cryptsoft.com).
*
*/
Original SSLeay License
-----------------------
/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
* All rights reserved.
*
* This package is an SSL implementation written
* by Eric Young (eay@cryptsoft.com).
* The implementation was written so as to conform with Netscapes SSL.
*
* This library is free for commercial and non-commercial use as long as
* the following conditions are aheared to. The following conditions
* apply to all code found in this distribution, be it the RC4, RSA,
* lhash, DES, etc., code; not just the SSL code. The SSL documentation
* included with this distribution is covered by the same copyright terms
* except that the holder is Tim Hudson (tjh@cryptsoft.com).
*
* Copyright remains Eric Young's, and as such any Copyright notices in
* the code are not to be removed.
* If this package is used in a product, Eric Young should be given attribution
* as the author of the parts of the library used.
* This can be in the form of a textual message at program startup or
* in documentation (online or textual) provided with the package.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* "This product includes cryptographic software written by
* Eric Young (eay@cryptsoft.com)"
* The word 'cryptographic' can be left out if the rouines from the library
* being used are not cryptographic related :-).
* 4. If you include any Windows specific code (or a derivative thereof) from
* the apps directory (application code) you must include an acknowledgement:
* "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
*
* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* The licence and distribution terms for any publically available version or
* derivative of this code cannot be changed. i.e. this code cannot simply be
* copied and put under another distribution licence
* [including the GNU Public Licence.]
*/
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.