Increasing Frame Errors On Interfaces Eth1/eth2 On Exadata 10Gb

Asset ID:	1-72-1488923.1
Update Date:	2017-05-08
Keywords:

Solution Type Problem Resolution Sure

Solution 1488923.1 : Increasing Frame Errors On Interfaces Eth1/eth2 On Exadata 10Gb

Applies to:

Exadata Database Machine X2-2 Hardware - Version All Versions and later
Information in this document applies to any platform.
***Checked for relevance on 04-Dec-2015***

Symptoms

ifconfig output on DB node shows frame errors increasing on eth1 (10Gb Client uplink):

eth1 Link encap:Ethernet HWaddr 00:21:28:D4:EE:D3
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:32760569 errors:26666 dropped:0 overruns:0 frame:26666 <------
TX packets:344718986 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10000
RX bytes:4845720582 (4.5 GiB) TX bytes:505206608821 (470.5 GiB)
Memory:df0e0000-df100000

The following output errors are seen in the show interface output on the Customer client network switch:

Cisco#show interface tengigabit ss/pp status (where ss/pp is the slot and port that is connected to the db node port that is showing RX errors)

42637428 unicast packets 5533870 multicast packets 66599 broadcast packets
48340033 output packets 14553936880 bytes
0 jumbo packets
102136 output errors 0 collision 0 deferred 0 late collision<============ Output errors reported.
0 lost carrier 0 no carrier 0 babble

Cause

Defective cable between dbnode eth1 and and client network Cisco switch

Solution

Customer replaced their cable between dbnode eth1 and Cisco switch (Client network)

Attachments

This solution has no attachment