Avaya Primary & Secondary server VM Pros not syncing, VM Pro failover not working. 1

[Maducas]

Hi Guys,

I have a customer that has an IP Office primary server & secondary server on release 11.0.4.4
The 2 VM Pros are not syncing via SMTP. I believe I have set it up correctly after following the documentation, but the sync never starts. I see no trace of it in the debugtrail.txt on either server and nothing shows up in the distributed voicemail section.

I have opened an SR with Avaya for them to help, they first sent me a link to this support notice (

https://support.avaya.com/ext/index?page=content&id=SOLN240526)

and told me to ensure my SMTP settings are setup the same way in this link. I have done this and there is still no sync between the servers. Avaya have now told me to redeploy the 2 servers as brand new servers and see if that fixes the issue -_-
I have told Avaya that the customer can't accommodate a redeploy of both servers at the moment and this is also a pretty new install, they ignore this and continue to ask me to redeploy the servers.

I was wondering if anyone has any ideas on anything else I could try to get these servers syncing?

Customer has confirmed there is no firewall or port blocking between the 2 servers and I have verified that port 25 is open to both servers.

Any help would be greatly appreciated.

 

[TouchToneTommy]

Try port 2525 instead of 25

 

[Maducas]

@TouchToneTommy sorry I forgot to mention this, I have already tried using port 2525 as well. Same result, I still get no sync.

 

[Okkie26]

Did you setup the secondary vm pro as backup server in IPO manager?

 

[snowman50]

I had to do a full power down on the primary in order to get the secondary to sync up for failover correctly.


Look at this site

https://www.ipofficeassistance.com/tips/page/14/

I set it up like this and worked ok

Like I said for the first time I need to do a fulll power down of the primary.
After that just unplugging the network cable was sufficient to generate a fail over.

Also look at this thread

thread940-1808500

 

[Maducas]

@Okkie26 Yeah I have set the secondary as backup in Manager and ticked the resiliency options as well.

@snowman50 I did originally setup the SMTP as per the ip office assistance Avaya support told me it was wrong and to change it.
I'm waiting on a time frame from the customer to do a full power down of both servers to see if it will start syncing when they power back up.

I'll also try what's suggested in the thread you linked and see if that works.
I'll update this post after I try everything and let everyone know what happens.

Thanks again for your suggestions.

 

[Maducas]

Just in case anyone stumbles across this thread that has the same issue.
I used the info in the thread provided by @snowman50 above.

I changed the SMTP details for the servers to the following and they started syncing:

Primary server VM SMTP sender:
Mail Domain: IP address of the primary VM server
Mail server: IP address of the primary VM server
port:25
sender: vmpro@IP address of the primary vm server
Main VM SMTP receiver:
internal
port: 25
Domain: ip address of the primary VM server

Secondary VM SMTP sender:
Mail Domain: ip address of the secondary VM server
Mail server: ip address of the primary VM server
Port: 25
Sender: vmpro@IP address of the primary vm server
Remote SMTP Receiver:
internal
Port: 25
Domain: ip address of the secondary VM server


I did also WINSCP in to the Secondary server and went to opt/vmpro and checked the syncmetadata.ini file and saw there was an entry for 172.0.0.1 in there.
This entry wasn't in the syncmetadata.ini file on the Primary server.
Not sure where it came from, perhaps it was a typo from one of our other techs when they tried using 127.0.0.1.
Anyway I deleted the 172.0.0.1 entry and re-uploaded the file to the secondary. So the only IP addresses in this file were the primary and secondary server IPs.
Not sure if this contributed to getting the sync working, but I thought I'd mention it anyway.

Thanks everyone for your time and help.

 

[snowman50]

Main thing is it’s working now.
Glad it’s sorted