阿朗基站设备告警查看及命令操作

阿朗传输网管使用手册目录1 网管登陆 (1)2 当前告警查看 (2)3 拓扑查看： (3)4 光功率查询 (7)5 历史告警查询 (9)前言：鹰潭、吉安、景德镇PTN网络使用阿尔卡特传输设备，设备型号主要有1850TSS-320，1850TSS-160，1850TSS-5C和1850TSS-5R，后缀代表设备容量，比如：1850TSS-320代表设备最大支持320G的多速率交叉能力（相当于2048个155M）。

1850TSS-320和1850TSS-160主要用于汇聚层设备，1850TSS—5R主要用于接入层设备，带基站业务或宽带业务。

由于1850TSS-5C问题较多且容量不足，已逐渐升级成5R设备。

1 网管登陆1.1 通过安全管控平台登陆吉安PTN本地网。

1.2 点击弹出的网页界面，可进入登陆界面，输入正确的用户名和密码。

2.1 登陆成功后，选择左边菜单-》Operation-》Alarms，双击Gobal Alarms图标。

2.2 此时弹出告警浏览界面，监控主要关注MAJOR级别告警：Loss of Signal以及Hardware failure，点击左边树图中MAJOR栏，可选择查看MAJOR级别告警。

勾选掉菜单View-》Paginate sublist选项，可取消告警分页显示，提高告警查看效率。

若告警变成绿色表示告警已清除，若找不到此告警，表明告警已清除且被存入历时库，历史库中的告警需要登陆网元主页中查询，详见第5节。

由于告警查看界面无法关联到拓扑，要查看网络拓扑，需要启动Network Management服务，详见第3节。

3.1在登陆主界面中，选择左边菜单-》Operation-》Management，双击Network Management 图标。

3.2 根据告警信息，查找告警网元：选择菜单Search-》Physical-》Nodes，可以显示所有网元，按Location（区县）排序，可以找到对应网元，注意区分5R和5C设备。

如何查看基站所属地市Miscellaneous Applications=>OMP Shell=>apxrcv=>start=>rDialing Class 10Processor Type cLogical Number 站号按<回退查看基站硬件设备op:cell 基站号,inventory查看基站版本op:cell x,generic激活版本init：cell xxx：sc查看AP下挂几个站op:ap *,status抓Rop日志hf5omp root> cd /omp-data/logs/OMPROP1 (主要查看HEH硬件告警和ALARM 隐性告警)hf5omp root> lshf5omp root> cgrep +-w# "CELL 226 (此处有空格)" 110503.APX(大小写要注意) hf5omp root>cat 日期文件|cgrep –R “CELL XXX|RCS XXX”如何抓取已经被打过包的基站ROPgzcat 110106.APX.gz | cgrep +w# "CELL 905 " （gzcat *.APX.gz | cgrep +w#"CELL XXX"）查看传输误码如果传输显示mino次要告警，查看是否有误码(误码会造成基站瞬断)，如下DO: exc:cell 816,cdm 2,ds1 1,report 1(第1路)exc:cell 816,cdm 2,ds1 2,report 1exc:cell 816,cdm 2,ds1 3,report 11X: exc:cell 816,cdm 1,ds1 1,report 1(注明：第1行表示15m内，第2行表示24h) exc:cell 816,cdm 1,ds1 1,report 3(注明：每隔15分钟刷一次数据，一共24h) 清除误码：exc:cell 816,cdm 1,ds1 1,clear查看底噪dump:cell 851;plm 10;carrier 1,sector 1（1为扇区）将软件下载到基站send:cell 345,generic "F2605DDGA.00"查看基站是否阻塞sy2omp omptech> /omp/bin/SMsmdump -C 2 -H 9 -t >smdump2.txt sy2omp omptech> more smdump2.txt如何屏蔽分集接收告警Miscellaneous Applications=>OMP Shell=>apxrcv=>ceqface=>uNumber基站号/ Physical Antenna Face扇区号26Receive Diversity Equipped改为n:C2012n提取话务信息Miscellaneous Applications->OMP Shellcd /home/root/sm/smart32.1a/outputlssz 日志编号(默认存储到C盘根目录下)查看某个载扇的功率配置Miscellaneous Applications->OMP Shell =>apxrcv=>btseqpr21查看邻区Miscellaneous Applications->OMP Shell =>apxrcv=>fcir15/16查看PN配置Miscellaneous Applications->OMP Shell =>apxrcv=>ceqface8查看1X占用第几路传输Miscellaneous Applications->OMP Shell=>apxrcv=>btseqpr2判断分集接收是否失衡bb1omp TICLI 16>op:cell 851,cdm 1,cbr 1 rssi (仅适于4.0基站)如何做拨打测试op: dn “电话号码”op:cbr/mcr xxx,cdm xxx定位跟踪op: ctrc；dn “电话号码”查看所有基站的告警op:alarm,all在VLR中是否注册APXRCV-VLR 在第5列输入手机号码回车回车就行了重启、初始化和拉下基站restart:rcs # 重启RCS #rmv:rcs # 落下基站init:cell #:sc 初始化基站#对URC/URC-II 的操作rst：cell #，cdm 1，crc；ucl 重启1X主控板；rmv：cell #，cdm 1，crc；ucl 拉下1X主控板；rst：cell #，cdm 2，crc；ucl 重启DO主控板；rmv：cell #，cdm 2，crc；ucl 拉下DO主控板；对CBR/UCR/MCR的操作rmv：cell #，cdm 1，cbr #；ucl 拉下射频板；rst：cell #，cdm 1，cbr #；ucl 重启射频板；dump:cell #:mra 查看状态对CCU/CMU的操作rst：cell 953，cdm 1，ccu #；ucl 重启1X信道板；rmv：cell #，cdm 1，ccu #；ucl 拉下1X信道板；rst：cell 953，cdm 2，ccu 2；ucl 重启DO信道板；rmv：cell #，cdm 2，ccu #；ucl 拉下DO信道板；对功放的操作rst：cell 小区号，asmb 1，txamp #；ucl 重启第#块功放rmv：cell 小区号，asmb 1，txamp #；ucl 拉下第#块功放查看其他命令的执行：dump:cell #:mra对TFU/CTU的操作rmv:cell #,tfu 1;ucl 拉下TFU/CTUrst:cell #,tfu:gps 1;ucl 强制抓星查看/更改信道板配置Miscellaneous Applications->OMP Shell=>apxrcv=>btseqp（4.0/4400）/cdmeqp(MOD站)14页/2页工程状态改eMiscellaneous Applications->OMP Shell=>apxrcv=>cell2Enter Update, Change, Validate, screen#, or Print:c定位op:ctrc;dn"电话号码"RCV表CELL24页(104)基站软件版本信息；31页BHS信息;35页Backhaul Enabled CMODEQP1页(2)C4.0是1bts_mod；MODCELL是flex_mod;1页(3或4)主备用AP5页TFU信息;6页filter信息;7页功放信息CEQFACE1页定义扇区;1页(111)第一个扇区的PN值;24页导频寻呼同步增益41页网络IDBTSEQP1页Assemblage Number URC号，背板SN号;2页1X占用几路传输;7页DO占用几路传输;14页1X信道板配置;15页DO信道板配置;20页定义滤波; 21页定义载频射频功率衰减(查看功率);FCI 15页定义邻区START 1页查询基站归属地ECPCDMEQP2页射频板配置;3页基站传输配置; 7页定义CBR;8页定义滤波器CELL2>CMODEQP>CEQFACE>BTSEQP> FCI>START>ECP 基站类型C4.0/4400 CELL2>CMODEQP>CEQFACE>CDMEQP> >FCI>START>ECP 基站类型MD1.0&2.0/C3.0 一、基站开通准备各种参数收集、确认基站数据包括基站RCS号：（RCS：Radio Cluster Servers），基站所属的AP（Application Process），基站在AP上占用的时隙，基站例行诊断和呼叫处理所使用的软件版本，基站的配置以及各个扇区的PN（Preamble Number）码，基站的其他功能控制参数。

