Configuring Hardware Monitoring

Hardware Sentry monitors the hardware of almost any server and external storage device available in datacenters. The configuration procedure will differ whether the server is locally and remotely monitored.

Configuring the Localhost Monitoring

No specific configuration is generally required as Hardware Sentry automatically detects the components of the server it is running on along with the PATROL Agent. However, additional configuration will be necessary if you monitor local hosts in network secure environments. In that case, you might need to:

  1. Select the protocol to use to connect to the localhost
  2. Specify the connectors to be used
  3. Apply the connection settings to the localhost

Additional settings are also available to help you fine-tune your local hosts monitoring. You can for example disable the localhost monitoring if you only need to monitor remote systems, such as blade chassis.

Selecting the Connection Protocol (local)

By default, Hardware Sentry detects and preselects the protocol(s) that can be used to communicate with the local host. You can however modify this selection to suit your specific needs.

To select the connection protocols:

  1. Right-click the localhost’s Hardware icon and selecting KM Commands > This System’s Settings > Connection, Credentials and Connectors….:

    Selecting the Connection Protocol

  2. The protocols available for localhost monitoring are:

  3. Click Next to configure the settings of the selected protocol.

Configuring an HTTP Connection (local)

Hardware Sentry can leverage the HTTP protocol to communicate directly with the CIM server running on the localhost and collect information.

To configure an HTTP connection:

  1. Right-click the localhost’s Hardware icon and select KM Commands > This System’s Settings > Connection, Credentials and Connectors.
  2. Select the HTTP protocol and click Next.
  3. Select the Connector Selection Mode:

    • Automatically: to let Hardware Sentry select the appropriate connector
    • Manually: to select the connector(s) of your choice
  4. Click Next to continue.

  5. Configure the HTTP connection settings:

    • the protocol you wish to use: HTTP or HTTPS. By default Hardware Sentry proposes to use HTTPS.
    • the port number to be used. By default, Hardware Sentry proposes to use port 443.
    • the HTTP credentials or leave blank to use the default PATROL account credentials.

    Connection Credentials and Connectors on Local Host — HTTP Credentials

  6. Click Next to apply the connection settings.

  7. Click Finish.

Configuring OS Commands Settings (local)

By default, Hardware Sentry uses the PATROL Agent default account (patrol) to execute commands against the local host to collect hardware information. If a different account has been configured, the alternate user account to be used should be provided through the Command Execution Credentials dialog box.

To specify the alternate user account to be used:

  1. Right-click the localhost’s Hardware icon and select KM Commands > This System’s Settings > Connection, Credentials and Connectors…

  2. Select the OS Commands protocol and click Next.

  3. Select the Connector Selection Mode:

    • Automatically: to let Hardware Sentry select the appropriate connector
    • Manually: to select the connector(s) of your choice
  4. Click Next to continue.

    Editing the Localhost Settings — Command Execution Credentials

  5. Enter the credentials of the alternate user account that will be used to execute external commands. Leave blank to use the default PATROL account credentials. You will then have to restart the PATROL Agent to ensure this modification will be taken into account.

  6. (UNIX) If the PATROL Agent default account does not have sufficient privileges to execute commands and cannot be granted super-user rights, use the “sudo” utility to authorize users to execute specific commands as another user account (typically root). To configure Hardware Sentry to use “sudo”:

    • Identify the commands run by Hardware Sentry that require advanced privileges.
    • Make sure the sudo utility is installed on the system and the /etc/sudoers file is configured to allow the PATROL Agent to execute the commands as root.
    • Configure “sudo” to allow the PATROL Agent default account to execute the needed commands as root (modify the /etc/sudoers file). Configuring “sudo” requires root privileges.
    • Check that the PATROL Agent default account is properly authorized to execute the needed commands through the “sudo” utility.
    • Click the Sudo Options button:

    Connection Credentials and Connectors on Local Host — Sudo Options

    • Select the commands Hardware Sentry should execute using the “sudo” utility.
    • Enter the command line or leave the field blank to use the default /usr/local/bin/sudo path.
    • Click Accept.
  7. Click Next to apply the connection settings.

  8. Click Finish.

For more information about Sudo, please refer to Using ‘sudo’ in Hardware Sentry KM.

Configuring an SNMP Connection (local)

Hardware Sentry can leverage the SNMP protocol to collect hardware information about the local host. In that case, an SNMP agent must be installed on the monitored host and the SNMP connection configured through the SNMP Connection Settings wizard. The information required by Hardware Sentry will vary according to the version used:

