1. Purpose:
Upgrading F/W via ipmitool is supported by the BMC. The available IPMI interfaces for update are KCS and IOL with RMCP+ protocol.
KCS interface: The upgrade process is executed from local OS.
IOL interface: Leverage NC-SI and upgrade firmware remotely.
Upgrade sequence :
When multiple f/w need to be updated, please follow the sequence in order to avoid unexpected behavior after upgrade.
BMC --> BMC Bootloader --> FPGA or CPLD --> BIOS
In this article, we describe steps to upgrade firmware using different methods.
2. Audience:
All users with BMC supported SKUs.
3. Prerequisites:
ipmitool is 1.8.17 or later
BMC supported related devices.
4. Procedures:
A- Via Node Explorer
- Please follow How to access node explorer to access Node Explorer
- Go to the Maintenance >> Firmware Upgrade page:
- Select the xxx.img file to upload and start to upgrade.
Note 1: Please note that the power cycle is required for BIOS and FPGA upgrades.
Note 2: Please repeat the above instructions to upgrade the backup Firmware.
B- Via IPMITOOL over KCS
- Ensure that the ipmitool utility works normally and the version of ipmitool is 1.8.17 or later.
- BMC bootloader:
# ipmitool -z 270 hpm upgrade bootloader.img activate
- BMC: Please run the following command twice for backup BMC.
# ipmitool -z 270 hpm upgrade bmc.img activate
- FPGA: Please power cycle the system after the upgrade, then run the command again for backup FPGA.
# ipmitool -z 270 hpm upgrade fpga.img activate
# ipmitool chassis power cycle
# ipmitool -z 270 hpm upgrade fpga.img activate
- System BIOS: Please power cycle the system after the upgrade, then run the command again for backup BIOS.
# ipmitool -z 270 hpm upgrade bios.img activate
# ipmitool chassis power cycle
# ipmitool -z 270 hpm upgrade bios.img activate
- NVRAM:
# ipmitool -z 270 hpm upgrade NVRAM.img activate
- FW version Check:
# ipmitool hpm check
C- Via BMC IPMI LAN channel 2
- Upload firmware image to OS.
- Check BMC MAC 2 IP via the following command. Default BMC MAC2 IP should be 192.168.2.1.
# ipmitool lan print 2
- BMC MAC2 network should be detected as a USB Ethernet device under OS (x86). Please Set the IP of USB Ethernet (like enp0s20f0u4u4 in the following example) as the same domain as BMC MAC2 IP.
# ethtool -i enp0s20f0u4u4
driver: cdc_eem
version: 22-Aug-2005
firmware-version: CDC EEM Device
expansion-rom-version:
bus-info: usb-0000:00:14.0-4.4
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
# ip a |grep enp0s20f0u4u4
5: enp0s20f0u4u4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
inet 192.168.2.100/24 scope global enp0s20f0u4u4
- Check the BMC IPMI LAN channel 2 connection through "ping".
# ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=1.40 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.479 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=0.458 ms
- Run below command to upgrade firmware.
# ipmitool -I lanplus -H 192.168.2.1 -U administrator -P advantech hpm upgrade firmware.img
PICMG HPM.1 Upgrade Agent 1.0.9:
Validating firmware image integrity...OK
Performing preparation stage...
Services may be affected during upgrade. Do you wish to continue? (y/n): y
OK
Performing upgrade stage:
-------------------------------------------------------------------------------
|ID | Name | Versions | % |
| | | Active | Backup | File | |
|----|-------------|-----------------|-----------------|-----------------|----|
| 1|8312 BMC | 1.03 00000000 | 1.03 00000000 | 1.03 00000000 |100%|
| |Upload Time: 03:06 | Image Size: 10414410 bytes |
-------------------------------------------------------------------------------
(*) Component requires Payload Cold Reset
Firmware upgrade procedure successful
- Activate the firmware via KCS.
# ipmitool hpm activate
- Check firmware upgrade is successful or not.
# ipmitool hpm check
D- Via BMC IPMI LAN channel 3
- Upload firmware image to OS.
- Check BMC MAC 3 IP via the following command. Default BMC MAC 3 IP should be10.234.147.1
# ipmitool lan print 3
- BMC MAC 3 network should be detected as a USB Ethernet device under OS (x86). Please Set the IP of USB Ethernet (like usb0 in the following example) as the same domain as BMC MAC 3 IP.
# ethtool -i usb0
driver: cdc_ether
version: 22-Aug-2005
firmware-version: CDC Ethernet Device
expansion-rom-version:
bus-info: usb-0000:00:14.0-5.4
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
# ifconfig usb0
usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.234.147.100 netmask 255.0.0.0 broadcast 10.255.255.255
inet6 fe80::a1b1:6164:b7ce:6f1 prefixlen 64 scopeid 0x20<link>
ether da:d7:16:f4:b1:cd txqueuelen 1000 (Ethernet)
RX packets 29 bytes 1748 (1.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 59 bytes 9494 (9.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
- Check the BMC IPMI LAN channel 3 connection through "ping".
# ping 10.234.147.1
PING 10.234.147.1 (10.234.147.1) 56(84) bytes of data.
64 bytes from 10.234.147.1: icmp_seq=1 ttl=64 time=0.740 ms
64 bytes from 10.234.147.1: icmp_seq=2 ttl=64 time=0.565 ms
64 bytes from 10.234.147.1: icmp_seq=3 ttl=64 time=0.474 ms
- Run the below command to upgrade firmware.
# ipmitool -I lanplus -H 10.234.147.1 -U administrator -P advantech hpm upgrade firmware.img
PICMG HPM.1 Upgrade Agent 1.0.9:
Validating firmware image integrity...OK
Performing preparation stage...
Services may be affected during upgrade. Do you wish to continue? (y/n): y
OK
Performing upgrade stage:
-------------------------------------------------------------------------------
|ID | Name | Versions | % |
| | | Active | Backup | File | |
|----|-------------|-----------------|-----------------|-----------------|----|
| 1|8312 BMC | 1.03 00000000 | 1.03 00000000 | 1.03 00000000 |100%|
| |Upload Time: 03:06 | Image Size: 10414410 bytes |
-------------------------------------------------------------------------------
(*) Component requires Payload Cold Reset
Firmware upgrade procedure successful
- Activate the firmware via KCS.
# ipmitool hpm activate
- Check firmware upgrade is successful or not.
# ipmitool hpm check
Comments
0 comments
Please sign in to leave a comment.