Author Topic: Saving configurations error and self-restart  (Read 9707 times)

Offline eciroglu

  • Jr. Member
  • **
  • Posts: 41
  • Karma: +0/-0
    • View Profile
Saving configurations error and self-restart
« on: May 16, 2012, 04:29:17 AM »
Hi everone,

I am new at 3300 CXi and there are some problems.

I programmed the ASU and create 2 analog extensions, but there is no dial tone. In addition, after programming ASU, pbx runs a restart progress by self in 1 minute. After restart progress, there is no programmed ASU and no created entensions.

The other problem is that: When power off the pbx, all changes are replacing as default. Like that i didnt do any configuration changes.

Volkan,


Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Saving configurations error and self-restart
« Reply #1 on: May 16, 2012, 06:05:16 AM »
What version of software?   What hardware platform?

Is there something in the logs that show reboot cause?

Ralph

Offline august

  • Sr. Member
  • ****
  • Posts: 258
  • Country: ca
  • Karma: +9/-0
    • View Profile
Re: Saving configurations error and self-restart
« Reply #2 on: May 16, 2012, 06:32:19 AM »
I dont know why it reboot by adding an ASU, but your flag must be OFF (DBMS STAT).

You should do a DBMS SAVE in maintenance, this will bring the flag to ON and it will keep the configuration after a reboot instead of a factory default.

Offline eciroglu

  • Jr. Member
  • **
  • Posts: 41
  • Karma: +0/-0
    • View Profile
Re: Saving configurations error and self-restart
« Reply #3 on: May 16, 2012, 06:38:03 AM »
I am using 3300 CXi, Rev. 8.0. What is it meaning hardware platform? Can you expand the meaning of 'hardware paltform'?

I have a text file includes log records for this situation. I can publish under this post if you want to see. But the record is a bit long.

Thanks.

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Saving configurations error and self-restart
« Reply #4 on: May 16, 2012, 07:50:24 AM »
Hardware platform means "what model of 3300" do you have?

What august suggest is correct.   In maintenance, enter "dbms save".

You can attach a screen shot of the logs where it shows the system reboot.   That should be enough.

Ralph

Offline eciroglu

  • Jr. Member
  • **
  • Posts: 41
  • Karma: +0/-0
    • View Profile
Re: Saving configurations error and self-restart
« Reply #5 on: May 16, 2012, 08:21:01 AM »
There is a log record. This is the record that shows you a reboot. This reboot occurs when I picked up handset of an analog extension on AMB. I dont have any idea what this log record tell me.

Thanks.

Volkan,

<<<  Log record >>>

All Software Logs vid1.1 8.0.5.12
1 2 3 4 6 8 7

Log Number Severity Date Time Source Description File Name and Line Number

2594 Warning 2012/May/16 13:25:46 MitaiApp <U:/APIs/MiTAI_VxwLib_src/libmtai_vxw/../mitai_toolkit/source/sockhndl_vxw.c:980>: Error reading opening response from server sockhndl_vxw.c;978

2592 Warning 2012/May/16 13:25:36 MitaiApp <U:/APIs/MiTAI_VxwLib_src/libmtai_vxw/../mitai_toolkit/source/sockhndl_vxw.c:980>: Error reading opening response from server sockhndl_vxw.c;978

2590 Warning 2012/May/16 13:25:25 MitaiApp <U:/APIs/MiTAI_VxwLib_src/libmtai_vxw/../mitai_toolkit/source/sockhndl_vxw.c:980>: Error reading opening response from server sockhndl_vxw.c;978

2588 Error 2012/May/16 13:25:23 HUBServer CHUBServiceProviderServer::HUBTypeMatchesProgramming - Programming mismatch for ASU on CIM: 1, installed: NA COMBO, programmed: UNKNOWN CHUBServiceProviderServer.cpp;533

2585 Warning 2012/May/16 13:25:22 IP Networking - MIPS rdisc: state=enable MIPSServiceProvider.cpp;1024

2584 Warning 2012/May/16 13:25:20 ASU on CIM: 1  CHubDriver::ProcessSocketUp() - 00:10.355] ASU Last Reset: No Logs from Last Reset
 chubdriver.cpp;123

2582 Warning 2012/May/16 13:25:15 MitaiApp <U:/APIs/MiTAI_VxwLib_src/libmtai_vxw/../mitai_toolkit/source/sockhndl_vxw.c:980>: Error reading opening response from server sockhndl_vxw.c;978