SNMP Version Description Information Required
SNMP v1 Supports 32-bit counters. Community and Port Number (Default: 161). Timeout is set through the PATROL Agent Configuration variable /snmp/default_timeout.
SNMP v2c Supports both 32 and 64-bit counters. Community, Port Number, and Timeout (Default: 120 seconds).
SNMP v3 Encryption and authentication added to the 64-bit counters. Authentication information (username, protocol, and password), Encryption information (privacy protocol and password), Context name, Port Number, and Timeout (Default: 120 seconds).

To configure the SNMP connection:

  1. Right-click the localhost’s Hardware icon and select KM Commands > This System’s Settings > Connection, Credentials and Connectors.
  2. Select the SNMP protocol and click Next.
  3. Select the Connector Selection Mode:

    • Automatically: to let Hardware Sentry select the appropriate connector
    • Manually: to select the connector(s) of your choice
  4. Click Next to continue.

  5. Select the SNMP version to be used and click Next. If no SNMP agent is running on the host, select 1 and leave the connection settings fields blank.

    Editing the Localhost Settings — SNMP Connection Settings

  6. If you have previously selected SNMP version 1, indicate:

    • the Community to be used. Leave blank if you want Hardware Sentry to automatically detect the SNMP community.
    • the Port number (default: 161).

    Editing the Localhost Settings — SNMP v1 Connection Settings

  7. If you have previously selected SNMP version 2c, indicate:

    • the Community to be used. Leave blank if you want Hardware Sentry to automatically detect the SNMP community.
    • the Port number(default: 161).
    • the number of seconds Hardware Sentry will wait for an SNMP response (Default timeout: 120 seconds). This timeout covers all the sub-queries that compose the ‘parent’ query.

    Editing the Localhost Settings — SNMP v2c Connection Settings

  8. 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 authenticate 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 Hardware Sentry will wait for an SNMP response (Default timeout: 120 seconds). This timeout covers all the sub-queries that compose the ‘parent’ query.

    Editing the Localhost Settings — SNMP v3 Connection Settings

  9. Click Next to apply the connection settings.

  10. Click Finish.

Configuring a WMI Connection (local)

Hardware Sentry can leverage the WMI protocol to communicate directly with a SMI-S Provider/storage system and collect information.

To configure a WMI connection:

  1. Right-click the localhost’s Hardware icon and select KM Commands > This System’s Settings > Connection, Credentials and Connectors.
  2. Select the WMI protocol and click Next.
  3. Select the Connector Selection Mode:
    • Automatically: to let Hardware Sentry select the appropriate connector
    • Manually: to select the connector(s) of your choice
  4. Click Next to continue.

  5. Provide the WMI Credentials or leave blank to use the default PATROL account credentials.

    Connection Credentials and Connectors on Local Host — WMI Credentials

  6. Click Next to apply the connection settings.

  7. Click Finish.

Configuring a WBEM Connection (local)

Hardware Sentry can leverage the WBEM protocol to communicate directly with an SMI-S Provider/storage system and collect information.

To configure a WBEM connection:

  1. Right-click the localhost’s Hardware icon and select KM Commands > This System’s Settings > Connection, Credentials and Connectors.
  2. Select the WBEM protocol and click Next.
  3. Select the Connector Selection Mode:
    • Automatically: to let Hardware Sentry select the appropriate connector
    • Manually: to select the connector(s) of your choice
  4. Click Next to continue.
  5. Configure the WBEM Credentials:

    • Enter the port number to be used. By default port 5989 is used for encrypted connections and 5988 for non-encrypted connections.
    • Check the Encrypt data for encryption, if needed.
    • Enter WBEM credentials or leave blank to use the default PATROL account credentials.

    Connection Credentials and Connectors on Local Host — WBEM Credentials

  6. Click Advanced Options to access specific settings related to the WBEM connection:

    • Enter the IP address/Hostname of the Multi-Tier Authentication Server (This option is mostly used for VMware servers).
    • Enter the WBEM Namespace or leave blank to let the KM automatically detect the proper name (recommended). If the WBEM credentials are not provided, Hardware Sentry will authenticate using the credentials provided in the previous panel (WBEM Credentials). This therefore disables multi-Tier authentication.

    Connection Credentials and Connectors on Local Host — WBEM Credentials (Advanced Options)

  7. Click Accept to validate your changes.

  8. Click Next to apply the connection settings.
  9. Click Finish.

