Windows

Installation on Windows system is fairly straight forward and accomplished by installing the latest version of HP System Management Homepage found on the HP Website:

HP System Management Homepage for Windows (x64)

HP System Management Homepage for Windows (x86)

(Note: these links may be outdated, please use the Search field to download the latest version.)

Once installed you will need to ensure that snmp is installed on the Windows host and configured to allow the collector to poll it. To configure open windows services and find “snmp” and go into the properties of the service.

• <Collector_IP> = the ip address of the collector in LogicMonitor that will be monitoring this device.
• <mycommunity> = The community string used in LogicMonitor.

Linux

HP System Management Homepage for Linux (x86)

HP System Management Homepage for Linux (x64) 

(Note: these links may be outdated, please use the Search field to download the latest version.)

Prerequisites:

The rpm will search for prerequisites and notify the user of any not present on the machine. To ensure the integrity of your download, HP recommends verifying your results with the MD5 Checksum value:

For x86: hpsmh-7.2.0-14.i386.rpm        338433c8f29a02645b0b580e0e804db8

For x86_64: hpsmh-7.2.0-14.x86_64.rpm        b9b21e53d694922bd41c264fd95447ee

Reboot Requirement:

Reboot is not required after installation for updates to take effect and hardware stability to be maintained.

Installation:

Download the rpm package to a directory on your hard drive and change to that directory. Install for x86 by typing “rpm -ivh hpsmh-< version >.i386.rpm”, or for x86_64 by typing “rpm -ivh hpsmh-< version >.x86_64.rpm”.

Known Issues

Some HP management stations will still not report health statistics after this process and may require the following additional software suite to be installed:

HP Insight Management Agents for Windows Server x64 Editions

(Note: these links may be outdated, please use the Search field to download the latest version.)

Overview

For hosts that support IPMI sensors, LogicMonitor can gather that data and integrate it into the monitoring.

Setup Requirements

All that is required is that IPMI be enabled on the hosts, and IPMI credentials be set for the ipmi.user and ipmi.pass properties located on the resources being monitored within LogicMonitor. If you enable IPMI on the host after you have already added the host into monitoring in LogicMonitor, you can manually trigger Active Discovery to speed up the process of discovering the IPMI information.

Note: IPMI devices (ie. DRACs) typically have their own IP addresses, distinct from those of their hosts. As such, they should be added as separate devices into monitoring.

Troubleshooting

If IPMI information is not showing up for hosts you expect it to be available on, ensure:

• IPMI is enabled on the host, or on the host’s management card. Often, IPMI support is disabled by default.
• The IPMI user specified in the host’s IPMI configuration is allowed to connect remotely, and that this user’s credentials are correctly entered as properties in LogicMonitor.

  Note: Depending on the manufacturer, an admin level user account may be required for some devices in order to access IPMI information. Please refer to your device manufacturer for details about the necessary credentials.

• There is no firewall blocking the collector from the IPMI port (UDP port 623).
• You have a defined script EventSource for IPMI event log messages to be received.

IPMI Memory Leak Issue

We have recently noticed memory leak issue with various IPMI versions for Windows server 2019. We observed the issue on multiple Collector versions. We recommend you to use Windows Server 2022 on Collectors that need to monitor devices with IPMI.

Importing IPMI LogicModules

If you don’t currently have IPMI LogicModules installed in your portal (or if you don’t have the latest versions), you can import them from the LogicMonitor repository.

For the most part, standard monitoring of LSI MegaRAID RAID controller expansion cards are provided out-of-box as long as SNMP is enabled on your device and the sas_snmp and sas_ir_snmp packages are installed from LSI. However, depending on your operating environment, there may be additional steps involved:

1. For Linux machines, please enable SNMP access on your server via the net-snmp package and the datasource should appear on your host shortly after.
2. For Windows machine, please enable SNMP access by enabling the SNMP service. To do this, navigate to Programs and Features on your Windows machine and select ‘Turn Windows features on or off’ – select the checkbox next to Simple Network Management Protocol (SNMP). The datasource should appear on your host shortly after.