2581 Warning 2012/May/16 13:25:14 IP Networking - MIPS rdisc: state=enable MIPSServiceProvider.cpp;1024

2580 Warning 2012/May/16 13:25:07 IP Networking - MIPS Accepted connection from L2 subsystem (1). MIPSServiceProvider.cpp;785

2567 Warning 2012/May/16 13:25:04 MitaiApp <U:/APIs/MiTAI_VxwLib_src/libmtai_vxw/../mitai_toolkit/source/sockhndl_vxw.c:980>: Error reading opening response from server sockhndl_vxw.c;978

2566 Warning 2012/May/16 13:25:04 CommonDsClient InitPortFilter()
Local Port Filter is off.
 CommonDsClient.cpp;404

2564 Warning 2012/May/16 13:24:53 BndWdth InitializeESMInfo - Entering ESM Initialization.
 BndWdth_Mgr.cpp;5977

2563 Warning 2012/May/16 13:24:51 GetChubData CreateSystemIniFile->GetServantData failed for SYSID_PROPERTY_ID
 GetChubData.cpp;71

2562 Warning 2012/May/16 13:24:50 CLMTRemeasureDriver::StartUp() TASK EntryPoint started
 CLMTRemeasureDriver.cpp;248

2560 Warning 2012/May/16 13:24:44 E2tSp Progress Monitor->E2TServiceProvider::StartUp
invoked E2TServiceProvider.cpp;178

2559 Warning 2012/May/16 13:24:44 SLCoordinator Progress Monitor->ServiceLayerCoordinator::ServiceLayerCoordinator
invoked ServiceLayerCoordinator.cpp;2422

2557 Warning 2012/May/16 13:24:41 Call Control - Software DB (DBTable) error: First Key for table 175 not supported.
 log_outputs_util_en.c;1595

2556 Error 2012/May/16 13:24:31 SX2KAlarmSP Start->Failed to retrieve alarm info at start up SX2KAlarm_SP.cpp;1461

2555 Error 2012/May/16 13:24:31 SX2KAlarmSP CheckResponseMessage->Got invalid response message, error =MNMSERROR_SYSTEM_ACCESS_UNAVAILABLE SX2KAlarm_SP.cpp;917

2550 Warning 2012/May/16 13:24:02 Call Control - Software DB (DBTable) error: First Key for table 175 not supported.
 log_outputs_util_en.c;1595

2546 Warning 2012/May/16 13:24:01 MitaiSrv TestMitaiLink: Error 61 returned to Interrogate Switch cmd. HCI_SERVICE_NOT_FOUND
 vxw_linkup.c;810

2541 Warning 2012/May/16 13:23:51 Call Control - Software DB (DBTable) error: Not enough table space to allocate [1, 0 0].
 log_outputs_util_en.c;1595

2530 Warning 2012/May/16 13:23:47 Call Control - Software LOGSYSRTR is ready to route entries
Log name: maintenance log_outputs_util_en.c;1595

2529 Warning 2012/May/16 13:23:47 Call Control - Software LOGSYSRTR is ready to route entries
Log name: security log_outputs_util_en.c;1595

2528 Warning 2012/May/16 13:23:47 Call Control - Software LOGSYSRTR is ready to route entries
Log name: mobility log_outputs_util_en.c;1595

2527 Warning 2012/May/16 13:23:44 Call Control - Software GPAGEMGR: Initializing data structures                                                                                                                                                                                                                 log_outputs_util_en.c;1595

2526 Warning 2012/May/16 13:23:43 Call Control - Software DBMS WARNING: Default (minimal) Configuration in effect. log_outputs_util_en.c;1595

2525 Warning 2012/May/16 13:23:37 Call Control - Software DBASRV created: PID = ($0005,$0034) log_outputs_util_en.c;1595

2524 Warning 2012/May/16 13:23:37 Call Control - Software DBASRV created: PID = ($0004,$0033) log_outputs_util_en.c;1595

2523 Warning 2012/May/16 13:23:37 Call Control - Software DBASRV created: PID = ($0003,$0032) log_outputs_util_en.c;1595

2522 Warning 2012/May/16 13:23:37 Call Control - Software DBASRV created: PID = ($0002,$0031) log_outputs_util_en.c;1595

