Author Topic: MCD 4.0 E2T Reset w/ logs  (Read 4738 times)

Offline wobbly_head_bob

  • Jr. Member
  • **
  • Posts: 62
  • Karma: +0/-0
    • View Profile
MCD 4.0 E2T Reset w/ logs
« on: May 18, 2012, 02:00:35 PM »
Today we updated our 3300 with 20 SIP user licenses and have begun to play with them.  Everything was going fine for a few hours, I was THIIIIIS close to letting leadership play with it as I felt more and more comfortable with it.  Then we had an implosion:

Log Number:    783
Severity:    Warning
Date:    2012/May/18
Time:    12:03:00
Source:    E2T/AppStartup
Description:    Unexpected Result->SysServices::appStartup (10.59.139.114) Normal reset, cause: (0x3) EXTERNAL_INTERNAL_HARD_RESET
File Name and Line Number:    appStartup.cpp;1599

Prior to the E2T resetting (assuming that's what happened in the above log) there were pages of logs that look like these:

Log Number:    729
Severity:    Warning
Date:    2012/May/18
Time:    12:00:49
Source:    CCC_Ipsw
Description:    CompleteFsmRequest: MID:869c4653 CID: 69c4774 PCC[ 0x69C4774 ]: Tx[ FIM, PortId:61, CompId:25, DN: ] Rx[ SIP, PortId=-1, CompId=-1, DN:2780 ] completed in [ 10110 ] msec in state [ AWAITING_OPEN_TX_ACK ] with a failure [ FSM_TX_OPEN_TIMEDOUT ]
File Name and Line Number:    IPSwSP_fsm.cpp;5179

Log Number:    730
Severity:    Warning
Date:    2012/May/18
Time:    12:00:59
Source:    CCC_Ipsw
Description:    CompleteFsmRequest: MID:8e9c4675 CID: 69c4774 PCC[ 0x69C4774 ]: Tx[ FIM, PortId:61, CompId:25, DN: ] Rx[ SIP, PortId=-1, CompId=-1, DN:2780 ] completed in [ 10000 ] msec in state [ STREAM_CLOSED ] with a failure [ FSM_TX_CLOSE_TIMEDOUT ]
File Name and Line Number:    IPSwSP_fsm.cpp;5179

Log Number:    731
Severity:    Warning
Date:    2012/May/18
Time:    12:01:06
Source:    CCC_Ipsw
Description:    CompleteFsmRequest: MID:98578677 CID: 4578773 PCC[ 0x4578773 ]: Tx[ SIP, PortId:-1, CompId:-1, DN:2780 ] Rx[ FIM, PortId=61, CompId=25, DN: ] completed in [ 10000 ] msec in state [ RX_CLOSED ] with a failure [ FSM_RX_CLOSE_TIMEDOUT ]
File Name and Line Number:    IPSwSP_fsm.cpp;5179

Log Number:    732
Severity:    Warning
Date:    2012/May/18
Time:    12:01:24
Source:    CCC_Ipsw
Description:    CompleteFsmRequest: MID:985886d5 CID: 786c537 PCC[ 0x786C537 ]: Tx[ FIM, PortId:69, CompId:25, DN: ] Rx[ IP_TRUNK, PortId=3158, CompId=2, DN:IPTrk ] completed in [ 10000 ] msec in state [ STREAM_CLOSED ] with a failure [ FSM_TX_CLOSE_TIMEDOUT ]
File Name and Line Number:    IPSwSP_fsm.cpp;5179

Log Number:    733
Severity:    Warning
Date:    2012/May/18
Time:    12:01:24
Source:    CCC_Ipsw
Description:    CompleteFsmRequest: MID:985886d6 CID: 4588538 PCC[ 0x4588538 ]: Tx[ IP_TRUNK, PortId:3158, CompId:2, DN:IPTrk ] Rx[ FIM, PortId=69, CompId=25, DN: ] completed in [ 10100 ] msec in state [ RX_CLOSED ] with a failure [ FSM_RX_CLOSE_TIMEDOUT ]
File Name and Line Number:    IPSwSP_fsm.cpp;5179

Do any of you guys have any idea what happened above? 

I can tell you that I was performing a test to see if my Bria Softphone (DN: 2780), installed on an iPhone and configured with multicall lines, could accept two calls (it can) and then merge them into a conference (nope).  The result was a transfer and not a conference using the softphone.  Instead of failing gracefully (if you want to call a failure that) and just not working, the 3300 looks like it was inundated with these requests resulting in the E2T crapping itself and rebooting.  Any input you guys can offer is greatly appreciated.










Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: MCD 4.0 E2T Reset w/ logs
« Reply #1 on: May 18, 2012, 02:13:29 PM »
Seems to me I recently saw a bulletin regarding Bria Softphones causing resets.
If I can find it I'll post the note.

Ralph

Offline bluewhite4

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1041
  • Country: us
  • Karma: +20/-0
    • View Profile
Re: MCD 4.0 E2T Reset w/ logs
« Reply #2 on: May 18, 2012, 04:50:53 PM »
What version of MCD 4 are you using?

There was a fix for a Bria softphone issue that sounds similar in releases 10.0.4.15, 10.2.2.17, and/or MCD 5.0

Offline wobbly_head_bob

  • Jr. Member
  • **
  • Posts: 62
  • Karma: +0/-0
    • View Profile
Re: MCD 4.0 E2T Reset w/ logs
« Reply #3 on: May 21, 2012, 08:27:20 AM »
MCD 4.0 SP4 10.0.4.14

I'm as high in software level as I can go for the time being.  We use Ops/Enterprise manager and aren't able to upgrade it quite yet...plus we're getting ready to move our 3300s to "clusters" (40 switches all ARS'd) so software upgrades at this point just aint happenin'.  I'll see if I can't dig up the RN for 10.0.4.15 though, thanks!!!

Offline wobbly_head_bob

  • Jr. Member
  • **
  • Posts: 62
  • Karma: +0/-0
    • View Profile
Re: MCD 4.0 E2T Reset w/ logs
« Reply #4 on: May 30, 2012, 09:43:37 AM »
I wasn't able to dig up any information on 10.0.4.15...in fact, I'm fairly sure that number was either mistyped or was a very very short lived version.

A ticket opened with Mitel pretty much verified what I already knew and suggested what I knew they'd suggest:

  -  The reset was caused by the SIP testing and subsequent network congestion and E2T loss.
  -  Multiple improvements made to the SIP capabilities in MCD 5.0.

It almost never fails that I have a problem that Mitel has conveniently addressed in the next level of software!   :o  Ahh well, I guess we'll get there after we go through the clustering project.


 

Sitemap 1 2 3 4 5 6 7 8 9 10