Specifying the Connectors to Use (local)

By default, Hardware Sentry automatically detects the connectors that are best suited to monitor the system hardware. You can however decide to manually choose the connectors to be used. For an exhaustive list of available connectors, refer to the Hardware Connector Library documentation.

To specify the connectors to use

  1. Right-click the localhost’s Hardware icon and select KM Commands > This System’s Settings > Connection, Credentials and Connectors.
  2. Specify the Connectors Selection Mode:

    Connection Credentials and Connectors on Local Host - Specify the Connectors Selections Mode

    • (Default and Recommended) Automatic: automatically detect the relevant connectors: In this mode, Hardware Sentry will run tests at each discovery and select the connectors that best match the managed system. You will however be able to exclude connectors from the detection process (see step 4).
    • Manual: specify the connectors to use: In this mode, you will have to manually select the connectors Hardware Sentry should use to monitor the system hardware. Hardware Sentry then runs a full discovery to detect all devices and sensors. If you use this option, pay close attention to the PATROL System Output Window for error messages. A poor selection of connectors may lead the KM to remove all devices and sensors from the Console and may prevent Hardware Sentry from properly monitoring the system’s hardware. For an exhaustive list of available connectors, refer to the Hardware Connector Library documentation.
  3. Click Next.

  4. Apply connection settings

    Connection Credentials and Connectors on Local Host — Apply New Host Settings

  5. (Optional) If you have previously chosen the Automatic connector selection mode, you can click Exclude Connectors to select the connectors to be excluded from the detection process.

    Connection Credentials and Connectors on Local Host — Exclude Connectors

  6. Click Accept.

  7. Click Finish to apply the new settings.

Applying the Connection Settings to the Localhost

The last step of the configuration of the localhost monitoring consists in applying your connection settings.

  1. Right-click the localhost’s Hardware icon and select KM Commands > This System’s Settings > Connection, Credentials and Connectors…
  2. Select and configure the Connection Protocol.
  3. Select the Connectors Selection Mode.
  4. Apply the connection settings:

    Configuring the Localhost Settings — Apply Settings

  5. (Optional) If you have previously chosen the Automatic connector selection mode, you can click Exclude Connectors to select the connectors to be excluded from the detection process. Click Accept to save your selection.

    Configuring the Localhost Settings — Exclude Connectors

  6. Click Finish to apply the new settings.

Disabling Localhost Monitoring

Disabling the monitoring of the localhost may be useful when you need to exclusively monitor remote systems, such as blade chassis for example.

  • To disable the localhost monitoring, right-click the localhost icon > KM Commands > Remove this System.
  • To enable the localhost monitoring, right-click the Hardware icon > KM Commands > Reinitialize KM and select the Force localhost monitoring option.

Forcing Localhost Monitoring

Configuring Remote Hosts Monitoring

Remote monitoring allows you to monitor multiple hosts from a single agent. This feature will prove to be useful if you lack resources or time to deploy a PATROL Agent and Hardware Sentry on several systems.

Hardware Sentry offers the possibility to add remote hosts to your monitoring environment individually or in a batch when the hosts share the same configuration settings (OS, protocol, credentials, etc.). When creating a group of hosts you are proposed to define the group name (Internal ID) as well as the set of hosts included into a group being created. The name (Internal ID) makes it easier for you to identify the hosts that are part of a group in the PATROL console. Additionally, you can associate your system to Fully Qualified Domain Names (FQDNs) of specific devices in TrueSight when you define the connection settings of your host(s). The FQDN designates the specific location of a device within the Domain Name System (DNS) hierarchy; it communicates the host’s position relative to the root of the DNS namespace. An FQDN enables each connected device to be uniquely identified and located within the monitored environment and therefore ensures that a device is properly identified.

Remote monitoring is required if you need to:

Adding a Remote Host

Hardware Sentry allows you to configure remote monitoring for any accessible device to get a real-time insight of the health of your monitored environment, perform proactive maintenance operations, and maintain the highest level of performance you need.

Adding a remote host or an external device to your monitored environment consists in identifying the host(s)/device(s) you wish to monitor and configure the connection settings according to the protocol you need to use. This section provides step-by-step instructions for adding a single host/device or for adding multiple hosts/devices at a time, that will be easily identified as part of a group in the PATROL console.

