topic Re: Errors on interface connected to WAN in Switches, Hubs, and Modems

Errors on interface connected to WAN

KCollinson — Fri, 27 Feb 2009 14:45:55 GMT

Afternoon All,

Why am i getting alot of the following errors on the uplink interface to the WAN Router.

Drops Rx 222,234
Collisions TX 800,000
Late Colln 169,766
Deferred Tx 1,3921,499

Interface 1 on Switch set to Full Duplex @ 100

Interface 1 on Router set to Full Duplex @ 100

No VLAN is tagged on uplink / uplink is assigned to Data VLAN and untagged.

Quick over on Switch.
3x VLANs
Vid1 (Default)
Vid2 (Data)
Vid3 (VoIP)

using default route 0.0.0.0 0.0.0.0 192.168.0.254

Any Ideas?
Thx!

Re: Errors on interface connected to WAN

KCollinson — Fri, 27 Feb 2009 14:47:53 GMT

Ignore Vid 2 Please!!!
Data is all on Default.
Thx.

Re: Errors on interface connected to WAN

Richard Brodie_1 — Fri, 27 Feb 2009 15:10:48 GMT

You shouldn't be seeing collisions increase in Full Duplex mode, by definition.

So the obvious question is "are you *sure* that the switch interface 1 is operating in Full Duplex mode?" Sorry for having to ask it.

Re: Errors on interface connected to WAN

KCollinson — Fri, 27 Feb 2009 15:49:23 GMT

Thanks for you reply Richard,

I can confirm the interface is set to Manual @ 100 Full Duplex.

Looking to replace Uplink cable asap.
Any other recommedations or tips?
Thanks,
Karl

Re: Errors on interface connected to WAN

cenk sasmaztin — Fri, 27 Feb 2009 18:30:37 GMT

many collisions and packet drop issue be happen aoutonegotiation division between two device

aoutonegotiation being between two device each device check speed dublex and mdi mode,freame size etc.

so if make set on two port for example 100-full very good

my advice
now you must be set mdi mode on swithc port
if you have patch ceble strain through cable (standart 568 A or B cable)
take switch port mdix mode not to leave auto

for example
switch(eth-14)# mdix-mode mdix [enter]

Re: Errors on interface connected to WAN

Richard Brodie_1 — Tue, 03 Mar 2009 10:02:18 GMT

It feels like an autonegotiation problem, even if it shouldn't be one. If it's in FD mode, collision detection should be disabled.

Not sure what to suggest, except bringing the link up and down, seeing if that changes everything. I'd be tempted to try autonegotation or even forcing HD at both ends (keeping track of the counter differences).

I assume the WAN link is likely less that 100Mbit/s, if so running the link to it HD is going to make no practical difference, as long as it's reasonably error free.

Re: Errors on interface connected to WAN

KCollinson — Tue, 03 Mar 2009 19:35:06 GMT

Evening Chaps,

Thanks for all the replys!!!

Replaced the MDIx cable and forced the interface to MDIx not auto and the counters are staying at 0

PS the WAN link speed is 100Mb.

Cheers,
Karl.