• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 8319
  • Last Modified:

how to determine clock provided in T1 line ?

Hey all,

I have got  a CISCO router on our end and Adtran router at the remote end. AT&T with the help of LEC  is providing us T1 line. Lately the line has been going up and down and we suspect clock issue being the cause. We ave done some testing on both of our ends and confident that there is no hardware failure and cables are OK.

We have set the clock source as "line" both at CISCO and Adtran . For the past year or so there has been no problems with the line and everything was OK. Now that we have issues , we suspect problems with T1 line.

I understand that if AT&T is not providing clock for the T1 line , we would have to provide that clock on our router end.
So if AT&T is not providing clock, I would set
CISCO router : clock source "Internal"
ADTRAN router : clock source "line".

My question here is , Is there a way that I can determine from my end whether clock is being provided in the T1 line by AT&T.. I am sure asking AT&T over phone would be the easiest but I am curious to know If I can determine and If yes, How ?

If yes , should I being  any device to do that..

Hope I am clear

SR
0
sunray_2003
Asked:
sunray_2003
  • 22
  • 14
  • 3
2 Solutions
 
AutoSpongeCommented:
If it's a point-to-point T1 they aren't providing a clock.  They will only do so if you go into their frame on almost all circumstances.  Check what type of errors your getting from the 'sho serv' and 'sho serv s0 perf' if you ahve a service-module or 'sho controller' if you don't.  Look for slip errors or on the 'sho int s0' command look for output drops.

A good test meter can tell you if you have a clock on the line or how many there are.  A good CSU can provide a stronger clock while most routers are only a stratum 2 and can sometimes tell you if a second clock is detected (telco is best with stratum 4).
0
 
sunray_2003Author Commented:
Couple of Questions

how to determine that we have point to point.. might be the silly Q to ask and I think we have point to point but is there any way to check ?

When i type "show controller", i get many data like for Fastethernet0 , 1 , and for each T1 card.
can you tell me which information , I can provide here ..

our CSU is inbuilt in our T1 card . just for your information.

0
 
sunray_2003Author Commented:
Here is some more info on the 2 T1 lines that are currently down.. I can see output drops in here.. Does it say anything about who is providing clock

*************
Serial1/0:0 is reset, line protocol is down
  Hardware is DSX1
  Internet address is 172.16.90.10/24
  MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec,
     reliability 253/255, txload 1/255, rxload 1/255
  Encapsulation PPP, loopback not set
  Keepalive set (10 sec)
  LCP Closed
  Closed: IPCP, CDPCP
  Last input 01:27:49, output 01:26:31, output hang never
  Last clearing of "show interface" counters 3d18h
  Input queue: 0/75/14398295/0 (size/max/drops/flushes); Total output drops: 77671  <<----------
  Queueing strategy: weighted fair
  Output queue: 0/1000/64/0 (size/max total/threshold/drops)
     Conversations  0/1/256 (active/max active/max total)
     Reserved Conversations 0/0 (allocated/max allocated)
     Available Bandwidth 1152 kilobits/sec
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     305527 packets input, 16022544 bytes, 0 no buffer
     Received 0 broadcasts, 3420308 runts, 0 giants, 0 throttles
     14398359 input errors, 1536252 CRC, 12862239 frame, 0 overrun, 0 ignored, 7363305 abort
     303674 packets output, 12068309 bytes, 0 underruns
     0 output errors, 0 collisions, 19391 interface resets
     0 output buffer failures, 0 output buffers swapped out
     26 carrier transitions
  Timeslot(s) Used:1-24, Transmitter delay is 0 flags

************************************

Serial1/1:1 is up, line protocol is down
  Hardware is DSX1
  Internet address is 172.16.96.10/24
  MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation PPP, loopback not set
  Keepalive set (10 sec)
  LCP ACKsent
  Closed: IPCP, CDPCP
  Last input 00:00:00, output 00:00:00, output hang never
  Last clearing of "show interface" counters 3d18h
  Input queue: 0/75/11230565/0 (size/max/drops/flushes); Total output drops: 60548   <<----------
  Queueing strategy: weighted fair
  Output queue: 0/1000/64/0 (size/max total/threshold/drops)
     Conversations  0/1/256 (active/max active/max total)
     Reserved Conversations 0/0 (allocated/max allocated)
     Available Bandwidth 1152 kilobits/sec
  5 minute input rate 0 bits/sec, 1 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     278981 packets input, 5223344 bytes, 0 no buffer
     Received 0 broadcasts, 2674438 runts, 0 giants, 0 throttles
     11230590 input errors, 1198965 CRC, 10031706 frame, 0 overrun, 0 ignored, 5743511 abort
     281981 packets output, 5256582 bytes, 0 underruns
     0 output errors, 0 collisions, 15116 interface resets
     0 output buffer failures, 0 output buffers swapped out
     21 carrier transitions
  Timeslot(s) Used:1-24, Transmitter delay is 0 flags


