HMP Fwupdate Command Fails To Update Network Controller Firmware

Asset ID:	1-72-2204196.1
Update Date:	2016-12-21
Keywords:

Solution Type Problem Resolution Sure

Solution 2204196.1 : HMP Fwupdate Command Fails To Update Network Controller Firmware

Applies to:

Sun Server X4-2L - Version All Versions to All Versions [Release All Releases]
Sun Server X4-2 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

Firmware update of network controller is failing with HMP 2.3.7.0

Example
# fwupdate update controller -x metadata.xml

The following components will be upgraded as shown:
==========================================================
ID Priority Action Status Old Firmware Ver. Proposed Ver. New Firmware Ver. System Reboot
------------------------------------------------------------------------------------------------------------------------
c1 1 Check FW Success 8000042D 800005BD N/A System Power Cycle
c2 1 Check FW Success N/A 800005CD N/A System Power Cycle
Do you wish to process all of the above component upgrades? [y/n]? y
Updating c1: ixgbe 0000:20:00.0: eth0: NIC Link is Down
ixgbe 0000:20:00.0: eth0: NIC Link is Up 1 Gbps, Flow Control: None
Success
Sleeping for 30 seconds for component to recover
Updating c2: Failed -->

Execution Summary
==========================================================
ID Priority Action Status Old Firmware Ver. Proposed Ver. New Firmware Ver. System Reboot
------------------------------------------------------------------------------------------------------------------------
c1 1 Post Power Pending 8000042D 800005BD N/A System Power Cycle
c2 1 Update Failure N/A 800005CD N/A System Power Cycle
Error: Firmware download failed for component
Extended Error: Invalid Argument
System Reboot required for some applied firmware
Do you wish to automatically reboot now? [y/n]? y
WARNING: File transfer to SP will go through the KCS interface.
This may take a long time ( > 60 min).

Changes

Cause

If the customer is using Network Bonding, then the issue may be due to duplicated MAC addresses.

# ifconfig -a

bond0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

bond1 Link encap:Ethernet HWaddr 00:10:E0:71:D7:AF
UP BROADCAST RUNNING MASTER MULTICAST MTU:9000 Metric:1
RX packets:28018367 errors:0 dropped:65248 overruns:0 frame:0
TX packets:28847398 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:26596553879 (24.7 GiB) TX bytes:23573794016 (21.9 GiB)

bond1.398 Link encap:Ethernet HWaddr 00:10:E0:71:D7:AF
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:27325217 errors:0 dropped:0 overruns:0 frame:0
TX packets:28847398 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:26155649548 (24.3 GiB) TX bytes:23573794016 (21.9 GiB)

br344 Link encap:Ethernet HWaddr 00:10:E0:71:D7:B1
inet addr:xx.xx.xx.xx Bcast:xx.xx.xx.xx Mask:xx.xx.xx.xx
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1218479 errors:0 dropped:0 overruns:0 frame:0
TX packets:442210 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:562244193 (536.1 MiB) TX bytes:76879535 (73.3 MiB)

br398 Link encap:Ethernet HWaddr 00:10:E0:71:D7:AF
inet addr:xx.xx.xx.xx Bcast:xx.xx.xx.xx Mask:xx.xx.xx.xx
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:27317802 errors:0 dropped:16 overruns:0 frame:0
TX packets:28841339 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:26155255218 (24.3 GiB) TX bytes:23573515302 (21.9 GiB)

eth0 Link encap:Ethernet HWaddr 00:10:E0:71:D7:AE
inet addr: xx.xx.xx.xx Bcast:xx.xx.xx.xx Mask:xx.xx.xx.xx
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:42 (42.0 b)

eth1 Link encap:Ethernet HWaddr 00:10:E0:71:D7:AF
UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1
RX packets:39793 errors:0 dropped:39793 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2387580 (2.2 MiB) TX bytes:0 (0.0 b)

eth2 Link encap:Ethernet HWaddr 00:10:E0:71:D7:AF
UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1
RX packets:27978574 errors:0 dropped:0 overruns:0 frame:0
TX packets:28847398 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:26594166299 (24.7 GiB) TX bytes:23573794016 (21.9 GiB)

eth3 Link encap:Ethernet HWaddr 00:10:E0:71:D7:B1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7408306 errors:0 dropped:2050330 overruns:0 frame:0
TX packets:457253 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1863644520 (1.7 GiB) TX bytes:77754665 (74.1 MiB)

eth3.344 Link encap:Ethernet HWaddr 00:10:E0:71:D7:B1
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1218785 errors:0 dropped:0 overruns:0 frame:0
TX packets:448298 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:562290325 (536.2 MiB) TX bytes:77164243 (73.5 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:58787 errors:0 dropped:0 overruns:0 frame:0
TX packets:58787 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:34021132 (32.4 MiB) TX bytes:34021132 (32.4 MiB)

usb0 Link encap:Ethernet HWaddr 02:21:28:57:47:17
inet addr:xx.xx.xx.xx Bcast:xx.xx.xx.xx Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7529 errors:0 dropped:0 overruns:0 frame:0
TX packets:5068 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:981124 (958.1 KiB) TX bytes:878176 (857.5 KiB)

# ls -l /sys/class/net/eth?
lrwxrwxrwx 1 root root 0 Oct 24 16:46 /sys/class/net/eth0 -> ../../devices/pci0000:00/0000:00:02.0/0000:20:00.0/net/eth0
lrwxrwxrwx 1 root root 0 Oct 24 16:46 /sys/class/net/eth1 -> ../../devices/pci0000:00/0000:00:02.0/0000:20:00.1/net/eth1
lrwxrwxrwx 1 root root 0 Oct 24 16:46 /sys/class/net/eth2 -> ../../devices/pci0000:80/0000:80:01.0/0000:88:00.0/net/eth2
lrwxrwxrwx 1 root root 0 Oct 24 16:46 /sys/class/net/eth3 -> ../../devices/pci0000:80/0000:80:01.0/0000:88:00.1/net/eth3

# cat /sys/devices/pci0000:00/0000:00:02.0/0000:20:00.0/net/eth0/address
00:10:e0:71:d7:ae
# cat /sys/devices/pci0000:00/0000:00:02.0/0000:20:00.1/net/eth1/address
00:10:e0:71:d7:af
# cat /sys/devices/pci0000:80/0000:80:01.0/0000:88:00.0/net/eth2/address
00:10:e0:71:d7:af
# cat /sys/devices/pci0000:80/0000:80:01.0/0000:88:00.1/net/eth3/address
00:10:e0:71:d7:b1

Root cause is incorrect MAC address retrieval due to network interfaces are part of bond network.

Solution

Current HMP version is not supporting firmware update on network interface which are part of bond
You can use below workaround:

1)you could boot into OSA, and update network card firmware from there.
If the firmware needed is not available, you could update OSA to the latest version, and then update firmware from OSA.
Refer the below guide for updating OSA
https://docs.oracle.com/cd/E23161_01/html/E37044/gkvvd.html

2)Break the bond network, update the network controller firmware using HMP, create the bond network

INTERNAL NOTE: HMP team is planning to fix this issue with future release 2.4

Attachments

This solution has no attachment