ZenPacks

Dell PowerEdge ZenPack

The Dell PowerEdge ZenPack allows you to monitor Dell PowerEdge Servers, including blade servers with the Dell PowerEdge M1000e chassis.

Background

This ZenPack provides support for monitoring Dell PowerEdge Servers (11G, 12G and 13G), including blade servers with the Dell PowerEdge M1000e chassis.

Monitoring is performed via the OpenManage Server Agent (OMSA) using the SNMP API, on servers running either the Windows or Linux OS. This ZenPack also provides support for monitoring via the Dell iDRAC using the WSMAN interface, regardless of host OS.

Note: Please restart zenoss after installing this ZenPack

Releases

Version 2.0.3- Download
Released on 2017/04/10
Requires WSMAN ZenPack
Compatible with Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.x.x
Version 2.0.2- Download
Released on 2015/11/05
Requires WSMAN ZenPack
Compatible with Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.x.x
Version 2.0.1- Download
Released on 2014/08/15
Requires WSMAN ZenPack
Compatible with Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.x.x

Contents

This ZenPack provides support for monitoring Dell PowerEdge Servers (11G, 12G and 13G), including blade servers with the Dell PowerEdge M1000e chassis.

Monitoring is performed via the OpenManage Server Agent (OMSA) using the SNMP API, on servers running either the Windows or Linux OS. This ZenPack also provides support for monitoring via the Dell iDRAC using the WSMAN interface, regardless of host OS.

Please restart zenoss after installing this ZenPack

Prerequisites

External Dependencies:

  • OpenManage Server Administrator Agent 7.2.0 (OMSA Agent) should be running on Linux/Windows devices.
  • This should be verified using snmpwalk from your zenoss server:
    snmpwalk -v2c -c [community] [hostname]
  • WSMAN interface should be enabled and running on your zenoss server.

Features

The features added by this ZenPack be summarized as follows. They are each detailed further below.

  • Initial discovery and continual synchronization of relevant components.
  • Performance monitoring.
  • Event management.
  • Service impact and root cause analysis. (Requires Zenoss Service Dynamics)

Discovery

Dell M1000e Blade Chassis

The following components will be automatically discovered through the Chassis Management Controller(CMC) IP address and the host name you provide. The properties and relationships will be continually maintained.

Chassis Power Consumption
Attributes:Chassis Name, Current Usage, Peak Usage, Min Usage, Max Power, Status
Relationships:Chassis Management Controller
Chassis PowerSupply Units
Attributes:Name, Chassis, Power in Amps, Power in Watts
Relationships:Chassis Management Controller
Chassis Management Controller
Attributes:Name, System Slot, Chassis Name, Manufacturer, Service Tag, Model Name
Relationships:Chassis Power Consumption, Chassis Power Supply Units, Chassis Temperature Sensors, Chassis Slots
Chassis Temperature Sensors
Attributes:Chassis Name, Front Panel, CMC Board, CMC Processor, State
Relationships:Chassis Management Controller
Chassis Slots
Attributes:Name, Slot Name, Server Index, Service Tag, Model
Relationships:Chassis Management Controller

Dell 11g and 12g Servers

The following components will be automatically discovered through the Server IP address and the host name you provide. The properties and relationships will be continually maintained.

Main System Chassis
Attributes: Chassis Name, Manufacturer, Host Name, Service Code, Model, Service Tag, Lock Present, Chassis Type
Relationships: Physical Disks, Temperature Sensors, Power Consumption, Virtual Disks, Processors, Processor Caches, Memory Cards, ChipSets, Ports, Cooling Fans
Physical Disks
Attributes: Name, Capacity, Used Space, Free Space, State
Relationships: Main System Chassis
Temperature Sensors
Attributes: Probe Name, Temperature, State
Relationships: Main System Chassis
Power Consumption
Attributes: Name, Power, Status
Relationships: Main System Chassis
Virtual Disks
Attributes: Name, Device Name, Type, Disk Number, Read Policy, Write Policy, Cache Policy, Status, Layout
Relationships: Main System Chassis
Processors
Attributes: Name, Version, Manufacturer, Model, Speed, Core Count, Status
Relationships: Main System Chassis
Processor Caches
Attributes: Name, Processor Name, Associativity, Current Size, Maximum Size, Policy, Status
Relationships: Main System Chassis
Memory Cards
Attributes: Name, Manufacturer, Size, Type, Status
Relationships: Main System Chassis
ChipSets :Attributes: Name, Manufacturer, Slot Index, Speed, Status
Relationships: Main System Chassis
Ports
Attributes: Name, Connector Type, Security State, Status
Relationships: Main System Chassis