To add the monitoring of remote hosts

  1. Right-click the Hardware icon and select KM Commands > Add a Remote System or an External Device…

    Single host monitoring

    Adding a Single Remote Host — System Identification

    • Internal ID: Enter the name of the system or device you wish to monitor
    • Hostname(s) or IP address(es): Enter the Hostname or IP address of the system or device you wish to monitor. Leave this field blank if you have specified the hostname in the Internal ID field.
    • From the drop-down list, select the System or Device type.
    • (Optional) Enter the FQDN to associate the system to another device in TrueSight. The FQDN uniquely distinguishes a device from any other system and ensures that a device monitored via their management cards or through controllers, for example, is properly identified.

    Multiple hosts monitoring

    Adding Multiple Remote Host — System Identification

    • Internal ID: Enter an ID that will be used as a group name for hosts that share the same configuration information (OS, protocol, credentials, etc.).
    • Hostname(s) or IP address(es): Enter the Hostnames or IP addresses of the hosts you wish to monitor. A group can contain multiple hostnames/IP addresses that must be separated by commas.
    • From the drop-down list, select the System or Device type.
    • (Optional) Enter the FQDN to associate the system to a device in TrueSight. The FQDN uniquely distinguishes a device from any other system and ensures that a device monitored via their management cards or through controllers, for example, is properly identified.

    The number of FQDNs has to match the number of hostnames/IP addresses.

    Hardware Sentry will create as many hosts instances (instances of the MS_HW_MAIN application class) as hostnames/IP addresses. The hosts instances are displayed in the interface as if they were single hosts, but are identified as part of a group with their common Internal ID added to their labels between brackets.

  2. Click Next to continue.

Selecting the Connection Protocol (remote)

By default, Hardware Sentry detects and preselects the protocol(s) that can be used to communicate with the remote host. You can modify this selection to suit your specific needs.

To select the connection protocol:

  1. Add a remote host.
  2. Select the protocol(s) you wish to use to communicate with the hardware instrumentation layer of the remote host (the list of protocols may vary according to the selected device type):

  3. Click Next to configure the settings of the selected protocol.

Configuring an HTTP Connection (remote)

Hardware Sentry can leverage the HTTP protocol to communicate directly with the CIM server running on the remote host and collect information.

To configure an HTTP connection:

  1. Add a remote host.
  2. Select the HTTP connection protocol.
  3. Select the protocol you wish to use: HTTP or HTTPS. By default, Hardware Sentry proposes to use HTTPS.
  4. Select the port number to be used. By default, Hardware Sentry proposes to use port 443.
  5. Provide the HTTP credentials or leave blank to use the default PATROL account credentials.

    Adding a Remote Host — HTTP Connection Settings

  6. Click Next to continue.

Configuring an SNMP Connection (remote)

Hardware Sentry can leverage the SNMP protocol to collect hardware information about the local host. In that case, an SNMP agent must be installed on the monitored host and the SNMP connection configured through the SNMP Connection Settings wizard. The information required by Hardware Sentry will vary according to the version used:

SNMP Version Description Information Required
SNMP v1 Supports 32-bit counters. Community and Port Number (Default: 161). Timeout is set through the PATROL Agent Configuration variable /snmp/default_timeout.
SNMP v2c Supports both 32 and 64-bit counters. Community, Port Number, and Timeout (Default: 120 seconds).
SNMP v3 Encryption and authentication added to the 64-bit counters. Authentication information (username, protocol, and password), Encryption information (privacy protocol and password), Context name, Port Number, and Timeout (Default: 120 seconds).

To configure the SNMP connection:

  1. Add a remote host.
  2. Select the SNMP connection protocol.
  3. Select the SNMP version to be used and click Next.
  4. If you have previously selected SNMP version 1, indicate:

    • the Community to be used.
    • the Port number (default: 161).

    Adding a Remote Host — SNMP v1 Connection Settings

  5. If you have previously selected SNMP version 2c, indicate:

    • the Community to be used.
    • the Port number (default: 161).
    • the number of seconds Hardware Sentry will wait for an SNMP response (Default timeout: 120 seconds). This timeout covers all the sub-queries that compose the ‘parent’ query.

    Adding a Remote Host — SNMP v2c Connection Settings

  6. 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 authenticate 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 Hardware Sentry will wait for an SNMP response (Default timeout: 120 seconds). This timeout covers all the sub-queries that compose the ‘parent’ query.

    Adding a Remote Host — SNMP v3 Connection Settings

  7. Click Next.

Configuring an SSH Connection (remote)

Hardware Sentry can leverage the SSH protocol to communicate directly with the CIM server running on the remote host and collect information.

