Importing a Configuration

Home  Previous  Next

This feature allows you to configure Monitoring Studio by importing a configuration already in use on another PATROL Agent:

It eliminates the trouble of manually configuring Monitoring Studio on another PATROL Agent all over again
It ensures both configurations are identical

Basically, you can import from another PATROL Agent:

an entire Monitoring Studio configuration that has been backed-up which contains all the Groups, Hosts, and Monitors created under the Monitoring Studio icon (SEN_MS_MAIN_ok_32) or,
a single Group configuration that has been exported which contains all the Hosts and Monitors created under the chosen Group (SEN_MS_GROUP_ok_32).

All information found in the configuration file (.cfg) will be imported and merged into the current installation.

NoteYou may import a PATROL Agent configuration (".cfg") with any type of thresholds. If necessary, Monitoring Studio will convert the thresholds to the type of thresholds currently used at the next discovery (within an hour).

To import an existing configuration

1.Right-click the Monitoring Studio icon > KM commands > Configuration > Import Configuration.

ImportConfig_1Welcome

Importing Configuration - Welcome Page

2.Enter the path to the folder containing the configuration file(s) and click Next. By default, all .cfg files found under %PATROL_HOME%\config on Windows and $PATROL_HOME/config on UNIX systems will be listed.

ImportConfig_2File

Importing Configuration -  Import File Selection

3.Select the configuration file to import.  It can either be an entire Monitoring Studio configuration or a single Group configuration.
4.Click Next and wait while Monitoring Studio processes your configuration file.

ImportConfig_3GlobalSettings

Importing Configuration - Global Settings

5.(Optional) When importing an entire Monitoring Studio configuration, select which global variables you wish to import and click Next. Please note that global variables will only be displayed if they have previously been exported.

WarningImporting global settings will overwrite the current global settings of your existing objects.

ImportConfig_4GroupConstants

Importing Configuration - Group Constants Import

6.Provide a value for each Group Constant to be imported and click Next.

NoteIf a Group Constant is marked as required, its corresponding value cannot be left blank.

TipUpdating the Group Constant(s) remains possible after the import process by right-clicking a Group > KM commands > Group Constants...

 

ImportConfig_5HostInformation

Importing Configuration - Host Information

7.(Optional) If you have cleared the host information during the export process, Monitoring Studio indicates the number of hosts found in the configuration file that require specific information before being imported. You can click the Hosts button to view the complete list.
8.Click Next.

ImportConfig_6HostInformation_specific_information

Importing Configuration - Host Information

9.Provide specific information for each imported host (a counter indicates the number of hosts to identify):
Hostname/IP address/FQDN: Enter the Hostname, IP address or Fully Qualified Domain Name of the host on which the technology you wish to monitor is running.
(Optional) Display Name: Enter the name that will be displayed in the console for this host.
(Optional) Description: Enter a unique description or edit the existing description if you have already provided one during the export process.
Create a separate device in TrueSight: Check this box if you want the remote monitored host to appear as a separate device in BMC TrueSight Operations Management.
10.Click Next.

ImportConfig_7SystemCredentials

Importing Configuration - Credentials

11.(Optional) If you have chosen to clear credentials during the export process, provide system credentials and SNMP information for each imported host. A counter indicates the number of system credentials to provide:
Monitors using these credentials: Click this button to display the list of Monitors using system credentials.
Enter the Username and Password to connect to the targeted host. These credentials will be used for all system related monitoring tasks to gather data.
(Optional - for system credentials only) SNMP version used by <Managed System>: Select the SNMP version to be used when monitoring via SNMP and/or when performing an SNMP availability check. If no SNMP agent is running on the host, select None.
12.Click Next.

TipThe following steps which consist in configuring SNMP settings (v1, v2c, or v3) are optional and only available when an SNMP version is selected.

ImportConfig_7SNMP_v1

Importing Configuration  -  SNMP v1 Settings

13.If you have previously selected SNMP version 1, indicate:
the Community to be used.
the Port number (default: 161).

ImportConfig_7SNMP_v2c

Importing Configuration  -  SNMP v2c Settings

13.If you have previously selected SNMP version 2c, indicate:
the Community to be used.
the Port number (default: 161).
the number of seconds Monitoring Studio will wait for an SNMP response (Default: 120 seconds). This timeout covers all the sub-queries that compose the 'parent' query.

ImportConfig_7SNMP_v3

Importing Configuration  -  SNMP v3 Settings

13.If you have previously selected SNMP version 3, indicate:
The Username to be used to perform the SNMP query.
The Authentication protocol to be used to authenticate the SNMP v3 messages. Possible values are: None, MD5, SHA.
The Authentication password to be used to authenticate the SNMP v3 messages.
The Privacy protocol to be used to encrypt SNMP v3 messages. Possible values are: None, AES, DES.
The Privacy password associated with the privacy protocol.
The Context name accessible to the SNMP entity.
The Port number (default: 161).
The number of seconds Monitoring Studio will wait for an SNMP response (Default timeout: 120 seconds).
14.Click Next.

ImportConfig_7.5_Conflicting_Objects

Importing Configuration -  Overwrite/Rename Existing Objects

15.This step is only displayed when some objects (Groups, Hosts, or Monitors) defined in the imported configuration already exist in the PATROL Agent configuration. In this case, you can view the complete list of conflicting objects by clicking the Conflicting Objects button. You then need to select one of these two options:
Overwrite: if you want to overwrite existing objects.
Rename by adding this prefix: if you do not want to overwrite existing objects. You can enter a prefix to be assigned to these copied objects. The prefix will be applied to the ID of all the Groups, Hosts and Monitors found in the configuration. Example: you enter "NEW_" in the prefix box and you have a Group called "Lync". The new ID will be "NEW_Lync" thus avoiding overwriting the existing "Lync" configuration.
16.Click Next.

ImportConfig_8_Import_Summary

Importing Configuration  -  Import Summary

17.Before importing the configuration, the number of objects, groups, and hosts to be imported are listed. You can choose to pause the monitoring of the imported objects to have time to review them. This will allow you to make sure the configuration is correct before starting the monitoring of the imported objects.

NoteNote that you can resume the monitoring of the imported objects at anytime by right-clicking on the instances > KM Commands > Resume Monitoring.

18. Click Next to start the import process.

ImportConfig_9_Import_Completed

Importing Configuration - Completed Import Confirmation

19.A message confirming the import and listing the number of imported configuration variables appears. Click Finish.

Once the discovery process is completed, all monitors related to the imported configuration will be displayed on your console.