HPE服务器380GEN 9, 360GEN9网卡驱动BCM5719 2008r2驱动.zip

=========== R E A D M E =========== Broadcom Ethernet Controller WMI provider Copyright (c) 2016 Broadcom Ltd All rights reserved. Table of Contents ----------------- 1. Overview 2. Limitation 3. Files 4. Dependency 5. Installation 6. Implementation 7. Known Limitations 8. Troubleshooting 9. 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 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) Windows 7 (32 bit and 64 bit) Windows 2008 (32 bit and 64 bit) Windows 8 (32 bit and 64 bit) Windows 2012 (32 bit and 64 bit) Windows 2012 R2 Windows 8.1 (32 bit and 64 bit) Please also refer to 'Dependency' section for more information. 3. Files -------- BnxWmiProvider.<version>.dll BRCM CIM provider library bmapi.dll BMAPI share library libxml2.dll XML 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 BnxInterop.mof MOF file for Broadcom derived classes for Profile Registration Profile BnxWmiProvier.mof MOF file for class registration 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.30.19 c. OpenSSL Refer to license information below. d. TCL libraries e. CIM Studio This provider package is tested with CIM Studio. 5. Installation -------------------- The provider can be manually installed/uninstalled in a command prompt. For Windows Vista and above, you must open the command prompt with "run as administrator". 5.1 Uninstall 1. CD to the path containing the provider files. 2. mofcomp BnxWmiProvider_Uninstall.mof 3. regsvr32 /u BnxWmiProvider.<version>.dll 5.2 Install 1. CD to the path containing the provider files. 2. mofcomp BnxWmiProvider.mof 3. regsvr32 BnxWmiProvider.<version>.dll 6. Implementation -------------------- 6.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. 6.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. 6.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. 6.4 Software Inventory Profile Broadcom device firmware, drivers, installers, management software, etc. are represented by instances of CIM_SoftwareIdentity. 6.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