Device Interface Warning - Enslaved Device Eth<xx> is Down in Rackmount Server

Asset ID:	1-72-2324767.1
Update Date:	2017-11-05
Keywords:

Solution Type Problem Resolution Sure

Solution 2324767.1 : Device Interface Warning - Enslaved Device Eth is Down in Rackmount Server

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 5.1 and later
Information in this document applies to any platform.

Symptoms

Syscheck on the TVOE platform (for a rack mount server) shows for net module:

Running modules in class net...
     * ipbond: FAILURE:: MINOR::5000000000002000 -- Device Interface Warning
     * ipbond: FAILURE:: Enslaved device eth<XY> is down    [where <XY> is the port number, e.g. eth02]
     One or more module in class "net" FAILED

Viewing /proc/net/bonding/bond<Z> [where <Z> is the bond number, e.g. bond0], the MII status shows Down and the Speed and Duplex show Unknown

Slave Interface: eth<XY>
     MII Status: down    < ============= down ======
     Speed: Unknown    < ============= Unk ======
     Duplex: Unknown    < ============= Unk ======
     Link Failure Count: 2
     Permanent HW addr: 10:60:4b:a4:c1:bc
     Slave queue ID: 0

Viewing the interface (#ifconfig eth<XY>) successively shows no receive (RX) or transmit (TX) values incrementing.

eth<XY> Link encap:Ethernet HWaddr 10:60:4B:A4:C1:BC
                  UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
                  RX packets:39001956 errors:0 dropped:0 overruns:0 frame:0    < === RX unchanged over time ====
                  TX packets:37358630 errors:0 dropped:0 overruns:0 carrier:0    < === TX unchanged over time ====
                  collisions:0 txqueuelen:1000
                  RX bytes:0 (0 b) TX bytes:(0 b)
                  Interrupt:36 Memory:f4800000-f4ffffff

Changes

Since this is TVOE, no recent change may be known. TVOE host environments do not alarm on the application, but may generate a SNMP trap notification.

Cause

The Symptoms are indicative of either a faulty or removed cable from the interface (either locally or on remote end), or the interface on the remote end is administratively disabled.

Solution

Trace the cable, checking integrity and ensuring the connections are securely inserted in the appropriate ports at both ends. Access the remote equipment (switch or router) and check administrative and operational states. Address any problems identified. If unable to identify any issue, replace cable and/or move to another port on the remote premise equipment.

Attachments

This solution has no attachment