To configure the SSH connection:

  1. Add a remote host.
  2. Select the SSH connection protocol.
  3. Provide the SSH connection credentials:

    • SSH, enter the credentials required to connect to the remote host through the SSH protocol.
    • SSH with authentication key, you will be prompted for specific credentials, that is a Username, an OpenSSh Private Key File and a Passphrase (if required).

    Adding a Remote Host — SSH Connection Credentials

  4. (UNIX/Linux) Click Sudo Options to allow Hardware Sentry to use the Sudo utility to execute external commands using root.

  5. Click Next.

Configuring a WMI Connection (remote)

Hardware Sentry can leverage the WMI protocol to communicate directly with the CIM server running on the remote host and collect information.

To configure a WMI connection:

  1. Add a remote host.
  2. Select the WMI connection protocol
  3. Provide the WMI credentials or leave blank to use the default PATROL account credentials.

    Adding a Remote Host — WMI Credentials

  4. Click Next.

Configuring a WBEM Connection (remote)

Hardware Sentry can leverage the WBEM protocol to communicate directly with the CIM server running on the remote host and collect information.

To configure a WBEM connection:

  1. Add a remote host.
  2. Select the WBEM connection protocol.
  3. Configure the WBEM connection settings:

    • Enter the port number to be used. By default port 5989 is used for encrypted connections and 5988 for non-encrypted connections.
    • Select the Encrypt data option to enable data encryption when performing the WBEM connection.
    • Enter the WBEM credentials (Username/Password) to use to establish the connection with the remote device.

    Adding a Remote Host — WBEM Credentials

    • Click Advanced Options to access specific settings related to the WBEM connection:

    Adding a Remote Host — WBEM Credentials — Advanced Options

    • Enter the IP address/Hostname of the Multi-Tier Authentication Server (This option is mostly used for VMware servers).
    • Enter the WBEM Namespace or leave blank to let the KM automatically detect the proper name (recommended). If the WBEM credentials are not provided, Hardware Sentry will authenticate using the credentials provided in the previous panel (WBEM Credentials). This therefore disables multi-Tier authentication.
    • Click Accept to validate your changes
  4. Click Next.

Configuring an IPMI-over-LAN Connection (remote)

IPMI-Over-LAN is the out-of-band interface used by Hardware Sentry to bypass the usual hardware agents and communicate directly with the motherboard’s BMC chip.

To configure an IPMI-over-LAN connection:

  1. Add a remote host.
  2. Select the IPMI-Over-LAN connection protocol.
  3. Enter the credentials to connect to the IPMI chip out-of-band (IPMI-over-LAN).

    Adding a Remote Host — IPMI Protocol

  4. Click Next.

Configuring a Cisco UCS Connection (remote)

Hardware Sentry can leverage the Cisco UCS API to communicate directly with the Cisco UCS (Unified Computing System) Manager running on the remote host and collect information.

To configure a Cisco UCS connection:

  1. Add a remote host.
  2. Select Cisco UCS API.
  3. Provide the following information:

    • Encrypt data: Select this option to encrypt the communication between the KM and Cisco UCS Manager using SSL (HTTPS)
    • Username: credentials valid on the specified Cisco UCS Manager
    • Password: password associated to the specified username

    Adding a Remote Host — Cisco UCS API Protocol

  4. Click Next.

Specifying the Connectors to Use (remote)

By default, Hardware Sentry automatically detects the connectors that are best suited to monitor the system hardware. You can however decide to manually choose the connectors to be used. For an exhaustive list of available connectors, refer to the Hardware Connector Library documentation.

To specify the connectors to use:

  1. Add a remote host.
  2. Select and configure the connection protocol.
  3. Specify the connector selection mode:

    Adding a Remote Host — Connector Selection Mode

  4. (Default and Recommended) Automatically detect the suitable connectors: In this mode, Hardware Sentry will run tests at each discovery and select the connectors that best match the managed system.

  5. (Advanced) Manually choose which connectors to use: With this mode, you will have to manually select the connectors Hardware Sentry will use to monitor the system Hardware. If you use this option, pay close attention to the PATROL System Output Window for error messages. A poor selection of connectors may remove all devices and sensors and may prevent Hardware Sentry from properly monitoring the system’s hardware. For an exhaustive list of available connectors, refer to the Hardware Connector Library documentation.

6.Click Next.

Manually Selecting Connectors

