Hi Akhil
the fact that there is an OID is good news. I guess the problem is with what we do with the data once is collected. Based on the MIB file (http://oidref.com/1.3.6.1.2.1.10.7.2.1.3), this OID is a COUNTER, meaning that we should store only the difference between the last poll and the new poll (also called DELTA value), because the value of this OID will never go down.
To make it clearer, when we start the device, the value of the OID will be 0. When there is a CRC error, the value of the OID will go to 1, and will remain 1 until there is another CRC error or when the device is rebooted. This can become a problem because if you don't store the value properly, it might be that after 6 months of the device being up, the CRC errors can be at 499, and the following one single CRC error will bring the metric to 500 and trigger the alert on your other NMS system.
In order to troubleshoot this further, we would need a graphic from both tools (SevOne and the other NMS) to compare how we are treating the data, because it might be that the issue is not in SevOne but on how the other tool has been configured.
------------------------------
Raul Gonzalez
Software Networking Solutions Architect
IBM
Brighton, UK
------------------------------
Original Message:
Sent: Fri September 15, 2023 05:13 AM
From: AKHIL Raj
Subject: Interface CRC error monitoring using Sevone
Hi Raul Gonzalez, Thank you for the support . We received OID details from Cisco reference to CRC - 1.3.6.1.2.1.10.7.2.1.3. I can see its already certified in Sevone and its populating the graph and data . But when we create the thresholds like if CRC more than 500 number > 10 min out of 15 min trigger alarm and It's not generating alert ( but the alert got triggered for same device and same criteria in different NMS tool ). while t-shooting the values showing up is bit confusing as average showing in 0.584 but total is more than 2k for a time window of 1hr.
So wanted to check in forum anyone have seen this issue or using the CRC monitoring effectively using SNMP data.
------------------------------
AKHIL Raj
Original Message:
Sent: Fri September 15, 2023 04:35 AM
From: Raul Gonzalez
Subject: Interface CRC error monitoring using Sevone
Hi Akhil
short answer: yes, it is possible.
long answer: one of the problems we have with vendors is that they don't normally share CRC errors using standardised protocols such as SNMP. Some times they try (like Cisco did with the OID .1.3.6.1.4.1.9.9.45.1.1.1.20) but most of them fail miserably :). So what options do we have? as you might possibly know, SevOne is able to collect any time series data, as long as that data is available in some kind of format. I understand that you are using some kind of CLI command to get the CRC errors, well, with SevOne you can do the same, execute that command (either using our nocode platform, or if you prefer using a custom script) and then ingest that data back into SevOne.
Similar principles can be found here: https://community.ibm.com/community/user/aiops/viewdocument/monitor-ibm-cloud-metrics-using-the?CommunityKey=fe9d91df-352c-4846-9060-189fd98d00ca&tab=librarydocuments where we are monitoring data coming from APIs.
------------------------------
Raul Gonzalez
Software Networking Solutions Architect
IBM
Brighton, UK
Original Message:
Sent: Thu September 14, 2023 12:55 PM
From: AKHIL Raj
Subject: Interface CRC error monitoring using Sevone
Can someone put some light on this subject. We have a requirement to monitor the CRC interface errors . Currently we tried to create it using fcs error counter but the value showing up in sevone is very less while averaging compare to the existing monitoring tool.
We are looking for some help to do a effective crc monitoring,
------------------------------
AKHIL Raj
------------------------------