Setting up and Configuring Hierarchy and Replication — ITMS 8.7.x and Higher

Products

• IT Management Suite

Issue/Introduction

Setting up a Notification Server (NS) hierarchy allows multiple Symantec Management Platform (SMP) servers to share configuration policies, data, and management tasks across single or multi-domain environments. Establishing a Parent-Child relationship streamlines central administration, enabling the Parent SMP Server to distribute policies downward while Child SMP Server nodes send inventory, patch status, and event data back up the hierarchy.

This article provides the step-by-step procedure for configuring a hierarchical relationship between two SMP Servers, specifying return credentials, and establishing differential or complete replication schedules.

Environment

IT Management Suite (ITMS) 8.7.x, 8.8.x

Component: Symantec Management Platform (SMP) — Hierarchy & Replication

Cause

How It Works

                     ┌──────────────────────────────┐
                     │          Parent NS           │
                     │  (Central Policy / Reports)  │
                     └──────────────┬───────────────┘
                                    │  ▲
              Hierarchy Replication │  │ Replication
              (Policies / Data)     │  │ (Status / Inventory)
                                    ▼  │
                     ┌──────────────────────────────┐
                     │           Child NS           │
                     │    (Remote Site / Domain)    │
                     └──────────────┬───────────────┘
                                    │
                       Package Sync │ (Required)
                                    ▼
                     ┌──────────────────────────────┐
                     │        Package Server        │
                     └──────────────────────────────┘

1. Policy & Data Distribution: The Parent SMP Server replicates policies, software resource definitions, and task items down to one or more Child SMP Servers.
2. Status Reporting: Child SMP Servers execute local management operations and replicate aggregated status, inventory, and patch compliance data back up to the Parent NS.
3. Mandatory Package Server Requirement: A designated Package Server must be assigned and functional within the site for both the local and remote SMP Servers. Package Servers handle resource file delivery during replication; hierarchy establishment fails if a Package Server is missing at either site.
4. Replication Types:

• • Differential Replication (Default): Replicates only changes (deltas) made since the last run. Runs on a staggered schedule to optimize network usage.
  • Complete Replication: Full sync of all database items in scope. Resource-intensive; intended only for initial synchronization or database recovery scenarios.

Prerequisites & Diagnostic Checklist

Verify the following conditions before establishing a hierarchy relationship:

• Package Server Availability: Confirm that both local and remote SMP Servers have at least one assigned Package Server within their respective sites.
• Network Connectivity: Ensure bi-directional communication over HTTP (Port 80) or HTTPS (Port 443) between both SMP Servers.
• Administrative Credentials: Prepare service or administrative account credentials with Symantec Administrators rights on both local and remote servers.
• Stable Application Accounts: Ensure the SMP Server application credentials are dedicated, stable accounts with passwords set not to expire frequently. If an application account password becomes invalid, update it before stablishing the Hierarchy. Changing the Application Identity account password (KB 156852)

Resolution

NOTE: 
Review our official online documentation for more details about how to accomplish your initial setup.

Setting up a Hierarchical Relationship Between Two Notification Server Computers

Implementing Notification Server hierarchy

About Notification Server hierarchy

Hierarchy and replication requirements

1.Open Hierarchy Management:

In the Symantec Management Console, navigate to Settings > Notification Server Management > Hierarchy.

2.Initiate Node Addition:

1. Select the Topology tab.
2. Right-click the local Notification Server node in the topology tree.
3. Select Add > Parent (if connecting to an upstream Parent SMP) or Add > Child (if adding a downstream Child SMP).

3.Configure Remote Server Connection:

1. 1. In the Add Hierarchy Node Wizard, on the Notification Server page, enter the following details for the remote server:
      • Name / FQDN
      • URL (include port and HTTPS protocol prefix if using non-default port configurations, e.g., [https://remotens.domain.com:443](https://remotens.domain.com:443))
      • Credentials: User name and password for a Symantec Administrator account on the remote Notification Server.
   2. Click Advanced.

4.Set Return Credentials:

1. In the Return Credential Setting dialog box, specify the Symantec Administrator account credentials that the remote Notification Server will use when initiating connection back to the local SMP Server.
2. Click OK to close the dialog.
3. Click Next in the wizard.

5.Configure Replication Schedules:

1. Configure the Differential Replication schedule (enabled by default). Adjust start times to stagger replication jobs across multiple child nodes to prevent network congestion.
2. Leave Complete Replication disabled unless an initial full synchronization is specifically required.
3. Click Next.
   

        Managing shared schedules

        Configuring a schedule

6.Confirm and Establish Relationship:

1. Review the summary configuration details on the Confirm Settings page.
2. Click Finish.

Note: The local SMP Server immediately attempts to connect to and validate the remote server. If either site lacks an assigned Package Server, the wizard returns a validation error and the relationship will not be established.

 

Verification

To confirm that the hierarchical relationship and communication are functioning correctly:

1. Console Status:
   Navigate to Settings > Notification Server Management > Hierarchy. Verify that the remote server node appears correctly under the Topology tab hierarchy tree with a status of Active.
2. Replication Job Execution:
   • Select the Replication tab.
   • Highlight the target server node and click Run Differential Replication Now.
   • Verify that the status transitions from Running to Completed Successfully.