If you have previously selected the option Manually choose which connectors to use:

  1. Select the connectors Hardware Sentry will use to monitor the host. You can refer to the list of available connectors to find out which connectors are suitable for each system.

    Manually Selecting Connectors

  2. Click Next.

  3. Depending on the monitors selected and the protocol used to collect hardware information, you may have to configure the connection settings.

Automatically Detecting Suitable Connectors

If you have previously selected the option Automatically detect the suitable connectors based on:

  1. Select the protocols to be tested by Hardware Sentry (for example: SNMP, WMI, WBEM) and click Next.

  2. You will then have to configure the connection settings for the selected protocols.

Applying the Connection Settings to the Remote Host

The last step of the configuration of a remote host monitoring consists in applying your connection settings.

To specify the connectors to use:

  1. Add a remote host.
  2. Select and configure the connection protocol.
  3. Select the Connector Selection Mode.
  4. Apply the connection settings. If you have previously chosen the “Automatic” connector selection mode, you can specify one or more connectors to be excluded from the detection process:

    • Click Exclude Connectors.

    Adding a Remote Host — Add Remote Host and Discover its Environment

    • Select the connector(s) to be excluded and click Accept.
  5. Click Finish.

Hardware Sentry will perform a new full discovery to detect this(these) new remote system(s). An icon labeled Hardware on <host ID/name> or < host ID/name> (<Internal ID>) will be displayed in the PATROL console. It represents the system(s)/device(s) you are monitoring remotely:

Single hosts added individually

Single hosts added individually

Multiple hosts added as part of a group

Multiple hosts added as part of a group

Editing the Remote Host Settings

The Connection, Credentials and Connectors KM command allows you to modify the connection settings for any remote host/device whether it is monitored individually or as part of a group.

To edit the remote host settings

  1. Right-click a previously added remote system’s Hardware icon > KM Commands > This System’s Settings > Connection, Credentials and Connectors.

    Single Host Monitoring

    Editing a Remote Host Settings — System or Device Identification

    Multiple Hosts Monitoring

    Editing Multiple Remote Hosts Settings — System or Device Identification

    Tip: Accessing the remote system’s Hardware icon > KM Commands > This System’s Settings > Connection, Credentials and Connectors KM command from any host that is part of a group automatically opens the group configuration settings window.

  2. Modify the necessary information following the different steps of the wizard as described in the Adding a Remote Host section (i.e., system or device type, connector selection mode, list of selected connectors, connection credentials, etc.).

    Warning: If you change the monitoring settings for hosts that are part of a group, make sure that these settings apply to all the hosts in the group. Once saved, the new configuration will automatically be applied to all the hosts in the group.

  3. (Optional) If you have previously chosen the “Automatic” connector selection mode, click Exclude Connectors to select the connectors to be excluded from the detection process and click Accept.

     Connection Credentials and Connectors on Remote Host — Exclude Connectors

  4. Click Finish to apply the new settings to the selected host or to all the hosts in a group.

    Tip: Removing a host that is part of a group using the KM Command “Remove this System”, automatically deletes the host from the group and stops its monitoring.

Remote Hosts Monitoring Examples

Remote monitoring is required if you need to:

Monitoring a Blade Chassis

Blade servers are small-factor servers that share the same enclosure which provides the powering and cooling for all the blade servers inside the chassis. Most popular blade systems are:

  • Dell Modular Chassis
  • Hitachi BladeSymphony
  • HP BladeSystem
  • IBM BladeCenter
  • Fujitsu-Siemens Blade BX

All these blade chassis are fully supported by Hardware Sentry.

Each blade server can be considered as a true physical server for which every hardware components need to be monitored. A PATROL Agent and Hardware Sentry must be installed on each blade server to monitor the various parts of the blade: processors, memory modules, internal temperature, internal disks, etc.

Additionally, it is important to monitor the different components of the shared enclosure: power supplies and fans notably. Blade enclosures are generally equipped with a management card (the name can vary depending on the manufacturer: management module for the IBM BladeCenter, management blade for the Fujitsu-Siemens Blade BX, iLO or On-board Administrator for the HP BladeSystem, DRAC-MC for the Dell Modular Chassis).

You can also configure Hardware Sentry to connect to the management interface of the enclosure and monitor its hardware parts:

  1. Add a remote host to specify the name and IP address of the management interface.
  2. Specify that the element is a “Blade Chassis or Out-of-band Management Card”.
  3. Choose the appropriate connector corresponding to the type of the chassis or let the KM automatically detect it, and then provide the wizard with the credentials to connect to the management interface (SNMP community or username and password if it is an SSH-based interface). For an exhaustive list of available connectors, refer to the Hardware Connector Library documentation.