Rack and Tower Servers

The following additional components apply only to Rack and Tower servers.

Cooling Fans
Attributes: Name, Number, Current Speed, Location, Status
Relationships: Main System Chassis

Dell iDRAC (Dell Remote Access Controller)

The following components will be automatically discovered through the iDRAC IP address and the host name you provide. The properties and relationships will be continually maintained.

Main System Chassis
Attributes: Chassis Name, Host Name, Manufacturer, Model, Service Tag, BIOS Version, Life Cycle Controller Version, Power State
Relationships: Physical Disks, Virtual Disks, Processors, Memory Cards, ChipSets, Enclosure View, Software, Video Controller
Physical Disks
Attributes: Name, Slot Number, Security State, Bus Type, Media Type, Hot Spare, Capacity, Used Space, Free Space, State
Relationships: Main System Chassis
Virtual Disks
Attributes: Name, Layout, Read Policy, Write Policy, Size, Stripe Size, Remaining Redundancy, State
Relationships: Main System Chassis
Processors
Attributes: Name, Model, Family, Manufacturer, Speed, Core Count, CPU Status, Status
Relationships: Main System Chassis
Memory Cards
Attributes: Name, Manufacturer, Serial Number, Type, Size, Speed
Relationships: Main System Chassis
ChipSets
Attributes: Name, Manufacturer, Device Index
Relationships: Main System Chassis
Enclosure View
Attributes: Name, FQDD, Version, Slot Count, Connector, Enclosure Position
Relationships: Main System Chassis
Software
Attributes: Name, Version, Vendor ID, Installation Date
Relationships: Main System Chassis

iDRAC7 and iDRAC8 Controllers

The following additional components apply only to iDRAC7 and iDRAC8 Controllers.

Video Controller
Attributes: Name, Description, Manufacturer, Bus Number, Data Bus Width, Slot Type, PCI Device ID, PCI Vendor ID
Relationships: Main System Chassis
NIC Ports
Attributes: Name, FQDD, Link Status, PCI Device ID, Product Name, Vendor Name, Current MAC Address
Relationships: Main SystemChassis

Performance Monitoring

The following metrics will be collected every 5 minutes by default. Any other Dell PowerEdge Server metrics can also be collected by adding them to the appropriate monitoring template.

Physical Disk : Disk Utilization: disk/usage in percentage (MAXIMUM)

Temperature Sensor : Temperature: current temperature in Celsius(MAXIMUM)

Power Consumption : Power Usage: current consumption in watts (MAXIMUM)

Processor Caches : Cache Utilization: cache/ usage in percentage (MAXIMUM)

Chassis Power Consumption
Power Usage: current consumption in watts (MAXIMUM)

Dell Remote Access Controller(iDRAC) will also provide performance metrics data of the Dell PowerEdge Server. The following metrics will be collected every 5 minutes by default. Any other Dell PowerEdge Server metrics can also be collected by adding them to the appropriate monitoring template.

Physical Disk : Disk Utilization : disk/usage and disk/free space in percentage (MAXIMUM)

Processor : Processor Current Speed: processor/current speed space in MHz(MAXIMUM)

Event Management

The following event classes and their subclasses will be continually collected and passed into the Zenoss event management system.

  • Alarm
  • Event

Various information encoded in these event classes will be used to automatically determine as best as possible the following Zenoss event fields.

Standard Zenoss Event Fields:

  • device (set to device class)
  • component
  • summary
  • severity
  • eventClassKey (for mapping specific event types)

Installed Items

Installing this ZenPack will add the following items to your Zenoss system.

Configuration Properties:

  • zCollectorPlugins
  • zSnmpMonitorIgnore
  • zWSMANPort
  • zWSMANUseSSL
  • zWSMANUsername
  • zWSMANPassword

