Eagle :: SHS Clock Failed Alarm

Asset ID:	1-72-2037176.1
Update Date:	2017-02-15
Keywords:

Solution Type Problem Resolution Sure

Solution 2037176.1 : Eagle :: SHS Clock Failed Alarm

Applies to:

Oracle Communications EAGLE (Hardware) - Version EAGLE 43.x and later
Tekelec

Symptoms

Eagle STP has the following alarm:

0187 1114-SHS, 1116-SHS clocks failed

This has no impact as the alarm is for secondary clock source.

Cause

Cause of issue is one of following:

Cause 1. No secondary clock source connected

Cause 2. Secondary clock source not working

Cause 3. Clock cable for secondary clock source is faulty

The following command outputs prove the cause:

EAGLECLLI 15-04-03 15:45:59 EEST EAGLE5 43.0.2-63.65.1
  4559.1185 CARD 1113 INFO GTI input clock anomalies detected
  Reporting TDM Location : 1114
  GTI Clock Status Register : H'0041
  Primary LIU Violation Count : 255
  Secondary LIU Violation Count : 0
  GTI Status Register : H'00e9
  Report Date:15-04-03 Time:15:45:59
;

  EAGLECLLI 15-04-03 15:46:01 EEST EAGLE5 43.0.2-63.65.1
  4562.1185 CARD 1115 INFO GTI input clock anomalies detected
  Reporting TDM Location : 1116
  GTI Clock Status Register : H'0041
  Primary LIU Violation Count : 255
  Secondary LIU Violation Count : 0
  GTI Status Register : H'00e9
  Report Date:15-04-03 Time:15:46:00
;

> send-msg:ds=1:oa=h'98:da=h'5d:f=h'61:loc=1113

  EAGLECLLI 15-04-03 15:45:17 EEST EAGLE5 43.0.2-63.65.1
  Measurement Server Connection Successful
;

  EAGLECLLI 15-04-03 15:45:22 EEST EAGLE5 43.0.2-63.65.1
  send-msg:ds=1:oa=h'98:da=h'5d:f=h'61:loc=1113
  Command entered at terminal #17.
;

Command Accepted - Processing

  EAGLECLLI 15-04-03 15:45:22 EEST EAGLE5 43.0.2-63.65.1
  System Buffer sent has following attributes :
  Msg Length = H'001e
  Dest Card = H'00fa
  Orig Subsys = H'0001 Dest Subsys = H'0001
  Orig Appl ID = H'0098 Dest Appl ID = H'005d
  Func ID = H'0061 Bus/Ret/Sut = H'0002
  Violation Ind = H'0000
  User Message sent to location 1113.
;

Command Executed

  EAGLECLLI 15-04-03 15:45:22 EEST EAGLE5 43.0.2-63.65.1
  Please use the rept-stat-clk cmd to retrieve the clock info.

  BITS clock status register H'008b
  HS clock status register H'00ad
  GTI status register H'00e9
  GTI clock status register H'0041
  Primary LIU violation register 255
  Secondary LIU violation register 0
;

> send-msg:ds=1:oa=h'98:da=h'5d:f=h'61:loc=1115

  EAGLECLLI 15-04-03 15:46:42 EEST EAGLE5 43.0.2-63.65.1
  0244.1330 CARD 2114,B3 INFO Mismatched UA Routing Context
  EAGLECLLI 15-04-03 15:46:45 EEST EAGLE5 43.0.2-63.65.1
  send-msg:ds=1:oa=h'98:da=h'5d:f=h'61:loc=1115
  Command entered at terminal #17.
;

Command Accepted - Processing

  EAGLECLLI 15-04-03 15:46:45 EEST EAGLE5 43.0.2-63.65.1
  System Buffer sent has following attributes :
  Msg Length = H'001e
  Dest Card = H'00fb
  Orig Subsys = H'0001 Dest Subsys = H'0001
  Orig Appl ID = H'0098 Dest Appl ID = H'005d
  Func ID = H'0061 Bus/Ret/Sut = H'0002
  Violation Ind = H'0000
  User Message sent to location 1115.
;

Command Executed

  EAGLECLLI 15-04-03 15:46:45 EEST EAGLE5 43.0.2-63.65.1
  Please use the rept-stat-clk cmd to retrieve the clock info.

  BITS clock status register H'008b
  HS clock status register H'00ad
  GTI status register H'00e9
  GTI clock status register H'0041
  Primary LIU violation register 255
  Secondary LIU violation register 0
;

Solution

Solution for Cause 1. No secondary clock source connected:
Check in the STP control shelf backplane if the Secondary Clock is connected.
Position of clock input slot can be seen from following in customer documentation: Hardware - Signalling Products >> Control Shelf Backplanes >> Page 61
If the secondary Clock is not connected
a. Connect a Secondary clock source cable.

Solution for Cause 2. Secondary clock source not working:

If the Secondary Clock is connected
1. Enter command

rept-stat-clk:mode=full

2. Enter command

rtrv-e1

(make sure all have E1TSEL parameter set as LINE. If yes; move to next step)
3. Change the clock cables between primary and secondary.
4. Enter command

rept-stat-clk:mode=full

   (check that the clock alarm has moved from secondary to primary clock)
5a. If clock alarm has moved from Secondary to Primary:
  a The clock source is not correct. Check patching and make sure the ntp source is sending clock signals.
  b Shift the clock cables back and see that clock alarm is again shown for secondary.
5b. If clock alarm has not moved from Secondary clock to Primary clock:
  a Perform MASP Switchover.
  b If alarm still remains; contact Oracle Support with all the activity data.

Solution for Cause 3. Clock cable for secondary clock source is faulty

Arrange a Field Task and replace the faulty cable

Attachments

This solution has no attachment