From where the errors come from...

Started by TheGreatDoc, February 07, 2016, 06:24:45 AM

Previous topic - Next topic

TheGreatDoc

Hi NFS Pro Dudes,

Im saying for a time big peaks of errors on some ports of my switches.

How can I debug from where the errors come from and what is causing them?
a.k.a. Daniel.
I dont have any cert, just learned all by my self.

SimonV

What sort of errors are you seeing exactly?

TheGreatDoc

Graphed by cacti from default interface errors/discards template.

a.k.a. Daniel.
I dont have any cert, just learned all by my self.

deanwebb

If you could post the errors, we could take a look at them. Just modify machine names and IP addresses if those would reveal anything that shouldn't be revealed, and we'll look at them.
Take a baseball bat and trash all the routers, shout out "IT'S A NETWORK PROBLEM NOW, SUCKERS!" and then peel out of the parking lot in your Ferrari.
"The world could perish if people only worked on things that were easy to handle." -- Vladimir Savchenko
Вопросы есть? Вопросов нет! | BCEB: Belkin Certified Expert Baffler | "Plan B is Plan A with an element of panic." -- John Clarke
Accounting is architecture, remember that!
Air gaps are high-latency Internet connections.

TheGreatDoc

Quote from: deanwebb on February 07, 2016, 08:10:28 AM
If you could post the errors, we could take a look at them. Just modify machine names and IP addresses if those would reveal anything that shouldn't be revealed, and we'll look at them.
And that is exactly my question. Where can i look further than a "show interface"?
a.k.a. Daniel.
I dont have any cert, just learned all by my self.

srg

What platform is this? (this kind of counters are often very platform specific)
som om sinnet hade svartnat för evigt.

TheGreatDoc

Its a Cisco C3750. But as far I can see, the errors showed in graph are not in the "show interface" command.....
a.k.a. Daniel.
I dont have any cert, just learned all by my self.

GeorgeS

play a bit with the show controller command, i am a bit busy this morning and do not have the time to find  a c3750 in our network.  sh controller ethernet (something) should be what are you looking. 

dlots

Errors come mostly from duplex mismatches and bad cables in my experiance

TheGreatDoc

The thing is that the errors/discards are not constant and the dont come in the heavy traffic timeline.

a.k.a. Daniel.
I dont have any cert, just learned all by my self.

icecream-guy

Quote from: TheGreatDoc on February 11, 2016, 04:17:31 AM
The thing is that the errors/discards are not constant and the dont come in the heavy traffic timeline.

It could also be EMF radiation, e.g. cables are run too close to fluorescent lights, so when someone goes and turns a light on, someone else network becomes slow.   

I've seen this when I worked in a large warehouse where the network cables were run up in the top of the warehouse along with the lighting and electrical with wires run down around electrical conduit to the workstations...and they wondered why the network was slow...

:professorcat:

My Moral Fibers have been cut.

matgar

Quote from: TheGreatDoc on February 07, 2016, 09:24:01 AM
Its a Cisco C3750. But as far I can see, the errors showed in graph are not in the "show interface" command.....
You could give this a try.

sh controllers ethernet-controller GigabitEthernet x/y/z


I also found this list of commands for trouble shooting links.

Show interface status | inc connected
Test cable-diagnostics tdr interface <>
Show cable-diagnostic tdr interface <>
Show interface <>
Show interface <> counters
Show interface <> counters errors
Show interface counter errors
Show controller Ethernet-controller <>
Show platform pm if-numbers
Show controllers Ethernet-controller port-asic statistics
Show platform port-asic stats drop <>