Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: northernscum on February 29, 2016, 01:53:41 PM
-
Hey there
just wondering anyone else experienced this and what the resolution was. So far I have yet to find anything on the network.
But something definitely is up. Thanks
1785 2016/Feb/29 9:20:00 Call Control - Maintenance IP Trunk link to icp 004 SEIC failed and link dropped.
1784 2016/Feb/29 9:20:00 STSP IP trunk to 172.25.10.1:2315 has failed.
1783 2016/Feb/29 9:20:00 Heartbeat Server ICP has lost contact with (172.25.10.1:2315), network driver cluster pool free: 6129 and low water mark: 5814
1782 2016/Feb/29 9:19:54 Call Control - Software MSG_DATA: $0 $6 $8 $6A $70 $0 $87 $F4 $FC $0 $0 $0 $4 $20 $A $BRMSG DL State: 06, LinkH: 011Remote IP: 172.018.001.037
1781 2016/Feb/29 9:19:54 Call Control - Software UNEXPECTED MESSAGE, OFFSET 2:$14BA, PC: $38EA4ALOG_ID: rmsgdlh#51, PROCEDURE: handle_rmsg_dl_release_indicatio, SEVERITY: cp_minorPID: ($6, $5AE)MSG_FUNC_CODE: $D5, MSG_TX_PID: ($0, $1)
1780 2016/Feb/29 9:19:53 CCC_Ipsw CompleteFsmRequest: MID:86635e7a CID: 6634a2c PCC[ 0x6634A2C ]:Tx[ IP_PHONE, PortId:791, CompId:1, DN:4809 ] Rx[ IP_PHONE, PortId=829, CompId=1, DN:3991 ]completed in [ 10010 ] msec in state [ AWAITING_OPEN_RX_ACK ] with a failure [ FSM_RX_OPEN_TIMEDOUT ]
1779 2016/Feb/29 9:19:53 CCC_Ipsw CompleteFsmRequest: MID:865f3e78 CID: 65f2a2b PCC[ 0x65F2A2B ]:Tx[ IP_PHONE, PortId:829, CompId:1, DN:3991 ] Rx[ IP_PHONE, PortId=791, CompId=1, DN:4809 ]completed in [ 10000 ] msec in state [ AWAITING_OPEN_RX_ACK ] with a failure [ FSM_RX_OPEN_TIMEDOUT ]
1778 2016/Feb/29 9:19:50 Call Control - Maintenance IP Trunk link to icp 003 vmcd failed and link dropped.
1777 2016/Feb/29 9:19:50 Call Control - Maintenance ---------------+--------+-------+-------+-------+---------+---------+---------- ICP Comms Card | 4 | 2 | 50 % | Major | > 0 % | 25 % | 100 % | ---------------+--------+-------+-------+-------+---------+---------+----------
1776 2016/Feb/29 9:19:50 Call Control - Maintenance ---------------+--------+-------+-------+-------+---------+---------+---------- |Total In| Unavailable | Alarm Threshold Percentages Category | System | Total | % | Alarm | MINOR | MAJOR | CRITICAL
1775 2016/Feb/29 9:19:50 Call Control - Maintenance ------------ Current System Alarm : | MAJOR | viewed from Active ------------
1774 2016/Feb/29 9:19:49 STSP IP trunk to 172.18.1.37:1067 has failed.
-
You are losing network connectivity to Node 3&4 (vmcd & SEIC)... items 1779-1782 are failures because the link is down, not the cause of the failure, I would guess that it was something that the system attempted before realizing the link was down, then just timed out and flagged an error.
How are you connected to these sites? VPN, MPLS, or some other connection? Can you give us a little more detail about the setup and when this started, what may have changed, etc?