Setting up Hierachy in ITMS 8.6.x+
Article ID: 197480
Updated On:
Products
Issue/Introduction
I need to setup a Hierarchy for some servers we have in another domain.
Environment
Release: 8.6.x +
Component: Hierarchy
Resolution
Setting up a Hierarchical Relationship Between Two Notification Server Computers
Last Updated August 14, 2020
You can set up a hierarchical relationship (either Parent of or Child of) between your Notification Server computer and a remote Notification Server computer. You need to specify the name, URL (which should include any non-default port configurations or HTTPS), and access details of the remote Notification Server computer. You also need to provide the access details of your local Notification Server computer. By default, the hierarchy replication schedule staggers the replication between each pair of Notification Server computers. You can change the replication schedule to suit your requirements, but you should ensure that replication staggering is maintained.
Both Notification Server computers must have a package server available within their respective sites. The package server is required for performance reasons. You cannot create a hierarchical relationship between two Notification Server computers if either one does not have a package server available.
Notification Server application credentials should be stable and not be changed regularly like some user account passwords. If the Notification Server computer application account password becomes invalid, a message is displayed in the console. The message prompts you to use the AexConfig command-line tool to make the necessary updates.
This task is a step in the process for implementing the Notification Server hierarchy.
Implementing Notification Server hierarchy
To set up a hierarchical relationship between two Notification Server computers
In the Symantec Management Console, on the Settings menu, click Notification Server Management > Hierarchy
On the Hierarchy Management page, on the Topology tab, right-click your Notification Server, and then click the appropriate option:
Add > Parent
Add > Child
In the Add Hierarchy Node Wizard, on the Notification Server page, enter the name, URL, and access credentials of the remote Notification Server computer. The access credentials must be a Symantec Administrator account or equivalent account on the remote Notification Server computer.
Click Advanced
In the Return Credential Setting dialog box, specify the Symantec Administrator (or equivalent) account that the remote Notification Server computer uses to communicate with the local Notification Server computer, and then click OK.
In the Add Hierarchy Node Wizard, click Next.
On the Replication Schedules page, set up the differential and the complete replication schedules, and enable those that you want to use on the Notification Server computer, and then click Next.
By default, only the differential replication schedule is enabled. Complete replication is rarely used because it puts a heavy load on the Notification Server computer, but you can enable it when necessary. You should schedule the replication at the times that do not clash with replication schedules on other Notification Server computers in the hierarchy.
On the Confirm Settings page, verify that the settings are correct, and then click Finish.
The local Notification Server computer uses the specified information to locate and verify the remote Notification Server computer and set up the appropriate hierarchical relationship with it.If the remote Notification Server computer does not have a package server available within its site, the verification fails and the hierarchical relationship cannot be established.
Feedback
