May 09, 2012 Hi there, Some relevant show commands are given below for a cisco router whose L2 on Serial interface seems to be going up. An explanation of the alarm and common troubleshooting. Alarm indication signal. The AIS failure is declared when an AIS defect is detected at the. Troubleshooting Cisco interface. Biggybiggy Aug 6, 2012 12:29 PM. Aug 1 2:23:09:%CONTROLLER-5-UPDOWN: Controller T1 0/0/0, changed state to down (AIS detected).

Ask questions, create discussions or post news! This subreddit is for all things Cisco related!

This subreddit is not affiliated with Cisco Systems. Related subreddits: - - - - - - Useful Links • Rules • Be respectful to others. • No questions about how to get Cisco software without a service contract. • No posting or discussion of brain dumps. • Stay on topic • No sales posts NOTE: The 'Reddit Cisco Ring', its associates, subreddits, and creator 'mechman991' are not endorsed, sponsored, or officially associated with Cisco Systems Inc. All opinions stated are those of the poster only, and do not reflect the opinion of Cisco Systems Inc., or its affiliates.

Last Update: April 14th, 2016. I have a Cisco 1700 with a t1 CSU/DSU card (really old found in a closet. Fs9 Aerosoft Luxembourg Airports Ellx Airport. ) and a Cisco 1941 (brand new) with a T1 card as well. These two are connected via a RJ48 cable and I can ping from one side of the router to the other. The new 1941 is getting RAI detected and the T1 connection goes down. As far as I can tell, there is no rhyme or reason as to why this is happening. I am not 100% sure the configuration is correct but I am more thinking this is a hardware issue.

This RAI detected issue happens frequently (every couple of seconds) Off the top of my head, the serial connections are PPP encapsulated, link code is r8, 1941 timing is internal, 1700 is line. I can post the config if you think this is possibly the issue. This is currently just a lab situation where these are sitting right next to each other with the rj48 cable. They will be put over a point to point connection over an mpls connection once configurations are setup correctly. Unfortunately, 1 end is in Chicago and the other is in Ohio so I would like for the test to work before I ship out hardware. So - do you think I have faulty hardware or config.

(PS - if you cant tell. I am not highly knowledgeable in the matter. Just enough to be dangerous.) • • • • •.

The linecode hdb3 is a dafult line code for E1. You can check it out in show controllers command and you will find it. 1995 Jayco Pop Up Camper Specs. Some time we miss use default and which does create some problems and issue in the configuration and depends on how ios behaves.

It was just to confurm that all the conigs are done on the interface. As above it was also siad that this could be a line problem with the isp which i totaly agree. As you said the flapping is 1 time in about 2 days would not be a big deal for me if the downtime is in seconds and is not casueing any problems to the production network. In case if this is causing an outage to the network then you need to get it reolved. I would also suggest to get the line tested from both the direction with the telco.

A stress test. Hi, The serial int is up and running. Below is the output data for controller/int statistics: Router A #show controllers E1 E1 0/2 is up. Applique type is Channelized E1 - balanced No alarms detected. Alarm-trigger is not set Version info Firmware: 20030807, FPGA: 11 Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line. CRC Threshold is 320. Reported from firmware is 0.

Data in current interval (536 seconds elapsed): 0 Line Code Violations, 0 Path Code Violations 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs Total Data (last 24 hours) 0 Line Code Violations, 0 Path Code Violations, 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins, 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs E1 0/3 is down. Applique type is Channelized E1 - balanced Far End Block Errors Detected Receiver has loss of signal. Alarm-trigger is not set Version info Firmware: 20030807, FPGA: 11 Framing is CRC4, Line Code is HDB3, Clock Source is Line. CRC Threshold is 320. Reported from firmware is 0.