Alcatel Unleashed

OXE 6.0.1 /CCD/ACR

At times I have MAO errors regarding agents like:

04/07/07 15:48:05 000001S|--/--/-/---|=2:2686=MAO err on stand-by CPU: err 2137 Ope ope 106 Obj ACTION_ACDV2 Inst : 1 1 1 1 8672
04/07/07 15:36:52 000001S|--/--/-/---|=2:2686=MAO err on stand-by CPU: err 2137 Ope ope 106 Obj ACTION_ACDV2 Inst : 1 1 1 1 8672

Which are solved doing a mastercopy.
The procedure I have been suggested to do a mastercopy is the following:

1. Stop the telephone on stdby CPU (swinst, option1, option7)
2. lanch the mastercopy command from the stby CPU with the option -noruntel. This does not launch the telephony application
3. Start the telephone (swinst, option1, option8) (telephone is started after another reset)

My feeling is that during the subsequent reset of the stby CPU, changes made to the main CPU are not reflected on the stdby CPU.
I have lots of agents that do logon/logoff etc. all the time and I end up with an inconsistent database again.

Questions:
1. What is causing the databases becoming inconsistent in time. Do I have some problem in the system?
2. Is the procedure above indeed the correct (or best) way to perform mastercopy. If not, what is?
3. What might be the reason of suggesting -noruntel and start the telephonone afterwards instead of just omitting the -noruntel option?

Thanks in advance

jigsaw wrote:
Question:

2. Is the procedure above indeed the correct (or best) way to perform mastercopy. If not, what is?


Thanks in advance

I think the best way to do it is:

1. Login swinst on standby CPU
2. Switch off autostart (swinst > expert menu > option 6 > option 2
3. shutdown -r now on standby
4. when standby is backup (without telephony) login mtcl and then in to swinst
5. go to expert menu
6. go to 'cloning & duplication' menu
7. go to database cloning option
8. accept all options with 'y'
9. accept the option to start telephony at end of cloning

This way, mao will be suspended until both CPU's are running (main & Standby) so nothing can change in the meantime.

If I can say something here ...

Instead of turning off the auto-start, and do a reboot -r , simply go to the easy meny, then stop the phone application (7).

Regarding the copy, I would not recommend to answer YES at the "copy linux data" question.
This will duplicate data that should be unique on each CPU.

F.

frank wrote:If I can say something here ...

Instead of turning off the auto-start, and do a reboot -r , simply go to the easy meny, then stop the phone application (7).

Fair comment

frank wrote: Regarding the copy, I would not recommend to answer YES at the "copy linux data" question.
This will duplicate data that should be unique on each CPU.
F.

Other than the static IP addresses (which mastercopy doesn't screw up), or the case of spatial redundancy, what else needs to be unique?

The database cloning option with autostart does in fact what I want, namely lock the MAO until all is up and running.

Done that yesterday. However, next morning I still get MAO errors:

05/07/07 09:03:22 000001S|--/--/-/---|=2:2686=MAO err on stand-by CPU: err 2113 Ope ope 106 Obj ACTION_ACDV2 Inst : 1 1 1 1 8621

What might be the cause?

By the way, I only have done the database cloning, not the linux or delivery options.

hi jigsaw,

2686=MAO err on stand-by CPU>>>>>what is the solution for this problem?

mastercopy >>> I did that

but the problem does not end!

thanks

Mastercopy not help or problem starts again after some time?
May be you have problem comes from management for signaling mode in shelf 0 (Nx64)?

For big duplicated PBX - better to use IO2 (or Ethernet).

hi Vad

I know this is an old post but are you saying that signalling mode for duplicated cpu is better to be using io2 or ethernet and not n64? I have some systems with 5000 or more users but they are all using n64 and i do see this incident sometimes

It can be bug in OXE SW R6.0.1 without real possibility to solve without upgrade to newer version