Hi
Maybe this isn't the right post.
I'm playing with OXE to set CS duplication. There are two CS hosted on vmware. Keep in mind there's not a problem at the customer. It's a test.
So, I set the two CS with the following settings:
Main: 192.168.0.250/24
Twin: 192.168.0.251/24
Reading the CS duplication databook, it asks us to set CPU redundancy. Is this done on the mai CPU or ion the twin CPU? The databook isn't clear.
Regards.
Trying to set CS duplication
Trying to set CS duplication
Enio Eltz Filho
ACFE OXE R12
ACFE OXO C R3
ACFE OXE R12
ACFE OXO C R3
Re: Trying to set CS duplication
Hi enio.eltz
You should have declared the a & b CPU when setting up netadmin, therefore cpu a should look like:
cpu a: 192.168.0.250
When main: 192.168.0.252 (or whatever you wish)
cpu b: 192.168.0.251
The opposite is true for cpu b:
cpu b: 192.168.0.251
When main: 192.168.0.252 (as declared on cpu a)
cpu a: 192.168.0.250
As you may notice, you have to do this on both CPU's
You should have declared the a & b CPU when setting up netadmin, therefore cpu a should look like:
cpu a: 192.168.0.250
When main: 192.168.0.252 (or whatever you wish)
cpu b: 192.168.0.251
The opposite is true for cpu b:
cpu b: 192.168.0.251
When main: 192.168.0.252 (as declared on cpu a)
cpu a: 192.168.0.250
As you may notice, you have to do this on both CPU's
We don't see things the way they are; we see things the way we are!
Re: Trying to set CS duplication
Hi Patmul39
Thanks a lot for your answers, now the things seem clear. I will do the settings this week.
Thanks a lot for your answers, now the things seem clear. I will do the settings this week.
Enio Eltz Filho
ACFE OXE R12
ACFE OXO C R3
ACFE OXE R12
ACFE OXO C R3
Re: Trying to set CS duplication
Hi
It seems I have a CS duplication working here. But I would like to know more informations about it.
I did the settings in the netadmin as patmul39 asked. So, now I have the following settings:
CPU A: 192.168.0.251
CPU B: 192.168.0.252
When MAIN for both CS: 192.168.0.250
With these @IP I did the settings in the CPU A (starting the telephone, some boards, some extensions).
In the CPU B, with telephone stopped, I ran mastercopy to get everything from CPU A, it worked fine. I set autostart telephone and shutdown on both CPUs.
After this I only make settings with @IP 192.168.0.250, where I will have these modifications on both CPUs, and it seems to be running very well.
Now, if I need to run mastercopy again, I will need to stop telephone in the CPU b, am I right? I read in this forum something about this and I think I'm right.
So, I did a test, I turned CPU A off, CPU B became main. When does this CPU B run as main until? When CPU A turned on, it remained as stand-by, is this the normal behaviour?
And the last question, with bascul command. I ran it in the @IP 192.168.0.250, so CPU A restarted and CPU B got main. Is it the right behaviour?
Thank you very much.
It seems I have a CS duplication working here. But I would like to know more informations about it.
I did the settings in the netadmin as patmul39 asked. So, now I have the following settings:
CPU A: 192.168.0.251
CPU B: 192.168.0.252
When MAIN for both CS: 192.168.0.250
With these @IP I did the settings in the CPU A (starting the telephone, some boards, some extensions).
In the CPU B, with telephone stopped, I ran mastercopy to get everything from CPU A, it worked fine. I set autostart telephone and shutdown on both CPUs.
After this I only make settings with @IP 192.168.0.250, where I will have these modifications on both CPUs, and it seems to be running very well.
Now, if I need to run mastercopy again, I will need to stop telephone in the CPU b, am I right? I read in this forum something about this and I think I'm right.
So, I did a test, I turned CPU A off, CPU B became main. When does this CPU B run as main until? When CPU A turned on, it remained as stand-by, is this the normal behaviour?
And the last question, with bascul command. I ran it in the @IP 192.168.0.250, so CPU A restarted and CPU B got main. Is it the right behaviour?
Thank you very much.
Enio Eltz Filho
ACFE OXE R12
ACFE OXO C R3
ACFE OXE R12
ACFE OXO C R3
Re: Trying to set CS duplication
"Now, if I need to run mastercopy again, I will need to stop telephone in the CPU b, am I right?" - Yes, you can do this (from the standby CPU) by logging into swinst, easy menu, option 7. Note that this will disable your autostart on that cpu so you will need to change it again.
"So, I did a test, I turned CPU A off, CPU B became main. When does this CPU B run as main until? When CPU A turned on, it remained as stand-by, is this the normal behaviour?" - Yes, probably because you have not declared a reference media gateway.
"..with bascul command. I ran it in the @IP 192.168.0.250, so CPU A restarted and CPU B got main. Is it the right behaviour?" - Not exactly. It is correct that the bascul causes the main to restart and the standby to take over but it is recommended to do this from the cpu that is running as standby. So if cpu A is main, telnet to b (.0.252 IP) and run the command from there.
"So, I did a test, I turned CPU A off, CPU B became main. When does this CPU B run as main until? When CPU A turned on, it remained as stand-by, is this the normal behaviour?" - Yes, probably because you have not declared a reference media gateway.
"..with bascul command. I ran it in the @IP 192.168.0.250, so CPU A restarted and CPU B got main. Is it the right behaviour?" - Not exactly. It is correct that the bascul causes the main to restart and the standby to take over but it is recommended to do this from the cpu that is running as standby. So if cpu A is main, telnet to b (.0.252 IP) and run the command from there.
We don't see things the way they are; we see things the way we are!
Re: Trying to set CS duplication
Hi,
- You're right, to make a mastercopy you need to stop the phone application on the stand by.
- After a bascul from CPU A to CPU B, CPU B will remain in main role until you make a manual bascul or you lost the CPU B.
- The main ip adress (192.168.0.250) follow the CPU wich is main.
Turlupin
- You're right, to make a mastercopy you need to stop the phone application on the stand by.
- After a bascul from CPU A to CPU B, CPU B will remain in main role until you make a manual bascul or you lost the CPU B.
- The main ip adress (192.168.0.250) follow the CPU wich is main.
Turlupin
Sorry for my english .... 
Re: Trying to set CS duplication
Hi
Thanks a lot for you spent your time with me. Now it is very clear.
Thanks a lot
Thanks a lot for you spent your time with me. Now it is very clear.
OK, it is understood."Now, if I need to run mastercopy again, I will need to stop telephone in the CPU b, am I right?" - Yes, you can do this (from the standby CPU) by logging into swinst, easy menu, option 7. Note that this will disable your autostart on that cpu so you will need to change it again.
Ok, I ran bascul from stand-by CPU, everything is right."..with bascul command. I ran it in the @IP 192.168.0.250, so CPU A restarted and CPU B got main. Is it the right behaviour?" - Not exactly. It is correct that the bascul causes the main to restart and the standby to take over but it is recommended to do this from the cpu that is running as standby. So if cpu A is main, telnet to b (.0.252 IP) and run the command from there.
I set MG 2 as reference MG, mgr --> MG --> review/modify --> main shelf address 2 --> reference : yes. I will do some tests.Yes, probably because you have not declared a reference media gateway.
Thanks a lot
Enio Eltz Filho
ACFE OXE R12
ACFE OXO C R3
ACFE OXE R12
ACFE OXO C R3
Re: Trying to set CS duplication
Enjoy 
We don't see things the way they are; we see things the way we are!