Device Classes

  • /Devices/Server/Dell/ChassisController :Chassis Management Controller will be added in this device class using Chassis IP.

  • /Devices/Server/Linux/Dell: Linux Dell Blade server will be added in this device class using Blade device IP.

  • /Devices/Server/Windows/Dell: Windows Dell Blade server will be added in this device class using Blade device IP.

  • /Devices/Server/Dell/iDRAC6: iDRAC6 controller of Blade will be added in this device class using respective iDRAC6 IP.

  • /Devices/Server/Dell/iDRAC7: iDRAC7 controller of Blade will be added in this device class using respective iDRAC7 IP.

  • /Devices/Server/Dell/iDRAC8: iDRAC8 controller of Blade will be added in this device class using respective iDRAC8 IP.

Modeler Plugins

The following plugins will be used for modeling Blade and Chassis Controller using the respective blade and Chassis Controller IP Addresses via SNMP interface.

  • ChassisControllerModeler: This plugin is for modeling Chassis Controller.

  • PowerEdgeModeler: This plugin is for modeling Blade and Rack devices.

  • zenoss.dell.snmp.DellDeviceModeler: This plugin is for retrieving the basic Dell hardware and os information. The following plugins will be used for modeling Blade and Chassis Controller details using the iDRAC controller via WSMAN interface.

  • iDRAC6Modeler: This plugin is for modeling Dell Remote Access Controller 6.

  • iDRAC7Modeler: This plugin is for modeling Dell Remote Access Controller 7.

  • iDRAC8Modeler: This plugin is for modeling Dell Remote Access Controller 8.

  • DellIDRACModeler: This plugin is for retrieving the basic iDRAC manufacturer, firmware information.

Datasource Types

  • SNMP
  • WSMAN

Monitoring Templates

  • PhysicalDisk (/Server/Linux/Dell, /Server/Windows/Dell , /Server/Dell/iDRAC6, /Server/Dell/iDRAC7, /Server/Dell/iDRAC8)
  • Temperature (/Server/Linux/Dell, /Server/Windows/Dell)
  • PowerConsumption (/Server/Linux/Dell, /Server/Windows/Dell)
  • ChassisPowerConsumption (/Server/Dell/ChassisController)
  • ProcessorCache (/Server/Linux/Dell, /Server/Windows/Dell)
  • Processor (/Server/Dell/iDRAC6, /Server/Dell/iDRAC7, /Server/Dell/iDRAC8)

Service Impact and Root Cause Analysis

When combined with the Zenoss Service Dynamics product, this ZenPack adds built-in service impact and root cause analysis capabilities for services running on Dell PowerEdge. The service impact relationships shown in the diagram and described below are automatically added. These will be included in any services that contain one or more of the explicitly mentioned components.

Internal Impact Relationships:

  • Chassis Controller access failure impacts all the blade devices available in its slots.
  • Chassis Management Controller failure impacts all related hosts, chassis slots, temperature sensors, power consumption, power supply units.
  • Blade/NonBlade Host failure impacts the related physical disks, virtual disks, temperature sensors, memory cards, processors, processor caches, power consumption, chipsets, ports, cooling fans.
  • In iDRAC modeling, Blade Host failure impacts the related physical disks, virtual disks, memory cards, processors, chipsets, enclosures, softwares and video controllers.

Most of the impacts described above follow the default policy of a node being in the worst state of the nodes that impact it. For example, a Chassis Management Controller failure will imply that all related hosts are also failed.

Usage

Adding ChassisController

Use the following steps to start monitoring ChassisController using the Zenoss web interface.

  • Navigate to the Infrastructure page.
  • Navigate to organizer Devices/Server/Dell/ChassisController.
  • Choose Add a Single Device from the add button.

Fill out the form.

  • ''Name'' can be anything you want.
  • ''Hostname or IP'' must be resolvable and accessible from the collector server chosen in the ''Collector'' field.
  • Click ''ADD''.

Adding Linux SNMP Dell Blade/Rack Device

Use the following steps to start monitoring Linux Dell PowerEdge device using the Zenoss web interface.

Navigate to the Infrastructure page.

