HOME HO ME SEAR SEARCH CH ACTI ACTIVE VE SEAR SEARCH CH LO LOG G
Search » Search Log » View Experience Recording
Experience Recording:
PREF PREFER EREN ENCE CES S
Active Knowledge Group : Select..
ER730431
Title Clock synchronisation problem Products RBS 6601 WCDMA
Enterprise Keywords
Context Fault finding (CS)
Issue category Alarms & Logs
Statements Sync Reference PDV Problem Synchronization=1 (clock_synchronisation_problem) Loss of Synch Reference Redundancy Synchronization=1 (replaceable_unit_problem)
Background Sync alarms were reported to show clock synchronisation problem. 1.Clock synchronisation problem 2.DUW&ELC Aleady Swap 7210 to 7705 Alarms: 2015-01-19 00:13:00 AL M Sync Reference PDV Problem Synchronization=1 (clock_synchronisation_problem) 2015-01-19 00:14:00 AL m Loss of Synch Reference Redundancy Synchronization=1 (replaceable_unit_problem) 2015-01-19 01:03:00 AL * Sync Reference PDV Problem Synchronization=1 (clock_synchronisation_problem) 2015-01-19 01:03:00 AL * Loss of Synch Reference Redundancy Synchronization=1 (replaceable_unit_problem) Custodian: RNEA-CSR-TW-RAN
one synchronization reference has high or time-variant PDV. As the consequence of the fault, the synchronization reference is unavailable for the node. If no other synchronization references are available, the clock fulfills the accuracy requirements for normal operation, both for transport and radio interfaces, for a limited period of time. Below are the Alarm Causes: Alarm Cause Description Fault Reason Fault Impact Location Transport Synchronization Transport network Transport If no standby synchronization network references have high or incorrectly network reference is available, the fault problem time-variant PDV dimensioned can stop or disturb the traffic or the network synchronization Transport Synchronization Configuration fault Transport network references have in the Transport network problem complicated PDV network Unsupported The time server is not Configuration or Time server time server verified as a suitable characteristics of product, together with the the time server client
PROCEDURE: Ericsson has a procedure to solve this issue. Before starting this procedure, ensure that the following conditions are met: The Network Synchronization Plan is available. The Transmission Plan is available. This alarm is issued by MO Synchronization, please perform the following steps at the maintenance center: 1. Examine the value of the attribute syncRefStatus in the MO Synchronization. For all defined references with the value PDV_PROBLEM, continue with the next step. 2. Ensure that the MO IpSyncRef is correctly configured in accordance with the Network Synchronization Plan. If the alarm is issued again, continue with the next step. If the alarm is not issued again, exit this procedure. 3. Ensure that the MO IpAccessHostEt is configured in accordance with the Transmission Plan. In particular, pay attention to the configuration of the attribute ntpDscp (priority of IP packets). If the alarm is issued again, continue with the next step. If the alarm is not issued again, exit this procedure. 4. Verify that the time server is supported by Ericsson for the purpose of network synchronization. If the time server is supported, go to the next step. If the time server is not supported, consult the next level of maintenance support. 5. Examine the NTP time server configuration. If an NTP time server integrated in an Ericsson RNC is used, ensure that the MO IpAccessHostEt is configured according to the Network Synchronization Plan. If a stand-alone time server is used, verify its configuration with the network synchronization plan. If the alarm is issued again, continue with the next step. If the alarm is not issued again, exit this
7. Consult the next level of maintenance support. Further actions are outside the scope of this instruction. ----------------------------------------------------------------------------------------------------------------Recommended logs and traces: Please collect below logs and traces on faulty RBS, in case these alarms are reported again. Print logs: nsssysclkinfo nssrefchangeinfo nssmpinfo all nssinfo all Trace: te e trace4 trace5 trace6 trace7 trace9 state_change NSS_CBM_TUM2_TUREG -----------------------------------------------------------------------------------------------------------------
