ZenPack:Enterprise Linux

Note: This Zenpack has been merged and replaced by the Linux Monitor ZenPack

Note: This ZenPack is available in commercial versions of Zenoss. Click here to request more information about this commercial ZenPack. Click here to see all commercial ZenPacks.

Organization

Zenoss, Inc.

ZenPack name

ZenPacks.zenoss.EnterpriseLinux

Enterprise Linux ZenPack

The EnterpriseLinux ZenPack extends the capabilities of the LinuxMonitor ZenPack and enables Resource Manager to use Secure Shell (SSH) to monitor Linux hosts.

Warning

The ZenPack Catalog has moved to its new home at https://www.zenoss.com/product/zenpacks as of January 17, 2017. The following information may be out of date, and this page will eventually be removed.

Support

This ZenPack is included with commercial versions of Zenoss and enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.

Releases

Version 1.3.7- Download

Released on 2013/09/19

Requires Linux Monitor ZenPack

Compatible with Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.0.x

Background

Note: This Zenpack has been merged and replaced by the Linux Monitor ZenPack

The ZenPacks.zenoss.EnterpriseLinux ZenPack extends the capabilities of ZenPacks.zenoss.LinuxMonitor and enables Zenoss platform to use Secure Shell (SSH) to monitor Linux hosts.

Zenoss platform models and monitors devices placed in the /Server/SSH/Linux device class by running commands and parsing the output. Parsing of command output is performed on the Zenoss platform server or on a distributed collector. The account used to monitor the device does not require root access or special privileges for the default modeler plugins.

Prerequisites

Prerequisite	Restriction
Product	Zenoss platform 4.x, Zenoss 2.4 or higher
Required ZenPacks	ZenPacks.zenoss.LinuxMonitor, ZenPacks.zenoss.EnterpriseLinux

Add a Linux Server

The following procedure assumes that the credentials have been set.

1. From Infrastructure > Devices, Select Add a Single Device from the Add Device menu.
2. Enter the following information:

   Adding Linux Device Information

   Name	Description
   Device Name	Linux host to model
   Device Class Path	/Server/SSH/Linux
   Discovery Protocol	Set this to auto unless adding a device with username/password different than found in the device class. If you set this to none, then you will need to add the credentials, and then manually model the device.

   
   

3. Click Add.

Set Linux Server Monitoring Credentials

All Linux servers must have a device entry in an organizer below the /Devices/Server/SSH/Linux device class.

Tip: The SSH monitoring feature will attempt to use key-based authentication before using a configuration properties password value.

1. Navigate to the device or device class in the Zenoss platform interface.
   • If applying changes to a device class:
     1. Select the class in the devices hierarchy.
     2. Click Details.
     3. Select Configuration Properties.
   • If applying changes to a device:
     1. Click the device in the device list.
     2. Select Configuration Properties.
2. Verify the credentials for the service account to access the service.

   Linux Configuration Properties

   Name	Description
   zCommandUsername	Linux user with privileges to gather performance information.
   zCommandPassword	Password for the above user.

   
   

3. Click Save to save your changes.

Resolving CHANNEL_OPEN_FAILURE Issues

The zencommand daemon's log file ($ZENHOME/collector/zencommand.log) may show messages stating:

ERROR zen.SshClient CHANNEL_OPEN_FAILURE: Authentication failure
WARNING:zen.SshClient:Open of command failed (error code 1): open failed

If the sshd daemon's log file on the remote device is examined, it may report that the MAX_SESSIONS number of connections has been exceeded and that it is denying the connection request. At least in the OpenSSH daemons, this MAX_SESSIONS number is a compile-time option and cannot be reset in a configuration file.

In order to work around this limitation of the sshd daemon, use the configuration property zSshConcurrentSessions to control the number of connections created by zencommand to the remote device.

1. Navigate to the device or device class in the Zenoss platform interface.
   • If applying changes to a device class:
     1. Select the class in the devices hierarchy.
     2. Click Details.
     3. Select Configuration Properties.
   • If applying changes to a device:
     1. Click the device in the device list.
     2. Select Configuration Properties.
2. Apply an appropriate value for the maximum number of sessions.

   Concurrent SSH Configuration Properties

   Name	Description
   zSshConcurrentSessions	Maximum number of sessions supported by the remote device's MAX_SESSIONS parameter. A common value for Linux is 10.

   
   

3. Click Save to save your changes.

Resolving Command timed out Issues

The zencommand daemon's log file ($ZENHOME/collector/zencommand.log) may show messages stating:

WARNING:zen.zencommand:Command timed out on device device_name: command

If this occurs, it usually indicates that the remote device has taken too long to return results from the commands. To increase the amount of time to return results, change the configuration property zCommandCommandTimeout to a larger value.

1. Navigate to the device or device class in the Zenoss platform interface.
   • If applying changes to a device class:
     1. Select the class in the devices hierarchy.
     2. Click Details.
     3. Select Configuration Properties.
   • If applying changes to a device:
     1. Click the device in the device list.
     2. Select Configuration Properties.
2. Apply an appropriate value for the command timeout.

   SSH Timeout Configuration Properties

   Name	Description
   zCommandCommandTimeout	Time in seconds to wait for commands to complete on the remote device.

   
   

3. Click Save to save your changes.

DMIDECODE Modeler Plugin

This plugin allows you to collect and model detailed hardware and kernel information on your Linux devices.

Since the dmidecode command requires root privileges, it needs to be run with something like sudo. Sample entries required on the sudoers file on each remote device are:

Cmnd_Alias DMIDECODE = /usr/sbin/dmidecode 
## Allows members of the zenoss group to gather modeling information 
Defaults:zenoss !requiretty 
%zenoss ALL = (ALL) NOPASSWD: DMIDECODE 

To use this plugin, add it to the list of collector plugins for the device or device class, and then remodel. For more information about working with Zenoss platform plugins, refer to Zenoss Service Dynamics Resource Management Administration.

Daemons

Type	Name
Modeler	zenmodeler
Performance Collector	zencommand

Installation

Normal Installation (packaged egg)

1. Download the appropriate egg file for the version of Zenoss you are running.
2. Ensure you are logged in as the zenoss user:

   $ sudo su - zenoss

3. Install the ZenPack:

   $ zenpack --install ZenPacks.zenoss.EnterpriseLinux-*.egg

4. Restart these services:

   $ zenoss restart

Discuss

New: Don't forget to add yourself to the Zenoss User Map!

blog comments powered by Disqus