*************************
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
lrmooreCommented:
Bottom line - if you are NOT using frame-relay, then chances are you have leased line point-2-point
Also, it never hurts to simply ask your telco provider..
0
 
sunray_2003Author Commented:
OK.. My supervisor had a talk with AT&T and confirmed that they are not providing clock .

So What I did , went to CISCO interface and gave clock source as internal

config t
controller t1 1/1
clock source internal
exit
exit
write memory

Restarted the CISCO router.

Could not reboot the Adtran at the remote end as the line was down.

Is there anything specific I need to do other than just changing the clock source "internal"

SR
0
 
lrmooreCommented:
If you remember in your lab experiments, you had to set the Adtran as the clock source.. something to do with the multi-port module you have in the 3660 I suspect.
0
 
sunray_2003Author Commented:
Now it is time for me to explain some more to help you swallow this hotcake (as usual)

CISCO 3660
interface  1/0, 1/1 and 2/0
All the interfaces have got clock source as "line"

CISCO T1 1/0  <-------Local end T1 line provided by MCI-----> <------ Somewhere in the middle AT&T -------->
<------ Remote end provided by Highland -------> Adtran router 3205 (clock source line)  (Destination 1)  

CISCO T1 1/1  <-------Local end T1 line provided by MCI-----> <------ Somewhere in the middle AT&T -------->
<------ Remote end provided by BellSouth -------> Adtran router 3205 (clock source line) (Destination 2)

CISCO T1 2/0 <-------Local end T1 line provided by BellSouth -----> <------ Somewhere in the middle AT&T -------->
<------ Remote end provided by BellSouth -------> Adtran router 1224 (clock source line) (Destination 3)

The lab experiement that I did was for 2/0. I had changed the clock source as "internal" for 1224 when I did back to back router connection to do the testing. Once the testing was completed , I changed it back to "line".This circuit is working fine and has been stable since I installed the router at the remote end..

Now the T1 lines that are down are 1/0 and 1/1. AT&T has said that they donot provide the clock source for these lines.
So I decided to change the clock source as internal.. I am not sure merely giving the command "clock source internal" would do the job or I have to do something else..

Since T1 line 2/0 has been working fine without me any clock source on either ends, I guess BellSouth is providing clock source on that line ( I am yet to confirm from bellsouth) but as part of this Question , would like to know if I can find that myself.


Hope I am clear

SR
0
 
lrmooreCommented:
Easy question first - there is no way for you to validate the clocking on the T1 link without asking Bell South. Generally speaking, if there are 0 CIR/frame errors on both ends, then the clocks are happy as is and are probably getting timing from the telco.

Because you are using the multi-port DSU T1 module on the 3660, I suggest that you let the Adtran 3205s provide the clocking at each remote site

Setting clock source internal will use the default clockrate of the interface. T1's default to 1540000
You "can" set the clock rate to something else if you so desire, but there is no real reason as long as they are full T1's.
0
 
lrmooreCommented:
sorry - 1540000 above should be 1536000 (64k channels x 24 = 1536)

0
 
sunray_2003Author Commented:
I am planning to get hold of someone at BellSouth tommorrow to know whether they are providing the clock on the T1 line that is used in 2/0 interface of CISCO. I am not touching that clock source as that line has been stable for more than 3 weeks.

I will take your advise for interface 1/0 and 1/1. 2 reasons
a) Those are the two lines that are down
b) AT&T has confirmed that they are not providing clock on those lines.

I guess my next step would be to go to those remote locations and change the clock source on adtran to "internal" and watch..

0
 
lrmooreCommented:
If you want to save yourself some travel time, you can hook up a modem to the console port of the remote routers and use Hyperterm to dial right into the console..

Else, go ahead and make the change from a telnet session. If you lose all connectivity, have someone simply reboot the router to the previous config..
0
 
sunray_2003Author Commented:
Just confirming

For adtran to change clock source:

telnet to router
config t
interface t1 1/1
clock source internal
exit
exit
write mem ( I think i better donot write to memory , If I need to reboot the router to get previous config)
0
 
lrmooreCommented:
Yes, just don't do the write mem - just in case.
If all goes well for a couple of days, then save the config..
0
 
sunray_2003Author Commented:
well, first thing I will tommorrow morning then... Yet another day to fight with clock .. Oh well.. Fun of working with networking..

