Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Watch4net APG 5: Encrypting the APG password in the configuration (*.conf) files for SMARTS and SMARTS-Health (374538)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 4095Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Watch4net APG 5: Encrypting the APG password in the configuration (*.conf) files for SMARTS and SMARTS-Health
How to encrypt the Watch4net APG 5 password in the SMARTS and SMARTS-Health configuration (*.conf) files

Resolution

Watch4net provides a tool with APG to encrypt passwords called crypt-password.

To encrypt the password in the conf files for SMARTS and SMARTS-Health, do the following:

1.    Generate the secure password with the crypt-password tool (see EMC knowledgebase solution article  Link Error: ).

2.    Look in /opt/APG/APG-Backend/conf/collecting.xml  for the <collectors> block. There, look for the <collector> with SmCollectorDiscovery or SmDiscovery in the <classname> block.

A. SmCollectorDiscovery

If you are using the Smarts AutoDiscovery, the file to modify will be/opt/APG/APG-Backend/conf/sm-discovery.xml:

<authentication>
<broker>10.10.10.10:426</broker>
<domains refresh-period="240">
<default-username>admin</default-username>
<default-password>{Encrypted password generated using APG crypt-password tool}</default-password>
</domains> </authentication>

B. SmDiscovery

In the case of specific domains configured, each domains will have its own configuration file. The filename is included in the block <config-file>:

<collector enabled="true" name="INCHARGE-AM-PM2" next="Cache">
<classname>com.watch4net.apg.v2.collector.plugins.SmCollector</classname>
<config-file>conf/smarts-INCHARGE-AM-PM2.xml</config-file>
</collector>

Replace the password in each SMARTS domain's configuration file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE config SYSTEM "smarts.dtd">
<config>
<domain>INCHARGE-AM-PM2</domain>
<broker>localhost:426</broker>
<username>admin</username>
<password>{Encrypted password generated using APG crypt-password tool}</password>
<group>group</group>
<period>240</period>
<thread pool-size="3" />
<dm-connection pool-size="2" keep-connection="false" creation-grace-time="100" />
<indicators select="both">conf/pm.xml</indicators>
<properties refresh="00:00/86400" send-on-refresh-only="false" />
<smooth-factor>0.5</smooth-factor>
</config>

C. SMARTS-Health

If you are using a per domain configuration and you need the SMARTS Health metrics, apply the same change to the SMARTS Health configuration file. The default name is smarts-pm-health.xml:

<collector enabled="true" name="INCHARGE-AM-PM2-Health" next="Cache">
<classname>com.watch4net.apg.v2.collector.plugins.SmCollector</classname>
<config-file>conf/smarts-pm-health-2.xml</config-file>
</collector>

Replace the password in each SMARTS-Health domain's configuration file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE config SYSTEM "smarts.dtd">
<config>
<domain>INCHARGE-AM-PM2</domain>
<broker>localhost:426</broker>
<username>admin</username>
<password>{Encrypted password generated using APG crypt-password tool}</password>
<group>group</group>
<period>240</period>
<thread pool-size="3" />
<dm-connection pool-size="2" keep-connection="false" creation-grace-time="100" />
<indicators select="both">conf/pm-health.xml</indicators>
<properties refresh="00:00/86400" send-on-refresh-only="false" />
<smooth-factor>0.5</smooth-factor>
</config>

3. Execute /opt/APG/bin/apg-collector restart.

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 - Watch4Net/M&R

Take Our Survey

Support Assistant