In the PATROL Console, you obtain two separate Hardware icons:

  • Hardware on <blade chassis name>, representing the hardware components of the shared enclosure
  • Hardware on local host, representing the hardware components of the server (blade) the KM is running on

Monitoring a Blade Chassis — Discovered Components

Under the shared chassis, an icon is also created for each blade server in the enclosure with an overall status for the blade (when available).

No additional license capacity is required to monitor the shared blade enclosure in addition to the blade servers present in the main chassis.

Monitoring VMware Servers

Virtualization helps IT administrators reduce capital expenses through server consolidation and optimize operating expenses through automation. Because a virtualized environment faces more risks than a physical one, IT administrators must consider monitoring their virtual machines. They should always keep in mind that when an issue occurs on the physical host, it impacts all the virtual machines running on the server.

As a PATROL Agent cannot be installed on the VMware ESXi Host, the monitoring needs to be done remotely, from a PATROL Agent running on another server, physical or virtual. It is recommended that the PATROL Agent and Hardware Sentry run on a separate physical system (or on a virtual machine on a separate physical system) to ensure continuous monitoring even in case of hardware failures.

Hardware Sentry needs to be manually configured to connect to the VMware ESXi Host to discover what the physical system is made of and collect the status of all components.

For more information about the installation procedure, please refer to the KB article Monitoring VMware ESX/ESXi.

To monitor VMware servers

  1. Right click the local host’s Hardware icon > KM Commands > Add a Remote System or an External Device…
  2. Identify the system or device you want to monitor remotely and click Next.

    Monitoring VMware Servers — System Identification

    • System or Device name: Enter the name of the system or device you wish to monitor
    • IP address or fully qualified name: Leave this field blank if you specify the host name above
    • System or Device type: Select Management Card/Chip, Blade Chassis, ESXi
  3. Click Next.

  4. Select the WBEM protocol and click Next.
  5. Provide the WBEM credentials.

    Monitoring VMware Servers — WBEM credentials

  6. If you need to use Multi-tier authentication, click on the Advanced Options button:

    Monitoring Another System Remotely — WBEM Credentials — Advanced Options

    • Enter the IP address/Host-name of the Multi-tier Authentication Server.
    • Enter the WBEM namespace or leave the field empty to let the KM automatically detect the proper name (recommended).
    • Click Accept to validate your changes.
  7. Click Next. A new icon is then created in the PATROL Console

    Monitoring VMware Servers — Discovered Components

Monitoring a Server through its Out-of-Band Management Card

For most servers, Hardware Sentry relies on an instrumentation layer running on the operating system itself (an SNMP agent, a WBEM provider, or some system commands). However, for some types of servers (mostly UNIX systems), the information available in-band is not sufficient and does not provide any data regarding environment sensors, power supplies, etc. For these systems, Hardware Sentry offers the ability to get additional information about the server through its out-of-band management card (if any).

By default, Hardware Sentry monitors the hardware components in-band only. To make Hardware Sentry connect to the out-of-band management card and retrieve the additional information available:

  1. Add a remote host.
  2. Enter the name of the out-of-band management card and its IP address.
  3. Select Management Card/Chip, Blade Chassis, ESXi as the system type.
  4. Choose the appropriate connector corresponding to the management card in the system and then enter the credentials to connect to it. For an exhaustive list of available connectors, refer to the Hardware Connector Library documentation.

In the PATROL Console, an additional icon is created:

  • Hardware on local host, corresponding to the monitoring done in-band
  • Hardware on <management card name>, corresponding to the monitoring done out-of-band through the management card.

Monitoring a Server Out-of-Band — Discovered Components

No additional license capacity is required when monitoring a system from both in-band and out-of-band.

Monitoring a SAN Switch

As the importance of the external storage grows with the implementation of blade servers and virtualization, monitoring the center piece of the SAN, i.e. the fiber switch, is more critical than ever. Hardware Sentry is able to monitor SAN switches from Cisco, Brocade and McData: their internal hardware components, fiber ports, temperature, power supplies, fans, as well as the traffic on each port. This greatly helps SAN administrators understand the performance issues in the environment: which servers are very demanding, which array is under pressure, backups impact, etc.

For an exhaustive list of available connectors and detailed information about the supported switches, refer to the Hardware Connector Library documentation.