Being a clock Q , I would like to know this

CISCO T1 1/0  <-------Local end T1 line provided by MCI-----> <------ Somewhere in the middle AT&T -------->
<------ Remote end provided by Highland -------> Adtran router 3205 (clock source line)  (Destination 1)

In the above scenario , AT&T has said they donot provide clock.. So in a typical point - point T1 , if the telco says they dont provide clock , does it mean , no clock for the entire T1 line or only on one of ends. In this case, Should I confirm from Highland (which is the LEC) , that they donot provide clock at the remote end aswell...  
0
 
lrmooreCommented:
Typically, the telco that sends you the bill (AT&T) has responsibility for end-to-end. They wholesale the local loops from the local LEC, and you should never have to deal directly with the LEC.
0
 
sunray_2003Author Commented:
OK. Thanks for making this clock situation clear.. I shall try changing the clock source on Adtran tommorrow and obviously have to wait before knowing whether everything goes well. Hopefully , it does..
0
 
AutoSpongeCommented:
Yeah, the LEC won't provide a clock when they hand off the circuit to someone else.  Then the clock is either on the 'long haul' portion or in 'customer equipment' (the LEC's perspective of customer equipment is that AT&T is the customer or the end-user is the customer).

However, I'm concerned you may have more than a line problem if the adtran doesn't regain line signal after you reset the cisco.  That may be adtran behavior, I'm not sure.

Try the other commands I suggested on the cisco, sho controller, sho service-module, and service-module performance stats.
0
 
sunray_2003Author Commented:
Autosponge,

As it has been confirmed that telco is not providing clock , I am going to go ahead and give clock on Adtran end to see how it goes.

Regarding commands
show controller : gives lots of info. Do you want to post anything specific here ?
show service-module: does not work.. I just gave it from router# and I guess it is not concerned with my CISCO 3660 or may be I am giving it in the wrong place.
0
 
AutoSpongeCommented:
Sho controller output can sometimes give you more error information as well as "clock source detected" indication near the top.  I wouldn't bother trying to decypher the memory hex information.
0
 
sunray_2003Author Commented:
This is what I get for 1/0 and 1/1 which have the line problem

**************************
Controller 0 is type: T1 with CSU interface in slot 1
Serial interface 1/0:0  Munich32 version 3.4
Total chip configuration successes: 10, failures: 0, timeouts: 0
  Interrupt Queue Element(index=1304): interrupt is enabled
  0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
  0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
  0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
  0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
  0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000

  Channel state: UP  Channel IDB: 613EB7B4
  RX ring entries: 9, buffer size 1548
  RX descriptor ring: head = 9781560, tail = 9781540
  RX pak ring: head = 612B1A74, tail = 612B1A54
  00 params=0x460C0000 status=0x0 data ptr=0x9762C44 next ptr=0x9781550
  01 params=0x60C0000 status=0x0 data ptr=0x97632C4 next ptr=0x9781560
  02 params=0x60C0000 status=0x0 data ptr=0x9763FC4 next ptr=0x9781570
  03 params=0x60C0000 status=0x0 data ptr=0x9760544 next ptr=0x9781580
  04 params=0x60C0000 status=0x0 data ptr=0x97625C4 next ptr=0x9781590
  05 params=0x60C0000 status=0x0 data ptr=0x975F1C4 next ptr=0x97815A0
  06 params=0x60C0000 status=0x0 data ptr=0x9763944 next ptr=0x97815B0
  07 params=0x60C0000 status=0x0 data ptr=0x975FEC4 next ptr=0x97815C0
  08 params=0x60C0000 status=0x0 data ptr=0x975F844 next ptr=0x9781540
  TX ring entries: 17, in use: 0, buffer size 1548
  TX descriptor ring: head = 0, tail = 0
  TX pak ring: head = 6148FED0, tail = 6148FED0
  00 params=0x0 data ptr=0x0000000 next ptr=0x4D0043A8
  01 params=0x0 data ptr=0x0000000 next ptr=0x4D0043B4
  02 params=0x0 data ptr=0x0000000 next ptr=0x4D0043C0
  03 params=0x40000000 data ptr=0x0000000 next ptr=0x4D0043CC
  04 params=0x0 data ptr=0x0000000 next ptr=0x4D0043D8
  05 params=0x0 data ptr=0x0000000 next ptr=0x4D0043E4
  06 params=0x0 data ptr=0x0000000 next ptr=0x4D0043F0
  07 params=0x0 data ptr=0x0000000 next ptr=0x4D0043FC
  08 params=0x0 data ptr=0x0000000 next ptr=0x4D004408
  09 params=0x0 data ptr=0x0000000 next ptr=0x4D004414
  10 params=0x0 data ptr=0x0000000 next ptr=0x4D004420
  11 params=0x0 data ptr=0x0000000 next ptr=0x4D00442C
  12 params=0x0 data ptr=0x0000000 next ptr=0x4D004438
  13 params=0x0 data ptr=0x0000000 next ptr=0x4D004444
  14 params=0x0 data ptr=0x0000000 next ptr=0x4D004450
  15 params=0x0 data ptr=0x0000000 next ptr=0x4D00445C
  16 params=0x0 data ptr=0x0000000 next ptr=0x4D00439C
  List of timeslots (sw): 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
                          17 18 19 20 21 22 23
  List of all timeslots (hw):
   00:00FF00FF 01:00FF00FF 02:00FF00FF 03:00FF00FF 04:00FF00FF 05:00FF00FF
   06:00FF00FF 07:00FF00FF 08:00FF00FF 09:00FF00FF 10:00FF00FF 11:00FF00FF
   12:00FF00FF 13:00FF00FF 14:00FF00FF 15:00FF00FF 16:00FF00FF 17:00FF00FF
   18:00FF00FF 19:00FF00FF 20:00FF00FF 21:00FF00FF 22:00FF00FF 23:00FF00FF
   24:20002000 25:20002000 26:20002000 27:20002000 28:20002000 29:20002000
   30:20002000 31:20002000
  Bandwidth: 1536, idle channel: Unassigned, idle ts bitfield: 0x0
  0 missed datagrams, 0 overruns, 0 memory errors
  0 transmitter underruns, 0 throttles, 0 enables, 0 bad interrupt elements
  0 spurious signaling interrupts

