FS.Com Switches -- all active interfaces show errors

Noted, good catch.

I've raised this issue to FS.com support staff.  Honestly, this is first time im seeing this on these switches. My prior NMS product didnt have the FS.COM MIBs so I never had much insight into these devices.

0 discard, 0 error, 0 PAUSE
0 align, 0 FCS, 0 symbol
0 jabber, 0 oversize, 1160780 undersize
0 carriersense, 0 collision, 0 fragment
0 L3 packets, 0 discards, 0 Header errors

0 discard, 0 error, 0 PAUSE
0 align, 0 FCS, 0 symbol
0 jabber, 0 oversize, 1160780 undersize
0 carriersense, 0 collision, 0 fragment
0 L3 packets, 0 discards, 0 Header errors

It’s probably rolling all of these into the ifErrors counter, so clogging it up by counting undersize frames.

@Adam - Thanks for looking into and the reply.

Here is interface output, no errors:

I'm also uploading two(2) new screenshots that associate with this port g0/16

For now I've modified the alert rule to exclude device vendor FS.COM from alerting on port errors.

OSG-SW02#sh int gig0/16
GigaEthernet0/16 is up, line protocol is up
protocolstatus upTimes 1, downTimes 0, last transition 1970-1-1 0:0:43
Ifindex is 16, unique port number is 16
Hardware is Giga-TX, address is 649d.9922.fa2d (bia 649d.9922.fa2d)
MTU 1500 bytes, BW 100000 kbit, DLY 10 usec
Encapsulation ARPA
Auto-Duplex(Full), Auto-Speed(100Mb/s), Flow-Control Off
5 minutes input rate 1474 bits/sec, 15 packets/sec
5 minutes output rate 29638 bits/sec, 39 packets/sec
Real time input rate 440 bits/sec, 59 packets/sec
Real time output rate 46476 bits/sec, 84 packets/sec
Received 278400 packets, 56664898 bytes
11027 broadcasts, 45556 multicasts 221817 ucasts
0 discard, 0 error, 0 PAUSE
0 align, 0 FCS, 0 symbol
0 jabber, 0 oversize, 1160780 undersize
0 carriersense, 0 collision, 0 fragment
0 L3 packets, 0 discards, 0 Header errors
Transmitted 3509612 packets, 595353004 bytes
2547352 broadcasts, 610433 multicasts 221817 ucasts
0 discard, 0 error, 0 PAUSE
0 sqettest, 0 deferred, 0 oversize
0 single, 0 multiple, 0 excessive, 0 late
0 L3 forwards
OSG-SW02#

Errors just come from ifInErrors and ifOutErrors, if those counters are being incremented, the device thinks it has seen errors.

These counters aren’t related to vendor mibs, and aren’t affected by them.

What various vendors consider as errors worth incrementing those counters is an altogether different matter.

You can likely see in the dot3 tables what the actual errors are (or in the switches CLI)

Also all these clients FS.COM switches, i have LLDP enabled and send to lldp-mib enabled. etc.

However, within Observium after a neighbor discovery is ran..... not all devices are populated in the Neighbours tab.  Only one or two devices appear. 

Where as, the same client or others have Cisco switches; the neighbours are partly correct... and shows devices connected.

Why is it not parsing the devices ARP table and putting that up into Neighbours?

snmp dump incoming..

Please make and attach additional information about the device:

• full snmp dump from device:

  snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk

  snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

  If device not support SNMP version 2c, replace -v2c with -v1.

• If you have problems with discovery or poller processes, please do and attach these debugs:

  ./discovery.php -d -h <device>

  ./poller.php -d -h <device>

• additionally attach device and/or vendor specific MIB files

Note, this comment is added automatically.