Content Comparison

Snare Agents

...

1. Choose the Web Site document you want to edit and click Edit Document.
2. Click the Domino Web Engine tab. Under "Conversion/Display", the default settings are: Default lines per view page: 30 Maximum lines per view page: 1000. These values should be configured as follows: Default lines per view page: 250 Maximum lines per view page: 0

User and group information will be used by user/group snapshot objectives.

...

To set up an Agent Management objective, open one of the Remote Management objectives (the default is Manage Agents) and go to the Configuration section (click 'Configure' in the top icons menu).

Snare Agent Type

Specify the type of the Snare Agents to be managed through this objective. Different agent versions have been grouped based on Operating System and major version changes to prevent incompatible configurations from being compared and saved. Remember, you can easily Clone the objective for each type of Snare Agent you use.

...

For example, the "Snare Agent for Linux (1.x.x - 2.1.x)" type will not match a "Snare Agent for Windows" or even a "Snare Agent for Linux v2.2.0" Agent. However, it will match a "Snare Agent for Linux v2.1.0" or a "Snare Agent for Linux v1.8.2" Agent.

Hostname Filter

To help filter the Agents being managed through the objective, a hostname filter can be specified that will restrict the managed Agents to those matching the filter. The filter supports by default * as a wildcard, but this can be changed to support Regular Expressions if the option is enabled.

...

For example, a filter of '*.intersectalliance.com' will manage 'agent001.intersectalliance.com', but not 'agent002.dni.gov.au'.

Version String filter

To further restrict the managed agents, a version string can be specified using the same matching rules as the Hostname Filter (i.e. * wildcard, or regular expressions). This filter is based off the reported version from the agent, which it can only obtain by attempting to contact the agent during each regeneration.

...

Non-reporting Agents

Snare Agents that do not report to the Snare Server can be specified within the Non-reporting Agents box. This will add them into the list of hosts to query and be managed if online.

...

Adding an IP address range inserts all of the specified IP addresses into the Non-reporting Agents field. So it is easy to remove specific IP addresses from the middle of the range as required.

Alternate Passwords

The objective, by default, uses the Agent password specified in the Configuration Wizard when it attempts to communicate with each Agent. If that password fails, it will attempt each of the Alternate Passwords until it finds one that works. This allows you to support legacy configurations, periodically change the Snare Agent password, or use different passwords for different groups of Agents, without stopping the objective from communicating with the agents.

Protocol to use

The legacy agents (pre-v5) may only use HTTP (the default option).  Version 5 agents, such as Snare Enterprise Agent for WIndows, Snare Enterprise Agent for MSSQL,Snare Enterprise Epilog for WIndows, may be configured to use HTTPS.  To configure the version 5 agents:

...

Each report may be configured per agent type/version per protocol. 

Alternate listening port

Likewise, the objective uses the Agent listening port specified in the Configuration Wizard when it attempts to communicate with each agent. If that port fails, it will attempt to use the alternate port specified here. The purpose of this field is the same as the alternate password fields - legacy and change support.

Management Mode

Only highlight differences between Master config and Agent config

...

Comparison Options

Ignore Agent version mismatch in configuration differences report.

...

The objective needs to be configured and regenerated at least once before any of its functions are available.

Snare Agents

The first content tab provides a summary overview of the status of each Agent (both managed and ignored), grouped by status. The hostname of each agent is listed, along with IP address, Agent Type and version.

...

• Agents matching the Master configuration

  • These Agents are online and completely match the Master Configuration, with no differences.

• Agents with configuration different to the Master Configuration

  • These Agents are online but their configuration is different to the Master Configuration.

• Agents that cannot be contacted

  • Agents that match the Operating System (from Agent Type filter), and Hostname filter, but cannot be contacted. Some of these Agents may have the wrong version, but since this information is identified once the Agent is contacted it is impossible to determine this information while they are offline.

• Agents ignored by version string filter

  • Online Agents excluded from management due to the version string filter. 

• Agents ignored by hostname filter

  • Agents excluded from management due to the hostname filter.

• Agents ignored by type filter

  • Agents excluded from management due to the Agent type filter.

Master Config

The Master Config tab provides a way to view the existing Master Configuration, refresh it with imported config from an Agent, or clear it completely.

...

Finally, the Master configuration can be cleared from the objective if it is no longer required/accurate.

Config Differences

The Agent Config Differences tab lists each online Agent that doesn't match the Master configuration exactly, with a list of the parameters that do not match for review. Only the Agent parameters which do not match the Master parameters are listed, and all others will be an exact match.

The first column is the configuration parameter name, the second is the value set on the Agent, and the third is the Master configuration value. Fields which are missing from either side will be marked with 'Not Configured'.

Refresh Specific Agents

When there are a large number of Agents managed in a single objective, it takes time to Regenerate everything. This makes debugging a small subset of Agents a problem if you have to wait for 30+ minutes after each change. To get around this, the Refresh Specific Agents tab provides the ability to specify which Agents you wish to regenerate on-demand.

Simply select the Agents to be regenerated by ticking the Checkboxes and clicking 'Refresh Selected Agents'. The objective will regenerate, and only retrieve data from the selected Agents. It will use the previously retrieved config values to work out the differences reports for each Agent that wasn't refreshed.

Agent Processing Errors

Any errors encountered while regenerating the objective will be listed on this tab. All of the Agents listed under "Agents that cannot be contacted" will be listed on this page with the reason why they could not be contacted. Likewise, when Config Push is enabled, Agents with a configuration that does not match, will have a reason listed here too. 

Snare Agent Management Console

As part of installing or upgrading to version 7.2, the Snare Agent Manager (SAM) is included.  This will help to manage your agents and licensing of the agents.

Selecting the menu item will launch SAM in another tab.  The Snare Agent Manager is used for the license allocation and management of the v5+ Snare Agents using the Web application interface which can be used via any modern web browser (The minimum versions are IE9+. and current versions of Chrome, Safari and Firefox, refer to the installation guide for more details ). The SAM is designed to provide centralized management of all your Snare agent licensing. It contains a dashboard to allow the easy identification and status of the licensing system, usage and if there are operational issues from agents and their licenses.

Please refer to the User Guide for Snare Agent Manager for further information.