Navigate to organizer Devices/Server/Linux/Dell.

Choose Add a Single Device from the add button.

Fill out the form.

  • ''Name'' can be anything you want.
  • ''Hostname or IP'' must be resolvable and accessible from the collector server chosen in the ''Collector'' field.
  • Click ''ADD''.

Dell Blade / Rack server that runs on Linux will be added in the /Devices/Server/Linux/Dell device class.

Adding Windows SNMP Dell Blade/Rack Device

Use the following steps to start monitoring Windows Dell PowerEdge device using the Zenoss web interface. Navigate to the Infrastructure page.

  • Navigate to organizer Devices/Server/Windows/Dell.
  • Choose Add a Single Device from the add button.

Fill out the form.

  • ''Name'' can be anything you want.
  • ''Hostname or IP'' must be resolvable and accessible from the collector server chosen in the ''Collector'' field.
  • Click ''ADD''.

Dell Blade / Rack server that runs on Windows will be added in the /Devices/Server/Windows/Dell device class.

Adding Dell Blade/Rack information to the /Server/Microsoft/Windows Organizer

Use the following steps to monitor a Windows Device using the ZenPacks.zenoss.Microsoft.Windows zenpack.

  • Navigate to the Infrastructure page.
  • Navigate to organizer Devices/Server/Microsoft/Windows.
  • Select Details
  • Select Modeler Plugins
  • Add zenoss.dell.snmp.PowerEdgeModeler and zenoss.dell.snmp.DellDeviceModeler to the Selected list
  • Save

Adding iDRAC6 Controller

Use the following steps to start monitoring iDRAC6 using the Zenoss web interface.

  • Navigate to the Infrastructure page.
  • Navigate to organizer Devices/Server/Dell/iDRAC6.
  • Choose Add a Single Device from the add button.
  • Fill out the form.
  • ''Name'' can be anything you want.
  • ''Hostname or IP'' must be resolvable and accessible from the collector server chosen in the ''Collector'' field.
  • Click ''ADD''.
  • iDRAC6 controller of Dell Blade server will be added in the /Devices/Server/Dell/iDRAC6 device class.

Use the following steps for successful modeling:

  • Select the device added.
  • Navigate to Configuration Properties.
  • Provide the values for zWSMANPassword, zWSMANPort, zWSMANUseSSL and zWSMANUserName.
  • Model the device.

Adding iDRAC7 Controller

Use the following steps to start monitoring iDRAC7 using the Zenoss web interface.

  • Navigate to the Infrastructure page.
  • Navigate to organizer Devices/Server/Dell/iDRAC7.
  • Choose Add a Single Device from the add button.

Fill out the form.

  • ''Name'' can be anything you want.
  • ''Hostname or IP'' must be resolvable and accessible from the collector server chosen in the ''Collector'' field.
  • Click ''ADD''.
  • iDRAC7 controller of Dell Blade server will be added in the /Devices/Server/Dell/iDRAC7 device class. Use the following steps for successful modeling.
  • Select the device added.
  • Navigate to Configuration Properties.
  • Provide the values for zWSMANPassword, zWSMANPort, zWSMANUseSSL and zWSMANUserName.
  • Model the device.

Adding iDRAC8 Controller

Use the following steps to start monitoring iDRAC8 using the Zenoss web interface.

  • Navigate to the Infrastructure page.
  • Navigate to organizer Devices/Server/Dell/iDRAC8.
  • Choose Add a Single Device from the add button.
  • Fill out the form.
  • ''Name'' can be anything you want.
  • ''Hostname or IP'' must be resolvable and accessible from the collector server chosen in the ''Collector'' field.
  • Click ''ADD''.
  • iDRAC8 controller of Dell Blade server will be added in the /Devices/Server/Dell/iDRAC8 device class.

Use the following steps for successful modeling.

  • Select the device added.
  • Navigate to Configuration Properties.
  • Provide the values for zWSMANPassword, zWSMANPort, zWSMANUseSSL and zWSMANUserName.
  • Model the device.

zenbatchload

Alternatively you can use zenbatchload to add devices from the command line. To do this, you must create a file with contents similar to the following. Replace all values in angle brackets with your values minus the brackets. Multiple devices can be added under the same sections.

