Operating System - Tru64 Unix
1827894 Members
1540 Online
109969 Solutions
New Discussion

Re: error netstat -I

 
Michael Schulte zur Sur
Honored Contributor

error netstat -I

Hi,

does that indicate a bad cable?

Thanks for any help,

Michael

45 send failures, reasons include:
45 short circuit
5 REPLIES 5
Ivan Ferreira
Honored Contributor

Re: error netstat -I

With a bad cable normally you will have a fair number of input and output errors. What is the output of netstat -ni?
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Michael Schulte zur Sur
Honored Contributor

Re: error netstat -I

Hi,

thanks for the post.
This is the output.

Michael

Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
tu0 1500 00:06:2b:00:cd:56 158318020 218 181198535 1940 0
tu0 1500 DLI none 158318020 218 181198535 1940 0
tu0 1500 2.49.119/24 2.49.119.30 158318020 218 181198535 1940 0
Ivan Ferreira
Honored Contributor

Re: error netstat -I

This looks to me like a real problem. You don't have collisions, so this should indicate that the speed and duplex negotiation or setting is correct, but you may want to verify that first.

Start by replacing the conection to the switch, then replace cable.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Ivan Ferreira
Honored Contributor

Re: error netstat -I

Yet is a small number, I don't know how long the system was running. Normally, I have 0 for input and output errors on all my systems. If the errors does not grow, maybe you don't have to worry too much.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Michael Schulte zur Sur
Honored Contributor

Re: error netstat -I

Hi Ivan,

thanks for the comment. I have resetted the counter and will monitor it the next days. Then I will have to see how I can get a hold of the people there because it is another site.

Michael