Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

CRC Errors on devices

My NOC is asking me to setup CRC collection on all routers (Cisco). There has to be an easier way than to create a custom poller and assign it to every WAN interface. We're talking about over 1,000 interfaces. This would be a logistical nightmare to manage, especially when adding and deleting devices.

If that is the only way to go, does anyone know the oid for CRC errors.

Thanks in advance...

Find more posts tagged with

Accepted answers

All comments

charly_DF

mmm i collect CRC with an script that run the command "sh int serial x/x/x | inc CRC" and then a program with regex give me a list

charly_DF

CRC????

WARNING: This interface has received a high
number (99.99893% of input packets) of packets with incorrect CRCs (corrupted
data) (> 0.1%). Problems that
may cause this symptom include:

<![if !supportLists]>
style='mso-list:Ignore'>a.
<![endif]>Noisy serial line

<![if !supportLists]>
style='mso-list:Ignore'>b.
<![endif]> Serial cable is too long or
cable from the CSU/DSU to the router is not shielded

<![if !supportLists]>
style='mso-list:Ignore'>c.
<![endif]>SCTE mode is not enabled on the
DSU

<![if !supportLists]>
style='mso-list:Ignore'>d.
<![endif]>The CSU line clock is
incorrectly configured

<![if !supportLists]>
style='mso-list:Ignore'>e.
<![endif]> A Ones density problem on the
link (incorrect framing or coding specification), exists

<![if !supportLists]>
style='mso-list:Ignore'>f.
<![endif]>Verify the queuing strategies
are the same on both ends of the link.

TRY THIS:

1. Ensure that the line is clean enough for
transmission requirements. Shield the cable if necessary.

2. Make sure the cable is within the
recommended length (no more than 50 feet [15.24 meters], or 25 feet [7.62
meters] for the link).

3. Ensure that all devices are properly
configured for a common line clock. Set serial clock transmit external (SCTE)
on the local and remote DSU. If you are attempting serial connections at speeds
greater than 64 kbps with a CSU/DSU that does not support (SCTE), you might
have to invert the transmit clock on the router. Inverting the transmit
clock compensates for phase-shifts between the data and clock signals.

4. Make certain that the local and remote
CSU/DSU are configured for the same framing and coding scheme as that used by
the leased-line or other carrier service (for example, ESF/B8ZS).

5. Contact your leased-line or other
carrier service and have them perform integrity tests on the line.

Nux

Here are the OID and MIB for collecting CRC errors on an interface.

This is for CISCO

interface CRC Errors /OID/MIB

1.3.6.1.4.1.9.2.2.1.1.12

OLD-CISCO-INTERFACES-MIB:locIfInCRC

Emilio

I have the same requirement. I already created a custom poller with the OID mentioned here. I tested and was Ok but with value of 0.

I indicated Counter and Keep real-time and historical statistics. But, Orion view shows me always a value of 0 for all my interfaces (+2000). The only data that really updates here, is the date for the polling.

Something like this at Orion's view once I selected a serial interface :

CRC_Errors (name of my custom poller) 0 Last polled: <current time>

any ideas to solve my problem would be appraciated.

Thanks in advance

Orion SLX 8.5.1 SP3

NTA 3

Nicki

I have seen and tried many templates, scripts, and mrtg to collect data on crc errors, input errors, etc. As of yet, I have not seen one that works.

I challenge anyone to step up to the plate. We all know what the OIDs are, but have any of us got this to work? Even in MRTG?

Let me and the rest of the world in on the bi--i-i-i-i-i-g secret!

Thanks.

FormerMember

The answer for a cisco was already given. You have to use the old-cisco-interfaces mib. Mileage may vary though if not supported in your version of IOS. If you ever cleared counters on the interface, the number through SNMP isn't going to match. SNMP counters only clear on reload. It works for me. I have it set as an interface poller and raw value, counter gave me zeros. Keep in mind it is a running total.

Other vendors you'll need to check if supported in their private MIB.

You could also try the going after the the mib2 transmission mib for the type of interface and get DSU/CSU perspective.

Uploaded it if you want to test drive the poller.

crc.JPG