2521 Warning 2012/May/16 13:23:37 Call Control - Software DBASRV created: PID = ($0001,$0030) log_outputs_util_en.c;1595

2520 Warning 2012/May/16 13:23:37 Call Control - Software DBASRV created: PID = ($0008,$002F) log_outputs_util_en.c;1595

2519 Warning 2012/May/16 13:23:37 Call Control - Software DBASRV created: PID = ($0007,$002E) log_outputs_util_en.c;1595

2518 Warning 2012/May/16 13:23:37 Call Control - Software DBASRV created: PID = ($0006,$002D) log_outputs_util_en.c;1595

2517 Warning 2012/May/16 13:23:33 Call Control - Software DBMS - DBREFUTIL  Function : Read_Db_State_File
Operation : Open     File : state
Return Code : Node does not exist
 log_outputs_util_en.c;1595

2513 Warning 2012/May/16 13:23:06 AppStartup Progress Monitor->SysServices::appStartupPart2 (192.168.1.222)
appStartup successful. appStartup Task will exit. appStartup.cpp;1320

2512 Warning 2012/May/16 13:23:06 ProcessorCoordinator Progress Monitor->ProcessorCoordinator::ProcessorCoordinator
Processor Coordinator source Logs initialized. ProcessorCoordinator.cpp;1037

2510 Warning 2012/May/16 13:23:06 AppStartup Unexpected Result->SysServices::appStartupPart2 (192.168.1.222)
Abnormal reset, cause: (0x103) SOFTWARE_RESET appStartup.cpp;1218

2508 Info 2012/May/16 13:22:50 OtpLogsClient Progress Monitor - SubscribeNewLog
Subscribed to * for Error Otp_Logs_Client.cpp;1391

2507 Info 2012/May/16 13:22:50 OtpLogsClient Progress Monitor - SubscribeNewLog
Subscribed to * for Warning Otp_Logs_Client.cpp;1391

2506 Info 2012/May/16 13:21:09 OtpLogsClient Progress Monitor - OtpLogsClientStop
OtpLogsClient stopped Otp_Logs_Client.cpp;1619

2505 Info 2012/May/16 13:21:08 OtpLogsClient Progress Monitor - OtpLogsClientStop
Stopping OtpLogsClient Otp_Logs_Client.cpp;1504

2504 Warning 2012/May/16 13:21:04 DBASRV DBASRV_HandleClientDisconnect->Error removing client ESM_DBA_Adaptor dbasrv.c;2106

2503 Warning 2012/May/16 13:21:04 DBASRV DBASRV_HandleClientDisconnect->Disconnect client: 0ESM_DBA_Adaptortask name: tDBasrv dbasrv.c;2088

2502 Warning 2012/May/16 13:21:01 HAL Unexpected Result->MsgSend()
Message send delayed hw_msg_sys_if.c;269

2501 Warning 2012/May/16 13:20:51 HAL Unexpected Result->MsgSend()
Message send delayed hw_msg_sys_if.c;269

2500 Warning 2012/May/16 13:20:50 ESM SX2KMaint SX2KCmdOut_ReceiveSignalHandler->SX2KCmdOut Client: Received SIGTERM - terminating sx2kcmdout.c;111

2499 Warning 2012/May/16 13:20:41 HAL Unexpected Result->MsgSend()
Message send delayed hw_msg_sys_if.c;269

2498 Warning 2012/May/16 13:20:40 IPMO IPMOTask()->Unrecognized event received by the IPMO task: 1.
 IPPhoneMgmt.cpp;3793

2497 Warning 2012/May/16 13:20:34 AppShutdown Progress Monitor->theOriginalAppShutdown
WARNING: System Shutdown about to start. Reset Backup task launched and will force a reset if shutdown fails. AppShutdown.cpp;184

2495 Warning 2012/May/16 13:20:30 HAL Calling appShutdown(eBrutalShutDown).
 port2vxworks.c;1186

2494 Warning 2012/May/16 13:20:30 HAL Emu68k thread exited.
 port2vxworks.c;1183

2493 Warning 2012/May/16 13:20:30 HAL Saved Panic Area To File.
 port2vxworks.c;1176

2492 Error 2012/May/16 13:20:29 HAL Unexpected Result->LogPanicArea()
Address Registers --- Exception 04 :Illegal Instruction
A0:   0060D9B0
A1:   01AC4778
A2:   01ACB118
A3:   01A4E6D8
A4:   00061EB4
A5:   00000000
A6:   00061E92
A7:   00049794 hw_restart.c;128