'/Devices/Server/Dell/ChassisController' setManageIp="" '/Devices/Server/Dell/iDRAC8' setManageIp="", zWSMANUsername='', zWSMANPassword='', zWSMANPort=443, zWSMANUseSSL='true' '/Devices/Server/Dell/iDRAC7' setManageIp="", zWSMANUsername='', zWSMANPassword='', zWSMANPort=443, zWSMANUseSSL='true' '/Devices/Server/Dell/iDRAC6' setManageIp="", zWSMANUsername='', zWSMANPassword='', zWSMANPort=443, zWSMANUseSSL='true' '/Devices/Server/Windows/Dell' setManageIp="" '/Devices/Server/Linux/Dell' setManageIp=""

Examples: /Server/Dell/ChassisController CMC_1 setManageIp='10.100.10.30' /Server/Dell/iDRAC6 iDRAC6_1 setManageIp='10.100.10.32', zWSMANUsername='root', zWSMANPassword='calvin' /Server/Dell/iDRAC7 iDRAC7_1 setManageIp='10.100.10.31', zWSMANUsername='root', zWSMANPassword='calvin' /Server/Dell/iDRAC8 iDRAC8_1 setManageIp='10.100.10.30', zWSMANUsername='root', zWSMANPassword='calvin' /Server/Windows/Dell Windows-Blade setManageIp='10.100.10.27' /Server/Linux/Dell Linux-Blade setManageIp='10.100.10.29'

You can then load the Devices using zenbatchload with the following command.

zenbatchload

Upgrade

Upgrading of Dell ZenPack from version of 1.0.0 to new version 2.0.0

Refer to Prerequisites section

Use the following steps to upgrade from Dell PowerEdge 1.0.0 to 2.0.0

  • On the Zenoss Master Backup the original init.py file located in $ZENHOME/ZenPacks/ZenPacks.zenoss.Dell.PowerEdge-1.0.0-py2.7.egg/ZenPacks/zenoss/Dell/PowerEdge
  • Copy the 2.0.0 egg file onto the zenoss master filesystem
  • Extract the patched init.py with the following command: unzip Dell.PowerEdge-2.egg patches/init.py
  • Copy the init.py to $ZENHOME/ZenPacks/ZenPacks.zenoss.Dell.PowerEdge-1.0.00-py2.7.egg/ZenPacks/zenoss/Dell/PowerEdge
  • Install the 2.0.0 version of the Dell PowerEdge zenpack through UI / CLI.
  • On all collectors, run the following command if you wish to keep all performance data. This is due to a relationship change. find $ZENHOME/perf/Devices -name blade_Index* -exec sh -c 'mv "${0}" "${0/Blade_Index_/Main System Chassis}"' {} ;
  • Re-start the zenoss instance on the master.
  • Push the updates to the remote hubs/collectors.
  • Verify the Upgrading to Dell PowerEdge ZenPack 2.0.0 with the following command. zenpack --list | grep -i PowerEdge

Limitations

  • Dell Servers running VMware are not monitored by this ZenPack.
  • Currently this ZenPack does not recognize / model IO modules and Fans of Chassis.

See Upgrade section if Upgrading from 1.0.0 to 2.0.0

Changes

2.0.3

  • Fix PowerEdgeModeler modeling. (SVC-833, ZEN-23224)
  • Fix Dell PowerEdge 2.0.2 breaks Modeling Plugins page (ZPS-1273)
  • Fix modeling of IDRAC version 7. (ZEN-21718)

2.0.2

  • Add iDRAC8 and Dell 13G Server support. (ZEN-20738)
  • Add NIC components to iDRAC7 and iDRAC8 controllers. (ZEN-17954)
  • Several user interface fixes. (ZEN-20376, ZEN-16190, ZEN-14015, ZEN-13987)

2.0.1

  • Fix "compname" error during modeling. (ZEN-13273)

2.0.0

  • Add support for iDRAC.

1.0.0

  • Initial release.
Commercial

This ZenPack is developed and supported by Zenoss Inc. Commercial ZenPacks are available to Zenoss commercial customers only. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Commercial ZenPacks.

randomness