****************************

Controller 1 is type: T1 with CSU interface in slot 1
Serial interface 1/1:1  Munich32 version 3.4
Total chip configuration successes: 19538, failures: 0, timeouts: 0
  Interrupt Queue Element(index=2965): interrupt is enabled
  0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
  0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
  0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
  0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
  0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000

  Channel state: UP  Channel IDB: 613F2D08
  RX ring entries: 9, buffer size 1548
  RX descriptor ring: head = 977F810, tail = 977F880
  RX pak ring: head = 613AB404, tail = 613AB474
  00 params=0x60C0000 status=0x0 data ptr=0x97681C4 next ptr=0x977F810
  01 params=0x60C0000 status=0x0 data ptr=0x9767B44 next ptr=0x977F820
  02 params=0x60C0000 status=0x0 data ptr=0x976AF44 next ptr=0x977F830
  03 params=0x60C0000 status=0x0 data ptr=0x9769544 next ptr=0x977F840
  04 params=0x60C0000 status=0x0 data ptr=0x976B5C4 next ptr=0x977F850
  05 params=0x60C0000 status=0x0 data ptr=0x976A244 next ptr=0x977F860
  06 params=0x60C0000 status=0x0 data ptr=0x9768EC4 next ptr=0x977F870
  07 params=0x60C0000 status=0x0 data ptr=0x9769BC4 next ptr=0x977F880
  08 params=0x460C0000 status=0x0 data ptr=0x976A8C4 next ptr=0x977F800
  TX ring entries: 17, in use: 0, buffer size 1548
  TX descriptor ring: head = 0, tail = 0
  TX pak ring: head = 61373968, tail = 61373968
  00 params=0x80000000 data ptr=0x0000000 next ptr=0x4D00EA34
  01 params=0x0 data ptr=0x0000000 next ptr=0x4D00EA40
  02 params=0x0 data ptr=0x0000000 next ptr=0x4D00EA4C
  03 params=0x0 data ptr=0x0000000 next ptr=0x4D00EA58
  04 params=0x0 data ptr=0x0000000 next ptr=0x4D00EA64
  05 params=0x0 data ptr=0x0000000 next ptr=0x4D00EA70
  06 params=0x0 data ptr=0x0000000 next ptr=0x4D00EA7C
  07 params=0x0 data ptr=0x0000000 next ptr=0x4D00EA88
  08 params=0x0 data ptr=0x0000000 next ptr=0x4D00EA94
  09 params=0x40000000 data ptr=0x0000000 next ptr=0x4D00EAA0
  10 params=0x0 data ptr=0x0000000 next ptr=0x4D00EAAC
  11 params=0x0 data ptr=0x0000000 next ptr=0x4D00EAB8
  12 params=0x0 data ptr=0x0000000 next ptr=0x4D00EAC4
  13 params=0x0 data ptr=0x0000000 next ptr=0x4D00EAD0
  14 params=0x0 data ptr=0x0000000 next ptr=0x4D00EADC
  15 params=0x0 data ptr=0x0000000 next ptr=0x4D00EAE8
  16 params=0x0 data ptr=0x0000000 next ptr=0x4D00EA28
  List of timeslots (sw): 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
                          17 18 19 20 21 22 23
  List of all timeslots (hw):
   00:01FF01FF 01:01FF01FF 02:01FF01FF 03:01FF01FF 04:01FF01FF 05:01FF01FF
   06:01FF01FF 07:01FF01FF 08:01FF01FF 09:01FF01FF 10:01FF01FF 11:01FF01FF
   12:01FF01FF 13:01FF01FF 14:01FF01FF 15:01FF01FF 16:01FF01FF 17:01FF01FF
   18:01FF01FF 19:01FF01FF 20:01FF01FF 21:01FF01FF 22:01FF01FF 23:01FF01FF
   24:20002000 25:20002000 26:20002000 27:20002000 28:20002000 29:20002000
   30:20002000 31:20002000
  Bandwidth: 1536, idle channel: Unassigned, idle ts bitfield: 0x0
  0 missed datagrams, 0 overruns, 0 memory errors
  0 transmitter underruns, 0 throttles, 0 enables, 0 bad interrupt elements
  0 spurious signaling interrupts

************************
0
 
sunray_2003Author Commented:
Lrmoore,

Rebooted the remote adtran router.
Line came up.

Following scenarios Tested for CISCO 1/1 :
---------------------------------

a) cisco router clock source line
adtran router clock source line
result : everything was working but since it was the original condition , never know when the line would go down

b) cisco router : clock : internal
adtran router : clock : line
Though i was able to ping the router , polycom unit connected at the remote end, I was not able to connect the polycoms so that one failed

c) latest situation
cisco router : clock : line
adtran router : clock : internal
result : everything is looking OK for the past 10 mins like a) but have to wait for 2 days to see if it would stay up or down
0
 
sunray_2003Author Commented:
This is the latest interface details for 1/0 and 1/1

************
Serial1/0:0 is up, line protocol is up
  Hardware is DSX1
  Internet address is 172.16.90.10/24
  MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation PPP, loopback not set
  Keepalive set (10 sec)
  LCP Open
  Listen: CDPCP
  Open: IPCP
  Last input 00:00:53, output 00:00:08, output hang never
  Last clearing of "show interface" counters 22:03:58
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 8
  Queueing strategy: weighted fair
  Output queue: 0/1000/64/0 (size/max total/threshold/drops)
     Conversations  0/1/256 (active/max active/max total)
     Reserved Conversations 0/0 (allocated/max allocated)
     Available Bandwidth 1152 kilobits/sec
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     63999 packets input, 16912254 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     51630 packets output, 7715876 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 output buffer failures, 0 output buffers swapped out
     1 carrier transitions
  Timeslot(s) Used:1-24, Transmitter delay is 0 flags

Serial1/1:1 is up, line protocol is up
  Hardware is DSX1
  Internet address is 172.16.96.10/24
  MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation PPP, loopback not set
  Keepalive set (10 sec)
  LCP Open
  Listen: CDPCP
  Open: IPCP
  Last input 00:43:28, output 00:00:03, output hang never
  Last clearing of "show interface" counters 22:03:58
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 21644
  Queueing strategy: weighted fair
  Output queue: 0/1000/64/0 (size/max total/threshold/drops)
     Conversations  0/2/256 (active/max active/max total)
     Reserved Conversations 0/0 (allocated/max allocated)
     Available Bandwidth 1152 kilobits/sec
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     78734 packets input, 19496465 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     85909 packets output, 16599231 bytes, 0 underruns
     0 output errors, 0 collisions, 5402 interface resets
     0 output buffer failures, 0 output buffers swapped out
     9 carrier transitions
  Timeslot(s) Used:1-24, Transmitter delay is 0 flags

*************

For 1/0 :
CISCO : clock : line
Adtran : clock :line

****

For 1/1 :
CISCO : clock : line
Adtran : clock : internal

Hopefully waiting to see if they would remain stable and then change 1/0's adtran to internal..

0
 
lrmooreCommented:
Looks like you're off to a good start. 0 CRC errors on both links is a good sign..
0
 
sunray_2003Author Commented:
As long as you feel good , I feel good.

From 11 am till 4 pm , 1/1 interface didnot go down.
From 4 pm yes till 4 pm today , 1/0 interface has not gone down (Netcrunch says so)

