Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts SAM: How do you configure one Smarts SAM server to connect and subscribe to events from another Smarts SAM server ? (319284)

Last Updated: 3/22/2024Categories: How toTotal Views: 1822Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

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?

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:

<BASEDIR>/SAM/smarts/bin/sm_edit conf/ics/ics.conf

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):

#  DomainType definition for INCHARGE-SA.
DomainType
{
ConfFile          = "dxa-sam.conf";
MinimumCertainty  = 0.24;
SmoothingInterval = 65;
#        HookScript        = "ics/dxa-sample-nl-hook.asl";
Name              = "INCHARGE-SA2";
}

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 13838, 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::13838/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:

<BASEDIR>/SAM/smarts/bin/sm_adapter -s <global_manager> ics/ICS_RemoteConfig.asl

Related Information

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:

<BASEDIR>/SAM/smarts/bin/brcontrol

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant