Network interfaces hangs

SUSE Linux Enterprise Server SLES Networking
1

Hi Everyone,

Following error found on /var/log/messages…

Oct 13 22:04:28 sapnode02 corosync[22212]: [TOTEM ] A processor failed, forming new configuration.
Oct 13 22:04:29 sapnode02 kernel: [1220257.488119] net eth1: firmware hang detected
Oct 13 22:04:29 sapnode02 kernel: [1220257.488135] net eth0: firmware hang detected
Oct 13 22:04:29 sapnode02 kernel: [1220257.488147] net eth2: firmware hang detected
Oct 13 22:04:29 sapnode02 kernel: [1220257.488158] net eth3: firmware hang detected
Oct 13 22:04:29 sapnode02 kernel: [1220257.524101] bonding: bond0: link status definitely down for interface eth2, disabling it
Oct 13 22:04:29 sapnode02 kernel: [1220257.524124] bonding: bond0: now running without any active interface !
Oct 13 22:04:29 sapnode02 kernel: [1220257.524131] bonding: bond0: link status definitely down for interface eth3, disabling it
Oct 13 22:04:29 sapnode02 kernel: [1220257.573657] netxen_nic 0000:04:00.3: phanfw.bin: firmware is older than flash
Oct 13 22:04:29 sapnode02 firmware.sh[31719]: Cannot find firmware file ‘nx3fwct.bin’

Note: OS is SLES 11 SP2 SAP version. After sometime the connection comes back again
What can be the cause and how can I get this sort out??Your help on this highly appreciated.

2

Hi
Is the qlogic-firmware package installed?

–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 12.2 (x86_64) Kernel 3.4.11-2.16-desktop
up 21:28, 4 users, load average: 0.27, 0.19, 0.20
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

3

Hi Malcolm,

I really don’t think so. Let me check this and get back to you. we have to similar HP ProLiant DL585 G7 server. SLES 11 SP2 SAP version running on both servers. but only one server gives this issue.

4

Hi Malcolm,

The fibre cards are qlogic. following is the out put from lspci…

02:00.0 System peripheral: Hewlett-Packard Company Integrated Lights-Out Standard Slave Instrumentation & System Support (rev 04)
02:00.2 System peripheral: Hewlett-Packard Company Integrated Lights-Out Standard Management Processor Support and Messaging (rev 04)
02:00.4 USB controller: Hewlett-Packard Company Integrated Lights-Out Standard Virtual USB Controller (rev 01)
03:00.0 RAID bus controller: Hewlett-Packard Company Smart Array G6 controllers (rev 01)
04:00.0 Ethernet controller: NetXen Incorporated NX3031 Multifunction 1/10-Gigabit Server Adapter (rev 42)
04:00.1 Ethernet controller: NetXen Incorporated NX3031 Multifunction 1/10-Gigabit Server Adapter (rev 42)
04:00.2 Ethernet controller: NetXen Incorporated NX3031 Multifunction 1/10-Gigabit Server Adapter (rev 42)
04:00.3 Ethernet controller: NetXen Incorporated NX3031 Multifunction 1/10-Gigabit Server Adapter (rev 42)
08:00.0 RAID bus controller: Hewlett-Packard Company Smart Array G6 controllers (rev 01)
40:00.0 Host bridge: ATI Technologies Inc RD890 Northbridge only dual slot (2x16) PCI-e GFX Hydra part (rev 02)
40:0b.0 PCI bridge: ATI Technologies Inc RD890 PCI to PCI bridge (NB-SB link)
40:0c.0 PCI bridge: ATI Technologies Inc Device 5a20
44:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02)
44:00.1 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02)
47:00.0 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02)
47:00.1 Fibre Channel: QLogic Corp. ISP2532-based 8Gb Fibre Channel to PCI Express HBA (rev 02)

5

Hi lash04,

grab yourself a bag of tissues and start reading http://wahlnetwork.com/2011/08/16/identifying-and-resolving-netxen-nx_nic-qlogic-nic-failures/ - it seems these adapters are likely the root cause of the problem and you’re not alone… :confused:

Sorry for the not-help,
Jens

6

Hi everyone,

For the network firmware hang, HP gave a new driver (nx_nic) to be installed. It seems that when you do a firmware upgrade for an Ethernet Interface which is not configured or is in a slave bonding configuration, the upgrade will not work as expected. This was the cause for the network hang and we are monitoring the status of network connectivity after properly carried out firmware upgrade. I think the problem is sorted out but we are still monitoring on this matter and I will write to you back with the status on this.