下载文件
文件格式: Microsoft Windows 32位格式中的戴尔更新包(DUP)设计为可以在Microsoft Windows 64位操作系统上运行。Microsoft Windows 64位格式中的戴尔更新包(DUP)仅可在Microsoft Windows 64位操作系统上运行。选择设备驱动程序更新时,请务必选择适合您的操作系统的更新。
文件名: ESM_Firmware_V4DTW_WN32_2.25.EXE
文件大小: 22.4 MB
为确保下载的完整性,请验证校验和值。
MD5: 329fed8ed971c0c01b65cd30ca708fa2
SHA1: 277c47d4fccd86401c2bde40118e2c8c0ada311c
SHA-256: 819d32d3e1e8f2108831d65508929cf55a5f2ddb8f01a85cae6637b3187cf8e1
文件格式: 此文件包含一组压缩文件。将文件下载到硬盘上的文件夹中,然后双击它来解压这组文件。请按照说明完成安装。
文件名: PEC6220&PEC8000BMC225.exe
文件大小: 134.49 MB
为确保下载的完整性,请验证校验和值。
MD5: e0aa8a257663927d7d37b7c1584c2ea5
SHA1: fe7775900d87b14b8b1b1f21b6c6173d7cc891f1
SHA-256: b821dcd91049e658694e15e20538aff7d60e64a6a0f11f14c851a5c6e2a0717d
文件格式: Red Hat Linux更新包的GnuPG签名可用于验证戴尔在相关Red Hat Linux更新包中的身份。
文件名: ESM_Firmware_V4DTW_LN32_2.25.BIN.sign
文件大小: 189 Bytes
为确保下载的完整性,请验证校验和值。
MD5: a200322e6ff094e9719f32ec173267b3
SHA1: e8c7aa83f16278f380f2ffcaa15f77586d1aaae8
SHA-256: ab5047fda3af64f6a2e10172f64adc92a7a1a046952707a0b085094ae3f6606b
文件格式: 此文件格式包含纯文本,您可以采用标准文本编辑器进行查看。
文件名: EndUser LicenseAgreementType S_Rev. 040512.txt
文件大小: 11.4 KB
为确保下载的完整性,请验证校验和值。
MD5: c2ffe409366d225552ac6ed58f206b58
SHA1: 88522584d2ed8711c12c71ae9e569116a26e7b0a
SHA-256: b85aae437264a3f053c9efec6b47fa1ba6610de28b749a06c2fec3dfc87bf333
文件格式: 适用于Linux 的戴 尔更新包是在 满足特定的标准系统环境下使用的独立应用程序。,然后应用更新。<br /><b>注意:</b>Linux的更新包是开源的。查看适用于Linux 的戴 尔更新包自述以了解 详情,了解详情。
文件名: ESM_Firmware_V4DTW_LN32_2.25.BIN
文件大小: 17.46 MB
为确保下载的完整性,请验证校验和值。
MD5: 86ad58303a5ef0584e6646323ed112a0
SHA1: 1c515aaf26bac32e3be056879866946c114ca2f5
SHA-256: a1286643ae05cd27eef453863ddd632998115c065a08c774374eab305d3fbd31
补丁和增强功能
Fixes
- Web IPMI over LAN settings is abnormal
- BMC network sometimes behave abnormal after A/C cycle stress.
- Display wrong field data with IPv6 DNS Server 1 and Server 2
- Incorrect BMC Firmware version of are shown via OEM command after firmware update
- BMC IOL session can't be established by User ID 8
- BMC will respond error message during KCS Firmware updating
- After generate IERR by using ITP or HW, SUT didn't occurred error message in SEL
- PEF action function will intermittently malfunction.
- BMC is not supporting configuring IP address with .255 and .0.
- Sometimes system will not auto power on with "always on policy" during AC Cycle
- DCMI 1.1 VLAN RMCP+ Entries will fail in DCTS
- Fail to access BMC via SSH/Telnet if flash BMC with preserve config
- LAN parameter data does not match when BMC IP over 14 character
- Identification LED will malfunction during AC cycle
- UID LED will not light steady when press UID button
- GPGPU sensor malfunction after AC cycle
- GPGPUsensors are shown no reading unexpectedly after DC cycle
- BMC DUP firmware update sometimes fail.
- Watchdog function works abnormal under dos
- BMC sometimes will not responding to IPMI commands when power off the system
- BMC may have error behavior when dedicated NIC try to get DHCP IP in network environment with no DHCP server.
Enhancements
- Enhance IPv6 behavior.
- Enhance F/W update behavior.
- Enhance IPMI command behavior.
- Enhance network behavior.
- Enhance dynamic sensor behavior.
- Enhance Web behavior.
- Enhance I/O control.
重要信息
- If BMC is under DHCP mode, user may not read BMC IP address under BIOS setup menu in some specific network switch. The alternative way is to use IPMI command to query BMC IP address via KCS.
- Do not roll back to old version after you update to V1.14 already.
If you want to flash to old version, please use socflash.
BMC firmware might have version dependency with chassis firmware. Before update BMC firmware, please check related chassis FAN Controller Board firmware release package first.
KCSflash - use *.dcs for firmware update
NOTE: Since the KCS update utility may refer to some dynamic linked library files, KCSflash directory structure must be maintained to update BMC via KCS channel when it is extracted from the package.
=================================================================
Dos: Execute FBMC.bat in the folder, and utility will show the steps to upgrade BMC F/W.
=================================================================
Linux: Execute FBMC.sh in the folder,and utility will show the steps to upgrade BMC F/W.
=================================================================
Windows: Execute FBMC.bat in the folder, and utility will show the steps to upgrade BMC F/W.
=================================================================
Web Upgrade: Update via web by using *.dcs file under KCSflash/dos folder.
Note that Web upgrade is only for the current BMC is higher than V1.14.
=================================================================
Most usful parameter of DCSFWUD.EXE:
-e=value Specify enitity ID of image.
-f, -force Force reboot system or BMC without prompt user.
-o=value Specify the Install Options. Optional.
0 - Do not preserve config (default). (update BMC with default value)
1 - Preserve config. (update BMC with previous configuration)
-help Search for all parameter
=================================================================
Socflash - use allv***.bin for firmware update
安装说明
Download
1. Click 'Download File' to download the file.
2. When the File Download window appears, click Save to save the file to your hard drive.
Installation
1. Browse to the location where you downloaded the file and double-click the new file.
2. Read over the release information presented in the dialog window.
3. Download and install any prerequisites identified in the dialog window before proceeding.
4. Click the Install button.
5. Follow the remaining prompts to perform the update.
This new version changed BMC shared NIC behavior from bonding mode to NCSI mode. That means you can specify the specific NCSI port (NIC1 or NIC2) as BMC shared NIC. Due to this change, if you're updating via KCS (fbmc.sh) instead of running DUP, it would perform "restore LAN setting to default" to enable this new feature. Please check your network setting after firmware update to confirm if there is any setting changed by this.
If you're updating BMC by DUP (without configuration preserved), Shared NIC2 MAC will be restored to default MAC address. It did not affect the normal operation on shared NIC1. However, if you would like to apply NIC2 as BMC shared NIC, you should program the MAC address again manually by IPMI command.
1. #Get reservation ID
ipmitool raw 0x30 0x01
2. #switch to NIC 2
ipmitool raw 0x30 0x03 0x[reservation ID from first step] 0x02 0x02 0x00 0x00 0x00 0x01 0x02
3. #Enter manufacturing test mode
ipmitool raw 0x06 0x05 0x64 0x52 0x45 0x4d 0x24 0x73 0x74 0x38
4. #Program MAC address for NIC 2 (assuming MAC address 00:11:22:33:44:56)
ipmitool 0x20 0x30 0x01 0x01 0x05 0x00 0x11 0x22 0x33 0x44 0x56
(The last 6 bytes are MAC address)
Reboot will be required