Monitoring a Remote System or an External Device

Home  Previous  Next

Hardware Sentry is able to monitor the hardware of a system remotely through the network. The purpose of this function is not to monitor all servers from one agent, but to be able to monitor devices on which one cannot install a PATROL Agent, like the chassis of blade servers, tape libraries, etc.

Hardware Sentry monitors systems or external devices remotely through the SNMP, SSH, Telnet and WBEM/WMI protocols. This means that only SNMP, SSH, Telnet and WBEM/WMI based connectors will function properly for remote devices..

NoteConfiguring Hardware Sentry to monitor another system or external device remotely does not prevent it from monitoring the hardware of the local host where the KM is running. Once configured to monitor another system remotely, the KM will show two icons side-by-side in the PATROL Console: "Hardware on local host" and "Hardware on <RemoteSystem>".

How to monitor a device remotely?

1.Right click the local host’s Hardware icon > KM Commands > Add a Remote System or an External Device...

MNG_Wiz_Remote_Monitoring_Welcome

Monitor a Remote System or an External Device — Licence Agreement

Read the license agreement, accept it and click Next to continue.

2.Identify the system or device you want to monitor remotely and click Next.

MNG_Wiz_Remote_Monitoring_SystemID

Monitor Another System Remotely — 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 a platform from the drop down list to specify the system or device type. The options are: OpenVMS, HP Tru64 UNIX, HP-UX, IBM AIX, Linux (Red Hat, SuSe, VMWare), Blade Chassis, Out-of-band Management Card, Network (Switch), Storage (Array, Switch, Library), Sun Solaris, and Windows 2000/XP/2003/Vista/2008.
3.Select the connectors for Hardware Sentry to use to monitor the remote system.

MNG_Wiz_Remote_Monitoring_Select_Connectors

Monitor Another System Remotely — Connectors Selection

The connectors displayed depend on the system or device specified in the previous step. Select the appropriate connectors and click Next.

NoteThe following steps depend on the system/device type of the remote element and the protocols used to connect to it. For information on which connectors are suitable for each system/device, please refer to the Connectors and Platforms in the Reference Guide.
If the connectors selected use SNMP, this panel appears:

MNG_Wiz_Remote_Monitoring_SNMP

Monitor Another System Remotely — SNMP Community String

SNMP community string: Enter the SNMP community string and click Next.

If the connectors selected use WMI or WBEM these panels appear asking for connection
credentials:

MNG_Wiz_Remote_Monitoring_Credentials_WMI

Monitor Another System Remotely — WMI Queries Credentials

MNG_Wiz_Remote_Monitoring_Credentials_WEBM

Monitor Another System Remotely — WBEM Queries Credentials

WMI/WBEM credentials: Enter the WMI/WBEM credentials and click Finish/Next.

If the connectors selected require Telnet or SSH to connect to the remote element, the following panel appears:

MNG_Wiz_Remote_Monitoring_Credentials_SSH_Telnet

Monitor Another System Remotely — Scripts Credentials

Connect to [System/Device] using the following protocol: Select either Telnet or SSH and enter the credentials required to execute the protocols and click Next.
Login and Password: Enter the login and password that Hardware Sentry is required to use to connect to the system/device to monitor.
Sudo options: On UNIX/Linux platforms, you have the option of permitting Hardware Sentry to use the Sudo utility to execute external commands using root.

KMCmd_Credentials_Sudo_Options

Monitor Another System Remotely — Sudo Options

Final Step in the remote monitoring wizard is common to all platforms/systems. Click Finish and Hardware Sentry will perform a new full discovery to detect this new remote system.

The Hardware icon for the local host will change to Hardware on localhost and an icon labeled Hardware on <remotehostname> will appear. This represents the system/device you are now monitoring remotely, along with icons for all of the detected parameters of this remote system/device.