LIVE Webinar: Dec. 19, 1pm CSTLearn how to overcome the challenges posed by containerized microservices in highly dynamic IT environments.
451 Research: Key Trends in Machine Learning, AI & Cloud
Zenoss is the only enterprise monitoring solution certified Nutanix Ready - Integrated.
Zenoss Partner Portal
Become a Partner
Learn. Discuss. Participate.Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Customer Support Portal
Zenoss Learning Center
Forrester Insights:Powering Digital Transformation With Intelligent Monitoring & Analytics
Customers for LifeAt Zenoss, our customers are at the core of everything we do.
Request A Demo
The Dell PowerEdge ZenPack allows you to monitor Dell PowerEdge Servers (including Dell EMC VxRail appliances based on PowerEdge Hardware), including blade servers with the Dell PowerEdge M1000e chassis.
This ZenPack provides support for monitoring Dell PowerEdge Servers (11G, 12G, 13G, and 14G), 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.
The features added by this ZenPack be summarized as follows. They are each detailed further below.
The following components will be automatically discovered through the Chassis Management Controller(CMC) IP address and the hostname you provide. The properties and relationships will be continually maintained.
The following components will be automatically discovered through the Server IP address and the hostname you provide. The properties and relationships will be continually maintained.
The following additional components apply only to Rack and Tower servers.
The following components will be automatically discovered through the iDRAC IP address and the hostname you provide. The properties and relationships will be continually maintained.
The following additional components apply only to iDRAC7, iDRAC8, and iDRAC9 Controllers.
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.
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.
Note: Main System Chassis, Cooling Fans, Processors and Server Power Supplies show graphs based on related Analog Sensors.
Note: Main System Chassis and Server Power Supplies show graphs based on related Server Power Supply Sensors.
Zenoss periodically polls the Dell PowerEdge iDRAC for Lifecycle Log entries and creates Zenoss events when they occur. The event polling runs by LifecycleLog datasource which is defined on the device level.
LifecycleLog Data Source Fields
The Lifecycle Log entry closely matches that of a Zenoss event. This means that corresponding Zenoss events will automatically clear when their Lifecycle Log counterparts clear.
Note: To improve performance, LifeCycle audit level logs are not monitored.
Note: Zenoss attempts to set the timestamp on Lifecycle Log events to the timestamp the Dell PowerEdge iDRAC reported their occurrence instead of the time that Zenoss collected them. For this reason, it is recommended that both your Dell PowerEdge and Zenoss servers keep accurate time.
The following fields will be populated for each event:
Standard Zenoss Event Fields
The following additional fields and potentially more will also be populated for each event. These are the fields native to a Lifecycle Log event. If an event occurs that has other fields, those fields will be added with the same poweredge.idrac.lifecycle-log prefix.
Additional Lifecycle Log Event Details
Installing this ZenPack will add the following items to your Zenoss system.
/Devices/Server/Dell/ChassisController: Chassis Management Controller will be added in this device class using Chassis IP.
/Devices/Server/Linux/Dell: Linux Dell server will be added in this device class using device IP.
/Devices/Server/Windows/Dell: Windows Dell server will be added in this device class using device IP.
/Devices/Server/Dell/iDRAC6: iDRAC6 controller will be added in this device class using respective iDRAC6 IP.
/Devices/Server/Dell/iDRAC7: iDRAC7 controller will be added in this device class using respective iDRAC7 IP.
/Devices/Server/Dell/iDRAC8: iDRAC8 controller will be added in this device class using respective iDRAC8 IP.
/Devices/Server/Dell/iDRAC9: iDRAC9 controller will be added in this device class using respective iDRAC9 IP.
/Status/PowerEdge: The event class covers the Dell PowerEdge statuses.
/PowerEdge: The event class covers Dell PowerEdge events.
/PowerEdge/Error: The error class covers Dell PowerEdge errors.
poweredge.idrac.lifecycle-log.event: Mapped to /PowerEdge event class.
poweredge.idrac.lifecycle-log.error: Mapped to /PowerEdge/Error event class.
The following plugins will be used for modeling a PowerEdge Blade or Chassis Controller details, using the respective blade or controller IP addresses via SNMP interface:
zenoss.snmp.NewDeviceMap: Determines OS and hardware manufacturer information based on the SNMP description (sysDescr).
zenoss.snmp.DeviceMap: Gathers sysDescr, sysContact, sysName, and sysLocation information and adds it to the device.
zenoss.snmp.InterfaceMap: Gathers IPv4 and IPv6 network interface information.
zenoss.snmp.HRFileSystemMap: Retrieves information about filesystems.
zenoss.dell.snmp.DellDeviceModeler: This plugin is for retrieving the basic Dell hardware and OS information.
zenoss.dell.snmp.PowerEdgeModeler: SNMP plugin that gathers Dell PowerEdge blade device information.
zenoss.dell.snmp.ChassisControllerModeler: This plugin is for modeling Chassis Controller.
The following plugins will be used for modeling a PowerEdge Rack or Blade details, using the iDRAC controller via WSMAN interface:
DellIDRACModeler: This plugin is for retrieving the basic iDRAC manufacturer, firmware information.
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.
iDRAC9Modeler: This plugin is for modeling Dell Remote Access Controller 9.
To provide a high-level overview of the modeled device, on device level a separate Dynamic View diagram is provided.
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:
External Impact Relationships:
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 blade devices are also failed.
snmpwalk -v2c -c [community] [hostname]
Use the following steps to start monitoring ChassisController using the Zenoss web interface.
Fill out the form.
Use the following steps to start monitoring Linux Dell PowerEdge device using the Zenoss web interface.
Dell Blade/Rack server that runs on Linux will be added in the /Devices/Server/Linux/Dell device class.
Use the following steps to start monitoring Windows Dell PowerEdge device using the Zenoss web interface.
Dell Blade/Rack server that runs on Windows will be added in the /Devices/Server/Windows/Dell device class.
Note: Dell PowerEdge 3.0.0 and greater no longer supports iDRAC6.
Use the following steps to start monitoring iDRAC6 using the Zenoss web interface.
Use the following steps for successful modeling:
Use the following steps to start monitoring iDRAC7 using the Zenoss web interface.
Use the following steps for successful modeling.
Use the following steps to start monitoring iDRAC8 using the Zenoss web interface.
Use the following steps to start monitoring iDRAC9 using the Zenoss web interface.
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/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'
/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.
It was found that WSMAN API isn't available for iDRAC 7 device when 1.30.30 firmware is installed, 1.31.30 update has resolved the issue. Therefore, if you get Fault Value: s:Receiver wsman:TimedOut error while connecting to your iDRAC device via WSMAN API, make sure the firmware version is updated to the recent stable version. The timeout error may appear on the other iDRAC versions as well.
Fault Value: s:Receiver wsman:TimedOut
Another confirmed solution is a restart of Dell iDRAC interface, use the following steps to restart the interface: - Open a browser software, enter the IP address of your iDRAC interface and access the administrative web interface. - On the prompt screen, enter the administrative login information. After a successful login, the administrative menu will be displayed.
Factory default access information:
View the discussion thread.
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.