ODA (Oracle Database Appliance): 'eth0' reports FIBRE instead of Twisted Pair (TP)

Asset ID:	1-72-2078072.1
Update Date:	2015-11-30
Keywords:

Solution Type Problem Resolution Sure

Solution 2078072.1 : ODA (Oracle Database Appliance): 'eth0' reports FIBRE instead of Twisted Pair (TP)

Applies to:

Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Linux x86-64

Symptoms

The output for 'eth0' reports FIBRE instead of Twisted Pair (TP) even though copper was chosen during deployment:

dom 0

[root@oda_dom_0 ~]# ethtool eth0
Settings for eth0:
Supported ports: [ FIBRE ] <<<<<<<<<<<<<

dom1

[root@oda_dom_1 ~]# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]

[root@odarac01n0 ~]# oakcli validate -v -c NetworkComponents
DEBUG: parseArgs: running named checks
DEBUG: runNamedChecks: inside named checks fn
DEBUG: runNamedChecks: calling check function NetworkComponents
INFO: Doing oak network checks
DEBUG: oakNetworkInfo: oak network info
DEBUG: checkLinkStatus: Checking link status
RESULT: Detected active link for interface eth0 with link speed 100Mb/s and cable type as Other <<<<<<<<<<<<<
RESULT: Detected active link for interface eth1 with link speed 1000Mb/s and cable type as TwistedPair
RESULT: Detected active link for interface eth2 with link speed 1000Mb/s and cable type as TwistedPair
RESULT: Detected active link for interface eth3 with link speed 1000Mb/s and cable type as TwistedPair

[root@odarac01n1 ~]# oakcli validate -v -c NetworkComponents
DEBUG: parseArgs: running named checks
DEBUG: runNamedChecks: inside named checks fn
DEBUG: runNamedChecks: calling check function NetworkComponents
INFO: Doing oak network checks
DEBUG: oakNetworkInfo: oak network info
DEBUG: checkLinkStatus: Checking link status
RESULT: Detected active link for interface eth0 with link speed 1000Mb/s and cable type as TwistedPair
RESULT: Detected active link for interface eth1 with link speed 1000Mb/s and cable type as TwistedPair
RESULT: Detected active link for interface eth2 with link speed 1000Mb/s and cable type as TwistedPair
RESULT: Detected active link for interface eth3 with link speed 1000Mb/s and cable type as TwistedPair

This can lead to connection for this port drop to 100 Mb/s causing slowness in accessing VMs and inaccessible VMs.

Cause

Linux makes a best guess as to the cable type, but when there is something wrong with the speed, it often guesses "FIBRE".

Anytime the speed drops down to 100Mb/s, we can suspect issue with either the cabling, switch port or maybe even the port on the motherboard itself.

Solution

Steps to take to isolate the problem:

* Swap cables between NET0 of node0 and NET0 of node1: does the problem follow the cable or stay with the node?

* Swap cables on the switch side: does the problem stay with the switch port or with the node?

If the issue still persists, there might be a problem with the motherboard. Open a Service Request for Hardware team review and provide the data collection from <Document 1682640.1> SRDC - EEST ODA ILOM Snapshot.

References

<NOTE:1682640.1> - SRDC - EEST ODA ILOM Snapshot

Attachments

This solution has no attachment