問(wèn)題已開啟
(普通問(wèn)題)
幫看一下愛(ài)立信LOG,看看有什么問(wèn)題 謝謝
幫看一下愛(ài)立信LOG,看看有什么問(wèn)題 謝謝
[11-12-22 11:23:15.402] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-22 11:35:02.902] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-22 11:35:05.902] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-22 11:46:53.902] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-22 11:46:56.902] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-22 12:16:24.902] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-22 12:16:27.902] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-22 12:28:16.402] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-22 12:28:19.402] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-22 12:40:06.902] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-22 12:40:09.902] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-22 13:15:27.402] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-22 13:15:30.402] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-22 13:33:06.902] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-22 13:33:09.900] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-22 13:41:19.996] P_MPSK_CLOCK timeout_clock_main.c:419 TRACED:Setting time: 11-12-22 13:41:41.000
[11-12-22 13:51:07.906] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-22 13:51:10.906] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-22 14:08:47.906] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-22 14:08:50.906] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-22 14:14:36.906] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-22 14:14:39.906] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-22 15:01:35.406] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-22 15:01:38.406] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-22 15:26:03.406] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-22 15:26:06.406] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-22 15:30:53.406] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-26 19:59:51.852] TSC_Regulation regulation.c:2697 TRACED:C_V: 8859
[11-12-26 19:59:51.852] TSC_Regulation regulation.c:1464 TRACED:Send subscrSynchStateRsp: synched 0, frame 0, exec 0
[11-12-26 19:59:53.196] O_RBS_Status RBS_STATUS_DEF.c:393 TRACEH:FAULT:11-12-26 19:59 MO: TF, Instance 0, Raise , EC1, PCM SYNCH NO USABLE PCM REFERENCE
[11-12-26 19:59:53.202] O_RBS_Status RBS_STATUS_DEF.c:398 FAULT:11-12-26 19:59 FuncType: DX, Instance 0, Raise , EC1, PCM REF HOLD OVER TIMEOUT
[11-12-26 20:02:49.852] TSC_Regulation regulation.c:1333 TRACEH:S Y N C H S T A T E = S Y N C H E D !
[11-12-26 20:02:49.852] TSC_Regulation regulation.c:2336 TRACED:syncState: SYNCHRONIZED
[11-12-26 20:02:49.852] TSC_Regulation regulation.c:2355 TRACED:syncStatus.freqSync: GOOD
[11-12-26 20:02:49.852] TSC_Regulation regulation.c:2396 TRACED:syncStatus.frameSync: BAD
[11-12-26 20:02:49.852] TSC_Regulation regulation.c:2644 TRACED:exec_ref: 0
[11-12-26 20:02:49.852] TSC_Regulation regulation.c:2648 TRACED:FI: 4559
[11-12-26 20:02:49.852] TSC_Regulation regulation.c:2651 TRACED:FI_error: 31
[11-12-26 20:02:49.852] TSC_Regulation regulation.c:2657 TRACED:freqEst: -1, ip: -1876619478, ep: -31
[11-12-26 20:02:49.852] TSC_Regulation regulation.c:2662 TRACED:freqEstVar: 4, ip: 1180786556, ep: -28
[11-12-26 20:02:49.852] TSC_Regulation regulation.c:2683 TRACED:c_adj CO.ip:0 C0.ep:-30
[11-12-26 20:02:49.852] TSC_Regulation regulation.c:2686 TRACED:c_adj C1.ip:0 C1.ep:-30
[11-12-26 20:02:49.852] TSC_Regulation regulation.c:2689 TRACED:c_adj C2.ip:1161101934 C2.ep:-17
[11-12-26 20:02:49.852] TSC_Regulation regulation.c:2694 TRACED:refTemp: 215, tempRange Tmin: 1280, Tmax-1280
[11-12-26 20:02:49.854] TSC_Regulation regulation.c:2697 TRACED:C_V: 8760
[11-12-26 20:02:49.854] TSC_Regulation regulation.c:1464 TRACED:Send subscrSynchStateRsp: synched 1, frame 0, exec 0
[11-12-26 20:02:53.450] O_RBS_Status RBS_STATUS_DEF.c:393 TRACEH:FAULT:11-12-26 20:02 MO: TF, Instance 0, Cease , EC1, PCM SYNCH NO USABLE PCM REFERENCE
[11-12-26 20:02:53.456] O_RBS_Status RBS_STATUS_DEF.c:398 FAULT:11-12-26 20:02 FuncType: DX, Instance 0, Cease , EC1, PCM REF HOLD OVER TIMEOUT
[11-12-26 20:02:53.514] TSC_CO_Timing hw_driver_garp.c:1283 TRACED:NO! TRAFFIC ON SBUS
[11-12-26 20:02:53.514] TSC_CO_Timing methods.c:1031 TRACEH:External State = RESET
[11-12-26 20:02:53.514] TSC_CO_Timing methods.c:939 TRACEH:External State = DISABLED
[11-12-26 20:02:53.522] TSC_CO_Timing hw_driver_garp.c:1283 TRACED:NO! TRAFFIC ON SBUS
[11-12-26 20:02:53.596] TSC_CO_Timing methods.c:166 TRACEH:coConfig syncSource = 3, coConfig syncMode = 1
[11-12-26 20:02:53.596] TSC_CO_Timing methods.c:168 TRACEH:coConfig compValue = 0, coConfig FS offset = FFFFFFFFFF
[11-12-26 20:02:53.596] TSC_CO_Timing methods.c:173 TRACEH:coConfig, esbTs= 255, master_TgInst= 65535, master_TXChainDelay:=65535
[11-12-26 20:02:53.596] TSC_CO_Timing methods.c:410 TRACEH:The DXU has been configured to Standalone mode!
[11-12-26 20:02:53.852] TSC_Regulation regulation.c:1464 TRACED:Send subscrSynchStateRsp: synched 1, frame 0, exec 0
[11-12-26 20:02:53.852] TSC_CO_Timing methods.c:1139 TRACED:Sending ConfigResult
[11-12-26 20:02:54.384] TSC_CO_Timing methods.c:882 TRACEH:External State = ENABLED
[11-12-31 11:20:25.798] TSC_Regulation regulation.c:2686 TRACED:c_adj C1.ip:0 C1.ep:-30
[11-12-31 11:20:25.798] TSC_Regulation regulation.c:2689 TRACED:c_adj C2.ip:1160780509 C2.ep:-17
[11-12-31 11:20:25.798] TSC_Regulation regulation.c:2694 TRACED:refTemp: 225, tempRange Tmin: 1280, Tmax-1280
[11-12-31 11:20:25.800] TSC_Regulation regulation.c:2697 TRACED:C_V: 8767
[11-12-31 11:20:25.800] TSC_Regulation regulation.c:1464 TRACED:Send subscrSynchStateRsp: synched 1, frame 0, exec 0
[11-12-31 11:20:29.382] O_RBS_Status RBS_STATUS_DEF.c:393 TRACEH:FAULT:11-12-31 11:20 MO: TF, Instance 0, Cease , EC1, PCM SYNCH NO USABLE PCM REFERENCE
[11-12-31 11:20:29.386] O_RBS_Status RBS_STATUS_DEF.c:398 FAULT:11-12-31 11:20 FuncType: DX, Instance 0, Cease , EC1, PCM REF HOLD OVER TIMEOUT
[11-12-31 11:20:29.446] TSC_CO_Timing hw_driver_garp.c:1283 TRACED:NO! TRAFFIC ON SBUS
[11-12-31 11:20:29.446] TSC_CO_Timing methods.c:1031 TRACEH:External State = RESET
[11-12-31 11:20:29.446] TSC_CO_Timing methods.c:939 TRACEH:External State = DISABLED
[11-12-31 11:20:29.454] TSC_CO_Timing hw_driver_garp.c:1283 TRACED:NO! TRAFFIC ON SBUS
[11-12-31 11:20:29.528] TSC_CO_Timing methods.c:166 TRACEH:coConfig syncSource = 3, coConfig syncMode = 1
[11-12-31 11:20:29.528] TSC_CO_Timing methods.c:168 TRACEH:coConfig compValue = 0, coConfig FS offset = FFFFFFFFFF
[11-12-31 11:20:29.528] TSC_CO_Timing methods.c:173 TRACEH:coConfig, esbTs= 255, master_TgInst= 65535, master_TXChainDelay:=65535
[11-12-31 11:20:29.528] TSC_CO_Timing methods.c:410 TRACEH:The DXU has been configured to Standalone mode!
[11-12-31 11:20:29.798] TSC_Regulation regulation.c:1464 TRACED:Send subscrSynchStateRsp: synched 1, frame 0, exec 0
[11-12-31 11:20:29.798] TSC_CO_Timing methods.c:1139 TRACED:Sending ConfigResult
[11-12-31 11:20:30.326] TSC_CO_Timing methods.c:882 TRACEH:External State = ENABLED
[11-12-31 11:24:12.298] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-31 11:24:15.298] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-31 11:27:43.298] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-31 11:27:46.298] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-31 11:30:25.800] TSC_Regulation regulation.c:1219 TRACED:Start supervising class2 limit
[11-12-31 11:39:34.798] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
[11-12-31 11:39:37.798] TSC_Regulation regulate.c:1185 TRACED:Info: Leaving HoldOver (Technical mode)
[11-12-31 11:57:28.298] TSC_Regulation regulate.c:1179 TRACED:Info: Entering HoldOver (Technical mode)
提問(wèn)者: 8694694 提問(wèn)時(shí)間: 2012-01-31
• 愛(ài)立信5G如何LMT登錄 2020-07-15
• 愛(ài)立信MSC退網(wǎng)流程 2020-05-07
• 愛(ài)立信CQI優(yōu)化有沒(méi)有什么參數(shù)可以修改? 2020-01-08
• 愛(ài)立信volte語(yǔ)音說(shuō)話模糊,聽不清,從哪方面著手處理? 2019-12-17
• 愛(ài)立信NRO,NDO是什么的縮寫 2019-12-10
• win10系統(tǒng)愛(ài)立信幫助文件庫(kù)Alex無(wú)法使用 2019-12-06
• 有沒(méi)有愛(ài)立信基站技術(shù)交流群 2019-10-24
• 愛(ài)立信核心網(wǎng)網(wǎng)管OSS-RC 2019-09-27
• 愛(ài)立信MSC退網(wǎng)流程 2020-05-07
• 愛(ài)立信CQI優(yōu)化有沒(méi)有什么參數(shù)可以修改? 2020-01-08
• 愛(ài)立信volte語(yǔ)音說(shuō)話模糊,聽不清,從哪方面著手處理? 2019-12-17
• 愛(ài)立信NRO,NDO是什么的縮寫 2019-12-10
• win10系統(tǒng)愛(ài)立信幫助文件庫(kù)Alex無(wú)法使用 2019-12-06
• 有沒(méi)有愛(ài)立信基站技術(shù)交流群 2019-10-24
• 愛(ài)立信核心網(wǎng)網(wǎng)管OSS-RC 2019-09-27
問(wèn)題答案
( 8 )
樓主,LOG信息沒(méi)貼上來(lái)啊~
回答者:
buptwzz
回答時(shí)間:2012-01-31 13:05
26 21
log信息呢?
回答者:
yeyazi520
回答時(shí)間:2012-01-31 14:37
31 19
....這是神貓問(wèn)題啊 求描述
回答者:
sgivan
回答時(shí)間:2012-01-31 15:15
21 21
沒(méi)看到LOG信息,樓主沒(méi)上傳上來(lái)吧
回答者:
jingyan8661
回答時(shí)間:2012-02-01 09:26
20 19
NO LOG , NO PROBLEM !
回答者:
post927
回答時(shí)間:2012-02-01 12:39
22 20
這問(wèn)題提的真是飄渺。。。讓人沒(méi)法回答。。。沒(méi)有什么實(shí)際的東西叫人怎么幫忙? 樓主你喝麻了
回答者:
wanglei_tx
回答時(shí)間:2012-02-01 16:11
23 19
什么東西都沒(méi)有,怎么看?!
回答者:
liupeixin
回答時(shí)間:2012-02-01 19:13
22 25
哥哥神啊,這是啥東西嘛?雌饋(lái)眼花繚亂的啊
回答者:
zengyu
回答時(shí)間:2012-02-05 09:28
23 22
• 西安中興精誠(chéng)通訊有限公司
聘:重慶-網(wǎng)優(yōu)高級(jí)工程師
需求人數(shù):2 人 地點(diǎn):重慶市
• 南京華蘇科技有限公司 聘:中興網(wǎng)優(yōu)測(cè)試工程師(河南)
需求人數(shù):15 人 地點(diǎn):鄭州市,商丘市,濟(jì)源市,開封市
• 怡利科技發(fā)展有限公司 聘:移動(dòng)電信聯(lián)通單驗(yàn)工程師
需求人數(shù):5 人 地點(diǎn):貴州省
• 南京順盛通信科技有限責(zé)任公司 聘:中興傳輸IPRAN工程師
需求人數(shù):1 人 地點(diǎn):連云港市,鹽城市
• 北京電旗通訊技術(shù)股份有限公司 聘:網(wǎng)優(yōu)實(shí)習(xí)生通信應(yīng)屆生(云南)
需求人數(shù):1 人 地點(diǎn):昆明市,思茅市,昭通市
• 南京格安信息系統(tǒng)有限責(zé)任公司 聘:5G工程后臺(tái)人員
需求人數(shù):10 人 地點(diǎn):北京市
• 重慶信科通信工程有限公司 聘:南昌電信中興原廠高級(jí)
需求人數(shù):2 人 地點(diǎn):南昌市
• 杭州東信網(wǎng)絡(luò)技術(shù)有限公司 聘:LTE/5G網(wǎng)絡(luò)中高級(jí)優(yōu)化工程師
需求人數(shù):2 人 地點(diǎn):上海市
• 安徽引途科技有限公司 聘:皖北地區(qū)單驗(yàn)測(cè)試工程師
需求人數(shù):20 人 地點(diǎn):安徽省
• 浙江明訊網(wǎng)絡(luò)技術(shù)有限公司 聘:浙江網(wǎng)絡(luò)優(yōu)化工程師
需求人數(shù):8 人 地點(diǎn):寧波市,舟山市,湖州市,紹興市
需求人數(shù):2 人 地點(diǎn):重慶市
• 南京華蘇科技有限公司 聘:中興網(wǎng)優(yōu)測(cè)試工程師(河南)
需求人數(shù):15 人 地點(diǎn):鄭州市,商丘市,濟(jì)源市,開封市
• 怡利科技發(fā)展有限公司 聘:移動(dòng)電信聯(lián)通單驗(yàn)工程師
需求人數(shù):5 人 地點(diǎn):貴州省
• 南京順盛通信科技有限責(zé)任公司 聘:中興傳輸IPRAN工程師
需求人數(shù):1 人 地點(diǎn):連云港市,鹽城市
• 北京電旗通訊技術(shù)股份有限公司 聘:網(wǎng)優(yōu)實(shí)習(xí)生通信應(yīng)屆生(云南)
需求人數(shù):1 人 地點(diǎn):昆明市,思茅市,昭通市
• 南京格安信息系統(tǒng)有限責(zé)任公司 聘:5G工程后臺(tái)人員
需求人數(shù):10 人 地點(diǎn):北京市
• 重慶信科通信工程有限公司 聘:南昌電信中興原廠高級(jí)
需求人數(shù):2 人 地點(diǎn):南昌市
• 杭州東信網(wǎng)絡(luò)技術(shù)有限公司 聘:LTE/5G網(wǎng)絡(luò)中高級(jí)優(yōu)化工程師
需求人數(shù):2 人 地點(diǎn):上海市
• 安徽引途科技有限公司 聘:皖北地區(qū)單驗(yàn)測(cè)試工程師
需求人數(shù):20 人 地點(diǎn):安徽省
• 浙江明訊網(wǎng)絡(luò)技術(shù)有限公司 聘:浙江網(wǎng)絡(luò)優(yōu)化工程師
需求人數(shù):8 人 地點(diǎn):寧波市,舟山市,湖州市,紹興市
熱點(diǎn)問(wèn)題
更多精彩
聯(lián)系我們 - 問(wèn)通信專家 | Powered by MSCBSC 移動(dòng)通信網(wǎng) © 2006 - |