Details
Major Description
I've recently added three(3) customers of mine to Observium. These customers have FS.COM PoE+ Switches in their environments. No known issues.
I have these switches for other clients as well.
However, so far all three(3) of these switches are showing all the ACTIVE interfaces having errors on the port.... no way three(3) of my clients have wiring issues!?
Like to have the latest FS.COM MIB package loaded.
Attachments
Activity
| Resolution | New: Not A Bug [ 6 ] | |
| Status | Original: In Review [ 10101 ] | New: Closed [ 6 ] |
| Status | Original: Pending Response [ 10000 ] | New: In Review [ 10101 ] |
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
| Status | Original: In Review [ 10101 ] | New: Pending Response [ 10000 ] |
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.
| Attachment | New: Screen Shot 2021-07-06 at 11.42.48 PM.png [ 18830 ] | |
| Attachment | New: Screen Shot 2021-07-06 at 11.42.42 PM.png [ 18831 ] |
| Status | Original: Pending Response [ 10000 ] | New: In Review [ 10101 ] |
@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#
| Status | Original: In Review [ 10101 ] | New: Pending Response [ 10000 ] |
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.