Customer meets a timeout prompt after executing TL1 commands on the BMS server and this problem is affecting their operation department.Version information: N2000 BMS V200R011C03B036SPC003.
HQ engineer checks the XDSL process log file(base_p74_*), which includes the time when we meet the fault, and find follow information, as the last line, we can find "task id of XDSl process" has been using out!" This is leaded by that xdsl process works with a lot of trap messages.
15:50:21.913893.T75 xdsl ADSL_Module INFO: TaskMgr,CommandCode,m_iTaskCount,ThreadID[0x75],IdleThread
15:50:21.913963.T75 xdsl ADSL_Module INFO: Receive CmdCode ,before new CADSLPortTrapRegisterTask()!
15:50:21.914029.T75 xdsl ADSL_MOUDLE INFO: Receive CmdCode ,before new CADSLPortTrapRegisterTask()!
15:50:21.914127.T75 xdsl ADSL_Module INFO: Finish Function:CADSLPortTaskMgr::iMapCreateTask()!
15:50:21.914213.T75 xdsl ADSL_MOUDLE INFO: Finish Function:CADSLPortTaskMgr::iMapCreateTask()!
15:50:21.914298.T75 TMGR INFO: task id has been using out!
It happens due the trap packets quantity is over xdsl process capability. To restore it, you can apply following method:
delete FaultDB..tbl_RegTrap where ProcID = 74 and TrapID = 21
Then, restart the XDSL process.
Otherwise,you still can mask the xdsl events and alarms for related host devices, which report these message to the BMS server.
Customer can not activate, deactivate, list adsl port and so on by TL1 commands on BMS server.
For example, it was not possible to make a simple active operation by using the ACT-ADSLPORT command, as follow:
;ACT-ADSLPORT::DEV=RJCBF__-EHI101,FN=0,SN=13,PN=46:1::; 0 2010-10-22 15:47:26
M 1 COMPLD
EN=2686058508 ENDESC=Task timeout;