Chapter2Alarm
PossibleCauses
1.TheIPaddressoftheSNTPserverissetincorrectly.
2.TheSNTPserverfails.
3.Thenetworkisfaulty.
4.TheRCUboardisfaulty.
HandlingProcedure
IntheLMTsystem:
1.EnsurethattheSNTPServerIPAddressontheSNTPmanagementpageisset
correctly.(Path:Setup>System>Time).
2.SetSNTPModeandSNTPClockSynchronizationService,andthenclickApply.Ifa
dialogboxappearstoindicatethattheoperationfails,ensurethattheSNTPserveris
operatingproperly.
3.CheckthecommunicationqualitybetweenNEandSNTPservertoensurethattheNE
canbeaccessedthroughtheSNTPserver.
4.Ifthealarmpersistsaftertheprecedingsteps,replacethefaultyRCUboard.
2.1.6134217730RTCclockalarm
AlarmProperty
lAlarmCode:134217730
lAlarmInformation:ThealarmisreportedifthemasterRTCclocktimingfails.
lAlarmLevel:Minor
lAlarmType:EquipmentAlarm
Sub-codeDescription
lSub-code1:RTCclockfailure;
lSub-code2:RTCclocknotset.
EffectontheSystem
Thesystemtimeisnotaccurate.Whenthisalarmisreported,thesystementersthesoft
timingstatusandthesystemtimescaleprecisiondecreases.
PossibleCauses
1.RTCclockchipfailure;
2.TheRTCclockchipisnotinitialized.
HandlingProcedure
1.Settheclockparameters.
2.CheckiftherequiredbatteryisavailableontheRCUboard.
2-5
SJ-20111008094748-008|2012–05–30(R1.1)ZTEProprietaryandCondential
To Next Page
Loading...
Need help?
General