2491 Error 2012/May/16 13:20:29 HAL Unexpected Result->LogPanicArea()
Exception 04 :Illegal Instruction
PC:   004BDFC2
SR:   0008
D0:   000000BA
D1:   00000000
D2:   01AC0054
D3:   01AC4796
D4:   00000000
D5:   00000000
D6:   00000000
D7:   00000000 hw_restart.c;114

2490 Error 2012/May/16 13:20:29 HAL Unexpected Result->RestartPlatform()
Exception in sx2k code port2vxworks.c;1147

2489 Warning 2012/May/16 13:20:29 ViPER CViPERManager::ReloadingViPER -> Request made for viper to reload when platform is shutting down. Ignoring request.
 ViPERManager.cpp;1458

2488 Warning 2012/May/16 13:20:29 ViPER CViPERManager::ReloadingViPER -> Request made for viper to reload when platform is shutting down. Ignoring request.
 ViPERManager.cpp;1458

2487 Warning 2012/May/16 13:20:29 ViPER CASUViPER::MsgRouter(dx) -> Receive a MSG_RESET_LINKS Message. ASUViPER.cpp;325
2486 Warning 2012/May/16 13:20:29 ViPER CIPViPER::MsgRouter(dx) -> Receive a MSG_RESET_LINKS Message. IPViPER.cpp;1572

2485 Warning 2012/May/16 13:20:24 Call Control - Software DB (DBTable) error: First Key for table 234 not supported.
 log_outputs_util_en.c;1595

2484 Warning 2012/May/16 13:20:24 Call Control - Software DB (DBTable) error: First Key for table 190 not supported.
 log_outputs_util_en.c;1595

2483 Warning 2012/May/16 13:20:23 Call Control - Software DB (DBTable) error: First Key for table 234 not supported.
 log_outputs_util_en.c;1595

2482 Warning 2012/May/16 13:20:23 Call Control - Software DB (DBTable) error: First Key for table 190 not supported.
 log_outputs_util_en.c;1595

2481 Warning 2012/May/16 13:20:23 Call Control - Software DB (DBTable) error: First Key for table 234 not supported.
 log_outputs_util_en.c;1595

2480 Warning 2012/May/16 13:20:23 Call Control - Software DB (DBTable) error: First Key for table 190 not supported.

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Saving configurations error and self-restart
« Reply #6 on: May 16, 2012, 08:32:10 AM »
Looks like some type of database corruption to me.
you may have to do a data save / data restore and then try again.

Ralph

Offline eciroglu

  • Jr. Member
  • **
  • Posts: 41
  • Karma: +0/-0
    • View Profile
Re: Saving configurations error and self-restart
« Reply #7 on: May 16, 2012, 09:03:50 AM »
The PBX is started to use 1 day ago. It is still using factory default settings. May I forgot to do any parameter configuration in first usage?

Additionally, I have no App. Rec. ID now. I read that the PBX is coming with a default license includes 4 analog extension, 6 analog trunk line and 12 IP user. Is an App. Rec. ID needed to use with default license?

Thanks.

Volkan,

Offline Mattmayn

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1069
  • Country: vi
  • Karma: +14/-0
    • View Profile
Re: Saving configurations error and self-restart
« Reply #8 on: May 16, 2012, 09:41:31 AM »
You must have an ARID before anything on the system will work. The base license does have some users in it but you must apply the base to the hardware.

Offline eciroglu

  • Jr. Member
  • **
  • Posts: 41
  • Karma: +0/-0
    • View Profile
Re: Saving configurations error and self-restart
« Reply #9 on: May 17, 2012, 05:04:11 AM »
For this moment, can I use the PBX (with 4 ONS 6 LS 12 IP User) without ARID? If your answer is yes, how? If your answer is no, what must I do to be able to use the PBX?

Thanks.

Volkan,

Offline bluewhite4

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1041
  • Country: us
  • Karma: +20/-0
    • View Profile
Re: Saving configurations error and self-restart
« Reply #10 on: May 17, 2012, 10:02:38 AM »
No, you can't used the system without an ARID. You must purchase a base package from a Mitel dealer, and they will create an ARID, and assign the base package to it through the Mitel AMC.


 

Sitemap 1 2 3 4 5 6 7 8 9 10