Composite clock error? 1

[Opie the Phoneman]

I have a:

VERSION 3621

System type is - Communication Server 1000M MG/CP PIV
CP PIV - Pentium M 1.1 GHz

RELEASE 7
ISSUE 50 Q +
IDLE_SET_DISPLAY NORTE


I am seeing some, CC STATUS, RESTART ACK, 2ND T303 TIMEOUT messages on my DCH XX MSG log.

When I monitor my DCH in LD 96 I see several of these messages repeated on DCH XX


DCH XX UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 11:00:00 CK EB026357
STATUS: OUT OF SERVICE

DCH XX UIPE_OMSG CC_STATUS_REQ REF 00000000 CH 0 TOD 11:00:01 CK EB026357
CAUSE: #34 - NO CHANNEL/CIRC AVAIL
STATE:NULL

Could this indicate a Composite clock ( CC ) error? Could I have my CC intermittently out of service?

Thanks in advance,

Opie

 

[KCFLHRC]

Did you look at the CC in LD 60 to see if they are tracking ?

 

[Opie the Phoneman]

Here is what I see in LD 60:

.ssck 0
ENBL
CLOCK ACTIVE
GROUP 2
SIDE 0
CLOCK CONTROLLER - LOCKED TO LOOP 2
PREF - 5
SREF - 2
AUTO SWREF CLK - ENBL
NO ERROR
.ssck 1
ENBL
STANDBY
GROUP 1
SIDE 1
CLOCK CONTROLLER - LOCKED TO LOOP 2
PREF - 5
SREF - 2
AUTO SWREF CLK - ENBL
NO ERROR
.****

 

[KCFLHRC]

That looks OK except for the fact that you are tracking on your secondary reference instead of the primary reference.

Try this

LD 60
TRCK PCK

and see if it locks to loop 5

Hopefully Loop 5 is still configured in the DLOP and a functioning T-1/PRI

 

[Opie the Phoneman]

I did and it did lock to loop 5. both loop 2 and loop 5 are valid PRI circuits.

 

[KCFLHRC]

I don't think anything is wrong. Not sure what those D-Channel messages mean. Look at your Trash Counters in LD 60 snd see if anything is taking error's.

LD 60
LCNT

 

[Opie the Phoneman]

KCFLHRC, My LCNT's have been clean for 7 days. I pull my AHST in LD 22 each day!! During daily routines I have no errors on my LCNT's.

 

[KCFLHRC]

I think it's just a Bogus Error, there could be a patch out there that takes care of it

 

[Opie the Phoneman]

This D-channel was printing out a lot of MSG logs. With a lot of CC Status, restart ACK and 2ND T303 TIMEOUT. I was worried about these restart and timeout occrances.

% DCH: XX MSG LOG INDICATION TIME: 5:00:00
% CC ALERTING : 423
% CC DISCONNECT : 130
% CC CALL PROCEEDING : 520
% CC PROGRESS : 27
% CC REJECT : 2160
% CC RELEASE : 439
% CC SETUP : 49
% CC SETUP ACK : 285
% CC STATUS : 65150
% CC RESTART ACK : 1
% CC SERVICE : 1
% CC SERVICE ACK : 382
% H.1A : 128
% H.1B : 47
% ALERTING : 107
% CALL PROCEEDING : 20
% CONNECT : 285
% CONNECT ACK : 441
% NOTIFY : 43
% PROGRESS : 132
% RELEASE : 439
% RELEASE COMPLETE : 1
% RESTART ACK : 65535
% SERVICE : 108
% SERVICE ACK : 2684
% SETUP ACK : 1
% 2ND T303 TIMEOUT : 65136
% T304 TIMEOUT : 5

When I monitored the D-channel I would notice 23 out of service and No channel cause #34 messages.

DCH XX UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 11:00:00 CK EB026357
STATUS: OUT OF SERVICE

DCH XX UIPE_OMSG CC_STATUS_REQ REF 00000000 CH 0 TOD 11:00:01 CK EB026357
CAUSE: #34 - NO CHANNEL/CIRC AVAIL
STATE:NULL

I checked my route that used this PRI:

>ld 21

REQ: ltm
CUST 0
ROUT x

TYPE TLST
TKTP DID
ROUT x
DES TW_LOCAL
TN xxx 01 MBER 1 TW_LOCAL
TN xxx 02 MBER 2 TW_LOCAL
I went to ld 60 and checked all of the PRI's associated with this route. I found the last PRI (there are 382 members in this route) uneq. I restored that PRI and the messages have stopped. I will see if this reduces the timeout and reset ACK messages as well.