When Geographic Redundancy is configured, on Communication Manager, the system registers the IP address of the primary or secondary System Manager that manages Communication Manager.
Before you begin
On the Manage Elements page, register both the IP addresses of the duplex Communication Manager pair for System Manager to handle the notify sync messages.
Note:
In a duplex configuration, you cannot use the virtual address on Communication Manager.
Procedure
On the System Manager web console, click Services > Inventory.
In the navigation pane, click Manage Elements.
Select a Communication Manager system.
In the Attributes section, select Enable Notifications.
When you enable notify sync, the system sends a register command to Communication Manager for registering the IP address of System Manager as a syslog server. The system sends all administrative changes that you make on Communication Manager to System Manager.
To verify that the notify sync feature is successfully enabled, do the following:
Using an SSH client, log in to Communication Manager as sroot.
At the prompt, type sudo /opt/ws/cmSyslogConfig --iptcmquery.
The system displays the details of the registration.
When the notify sync is nonoperational, and when Geographic Redundancy is set up on System Manager, complete the following:
Ensure that you have root permissions to Communication Manager to edit the file.
Using an SSH client, log in to Communication Manager as root.
Open the /etc/syslog.conf file.
Add hash (#) at the beginning of the following secondary System Manager related entries in the file:
To restart the rsyslog service on Communication Manager, type service rsyslog restart.
Notify sync becomes operational.
If the primary System Manager becomes nonoperational, and you want to manage Communication Manager by using the secondary System Manager, complete the following:
In the /etc/syslog.conf file, replace the primary System Manager IP address with the secondary System Manager IP address.