But I would like to wait for 48 hrs to see how it all goes. I would really like 1/1 to stay up for 48 hrs as in that case, CISCO is set at line and Adtran on the remote end is set as internal (clock). But for 1/0 , it is line on both ends ..

Unfortunately , i donot have vpn access to my office so cannot check tonite but hopefully tomm morning at 8 , I can know if it went down or not..

0
 
sunray_2003Author Commented:
Lrmoore,

This is the latest. From 4 pm 11/17 till 8 am 11/18 , both the lines have not gone down.

*********
Serial1/0:0 is up, line protocol is up
  Hardware is DSX1
  Internet address is 172.16.90.10/24
  MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation PPP, loopback not set
  Keepalive set (10 sec)
  LCP Open
  Listen: CDPCP
  Open: IPCP
  Last input 00:10:56, output 00:00:03, output hang never
  Last clearing of "show interface" counters 1d16h
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 8
  Queueing strategy: weighted fair
  Output queue: 0/1000/64/0 (size/max total/threshold/drops)
     Conversations  0/1/256 (active/max active/max total)
     Reserved Conversations 0/0 (allocated/max allocated)
     Available Bandwidth 1152 kilobits/sec
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     103616 packets input, 24667264 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     87756 packets output, 14126211 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 output buffer failures, 0 output buffers swapped out
     1 carrier transitions
  Timeslot(s) Used:1-24, Transmitter delay is 0 flags

Serial1/1:1 is up, line protocol is up
  Hardware is DSX1
  Internet address is 172.16.96.10/24
  MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation PPP, loopback not set
  Keepalive set (10 sec)
  LCP Open
  Listen: CDPCP
  Open: IPCP
  Last input 00:28:13, output 00:00:05, output hang never
  Last clearing of "show interface" counters 1d16h
  Input queue: 0/75/1/0 (size/max/drops/flushes); Total output drops: 21644
  Queueing strategy: weighted fair
  Output queue: 0/1000/64/0 (size/max total/threshold/drops)
     Conversations  0/2/256 (active/max active/max total)
     Reserved Conversations 0/0 (allocated/max allocated)
     Available Bandwidth 1152 kilobits/sec
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     94820 packets input, 20161338 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     1 input errors, 0 CRC, 1 frame, 0 overrun, 0 ignored, 1 abort
     102103 packets output, 17452228 bytes, 0 underruns
     0 output errors, 0 collisions, 5402 interface resets
     0 output buffer failures, 0 output buffers swapped out
     9 carrier transitions
  Timeslot(s) Used:1-24, Transmitter delay is 0 flags

***************

Yesterday after rebooting the Adtran router at the remote end pertaining to 1/1, I should have rebooted the CISCO router.
I guess hence both the interface shows carrier transitions as 1 and 9 respectively.

My understanding from that is the serial interface has changed state 1 and 9 times on 1/0 and 1/1 respectively.
That could have happened before yesterday when the lines actually started looking stable..

SR
0
 
lrmooreCommented:
I would be more concerned with the 5402 interface resets:
  >  0 output errors, 0 collisions, 5402 interface resets  <====

Even without the CRC errors, this is not a good sign of a stable circuit.
It appears that 1/0 is still holding good without the clocking on the Adtran side?


0
 
sunray_2003Author Commented:
Yeah makes me wonder too how 1/0 is good with no clock on either end.

For the 5402 resets on 1/1 , do you think , I should reboot the CISCO router and see if the resets would grow ?
I have not restarted the router for the past 2 days..
0
 
lrmooreCommented:
You should not have to reboot the Cisco.
Just keep an eye on the counters. If it keeps increasing on one link and not the other, then we know there is still something screwy with the clocking.
0
 
sunray_2003Author Commented:
I assume when you say counter , you are referring to  " 5402 interface resets"  or
" Last clearing of "show interface" counters 1d16h "

0
 
sunray_2003Author Commented:
Doesnot look like a happy line on the other end for 1/0..


Adtran connected to 1/0 of the CISCO

*************
t1 1/1 is UP
  T1 coding is B8ZS, framing is ESF
  Clock source is line, FDL type is ANSI
  Line build-out is 0dB
  No remote loopbacks, No network loopbacks
  Acceptance of remote loopback requests enabled

  DS0 Status: 123456789012345678901234
              NNNNNNNNNNNNNNNNNNNNNNNN
  Status Legend: '-' = DS0 is unallocated
                 'N' = DS0 is dedicated (nailed)

  Line Status: -- No Alarms --

  Current Performance Statistics:
    0 Errored Seconds, 0 Bursty Errored Seconds
    0 Severely Errored Seconds, 0 Severely Errored Frame Seconds
    0 Unavailable Seconds, 0 Path Code Violations
    0 Line Code Violations, 0 Controlled Slip Seconds
    0 Line Errored Seconds, 0 Degraded Minutes

