|
Once you have created the Group associated to your targeted technology, the second action you need to perform is to provide Monitoring Studio with the information related to the Host on which the technology you want to monitor is running. A Host instance contains all the information about the server where the technology to monitor is running (hostname, system type, connection credentials list, SNMP information, host availability check information, etc.). Hosts are grouped under the Group instance and contain Monitors.
To create a host
| 1. | In the PATROL Console, right-click the Group icon and select KM Commands > New > Host... |
Adding the Hosts to be Monitored - Host Information
| 2. | Provide the name of the Host: |
| ▪ | 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 that will be used to describe this host. |
 The description is particularly useful to easily identify the host when importing a configuration through the Import Configuration wizard.
| ▪ | System type: Select the type of the operating system that is running on the host that will be monitored (Windows, UNIX/Linux, or Other). Select Other for any host that will not behave as a regular Linux or UNIX system would. For example, while a network device is likely to run a customized version of Linux of BSD, its restricted shell will not allow Monitoring Studio to use standard UNIX commands to perform the monitoring. |
Monitoring Studio requires you to specify the type of the operating system to avoid a costly identification phase and to offer more robust monitoring options.
| 3. | Create a separate device in TrueSight OM: Check this option if you want the remote monitored host to appear as a separate device in TrueSight OM. |
System Credentials
Adding the Hosts to be Monitored - Credentials
| 5. | (Optional) System Credentials: Enter the Username and Password required to establish a connection with the targeted host. These credentials are used for all system-related monitoring tasks to collect data. |
| 6. | (Optional) Associated OpenSSH Private Key File Path: When monitoring remote hosts running UNIX, Linux or other types of operating systems that support SSH authentication key file, you may need to provide an OpenSSH private key file to establish a secured connection with the remote host. Enter the path of the OpenSSH private key file you wish to use to establish this connection and enter the optional PassPhrase in the Password field. |
 The Private Key File should exists on the PATROL Agent node.
| 7. | SNMP version used by <Managed System>: Select the SNMP version to be used when performing SNMP monitoring and/or an SNMP availability check. Select None if no SNMP agent is running on the host, or if you do not plan to use SNMP to monitor this host. |
| 9. | If you have previously selected SNMP version 1, specify: |
| ▪ | the Community to be used. |
| ▪ | the Port number (default: 161). |
Adding the Hosts to be Monitored — SNMP v1 Settings
| 10. | If you have previously selected SNMP version 2c, specify: |
| ▪ | the Community to be used. |
| ▪ | the Port number (default: 161). |
| ▪ | the number of seconds Monitoring Studio KM for PATROL will wait for the completion of the SNMP polling (default: 120 seconds). This timeout must be long enough to complete the polling of an entire SNMP table. |
Adding the Hosts to be Monitored — SNMP v2c Settings
| 11. | If you have previously selected SNMP version 3, specify: |
| ▪ | the Username to be used to perform the SNMP query. |
| ▪ | the Authentication protocol to be used to authenticate the SNMP v3 messages. Possible options 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 options 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 the completion of the SNMP polling (default: 120 seconds). This timeout must be long enough to complete the polling of an entire SNMP table. |
Adding the Hosts to be Monitored — SNMP v3 Settings
Host Availability
Adding the Hosts to be Monitored - Host Availability
| 13. | (Optional) Select the method Monitoring Studio should use to test the availability of the monitored host: |
| ▪ | Ping check: Select this option to have Monitoring Studio ping the monitored host. To be successful, the targeted host must respond to at least 1 ping command out of 4, during each collection cycle. |
| ▪ | Hostname Resolution Check: Select this option to check that Monitoring Studio can resolve the hostname of the monitored host to an IP address. |
| ▪ | SNMP check: Select this option to have Monitoring Studio check the monitored host availability via an SNMP session. For the SNMP availability check to be successful, the targeted host must respond to a "GETNEXT" request on either the OID 1.3.6.1 or the OID 1.3.6.1.4.1. |
| ▪ | (Windows OS only) WMI check: Select this option to have Monitoring Studio check the monitored host availability via the WMI protocol. |
| ▪ | (Remote UNIX/Linux or other OS only) SSH check: Select this option to have Monitoring Studio check the targeted host availability (UNIX, Linux, or other systems) via the SSH protocol. For the SSH availability check to be successful, Monitoring Studio must be able to connect to the host using the provided System Credentials. |
| ▪ | TCP Port check: Select this option to have Monitoring Studio check the targeted host availability via a TCP connection. You must provide the port number the protocol must use to access the host. |
| ▪ | (Optional) Signature Files Check: Click to open the Signature Files Check dialog box. If at least one of the signature files is present on the targeted host, the check is considered successful: |
Adding the Hosts to be Monitored - Signature Files
| • | Provide the name and full path of the signature file on the targeted host. |
 Wildcards are not supported in signature files
| ▪ | Disable related monitors when the host is unreachable: Select this option if you wish Monitoring Studio to disable the monitoring of all Monitors attached to the Host. |
 The monitoring will automatically resume when the host is once again available.
| ▪ | What thresholds should be set on the newly created object? Mode to be used to set alert thresholds: |
| • | I want to use the default thresholds: Uses the default thresholds set by Monitoring Studio |
| • | I want to set custom thresholds: Allows you to customize the thresholds for all parameters of the instance |
| • | I want to use the default thresholds and customize them: Sets the default Monitoring Studio thresholds on certain parameters and then allows you to customize any/all of them. This is mainly intended to help save time if you wish to customize the thresholds of just one of many parameters for the instance, and leave the default settings for the others. |
| • | I do not want to set any thresholds for now: No thresholds will be set on any parameter of the instance, and as a result no alerts will be triggered. Monitoring Studio will poll the object and return the output of the polling – but will not raise any alerts until you set thresholds. |
The Host icon  is automatically created and displayed in the PATROL Console. Collected parameters for Host instances are listed in the SEN_MS_HOST chapter. You can now specify the Monitors to use or first create a Monitor Group.
|
