Ethernet errors

I have been trying to see where I can look at an ethernet port and see if there are any errors. I put in a Mikrotik and had to take it out as I found there were errors on the interface going to a Cisco Router. So, I have been getting leary of all my other Mikrotiks in my network and how I can see if they are running correctly.

Can anyone tell me where to look or if it isn’t possible?

Tom

Such information is not available. You may try to get some values over snmp for ‘interface print oid’.

I wonder why such important information is not accessible via winbox/console?

BTW: the SNMP counters are not much usable (on other devices like cisco too) because you see only one error counter (ifInErrors) which accumulates all possible errors often oncluding packet collisions on half duplex links. To know the health of the link one should see counters for CRCs, frames, overruns, collisions, late collisions, lost carriers a counter which accumulates all the error, etc.
Maybe linux drivers (or network card itself) doesn’t provide such counters, But if it is possible the behavior should change to allow this level of details about NIC and packets/frames

Information that you mention is not available at RouterOS.

I know. But if the network cards/chips support more details about errors it would be fine if RouterOS displays them

I have a Mikrotik hotspot controller that the ether2 port goes directly into an InscapeData wireless radio. I seemed to be having problems with the interface, so I switched it to 10mb FD. So far so good, but I sure wish I could see if there were any errors. There is not that capability in the inscape, so I’m reliant on the Mikrotik. On my linux boxes, I can just do a ifconfig and it will tell me the error count for the ethernet. This would be one of the few things I have found I can’t do somehow in the Mikrotik. There hasn’t been many.

Tom

I think you can add it as a feature request there: http://wiki.mikrotik.com/wiki/MikroTik_RouterOS/v3/Feature_Requests

It’d be nice to be able to check layer1 properties, at least those already available in ifconfig, in case something screws up at this level.

          RX packets:xxx errors:0 dropped:0 overruns:0 frame:0
          TX packets:yyy errors:0 dropped:0 overruns:0 carrier:0
          collisions:0

You know, shit happens, and then it is always too late…

Regards,
Andrzej