Configure one Smarts SAM server to connect and subscribe to events from another Smarts SAM server .
book
Article ID: 327721
calendar_today
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
This Article explains how to configure one Smarts SAM server to connect and subscribe to events from another Smarts SAM server.
Smarts SAM: How do you configure one Smarts SAM server to connect and subscribe to events from another Smarts SAM server ?
How do you build a hierarchical Smarts Service Assurance Manager (Smarts SAM) server architecture?
Environment
SMARTS - 10.1.x
Resolution
Configuring one Smarts SAM server to connect and subscribe to events from another Smarts SAM server is the same as configuring any other underlying domain that connects to a Smarts SAM server.
There is already a dxa-sam.conf section in the ics.conf file for this purpose.
To configure one Smarts SAM server to connect and subscribe to the events generated by another, do the following:
On the Smarts SAM server that will subscribe to the events generated by the other Smarts SAM server (the "top" Smarts SAM server in the hierarchy), open the ics.conf file for editing as follows:
Remove the code comment indicators (#) from the DomainType definition for INCHARGE-SA section of the file.
The following example shows this section with the comments removed (you should leave the "Hookscript" statement commmented out unless your system is using one):
If both Smarts SAM servers are on different brokers, configure the Name variable to bypass the brokers as follows (see Note statement):
<HOST>::<PORT>/SERVER_NAME
OR
<IP>::<PORT>/SERVER_NAME
The following shows an example of the Name variable in this section configured to use host name foucs, port number #####, and server name INCHARGE-SA2.
# DomainType definition for INCHARGE-SA. DomainType { ConfFile = "dxa-sam.conf"; MinimumCertainty = 0.24; SmoothingInterval = 65; # HookScript = "ics/dxa-sample-nl-hook.asl"; Name = "foucs::port number ####/INCHARGE-SA2"; }
Save and close the ics.conf file.
To implement the configuration changes (the Smarts SAM server does not need to be restarted), run the ICS_RemoteConfig.asl as follows:
To work in this configuration, both Smarts SAM servers must be reachable by each other over the network. The port number can be found by running brcontrol as follows: