S1240 STP(贝尔)信令链路频繁翻转的处理两例.doc

S1240 STP信令链路频繁翻转的处理两例 日常维护中遇到的信令频繁翻转多由传输不稳造成，S1240 设备原因一般都为信令模块造成。现将近日发生的两例中继模块原因导致的信令频繁翻转处理过程记录如下，供大家参考。故障现象一: HFH2-HFGA方向 SLC=1 信令链路频繁翻转处理过程: 1.HFH2 执行指令 220:DEST=HFGA&NAT,SLC=1,9=6. 220:DEST=HFGA&NAT,SLC=1,9=5. 对该信令打死激活，无效。 2.HFH2 对信令模块进行 ：V SLTC,203,4,ALL 操作后信令恢复正常。但一般两三天后信令又会不活。 3.查看5691报告，发现信令翻转时事件均为H1B,排除传输不稳导致信令翻转的可能。 HFH2 2006-07-11 06:21:40 TU 05691 C7S0301+ N7 ROUTE NETWORK MANAGEMENT N7 LINK STATUS REPORT DATE: 2006-07-11 - OWN IDENTIFICATION: HFH2 SSF: ALL -#-#-#-#-#-=-#-#-#-#-=-#-#- DESTINATION SSF LINK LINK SLC SIGN-LINK DTM LINK-STATE TRAFFIC-STATE TIME EVENT ID SET PCE TN PCE PREVIOUS ACTUAL PREVIOUS ACTUAL HH:MM:SS -#-#-#-#-#-=-#-#-#-#-=-#-#- HFGA ALL 181 104 1 H203 4 H110 ACTIVE ACTING TRAFFIC NO TRAF 06:21:09 H1B HFGA ALL 181 104 1 H203 4 H110 ACTING ACTIVE NO TRAF TRAFFIC 06:21:29 EVENT + MEANING -+- H1B SIE/SIN/SIO/SIOS RECEIVED UNSOLICITED REPORT NO = 05691 HFH2 2006-07-11 06:23:07 TU 05691 C7S0301+ N7 ROUTE NETWORK MANAGEMENT N7 LINK STATUS REPORT DATE: 2006-07-11 - OWN IDENTIFICATION: HFH2 SSF: ALL -#-#-#-#-#-=-#-#-#-#-=-#-#- DESTINATION SSF LINK LINK SLC SIGN-LINK DTM LINK-STATE TRAFFIC-STATE TIME EVENT ID SET PCE TN PCE PREVIOUS ACTUAL PREVIOUS ACTUAL HH:MM:SS -#-#-#-#-#-=-#-#-#-#-=-#-#- HFGA ALL 181 104 1 H203 4 H110 ACTIVE ACTING TRAFFIC NO TRAF 06:22:37 H1B HFGA ALL 181 104 1 H203 4 H110 ACTING ACTIVE NO TRAF TRAFFIC 06:22:50 EVENT + MEANING -+- H1B SIE/SIN/SIO/SIOS RECEIVED UNSOLICITED REPORT NO = 05691 3.HFH2 对信令模块做环回测试，执行指令 220:DEST=HFGA&NAT,SLC=1,9=6. 220:DEST=HFGA&NAT,SLC=1,9=30. 显示信令状态为 ACTIVE-LOOP。考虑到SLC=1信令链路所在的中继模块上同时承载了四条信令链路，而翻转的总是 SLC=1信令链路。于是考虑更换信令模块。但更换信令模块 H203&4后故障依旧。 4.在排除对端原因造成信令翻转的可能后，更换中继模块 H110。故障彻底解决。 故障现象二: HFH2-JNH2方向多条信令链路频繁翻转，且每次翻转的信令链路不尽相同处理过程: 1.HFH2 按一般处理流程对信令进行处理后无效。 2.检查信令模块和中继模块状态均正常。 3.联系济南移动处理后信令恢复正常。但一般两三天后又会有信令不活。不活的信令链路每次不尽相同，但都是承载在同一中继模块上。 4.查看5691报告，发现信令翻转时事件多为H1B,少量为H17 基本排除传输不稳导致信令翻转的可能。 HFH2 2006-07-17 20:31:27 MO 05691 C7S0301+ N7 ROUTE NETWORK MANAGEMENT N7 LINK STATUS REPORT DATE: 2006-07-17 - OWN IDENTIFICATION: HFH2 SSF: ALL -#-#-#-#-#-=-#-#-#-#-=-#-#- DESTINATION SSF LINK LINK SLC SIGN-LINK DTM LINK-STATE TRAFFIC-STATE TIME EVENT ID SET PCE TN PCE PREVIOUS ACTUAL PREVIOUS ACTUAL HH:MM:SS -#-#-#-#-#-=-#-#-#-#-=-#-#- JNH2 ALL 319 70 6 H205 6 H625 ACTIVE ACTING TRAFFIC NO TRAF 20:30:56 H17 JNH2 ALL 319 70 6 H205 6 H625 ACTING ACTIVE NO TRAF TRAFFIC 20:31:05 EVENT + MEANING -+- H17 SUERM TRESHOLD EXCEEDED UNSOLICITED REPORT NO = 05691 HFH2 2006-07-17 23:05:40 MO 05691 C7S0301+ N7 ROUTE NETWORK MANAGEMENT N7 LINK STATUS REPORT DATE: 2006-07-17 - OWN IDENTIFICATION: HFH2 SSF: ALL -#-#-#-#-#-=-#-#-#-#-=-#-#- DESTINATION SSF LINK LINK SLC SIGN-LINK DTM LINK-STATE TRAFFIC-STATE TIME EVENT ID SET PCE TN PCE PREVIOUS ACTUAL PREVIOUS ACTUAL HH:MM:SS -#-#-#-#-#-=-#-#-#-#-=-#-#- JNH2 ALL 306 70 0 H37 6 H625 ACTIVE ACTING TRAFFIC NO TRAF 23:05:09 H1B JNH2 ALL 534 70 14 H1335 6 H625 ACTIVE ACTING TRAFFIC NO TRAF 23:05:09 H1B JNH2 ALL 530 70 10 H1026 6 H625 ACTIVE ACTING TRAFFIC NO TRAF 23:05:09 H1B JNH2 ALL 528 70 8 H1020 6 H625 ACTIVE ACTING TRAFFIC NO TRAF 23:05:09 H1B JNH2 ALL 532 70 12 H1320 6 H625 ACTIVE ACTING TRAFFIC NO TRAF 23:05:09 H1B JNH2 ALL 319 70 6 H205 6 H625 ACTIVE ACTING TRAFFIC NO TRAF 23:05:09 H1B JNH2 ALL 315 70 2 H201 6 H625 ACTIVE ACTING TRAFFIC NO TRAF 23:05:09 H1B JNH2 ALL 317 70 4 H203 6 H625 ACTIVE ACTING TRAFFIC NO TRAF 23:05:09 H1B JNH2 ALL 534 70 14 H1335 6 H625 ACTING ACTIVE NO TRAF TRAFFIC 23:05:18 JNH2 ALL 530 70 10 H1026 6 H625 ACTING ACTIVE NO TRAF TRAFFIC 23:05:22 JNH2 ALL 319 70 6 H205 6 H625 ACTING ACTIVE NO TRAF TRAFFIC 23:05:24 JNH2 ALL 532 70 12 H1320 6 H625 ACTING ACTIVE NO TRAF TRAFFIC 23:05:27 JNH2 ALL 317 70 4 H203 6 H625 ACTING ACTIVE NO TRAF TRAFFIC 23:05:29 JNH2 ALL 528 70 8 H1020 6 H625 ACTING ACTIVE NO TRAF TRAFFIC 23:05:33 EVENT + MEANING -+- H1B SIE/SIN/SIO/SIOS RECEIVED UNSOLICITED REPORT NO = 05691 5.联系济南移动了解到对故障信令的处理情况为：每次对故障信令的信令模块进行VERIFY 操作后信令就能恢复，并且已经更换过两块信令模块。于是建议其更换中继模块。 6.济南移动更换中