TDM group 1, line protocol is UP
    Encapsulation PPP (ppp 1)
    180914 packets input, 23265161 bytes, 0 no buffer
    0 runts, 7 giants, 0 throttles
    2667058 input errors, 134742 CRC, 1140860 frame  <<------  May be something to be concerned about ?
    1391456 abort, 0 ignored, 0 overruns
    214528 packets output, 41527820 bytes, 0 underruns
    0 input clock glitches, 0 output clock glitches
    0 carrier lost, 0 cts lost

*****************************

Adtran router connected to 1/1  of CISCO

t1 1/1 is UP
  T1 coding is B8ZS, framing is ESF
  Clock source is internal, FDL type is ANSI
  Line build-out is 0dB
  No remote loopbacks, No network loopbacks
  Acceptance of remote loopback requests enabled

  DS0 Status: 123456789012345678901234
              NNNNNNNNNNNNNNNNNNNNNNNN
  Status Legend: '-' = DS0 is unallocated
                 'N' = DS0 is dedicated (nailed)

  Line Status: -- No Alarms --

  Current Performance Statistics:
    0 Errored Seconds, 0 Bursty Errored Seconds
    0 Severely Errored Seconds, 0 Severely Errored Frame Seconds
    0 Unavailable Seconds, 0 Path Code Violations
    0 Line Code Violations, 0 Controlled Slip Seconds
    0 Line Errored Seconds, 0 Degraded Minutes

  TDM group 1, line protocol is UP
    Encapsulation PPP (ppp 1)
    41398 packets input, 16233605 bytes, 0 no buffer
    0 runts, 0 giants, 0 throttles
    539 input errors, 36 CRC, 73 frame
    430 abort, 0 ignored, 0 overruns
    42408 packets output, 19337962 bytes, 0 underruns
    0 input clock glitches, 0 output clock glitches
    0 carrier lost, 0 cts lost

****************************
0
 
lrmooreCommented:
 2667058 input errors, 134742 CRC, 1140860 frame  <<------  May be something to be concerned about ?
Absolutely something to be concerned about. This is the line without the adtran providing clocking, right?
Don't wait any longer to setup the Adtran to clock..
0
 
sunray_2003Author Commented:
yes that is the line in which adtran doesnot have any clock..

do you think it is better to change the clock to internal on that line and then restart that router or just change the clock , write to memory and then monitor ?

Now i have got VPN access to my office comp so I can do it right away ..If i need to restart , I should be able to telnet to the router and do a restart using one of the commands. i have done that once..
0
 
lrmooreCommented:
I would not hesitate to set the clocking on the Adtran, write mem, then reboot...
0
 
sunray_2003Author Commented:
OK. I checked that interface again and now it shows

2667109 input errors, 134742 CRC, 1140911 frame

Slight increase in the errors in the past 12 hrs . I guess I will do the clocking and see what happens..
0
 
lrmooreCommented:
Quit thinking about it and be like Nike - JUST DO IT!
0
 
sunray_2003Author Commented:
Lrmoore,

I think it is time to close this Question . Here is the interface log for 1/0 that I have monitored after changing its clock to internal.. I am also posting the "error part" for the same on the CISCO end ..  
Line NEVER went down for more than 6 days.

Final question here, should there be 0 errors all the time or is it OK if the errors donot increase rapidly.

*********************************
Clock source = Internal   Adtran router 1/0 .

Router interface log taken at 2.45 pm Nov 19

TDM group 1, line protocol is UP
  Encapsulation PPP (ppp 1)
  48 packets input, 2061 bytes, 0 no buffer
  0 runts, 1 giants, 0 throttles
  60 input errors, 54 CRC, 2 frame
  4 abort, 0 ignored, 0 overruns
  58 packets output, 3069 bytes, 0 underruns
  0 input clock glitches, 0 output clock glitches
  0 carrier lost, 0 cts lost

*************************************
Router interface log taken at 5.45 pm Nov 19

 TDM group 1, line protocol is UP
   Encapsulation PPP (ppp 1)
   50298 packets input, 13680181 bytes, 0 no buffer
   0 runts, 1 giants, 0 throttles
   67 input errors, 55 CRC, 2 frame
   10 abort, 0 ignored, 0 overruns
   51657 packets output, 16485248 bytes, 0 underruns
   0 input clock glitches, 0 output clock glitches

