Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Clocking question 1

Status
Not open for further replies.

SherWat

Technical User
Feb 12, 2016
216
CA
CS1000 7.6
In LD 73 I printed DDB which shows my clocking from TN 0-0-2 and also 16-0-7. The secondary PRI at 16-0-7 is no longer active. Could that cause issue on our primary PRI as far as static calls?
1725460513634.png
 
Go to ld 60 and type ssck 0. Then show your results. Also in ld 60 type in lcnt 2 for loop 2 show results.
 
Last edited:
All clocking tends to be done in LD 60 as loopback55 has suggested,

LD 60

SSCK 0 - Status of the System Clock Number 0.(Option 11 & 51 only)

SSCK 1 - Status of the System Clock Number 1. (Option 61/71/81)

Go to page 360 in the attached file.
 

Attachments

  • LD_MTC.pdf
    1.8 MB · Views: 9
All clocking tends to be done in LD 60 as loopback55 has suggested,

LD 60

SSCK 0 - Status of the System Clock Number 0.(Option 11 & 51 only)

SSCK 1 - Status of the System Clock Number 1. (Option 61/71/81)

Go to page 360 in the attached file.
Sure spent many hours in that load and also ld 96.
 
Thanks everyone. No longer getting static calls - had nothing to do with the clocking as it was a carrier issue.
 
If you no longer have PRI in 16-0 you could just remove it
LD 96 dis the msdl/tmdi depending on what it is
LD 60 dis the loop associated with 16-0-7 if its not already (if you don't know the loop number LD 22 and prt the cequ)
LD 60 dis cc 16 0
Ld 73
REQ chg
TYPE ddb
MGCLK x16 0
LD 14 out the channels
LD 17 out the DCH
LD 17 cha cequ and remove the loop
 
CS1000 7.6
In LD 73 I printed DDB which shows my clocking from TN 0-0-2 and also 16-0-7. The secondary PRI at 16-0-7 is no longer active. Could that cause issue on our primary PRI as far as static calls?

If your system tries to track on the non-existent clock, it will fail and may go in to "Free-run" mode, (clocking on it's own processor). This can sometimes cause static if the clock signal between the CPU and the DTI/T1 are off.

But, as you found, in most cases, this is carrier issue.
 
So only remove the secondary clock, guessing you are on a multi group system I am mostly used to 1000E where it would be separate clock controllers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top