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 to sync only selected classes/objects from an underlying domain so that only those selected classes/objects appear in the topology (322878)

Last Updated: 12/17/2018Categories: How toTotal Views: 2635Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

This article explains how to achieve the following results in the product/environment:

How to sync only selected classes in the SAM from underlying domain

How to make the Smarts topo sync between SAM and an underlying domain happen only for selected classes/objects

How to use the dxa file to allow only certain classes/objects to appear in the Smarts SAM topology

To ensure that only certain selected classes/objects appear in the Smarts SAM topology, the topology synchronization (topo sync) needs to be configured accordingly. This can be done by configuring the dxa file that is responsible for the topo sync between SAM and underlying domain. The following section presents an example that shows how to do this for a Host object. The same procedure logic can be applied on any class such as Routers, Switches, Firewalls, and so on.

Configuration Example
Consider an environment that has three Hosts available in Smarts IP topology named "Host1", "Host2", "Host3". To configure the dxa file so that only "Host1" is part of the topo sync, you would do the following:

Open the dxa-conn-perf.conf using sm_edit as follows:

<BASEDIR>/SAM/smarts/bin>sm_edit <BASEDIR>\SAM\smarts\conf\ics\dxa-conn-perf.conf

Find the following lines:

#       Remote Name of Class/Property           Mapped Name of Class/Property
server INCHARGE-AM-PM

Remove all the class entries according to your requirement, starting from class   ICIM_UnitaryComputerSystem until the start of the # Subscriptions section.

Add following entries in the class section:

class Host
peek Name *Host1*

Save and close the dxa-conn-perf.conf file.

Run a reconfigure operation on the SAM domain.

After the reconfigure operation completes, open the Topology Builder for the SAM domain, and you would see only "Host1" available under the Host class.

Related Information

IMPORTANT! The "peek" option only applies to the topology browser and map consoles, it is not applicable to notifications. You will still receive notifications from other classes/objects in the Smarts SAM console even after the above configuration change is made.

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