**************************************
Router interface log taken at 11.15 am Nov 20

 TDM group 1, line protocol is UP
   Encapsulation PPP (ppp 1)
   93307 packets input, 22264682 bytes, 0 no buffer
   0 runts, 1 giants, 0 throttles
   73 input errors, 56 CRC, 4 frame
   13 abort, 0 ignored, 0 overruns
   100514 packets output, 29676152 bytes, 0 underruns
   0 input clock glitches, 0 output clock glitches
   0 carrier lost, 0 cts lost

***************************************
Router interface log taken at 4.30 pm Nov 20

 TDM group 1, line protocol is UP
   Encapsulation PPP (ppp 1)
   101721 packets input, 22835070 bytes, 0 no buffer
   0 runts, 1 giants, 0 throttles
   73 input errors, 56 CRC, 4 frame
   13 abort, 0 ignored, 0 overruns
   109185 packets output, 30432196 bytes, 0 underruns
   0 input clock glitches, 0 output clock glitches
   0 carrier lost, 0 cts lost

***************************************
Router interface log taken at 3.00 pm Nov 21

TDM group 1, line protocol is UP
  Encapsulation PPP (ppp 1)
  136747 packets input, 25248586 bytes, 0 no buffer
  0 runts, 1 giants, 0 throttles
  74 input errors, 56 CRC, 4 frame
  14 abort, 0 ignored, 0 overruns
  145582 packets output, 33650229 bytes, 0 underruns
  0 input clock glitches, 0 output clock glitches
  0 carrier lost, 0 cts lost

*****************************************
Router  interface log taken at 8.30 am Nov 22

 TDM group 1, line protocol is UP
   Encapsulation PPP (ppp 1)
   163990 packets input, 27144261 bytes, 0 no buffer
   0 runts, 1 giants, 0 throttles
   89 input errors, 58 CRC, 7 frame
   24 abort, 0 ignored, 0 overruns
   173993 packets output, 36180448 bytes, 0 underruns
   0 input clock glitches, 0 output clock glitches
   0 carrier lost, 0 cts lost

*****************************************
CISCO Log 1/0  

5.45 pm Nov 19  

     442597 packets input, 185243157 bytes, 0 no buffer
     Received 0 broadcasts, 4 runts, 0 giants, 0 throttles
     226 input errors, 21 CRC, 204 frame, 0 overrun, 0 ignored, 220 abort
     330908 packets output, 101636904 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 output buffer failures, 0 output buffers swapped out
     3 carrier transitions

*****************************
11.15 am Nov 20

     491133 packets input, 198327902 bytes, 0 no buffer
     Received 0 broadcasts, 4 runts, 0 giants, 0 throttles
     226 input errors, 21 CRC, 204 frame, 0 overrun, 0 ignored, 220 abort
     373615 packets output, 110198807 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 output buffer failures, 0 output buffers swapped out
     3 carrier transitions

*****************************
 4.30 pm Nov 20

     499782 packets input, 199059035 bytes, 0 no buffer
     Received 0 broadcasts, 4 runts, 0 giants, 0 throttles
     226 input errors, 21 CRC, 204 frame, 0 overrun, 0 ignored, 220 abort
     382007 packets output, 110767196 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 output buffer failures, 0 output buffers swapped out
     3 carrier transitions

*******************************
3.00 pm Nov 21

     536175 packets input, 202183468 bytes, 0 no buffer
     Received 0 broadcasts, 4 runts, 0 giants, 0 throttles
     226 input errors, 21 CRC, 204 frame, 0 overrun, 0 ignored, 220 abort
     417041 packets output, 113181469 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 output buffer failures, 0 output buffers swapped out
     3 carrier transitions

*******************************
8.30 am Nov 22

     564564 packets input, 204641809 bytes, 0 no buffer
     Received 0 broadcasts, 4 runts, 0 giants, 0 throttles
     226 input errors, 21 CRC, 204 frame, 0 overrun, 0 ignored, 220 abort
     444315 packets output, 115082041 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 output buffer failures, 0 output buffers swapped out
     3 carrier transitions

*******************************
0
 
lrmooreCommented:
The Cisco side looks good with zero increase in error counters, but the Adtran side still looks a little off with the increase in counts, but it's not enough to be too concerned about. My goal would be zero errors over an extended period of time, but an increase from 48 to 89 CRC errors over  days is not too bad.. If it starts jumping significantly, then it may be time to ask the telco if they can/will provide the clocking for you.
0
 
sunray_2003Author Commented:
OK .. Thanks a lot for your help..

SR
0
 
sunray_2003Author Commented:
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 22
  • 14
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now