What is wrong with my connection?

[bmrash]

I have a router that has two T1s going into it to provide network connectivity at a remote site. One of the serial connections works fine, while other shows that it is down, and shows only an amber light. Here are the configurations of those ports:

THIS IS THE INTERFACE THAT DOES WORK

interface Serial0/0/1:1
ip address [omitted]

ip pim sparse-dense-mode

load-interval 30

auto qos voip trust

service-policy output AutoQoS-Policy-Trust

Serial0/0/1:1 is up, line protocol is up

  Hardware is DSX1

  Internet address is [omitted]

  MTU 1500 bytes, BW 1536 Kbit/sec, DLY 20000 usec,

  reliability 255/255, txload 4/255, rxload 7/255

  Encapsulation HDLC, crc 16, loopback not set

  Keepalive set (10 sec)

  Last input 00:00:00, output 00:00:00, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 25504

  Queueing strategy: Class-based queueing

  Output queue: 0/1000/0 (size/max total/drops)

  30 second input rate 43000 bits/sec, 31 packets/sec

  30 second output rate 27000 bits/sec, 49 packets/sec

     73044938 packets input, 3272617538 bytes, 0 no buffer

     Received 793500 broadcasts (4086001 IP multicasts)

     69122 runts, 852 giants, 0 throttles

     86734 input errors, 85876 CRC, 0 frame, 0 overrun, 0 ignored, 1449 abort

     73110921 packets output, 1989216531 bytes, 0 underruns

     0 output errors, 0 collisions, 4 interface resets

     0 unknown protocol drops

     0 output buffer failures, 0 output buffers swapped out

     19 carrier transitions

-------------------------------------------------
Device#   PID                   SN
-------------------------------------------------
*0        CISCO2911/K9          FTX1632AKS6    
         

Technology Package License Information for Module:'c2900'

-----------------------------------------------------------------
Technology    Technology-package           Technology-package
              Current       Type           Next reboot 
------------------------------------------------------------------
ipbase        ipbasek9      Permanent      ipbasek9
security      None          None           None
uc            uck9          Permanent      uck9
data          None          None           None

Configuration register is 0x2102

Serial0/0/1:1 is up, line protocol is up

THIS IS THE INTERFACE THAT IS NOT WORKING

interface Serial0/0/0:1
ip address [omitted]

load-interval 30
auto qos voip trust
service-policy output AutoQoS-Policy-Trust

Serial0/0/0:1 is down, line protocol is down
  Hardware is DSX1
  Internet address is [omitted]

  MTU 1500 bytes, BW 1536 Kbit/sec, DLY 20000 usec,
     reliability 240/255, txload 1/255, rxload 1/255
  Encapsulation HDLC, crc 16, loopback not set
  Keepalive set (10 sec)
  Last input 3w6d, output 3w6d, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 6221
  Queueing strategy: Class-based queueing
  Output queue: 0/1000/0 (size/max total/drops)
  30 second input rate 0 bits/sec, 0 packets/sec
  30 second output rate 0 bits/sec, 0 packets/sec
     34290781 packets input, 3755121313 bytes, 0 no buffer
     Received 482586 broadcasts (894326 IP multicasts)
     8493 runts, 7 giants, 0 throttles
     10416 input errors, 10409 CRC, 0 frame, 0 overrun, 0 ignored, 620 abort
     32395697 packets output, 218182603 bytes, 0 underruns
     0 output errors, 0 collisions, 9 interface resets
     0 unknown protocol drops
     0 output buffer failures, 0 output buffers swapped out
     42 carrier transitions

Output of the Show Version command to provide information about the router:

-------------------------------------------------
Device#   PID                   SN
-------------------------------------------------
*0        CISCO2911/K9          FTX1632AKS6    
         

Technology Package License Information for Module:'c2900'

-----------------------------------------------------------------
Technology    Technology-package           Technology-package
              Current       Type           Next reboot 
------------------------------------------------------------------
ipbase        ipbasek9      Permanent      ipbasek9
security      None          None           None
uc            uck9          Permanent      uck9
data          None          None           None

Configuration register is 0x2102

If you need any more information please let me know. Any help is appreciated I have looked over this configuration repeatedly, but I have yet to figure out the issue.

[John Blakley]

Have you contacted the provider? I see a lot of CRCs on both interfaces. Can you clear counters to see if you're still getting errors? If so, I'd contact the provider and possibly change cables....

HTH,
John

*** Please rate all useful posts ***

[bmrash]

We had the T1 plugged into another device and it worked fine. We put it into this router and it won't work. The cabling is all brand new and we had a couple different people confirm that it's wired correctly. The other T1 (S0/0/1:1) works fine, that's where the confusion is right now.

[graham smart]

Any useful output from a show controllers ?

[bmrash]

Here is the "show controllers" output for the interfaces:

T1 0/0/0 is down.

  Applique type is Channelized T1

  Cablelength is long 0db

  Transmitter is sending remote alarm.

  Receiver is getting AIS.

  alarm-trigger is not set

  Soaking time: 3, Clearance time: 10

  AIS State:Failure LOS State:Clear  LOF State:Failure

  Version info FPGA Rev: 08121917, FPGA Type: PRK4

  Framing is ESF, Line Code is B8ZS, Clock Source is Line.

  CRC Threshold is 320. Reported from firmware  is 320.

  Data in current interval (385 seconds elapsed):

     0 Line Code Violations, 0 Path Code Violations

     0 Slip Secs, 385 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 385 Unavail Secs

  Total Data (last 24 hours)

     0 Line Code Violations, 0 Path Code Violations,

     0 Slip Secs, 86400 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,

     0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 86400 Unavail Secs

T1 0/0/1 is up.

  Applique type is Channelized T1

  Cablelength is long 0db

  No alarms detected.

  alarm-trigger is not set

  Soaking time: 3, Clearance time: 10

  AIS State:Clear  LOS State:Clear  LOF State:Clear

  Version info FPGA Rev: 08121917, FPGA Type: PRK4

  Framing is ESF, Line Code is B8ZS, Clock Source is Line.

  CRC Threshold is 320. Reported from firmware  is 320.

  Data in current interval (385 seconds elapsed):

     0 Line Code Violations, 0 Path Code Violations

     296 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

     296 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,

     66403 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,

     66403 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

[Leo Laohoo]

Serial0/0/0:1 is down, line protocol is down 
 Hardware is DSX1
 Internet address is [omitted]
 MTU 1500 bytes, BW 1536 Kbit/sec, DLY 20000 usec, 
 reliability 240/255, txload 1/255, rxload 1/255

It's a Layer 1 issue.  Contact your provider and tell them to run a 4-hour Bit Error Rate test (BER test).

In an ideal condition, "reliability" should be 255/255 (both values) and nothing less.

  AIS State:Failure LOS State:Clear  LOF State:Failure

RED alarm.

[graham smart]

As pointed out ( Red alarm )

This may help:

http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00801069ff.shtml

Transmit Sending Remote Alarm (Red)

A Red alarm is declared when the channel service unit (CSU) cannot       synchronize with the framing pattern on the T1 line.

To correct the transmitter from sending remote alarms, complete the       following steps:

1. Ensure the framing format configured on the port matches the             framing format of the line. If not, change the framing format on the controller             to match the format of the line.

2. Check the settings at the remote end and ensure that they match             your port settings.

3. Contact your Service Provider.

You could possibly try just for the hell of it....

To correct Rx AIS errors, complete the following steps:

1. Check the show controller t1             [slot/port] output to see if the framing             format configured on the port matches the framing format of the line. If not,             change the framing format on the controller to match the line.

   To change the framing format, use the framing {SF |             ESF} command in controller configuration mode. For example:

   maui-nas-03#configure terminalEnter configuration commands, one per line. End with CNTL/Z. 
   maui-nas-03(config)#controller t1 0maui-nas-03(config-controlle)#framing esf 

[Durga Prasad M.S]

Try swapping you transmit and receive pairs.
Ask your provider if they are doing framing or the link is unframed.

Rgds/dp


Sent from Cisco Technical Support Android App

[Milan Rai]

Brett is that working fine now?????

Some times a simple solution is being neglated.......Have you tried....shutting down the interface and No shut ......command????

Just go for that once..........I have faced port being hang sometimes..........So....one restart....can be the best.....solution for this problem.........Plz let me know if that works.......

[Leo Laohoo]

Some times a simple solution is being neglated.......Have you tried....shutting down the interface and No shut ......command????
Just go for that once..........I have faced port being hang sometimes..........So....one restart....can be the best.....solution for this problem.........Plz let me know if that works.......

As far as I know, when you have a RED Alarm on your Frame Relay connection, a shut/no shut isn't a solution.

[Milan Rai]

you never know leolaohoo....once i faced problem with my bgp peer.....everything was ok......Port was Up and Protocol was also UP.........but still there was problem on the peer..........after lots of troubleshooting........what i though of doing was to shut the interface and un shut it again.......after that it worked fine..............

You never know.......what happens to machines????

[bmrash]

I have tried a shut/no shut already. It is a basic troubleshooting technique and one of the first that I tried. Thanks for the suggestion.

[Leo Laohoo]

Hi Brett,

You're getting a RED alarm.  This is a service provider-issue with their equipment and they need to address this.

[graham smart]

Right..

Well it seems you are now down to two options ( one )

1. Check the settings at the remote end and ensure that they match your port settings.
2. Contact your Service Provider.

Both will need your ISP to actually help you.

-Graham
Please note: My comments are simply suggestions. I cannot be held liable for any loss of data, life or marbles due to following my instructions.

Live chat software for websites. Increase sales.