MOTOROLA系统设备告警评估
- 格式:doc
- 大小:264.50 KB
- 文档页数:6
交换网告警梳理——诺基亚分册目录一.诺基亚设备告警概述 (10)1.1原始告警格式 (10)1.2告警列表格式 (11)二.告警列表 (12)2.13ACCESS SERVICE IS OVERLOADED (12)2.24ACCESS SERVICE REJECT RATE LIMIT EXCEEDED (13)2.333FILE UPDATES TO DISK PREVENTED (13)2.4557STATISTICAL REPORTS LOST (14)2.5690WORKING STATE CHANGE (15)2.61001UNIT RESTARTED (15)2.71007RESTARTED PROGRAM BLOCK (16)2.81016MB INTERFACE FAILURE (17)2.91021PROGRAM BLOCK REWARMING STARTED (18)2.101022PROGRAM BLOCK WARMUP FAILURE (19)2.111024HAND PROCESS ERROR IN PROGRAM BLOCK (19)2.121044ERROR IN SWITCH COMPARE TEST (20)2.131072SIGNALLING LINK OUT OF SERVICE (21)2.141078PROCESS EXCEPTION (23)2.151088CONNECTION ERROR BETWEEN MSC AND SMSC (24)2.161103SIGNALLING MEASUREMENT REPORT LOST (25)2.171183HMS LINE CONNECTION LOST (27)2.181186NO RESPONSE TO HMN SUPERVISION (27)2.191195USSD SERVICE INFORMATION NOT FOUND (28)2.201425OVERFLOW IN ALARM BUFFERING (28)2.211559A-INTERFACE CIRCUIT ALLOCATION FAILURE (29)2.221569CRITICAL LIMIT IN SECURITY REPORTING REACHED (30)2.231574DATA ERROR FOUND BY PROTOCOL (30)2.241575COMPONENT NOT ACCEPTED BY REMOTE END (31)2.251645PROTOCOL MESSAGE QUEUE FULL (32)2.261647OPERATION TIMER EXPIRY (32)2.271667UNHANDLED MESSAGES OVERFLOW (33)2.281860DISK DISTURBANCE (34)2.292005CHECKSUM ERROR IN LOAD MODULE (34)2.302007FILE UPDATING ON AUXILIARY STORAGE IS NOT PROCEEDI (35)2.312012ERROR IN FILE OPENING (36)2.322015MB COMMUNICATION ERROR (37)2.332017FILE DISTRIBUTION ERROR (37)2.342018OVERFLOW IN HANDLING ALARM EVENTS (38)2.352023MAIN CLOCK FAILURE (39)2.362024MAIN CLOCK NEEDS ADJUSTMENT (39)2.372031MB CLOCK FAILURE (40)2.382032SSU CLOCK FAILURE (40)2.392033GSW CLOCK FAILURE (41)2.402034SWI CLOCK FAILURE (42)2.412035SUB CLOCK FAILURE (42)2.422036AONU CLOCK FAILURE (43)2.432037CLG-S FAILURE (44)2.442038MFR CLOCK FAILURE (44)2.452050PLUG-IN UNIT MISSING IN SWITCHING NETWORK (45)2.462051POWER FAILURE IN SWITCHING NETWORK (46)2.472052SWITCH CLOCK FAILURE (46)2.482064ROUTE SET UNAVAILABLE (47)2.492069SIGNALLING LINK TEST FAILED (47)2.502070LINK SET UNAVAILABLE (48)2.512071SIGNALLING LINK TERMINAL FAULTY (49)2.522072FAILURE IN SIGNALLING LINK ACTIVATION OR RESTORATION (50)2.532075COMMUNICATION FAILURE BETWEEN SIGNALLING TERMINAL (51)2.542079LOOP TEST FAILED IN SIGNALLING LINK TERMINAL (52)2.552087LOW TRAFFIC CAPACITY ON CIRCUIT GROUP (53)2.562092AVERAGE SEIZURE TIME BELOW THRESHOLD (53)2.572098CALL OVERLOAD IN EXCHANGE (54)2.582099LIMIT FOR UNSUCCESFUL CALLS EXCEEDED (55)2.592114FR VIRTUAL CONNECTION FAILED (55)2.602115FR USER LINK INTEGRITY VERIFICATION FAILED (56)2.612133SEND BUFFER OVERFLOW IN SIGNALLING TERMINAL (57)2.622137PLUG-IN UNIT LOCATION ERROR (58)2.632138PLUG-IN UNIT SOFTWARE PACKAGE CHECK SUM ERROR (58)2.642139PLUG-IN UNIT SOFTWARE PACKAGE LOAD FAILURE (59)2.652142PLUG-IN UNIT SUPERVISION FAILURE (60)2.662160PREPROCESSOR UNIT RESTART FAILURE (60)2.672171NO USER FOR OSI CLNS (61)2.682175OSI CLNS LINKAGE NOT AVAILABLE (61)2.692185ROUTING OF OSI OUTGOING CALL FAILED (62)2.702186CALL CONTROL ANALYSIS MISSING (63)2.712194ANNOUNCEMENT ID ANALYSIS ERROR (64)2.722202ET FAILURE (64)2.732205ET2FAILURE (65)2.742224ERROR IN MSU HANDLING (65)2.752241SCCP SUBSYSTEM PROHIBITED (67)2.762246SCCP ROUTING FAILURE (67)2.772247SS7ERRONEOUS SIGNALLING MESSAGE (69)2.782250FAILURE IN D-CHANNEL ACTIVATION OR RESTORATION (71)2.792252LOOP TEST FAILED IN PRIMARY RATE ACCESS TERMINAL (72)2.802254SCCP NOT DEFINED FOR NETWORK (72)2.812262OSI SUBNETWORK INTERFACE OUT OF ORDER (74)2.822269ERRONEOUS DISK CACHE SIZE (74)2.832272BOOT LOADING ERROR (75)2.842274SOMAFI ERROR (76)2.852285SIGNALLING TERMINAL FAULTY (77)2.862304TONE GENERATOR FAILURE (78)2.872339SP-CIC->PCM-TSL CONVERSION TABLE UPDATE ERROR (78)2.882347POWER SUPPLY FAILURE IN CPU (79)2.892386OVERWRITING UNTRANSFERRED VDS-DEVICE DATA FILE (79)2.902393FALLBACK COPYING TERMINATED IN ERROR (80)2.912394ERROR IN FINISHING FALLBACK COPYING (81)2.922397DATABASE FILE IS IN DANGER TO GET FULL (82)2.932399DATABASE DISK UPDATES ARE PREVENTED (82)2.942402AFS CONNECTION FAILURE (83)2.952403SERIAL CHANNEL FAILURE (83)2.962410CONNECTION OF A CIRCUIT HAS FAILED IN THE SWITCHING (84)2.972411RELEASING OF A CIRCUIT HAS FAILED IN THE SWITCHING (85)2.982414MISSING ACC REJECTION PERCENTAGES (86)2.992424DISCREPANCY BETWEEN RECORD DATA AND BITMAP (87)2.1002426CHECKSUM ERROR IN FILE BLOCK (88)2.1012439NO LINK BETWEEN MSC AND SMSC (88)2.1022445UNIT TYPE HAS NO REDUNDANCY (89)2.1032477GLOBAL RESET MESSAGE RECEIVED (89)2.1042478MOBILE ACCESS CLASSES ABNORMAL (90)2.1052494MSRN RESERVATION RATIO (91)2.1062503DETAILED CHARGING LOST (91)2.1072504CHARGING FILE FILLING UP (92)2.1082518NO VALID FALLBACK COPY FOR DEFAULT PACKAGE (93)2.1092525FAILURE IN STORING OF DETAILED CHARGING DATA (93)2.1102532ANALYSIS FOR NETWORK GENERATED NBR OR FOR CHA (94)2.1112536SUBSCRIBER DATABASE FILE IN VLR IS FULL (95)2.1122549FIRST ALARM LIMIT FOR UNAVAILABLE VDS-DEVICE (95)2.1132558ECHO CANCELLER CONNECTION FAILURE (96)2.1142562NUMBER NOT FOUND FROM HRNFIL OR INVALID DATA (97)2.1152568ERROR IN GSAPRB ANALYSIS FILE (98)2.1162590ERROR IN OPENING OUTPUT FILE (99)2.1172621FAULTY TIME SLOT IN TESTING OF TIME SLOT BASED UNIT (99)2.1182623TOTAL FAILURE OF TIME SLOT BASED UNIT (100)2.1192624FAULTY TIME SLOT IN TESTING OF MFST (101)2.1202632OSCILLATOR FAILURE (102)2.1212634POWER FAILURE IN SYNCHRONIZATION UNIT (102)2.1222636FAILURE IN OUTGOING CLOCK SIGNAL (103)2.1232638FAILURE IN BUS BETWEEN SYNCHRONIZATION UNITS (104)2.1242639FAILURE IN SYNCHRONIZATION UNIT SWITCHOVER (104)2.1252641FAILURE IN SYNCHRONIZATION SIGNAL (105)2.1262646PROTOCOL ROUTING FAILURE (106)2.1272650STORING OF THE DATA FAILED ON ONE DISK (107)2.1282651STORING OF THE DATA FAILED ON BOTH DISKS (107)2.1292652PHYSICAL DISK IS FULL (108)2.1302653FAILURE IN THE HANDLING OF CONTROL FILES (109)2.1312654NO SERVICE PACKAGE FOR CORE INAP TRIGGER KEY (109)2.1322656CIRCUIT POOL INFORMATION CONFLICT BETWEEN MSC (110)2.1332658CHARGED NUMBER FOR THE SECOND LEG OF REROUTING (111)2.1342661NO CONSISTENT COPY OF DATABASE ON DISK (111)2.1352662NO CONSISTENT DATABASE ANYWHERE (112)2.1362664DATABASE COPY STAYS INCONSISTENT ON SAME DISK (113)2.1372666DBSMAN STOPPED IN ACTIVE UNIT (114)2.1382668CALL ESTABLISHMENT FAILURE (114)2.1392671DATA SERVICE UNIT IS NOT AVAILABLE (116)2.1402675SS7GROUP RESET MESSAGE RECEIVED TO UNUSED CIRCUIT (117)2.1412683ERROR IN MML COMMAND LOG ACCESS (118)2.1422687SYSTEM RESTART IN PROGRESS (120)2.1432692INCORRECT WORKING STATE (121)2.1442693WO-EX UNIT FAULTY (121)2.1452703MAP PROCEDURE FAILURE–HIGH (122)2.1462720TELECOM LINK OVERLOAD (123)2.1472725ADJACENT CELL IDENTIFIER CONFIGURATION ERROR (124)2.1482733OUT OF AVAILABLE VDS-DEVICE DATA FILES (125)2.149273480%OF THE EVENT BUFFER USED (126)2.1502737ECHO CANCELLER CHANNEL FAILURE (126)2.1512740EXCESSIVE DISTURBANCES IN CALL INDEX RESERVATI (127)2.1522741NO SUCCESSFUL CALLS (127)2.1532742BSC/MGW(REL99)OUT OF SERVICE IN MSC (128)2.1542744BSC/MGW(REL99)OR BTS/SAC IN WRONG STATE IN MSC (129)2.1552745CELLULAR NETWORK CONFIGURATION ERROR (130)2.1562748NO ANALYSIS FOR SMSC ADDRESS (131)2.1572751PLUG-IN UNIT MISSING (132)2.1582754FUSE FAILURE (132)2.1592755CARTRIDGE CLOCK FAILURE (133)2.1602756CARTRIDGE POWER SUPPLY FAILURE (134)2.1612757CARTRIDGE NON-REDUNDANT POWER SUPPLY FAILURE (134)2.1622758POWER SUPPLY ADAPTER FAILURE (135)2.1632759POWER SUPPLY FUSE FAILURE (135)2.1642760HWAT FAILURE (136)2.1652761CLAB FAILURE (137)2.1662762SUPERVISION BUS FAILURE (138)2.1672763FAILURE IN BUS BETWEEN CLAB UNITS (138)2.1682764CLS FAILURE (139)2.1692767FEATURE NOT SUPPORTED (139)2.1702770PREPROCESSOR UNIT FAILURE (140)2.1712772BSC/MGW(REL99)CONTINUOUSLY OUT OF SERVICE IN MSC (140)2.1722773RESET CIRCUIT ACKNOWLEDGEMENT MISSING FROM BSC (141)2.1732777CDSU CHANNEL SUPERVISION FAILED (142)2.1742779CDSU PIU SOFTWARE LOADING FAILED (142)2.1752799FRAUD REPORTING NOT SUCCESSFUL (143)2.1762802CTU DISK BUFFERING INTERRUPTED (144)2.1772806SOMAFI UPDATE ERROR (145)2.1782809MASS MEMORY DEVICE POWER SUPPLY FAILURE (145)2.1792812PRINTER SPOOLER ALMOST FULL (146)2.1802818INCORRECT OPERATING STATE (147)2.1812827EMT PROTOCOL FAILURE (147)2.1822843ALARM DIFFERENCE BETWEEN BSC AND OMC (148)2.1832860DISK FAILURE (148)2.1842861NO ACCESS TO DISK (149)2.1852862DISK CHECKSUM ERROR (150)2.1862870MASS MEMORY POWER SUPPLY FAILURE (150)2.1872883TAPE MEDIA FULL (151)2.1882900INCOMING SIGNAL MISSING (151)2.1892902PCM LINE REMOTE END ALARM (152)2.1902908CODE ERROR RATE OVER LIMIT (153)2.1912909AIS RECEIVED (153)2.1922910FRAMING ERROR (154)2.1932911EXCESSIVE CODE ERROR RATE (155)2.1942912BIT ERROR RATE OVER LIMIT (155)2.1952915FAULT RATE MONITORING (156)2.1962923CRC BIT ERROR RATIO OVER LIMIT (157)2.1972925SLIP FREQUENCY LIMIT EXCEEDED (157)2.1982950TRCO FAILURE (158)2.1992952TRANSCODER PLUG-IN UNIT FAILURE (158)2.2002954NO TRAU FRAME SYNCHRONIZATION (159)2.2012955TRANSCODER CHANNEL FAILURE (160)2.2022992BTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON A (161)2.2032993BTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON AB (162)2.2043019NETWORK SERVICE ENTITY UNAVAILABLE (163)2.2053020NETWORK SERVICE VIRTUAL CONNECTION UNAVAILABL (164)2.2063022NETWORK SERVICE VIRTUAL CONNECTION BLOCK PROCEDURE165 2.2073023NETWORK SERVICE VIRTUAL CONNECTION RESET PROCEDURE 165 2.2083024NETWORK SERVICE ENTITY CONFIGURATION MISMATCH (166)2.2093025NETWORK SERVICE VIRTUAL CONNECTION TEST PROCEDURE (167)2.2103026NETWORK SERVICE VIRTUAL CONNECTION PROTOCOL ERROR.. 168 2.2113027.UPLINK CONGESTION ON THE NETWORK SERVICE VIRT (168)2.2123032BSSGP VIRTUAL CONNECTION PROTOCOL ERROR (169)2.2133050NO RESPONSE FROM PLUG-IN UNIT (169)2.2143053ETHERNET INTERFACE FAILURE (170)2.2153084ECHO CANCELLER CHANNELS FAILURE (171)2.2163118UNDERVOLTAGE IN POWER SUPPLY BRANCH UB1OF THE SYS (171)2.2173126DATABASE FILE FOR NORMAL SUBSCRIBERS IS IN DANG (172)2.2183146FAN UNIT FAILURE (173)2.2193156ASSOCIATION ROUTING FAILURE (173)2.2203159SCTP ASSOCIATION LOST (174)2.2213216CONNNECTION BETWEEN MSC AND SMSC FAILED (174)2.2223263CALL ESTABLISHMENT FAILURE IN USER PLANE CONTROL (175)2.2233273(E)GPRS TERRITORY FAILURE (178)2.2243293SCTP PRIMARY PATH NOT AVAILABLE (179)2.2253295LICENCE CAPACITY EXCEEDED (180)2.2263296IWF IP CONNECTION LOST (181)2.2273799MESSAGE BUS FAILURE (181)2.2283937H.248.IP CONNECTION LOST (182)2.2293947VIRTUAL MEDIA GATEWAY IS OUT OF SERVICE (183)2.2304000POWER FAILURE ALARM(外部告警) (184)2.2315001VMS(外部告警) (184)2.2325002VMS(外部告警) (185)2.2335003VMS(外部告警) (185)2.2347208LOCAL BLOCK (185)2.2357220RADIO LOOP OR RX ANTENNA TEST EXECUTION (186)2.2367524TX FREQUENCY TUNER OUT OF ORDER (186)2.2377526RX FREQUENCY TUNER OUT OF ORDER (187)2.2387528TEST LOOP TUNING OUT OF ORDER (188)2.2397530TX OUTPUT POWER LEVEL DECREASED (188)2.2407533TX ANTENNA OR COMBINER CONNECTION FAULTY (189)2.2417549INTERNAL DATA TRANSFER FAILURE (190)2.2427600BCF FAULTY (190)2.2437601BCF OPERATION DEGRADED (191)2.2447602BCF NOTIFICATION (192)2.2457604BTS OPERATION DEGRADED (193)2.2467606RX FAULTY (193)2.2477607TRX OPERATION DEGRADED (194)2.2487608TRX NOTIFICATION (194)2.2497609TRE FAULTY (195)2.2507616OSCILLATOR ADJUSTING TEMPORARILY INTERRUPTED (196)2.2517622CABINET OPEN (196)2.2527700BTS OMU INITIALIZATION (197)2.2537701BCF INITIALIZATION (197)2.2547704PCM FAILURE (198)2.2557705LAPD FAILURE (198)2.2567706BTS O&M LINK FAILURE (199)2.2577711WORKING FULL RATE TCH RATIO BELOW THRESHOLD (199)2.2587715CONTINUOUS RESTARTS OF BCF/TRX (200)2.2597716ACTIVE BCF HW DATABASE DIFFERENCE (200)2.2607717WORKING HALF RATE TCH RATIO BELOW THRESHOLD (201)2.2617723FAILURE IN SENDING SYSTEM INFORMATION TO BTS SIT (201)2.2627724CONFLICT BETWEEN BSS RADIO NETWORK DATABASE A (202)2.2637725TRAFFIC CHANNEL ACTIVATION FAILURE (204)2.2647730CONFIGURATION OF BCF FAILED (204)2.2657735TRX TEST FAILED (206)2.2667736ABIS LOOP TEST FAILED (207)2.2677738BTS WITH NO TRANSACTIONS (208)2.2687740BEATING BTS ALARM (208)2.2697741MEAN HOLDING TIME ABOVE DEFINED THRESHOLD (209)2.2707743MEAN HOLDING TIME BELOW DEFINED THRESHOLD (210)2.2717744EXCESSIVE TCH INTERFERENCE (211)2.2727745CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD (212)2.2737746CH CONGESTION IN CELL ABOVE DEFINED THRESHOLD (213)2.2747753TRX LOOP TEST FAILED (214)2.2757767BCCH MISSING (215)2.2767801MMI CONNECTED TO BASE STATION (216)2.2777805UNIT TEMPERATURE HIGH (216)2.2787808FAULT IN Q1-INTERFACE OF BCF (217)2.2797840SW DOWNLOAD TO UNIT FAILED (217)2.2807861SERVICE TERMINAL CONNECTED TO ABIS TRANSMISSIO (218)2.2817870CABINET DOOR OPEN (219)2.2827890FAULT IN COOLING FAN (219)2.2837900NO CONNECTION TO TRX (220)2.2847939FORWARD POWER TOO LOW AT TX ANTENNA (220)2.2857941TX ANTENNA PERFORMANCE DEGRADED (221)2.2867944MAIN BRANCH LNA OUT OF ORDER IN ANTENNA FILTER UNI (222)2.2877949DIFFERENCE IN RX LEVELS OF MAIN AND DIVERSITY ANTE (222)2.2887990MAINS BREAKDOWN WITHOUT BATTERY BACK-UP (223)2.2897991POWER SUPPLY FAULT (224)2.2908000POWER SUPPLY FAULT (224)2.2918050LOSS OF INCOMING2M SIGNAL (225)2.2928066ALARM INDICATION SIGNAL(AIS)RECEIVED (226)2.2938081LOSS OF FRAME ALIGNMENT (226)2.2948086LOSS OF CRC MULTIFRAME ALIGNMENT (227)2.2958099RECEIVED BIT ERROR RATIO(BER)>1E-3 (228)2.2968102RECEIVED BIT ERROR RATIO(BER)>1E-6 (229)2.2978112FREQUENCY ERROR (229)2.2988179FAR-END ALARM (230)2.2999011FAILURE IN DATA COMMUNICATION NETWORK (231)2.3009041PROCESS RECOVERY IS NEEDED REPEATEDLY (232)2.3019047ALARMS FROM NETWORK ELEMENT NOT ARRIVING (232)2.3029108FAILURE IN OMC-NE COMMUNICATION LINK (233)2.3039112THE MINIMUM NUMBER OF PROCESSES REQUIRED IS NO (234)2.3049122MEASUREMENT DATA HAS NOT ARRIVED FROM THE NE (234)2.3059205FILE SYSTEM IS BECOMING FULL (235)2.3069207NE CLOCK TIME DEVIATION EXCEEDS THE ALARM (236)2.3079212NO CONNECTION TO DATABASE CONNECTION SUPERVIS (236)2.3089224SUPERVISION PROGRAM FAILED (237)2.3099228ALARM DATABASE UPLOAD IN PROGRESS (238)2.3109450CONNECTION FAILURE TO AN SNMP HOST (238)2.3119451SNMP AGENT NOT RESPONDING (239)2.31219800CONNECTION LOST (240)2.31332333CAN NOT INITIALISE CHARGING (240)一. 诺基亚设备告警概述1.1 原始告警格式 ZMMSC2_I OMU-1SWITCH 2006-01-12 16:13:31.98**ALARM OMU-1 1A004-08SAVDAT FILE UPDATING ON AUXILIARY STORAGE IS NOT PROCEEDING 00 10053d 07670000 02A0 4402(1531)2007 交换机名称发送告警单元告警设备类型日期时间告警级别告警输出序列号告警号输出类型出现问题单元告警单元位置告警软件模块告警正文附加信息交换机名称:产生告警的设备名称 告警设备类型:SWITCH 交换单元 O&M 操作维护单元 TRANSM 传输单元 POWER 电源设备 EXTERN 外部设备 日期时间:告警的发生时间 告警级别:*** 需要立即处理** 在一段时间范围内处理 * 一般不需处理 (?). 未知的告警级别以?标识 输出类型:ALARM 故障状态 CANCEL 故障结束 DISTUR 干扰 NOTICE 通知 出现问题单元:产生告警的功能单元。
常见告警故障处理及分析MOTOROLA基站的告警按故障设备可分为三类:设备告警、内部告警、外部告警。
一、设备常见告警设备告警是硬件告警最常见也是最重要的告警,告警设备一般为基站的主要器件,它的告警类型就是它的设备类型。
1. DRI 29:[Front End Processor Failure - Watchdog Timer Expired] 前端处理器故障DRI硬件故障,出现此告警时DRI可能会反复自启,可能会退服,应先reset or ins DRI应进行INS或RESET处理,若告警未消失,更换TCU。
2. DRI 40-47 :[Channel Coder Timeslot 0(-7) Failure] 0-7时隙信道编码器失败。
M-CELL基站经常出现此类告警,应进行INS或RESET处理,不行再更换TCU900。
此告警在GSR4时出现,升级到GSR5可能会消失。
3. DRI 51 :[Baseband Hopping TDM Link Error]基带跳频TDM链路错误。
此告警有几种可能性:TDM-Highway BUS或KSW可能有问题。
DRIM的FEP,CCDSP可能有问题。
此告警须在现场具体测试分析。
测试后判定故障点。
此告警在GSR4时出现,升级到GSR5可能会消失TDM——Time Division Multiplexing时分复用:该总线用于把来自BTS的呼叫与信令数据传送到MSC,反之亦然。
可分为两个独立的部分:交换机公共通路&出局公共通路。
交换机公共通路:处理路由到交换机的数据,数据来自外部信源 (通过E1/T1接口)或由GPROC内部产生。
出局公共通路:这是一个被交换的数据,现在被路由出BSC/RXCDR (通过E1/T1接口)或通向内部GPROC。
4. DRI 81:[Transmitter Synthesizer Failure]收发单元故障此告警为收发单元TCU故障,故障原因有可能为:-接收Calibration频点丢失-信道盘的CEB故障-射频电缆连接失败处理方法:远程ins或reset TCU,告警消失并监测;若告警未消失,更换TCU 5. DRI 86 :[Transmitter Failure]输出功率失败,引起DRI退出服务。
摩托罗拉BSS系统安全监控手册摩托罗拉浙江分公司协维组内容提要本部分内容综述GSM BSC级系统网络的硬件告警处理及一些日常监控方法,提供维护过程中分析问题的一般思路,对常见告警的处理,实际故障解析等。
对一些工具的使用,还有常见故障的案例和日常维护工作的注意事项。
通过本部分的学习读者将具有GSM BSC级网络维护的一般知识,掌握BSS系统基本维护技能,能够承担日常的网络维护工作。
目录序论 (4)维护工作的要旨--防患未燃 (4)分析问题的一般思路 (5)第一章日常监控数据收集 (6)一、ECT (6)二、EVENT LOG : (7)第二章BSS系统安全监控 (8)一、告警定义 (8)二、监控列表及描述 (8)GPROC告警 (9)GCLK告警 (10)KSW告警 (11)LAN告警 (13)BSP告警 (14)MSI告警 (15)MTL告警 (15)XBL告警 (17)数据总线告警 (17)BSS告警 (19)第三章故障处理分析 (20)一、常见故障分析处理 (20)GPROC的故障处理 (20)GCLK的故障处理 (21)KSW的故障处理 (22)KSWX/DSWX板的故障: (22)LANX的故障处理 (23)MSI的故障处理 (24)MTL的故障处理 (24)BSP的故障处理 (25)数据总线的故障处理 (26)单通故障的处理 (29)二、日常维护的注意事项 (29)三、典型问题汇总 (30)序论维护工作的要旨--防患未然系统建设完成经过验收后,就转入系统维护工作。
由于此时系统已经给终端用户提供服务,网络的任何故障均可能对终端用户产生影响,从而对运营商的形象产生影响。
所以维护工作的要旨是防患于未燃,将系统隐患尽早排除,不要使其成为系统故障而影响系统的性能。
预防性维护是我们的最佳选择,定期对任何一个BSS网元的巡检和对基站的安装调测都进行严格的检测调整,保证系统及其附属外围设备工作在正常状态,通过集中性预防维护,可以及时发现系统隐患并加以排除,最大限度地提高现行系统设备的利用率,增强系统设备的可靠性,从而减轻平时日常维护的压力。
NOKiA 常见告警列表1252--数据连接错误率过多--EXCESSIVE ERROR RATE ON DATA LINK CONNECTION--不通知1569--安全报告达到临界极限--CRITICAL LIMIT IN SECURITY REPORTING REACHED--不通知2007--文件更新到备份储存器失败--FILE UPDATING ON AUXILIARY STORAGE IS NOT PROCEEDIN--通知(用DUQ查询是否更新成功,0为正常)2015-- MB单元通讯错误--MB COMMUNICATION ERROR--通知2017--文件分配错误--FILE DISTRIBUTION ERROR--不通知2018--标志池满--DYNAMIC FLAGPOOL FULL--如果附加信息为告警号0003、0004、0026、0691、0860、1001、1007、1014、1016、1020、1023、1024、1071、1072、1078、1559,1571、1645、1677、1860引起的告警,立即通知话务室,其他不通知(由附加信息第一项的告警产生过多引起,一般不会自动消失,需手动清除)2039--ET时钟失败--ET CLOCK FAILURE--通知2054--CHECKSUM ERROR IN BOOT PROM--通知2055--VANG FAILURE--通知2056--CHECKSUM ERROR IN VANG SAMPLE--不通知2064--ROUTE SEA无效--ROUTE SET UMAVAILABIE--通知---用NRI指令查看路由状态,正常状态为AV-EX或AV-SP2068--文件分配失败--FILE DISTRIBUTION FAILURE2069--信令检验失败--SIGNALLING LINK TEST FAILED--通知(一般由传输环路引起)---用NEL指令查LINK状态2070--LINK SET异常--LINK SET UNAVAILABLE--通知---用NSI指令查看状态,正常状态为AV2072--LINK激活或恢复失败--FAILURE IN SIGNALLING LINK ACTIVATION OR RESTORATION--通知---用NEL指令查LINK状态2099--不成功的呼叫率超过门限—忙时需重视(白天很重要,发单)——TUT:SER查询未接通率2122--多功能缺少--MULTIFRAE MISSING--不通知2123--REMOTE END MULTIFRAME MISSING--不通知2130—CCS电路错误状态CCS CIRCUIT IN FAILURE STA TE--不通知2137--插件单元位置错误--PLUG-IN UNIT LOCATION ERROR--通知2138--软件包插件单元校验错误--PLUG-IN UNIT SOFTWARE PACKAGE CHECK SUM ERROR--通知2139--软件包插件单元装载失败--OFTWARE PACKAGE LOAD FAILURE--通知2153--CIRCUIT RELEASING FAILED IN CAS--不通知2160--预处理单元重启失败--PREPROCESSOR UNIT RESTART FAILURE--通知2163--线路信号反常--ABNORMAL LINE SIGNAL RECEIVED --不通知2184--OSI CLNS MANAGEMENT INFORMA TION CORRUPTED--不通知2186--不通知2185--路由操作失败--ROUTING OF OSI OUTGOING CALL FAILED--不通知2205--传输告警--ET2 FAILURE--不通知(个别时隙不好)2224--ERROR IN MSU HANDLING--不通知2227--事件日志保留错误--EVENT LOG SAVING ERROR--不通知2234--计费文件缓存器已满--HOT BILLING RAM-BUFFER IS FILLING UP--不通知2241--SCCP子系统被禁止--SCCP SUBSYSTEM PROHIBITED--通知---用NHI查看子系统状态,正常状态为AV-EX2246--SCCP路由失败--SCCP ROUTING FAILURE--不通知2247--信令消息错误--SS7 ERRONEOUS SIGNALLING MESSAGE--不通知2250--D信道激活或恢复失败--FAILURE IN D-CHANNEL ACTIVATION OR RESTORATION--通知(附加信息最后一位是ET号)ZDTF:ET,ET号;2252--主要存取终端上的循环测试失败--LOOP TEST FAILED IN PRIMARY RATE ACCESS TERMINAL--通知2254--网络中的SCCP没有定义--SCCP NOT DEFINED FOR NETWORK--不通知2259--数据库不一致--DATABASE IS INCONSISTE NT--通知,发单2262--OSI子系统界面状态不好--OSI SUBNETWORK INTERFACE OUT OF ORDER--不通知(一般伴随3053告警,大量闪断时通知,重要时需发单)2269--错误的磁盘缓存尺寸--ERRONEOUS DISK CACHE SIZE--通知2272--BOOT LOADING ERROR2274--SOMAFI文件错误--SOMAFI ERROR--通知(SOMFI文件很重要)2381--空闲存储空间减少--AMOUNT OF FREE MEMORY CRITICALLY REDUCED 2386—VDS设备数据文件写入过多而无法转移--OVERWRITING UNTRANSFERREDVDS-DEVICE DATA FILE--不通知2390--时钟外同步信号丢失--EXTERNAL CLOCK SYNCHRONIZATION SIGNAL MISSING--不通知2393--FALLBACK COPYING TERMINATED IN ERROR--通知(ZZ所有HLR通知)2397—数据库文件将满--DATABASE FILE IS IN DANGER TO GET FULL--通知,发单2398--订户操作被阻止--SUBSCRIBER HANDLING BATCH JOB INTERRUPTED--不通知2399--数据库无法更新--DATABASE DISK UPDATES ARE PREVENTED--通知2402--AFS板连接故障--AFS CONNECTION FAILURE--通知2403--连续的信道错误--SERIAL CHANNEL FAILURE--通知2410--A口电路连接失败--CONNECTION OF A CIRCUIT HAS FAILED IN THE SWITCHING NETWORK2424--记录数据和位图内容不一致--DISCREPANCY BETWEEN RECORD DATA AND BITMAP----不通知2439--MSC和短信中心无连接--NO LINK BETWEEN MSC AND SMSC--通知并发单(MSC至SMSC断连,会影响短信收发,重要告警)2445--单元类型无冗余--UNIT TYPE HAS NO REDUNDANCY--通知2449--MSRN操作错误--MSRN HANDLING ERROR--2494—MSRN保留率--MSRN RESERVATION RATIO—立刻通知2503--计费丢失--DETAILED CHARGING LOST--2504--计费文件满--CHARGING FILE FILLING UP—2518--系统备份未完成--NO VALID FALLBACK COPY FOR DEFAULT RACKAGE--通知对端备份---用WQO:CR;查软件包状态,看FB包时间是否是最新2525--计费数据存储失败--FAILURE IN STORING OF DETAILED CHARGING DATA--2532--网络适配器丢失--ANALYSIS FOR NETWORK GENRATED NBR OR FOR CHA CASE IS MISSING--不通知2533--路由数字丢失--ROUTING NUMBER MISSING FROM RZN TABLE--通知2536--VLR上用户数据满--SUBSCRIBER DATABASE FILE IN VLR IS FULL--2547--调制解调器错误--MODEM FAILURE--2549--不可用的VDS存储器数据文件达到首要告警界限--FIRST ALARM LIMIT FOR UNAVAILABLE VDS-DEVICE DATA FILES REACHED--通知---用IFO:CHU:GSMCHA:,FULL;查询---用IFS:CHO:GSMCHA:号码&&号码:T;改状态ZIFS:STU:GSMCHA:3,TRANS,:T:;2550--不可用的VDS存储器数据文件达到第二告警界限--SECOND ALARM LIMIT FOR UNAVAILABLE VDS-DEVICE DATA FILES REACHED2551--可用的VDS存储器数据文件溢出--OUT OF AVAILABLE VDS-DEVICE DATA FILES 2558--回声抑制器连接失败--ECHO CANCELLER CONNECTION FAILURE-- (附加信息第一位为ET号)2559--数据访问出错--DATA CALL ERROR RATIO EXCEEDED-不通知2562--NUMBER NOT FOUND FROM HRNFIL OR INVALID DATA--通知(一般由于单元重启引起,可能不会自动消失,需手动清除)2568--ERROR IN GSAPRB ANALYSIS FILE--通知2590--ERROR IN OPENING OUTPUT FILE--通知2595--时隙失败--EC/IWF TIME SLOT FAILURE--不通知2596--SCCP登记错误--SCCP REGISTRATION ERROR--通知2618--计数器更新错误--UPDATING ERROR OF ACCOUNTING COUNTERS--附加信息第二项为FFFFFFFF第五项为 9999d的不用通知,若出现其他信息则需通知2621--时隙测试失败--FAULTY TIME SLOT IN TESTING OF TIME SLOT BASED UNIT--不通知2632--时钟震荡器故障--OSCILLATOR FAILURE--通知2638--同步单元故障--FAILURE IN BUS BETWEEN SYNCHRONIZATION UNITS --通知2639--FAILURE IN SYNCHRONIZATION UNIT SWITCHOVER--通知2641--同步输入信号失败--FAILURE IN SYNCHRONIZATION SIGNAL--通知,需发单(若为传输引起,查询传输不会显示局向)---用DRI查询看哪个2M不好(TUT:SER查呼叫失败率,20%为正常)2646--路由协议失败--PROTOCOL ROUTING FAILURE--不通知2650--硬盘数据存储失败--STORING OF THE DATA FAILED ON ONE DISK--通知2651--双方硬盘数据存储失败--STORING OF THE DATA FAILED ON BOTH DISKS--通知2653--管理文件操作失败--FAILURE IN THE HANDLING OF CONTROL FILES--不通知2654--核心网触发键无服务包--NO SERVICE PACKAGE FOR CORE INAP TRIGGER KEY--通知(该告警的出现是因为对端HLR中参数所引起,当用户漫游到河南时,用户数据里插入的有SSET参数,河南的SSET参数为20,当双方不一致时候产生该告警)2658--第二路由的计费数字丢失--CHARGED NUMBER FOU THE SECOND LEG OFREROUTING IS MISSING—根据附加信息是否通知一般不用处理2659--ERROR IN POOL CONTROLLER MESSAGE TRAFFIC--不通知2661--硬盘数据库拷贝不一致--NO CONSISTENT COPY OF DATABASE ON DISK--不通知2663--数据管理器堆积错误--DUMPING ERROR IN DATABASE MANAGER--不通知2664--同一硬盘数据库拷贝停留在不一致状态--DATABASE COPY STAYS INCONSISTENT ON SAME DISK--通知2666--数据更新停留在活动单元--DBSMAN STOPPED IN ACTIVE UNIT--不通知2668--呼叫建立失败--CALL ESTABL IS HMENT FALLURE----不通知2671--数据服务单元不可用--DATA SERVICE UNIT IS NOT AVAILABLE--通知2673--MAXIMUM NUMBER OF EX ECUTED DIGIT A NALYSIS EXCEEDED--不通知2683--MML命令日志访问错误--ERROR IN MML COMMAND LOG ACCESS--通知2692--相关单元或I/O设备工作状态异常--INCORRECT WORKING STATE--通知(CTU和FDU单元不用处理)---用USI查单元状态,在变为测试状态时系统会自动诊断,用UDH查诊断结果,结果为3999表示已通过,若状态仍未恢复,则需手动恢复2693--WO-EX单元错误--WO-EX UNIT FAULTY-通知2733--NO FREE RING DISK FILE--不通知2734--事件缓冲器溢出--EVENT BUFFER OVERFLOW--通知2735--事件缓冲器溢出--EVENT BUFFER OVERFLOW--通知2737--回声道删除失败--ECHO CANCELLER CHANNEL FAILURE--通知2740--呼叫指数保留有过多干扰--EXCESSIVE DISTURBANCES IN CALL INDEX RESERVATION2742--BSC退出服务--BSC/MGW(REL99) OUT OF SERVICE IN MSC--通知2744--MSC上的BSC或BTS状态错误--BSC/MGW(REL99) OR BTS/SAC IN WRONG STATE IN MSC--不通知2745--网络结构错误--CELLULAR NETWORK CONFIGURATION ERROR--通知地市(一般因相邻小区数据做错或未做引起)---用EDO或EPO查,LAC和CI号需转换为10进制2748--短信中心地址未分析--NO ANALYSIS FOR SMSC ADDRESS-2749--NO ANALYSIS FOR SMSC AEN--不通知2750--DC/DC CONVERTER FAILURE--通知2751--插件单元丢失--PLUG-IN UNIT MISSING--通知---WTI查插板2754--保险丝断连--FUSE FAILURE--通知2755--时钟创建失效--CARTRIDGE CLOCK FAILURE--通知2757--备用电源故障--CARTRIDGE NON-REDUNDANT POWER SUPPLY FAILURE--通知2758--电源故障--POWER SUPPLY ADAPTER FAILURE--通知,需发单2759--电源保险丝故障--POWER SUPPLY FUSE FAILURE--通知2760--HWAT板故障--HWAT FAILURE--通知2764-- CLS FAILURE2773--自BSC的电路重启确认失败--RESET CIRCUIT ACKNOWLEDGEMENT MISSING FROM BSC--不通知(一般由于传输引起,附加信息第三项为ET号)2777--CDSU CHANNEL SUPERVISION FAILED--不通知2778-- MOST OF CDSU CHANNELS ARE IN FAULTY STATE--通知2779--CDSU PIU SOF TWARN LOADING FAILED--不通知2802--CTU DISK BUFFERING INTERRUPTED--不通知2806--SOMAFI文件更新错误--SOMAFI UPDATE ERROR--通知(索玛菲文件很重要)2827--EMT协议失败--EMT PROTOCOL FAILURE--通知2860--硬盘故障--DISK FAILURE-通知2861--硬盘无法存取--NO ACCESS TO DISK--通知(注:硬盘系统严重故障,不能正常读写数据)2862--硬盘错误--DISK CHECKSUM ERROR--通知2883--磁带满--TAPE MEDIA FULL--不通知2900--引起信号丢失--MULTIFRAME MISSING--通知2909--传输告警--AIS RECEIVED--通知2915--传输告警--FAULT RATE MONITORING--通知地市RCI:SEA=4:CRCT=ET号-1&&-31;看局向发单2925--滑码超过界限--SLIP FREQUENCY LIMIT EXCEEDED-3053--以太网界面错误--ETHERNET INTERFACE FAILURE--通知(大量闪断时需发单,一般伴随2262告警)3083--回声抑制故障--ECHO CANCELLER FAILURE--通知3084--回声抑制信道故障--ECHO CANCELLER CHANNELS FAILURE--通知(可能是ET的某个时隙不好引起,也可能是由于硬件故障引起,一般重启ET后告警就能恢复)3126--用户数据库即将达到满容量门限--DATABASE FILE FOR NORMAL SUBSCRIBERS IS IN DANGER TO GET FULL--无需通知即发单至对端3146--风扇故障--FAN UNIT FAILURE--通知,发单话务3263--CALL ESTABLISHMENT FAILURE IN USER PLANE CONTROL--不通知(由于版本升级引起)3294--容量告警--LICENCE CAPACITY WARNING--通知,发单7404--AIR-CONDITION ABNORMAL7410--WATER7723--FAILURE IN SENDING SYSTEM7724--CONFLICT BETWEEN BSS RADIO NET WORK DATAB7406--TEMPERATURE OUER THE THRESHOLD7408-RECTIFIER ABNORMAL8050--LOSS OF INCOMING 2M SIGNAL8086--LOSS OF CRC MULTIFRAME ALIGNMENT8099--RECEIVED BIT ERROR RATIO(BER)〉IE-39108--通信链路失败--FAILURE IN OMC-NE COMMUNIC ATION LINK--通2494—MSRN RESERVATION RATIO注:漫游号保留的比率,可能引起限呼2099—LIMIT FOR UNSUCCESFUL CALLS EX CEEDED 注:成功的呼叫率低,在忙时需引起重视2397—DATABASE FILE IS IN DANGER TO GET FULL 注:在HLR中出现过,数据库文件满,需在附加信息中确定是哪一个数据库文件满。
诺基亚设备告警代码的含义翻译告警号星级网优级别告警描述告警解释及处理建议7523 ** 2 TRX TEMPERATURE DANGEROUSLY HIGH TRX 单元中的温度高于80 摄氏度(必须关闭TX 电源以防止组件损坏7524 ** 2 TX FREQUENCY TUNER OUT OF ORDER 某个TX 锁相合成器(PLLI 或PLL2 )出现故障7525 ** 2 TX MAIN FREQUENCY TUNER OUT OF ORDER TRX 参考频率合成器未锁7526 ** 2 RX FREQUENCY TUNER OUT OF ORDER 某个RX 锁相合成器出现故障7527 ** 2 RX MAIN FREQUENCY TUNER OUT OF ORDER RX 参考频率合成器未锁(PLL3 )7528 ** 3 TEST LOOP TUNING OUT OF ORDER TRX 环路合成器未锁并可能发生故障7529 ** 2 RECEIVER FAULT 该告警表示某个RX 模块合成器中有故障7530 ** 2 TX OUTPUT POWER LEVEL DECREASED 因为RFU 中的HW 发生故障,TX 功率电平低于给定的值(发射功率电平下降7531 ** 2 TX OUTPUT POWER LOST 如果发送器电源的测量指出断电(尽管传输应该是活的), TRX 软件产生该告警。
7532 ** 2 TRANSMITTER OUT OF CONTROL 如果发送器电源的测量指出有电(尽管传输应该被关闭), TRX 软件产生该告警7533 ** 2 TX ANTENNA OR COMBINER CONNECTION FAULTY 该告警指出在TRXTX 接口中的SWR 太高,发射天线或合路器连接失败7535 ** 2 RECEIVING FAULT IN BASEBAND MODULE 使用了分集,则两条EQDSP接收线路都有故障。
一.NOKIA告警概述1.告警查看方法ZEOL:BCF; 查看当前BCF告警;ZEOH:YYYY-MM-DD:BCF= BCF号;查看从输入日期至今的告警;ZAHO;查看BSC当前告警;ZAHP;查看BSC历史告警;2.告警格式我们平时主要关注BTS级别的告警,常见的告警格式如下输出类型:ALARM 故障状态CANCEL 故障结束DISTUR 干扰NOTICE 通知告警级别:*** 需要立即处理** 在一段时间范围内处理* 一般不需处理事件类型:COMM : communication failureQUAL : quality of servicePROCES: processing failureEQUIPM: equipment failureENVIR : environmental failure告警号:7000# ~ 7999# 告警是针对 BTS 出的告警,是我们日常需要关注的。
8000# ~ 8999# 告警是针对传输出的告警2000# ~ 2999# 告警是针对 BSC 级出的告警二.某市NOKIA告警概况为了对NOKIA告警有更形象的认识,2012年2月24日早提取FBSC01、FBSC02、FBSC07、FBSC08、FBSC28五个BSC共2406小区的BTS级当前告警,具体情况如下:按告警级别分:按告警类型分:从以上数据,不难发现,从告警级别看,现网两星告警较多,约占所有告警数的75%;从告警类型看,全网存在最多的告警为7743、7745,两者约占全部告警的40%左右。
这些告警具体表现是什么、该如何消除?下面将对现网中,常见的告警进行分析。
三.常见告警1.信道失败1.1.7743告警告警内容:FBSC01 BCF-0481 BTS-0482 QUAL 2012-02-24 04:25:17.53** ALARM TRX -003 TENGFEIQICXL2D(20176) 7743 MEAN HOLDING TIME BELOW DEFINED THRESHOLD00 00 00 01 01 01 01 01 03 02 3d告警解释:在测量时段内,在指定信道上的平均占用时间低于最小值。
MOTOROLA BSS系统设备告警评估常见故障分析部分按字母顺序:一、ABSS告警解释:The ABSS is equipped after its associate RXCDR. An ABSS is equipped for each BSS served by the RXCDR(也就是说,一个RXCDR带多少个BSS,就需要配置多少个ABSS,ABSS是与BSC对应的). ABSS are logical software–created process models which match existing BSC devices, and are equipped at RXCDRs to enable the provisioning of Ater circuit resources.(XBL:BSC和RXCDR之间的操作维护链路)*从RXCDR到指定BSC的XBL链路挂了。
*后果:If CIC validation is enabled for the local RXCDR, the BSC blocks all CICs routed through the RXCDR. No call traffic is possible between the specified BSS and the RXCDR.If CIC validation is not enabled for the local RXCDR, the BSC does not block CICs and call traffic is not immediately impacted. If the RXCDR experiences a fault condition causing the CIC to be blocked, the BSC is not notified. In this case, traffic is impacted because the BSC may attempt to use the blocked CIC resulting in no audio.*这个CIC确认,BSC端有个参数:CIC_V ALIDATION,可以设定为开或关。
*可能原因:设备故障导致XBL退服BSC或RXCDR上配置XBL的MMS退服了*The ABSS was placed in the Busy-Unlocked state indicating that CIC validation is enabled at the BSC, but the BSC did not initiate CIC validation for this RXCDR.(ABSS是B_U正常,并且指示BSC 是打开了CIC确认功能的(BSC端cic_validation参数=1),但BSC对这个功能的开启却未能传达到RXCDR(AXCDR))。
*后果:•All CICs going to the RXCDR are blocked at the MSC. No calls are handled by the RXCDR from the BSC until the problem is resolved.•CICs are not blocked at the MSC, but only certain CICs are actually capable of handling traffic. This may cause CERM alarms and high rates of incomplete calls.•总的来说会引起单通无声现象,并可能伴随BSS 43# 告警: Circuit Fault Detected on PCM Circuit*可能原因:XBL链路上LAPD协议出错XBL链路故障或者BSC和RXCDR之间的交换设备故障*解决办法:针对可能的原因排障关掉BSC的cic_validation参数复位相关的ABSS注意修改cic_validation参数后需重启BSC,以防止该问题发生相关文档:福建南平升级到GSR7后出现串话事件的这个RXCDR无法为至少一个CIC分配一个适当的连接。
ABSS处在D_U- No Validation 状态,And至少有一个CIC在ABSS上没有静态的Ater电路。
根据MSC的request,所有的呼叫都能被BSC建立,但是因为没有适当的物理连接For CIC(s),所以通话建立后在这个逻辑的CIC上就没有声音。
*附加信息:附加信息里有受到影响的CIC号,以及ABSS号。
*可能的原因:One or more CICs were equipped with no static Aters at the ABSS in Disabled-Unlocked-No Validation state.这个告警的原理参见前面。
*解决办法:删除CIC数据,重做二、AXCDR告警解释:动态分配要求在RXCDR和BSC中有逻辑设备来匹配两端对应的物理设备,并且进行Ater资源的分配。
在RXCDR中,这个逻辑设备是Associate RXCDR (AXCDR),BSC中是Associate BSS (ABSS),它们被RXCDR和BSC中的自动控制程序所控制,分别在两端的实际设备之间进行Ater资源的动态控制,The connection of the Ater circuits is achieved through interaction between the Allocation Manager process running under control of the Switch ManagerThe RXCDR failed to respond to repeated attempts by the BSC to initiate the CIC validation procedure.The affect of this failure is that CIC validation is not performed between the BSC and the RXCDR for the affected RXCDR. All CICs connected to the affected RXCDR are blocked.*可能的原因:The RXCDR has not been upgraded to a software release that supports CIC validation.*解决办法:首先关掉BSC的CIC确认参数;然后将RXCDR升级到能支持CIC确认;三、BCUP告警NONE系统监测到一个软件进程错误for BSP。
这是一个Intermittent告警。
The BSP detected a TDM Clock A failure。
如果故障是在CBUS,那么CBUS将OOS,否则BSP 就将倒换到备用的时钟。
如果备用的时钟无法倒换,那么内部的时钟提取将失败,并导致SITE OOS。
*可能的原因:KSWX A板挂了GPROC板件中的时钟接收电路坏了光纤连接有问题*解决办法:1、如果站挂了,那么更换CLOCK A GCLK板。
2、如果站是B_U,那么看看同一CAGE有无其他设备有Clock A Signal Loss和6.12 Second Reference Lo ss告警,如果只有BSP有时钟告警,则更换BSP,如果有50%的设备有时钟告警(此时有CBUS 0号告警Over 50% of Boards Detected Clock Failure告警),那么就倒换到GCLK备边看看,如果还是只有BSP有时钟告警,则更换BSP,如果还是有50%的设备有时钟告警(此时有CBUS 0号告警Over 50% of BoardsGCLK。
倒换GCLK备边时,BSC会RESET。
该告警与30号告警一样,只是现在BSP用的是哪一个GCLK(A/B)的信号。
BSP(主用与备用)之间的LAN连接失败。
BSP就挂了,如果是主用的BSP,那么SITE 就挂了。
*可能的原因:1、BSP复位了,或者由于软件复位,或者前面板人为复位2、GPROC(BSP)坏了BSP检测到一个软件故障(SWFM)。
如果只有一块BSP,那么SITE将RESET,如果有备用BSP,就倒换了。
BSP在BSC和RXCDR中都只能用GPROC2或GPROC3,如果插入一块GPROC作BSP无法占用为他指定的TDM时隙。
*可能的原因:GPROC(BSP)板坏了软件错误倒换TDM总线时出现该问题BSP程序自检失败。
(GPROC板的负荷(cpu_usage_mean)过高,可能会产生239号告警:“Process Safe test Audit Failure”(处理器自检失败),当BSP的CPU使用率达到100%,出现BSP[239]告警,BSC就会自动reset。
)*附加信息:*解决办法:1 如果附加信息为02,那么就人工做给板件一次Audit,命令如下:在MMI进入第二级,status_mode 0(BSC) on,alarm_mode 0 on,device_audit 0(bsc) safedevice device ID,给整个cage做Audit的命令是:cage_audit 0 safe cage no.。
可以做Audit的device包括:BSP GPROC SBUS BTP KSW TDM DHPMSI AXCDR DRI RXCDR2 如果为其他附加信息,则reset BSP,这样,SITE也reset了。
最后一条MTL断了,信令点码无法得到了。
此时BSS系统无法支持通话,或者发送消息至MSC。
一条MTL64Kbit/s。
MSC有协议错误。
当干线容量的利用率大于trunk_major_threshold这个BSC参数,但小于trunk_critical_threshold这个BSC参数时,就产生这个Major告警。
其实这个告警表示了退服的带CIC的MMS太多了。
*可能的原因:电路当前的利用率超过了trunk_major_threshold所设定的值,反过来讲,当干线容量的利用率大于trunk_critical_threshold这个BSC参数时,就产生这个Critical告警。
*可能的原因:电路当前的利用率超过了trunk_critical_threshold所设定的值,反过来讲,trunk_critical_threshold参数可能设置得太小了。