RNC侧常用命令：LST TNODEB查询NodeBLST TCELL查询小区DSP TCELL查询小区状态DSP TCARRIER查询载频状态LST TCARRIER查询载频配置LST OPT查询光口属性DSP E1T1查询E1/T1端口状态LST IMALNK查询IMA链路的配置DSP IMALNK查询IMA链路状态PING IP Ping对端IP地址NODEB侧常用命令：LST ALMAF查询活动告警LST ALMLOG查询告警日志LST NODEBSTATUS查询物理NodeB状态DSP LOCELL查询本地小区设备状态LST LOCELL询本地小区设备配置信息DSP CARRIERRES查询载波资源状态DSP RRU查询RRU状态LST RRU查询RRU配置信息DSP GPS查询GPS状态LST GPS查询GPS配置信息DSP CLKSRC查询参考时钟源状态DSP CLKRECORD查询时钟历史状态DSP BRD查询单板状态LST BRD查询单板配置信息LST SOFTWARE查询软件版本(DSP BRDVER查询单板版本信息DSP OPINFO查询光模块状态DSP RRUPARA查询RRU参数状态（驻波）DSP PATHPARA查询PATHPARA状态（所有通道驻波）TRG PATHVSWR驻波比扫频测量DSP PATH查询PATH状态DSP OMCH查询远端维护通道状态LST OMCH查询远端维护通道配置信息DSP BRDMFRINFO查询单板制造信息LST ANTENNA查询天线配置信息LST PORT查询光口速率配置信息DSP PORT查询PORT状态LST NTPC查询NTP客户端信息LST E1T1查询E1/T1端口配置信息DSP E1T1查询E1/T1端口状态LST VLANCLASS查询VLAN优先级映射配置信息LST VLANMAP查询下一跳VLAN映射配置信息LST IMALNK查询IMA链路配置信息DSP IMALNK查询IMA链路状态PING Ping命令RST SYS复位基站可能会引起断站RST BRD复位单板可能会引起断站RST BRDPWROFF下电复位单板可能会引起断站RST RRU复位RRU可能会引起断站RST SATCARD复位星卡可能会引起基站退服。

一、每日维护介绍1. 查看基站告警。

在ECP Control & Display界面输入以下命令：（其中c为RCS，n为CDM，x为CCU，d为DCS，t为TRKGRP）2121 显示所有基站的状态2131，c 显示基站c的状态，Signaling Link以及AP／RCS等2136，c 显示基站c的TFU，GPS，AMP状态2138，c，n 显示基站c，模块n的状态，包括CRC，CBR，Packet Pipe等2139，c，n，x 显示基站c，模块n，CCU盘 x 的状态2152，d，t 显示基站t的Packet Pipe Trunk Group状态，现在RCS号和Trunk Group号设为相同。

2100 命令索引。

在ECP Craft Shell界面输入以下命令：OP:CELL a 输出基站的状态OP:ALARM 输出详细的告警2. 当基站的某个机盘发生告警时。

可以在ECP Craft Shell界面输入以下命令对某个机盘进行恢复：∙对MODCELL：RST:CELL a, TFU b [;UCL]RST:CELL a, ULAM b [;UCL]RST:CELL a, CDM b, CBR c [;UCL]RST:CELL a, CDM b, CCU c [;UCL]RST:CELL a, CDM b, CRC [;UCL]∙对CDBS：RST:CELL a, BBU b, TFU [;UCL]RST:CELL a, BBU b, PCBR c，MMA [;UCL] /RST:CELL a, BBU b, PCBR c [;UCL]RST:CELL a, BBU b, CCU c [;UCL]RST:CELL a, BBU b, CRC [;UCL]其中加[;UCL]的选项表示unconditional，不加表示conditional。

它们的区别是：conditional restore会先对机盘进行diagnose，然后进行restore；而unconditional restore则直接进行restore。

阿尔卡特-朗讯基站维护指导书第一部分 阿尔卡特朗讯基站简介一、基站 1、基站外观和2、板件图解（1）FIT ：提供120欧姆传输接口，该传输接口盘上端有两个螺丝，拧开后可以打开，提供卡线接口。

（2）PDA ：电源接口盘，提供-48V 电源熔断器接口，通过熔断器控制各个电路板的电源供给。

每个熔断器具体给哪个板件供电，在PDA 面板上都有标注12345 6 7891012（3）Filter：Tx/Rx滤波器，接收路径集成了Rx低噪音放大器。

Modcell系列基站的Filter分为A1、A2两种，其中A1滤波器在分给CDMA的频段上可实现双工滤波功能，A2滤波器在CDMA频段上职能实现单工滤波，因此A1、A2滤波器不能互换。

（4）Smart Switch:晶振职能切换器。

该器件实现OM1、OM2的无缝职能切换（5）Amplifier Fan：放大器风扇（6）ULAM OR A-CmLAM：放大器。

Modcell系列基站支持ULAM和A-CmLAM，但是ULAM、A-CmLAM不能混用，也就是一个基站要么都使用ULAM，要么都使用A-CmLAM（7）UIP：功放接口面板（8）Digital Fan：数字单元风扇（9）CDM：CDMA数字单元模块（10）OM：晶体振荡器（11）RMP：远端维护面板（12）TFU: 时钟&频率单元3、CDM数字单元模块简介（使用 CDM图片）Launch Microsoft Office Outlook.lnk对于基站每个CDM都支持一个载频，图中CDM F1只CDM 1也就是1载频。

4、每个板件的正下方都标有板件名称及板件序列号，更换时请注意不要插错槽位5、CTRM是可选项目前所有Modcell系列基站都没有配置6、宽带配置是支持EV-DO的插槽，因耗电因素目前Modcell基站已经不建议扩展为EV-DO二、基站简介1、基站外观三、基站简介1、基站外观四、&基站差异1、& PDA差异：基站利用开关控制电源通断，基站通过插拔熔断器方式控制电源通断。

阿朗传输网管使用手册VHUA system office room 【HUA16H-TTMS2A-HUAS8Q8-HUAH1688】阿朗传输网管使用手册目录1 网管登陆 (1)2 当前告警查看 (2)3 拓扑查看： (3)4 光功率查询 (7)5 历史告警查询 (9)前言：鹰潭、吉安、景德镇PTN网络使用阿尔卡特传输设备，设备型号主要有1850TSS-320，1850TSS-160，1850TSS-5C和1850TSS-5R，后缀代表设备容量，比如：1850TSS-320代表设备最大支持320G的多速率交叉能力（相当于2048个155M）。

1850TSS-320和1850TSS-160主要用于汇聚层设备，1850TSS—5R主要用于接入层设备，带基站业务或宽带业务。

由于1850TSS-5C问题较多且容量不足，已逐渐升级成5R设备。

1 网管登陆1.1 通过安全管控平台登陆吉安PTN本地网。

1.2 点击弹出的网页界面，可进入登陆界面，输入正确的用户名和密码。

2 当前告警查看2.1 登陆成功后，选择左边菜单-》Operation-》Alarms，双击Gobal Alarms图标。

2.2 此时弹出告警浏览界面，监控主要关注MAJOR级别告警：Loss of Signal以及Hardware failure，点击左边树图中MAJOR栏，可选择查看MAJOR级别告警。

勾选掉菜单View-》Paginate sublist选项，可取消告警分页显示，提高告警查看效率。

若告警变成绿色表示告警已清除，若找不到此告警，表明告警已清除且被存入历时库，历史库中的告警需要登陆网元主页中查询，详见第5节。

由于告警查看界面无法关联到拓扑，要查看网络拓扑，需要启动Network Management服务，详见第3节。

3 拓扑查看：3.1在登陆主界面中，选择左边菜单-》Operation-》Management，双击Network Management图标。

阿朗常用命令集锦故障用SN码查询槽口位置:show equipment ont interface | match exact:f2b136bc阿卡设备查看语音具体配置信息（这条命令改成已做过对应IP段的端、槽、口就可以查语音网关和掩码）：info configure voice ont service 1/1/8/7/6/1info configure bridge port 1/1/1/9/25/voip 查看绑定的ip地址info configure voice ont service 1/1/1/9/25/1 查看语音具体配置信息info configure bridge port 1/1/1/9/25/1/1 查看vlanshow vlan bridge-port-fdb 1/1/1/9/25/1/1 查看用户macshow service fdb-mac （查找上联MAC)show vlan bridge-port-fdb 1/1/1/9/254/voipshow equipment ont optics 1/1/1/9/25 查看光功率info configure service 查看是否拓传VLANinfo configure bridge port flat 查看所有IPshow equipment ont sw-version 查看版本型号configure pon interface 1/1/2/3 admin-state downconfigure pon interface 1/1/2/3 admin-state up (重启pon口）admin equipment slot lt:1/1/2 reboot with-selftest 重启PON板show pon optics(查看板卡的光）show equipment temperature 查看温度查看光功率show equipment ont optics查看MAC show vlan bridge-port-fdb查看VLAN info configure service查看单个ONT VLAN info configure bridge port查看办卡状态show equipment slot查型号show equipment ont interface 1/1/1/9/25 detail查状态show interface port | match exact:1/1/8/1/14查vlan创建show vlan fdbid | match exact:615查已用vlan info configure bridge | match exact:3001查看OLT版本号show software-mngt oswp查看主备主控板那个主用show equipment protection-elementadmin equipment ont interface 1/1/4/8/12 reboot with-active-image 重启光猫阿卡：查状态show interface port | match exact:1/1/1/9/25uni:1/1/8/7/17/1/1 up up voip:1/1/8/7/17 up up bridge-port:1/1/8/7/17/1/1 not-appl upvlan-port:1/1/8/7/17/1/1:624 up up ont:1/1/8/7/17 up up 此两项都是up表示通了查型号show equipment ont interface 1/1/4/6/22 detail更换光猫configure equipment ont interface 1/1/1/9/25 admin-state downconfigure equipment ont interface 1/1/1/9/25 sernum ALCL:F2C9ECD2configure equipment ont interface 1/1/1/9/25 admin-state up强制更换ONT版本号configure equipment ont interface 1/1/1/9/25 admin-state downconfigure equipment ont interface 1/1/1/9/25 sw-ver-pland 3FE54377BOCI06 configure equipment ont interface 1/1/1/9/25 admin-state upWriting configuration to /pub/IPD/dm/config.cfg ?Received Dying Gasp indication from ONT 接到指示ONT垂死挣扎。

S022CNMetropolis® ADM Universal城域系列通用型分插复用器操作与维护课程故障排除手册版本 5.0S022CN-5.0-AMTCG.zh.A4第1版2006年4月朗讯科技 – 专利产品本文件含有朗讯科技的专利信息未经许可不得披露或使用版权所有 © 2005 朗讯科技非公开出版物保留所有权利朗讯科技（中国）客户培训中心本故障排障手册是参考Metropolis® ADM Universal 系统软件版本5.0(R5.0)。

为方便使用本手册，除告警条目保留原文(英文)外，其他均已译成中文，供学员参考。

其中告警严重等级和告警类别的说明如下：SDH告警严重等级：Prompt 紧急Deffer 延迟Information 信息告警类别Transmission<传输> 关于传输、定时的告警Equipment<设备> 关于单元盘、电源、风扇及配置的告警Processing<处理> 关于软件故障、重启动等告警Quality of service<业务质量> 关于性能监测的告警Environment<环境> 关于环境的告警Management<管理> 关于网管管理的告警序号告警名称1.1GEcANM; 1Gigabit Ethernet interface Auto Negotiation Mismatch (1)2.1GEcLOS; 1Gigabit Ethernet interface Loss of input signal (1)3.1GEcNES; 1Gigabit Ethernet interface Not expected input signal (1)4.E11cLOS; 1.5 Mbit/s Loss of input signal (1)5.E11cNES; 1.5 Mbit/s interface Not expected input signal (2)6.P11OTMcSW; 1.5 Mbit/s output timing mode change (2)7.P12ScAIS; 2Mbit/s Alarm indication signal received (2)8.E12cLOS; 2M bit/s Loss of input signal (2)9.P12ScLOFM; 2Mbit/s Loss of frame alignment (3)10.P12cDEG; 2Mbit/s Moderate block error rate (3)11.P12ScNCM; 2Mbit/s No CRC4 Multiframe alignment signal (3)12.E12cNESM; 2Mbit/s Not expected input signal (4)13.P12OTMcSW; 2 Mbit/s output timing mode change (4)14.P12ScRDI; 2Mbit/s Remote defect indicator (4)15.P12cRNCM; 2Mbit/s Remote No CRC-4 Multiframe alignment signal (4)16.E31cAIS; 34 Mbit/s AIS (5)17.E31cLOS; 34 Mbit/s Loss of input signal (5)18.E31cNES; 34 Mbit/s Not expected input signal (5)19.E32cLOS; 45 Mbit/s Loss of input signal (5)20.E32cNES; 45 Mbit/s Not expected input signal (6)21.E4cLOS; 140 Mbit/s Loss of input signal (6)22.E4cNES; 140 Mbit/s Not expected input signal (6)23.ALMcINH; Alarming inhibited (7)24.AU3cAIS; AU-3 Alarm indication signal received (7)25.AU3cLOP; AU-3 Loss of pointer (7)26.AUcAIS; AU-4 Alarm indication signal received (7)27.AUcLOP; AU-4 Loss of pointer (8)28.AU4cAISC; AU-4-4c Alarm indication signal received (8)29.AU4cLOPC; AU-4-4c Loss of pointer (8)30.AU16cAISC; AU-4-16c Alarm indication signal received (8)31.AU16cLOPC; AU-4-16c Loss of pointer (9)32.BCLANcUPF; BC LAN failure (9)33.OBALSRcFLR; Booster amplifier laser failure (9)34.VC4cPPE; Circuit provisioning error (9)35.UPcRST; CP reset in progress (10)36.XCCcINC; Cross-connect inconsistency (10)cUPF; Cross connect unit failure (10)cEQF; Cross connect unit failure - protected (10)cUNI; Cross connect Unit removed (10)40.DCNTAPcCONF; DCN-Tunnel auto provisioning configuration error (11)41.DS3cDEG; DS3 Line BER degraded (11)42.TIDcFLR; Duplicate node name (11)43.EMACcLOF; Encapsulated-MAC loss of frame alignment (11)NcANM; Ethernet interface Auto negotiation mismatch (12)NcLOS; Ethernet interface Loss of input signal (12)NcNES; Ethernet interface Not expected input signal (12)47.ATPcPRM; Extra traffic preempted (12)48.FANcFANX; Fan unit failure (13)49.FANcPWR; Fan unit power failure (13)50.FANcUNI; Fan unit removed (13)51.BAUcTYM; From backplane received AU-type does not match expected AU-type (13)52.GEcPLL; GBE Local Link Aggregation partial link loss (13)53.GEcTLL; GBE Local Link Aggregation total link loss (14)54.I2CcUPF; I2C-bus failure (14)55.INTCOMcRPF; Internal comunication interface fault protected (14)56.POWc1LS; Input voltage failure on PSU (15)57.DCNcCONF; IS-IS configuration error (15)58.DCNcREPAIR; IS-IS Level-2 Area repair, transmission/configuration error (15)NDPcTHR15; LAN Dropped packets threshold crossing 15-min (15)NDPcTHR24; LAN Dropped packets threshold crossing 24-hrs (15)61.IPcUPF; LAN unit failure (16)62.IPcEQF; LAN unit failure - protected (16)63.IPcUNI; LAN Unit removed (16)64.LSRcEDG; Laser degradation (16)65.LSRcFLR; Laser failure (17)66.MLQ2; Loss of Q2-communication (17)67.POWcLSV; Loss of secondary input voltage (17)68.DCNBUcLOST; Mandatory IS-IS parameters missing (18)69.MACcVLANOVFW; Maximum number of VLAN instances exceeded (18)70.MDcIPX; MDI #X :< 用户输入名> (18)71.MS16cLIVm; MS-16 Ring comm. server network address protocol failure/version mismatch1872.NIDcFLR; Node ID conflict (18)73.NUTRcPND; Non-preemptable unprotected traffic switch request pending (19)74.SYSMEMcNVM; NVM contents invalid (19)75.P12SNBBEcTHR15; P12s Near-end background block error thresh cross 15-min (19)76.P12SNBBEcTHR24; P12s Near-end background block error thresh cross 24-hrs (19)77.P12sNEScTHR15; P12s Near-end errored seconds threshold crossing 15-min (19)78.P12sCNEScTHR24; P12s Near-end errored seconds threshold crossing 24-hrs (20)79.P12sCNSEScTHR15; VC-4-4c Near-end severely ES threshold crossing 15-min (20)80.P12sCNSEScTHR24; P12s Near-end severely ES threshold crossing 24-hrs (20)81.P12SCNUAScTHR15; P12s Near-end unavailable seconds threshold crossing 15-min (20)82.P12SCNUAScTHR24; P12s Near-end unavailable seconds threshold crossing 24-hrs (20)83.PBcUPF; Paddle board failure (21)84.PBcEQF; Paddle board failure - protected (21)85.PBcUNI; Paddle board removed (21)86.VC4HPcPAF; Path integrity failure (21)87.PIcUPF; Plesiochronous Interface Unit failure (21)88.PIcEQF; Plesiochronous Interface Unit failure- protected (22)89.PIcUNI; Plesiochronous Interface Unit removed (22)90.PMcUPF; Pluggable Module failure (22)91.PMcEQF; Pluggable Module failure - protected (22)92.PMcUNI; Pluggable Module removed (23)93.PUcUPF; Power Unit failure (23)94.PUcEQF; Power Unit failure - protected (23)95.PUcUNI; Power Unit removed (23)96.PSUc1EQ; PSU failure (24)97.PSFcEQR; PSF removed (24)NcTRM; Q-LAN termination loopback failed (24)99.POWcBAT; Racktop battery failure (24)100.POWcFUS; Racktop fuse failure (25)101.AU4cTYM; Received AU-type does not match expected type AU4 (25)102.RGU16EQF; Regenerator failure (25)103.RGU16cDEG; Regenerator laser degradation (25)104.RGU16cEQR; Regenerator removed (25)105.RINGcOPEN; Ring incomplete/open (26)106.RINGcSTART; Ring startup in progress (26)107.RS16cLIVm; RS-16 Ring comm.server network address protocol failure/version mismatch (26)108.SCTcUPF; SCT Unit failure (26)109.SITEcPROV; Site provisioning conflict (27)110.SFTWcDWN; Software download in progress (27)111.SQcSUS; Squelch map update suspended (27)112.DISCON; Station alarms disconnected (27)113.MTcAIS; Station clock input alarm indication signal (28)114.MTcLOF; Station clock input Loss of frame alignment (28)115.MTcLOS; Station clock input Loss of signal (28)116.MTcNES; Station clock input Not expected signal (28)117.TSCOcSQ; Station clock output squelched (29)118.STMNcLOF; STM-N Loss of frame alignment (N=1， 4， 16，64) (29)119.STMNcLOS; STM-N Loss of input signal (N=1， 4， 16，64) (29)120.MS1cAIS; STM-N MS Alarm indication signal received (N=1， 4， 16，64) (30)121.MS1cBDEG; STM-N MS Moderate block error rate (N=1， 4， 16，64) (30)122.MS1NBBDEcTHR15; STM-N MS Near-end background block error thresh cross 15-min (N=1，4，16，64) (30)123.MS1NBBEcTHR24; STM-N MS Near-end background block error thresh cross 24-hrs (N=1，4，16，64) (30)124.MS1NEScTHR15; STM-N MS Near-end errored seconds threshold crossing 15-min (N=1，4， 16，64) (31)125.MS1NEScTHR24; STM-N MS Near-end errored seconds threshold crossing 24-hrs (N=1，4，16，64) (31)126.MS1NSEScTHR15; STM-N MS Near-end severely ES threshold crossing 15-min (N=1，4，16，64) (31)127.MS1NEScTHR24; STM-N MS Near-end severely ES threshold crossing 24-hrs (N=1， 4，16，64) (31)128.MS1NUAScTHR15; STM-N MS Near-end unavailable seconds threshold crossing 15-min (N=1， 4， 16，64) (31)129.MS1NUAScTHR24; STM-N MS Near-end unavailable seconds threshold crossing 24-hrs (N=1， 4， 16，64) (32)130.MS1cSSF; STM-N MS Network connection unavailable (N=1， 4， 16，64) (32)131.MS1cFOP; STM-N MS Protection switching protocol failure (N=1， 4， 16，64) (32)132.MS1cREM; STM-N MS Remote Defect Indicator (N=1， 4， 16，64) (33)133.STMNcNES; STM-N Not expected input signal (N=1， 4， 16，64) (33)134.RS1cTIM; STM-N RS trace identifier mismatch (N=1， 4， 16，64) (33)135.LTX16cALS; STM-16 ALS disabled (33)136.MS-NcBYF; STM-N APS byte failure (N-16, 64) (34)137.MS-NcCHF; STM-N APS channel failure (N-16, 64) (34)138.REG16CONcFLR; STM-16 fault locate fails (34)139.MS-NcFIC; STM-N Fiber connection conflict (N-16, 64) (34)140.MS16cLSROFF; STM-16 Laser switched off (35)141.STM-NcPLOS; STM-N LOS and restart pulse detected (N-16, 64) (35)142.STM-NcPLOSP; STM-N LOS and restart pulse detected – protected (N-16, 64) (35)143.STM-NcLOFP; STM-N Loss of frame alignment – protected (N-16, 64) (35)144.STM-NcLOSP; STM-N Loss of input signal- protected (N-16, 64) (36)145.STM-NcDEG; STM-N RS Moderate bit error rate (N-16, 64) (36)146.RS-N NBBEcTHR15; STM-N RS Near-end background block error thresh cross 15-min (N-16,64) (36)147.RS-N NBBEcTHR24; STM-N RS Near-end background block error thresh cross 24-hrs (N-16,64) (36)148.RS-N NEScTHR15; STM-N RS Near-end errored seconds threshold crossing 15-min (N-16, 64) (37)149.RS-N NEScTHR24; STM-N RS Near-end errored seconds threshold crossing 24-hrs (N-16, 64) (37)150.RS-N NSEScTHR15; STM-N RS Near-end severely ES threshold crossing 15-min (N-16, 64)37 151.RS-N NSEScTHR24; STM-N RS Near-end severely ES threshold crossing 24-hrs (N-16, 64).37 152.RS-N NUAScTHR15; STM-N RS Near-end unavailable seconds threshold crossing 15-min (N-16, 64) (37)153.RS-N NUAScTHR24; STM-N RS Near-end unavailable seconds threshold crossing 24-hrs (N-16, 64) (38)154.RS-NcTIM; STM-N RS trace identifier mismatch (N-16, 64) (38)155.SYSMEMcSWM; SW version mismatch (38)156.SIcUPF; Synchronous interface unit failure (38)157.SIcEQF; Synchronous interface unit failure - protected (39)158.SIcUNI; Synchronous interface unit removed (39)159.SCcEQF; System controller failure (39)160.TBACKcUPM; System timing in backup state (39)161.SYScALMT; Test station alarms (40)162.TLINKcFLR; Timing link failed (40)163.TLINKcUNEQ; Timing link unequipped (40)164.STM-NcTTD; Trace tone detected (N-16, 64) (40)165.SQcAIS; Traffic squelched (40)166.TUcAIS; TU-12 Alarm indication signal received (41)167.TUcLOP; TU-12 Loss of pointer (41)168.TU3cAIS; TU-3 Alarm indication signal received (41)169.TU3cLOP; TU-3 Loss of pointer (41)170.VC3NBBEcTHR15; TU-3 Near-end background block errors thresh cross 15-min (42)171.VC3NBBEcTHR24; TU3 Near-end background block errors thresh cross 24-hrs (42)172.VC3NEScTHR15; TU-3 Near-end errored seconds threshold crossing 15-min (42)173.VC3NEScTHR24; TU-3 Near-end errored seconds threshold crossing 24-hrs (42)174.VC3NSEScTHR15; TU-3 Near-end severely ES threshold crossing 15-min (42)175.VC3NSEScTHR24; TU-3 Near-end severely ES threshold crossing 24-hrs (43)176.VC3NUAScTHR15; TU-3 Near-end unavailable seconds threshold crossing 15-min (43)177.VC3NUAScTHR24; TU-3 Near-end unavailable seconds threshold crossing 24-hrs (43)178.VC12NBBEcTHR15; TU-12 Near-end background block errors threshold crossing 15-min (43)179.VC12NBBEcTHR24; TU-12 Near-end background block errors threshold crossing 24-hrs (43)180.VC12NEScTHR15; TU-12 Near-end errored second threshold crossing 15-min (44)181.VC12NEScTHR24; TU-12 Near-end errored second threshold crossing 24-hrs (44)182.VC12NSEScTHR15; TU-12 Near-end severely ES threshold crossing 15-min (44)183.VC12NSEScTHR24; TU-12 Near-end severely ES threshold crossing 24-hrs (44)184.VC12NUAScTHR15; TU-12 Near-end unavailable seconds threshold crossing 15-min (44)185.VC12NUAScTHR24; TU-12 Near-end unavailable seconds threshold crossing 24-hrs (44)186.UNITcINIT; Unit in initialisation (45)187.UPUS; Unit present in unassigned slot (45)188.UPLcEQF; UPL failure (45)189.UPLcUPR; User Panel removed (45)190.VC11cDEG; VC-11 Moderate block error rate (46)191.VC11NBBEcTHR15; VC-11 Near-end background block errors thresh cross 15-min (46)192.VC11NBBEcTHR24; VC-11 Near-end background block errors thresh cross 24-hrs (46)193.VC11NEScTHR15; VC-11 Near-end errored seconds threshold crossing 15-min (46)194.VC11NEScTHR24; VC-11 Near-end errored seconds threshold crossing 24-hrs (46)195.VC11NSEScTHR15; VC-11 Near-end severely ES threshold crossing 15-min (47)196.VC11NSEScTHR24; VC-11 Near-end severely ES threshold crossing 24-hrs (47)197.VC11NUAScTHR15; VC-11 Near-end unavailable seconds threshold crossing 15-min (47)198.VC11NUAScTHR24; VC-11 Near-end unavailable seconds threshold crossing 24-hrs (47)199.VC11cSSF; VC-11 Network connection server signal fail (47)200.VC11cTIM; VC-11 Path trace identifier mismatch (48)201.VC11cPLM; VC-11 Payload mismatch (48)202.VC11cRDI; VC-11 Remote defect indicator (48)203.VC11cUNEQ; VC-11 Unequiped (48)204.VC12cBDEG; VC12 Moderate block error rate (48)205.VC12cSSF; VC-12 Network connection server signal fail (49)206.VC12NBBEcTHR15; VC-12 Near-end background block errors threshold crossing 15-min (49)207.VC12NBBEcTHR24; VC-12 Near-end background block errors threshold crossing 24-hrs (49)208.VC12NEScTHR15; VC-12 Near-end errored second threshold crossing 15-min (49)209.VC12NEScTHR24; VC-12 Near-end errored second threshold crossing 24-hrs (49)210.VC12NSEScTHR15; VC-12 Near-end severely ES threshold crossing 15-min (50)211.VC12NSEScTHR24; VC-12 Near-end severely ES threshold crossing 24-hrs (50)212.VC12NUAScTHR24; VC-12 Near-end unavailable seconds threshold crossing 15-min (50)213.VC12NUAScTHR24; VC-12 Near-end unavailable seconds threshold crossing 24-hrs (50)214.VC12cTIM; VC-12 Path trace identifier mismatch (50)215.VC12cPLM; VC-12 Payload mismatch (51)216.VC12cRDI; VC-12 Remote Defect Indicator (51)217.VC12cUNEQ; VC-12 Unequipped (51)218.VC12VcLOA; VC-12 Virtual concatenated Loss of alignment (51)219.VC12VcLOM; VC-12 Virtual concatenated Loss of multiframe (52)220.VC12VcSQM; VC-12 Virtual concatenated sequence mismatch (52)221.VC12cSSF; VC-12 Virtual concatenated server signal fail (52)222.VC3cDEG; VC-3 Moderate block error rate (52)223.VC3cSSF; VC-3 Network connection server signal fail (53)224.VC3NBBEcTHR15; VC-3 Near-end background block errors thresh cross 15-min (53)225.VC3NBBEcTHR24; VC-3 Near-end background block errors thresh cross 24-hrs (53)226.VC3NEScTHR15; VC-3 Near-end errored seconds threshold crossing 15-min (53)227.VC3NEScTHR24; VC-3 Near-end errored seconds threshold crossing 24-hrs (53)228.VC3NSEScTHR15; VC-3 Near-end severely ES threshold crossing 15-min (54)229.VC3NSEScTHR24; VC-3 Near-end severely ES threshold crossing 24-hrs (54)230.VC3NUAScTHR15; VC-3 Near-end unavailable seconds threshold crossing 15-min (54)231.VC3NUAScTHR24; VC-3 Near-end unavailable seconds threshold crossing 24-hrs (54)232.VC3cTIM; VC-3 Path trace identifier mismatch (54)233.VC3cPLM; VC-3 Payload mismatch (54)234.VC3cRDI; VC-3 Remote defect indicator (55)235.VC3cUNEQ; VC-3 Unequipped (55)236.VC3VcLOA; VC-3 Virtual concatenated Loss of alignment (55)237.VC3VcLOM; VC-3 Virtual concatenated Loss of multiframe (55)238.VC3VcSQM; VC-3 Virtual concatenated sequence mismatch (56)239.VC3VcSSF; VC-3 Virtual concatenated server signal fail (56)240.VC3VcFOPR; VC-3 Virtual concatenated failure of protocol received (56)241.VC3VcFOPT; VC-3 Virtual concatenated failure of protocol transmitted (56)242.VC3VcLOPC; VC-3 Virtual concatenated loss of partial capacity (57)243.VC3VcLOTO; VC-3 Virtual concatenated loss of total capacity (57)244.VC3VcSSD; VC-3 Virtual concatenated server signal degrade (57)245.VC4cLOM; VC-4 Loss of multiframe (57)246.VC4cDEG; VC4 Moderate block error rate (57)247.VC4cSSF; VC-4 Network connection server signal fail (58)248.VC4NBBEcTHR15; VC-4 Near-end background block errors threshold crossing 15-min (58)249.VC4NBBEcTHR24; VC-4 Near-end background block errors threshold crossing 24-hrs (58)250.VC4NEScTHR15; VC-4 Near-end errored second threshold crossing 15-min (58)251.VC4NEScTHR24; VC-4 Near-end errored second threshold crossing 24-hrs (58)252.VC4NSEScTHR15; VC-4 Near-end severely ES threshold crossing 15-min (59)253.VC4NSEScTHR24; VC-4 Near-end severely ES threshold crossing 24-hrs (59)254.VC4NUAScTHR24; VC-4 Near-end unavailable seconds threshold crossing 15-min (59)255.VC4NUAScTHR24; VC-4 Near-end unavailable seconds threshold crossing 24-hrs (59)256.VC4cTIM; VC-4 Path trace identifier mismatch (59)257.VC4cPLM; VC-4 Payload mismatch (60)258.VC4cRDI; VC-4 Remote defect indicator (60)259.VC4cUNEQ; VC-4 Unequiped (60)260.VC4VcFOPR; VC-4 Virtual concatenated failure of protocol received (60)261.VC4VcFOPT; VC-4 Virtual concatenated failure of protocol transmitted (61)262.VC4VcLOA; VC-4 Virtual concatenated Loss of alignment (61)263.VC4VcLOM; VC-4 Virtual concatenated Loss of multiframe (61)264.VC4VcLOPC; VC-4 Virtual concatenated loss of partial capacity (61)265.VC4VcLOTC; VC-4 Virtual concatenated loss of total capacity (61)266.VC4VcSQM; VC-4 Virtual concatenated sequence mismatch (62)267.VC4VcSSD; VC-4 Virtual concatenated server signal degrade (62)268.VC4cSSF; VC-4 Virtual concatenated server signal fail (62)269.VC4CcDEG; VC-4-4c Moderate block error rate (62)270.VC4CNBBEcTHR15; VC-4-4c Near-end background block errors thresh cross 15-min (63)271.VC4CNBBEcTHR24; VC-4-4c Near-end background block errors thresh cross 24-hrs (63)272.VC4CNEScTHR15; VC-4-4c Near-end errored seconds threshold crossing 15-min (63)273.VC4CNEScTHR24; VC-4-4c Near-end errored seconds threshold crossing 24-hrs (63)274.VC4CNSEScTHR15; VC-4-4c Near-end severely ES threshold crossing 15-min (63)275.VC4CNSEScTHR24; VC-4-4c Near-end severely ES threshold crossing 24-hrs (63)276.VC4CNUAScTHR15; VC-4-4c Near-end unavailable seconds threshold crossing 15-min (64)277.VC4CNUAScTHR24; VC-4-4c Near-end unavailable seconds threshold crossing 24-hrs (64)278.VC4CcTIM; VC-4-4c Path trace identifier mismatch (64)279.VC4CcRDI; VC-4-4c Remote defect indicator (64)280.VC4CcSSF; VC-4-4c server signal fail (65)281.VC4CcUNEQ; VC-4-4c Unequiped (65)282.VC16CcDEG; VC-4-16c Moderate block error rate (65)283.VC16CNBBEcTHR15; VC-4-16c Near-end background block errors thresh cross 15-min (65)284.VC16CNBBEcTHR24; VC-4-16c Near-end background block errors thresh cross 24-hrs (65)285.VC16CNEScTHR15; VC-4-16c Near-end errored seconds threshold crossing 15-min (66)286.VC16CNEScTHR24; VC-4-16c Near-end errored seconds threshold crossing 24-hrs (66)287.VC16CNSEScTHR15; VC-4-16c Near-end severely ES threshold crossing 15-min (66)288.VC16CNSEScTHR24; VC-4-16c Near-end severely ES threshold crossing 24-hrs (66)289.VC16CNUAScTHR15; VC-4-16c Near-end unavailable seconds threshold crossing 15-min (66)290.VC16CNUAScTHR24; VC-4-16c Near-end unavailable seconds threshold crossing 24-hrs (66)291.VC16CcTIM; VC-4-16c Path trace identifier mismatch (67)292.VC16CcRDI; VC-4-16c Remote defect indicator (67)293.VC16CcSSF; VC-4-16c server signal fail (67)294.VC16CcUNEQ; VC-4-16c Unequiped (67)295.MACcVCM; VLAN configuration mismatch (68)296.WANDPcTHR15; WAN Dropped packets threshold crossing 15-min (68)297.WANDPcTHR24; WAN Dropped packets threshold crossing 24-hrs (68)cWUP; Wrong CC present (68)299.IPcWUP; Wrong LAN unit present (68)300.FANcWFUP; Wrong or failed FAN unit present (69)301.PBcWUP; Wrong Paddle broad present (69)302.PIcWUP; Wrong Plesiochronous interface present (69)303.PMcWUP; Wrong Pluggable Module present (69)304.SIcWUP; Wrong Synchronous interface unit present (69)305.WUPcEQF; Wrong unit- protected (70)1.1GEcANM; 1Gigabit Ethernet interface Auto Negotiation Mismatch告警描述：检测到本地与远端以太网设备的应用技术不匹配。

开新站必加85数据-------rlclc：cell=，hrtrx=“”；（除bsc302的bsc用）rlclc：cell=“”，ahrtrx=“”；（bsc302用）在闭传输的时候，有时候删了传输闭不了，那是时隙还没有闭，用blodi：dev=rblt2-“”&&-“”；先把时隙给闭了，在用dtbli：dip=“”rbl2；闭传输。

一、查看指令查看小区状态rlstp:cell=””; active为开halted为未开查看载波状态rxcdp:mo=rxotg-“”;查看是否开跳频rlchp:cell=””;查小区站名rxtcp:mo=rxotg-“”;查看小区TG rxtcp:moty=rxotg,cell=””;查看告警rxmfp:mo=rxotg-“”,subord,faulty;查看时隙rxapp:mo=rxotg-“”;查看TG状态rxmsp:mo=rxotg-“”,subord;查看传输状态dtstp:dip=“”rbl2; dip号可以是多个，例1rbl2&2rbl2，或更多查看配置rxmfp:mo=rxocf-“”;查看EDGE rlbdp:cell=””;改EDGE数rlbdc:cell=””,chgr=1,numreqegpsbpc=””;查看频点rlcfp:cell=””;查看小区信道状态rlcrp:cell=””; 可以跟一个小区也可以跟all。

查看信道组rldgp:cell=””;查看小区定义参数rldep:cell=””; 如CGI、BSIC、BCCH、等查看监控告警rlslp：cell=””；测试时隙rxtei：mo=rxots-“”--“”--“”；查看邻区rlnrp:cell=””,cellr=all,nodata;查看t3212 rlsbp：cell=“”；激活小区的时候用查看功率rlcpp：cell=“”；查看话务量rrtpp:trapool=all ;Rllop:cell=" ";查看传输质量Dtqup：dip=“”；查看所在BSC下Rllap:lai=all；所有的小区二、操作指令dev查TG Rxmdp：moty=rxots，dev=rblt2-“”；DEV=传输*32+1消传输误码dtqsr：dip=all，unacc，sf，degr；消光纤误码tpqsr：sdip=""setm2，unacc，degr；关跳频rlchc:cell=””,chgr=0,hop=off;开跳频rlchc:cell=””,chgr=0,hop=on;屏蔽监控告警rlsle：cell=””;放开监控告警rlsli：cell=””;删除监控告警rlsle：cell=””,rem；激活小区Rlstc:cell=””,state=active;禁闭小区Rlstc：cell=””,state=halted;禁闭TG Rxbli ：mo=rxotg-“tg号”，force，subord；带出服务Rxese ：mo=rxotg-“tg号”，subord；带入服务Rxesi ：mo=rxotg-“tg号”，subord；放开TG Rxble ：mo=rxotg-“tg号”，subord；禁闭载波Rxbli ：mo= rxotrx-“tg号”-“载波号”，force，subord；带出服务Rxese ：mo=rxotrx-“tg号”-“载波号”，subord；带入服务Rxesi ：mo=rxotrx-“tg号”-“载波号”，subord；放开载波Rxble ：mo=rxotrx-“tg号”-“载波号”，subord；查看光纤lp tpcop：sdip=all；查看传输状态ntcop:snt=all;解光纤tpble：sdip=“”etm2，lp=“”；解传输dtble：dip=“”rbl2；闭传输dtbli：dip=“”rbl2；查看时隙状态stdep：dev=rblt2-“”；带入服务exdai：dev=rblt-“”&&-“”;解时隙blode：dev=rblt-“”&&-“”;改TG关联小区rxmsc：mo=rxotg-“”，rsite=“”；三、修改指令加频点rlcfi:cell=””,chgr=””,dchno=”对应的是要加增的频点”；减频点rlcfe:cell=””,chgr=0,dchno=”对应的是要删去的频点”；删小区rldee：cell=“”；删传输rxape:mo=rxotg-“”,dcp=all; 删除本TG下的所有传输Rxape:mo=rxotg-“”,dcp=””; 删除“”口的传输删小区告警rlsle：cell=“”，perm；删参数rxmoe：mo=rxotf-“”-“”修改参数rxmoc：定义参数rxmoi：四、删数据闭载波Rxbli：mo=rxotrx -“TG号”-“载波号”，subord，force；载波退出服务Rxese：mo=rxotrx -“TG号”-“载波号”，subord；删MO参数TS Rxmoe：mo=rxots -“TG号”-“载波号”-0&&-7；删MO参数RX Rxmoe：mo=rxorx -“TG号”-“载波号”；删MO数据TX Rxmoe：mo=rxotx -“TG号”-“载波号”；删MO数据TRX Rxmoe：mo=rxotrx -“TG号”-“载波号”五、对传输查看传输状态Dtstp：dip=“”rbl2；不顺利的话如果STATE状态是AIS说明本传输是断的，MBL表示传输没有解。

OMCR查看告警指导文档（ASB设备操作文档）MLL-V1版2009-10-20目录1、对指定基站基本状态进行查看 (3)2、常见告警类型分析 (6)2.1 CEM板告警 (6)2.2 CCM板告警 (7)2.3 RRH告警及如何批量查看告警 (8)2.3.1 RRH告警 (8)2.3.2 批量查看告警小区 (9)2.3.3 如何设置模板 (12)2.4 无RRH (17)2.5 驻波比告警 (18)2.6 逻辑小区未起 (19)2.7 脱管 (19)3、查看基站的历史告警 (21)4、几个可能无大影响的告警 (23)在OMC-R网管上查基站基本状态，常见状态类型有：OK、CEM板告警、CCM板告警、RRH告警、无RRH、驻波比告警、逻辑小区未起、脱管（俗称掉站）等。

另外，可通过设置条件，对告警小区进行批量筛选，及对问题点基站进行历史告警查询等。

下面会做详细介绍。

1、对指定基站基本状态进行查看a、登陆终端后，进入下面的界面：b、直接选File—>Find：c、出现如下界面后，输入需查看的基站名（必须是拼音，全部或部分均可）：d、点击“Find”，进入如下界面：选中一个目标，进入后为：如果要查看这个站的告警，选中该站右键单击，选“Equipment monitor”后进入如下界面：从上图可以看出，该站基本状态显示正常，无任何告警。

2、常见告警类型分析2.1 CEM板告警CEM板告警，如下所示：CEM板告警会导致该站三个小区无信号，这种情况需上站确认是CEM板坏了还是基站设备温度过高导致，是否需更换CEM板。

如果想要知道更详尽的解释可以选择有问题的告警后，右击选择Fault，再选择Show Alarms/Show Alarms in New Window进行查看。

完成上面的操作后会出现下面的对话框，可查看具体的告警原因。

（此时与进行批量筛选告警时的对话框一样，后面会讲到批量筛选告警。

）下图为CEM板告警的另一种状态，仍然会导致基站三个小区无信号：2.2 CCM板告警由于目前CCM板告警的基站较少，这里用其他的图替代，如下所示，黄色告警不影响各种业务的进行，若此处为红色告警，则可能为CCM板坏了，也可能是基站设备温度过高导致，需上站明确是否需更换CCM板，此时（CCM板红色告警）基站三个小区均无信号。

基站动环常见告警及处理FSU离线告警原因分析：1）信号差或不稳定；2）FSU设备掉电；3）无线模块硬件故障；4）FSU设备硬件故障；5）天线和无线模块连接中断，或天线丢失；6）流量卡被盗、欠费或故障。

处理办法：第一步检查供电：1）在运维监控系统检查离线站点是否有停电告警，判断是否现场停电；2）现场检查FSU指示灯不亮设备没有供电。

原因分析： FSU供电异常。

解决方案：1）检查整个基站是否停电，如停电则通知相关人员取电；2）检查FSU供电空开是否跳闸及通电线路是否正常。

第二步检查无线模块：检查无线模块指示灯都不亮或都常亮。

原因分析：无线模块供电异常或无线模块故障。

解决方案：1）无线模块供电故障，则检查给无线模块供电接线是否正常如正常，则用万用表测量给无线模块供电FSU输出端是否有12V，如没有则为FSU供电板问题，更换FSU供电板。

2）确认供电正常，则更换无线模块进行测试。

第三步FSU检查登陆FSU设备，点击设备诊断管理，若信号强度小于15，表明由信号弱引起。

解决方案：更换运营商无线模块或将天线外延（室内站放到室外，室外柜放到底部隐蔽区域或有外层保护情况下放到机柜顶部）开关电源告警1、交流输入频率过低1）原因分析：交流输入多为市电引入，出告警即市电频率超越门限告警，低于48Hz。

2）处理方法：将数字型万用表测试档位置于Hz档，再将两根表笔分别接入信号源两端，测量信号源频率值是否低于48Hz。

2、电池充电过流告警1）原因分析：当充电电流超过0.1C时可认为是过电流充电。

3、电池熔丝故障告警1）原因分析：蓄电池熔丝未连接牢固或检测线未检测到蓄电池熔丝2）处理方法：（1）检查蓄电池熔丝是否连接牢固（2）检查检测线是否和蓄电池熔丝良好接触（3）开关电源显示屏是否有熔丝告警提示（如果没有，可能是平台数据不更新导致，或者开关电源协议解析不正确）。

4、防雷器故障告警1）原因分析：防雷器本身出现破损等故障或防雷器未插紧2）处理方法：（1）防雷器本身出现破损等故障则需要更换防雷器（2）将防雷器插紧，保证接触良好（3）核实是否在交维测试时做的告警一直未消除。