System Clock in Holdover Mode

[mpaizal]

Hello Expert,
Can someone help me to clear this alarm:-

================================================================================================
Date & Time (Local) S Specific Problem Cause Mo-Reference
================================================================================================
2012-03-09 09:35:52 M System Clock in Holdover Mode replaceable_unit_problem Synchronization=1
2012-03-09 11:57:22 m Remote IP Address Unreachable unavailable Sctp=1
2012-03-09 11:59:45 M NTP Server Reachability Fault unavailable IpAccessHostEt=Slot-2,IpSyncRef=1
2012-03-09 11:59:53 M NTP Server Reachability Fault unavailable IpAccessHostEt=Slot-2,IpSyncRef=2
>>> Total: 4 Alarms (0 Critical, 3 Major)

How to check the IP Tx is running well,

Thanks,

[kaizzer545]

show printout of: st sync

[jamalll2000]

Dear Friend,

Normally the System Holdover Mode is becuase the site after restart but not come back to normal. For this alarm normally need to wait for sometime before the NodeB back to normal but if not back to normal restart again for the second time. If still same must check the transmission. :D

[mpaizal]

show printout of: st sync

Hi KPI, as below:
120310-20:23:57 10.43.100.194 8.0t RBS_NODE_MODEL_M_1_34 stopfile=/tmp/13096
===================================================================================
Proxy Adm State Op. State MO
===================================================================================
107 0 (LOCKED) 0 (DISABLED) Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,TimingUnit=1,TuSyncRef=1
1339 1 (UNLOCKED) 1 (ENABLED) IpSystem=1,IpAccessHostEt=Slot-2,IpSyncRef=2
1340 1 (UNLOCKED) 1 (ENABLED) IpSystem=1,IpAccessHostEt=Slot-2,IpSyncRef=1
===================================================================================
Total: 3 MOs

I did reset the nodeB before, change ETMF-X but no improvement

[texplorer]

hi
this alarm is regarding synchronization
to clear this alarm
Check synchronization definitions
check transmission (TAN or router,cable as well)
chect TU ,ET-MFX, CBU

and also this alarm would be temporarily,if not cease try to reset nodeb.
Regards

[spiderman]

maybe it was about syncronization problem bro.
1. try to check transmission cable from Node to Transmission equipment.
2. Unplug and plug again RJ Connector
3. Test the cable pin connection with LAN Tester.
4. Maybe problem on transmission equipment problem need restart.
5. Restart again the node after finishing step 1-4

It was help?

[mpaizal]

maybe it was about syncronization problem bro.
1. try to check transmission cable from Node to Transmission equipment.
2. Unplug and plug again RJ Connector
3. Test the cable pin connection with LAN Tester.
4. Maybe problem on transmission equipment problem need restart.
5. Restart again the node after finishing step 1-4

It was help?

Now the only alarm appear is "Remote IP Address Unreachable unavailable Sctp=1", but sync now become locked mode,.

[bouciakt]

Now the only alarm appear is "Remote IP Address Unreachable unavailable Sctp=1", but sync now become locked mode,.

Try to ping Ip route traffic and OAM. make sure it's alive
command : lacc ipac ping

[mpaizal]

All alarm clear after reconfigure MXU Tx node, means that this alarm is due to Tx issue instead of NodeB itself,

[outcry007]

This is %99 percent transmission issue. Command : get 10

[conall]

1.nodeb software; 2.transmisson error; 3.cbu