北电故障信息映射说明 v10.docx
《北电故障信息映射说明 v10.docx》由会员分享，可在线阅读，更多相关《北电故障信息映射说明 v10.docx（37页珍藏版）》请在冰豆网上搜索。
北电故障信息映射说明v10
北电故障信息映射说明
v1.0
NortelMTXFMLogMapping
DraftV1.0
April7th,2004
Thealarmclearingloganditsassociatedalarmlogs
CARRlog
AlarmclearinglogCARR300alarmCARR310;
AlarmclearinglogCARR800alarmCARR810;
AlarmclearinglogCARR500alarmCARR501,CARR510,CARR511,orCARR512;
CCSlog
AlarmclearinglogCCS105CCS104;
AlarmclearinglogCCS109CCS110;
AlarmclearinglogCCS155CCS151,CCS152,CCS153,CCS154,CCS175;
AlarmclearinglogCCS163CCS156,CCS157,CCS158,CCS164;
AlarmclearinglogCCS161CCS159;
AlarmclearinglogCCS162CCS160;
AlarmclearinglogCCS166CCS167,CCS168;
AlarmclearinglogCCS172CCS172;
AlarmclearinglogCCS173CCS173;
AlarmclearinglogCCS186CCS186;
AlarmclearinglogCCS208CCS209;
AlarmclearinglogCCS211CCS210,CCS209,CCS208;#ignoreCCS229
AlarmclearinglogCCS216CCS212,CCS213,CCS214,CCS215;
AlarmclearinglogCCS220CCS217,CCS218,CCS219,CCS231;
AlarmclearinglogCCS235CCS232,CCS233,CCS234,CCS236;
AlarmclearinglogCCS892CCS891,CCS895,CCS896,CCS897;
CCSlogsamples
###以下为一条C7LINK中断及恢复时的报告:
HKCDMASNSECM*CCS164FEB0702:
39:
458200FLTLinkUnavailable
Link=CDMAHLR_LS10
Resource=LIU70
##CCS164报告说明LINK中断的时间---FEB0702：
39：
45,LINK所属LINKSET的名字---CDMAHLR_LS1及故障LINK在LINKSET中的编号---0。
还说明了相关LINK所使用的硬件---LIU70。
HKCDMASNSECMCCS163FEB0702:
43:
469100INFOLinkAvailable
Link=CDMAHLR_LS10
Resource=LIU70
##CCS163报告说明C7LINK已恢复，格式同CCS164报告。
###以下为一组LINKSET全部中断及恢复时的报告：
HKCDMASNSECM**CCS110FEB0702:
39:
458400FLTLINKSETUNAVAILABLE
LINKSET=CDMAHLR_LS1
##CCS110报告说明一组LINKSET不可用故障出现的时间---FEB0702：
39：
45，故障LINKSET的名称---CDMAHLR_LS1。
HKCDMASNSECMCCS109FEB0702:
43:
469300INFOLINKSETAVAILABLE
LINKSET=CDMAHLR_LS1
##CCS109报告说明故障的LINKSET已恢复，格式同CCS110报告。
###以下为远端CCSPOINTCODE不可用故障出现及恢复时的报告：
HKCDMASNSECM***CCS210FEB0702:
39:
458500SYSBPointCode（s）SBSY
RPC:
CDMAHLRRTE1RSS:
4
##CCS210报告说明一远端CCSPOINTCODE不可用故障发生的时间---FEB0702：
39：
45，故障的RTESET名及受影响的远端子系统数量---4。
HKCDMASNSECMCCS211FEB0702:
43:
479400INFOPointCode（s）INSV
RPC:
CDMAHLRRTE1RSS:
4
##CCS211报告说明一远端CCSPOINTCODE不可用故障恢复的时间，格式同CCS210报告。
CMLog
AlarmclearinglogCM108CM104,CM105,CM106,CM107,CM109,CM110;
AlarmclearinglogCM114CM112,CM113;
AlarmclearinglogCM117CM116;
AlarmclearinglogCM121CM122;
AlarmclearinglogCM124CM125;
AlarmclearinglogCM150CM127,MM111;
AlarmclearinglogCM135CM132,CM133,CM134;
AlarmclearinglogCM138CM136,CM137;
DDULog
AlarmclearinglogDDU205DDU204,DDU203,DDU205,DDU202;
AlarmclearinglogDDU213DDU210,DDU211;
AlarmclearinglogDDU214DDU210,DDU211;
ENETLog
AlarmclearinglogENET100ENET101,ENET102,ENET103,ENET104,ENET105,ENET106,ENET107,ENET108;
AlarmclearinglogENET200ENET201,ENET202,ENET203,ENET204,ENET205,ENET206,ENET207,ENET208;
AlarmclearinglogENET300ENET301,ENET302,ENET303,ENET304,ENET305,ENET306,ENET308,ENET309;
EXTLog
AlarmclearinglogEXT101<=>EXT101;
AlarmclearinglogEXT102EXT102;
AlarmclearinglogEXT103EXT103;
AlarmclearinglogEXT107EXT107;
AlarmclearinglogEXT108EXT108;
AlarmclearinglogEXT109EXT109;
EXTLogsamples:
###Thefollowingareexamplelogsgeneratedforalarmscanpoint（scannm）statechanges:
###EXT101logshowsaminoralarmscanpointindicatedintableALMSCchangesstate.A“*“infrontoflognameindicatesthisisaMinoralarm:
JXZHCIAJCM0*EXT101APR0112:
00:
002112INFOMNSUCFLRON
##MNSUCFLRminoralarmscanpoint告警激活.相应告警清除日志为：
JXZHCIAJCM0*EXT101APR0112:
00:
002112INFOMNSUCFLROFF
###EXT102logshowsamajoralarmscanpointindicatedintableALMSCchangesstate.A“**“infrontoflognameindicatesthisisaMajoralarm:
JXZHCIAJCM0**EXT102APR0112:
00:
002112INFOABMTMFLON
##ABMTMFLmajoralarmscanpoint告警激活.相应告警清除日志为：
JXZHCIAJCM0**EXT102APR0112:
00:
002112INFOABMTMFLOFF
###EXT103logshowsacriticalalarmscanpointindicatedintableALMSCchangesstate.A“***“infrontoflognameindicatesthisisaCriticalalarm:
JXZHCIAJCM0***EXT103APR0112:
00:
002112INFODEADSYSMON
##DEADSYSMcriticalalarmscanpoint告警激活.相应告警清除日志为：
JXZHCIAJCM0***EXT103APR0112:
00:
002112INFODEADSYSMOFF
###EXT104logshowsanexpectedchangeofstateonascanpointindicatedintableALMSCdoesnotoccur.A“*“infrontoflognameindicatesthisisaMinoralarm:
JXZHCIAJCM0*EXT104APR0112:
00:
002112INFOREMOTEARFAIL
##REMOTEARscanpointstatechangesfailstooccur.
##EXT104告警没有相应的告警清除日志，只能通过观察MAP告警消除得知。
###EXT106日志显示DMS收到来自DVS或VSN的告警，或tableSFWALARM定义的软件告警被激活。
A“*“infrontoflognameindicatesthisisaMinoralarm:
SXMSC1**EXT106OCT2915:
47:
062200INFOCMDUSEMAON
##CMDUSEMAminoralarm告警激活.相应告警清除日志为：
SXMSC1**EXT106OCT2915:
47:
215600INFOCMDUSEMAOFF
###EXT107日志显示DMS收到来自DVS，DNC100，VSN或SCPOAM的告警，或tableSFWALARM定义的软件告警被激活，或者来自开关TQMS_MIS_MINOR和TQMS_MIS_MAJOR告警。
A“**“infrontoflognameindicatesthisisaMajoralarm:
SXMSC1**EXT107OCT2915:
47:
062200INFOCMDUSEMAON
##CMDUSEMAmajoralarm告警激活.相应告警清除日志为：
SXMSC1**EXT107OCT2915:
47:
215600INFOCMDUSEMAOFF
###EXT108日志显示OMCRITICAL到达门限值，或者DMS收到来自DASdatalink的CriticalAlarm，或者DMS收到来自VSN的告警，或tableSFWALARM定义的软件告警被激活，或者来自开关TQMS_MIS_CRITICAL，TQMS_MIS_PROCESS和TQMS_MIS_BUFFS的紧急告警。
A“***“infrontoflognameindicatesthisisaCriticalalarm:
SXMSC1***EXT108JAN0116:
22:
115568INFODASLINKDOWNON
##DASdatalink告警激活.相应告警清除日志为：
SXMSC1***EXT108JAN0116:
22:
115568INFODASLINKDOWNOFF
###EXT109日志显示电池电压不足告警。
SXMSC1EXT109MAR1020:
10:
403456INFOLVDMSPWRON
PWRlevislowsince1987/03/0110:
20:
30
##电池电压告警激活.相应告警清除日志为：
SXMSC1EXT109MAR1020:
10:
403456INFOLVDMSPWROFF
PWRlevwaslowsince1987/03/0110:
20:
30
###EXT300logshowsEXTsubsystemdoesnotgenerateanEXT102“alarmoff”logwithin20seconds.A“**“infrontoflognameindicatesthisisaMajoralarm:
JXZHCIAJCM0**EXT300MAY0713:
50:
005200TBLExternalAlarm
Indication
Location:
CRSC_FSPAISB_MJ
Problemid:
5981
Status:
Alarmraised
Trouble:
Awaitingalarmclear
Action:
Checkalarmsource
Initialevent:
CRSC_FSPAISB_MJalarmindicated
Initialeventtime:
13:
40:
00
Duration:
20sec
Pendingevent:
CRSC_FSPAISB_MJalarmcleared
##CRSC_FSPAISB_MJEXT102告警清除日志在20秒内没有产生。
##EXT300告警没有相应的告警清除日志，只能通过观察MAP告警消除得知。
IODLog
AlarmclearinglogIOD105IOD101,IOD102,IOD103,IOD104;
AlarmclearinglogIOD110IOD106,IOD107,IOD108,IOD109;
AlarmclearinglogIOD114IOD111,IOD112,IOD113;
AlarmclearinglogIOD205IOD201,IOD202,IOD203,IOD204;
AlarmclearinglogIOD211IOD213;
AlarmclearinglogIOD305IOD301,IOD303,IOD304,IOD308,IOD305;
AlarmclearinglogIOD313IOD312;
AlarmclearinglogIOD315IOD308;
MSLog
AlarmclearinglogMS100MS101,MS102,MS103;
AlarmclearinglogMS150MS151,MS152,MS153,MS154,MS155,MS156;
AlarmclearinglogMS248MS248;
AlarmclearinglogMS260MS261,MS262,MS263,MS264,MS265,MS266,MS267;
AlarmclearinglogMS280MS281,MS282,MS283,MS284,MS285,MS286;
AlarmclearinglogMS281MS283,MS284,MS285,MS286;
AlarmclearinglogMS282MS283,MS284,MS285,MS286;
AlarmclearinglogMS283MS281,MS282,MS285,MS286;
AlarmclearinglogMS284MS281,MS282,MS285,MS286;
AlarmclearinglogMS285MS281,MS282,MS283,MS284;
AlarmclearinglogMS286MS281,MS282,MS283,MS284;
AlarmclearinglogMS300MS301,MS302,MS303,MS304,MS305,MS306;
AlarmclearinglogMS310MS311,MS312,MS313,MS314,MS315,MS316,MS317,MS318;
AlarmclearinglogMS320MS321,MS322,MS323,MS324,MS325,MS326,MS327;
AlarmclearinglogMS400MS401,MS402,MS403,MS404,MS405,MS406;
AlarmclearinglogMS410MS411,MS412,MS413,MS414,MS415;
PMLog
AlarmclearinglogPM106PM102,PM103,PM105,PM107,PM109,PM127,PM128;
AlarmclearinglogPM111PM109;
AlarmclearinglogPM154PM152,PM153;
AlarmclearinglogPM162PM163,PM164,PM165;
AlarmclearinglogPM181PM181;
AlarmclearinglogPM186PM187;
AlarmclearinglogPM195PM190,PM191,PM192,PM193,PM194;
AlarmclearinglogPM184PM182,PM183;
AlarmclearinglogPM223PM221,PM222;
PMLogsamples
###ThefollowingareexamplelogsgeneratedfortransmissionE1carrierloseandrecover:
###PM187logshowsthecarrier2onPDTC0ischangedtoSYSB（SystemBusy）state,theE1cannotbeusedsincethismoment.A“*“infrontoflognameindicatesthisisaMinoralarm:
JXZHCIAJCM0*PM187OCT1108:
18:
225800SYSBCARRIERPDTC0
CARRIER-NO:
2
SYSB:
RFAISSSET,
###7secondslater,thePM186logshowsthecarrier2onPDTC0isbacktoINSV（InService）state,theE1canbeused:
JXZHCIAJCM0PM186OCT1108:
18:
298000INFOCARRIERPDTC0
CARRIER-NO:
2
INSV:
RFAISSCLR,
RDTLog
AlarmclearinglogRDT301RDT301;
AlarmclearinglogRDT302RDT302;
AlarmclearinglogRDT303RDT303;
AlarmclearinglogRDT304RDT304;
AlarmclearinglogRDT305RDT305;
AlarmclearinglogRDT307RDT307;
AlarmclearinglogRDT308RDT308;
AlarmclearinglogRDT309RDT309;
SDMLog
AlarmclearinglogSDM501SDM502,SDM503,SDM504,SDM505;
AlarmclearinglogSDM550SDM550;
TRKLog
#trk101<-->trk102<-->trk103
AlarmclearinglogTRK101TRK102,TRK103
AlarmclearinglogTRK102TRK101,TRK103
AlarmclearinglogTRK103TRK101,TRK102;
AlarmclearinglogTRK104TRK101,TRK102,TRK103
AlarmclearinglogTRK107TRK106;
AlarmclearinglogTRK108TRK109;
AlarmclearinglogTRK112TRK110,TRK148;
TRKlogsamples
###以下为TRK告警产生及消失的过程报告:
HKCDMASNSECM*TRK101FEB1118:
27:
079500FLTGROUP_ALARMSB01VOICE8%BUSY
###TRK101报告表明FEB11,18:
27:
09时,中继组SB01VOICE有8%的电路忙。
HKCDMASNSECM
升级会员 