topic Re: Inbound Errors in lan in Operating System - HP-UX

Inbound Errors in lan

Carme Torca — Thu, 01 Apr 2004 09:03:20 GMT

Hi,

I have a server that has a lot of Inbound Errors... but no Outbound Errors....
I have clean the statistics and I have transfer a file with 15689454 bytes to the server and it's returns me:

LAN INTERFACE STATUS DISPLAY
Thu, Apr 1,2004 15:49:46

PPA Number = 0
Description = lan0 HP PCI 10/100Base-TX Core [100BASE-TX,FD,MANUAL,TT=1500]
Type (value) = ethernet-csmacd(6)
MTU Size = 1500
Speed = 100000000
Station Address = 0x306e1bcc08
Administration Status (value) = up(1)
Operation Status (value) = up(1)
Last Change = 5497
Inbound Octets = 35825170
Inbound Unicast Packets = 16465
Inbound Non-Unicast Packets = 9
Inbound Discards = 0
Inbound Errors = 2394
Inbound Unknown Protocols = 0
Outbound Octets = 1058177
Outbound Unicast Packets = 13212
Outbound Non-Unicast Packets = 1
Outbound Discards = 0
Outbound Errors = 0
Outbound Queue Length = 0
Specific = 655367

Press to continue

Ethernet-like Statistics Group

Index = 1
Alignment Errors = 1179
FCS Errors = 2394
Single Collision Frames = 0
Multiple Collision Frames = 0
Deferred Transmissions = 0
Late Collisions = 0
Excessive Collisions = 0
Internal MAC Transmit Errors = 0
Carrier Sense Errors = 0
Frames Too Long = 0
Internal MAC Receive Errors = 0

Maybe is this a problem with the target??

Thanks!,
Carmen.

Re: Inbound Errors in lan

Ian Box — Thu, 01 Apr 2004 09:23:32 GMT

My guess would be a duplex mis-match between the switch and your network card. Your card is set to 100 MB Full Duplex. The switch is probably set to 100 MB half duplex.

Ian

Re: Inbound Errors in lan

RAC_1 — Thu, 01 Apr 2004 09:30:17 GMT

What are the NIC settings. Your NIC is set to 100FD, check it is same on switch/router side.

Anil

Re: Inbound Errors in lan

rick jones — Fri, 02 Apr 2004 12:58:08 GMT

Notice in the description field how it says FD and manual? That means someone hardcoded the duplex setting of the NIC to full duplex. Unless it is _KNOWN_ to be broken on your switch, do not hardcode duplex settings on a NIC.

Hardcoding duplex settings on one side (HD or FD, doesn't matter) will cause the side trying to to autoneg to "fail" and when autoneg "fails" the side trying to autoneg is _required_ to go into half-duplex mode.

When a NIC is in FD mode, and there is a duplex mismatch, you will see FCS errors. When a NIC is in HD mode and there is a duplex mismatch, you will see late collisions.