【正文】 /276417 INFO:4 Command Successfully Completed REASON_CODE=No Reasonbvomcr4001663 disp bts182 status00166300007 COMMAND ACCEPTED CLICMD4424 020917 16:44:07 bvomcr4 OMCR27 330042/276592 INFO:1 Command Received and Accepted COMMAND=DISPLAY BTS182 STATUS [4425: New Connection (bvomcr4,IT_daemon,*,root,pid=810,optimised) ][4425: New IIoP Connection (bvomcr4:1620) ]DISPLAY BTS182 STATUS: | | | DEVSYNC | | | | | | | | | | Config |Calibration|Calibration|ISO RELATEDDEVICE |CBSC | STATUS | Data | Data | Sync | STATE ||||||BTS182 271 INS N/A N/A N/A UNLOCKED BTSSPAN1821 271 INS N/A N/A N/A N/A BTSSPAN1822 271 INS N/A N/A N/A N/A BTSSPAN1829 271 INS N/A N/A N/A N/A BTSSPAN18210 271 INS N/A N/A N/A N/A BTSLINK1821 271 INS N/A N/A N/A N/A BTSLINK1822 271 INS N/A N/A N/A N/A MGLI1821 271 INS_ACTIVE GOOD N/A N/A N/A MGLI1822 271 INS_STANDBY GOOD N/A N/A N/A MDM1821 271 INS N/A N/A N/A N/A CSM1821 271 INS_STANDBY GOOD N/A N/A N/A CSM1822 271 INS_ACTIVE GOOD N/A N/A N/A BBX1821 271 INS_ACTIVE GOOD GOOD GOOD KEYED BBX1822 271 INS_ACTIVE GOOD GOOD GOOD KEYED BBX1823 271 INS_ACTIVE GOOD GOOD GOOD KEYED BBX1824 271 INS_ACTIVE GOOD GOOD GOOD KEYED BBX1825 271 INS_ACTIVE GOOD GOOD GOOD KEYED BBX1826 271 INS_ACTIVE GOOD GOOD GOOD KEYED BBX1827 271 INS_ACTIVE GOOD GOOD GOOD KEYED BBX1828 271 INS_ACTIVE GOOD GOOD GOOD KEYED BBX1829 271 INS_ACTIVE GOOD GOOD GOOD KEYED BBX18210 271 INS_ACTIVE GOOD GOOD GOOD KEYED BBX18211 271 INS_ACTIVE GOOD GOOD GOOD KEYED BBX18212 271 INS_ACTIVE GOOD GOOD GOOD KEYED BBXR1821 271 INS_STANDBY GOOD GOOD GOOD DEKEYED MCC1821 271 INS GOOD N/A N/A N/A MCC1822 271 INS GOOD N/A N/A N/A MCC1823 271 INS GOOD N/A N/A N/A MCC1824 271 INS GOOD N/A N/A N/A MCC1825 271 INS GOOD N/A N/A N/A MCC1826 271 INS GOOD N/A N/A N/A MCC1827 271 INS GOOD N/A N/A N/A MCC1828 271 INS GOOD N/A N/A N/A MCC1829 271 INS GOOD N/A N/A N/A MCC18210 271 INS GOOD N/A N/A N/A MCC18211 271 INS GOOD N/A N/A N/A MCC18212 271 INS GOOD N/A N/A N/A LPA1821 271 INS N/A N/A N/A N/A LPA1822 271 INS N/A N/A N/A N/A LPA1823 271 INS N/A N/A N/A N/A LPA1824 271 INS N/A N/A N/A N/A RGLI1821 271 PREcUT BAD N/A N/A N/A  b. 在*.rpt, *.trf, a nd *mcX中可以找到較高的Access 和 Handoff Failures14:42:26 MGLI941 ** ALARM:11301 BTS LAPD GLIMM Datalink Failure: Not Recoveredc. 常見的 MGLI告警:d. 可能的解決方法i. 轉(zhuǎn)換 MGLI2 狀態(tài)為INS ，觀察是否MGLI的故障還繼續(xù)出現(xiàn)如果沒有，則可能是其他的問題ii. 如果MGLI INS還出現(xiàn)同樣的告警，則需要站點(diǎn)技術(shù)人員在BTS處測試CSU，上面的告警是由于LAPD GLIMM Datalink 引起II. CSM 故障a. GPS的定時(shí)問題i. BTS 將成為一個(gè)“Island Cell” （孤島小區(qū)）– 移動(dòng)臺(tái)只能在BTS中發(fā)起呼叫，但是不能從本小區(qū)切換，也不能切換到本小區(qū)b. STATUS的不同i. 檢查一下BTS 和CSM 中status的不同ii. 如果 CSM CLOCK_SRC 不是 GPS，則轉(zhuǎn)為HSO（高穩(wěn)度晶振控制）定時(shí) c. CSM2 INS,，這表示較早的時(shí)候出現(xiàn)過問題（因?yàn)橥ǔ?，CSM1 應(yīng)該是INS）i. 如果 CSM2是 INS (CLOCK_SRC為HSO)，CSM1是OOS，站點(diǎn)技術(shù)人員應(yīng)勘察站點(diǎn)d. 在*.rpt, *.trf, and *mcX中可以找到較高的 Oamp。 參見下面的BTS312例子 (這是運(yùn)行showevents腳本后的輸出，注：該腳本是Sprint公司自己的腳本)14:44:39 MGLI3121 ** ALARM:11301 BTS LAPD GLIMM Datalink Failure: Not Recovered14:44:44 MCC3127 ** ALARM:4510 PPP Session Is Down14:45:06 MGLI3121 CLR ALARM:11301 BTS LAPD GLIMM Datalink Failure: Not Recovered14:45:09 MCC3127 CLR ALARM:4510 PPP Session Is Down14:45:20 BTSSPAN3121 CLR ALARM:118068 SPAN OutofService Continuo