Mxe controller restarts automatically

[Jack Xu]

Hi buddies,

recently one mxe in my office restarted 2 times in the past several days, logs indict that due to E2t issue. the icp and e2t card ip address are out of the range of dhcp ip address pool . so there's no possibility that ip address conflict. below is relevant logs.




!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
E2t 192.168.1.4 is not responding to PING  @ FRI NOV 04 11:57:37 2011
This is not a LX system, so there is no L2 to reset
PING 192.168.1.4: 56 data bytes
ping: timeout
no answer from 192.168.1.4
E2t 192.168.1.4 is not responding to PING
/db/spyLog/ResetL2EventLog.wvr will contain 15 seconds of Object and System Libraries Events (WV_CLASS_3)
alt usage



and,

MCT_CommResetRemoteCb Raise SMCT_CommResetCystem Alarm
E2tRaiseAlarm called
Delay Component Failure notification by 120 sec while attempting to get E2T debug files
E2tProxy<->E2t (Remote) Communications failure
Unexpected Result->E2tProxySpImpl::E2TSP_Router_EntryGetMsg from E2T failed
Unexpected Result->ResetE2tConnection invoked
Unexpected Result->GetMsgm_ConnectedSocket.Read failed: Connection reset. (600b0036) Connection reset.
OpenMID:86fd4383 CID: 6fd5225 MSGConnection[CID:6d83207] already exists, OpenTxNack to CCC.
OpenMID:86f9236d CID: 6f9321f MSGConnection[CID:6d83207] already exists, OpenTxNack to CCC.
tE2tHeartBeat: Internal L2 Switch was Resetdue to E2T 192.168.1.4 Heartbeat failure; E2T might be rebooting. See log /db/L2ResetLog.txt
OpenMID:8452a31d CID: 452b210 MSGConnection[CID:4529209] already exists, OpenRxNack to CCC.
CompleteFsmRequest: MID:8c52830b CID: 4529209 PCC[ 0x4529209 ]:Tx[ IP_PHONE, PortId:1365, CompId:1, DN:7541 ] Rx[ TDM, PortId=5, CompId=16, DN: ]completed in [ 10000 ] msec in state [ RX_CLOSED ] with a failure [ FSM_RX_CLOSE_TIMEDOUT ]
OpenMID:86dc4318 CID: 6dc520e MSGConnection[CID:6d83207] already exists, OpenTxNack to CCC.


if there's anything wrong with the hardware ??


thx..

[wiseguy]

There could be several reasons for this to happen. If the RTC can't communicate with the E2T it will force through a reboot.
If this is a system that has worked for xxx time and had no IP address change or something then most likely this is HW.
If this is from the beginning then clear the E2T card entry's by entering a . in all lines. When walked through them all start the E2T card setup from the beginning and make sure that the E2T card has the same subnet setup as the RTC.

[Jack Xu]

Wiseguy,

thanks for your suggestion,

this device has worked for about three months, and no ip address change, now i have found a backup device to replace it, i 'll take it back to my office to monitor longer.

[Mattmayn]

What software release are you running? I remember a bug in one of the 4.x versions that caused this and was logged in the KPI with a fix in 5.0. I had this at one site but my logs pointed to power failure (wasn't the actual cause).

It may be hardware but if you swap it and the replacement does the same thing after a period of time it could be a bug.

[vito]

I have also case like that. As logs captured from the maintenance port at restarting.

=====================
x3d83880 (ASUTimersT3): Task called pure virtual function for which t
here is no definition
Critical Alarm being raised upon detecting the following task suspended: ASUTime
rsT3 taskId 0x3d83880 crash time SUN JAN 17 16:46:50 2016

Task SysPreMort0 being deleted while ACTIVE
WARNING-System shutdown requested by task: tTMonitor
Raised Critical Alarm on Stale Tasks
RaiseAlarm alarm severity critical, forcing machine shutdown

!!! HARDWARE RESET REQUEST FROM task HwReset !!!

16/01/17 16:47:49 - HardResetHookExecute called by task: HwReset


End HardResetHookExecute

/sysro/  - disk check in progress ...

Thx,
Angus


Angus U