1. For standalone ESX hypervisors, additional steps will need to be taken to enable the SNMP service with the necessary extended LSI objects. Out-of-box, the ESXi 5.1 U1 includes LSI drivers, but not LSI SMIS package, which allows the host to see the status of the controller in Hardware Health. Please download the SMI-S provider .vib package from LSI and install from command line using the following command to resolve this issue:esxcli software vib install -v /vmfs/volumes/[datastore]/[dir]/[file].vib –no-sig-checkNote: This requires a host reboot.

SMI-S providers for VMWare 5.0, VMWare 5.X, and VMWare 6.0 can be found here.

LogicMonitor will automatically detect data sensors, and start plotting them, but does not have default thresholds, as we don’t know what the data is that’s being reported – temperature? Humidity?

You should set thresholds for the sensors.

Contact sensors are not automatically detected by Active Discovery, as there is no way to know when a sensor is active or not. Thus, you have manually define a new contact switch sensor when you add one to the device.

Note that until you have one contact sensor defined, you won’t see the datasource.  To manually add a new contact switch sensor instance, select Add Monitored Instance from the Manage device menu:

Select the Sensor Switch data datasources, make the Name something explanatory (room east water sensor, etc) and make the value as the number of the sensor (on the sensatronic box) that you’ve just activated .

LogicMonitor can monitor the underlying hardware health of your Dell system. Metrics for fans, power supplies, RAID status, individual disks, memory, chassis temperature, etc., are automatically monitored with our out-of-the-box DataSources. Depending upon the operating system in use on your Dell system, or the specifications of the system itself, LogicMonitor offers varying methods of monitoring access, as highlighted in the following sections.

Setup Requirements for Dell Systems that Provide DRAC

LogicMonitor accesses Dell servers that provide DRAC platforms via the IPMI (Intelligent Platform Management Interface) protocol. For more information on setting up monitoring via IPMI, see IPMI Support.

Setup Requirements for Dell Systems without DRAC

If your Dell system does not offer the DRAC platform, the Dell EMC OpenManage Server Administrator (OMSA) must be installed on your system in order to facilitate monitoring.

Installing OMSA on Windows

Installation on Windows systems is fairly straightforward and can be accomplished by installing the latest version of Dell EMC OMSA. For more information, see the Dell EMC support website for download and installation instructions.

Note: For Windows 2012 Dell EMC OMSA 7.2 is needed.

Once installed, you will need to ensure that SNMP is installed on the Windows device and configured to allow the LogicMonitor Collector to poll it. 
To configure, open windows services, find “SNMP Service”, and open its properties.

Configure the following:

• <Collector_IP> – The IP address of the Collector in LogicMonitor that will be monitoring this device.
• <mycommunity> – The community string used in LogicMonitor. For more information on assigning SNMP community strings to devices as properties in LogicMonitor, see Defining Authentication Credentials.

Installing OMSA on Linux

Dell EMC OMSA on Linux extends the underlying SNMP server on the system to allow access to Dell-specific information. Procedures for installing OMSA on differing Linux distributions revolve around installing the OpenManage Linux Repository and then a few packages from it:

• srvadmin-base
• srvadmin-storage

After installation, be sure to start the ‘dataeng’ service:

/etc/init.d/dataeng start

Verify that the following entry has been entered into your snmpd.conf file (commonly found in /etc/snmp/):

smuxpeer .1.3.6.1.4.1.674.10892.1

Also verify that the snmpd service has been restarted. The above line will direct incoming SNMP queries from LogicMonitor for Dell-specific metrics to the service that was installed by OMSA.

Setup Requirements for Dell Systems Running ESXi

Dell EMC OpenManage Server Administrator vSphere Installation Bundle (VIB) must be installed on your system in order to facilitate monitoring. Visit the Dell EMC support website for download and installation instructions.

Once installed, run the following ESXCLI command:

esxcli system snmp set –hwsrc indications

Associating the Dell Hardware Health DataSources with Your Resource

After installing Dell EMC OMSA (or setting the appropriate IPMI credentials), manually initiate Active Discovery to automatically associate the Dell hardware health DataSources with your resource(s). For more information on manually initiating Active Discovery, see Adding Instances. For more information on how DataSources automatically associate with resources, see How DataSources Get Applied to Resources.