As a PATROL Agent cannot be installed on a SAN switch:

  1. Install the KM and the PATROL agent on a regular system.
  2. Configure Hardware Sentry to connect to the SAN switch and monitor it:

    • Add a remote host to specify the name and IP address of the SAN switch.
    • Select the appropriate connector or let the KM detect it automatically (Fiber Alliance SNMP Agent, for Brocade and McData switches; Cisco MDS9000 Series, for Cisco switches). For an exhaustive list of available connectors, refer to the Hardware Connector Library documentation.

A Hardware on <switch name> icon is created representing all of the monitored components of the switch:

Monitoring a SAN Switch — Discovered Components

Additionally, SAN administrators can use the Ethernet/Fiber Port Traffic Report tool in Hardware Sentry to visualize the amount of data that are processed by each port of the switch on an hourly or daily basis.

Monitoring an External Disk Array

To consolidate the monitoring and reporting of a variety of disk arrays from different vendor, Hardware Sentry supports a wide range of manufacturers: IBM DS, HP EVA, EMC, etc. By relying on their SMI-S standard instrumentation, or on their specific administration tools otherwise, Hardware Sentry monitors the health of the various internal components: the disks, the different levels of allocated volumes, the fiber ports, the environment and the controllers.

Depending on the disk array and the way it is instrumented, the configuration of Hardware Sentry may vary.

  • First case: The disk array is SMI-S compliant itself, i.e. it can be interrogated directly by using the SMI-S protocol (WBEM-based), like the EMC Symmetrix disk arrays. Add a remote host to specify the name and IP address of the disk array. Select the appropriate connector or let Hardware Sentry detect it automatically, and then enter the credentials to connect to the disk array. For an exhaustive list of available connectors, refer to the Hardware Connector Library documentation.

  • Second case: The disk array requires the installation of a management software tool on a separate server or workstation, like the EMC CLARiiON systems. The disk array management tool acts as a “proxy” with the disk array itself. You need to install the PATROL Agent and Hardware Sentry on the server or workstation where the disk array management tool is running. By default, Hardware Sentry will monitor the hardware components of the server or workstation it is running on. Add a remote host to make Hardware Sentry also monitor the disk array through the management “proxy”. Enter the System or Device name and specify “localhost” as the IP address. This will make Hardware Sentry send its SMI-S/WBEM queries to the local management software tool.

  • Third case: IBM DS3000 and IBM DS4000 disk arrays require the installation of the SMCli tool on a server or workstation. You need to install the PATROL Agent and Hardware Sentry on the server or workstation where SMCli has been installed. Add a remote host to make Hardware Sentry use the SMCli tool to connect to the IBM disk array. Enter the name of the disk array and its IP address (note that you do not specify “localhost” as in the previous case, SMICli is not a “proxy” interface). Select the appropriate connector or let Hardware Sentry detect it automatically, and then enter the credentials to connect to the disk array. For an exhaustive list of available connectors, refer to the Hardware Connector Library documentation.

  • Fourth case: NetApp Filers are monitored remotely through their native SNMP Agent. Add a remote host to make Hardware Sentry monitor the internal hardware components of the NetApp filer: enter the name and IP address of the disk array, select the appropriate connector or let Hardware Sentry detect it automatically, and then enter the SNMP community string (For an exhaustive list of available connectors, refer to the Hardware Connector Library documentation). Filers have a much broader feature set than pure disk arrays. Sentry Software provides an additional KM that focuses on the performance and statistics metrics of the filer itself (filesystems, backups, I/O, etc.): NetApp Filers KM for PATROL.

Monitoring a Tape Library

As backups are often centralized on tape libraries, it is important to ensure that these devices are available to backup software products. Hardware Sentry is able to monitor the health of the various internal components of a tape library, including the tape drives and the media changers. Please note that Hardware Sentry does not monitor the backup software products in charge of copying the data to the tapes. It will not report whether a backup operation could not complete or when a backup set is not up to date.

Most tape libraries are instrumented through SNMP. While bearing different vendor names, most tape libraries are OEM’d from StorageTek or Quantum/ADIC. To monitor tape libraries:

  1. Add a remote host to make Hardware Sentry monitor a tape library.
  2. Specify the name of the library and its IP address.
  3. Select the appropriate connector (most probably, simply corresponding to the real manufacturer of the library: IBM, Quantum/ADIC or StorageTek). For an exhaustive list of available connectors, refer to the Hardware Connector Library documentation.
  4. Enter the SNMP community.