Avaya System Manager Geo-redundancy: Service Impacting?

[Boulevard99]

Hi all,

I have a question on the GeoRedundancy feature in SysMgr. We have two ASM's.

Currently, the GR Replication. set to disabled. I don't know why it is, as I am new to this company, and not sure of the history.

My question is: Would simply re-enabling it cause any service affecting impact? What exactly would happen if I did? Rather what would the ASM's do? Would they just sync up and all is great? Or would they go thru some process that would affect service and wipe out data and whatnot?

Thanks!!

 

[jimbojimbo]

Before changing anything there are a couple of items to look at.
1. Are both SMGRs at the exact same release level? If not then no Geo-Redundancy.
2. Do you have DNS which will allow you to resolve from both SMGRs? If you have any capital letters in the hostname you MUST have DNS. When you setup GR the hostname is configured in all lower case. Lookup via the hosts file will fail and GR will fail if you have any capital letters and no DNS.
3. Do both SMGRs have the exact same GR vFQDN? the smgr-properties.properties file must match. You can't just edit the file to make it match. If you need to change it look in the admin manual at the FQDN shell commands.
4. Are your certificates setup correctly. I assume so since you are stating the redundancy is disabled which means the initial trust was extablished. The original documentation on certificates did not cover all 4 of the certificate profiles. If you didn't update the 4th one everything works except GR.

I would probably convert to standalone then on the secondary reconfigure GR just to make sure it is clean and then enable replication.

 

[Boulevard99]

Wow. Looks like I have quite a bit to look at and validate.

Thank you! This is great info that will help me determine the root of the issue and why it's in its current state.

 

[Boulevard99]

To jimbojimbo. Following up on this thread. To answer your questions:

1. Are both SMGRs at the exact same release level? If not then no Geo-Redundancy. - Yes. Both are the exact same release.

2. Do you have DNS which will allow you to resolve from both SMGRs? If you have any capital letters in the hostname you MUST have DNS. When you setup GR the hostname is configured in all lower case. Lookup via the hosts file will fail and GR will fail if you have any capital letters and no DNS.
- Yes I was able to get assistance confirming this.

3. Do both SMGRs have the exact same GR vFQDN? the smgr-properties.properties file must match. You can't just edit the file to make it match. If you need to change it look in the admin manual at the FQDN shell commands. - Yes the FQDN's match up.


4. Are your certificates setup correctly. I assume so since you are stating the redundancy is disabled which means the initial trust was established. The original documentation on certificates did not cover all 4 of the certificate profiles. If you didn't update the 4th one everything works except GR. - I wasn't able to confirm this yet.


Now, my last question is: If I proceed with switching the Primary to Stand Alone and then reconfigure GR on the Secondary and then enable replication, will this be service affecting? Can I run this during business hours without impact?

 

[Boulevard99]

Btw: Got it resolved. It was in fact the Date/Time setting that was off.

And performing the replication will not affect service. Thanks!!!