charly_DF replied on Thu, Mar 13 2008 9:47 PM

rated by 0 users

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: 

a.       Noisy serial line  

b.       Serial cable is too long or cable from the CSU/DSU to the router is not      shielded  

c.       SCTE mode is not enabled on the DSU  

d.      The CSU line clock is incorrectly configured  

e.       A Ones density problem on the link (incorrect framing or coding      specification), exists 

f.        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 replied on Sun, Mar 16 2008 4:05 PM

rated by 0 users

 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 replied on Fri, Jul 4 2008 2:08 PM

rated by 0 users

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