The iDRAC Service Module (iSM) is a small OS-resident process that expands iDRAC management into supported host operating systems. Specifically, iSM adds the following services:

• OS information
• Lifecycle Controller Log replication into operating system
• Automatic system recovery
• Windows Management Instrumentation (WMI) providers inclusive of storage data
• Automatic Technical Support Report collection
• NVMe PCIe SSD device removal support

We have built iSM for those customers want more OS integration with iDRAC. They want to know what OS type, version, and host name is being used on the server. In place of having to create tools to import OS event logs to gather hardware health to custom tools, iSM has been built as a very lightweight service that can be used to expand iDRAC's management capabilities. For Dell's 13th generation of PowerEdge servers, iSM has been enhanced with these new features:

• Reporting of host OS IP addresses
• WMI integration with new storage reporting
• Integration of iSM with Tech Support Report
• Remote iDRAC hard reset
• iDRAC access via Host OS (Experimental Feature)
• In-band support for iDRAC SNMP alerts

These new features provide easier troubleshooting of servers by adding key OS information, and add context to SNMP traps for more intelligent alert processing. With comprehensive WMI support for Windows Server customers and seamless remote support and servicing via TSR, less effort is needed to resolve technical/health issues.

Supported Platforms:

The following is the list of supported platforms for iDRAC Service Module.

Remote iDRAC hard reset

Using iDRAC, you can monitor the supported servers for critical system hardware, firmware, or software issues. Sometimes, iDRAC may become unresponsive due to various reasons. During such scenarios, you may have to turn off the server by plugging it off from the socket, after which the iDRAC can be reset.

Using the Remote iDRAC hard reset feature, whenever iDRAC becomes unresponsive, you can perform a remote iDRAC reset operation without the need to shut down the server. To reset the iDRAC remotely, ensure that you have administrative privileges on the host OS. By default, the remote iDRAC hard reset feature is enabled.

iDRAC access via Host OS (Experimental Feature)

Using Dell’s PowerEdge Servers, you can manage the hardware or the firmware of a device through iDRAC by configuring an iDRAC dedicated network. Through the dedicated network port, you can access the iDRAC interfaces such as GUI, WSMAN, RACADM, and Redfish client.

The prerequisite to manage the hardware or the firmware is to have a dedicated connection between a device and the supported iDRAC interface. Using the iDRAC access via Host OS feature, you can connect to an iDRAC interface from an OS IP or host irrespective of the connection between a device and an iDRAC dedicated network. This feature allows you to monitor the hardware or firmware even if the iDRAC is not connected to the servers.

In-band support for iDRAC SNMP alerts

Using iDRAC, an out-of-band server management and monitoring tool, the SNMP traps/alerts can be recorded in the log. However, from a host OS systems management using in-band agent perspective, the preference is more on the SNMP alert received from the host OS than the traps received from iDRAC. When an SNMP alert is received from iDRAC, it would be challenging to determine the source of the alert as it is from an iDRAC IP and not the system IP.

Using iDRAC Service Module 2.3, you can receive SNMP alerts from the host OS which is similar to the alerts that are generated by iDRAC.

Operating system information

Server Administrator currently shares operating system information and host name with iDRAC. The iDRAC Service Module provides similar information such as host OS name, server host IP address information, OS version, Fully Qualified Domain Name (FQDN) with iDRAC. The network interfaces on the host OS are also displayed. By default, this monitoring feature is enabled. This feature is available even if Server Administrator is installed on the host OS.

Lifecycle Controller log replication into operating system

Replicates the Lifecycle Controller (LC) logs to the OS logs. All events that have the OS Log option as the target (in the Alerts page or in the equivalent RACADM or WSMAN interfaces) are replicated in the OS log using the iDRAC Service Module. This process is similar to the System Event Log (SEL) replication performed by Server Administrator.

The default set of logs to be included in the OS logs are the same as the logs configured for SNMP traps/alerts. Only the events logged in the LC log after the iDRAC Service Module was installed are replicated to the OS Log. If Server Administrator is installed, the monitoring feature is disabled to avoid duplicate SEL entries in the OS log.

In iDRAC Service Module 2.1, you can customize the location to replicate the LC logs. By default, the LC logs are replicated in the Systemgroup of the Windows logs folder in the Windows Event Viewer. You can replicate the LC logs to an existing group or create a new folder in the Application and Services Logs folder in the Windows Event Viewer.

Automatic system recovery feature

Automatic System Recovery feature is a hardware-based timer, which is used to reset the server in the event of a hardware failure. You can perform automatic system recovery operations such as reboot, power cycle, or power off after a specified time interval. This feature is enabled only when the operating system watchdog timer is disabled. If Server Administrator is installed, the monitoring feature is disabled to avoid duplicate watchdog timers.

Windows Management Instrumentation Providers

Windows Management Instrumentation Providers available with iDRAC Service Module exposes hardware data through Windows Management Instrumentation (WMI). WMI is a set of extensions to the Windows Driver Model that provides an operating system interface through which instrumented components provide information and notification. WMI is Microsoft's implementation of the Web-Based Enterprise Management (WBEM) and Common Information Model (CIM) standards from the Distributed Management Task Force (DMTF) to manage Server hardware, operating systems and applications. WMI Providers helps to integrate with Systems Management Consoles such as Microsoft System Center and enables scripting to manage Microsoft Windows Servers.

Automatic Technical Support Report collection

The Technical Support Report (TSR) feature in iDRAC collects information about the hardware, OS and relevant application data and compresses this information. Currently, you have to manually run the OS Collector tool to generate the TSR. Using iDRAC Service Module 2.0 or later versions, the OS Collector tool automatically collects relevant OS and hardware information. Automatic Support Log collection including OS and Application Information Collection with TSR.

By using iDRAC Service Module you reduce the number of manual steps to collect the Technical Support Report as the collection process is automated.

NVMe PCIe SSD device removal support

You can remove a Non-Volatile Memory Express (NVMe) Pheripheral Component Interconnect Express (PCIE) Solid State Device (SSD) without shutting down or rebooting the system. When you are removing a device, all the activities associated with the device must be stopped to prevent data loss. To prevent loss of data use the Prepare to Remove option, which stops all the device-associated background activities, after which you can remove the NVMe PCIe SSD physically.

Links:

Linux download v2.1

Windows download v2.1

For other supported OSs, please visit support.dell.com.

This post was written by Sathish D of the Dell OpenManage Connections team.

OVERVIEW

HP Operations Manager (HPOM) supports scheduled task policy, which you can use to invoke external applications from the HPOM console. Dell Smart Plug-in (SPI) has a scheduled task policy, which retrieves the device health status and generates corresponding status messages in the HPOM console.

This post explains the Periodic Health monitoring of Dell Servers, Dell Remote Access Controllers (DRAC’s) and Dell Chassis using Dell SPI Scheduled Status Poll Polices with HP Operation Manager for Windows.

 Periodic Health Monitoring Scheduled Status Poll policies for Dell servers, DRAC’s, and Dell Chassis in HPOM console.

PREREQUISITES:

           Before scheduling status poll policies, complete these prerequisites

• Configure Simple Network Management Protocol (SNMP) and enable support for Dell servers, DRAC’s, and Chassis.
• Configure Web Services- Management (WS-MAN on ESXi Servers.
• Install OpenManage Server Administrator (OMSA) in Windows and Linux Servers, and install supported Dell OpenManage (OM) - bundles on ESXi servers.
• Schedule the Dell Hardware Auto-grouping policy in the HPOM console to classify Dell servers, DRAC’s, and Dell Chassis under the Dell groups.

Reference Documents:

• For SNMP configuration on Windows and Linux Servers,               
  
  

<ADMIN NOTE: Broken link has been removed from this post by Dell>

• For OMSA installation on Linux Servers,
    http://en.community.dell.com/techcenter/systems-management/f/4494/t/19425042.aspx
  
  
• For OM Bundle Installation and SNMP Configuration on ESXi Servers, 
    http://en.community.dell.com/techcenter/systems-management/f/4494/t/19424735.aspx

• For SNMP Configuration and for more details for DRAC and Chassis, 
    http://supportapj.dell.com/support/edocs/software/smdrac3/

MONITORING DELL SERVER’s IN HPOM CONSOLE:

Once the Dell Hardware Auto-grouping Policy is completed, the policy identifies the Dell servers that were discovered (in-band or out-of-band through iDRAC7 with available Licenses), and then creates hierarchies on both the Nodes and Services in HPOM console.

• Node Hierarchy:  Classification based on type of Dell servers (either Monolithic or Modular), representing the object with the Service Tag for the node
• Service Hierarchy: Classification based on type of operating systems installed in the server, representing the object both with the node’s service tag and its global health status.

Hierarchical representation of classified Dell Servers in Service Hierarchy:

(Both in-band and Out-of-band Management through iDRAC7 devices)

DEPLOYING THE DELL SERVER SCHEDULED STATUS POLL POLICY:

The scheduled task policy “Dell Server scheduled Status Poll” is used to monitor the overall system health status of Dell Servers in the HPOM Console, both in-band and Out-of-band with iDrac7 devices, as well as bare metal devices via iDrac7 devices. The default interval of this policy is every day 2:00 A.M. The interval can be changed to custom value as required; policies are deployed via the Management Server.

Once the policy is run, the health status of the device is queried through the communication protocol and its corresponding status with associated severity is displayed in the HPOM console. The health status message is also associated with the device, classified under Dell groups in both the Node and Service hierarchies.

The schedule task policy acknowledges the health message and posts the current health status message for the classified Servers and Integrated Dell Remote Access Controller (iDRAC) 7 devices in the Active Message Browser of the HPOM console. The latest health status of the servers and the iDRAC 7 devices is always displayed in the HPOM console.

The Scheduled Status Poll policy generates health messages with three different severities in the HPOM console.

    Message Association in Service Hierarchy:

Once the Dell Servers Scheduled Status Poll policy is run, the policy retrieves the overall health status of the classified Dell servers, and iDRAC 7 devices. The retrieved health status is mapped with its corresponding health messages (Normal, Warning, or Critical).The health message is associated with the server’s and iDrac7 devices (child node: Global System Status) and are seen on the Active Message Browser of the HPOM Console. The message severity of the child node is propagated to the parent Node in both the Node and Service Hierarchies

Service Hierarchy: Only the Global System Status message with its corresponding health severity will be associated and updated for the node. The health severity will propagate to the device parent group.

Node Hierarchy:  In Node hierarchy, SNMP Trap Messages and Health messages are associated with the Server node; the worst case message severity is propagated to its parent Node group.

Health Status Message Association for Server Node in Service Hierarchy:

TROUBLESHOOTING STEPS:

When the device Global health is warning or critical status, follow these steps to troubleshoot the issues:

-       Review the outstanding messages in the Active Message browser of the device.  If any issues exist, resolve them as per instructions in the message browser.

 -      Launch 1:1 console  for further troubleshooting,

• Dell Servers (in-band)

• • Dell OpenManage Server Administrator (OMSA) console launch for all Dell Windows and Linux OS servers (in-band)
  • Dell OpenManage Web Server Administrator console launches for Dell ESXi Servers (in-band).

• Dell Servers (Out-of –Band)

• • Dell Remote Access Controller (DRAC) Console launches for all Dell Windows, Linux, and ESXi Servers and iDRAC7 (bare metal) devices.
  • Dell OpenManage Server Administrator (OMSA) console launch from all Dell servers (Out-of-Band).

 -          Launch Dell tools for further troubleshooting, and to take the corrective action:

•  Warranty Report:

                     The Warranty report page is used to retrieve warranty related information via the service tag                 associated with the system.  You can review the warranty details of the system and also renew                   the warranty.

• OpenManage Essentials (OME) :

                    OME Console can be used to verify the device and component’s health. It also provides rich                 device inventory information. You can launch the OME console to further troubleshoot the device                 specific information.

MONITORING DELL DRAC’s AND CHASSIS IN HPOM CONSOLE:

Once the Dell Hardware Auto-grouping Policy is completed, it identifies discovered Dell DRAC’s and Chassis;

• Dell DRAC devices create the Hierarchies based on device type (Drac5 or iDrac6) and the server type (Monolithic or Modular), and are get classified under the respective DRAC5, or iDRAC6 groups in both the Nodes and Services.
• Dell Chassis create the hierarchies based on device type (CMC or DRAC/MC) and are get classified under respective Dell Chassis (CMC or DRAC/ MC) groups in both the Nodes and Services.

Hierarchical Representation of Dell DRAC’s and Chassis in Services: 

 DEPLOYING THE DELL DRAC’s AND CHASSIS STATUS POLL POLICY:

The scheduled task policy “Dell DRAC’s and Chassis scheduled Status Poll” monitors the overall system health status of Dell DRAC’s (DRAC5 and, iDRAC6 devices both Monolithic and Modular) and Dell Chassis (Chassis Management Controller (CMC) and DRAC/MC) devices in the HPOM console. The default interval of this policy is every day 2:00 A.M. The interval can be changed to the custom value as required. Policies are deployed via the Management Server.

Once the policy is run, the health status of the device is queried through the SNMP protocol and a corresponding message with the associated severity will be shown in the HPOM console. The health status message is also associated with the device, classified under Dell groups in the both Node and Service Hierarchies.

The schedule task policy acknowledges the health message and posts the current health status message for the classified DRAC’s and Chassis in the Active Message Browser of the HPOM console .The latest health status of the DRAC’s and Chassis is always displayed in the HPOM console.

Message Association in Service Hierarchy:

Once the Dell DRAC’s and Chassis Scheduled Status Poll policy is run, the policy retrieves the overall health status of the classified Dell DRAC’s and Chassis. The retrieved health status is mapped with the appropriate health message (Normal, Warning or Critical).The health message is associated for the DRAC’s or Chassis child nodes (Child node: Global System Status) and are seen on the Active Message Browser of the HPOM Console. The message severity for the node (Normal, Warning, and Critical) is propagated to the parent Node in both Node and the Service Hierarchies.

 Service Hierarchy: Only the Global System Status message with its corresponding health severity will be associated and updated for the node. The health severity will propagate to the device parent group.

Node Hierarchy:  In Node hierarchy, SNMP Trap Messages and Health messages are associated with the Server node; the worst case message severity is propagated to its parent Node group.

 Health Status Message Association for Chassis in Service Hierarchy:

TROUBLESHOOTING STEPS:

When the device Global health status is “Warning” or “Critical”, follow these steps to troubleshoot the issues:

-     Review the outstanding messages in the Active Message browser of the device.  If any issues exist– resolve them as per instructions in the message browser.

 -    Launch 1:1 console  for further troubleshooting,

• Dell DRAC console launches for all DRAC5 and, iDRAC6 devices, both Monolithic and Modular.
• Dell CMC console launches for all Dell CMC and DRAC/MC device.

 -     Launch Dell tools for further troubleshooting, and to take the corrective action:

• Warranty Report:
• Open Manage Essentials (OME) :

APPENDIX:

Refer to the following links:

• Dell OpenManage Connection for HP Operations Manager
• OpenManage Connections for 3rd Party Console Integration Forum

Executive Summary

The Dell Remote Access Controller 5 (DRAC 5) is a systems management hardware and software solution designed to provide remote management capabilities, crashed system recovery, and power control functions for Dell systems.

By communicating with the system's baseboard management controller (BMC), the DRAC 5 (when installed) can be configured to send you e-mail alerts for warnings or errors related to voltages, temperatures, intrusion, and fan speeds. The DRAC 5 also logs event data and the most recent crash screen (for systems running the Microsoft Windows operating system only) to help you diagnose the probable cause of a system crash.

The DRAC 5 has its own microprocessor and memory, and is powered by the system in which it is installed. The DRAC 5 may be preinstalled on your system, or available separately in a kit.

 ( top )

Dell iDRAC5.0 Overview - by Brian Summers

(Please visit the site to view this video)



(Please visit the site to view this video)

The following post was authored by Ashutosh Engg, Manager for Dell connection for HP/IBM/CA products.

Dell OpenManage Connection for IBM Tivoli Netcool/OMNIbus

With the release of Dell OpenManage Connection v1.0 for IBM Tivoli Netcool/OMNIbus 7.3.1, Datacenter customers who use Netcool/OMNIbus console will be able to monitor Dell Servers and Dell EqualLogic devices.

 The salient features of this connection are as follows:

• Event Monitoring of Dell Servers and Dell EqualLogic Storage Arrays
• Automatic Event Correlation of Dell Server And Dell EqualLogic SNMP Traps
• 1x1 Console launch support of Dell servers and Dell EqualLogic devices

IBM Tivoli Netcool/OMNIbus is a service level management (SLM) system that delivers real-time, centralized monitoring of complex networks and IT domains.  Tivoli Netcool/OMNIbus improves service availability and resiliency with real-time service management for data centers, network operations centers and IT domains. It also integrates with the broader Tivoli portfolio for a single view of operations, including cross-domain correlation, and common visualization, navigation, security and reporting and launch-in-context capabilities.

(Please visit the site to view this video)

Datacenter customers who use Netcool/OMNIbus console can use this connection with no additional cost for monitoring Dell Servers and Dell EqualLogic devices.

This release integrates with IBM OMNIbus components ObjectServer, MTTrapd SNMP probe, Desktop, and Web GUI. The integration consists of automation triggers for supporting automatic correlation of Dell Server and Dell EqualLogic events, tools and menus for supporting the console launch for the Dell devices.

 The entry point is MTTrapd SNMP Probe (multi-threaded SNMP trap listener provided by the IBM OMNIbus), which intercepts and process SNMP traps from devices (like Dell Servers and Dell EQL Storage devices).

 The ObjectServer is the core component of Tivoli Netcool/OMNIbus and is a high-speed memory-resident database that acts as a centralized data repository for the fault information.  ObjectServer provides support to configure the conversion classes, tools (event context with association of conversion class) and automations (procedures, triggers and user-defined signals) in its database using the OMNIbus Administrative console.  Dell Automation Triggers (OMSA automation trigger and OMSS automation trigger) configurations are configured at ObjectServer in order to support Dell Server events correlation.  Dell Tool configurations are also configured at ObjectServer and it consists of Dell Menus, Menu-items and its corresponding association of tools and class

Event List is an OMNIbus Desktop application, which is used for viewing and managing events in the OMNIbus environment.

Tivoli Netcool/OMNIbus Web GUI is a Web-based application that processes network events from one or more data sources (ObjectServers) and has its own database for tools, user, roles, etc.,. Similar to Desktop user, a Web GUI user will be able to launch event context-specific Dell Tools from the Active Event list web application.

Dell Server and Dell EqualLogic Storage Arrays Events are shown in OMNIbus Console with respective classes to uniquely identify their events. Here is an Example:

Dell Server and EqualLogic events are automatically correlated when the corresponding resolution events are received at OMNIbus console. The problem events correspond to the resolution events will be automatically cleared and both the events will be shown with Clear severity events. Here is an example:

Dell EqualLogic Storage Arrays supports 1x1 console for managing the EqualLogic devices. Once the Events are shown in the OMNIbus console, the context based menu items are available on right clicking the events to launch the EqualLogic Group Manager console from the OMNIbus console. Here is an example to launch the EqualLogic Group Manager Console.

Dell Server supports 1x1 console for managing them. Once the Events are shown in the OMNIbus console, the context based menu items are available for launching OpenManage Server Administrator web console from OMNIbus console. The Server Administrator Web Server console tool can be used for the servers where the remote management support is enabled.  Hence this supports the login to the multiple servers using the OpenManage Server Administrator Web Server console. The Server Administrator console tool can be used for the direct 1x1 console launch for the servers.

Here is an example of Launching the OpenManage Server Administrator and OpenManage Server Administrator Web Server Console directly from the OMNIbus Event List.

For the latest version of this release, see the Dell Support website at "support.dell.com" .  Release documents are available here. <ADMIN NOTE: Broken link has been removed from this post by Dell>

Contents: Documentation - Downloads - Whitepapers - Videos - Resources

Dell OpenManage Server Administrator (OMSA) is a software agent that provides a comprehensive, one-to-one systems management solution in two ways: from an integrated, Web browser-based graphical user interface (GUI) and from a command line interface (CLI) through the operating system. 

OMSA is designed so that system administrators can manage server systems both locally and remotely on a network. It also interfaces with OpenManage Essentials (OME) console, which allows for monitoring of the systems in your data center from a single interface.

Currently the OMSA agent can be installed on 32 and 64 bit versions of Windows Server and Red Hat Linux as well as Novell SUSE Linux.

Details for Server Administrator v8.3

29 March 2016
The links to the download can be found at: OMSA v8.3 Download

Installation:

• Support for PowerEdge R830
• Added support for the following operating systems:
  • Novell SUSE Linux Enterprise Server 12 Service Pack 1
  • VMware ESXi 5.5 update 3
  • VMware ESXi 6.0 update 1 and update 2
  • Red Hat Enterprise Linux 7.2

NOTE: Citrix XenServer Operating System support has been dropped for both Server Administrator and Storage Management.

Enhancements:

• Support for the following web browsers:
  • Google Chrome version 45
  • Mozilla Firefox version 40

• Support for the following features:
  • GP-GPU card enablement and thermal status on PowerEdge C4130
  • SNMP Test Trap Button feature on all Windows and Linux Operating Server.
    NOTE: This feature is not available on any VMware vSphere operating system versions.

Storage Management:

• Added new functionalities in Storage Management:
  • Support for 2.5-inch 4KB SATA drives on PERC 9 family of hardware controllers.
  • Support for rear SATA on PowerEdge R730xd connected to software RAID S130 controller.
  • Support for PMC SAS Expander on PowerEdge R730.
  • Support for Samsung PM1725 NVMe device.
  • Support for flexible backplane zoning functionality on backplanes with 24 slots — PowerEdge R630 and PowerEdge R730xd.
  • Support for setting Disk Cache Policy at physical disk and virtual disk level on software RAID S130 controller.
  • Support for setting non-RAID disk cache policy on PERC 9 controllers.
  • Support for HBA H330 Adapter/Mini controller.

Details for Server Administrator v8.2

15 September 2015
The links to the download can be found at: OMSA v8.2 Download

Installation:

• Added support for the following operating systems
  • Novell SUSE Linux Enterprise Server 11 SP4
  • VMware ESXi 6.0 Update 1
  • VMware ESXi 5.1 Update 3 on 11^th generation of PowerEdge servers
  • Red Hat Enterprise Linux 7.1
  • Red Hat Enterprise Linux 6.7

NOTE: Citrix XenServer Operating System support has been dropped for both Server Administrator and Storage Management.

Enhancements:

• Added following features:
  • Security Enhancement for SSL protocols
  • Operating System Alert Logging Filter
  • Hardware Event Log Rotation for 10^th and 11^th generations of PowerEdge servers

• Browser Support:
  • Google Chrome version 42
  • Firefox Firefox version 37
  • Safari Version 8.0

• Support for the following network cards
  • Emulex LightPulse LPe15000B-M8-D 1-Port 8G Gen 5 Fibre Channel Adapter
  • Emulex LightPulse LPe15002B-M8-D 2-Port 8G Gen 5 Fibre Channel Adapter
  • Emulex LightPulse LPm15002B-D 2-Port 8G Gen 5 Fibre Channel Adapter
  • Emulex OneConnect OCe14102B-U1-D 2-port PCIe 10GbE CNA
  • Emulex OneConnect OCm14104B-U1-D 4-port 10GbE rNDC CNA
  • Emulex OneConnect OCm14102B-U4-D 2-port 10GbE bNDC CNA
  • Emulex OneConnect OCm14102B-U5-D 2-port 10GbE Mezz CNA
  • Emulex OneConnect OCe14102B-N1-D 2-port PCIe 10GbE NIC
  • Emulex OneConnect OCm14104B-N1-D 4-port 10GbE rNDC NIC
  • Emulex OneConnect OCm14102B-N5-D 2-port 10GbE Mezz NIC
  • Emulex OneConnect OCm14102B-N6-D 2-port 10GbE bNDC NIC
  • Mellanox ConnectX-3 PrDual Port 10 GbE SFP+ PCIE Adapter
  • Mellanox ConnectX-3 PrDual Port 40 GbE QSFP+ Adapter
  • Mellanox ConnectX-3 PrDual Port 10 GbE KR Mezzanine Adapter

Storage Management:

• For 13th generation of PowerEdge servers, support for:
  • 3.5-inch 4KB SATA drives on PERC 9 Controller

• Added new functionalities in Storage Management:
  • Support to configure physical disks into Redundant Array of Independent Disks (RAID) 0 virtual disks
  • Support for setting the Remaining Rated Write Endurance Threshold for PCIe SSDs, SAS SSDs, and SATA SSDs
  • Support for RAID 10 virtual disk online capacity expansion

Details for Server Administrator v8.1

7 April 2015
The links to the download can be found at: OMSA v8.1 Download

Installation:

Added support for the following operating systems.

• Novell SUSE Linux Enterprise Server 12
• VMware ESXi 6.0
• Citrix XenServer 6.5. However, this Operating System is not supported for Storage Management.
• Added support for Red Hat Enterprise Linux 7.0 operating system on 11th generation or later PowerEdge servers

• Added support for the following servers:
  • PowerEdge FC830
  • PowerEdge M830
  • PowerEdge FC430
  • PowerEdge C4130
  • Dell PowerEdge FD332

Enhancements:

• Added following features:
  • A new utility, “omwsupdate”, to upgrade the Tomcat web server.
  • CLI commands to generate new certificate signing requests and import Certificate Authority signed certificates.
  • PKCS#12 certificate import on the Server Administrator GUI.
  • Automate Trusted Enterprise CA certificate Upload

• Browser Support:
  • Google Chrome version 38
  • Firefox version 33
  • Safari Version 7.0.6

• Support for the following network cards:
  • Emulex OCm14104-N1-D QP 4x10Gb rNDC Ethernet Network Adapter
  • Emulex OCm14102-N6-D DP 10Gb bNDC Ethernet Network Adapter
  • Emulex OCm14102-N1-D Dual-port 10Gb PCIe Ethernet Network Adapter
  • Emulex OCm14102-N5-D DP 10Gb bMezz Ethernet Network Adapter
  • Intel X710 QP 10Gb KR 4x10Gb Network Daughter Card
  • Intel I350/X710 2x10Gb BT 2x10Gb SFP+Network Daughter Card
  • Intel X710 4x10GE SFP+/DA FH PCIe Ethernet Network Adapter
  • Intel X710 2x10GE SFP+/DA FH PCIe Ethernet Network Adapter

Storage Management:

• For 13G PowerEdge servers, added support for:
  • All Spark SSD
  • Samsung Half Height Half Length (HHHL) PCIe card
  • 4KN SAS drives
  • Software RAID Hotplug support on PERC S130
  • Changing controller mode from RAID to HBA and vice versa on PERC9.
  • Samsung NVME drive on VMware ESXi v6.0
• Added support for 6GBps SATA drives
• Added support for following Dell PERC 9 controllers:
  • FD33xD controller
  • FD33xS controller

Dell OpenManage

Dell OpenManage is a set of systems management applications built using industry standard protocols and specifications. Dell OpenManage is not a product within itself, but rather a brand name for the suite of products in the portfolio. Server Administrator (OMSA) is part of OpenManage family.

You can refer various Enterprise Systems Management manuals to learn more about the Dell products.

Server Administrator v8.3 Documentation

Refer all the below documents from the Server Administrator v8.3 Manuals page.

• Dell OpenManage SNMP Reference Guide for iDRAC and Chassis Management Controller - PDF (1947 KB)
• Dell OpenManage SNMP Reference Guide Version 8.3 - PDF (11428 KB)
• Server Administrator Version 8.3 Installation Guide — Linux - PDF (1257 KB)
• Server Administrator Version 8.3 Installation Guide — Microsoft Windows - PDF (1657 KB)
• Systems Management Tools And Documentation Version 8.3 Installation Guide - PDF (285 KB)
• Dell OpenManage Server Administrator Version 8.3 CIM Reference Guide - PDF (4161 KB)
• Server Administrator 8.3.0 Release Notes - PDF (911 KB)
• Dell OpenManage Server Administrator 8.3 — Technical Information Sheet for Microsoft Windows Server 2016 - PDF (86 KB)
• Server Administrator Installation and Management 8.3.0 Release Notes - PDF (246 KB)
• Systems Management Tools And Documentation 8.3.0 Management Consoles Installation Release Notes - PDF (118 KB)
• Systems Management Tools And Documentation 8.3.0 Supported Systems Release Notes - PDF (150 KB)
• Dell OpenManage Server Administrator Version 8.3 Command Line Interface Guide - PDF (4427 KB)
• Dell OpenManage Server Administrator Version 8.3 User's Guide - PDF (2037 KB)
• Server Administrator Storage Management 8.3 User’s Guide - PDF (6641 KB)

Note: See the OpenManage Software page, for documents related to OpenManage Systems Management Overview Guide, Software Support Matrix, Software Compatibility Matrix, Port Information Guide, Messages Reference Guide, and so on.

Dell OpenManage Software version 8.3 Documentation is available at Dell OpenManage Software 8.3

Previous Server Administrator Documentation

Dell OpenManage Server Administrator Manuals

OpenManage Server Administrator Downloads

OMSA v8.3 Downloads

OMSA v8.3 can be downloaded from the following links.
Please refer Server Administrator Installation Guide and Support Matrix to install these packages on the supported operating system.

Windows OMSA:

• Dell OpenManage Server Administrator Managed Node (Windows - 32 bit) (191 MB)
• Dell OpenManage Server Administrator Managed Node (Windows - 64bit) (201 MB)

Windows miscellaneous:

• • Active Directory Snap-in Utility (32bit) (43 MB)
  • Active Directory Snap-in Utility (64bit) (42 MB)
  • BMC Utility (32 bit) (5 MB)
  • DRAC Tools, includes Racadm (32bit) (5 MB)
  • DRAC Tools, includes Racadm (64bit) (5 MB)
  • Dell OpenManage Deployment Toolkit Windows Driver Cabinet File (82 MB)
  • Dell OpenManage Deployment Toolkit (Windows - 64Bit) (209 MB)
  • Dell OpenManage Server Administrator Managed Node - DUP (164 MB - 64bit, 151 MB - 32bit)

Linux OMSA:

• Dell OpenManage Server Administrator Managed Node (Consolidated) (1014 MB)
• Dell OpenManage Server Administrator Managed Node (RHEL7 - 64bit) (Distribution Package, 260 MB)
• Dell OpenManage Server Administrator Managed Node (RHEL6 - 64bit) (Distribution Package, 263 MB)
• Dell OpenManage Server Administrator Managed Node (SLES 12 - 64bit) (Distribution Package, 239 MB)
• Dell OpenManage Server Administrator Managed Node (SLES 11 - 64bit) (Distribution Package, 251 MB)

Linux miscellaneous:

• • Dell OpenManage Linux Remote Access Utilities (52 MB)
  • Dell OpenManage Deployment Toolkit (Linux - 64Bit) (221 MB)
  • Dell OpenManage Deployment Toolkit Seamless Package (49 MB)

ESXi OMSA VIB:

• Dell OpenManage Server Administrator vSphere Installation Bundle (VIB) for ESXi 6.0  (7 MB)
• Dell OpenManage Server Administrator vSphere Installation Bundle (VIB) for ESXi 5.5  (7 MB)
• Dell OpenManage Server Administrator vSphere Installation Bundle (VIB) for ESXi 5.1  (7 MB)

To use the ESXi VIB with VMWare vSphere application, you can utilize the packages from Dell VMWare depot.

• Dell VMWare Depot (Download OMSA VIBs for different ESXi versions)
• Dell VMWare Depot (SSL)

Miscellaneous:

• Dell Systems Management Tools and Documentation DVD ISO, v8.3 (1494 MB)
• Server Driver Pack OM 8.3 (538 MB)
• Dell OpenManage MIBs for PowerEdge,v8.3 (261 KB)

OMSA v8.2 Downloads

OMSA v8.2 can be downloaded from the following links.
Please refer Server Administrator Installation Guide and Support Matrix to install these packages on the supported operating system.

Windows OMSA:

• Dell OpenManage Server Administrator Managed Node (Windows - 32 bit) (190MB)
• Dell OpenManage Server Administrator Managed Node (Windows - 64bit) (200MB)

Linux OMSA:

• Dell OpenManage Server Administrator Managed Node (Consolidated) (1008 MB)
• Dell OpenManage Server Administrator Managed Node (RHEL7 - 64bit) (Distribution Package, 258 MB)
• Dell OpenManage Server Administrator Managed Node (RHEL6 - 64bit) (Distribution Package, 261 MB)
• Dell OpenManage Server Administrator Managed Node (SLES 12 - 64bit) (Distribution Package, 238 MB)
• Dell OpenManage Server Administrator Managed Node (SLES 11 - 64bit) (x64) (Distribution Package, 250 MB)

ESXi OMSA VIB:

• Dell OpenManage Server Administrator vSphere Installation Bundle (VIB) for ESXi 6.0 (7 MB)
• Dell OpenManage Server Administrator vSphere Installation Bundle (VIB) for ESXi 5.5 (7 MB)
• Dell OpenManage Server Administrator vSphere Installation Bundle (VIB) for ESXi 5.1 (7 MB)

To use the ESXi VIB with VMWare vSphere application, you can utilize the packages from Dell VMWare depot.

• Dell VMWare Depot (Download OMSA VIBs for different ESXi versions)
• Dell VMWare Depot (SSL)

OMSA v8.1 Downloads

OMSA v8.1 can be downloaded from the following links.
Please refer Server Administrator Installation Guide and Support Matrix to install these packages on the supported operating system.

Windows OMSA:

• Dell OpenManage Server Administrator Managed Node (Windows - 32 bit) (189 MB)
• Dell OpenManage Server Administrator Managed Node (Windows - 64bit) (189 MB)

Linux OMSA:

• Dell OpenManage Server Administrator Managed Node (Consolidated) (644 MB)
• Dell OpenManage Server Administrator Managed Node (RHEL7 - 64bit) (Distribution Package, 182 MB)
• Dell OpenManage Server Administrator Managed Node (RHEL6 - 64bit) (Distribution Package, 181 MB)
• Dell OpenManage Server Administrator Managed Node (SLES 12 - 64bit) (Distribution Package, 134 MB)
• Dell OpenManage Server Administrator Managed Node (SLES 11 - 64bit) (Distribution Package, 146 MB)

ESXi OMSA VIB:

• Dell OpenManage Server Administrator vSphere Installation Bundle (VIB) for ESXi 6.0 (6 MB)
• Dell OpenManage Server Administrator vSphere Installation Bundle (VIB) for ESXi 5.5 (6 MB)
• Dell OpenManage Server Administrator vSphere Installation Bundle (VIB) for ESXi 5.1 (6 MB)

To use the ESXi VIB with VMWare vSphere application, you can utilize the packages from Dell VMWare depot.

• Dell VMWare Depot (Download OMSA VIBs for different ESXi versions)
• Dell VMWare Depot (SSL)

XenServer (Supplemental Pack):

• XenServer 6.5 (103 MB)

Resources

• Dell OpenManage Storage Services (OMSS) (Know more about storage management features)
• Dell OpenManage System Management Tools (Know more about Dell OpenManage Products)
• Dell OpenManage Essentials (Management console to remotely manage Dell devices) 
• Dell Troubleshooting Tool (Used in several of the videos below to test SNMP connection)
• Sample PowerShell scripts (To query system details from OMSA's WMI classes)
• How to install and configure OMSA on ESX 4.x

Whitepapers

• OpenManage Systems Management with iDRAC, iSM, & OMSA: selecting the right components for specific server management requirements
• Deploying OMSA on VMware ESXi Using Dell Online Depot and VMware Update Manager
• How to setup and configure ESXi 5 for use in OpenManage Essentials
• Configure VMware ESX Classic with OpenManage Essentials (OME)
• Granular Installation and Sanity Check for Management Interfaces on Microsoft Windows Operating System
• Dell OpenManage Server Administrator – Single Sign-On

Videos

 Configuring RAID 5 Virtual Disk using Server Administrator 

(Please visit the site to view this video)

OMSA Web Browser Installer

(Please visit the site to view this video)

Install OMSA on Citrix XenServer

(Please visit the site to view this video)

Linux SNMP Configuration + OMSA Installation for use with OpenManage Essentials

(Please visit the site to view this video)

ESXi4 SNMP Configuration + OMSA Installation for use with OpenManage Essentials

(Please visit the site to view this video)

Windows 2008 SNMP Configuration + OMSA Installation for use with OpenManage Essential

(Please visit the site to view this video)

Windows Granular Install (How to exclude various management interfaces SNMP, WMI, CLI, OS logging)

Starting with OMSA v7.2, during installation you can choose to exclude the management interfaces which you are not interested in. By default all these will be installed. Excluding any of the management interface has the impact on the way you can access the server details.

(Please visit the site to view this video)

Linux Granular Install (How to exclude various management interfaces SNMP, CLI, OS logging)

Starting with OMSA v7.2, during installation you can choose to exclude the management interfaces which you are not interested in. By default all these will be installed. Excluding any of the management interface has the impact on the way you can access the server details.

(Please visit the site to view this video)

How to use Fluid Cache (v7.3 and Onwards)

Fluid Cache is a solution that creates a large-scale, low-latency cache by using PCIe-SSD. It also includes features to prevent data loss or corruption while using caching techniques to increase performance.

(Please visit the site to view this video)

Virtual Disk Creation Wizard

You can create (any supported) RAID volumes in a more usable and effective approach. This video primarily showcase the user interactive pages of the same.

(Please visit the site to view this video)

 (1014 MB)

OpenManage Essentials (OME) management console replaces and improves upon ITA. You can find OME content at http://www.delltechcenter.com/OME

Dell IT Assistant (ITA) is a console for managing Dell servers, storage arrays, tape libraries, network switches, printers, and clients distributed throughout a network. Through proactive alerts and notifications, Systems Administrators gain increased control over the availability of Dell platforms from a central console. ITA is a component of the Dell OpenManage suite of products, is standards-based, and free to Dell customers.

Dell IT Assistant allows for easy identification of systems experiencing problems via alerts to administrators, helping to reduce the risk of system downtime that could impact businesses. Using ITA's Web-enabled graphical user interface, systems administrators can easily monitor systems anywhere within their network.

Getting Started and Software Support Matrix for IT Assistant

If you are new to ITA, please visit this OpenManage / ITA quick start guide:

Dell TechCenter 101 article on Systems Management
Installing and Troubleshooting Dell IT Assistant

To find out which operating systems and browsers support ITAm please visit this
Support Matrix for OpenManage (including IT Assistant)<ADMIN NOTE: Broken link has been removed from this post by Dell>

Manuals

For more details on Dell IT Assistant please browse the IT Assistant Manuals and Users Guide.

Downloads

To get the latest version of ITA, please visit the OpenManage Download Page.

IT Assistant Demo

ITA Server Updates Demo with Online Repository
By Scott Hanson
Download .WMV file ~8MB
This demo shows the new Online Repository functionality of IT Assistant to keep firmware/BIOS/drivers up to date with the latest versions that are available on the Dell.com support Web site.
(Please visit the site to view this video)

Dell IT Assistant Whitepapers

Remote Microsoft® SQL Server™ Use with IT Assistant Step-by-Step - Using OpenManage ITA with a remote SQL Connection
By Krishna Mohan and Manoj Poonia

Dell IT Assistant Power Solutions Articles

Introducing ITA 7
http://www.dell.com/downloads/global/power/ps3q05-20050179-Shetty.pdf

Configuring IT Dell OpenManage IT Assistant to Monitor Non-Dell Servers
http://www.dell.com/downloads/global/power/ps1q07-20070163-Saiprasad-OE.pdf

Using IT Assistant for Effective Systems Management
http://www.dell.com/downloads/global/power/ps2q07-20070238-Ramakrishnan-OE.pdf

Discovering Dell/EMC Storage Devices with IT Assistant
http://www.dell.com/downloads/global/power/ps2q07-20070238-Ramakrishnan-OE.pdf

Remote performance monitoring with IT Assistant
http://www.dell.com/downloads/global/power/ps4q06-20060326-Thathireddy-OE.pdf

Monitoring and Managing Agentless Servers Using IT Assistant
http://www.dell.com/downloads/global/power/ps4q06-20070158-John.pdf

Quick Links:

What is the Dell Chassis Management Controller (CMC)?

The Dell Chassis Management Controller (CMC) is an embedded system management hardware and software solution to manage:

• Multiple servers
• Networking
• Storage

It provides a secure browser-based interface that enables an IT administrator to take inventory, perform configuration and monitoring tasks, remotely power on/off blade servers and enable alerts for events on servers and components in the blade chassis. It has its own microprocessor and memory and powered by the modular chassis it is plugged into. The discovery is built-in and CMC has a dedicated internal network. The blade enclosure, which can hold multiple blade servers, provides power, cooling, various interconnects and additional systems management capabilities. Unlike a tower or rack server, a blade server cannot run by itself; it requires a compatible blade enclosure. For more information about the enclosures offered by Dell, please visit these links.

What makes it compelling to many customers is that blade servers are typically optimized to minimize the use of physical space and energy while still providing ample computing power. It is worth pointing out that the term “blade” or “blades” is largely interchangeable with the term “server node” when referring to the Dell PowerEdge VRTX platform, though the blades themselves are not interchangeable between different types of enclosures. Thus a server node from Dell PowerEdge VRTX is not physically compatible with the M1000e due to slightly different physical connections.

One of CMC’s more interesting features is multi-chassis management. This capability (which was introduced in CMC version 3.1) can monitor up to 9 fully loaded M1000e and VRTX chassis or 20 FX2 chassis with no additional cabling via a single web interface.

The CMC interface integrates with each blade or server node’s iDRAC module, so administrators can perform server-specific iDRAC functions such as performing updates, changing settings, or opening a remote console session from the CMC interface. Click here for more information on iDRAC-related management.

Additionally, CMC allows you to back up and replicate settings on the chassis, and save or apply BIOS profiles for individual blade servers so that adding new blades or chassis to your environment is easier and more automated. With newer versions of CMC, it is even possible to assign settings to an empty slot, so that the settings will be applied when a blade is inserted at some point in the future!
You can also capture a complete Chassis Inventory across all of your chassis that will return detailed information on all of the blades, IO modules, iDRAC cards, etc in your environment.

CMC is an innovative systems management tool built on proven and familiar Dell OpenManage design, and is available with these platforms:

Platform CMC Specific Information

  ( top )

What is iDRAC?

The Integrated Dell Remote Access Controller with Lifecycle Controller (iDRAC6 with Lifecycle Controller 1 or iDRAC7 with Lifecycle Controller 2) is an embedded device in all Dell PowerEdge™ servers that helps IT administrators manage, monitor, update, and deploy Dell servers.

The Integrated Dell Remote Access Controller (iDRAC) is designed to make server administrators more productive and improve the overall availability of Dell servers. iDRAC alerts administrators to server issues, helps them perform remote server management, and reduces the need for physical access to the server.

iDRAC7 with Lifecycle controller technology is part of a larger datacenter solution that helps keep business critical applications and workloads available at all times. The technology allows administrators to deploy, monitor, manage, configure, update, troubleshoot and remediate Dell servers from any location, and without the use of agents. It accomplishes this regardless of operating system or hypervisor presence or state.   

iDRAC7 Video Overview

(Please visit the site to view this video)

iDRAC7 Releases

( top )

NEW -- Dell iDRAC Service Module

The integrated Dell Remote Access Controller (iDRAC) Service Module is an optional, lightweight software application that can be installed on Dell 12th Generation Servers with iDRAC7 to provide additional systems management information. This lightweight agent runs in the host operating system and provides monitoring functionality similar to OpenManage Server Administrator (OMSA). This new offering bridges the gap between iDRAC's monitoring coverage and that which the full OMSA agent provides today. Some of the key features include:

• Lifecycle Controller Log replication in OS log (for Server Hardware Information via the OS/Hypervisor Log itself)
• Watchdog functions for dependent iDRAC monitoring functions:
  • Host name
  • OS Name
  • OS Version

n.b. the memory footprint of the iSM is 3-5MB. For comparison, OMSA occupies 100+ MB.

Download version 1.0 (includes release notes and Windows and Linux versions)

The new iSM page in the iDRAC GUI can be used to select the monitoring functions required. For more installation information, please review the Dell iDRAC Service Module 1.0 Installation Guide. You can also take a look at this blog post about installing and configuring iSM.

 ( top )

  ( top )

iDRAC7 12th Generation Licensing Summary

At a high level, the features and offerings for iDRAC are similar between iDRAC6 and iDRAC7. Dell provides three main offerings: Basic Management, Express, and Enterprise. As in Dell’s 11th generation servers, Basic Management (called BMC in 11th generation) is the default for servers 200-500 series. For 600 series and above, iDRAC Express is the default offering that is part of the base configuration. It does not require a license to be installed, backed up, or managed. Express offers embedded tools, console integration, and simplified remote access.

However, most IT administrators want a deeper, more inclusive solution that allows them to manage servers as if they were physically near the server, and this is available by upgrading to the Enterprise license level, which is fully digital.

Because all 600-series servers ship with iDRAC7 Express enabled, customers can take advantage of the features and benefits provided by iDRAC7 with Lifecycle Controller 2.0 technology. Customers with 200-500 series can also upgrade their systems to either Express or Enterprise by simply installing a license key. A physical part is required on 200-500 series to enable dedicated NIC and vFlash. Dell offers an online portal to keep track all of your iDRAC licenses; for example, which servers have Express, Enterprise, or even Trial licenses. In the unlikely event of motherboard failure, Dell also stores a copy of the key and makes it available to you in an online License Management portal (https://www.dell.com/support/licensing/).   

Utilizing the common language of industry standard protocols, non-Dell Systems Management products can be frequently configured to recognize Dell™ PowerEdge™ servers. The most popular protocol to use is SNMP with the particulars of the Dell implementation documented in the SNMP Reference Guide.

Basically four steps involved in setting this up:

• Install the OpenManage™ Server Administrator (OMSA) on the servers to be monitored. This agent maps the specifics of the Dell hardware and makes it available over the network via SNMP.
• Configure the SNMP settings on OMSA (which is actually in the OS) as well as the Dell Remote Access Card (DRAC) and Baseboard Management Controller (BMC) if you have them and want to use them as well. Typical configuration includes setting the community name, trap destination, and security for limiting SNMP traffic to the station doing the monitoring and Read Only access.
• Configure the monitoring product to discover or recognize the PowerEdge server by compiling or importing the SNMP the Dell-specific information or MIM. Success in this step is
• Configure the monitoring product to recognize the SNMP traps from the PowerEdge server.

And a reminder that additions and questions are always welcome. Just start or add to a thread at the bottom of this (and every) page!

Open Source Tools

Integrating OpenManage Server Administrator with Nagios and Ganglia has been written up in Dell Power Solutions and in another article, Managing with OpenNMS was also covered.

Systems Insight Manager

Another frequently used application is HP's Systems Insight Manager (SIM). While the latest versions recognize Dell servers, the SNMP information (MIB) in the application may need to be updated to reflect the latest PowerEdge features as listed in the What's New section of the SNMP reference guide for that release.

A good paper titled Integrating Dell PowerEdge Servers into an Environment Managed by HP Systems Insight Manager 5.0 goes into the details.

OpenManage Mobile Overview

Dell OpenManage Mobile is a software application that enables a user to securely perform a subset of datacenter monitoring and server remediation tasks from a mobile device.

OMM is supported for Android and iOS mobile devices.

OMM is supported on Android and iOS mobile devices.

OpenManage Mobile can connect to your datacenter through the Dell OpenManage Essentials management console. This allows a user to monitor all systems managed by OpenManage Essentials such as Dell Servers, Storage, Networking, and Firewall appliances and any other supported third party appliance from your mobile device.

OpenManage Mobile can also connect to a Dell PowerEdge server directly through the iDRAC interface. Once connected, a user can perform several basic management functions on the server. OpenManage Mobile can connect to a server in two possible ways:

1. Remotely using Wi-Fi or broadband network from anywhere.
2. Physically at the data center using Near Field Communications (NFC) technology. This requires a Dell 13G PowerEdge server equipped with an iDRAC Quick Sync bezel. (This connectivity is supported only on Android Mobile devices.)

Key benefits

• Flexible schedule for system administrators: Monitor your data center systems from anywhere at anytime
• Increase business productivity: Reduce response time on critical alerts by taking server remediation actions from your mobile device

Key Features

• Connect to multiple OpenManage Essentials servers from a single mobile device.
• Connect to multiple 12G and 13G servers individually through the iDRAC.
• Connect to 13G servers through the iDRAC Quick Sync bezel (Android only).
• Forward server details, health status, network info, firmware info, and log entries from iDRAC via email using compatible email clients.
• Establish connection with individual 12G & 13G server OS desktops remotely using Virtual Network Computing (VNC). Note: This needs a Third Party app download from Apple App Store or Google Play Store.
• Receive critical alert notification on your mobile device as they arrive into your OpenManage Essentials management console.
• Acknowledge, forward and delete alerts from your mobile device.
• Browse device details, health status, firmware inventory, and event logs of individual systems.
• Access server warranty information and QRL support pages directly from the mobile device

Perform server management functions such as Power On, Power cycle, Reboot, or Shutdown from the mobile application.

What is New in OpenManage Mobile 1.5

• Conveniently unlock OpenManage Mobile app with Fingerprint Sensor
  • Select the option “use fingerprint to authenticate,” and then easily unlock OMM app with the touch of a finger
• Get in-depth details of server CPUs, Memory, and Location
  • CPUs: Now includes clock speed, cores, threads, L3 cache size, etc.
  • Memory: Now includes serial number, part number, actual/rated speed, etc.
  • Location: Get slot, rack, aisle, room, and data center information
• Ask Dell a question, or send product feedback from the OMM app
  • Initiate a conversation with Dell Engineers, or provide product feedback through the “Contact Dell” option

In addition, OMM 1.5 will continue to support all features already in OMM 1.4, listed below.

What is New in OpenManage Mobile 1.4

• Demo Mode – OpenManage Mobile end users (customers, technicians, sales, etc.) can preview the capabilities of OpenManage Mobile utilizing an offline, pre-populated “demonstration database” included in the download of both the Android and iOS software.

• Enhanced views of data on tablet devices– relevant information is consolidated on a single screen when feasible

• Rapid identification of compromised systems in the data center – OMM end userscan set server LEDs to blink intermittently, visually informing  IT Admins of systems requiring service

• Multiple UI refreshes, enhancements and improvements – including the ability to launch the iDRAC GUI in the mobile browser and enable VNC settings in iDRAC/LC

• Share of Anonymous Use Case Data - OpenManage Mobile end users can opt-in to share anonymous usage data with Dell.  The data is utilized to improve the end user experience and functional capabilities of the application. 

• Support for the latest iOS 9 and Android 6.0 Marshmallow

FAQ: iDRAC Quick Sync & OpenManage Mobile - October 2014

Minimum Requirements 

• Mobile device running Android OS v 4.0.3 or higher OR iOS 7.1 or higher
• OME v1.3 or OME v2.0 management console (for data center monitoring features)
• 12G & 13G servers (for 1:1 connection through IDRAC)
• 13G servers (R630, R730, R730 XD) and the iDRAC Quick Sync Bezel (for at-the-box features)

Videos

Value proposition video for iDRAC with Quick Sync enabled by OMM

(Please visit the site to view this video)

Video showing iDRAC Quick Sync features with OMM 

(Please visit the site to view this video)

Video explaining the value proposition of the application –

(Please visit the site to view this video)

A video explaining the 4 key steps involved in using the application -

(Please visit the site to view this video)

Download

https://play.google.com/store/apps/details?id=com.dell.omm

Documents   

OpenManage Mobile v1.5 User Guide (for Android) 

OpenManage Mobile v1.5 User Guide (for iOS)

OpenManage Mobile Best Practices White Paper

iDRAC QuickSync Technical Guide - Nov. 2014

Understanding OpenManage Mobile Security White Paper

OpenManage Mobile TIP of the day

12/02/2014 - iDRAC Quick Sync

Certain Android handsets do not autonegotiate well at all NFC speeds. This might be an Android OS bug or a bug in the chipset silicon of the handset. So far we have not managed to isolate any vendor or Android OS version that  has this problem. It happens to be random across manufacturers, but consistent to a handset model.

Of the supported 106, 212, and 424 kbps for Quick Sync, only 106 kbps works effectively.

If you have a a device that has the above-mentioned problem during Quick Sync, then you are advised to launch the “Add via Quick Sync” animation within the OMM app before you perform an Quick Sync Scan, in order to have a successful scan.

For the devices that  do not have this problem, you can be in any state of using the app (even minimized) and the app is launched when you attempt to do a Quick Sync read.

03/18/2014 - Push Notifications

Question – I am able to connect to my OME through 3G/4G connections and get notifications. When I am not connected to my OME server I still keep receiving notifications from the devices I am monitoring. Why is this happening? How can I stop this?

Answer – When a user adds an OME to the OMM app on the phone, he/she chooses a filter for “push notifications”. This is the second screen of the “Add OME” wizard. Whenever OME receives an alert that matches the filter chosen by the user it sends an alert update via the end users phone network to the mobile device. If “All Alerts” was chosen, the user will receive all alerts that are received by OME. Ideally an administrator should set the filter to only those alerts that are critical and are of interest to avoid alert overload.

The alerts will get pushed to your mobile phone even when you are no longer connected to the OME, and away from your company network. These messages are not warnings about lack of connection to OME. As an OME administrator, you would want to receive these alerts even when not connected to the OME (for example when you are offsite or it is after work hours), since they usually indicate problems in your data center. After receiving one or more alerts log onto OMM, connect to the OME, and then view more details on the alerts. After browsing through the alert details take action on the alert, without having to physically access the OME or the targets managed by OME. If you don’t log onto OMM, the alerts will accumulate as they are still marked “unread.”

If you don’t want to receive alerts when not connected to the OME this feature can be turned off. There are several ways to do this.

1)      Log onto OMM, edit the OME’s connection and change your filter settings to “None” or to the filter you are most interested in. You have to be connected to the OME to make this change. A user can always re-subscribe to the right filter as his roles and responsibilities changes over time.

2)      Log onto OME via a web browser, and in the “Preference” section you will see your phone listed in the “Mobile Settings” page. You can choose to delete or disable your device from that list. 

OpenManage Mobile Forum -

Have a question or feedback on OMM. Start a discussion here.

Others –

OpenManage open source license document

What is iDRAC?

The integrated Dell Remote Access Controller (iDRAC) with Lifecycle Controller is embedded within every Dell PowerEdge™ server and provides functionality that helps IT administrators deploy, update, monitor, and maintain Dell servers with no need for any additional software to be installed. The Dell iDRAC works regardless of operating system or hypervisor presence because from a pre-OS or bare-metal state, iDRAC is ready to work because it is embedded within each server from the factory.

If you are new to iDRAC with Lifecycle Controller, check out the "how to" videos we have on youtube.com here.

The Integrated Dell Remote Access Controller (iDRAC) is designed to make server administrators more productive and improve the overall availability of Dell servers. iDRAC alerts administrators to server issues, helps them perform remote server management, and reduces the need for physical access to the server.

Download the iDRAC8 with Lifecycle Controller Specification Sheet here.

( top )

 ( top )

  ( top )

iDRAC with Lifecycle Controller Technology Licensing Summary

Dell provides three main offerings: Basic Management, Express, and Enterprise. As in Dell’s 11th generation servers, Basic Management (called BMC in 11th generation) is the default for servers 200-500 series. For 600 series and above, iDRAC Express is the default offering that is part of the base configuration. It does not require a license to be installed, backed up, or managed. Express offers embedded tools, console integration, and simplified remote access.

However, most IT administrators want a deeper, more inclusive solution that allows them to manage servers as if they were physically near the server, and this is available by upgrading to the Enterprise license level, which is fully digital. Dell also stores a copy of the key and makes it available to you in an online License Management portal (https://www.dell.com/support/licensing/).

Quick Links:

(Please visit the site to view this video)

CMC 4.4 (released June 2013) Overview

What is the M1000e?

The M1000e is Dell’s foundation for a blade server solution. It provides the infrastructure (industry-leading power & cooling, networking and blade manageability) for companies who choose to deploy blade-based server solutions. Its components include:

• The Dell Chassis Management Controller (CMC) is a systems management hardware and software solution for managing multiple Dell blade chassis.
• PowerEdge servers- M420, M520, M620, M820, M610, M610X, M710, M710HD, M905 and M910 Blade Servers.
• Blades Manageability Options- CMC, iDRAC, Dell AIM, Dell OpenManage Integration Suite for Microsoft System Center, and Dell OpenManage Integration for VMware vCenter.
• Integrated Networking

( top )

( top )

  ( top )

• Capture and replicate chassis configurations through XML, based on the Chassis Configuration Profile.

• Backup or restore through XML based on chassis configuration profile.

• Create and deploy a library of Boot Identity Profiles (boot from iSCSI/SAN configurations) to enable a quick restore of workload to a spare server.

• Support for launching IOA GUI on the Homepage and I/O Module overview page.

Quick Links:

What is CMC for FX?

The Dell PowerEdge FX architecture lets you precisely tailor, quickly deploy, and easily manage your infrastructure. With compute, storage and I/O modules in just 2U of rack space and 50% more available server-side storage, you can build a software-defined converged infrastructure that scales quickly and easily. In order to manage this platform, Dell is using its proven Chassis Management Controller (CMC) to manage the overall platform as well as its servers, networking components, and storage devices. With its familiar, easy-to-learn and use interface, Dell CMC lets you choose and use the system management style that best fits your needs. Manage FX servers individually via each embedded iDRAC with Lifecycle Controller as you would with traditional rack servers to integrate easily into server-level processes. Or manage FX servers collectively as you might already do with blade servers, using the Dell Chassis Management Controller (CMC) to manage FX. Either way, you can view and manage up to 20 separate FX systems from a single CMC management console for simplified collective management. As is the case with VRTX, Dell provides licensing choices for either comprehensive Enterprise or entry-level Express CMC options, whichever best suits a customer's needs.

Quick Links:

What is CMC for VRTX?

The newly announced Dell PowerEdge VRTX is a revolutionary, easy-to-manage, remote and office-optimized platform that converges servers, storage and networking into a compact package. It can hold up to 4 server nodes, up to 48TB of integrated, shared storage, and network switching.

Unique VRTX Features

More than simply a small blade server, the Dell PowerEdge VRTX offers something that no other blade server solution has: the ability to use PCIe slots. By combining the density of blade servers with the flexibility of rack server I/O options with PowerEdge VRTX, Dell gives you the flexibility to use less expensive PCIe cards while still being managed through shared chassis management. Another exciting new feature is VRTX's shared storage and on-board RAID controller. Pulling this all together into one, easy-to-manage platform is where VRTX shines.

CMC's role

Part of each VRTX platform, CMC is a dedicated, hot-pluggable module (a second, redundant unit is optional) within the platform that provides a secure web/browser-based interface that is used to take inventory, perform configuration and monitoring tasks, remotely power on/off blades and enable alerts for events on servers and components in the blade chassis. CMC integrates with each of the VRTX server nodes’ embedded iDRAC module, so users can perform iDRAC functions such as opening a remote console session from the CMC interface. Chief among those configuration tasks is setting up shared storage, creating virtual disks and managing PCI slot assignments. Like iDRAC7, CMC for VRTX is licensed in two different varieties: Express and Enterprise. More details on the difference between what comes with each license for both CMC and iDRAC7 for VRTX is available here.

( top )

( top )

( top )

Hardware

( top )

  ( top )

An OpenManage DVD is currently shipped with every PowerEdge server. The current version is 8.4. This DVD image (ISO) contains these OpenManage portfolio components:

• Dell OpenManage Server Administrator Managed Node (Linux Consolidated)
• Dell OpenManage Server Administrator Managed Node for each RHEL version supported
• Dell OpenManage Server Administrator Managed Node for each SLES version supported
• Dell OpenManage Server Administrator Managed Node for Xen version supported
• Dell OpenManage Server Administrator Managed Node for ESXi version supported
• Dell OpenManage Server Administrator Managed Node for Win 32 OS supported
• Dell OpenManage Server Administrator Managed Node for Win 64 OS supported
• Dell OpenManage Linux Remote Access Utilities
• Dell OpenManage Active Directory Snap-in Utility(32 bit)
• Dell OpenManage Active Directory Snap-in Utility(64 bit)
• Dell OpenManage BMC Utility
• Dell OpenManage DRAC Tools, includes Racadm (32bit)
• Dell OpenManage DRAC Tools, includes Racadm (64bit)
• Dell OpenManage Deployment Toolkit(Linux)
• Dell OpenManage Deployment Toolkit (Windows)
• Dell OpenManage MIBs for PowerEdge
• Dell Systems Management Tools and Documentation DVD ISO
• Dell iDRAC Service Module (Windows)
• Dell iDRAC Service Module (For Linux)
• Dell iDRAC Service Module (VIB) for ESX
• Dell iDRAC Service Module for XenServer

The ISO file (disc image) used to create this DVD has been, and will continue to be, offered on Dell’s support website for customers to download.

ISO Download: http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=8H5YW

Manuals: Main Server Administrator v8.4 Manuals page.

• Server Administrator Version 8.4 Installation Guide - Linux - PDF (1341 KB)
• Server Administrator Version 8.4 Installation Guide - Microsoft Windows - PDF (1727 KB)
• Systems Management Tools And Documentation Version 8.4 Installation Guide - PDF (311 KB)
• Server Administrator Installation and Management 8.4.0 Release Notes - PDF (261 KB)
• Systems Management Tools And Documentation 8.4.0 Supported Systems Release Notes - PDF (162 KB)

Quick Links:

DCIM Extensions Library Profile Collection

iDRAC8 (13th Generation PowerEdge - 2.40.40.40)

iDRAC8 (13th Generation PowerEdge - 2.30.30.30)

iDRAC8 (13th Generation PowerEdge - 2.20.20.20)

iDRAC8 (13th Generation PowerEdge - 2.10.10.10) 

iDRAC8 (13th Generation PowerEdge - 2.00.00.00 & 2.05.05.05)

iDRAC7 1.55.55 with Lifecycle Controller 2 1.4.0

iDRAC7 1.51.51 with Lifecycle Controller 2 1.3.0

The same set of profiles are applicable for both the above releases. 

CMC  for VRTX  2.1.0

CMC  for VRTX  1.3.0

CMC  for VRTX  1.2.5

CMC  for VRTX  1.0

CMC  for M1000e

iDRAC7 with Lifecycle Controller Technology   2.1.0

  iDRAC7 with Lifecycle Controller Technology 2.0.0

 iDRAC6 with Lifecycle Controller Technology  1.5.1

 iDRAC6 with Lifecycle Controller Technology  1.4.0

 iDRAC6 with Lifecycle Controller Technology  1.3.0

 iDRAC6 with Lifecycle Controller Technology  1.2.0

Other profile documents currrently published in this library (in alphabetical order by title):

• DCIM Active Directory Client Profile 1.0
• DCIM Active Directory Client Profile 2.0
• DCIM Power Supply Profile 1.0
• DCIM Power Topology Profile 1.0
• DCIM Power Utilization Profile 1.0
• DCIM SMASH Collections Profile 1.0
• DCIM Virtual Media Profile 1.0

Quick Links:

DCIM Extensions Library MOF Collection

DCIM is a schema that describes Dell extensions to the DMTF Common Information Model (CIM). DCIM schema describes the classes that represent various Dell management domains such as monitoring, inventory, update and configuration. These classes are exposed through Dell platform management access points such as iDRAC and CMC.  

The DCIM schema classes are described in the below MOF (Managed Object Format) files. Console developers and script writers can take advantage of the MOF files to process the objects returned from Dell platform management access points. Since DCIM schema extends from DMTF CIM schema, DCIM MOF files must be used in conjunction with DTMF CIM MOF files. DCIM MOF files together with DMTF CIM MOF files yield the full description DCIM class attributes such as properties and methods.

You may freely download and use the MOFs on this page and referring pages as long as you do not change the notice included in the files. If not already included, this notice will apply.

Back to DCIM Library page.

Quick Links: 

Executive Summary

With the launch of the Dell PowerEdge 13th generation servers on Sept 9th, 2014, Dell has enhanced our embedded management without the need to install a software based agent within the host operating system. At the heart of the 13th generation servers embedded management is the iDRAC8 with Lifecycle Controller technology, which allows users to perform useful tasks such as configure BIOS and hardware settings, deploy operating systems, update drivers, change RAID settings, and save hardware profiles. Together, they provide a robust set of management functions that can be leveraged throughout the entire server lifecycle.

If you are new to using iDRAC with Lifecycle Controller, check out the "how to" videos we have on youtube.com here.

Faster, More Efficient, More Secure Local and Remote Deployment, Configuration and Updates
Dell Lifecycle Controller simplifies server lifecycle management— from provisioning, deployment, patching and updating to servicing and user customization—for servers located both locally and remotely. It was delivered as part of the Dell Remote Access Controller or iDRAC (Express, Enterprise and vFlash) starting with Dell PowerEdge 11G servers. On 12G servers, the vFlash feature is included with the iDRAC7 Enterprise License, so you no longer have to separately license vFlash starting with Lifecycle Controller 2. Dell’s 12G servers only use Express or Enterprise licensing. Lifecycle Controller includes managed and persistant storage that embeds systems management features and Operating System device drivers directly on the server, thus eliminating the media-based system management tools and utilities traditionally needed for systems management.  

Lifecycle Controller reduces the time and number of steps taken to accomplish tasks, reduces potential for error, enhances server and application uptime and security, and results in more efficient IT management. Developed on the industry standard Unified Extensible Firmware Interface (UEFI) platform and Web Services for Management (WSMan) interfaces, Lifecycle Controller provides an open environment for console integration that also allows for custom scripting for Lifecycle Controller. Leading systems management consoles (e.g., Microsoft® System Center Configuration Manager, BMC Software BladeLogic® Operations Manager, Symantec™ Deployment Solution, Dell™ Management Console) have integrated Dell Lifecycle Controller, thus offering its features and capabilities to existing infrastructures where those consoles are installed.  

Why did Dell develop Lifecycle Controller?
When Dell examined common management tasks and the inefficiencies associated with them, we discovered something interesting – it wasn’t the tools that were making management tasks take so long, it was how they were delivered. The most common activities like provisioning, deploying, and updating required multiple tools, multiple forms of media and scouring the Web for the latest enablement tools, including drivers and firmware. This traditional delivery model resulted in inefficient use of time, a potential for error and potential exposure to security risks.

  ( top )

( top )

 ( top )

 ( top )

 ( top )

  ( top )

  ( top )

Other References

Additional Scripting Examples

Step 1: Install Nagios-Core on Ubuntu 16.04.01 LTS (Xenial Xerus)

• Install the following pre-requisites and all of their associated dependencies. You can ignore this step these are already installed on your Ubuntu management node:

• • Apache2 web server

  • PHP

  • Apache2 PHP and CGI module

  • GD Graphics development library

# Install apache2 and all of its associated dependencies

anupam@ubuntu:~$ sudo apt-get install apache2 apache2-bin apache2-data apache2-utils libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap liblua5.1-0

# Install PHP

anupam@ubuntu:~$ sudo apt-get install php-common php7.0 php7.0-cli php7.0-common php7.0-fpm php7.0-json  php7.0-opcache php7.0-readline

# Install apache2 mod-php module

anupam@ubuntu:~$ sudo apt-get install libapache2-mod-php7.0

# CGI module is installed as during apache2 installation but disabled by default; Enable it

anupam@ubuntu:~$ sudo a2enmod cgi

# Install libgd-dev and all of its associated dependencies

anupam@ubuntu:~$ sudo apt-get install libgd-dev libexpat1-dev libfontconfig1-dev libfreetype6-dev libice-dev libjbig-dev  libjpeg-dev libjpeg-turbo8-dev libjpeg8-dev liblzma-dev libpng12-dev  libpthread-stubs0-dev libsm-dev libtiff5-dev libtiffxx5 libvpx-dev  libx11-dev libx11-doc libxau-dev libxcb1-dev libxdmcp-dev libxpm-dev  libxt-dev x11proto-core-dev x11proto-input-dev x11proto-kb-dev  xorg-sgml-doctools xtrans-dev zlib1g-dev

• Create nagios user and nagcmd group:

anupam@ubuntu:~$ sudo useradd nagios

anupam@ubuntu:~$ sudo groupadd nagcmd

anupam@ubuntu:~$ sudo usermod -a -G nagcmd nagios

• Download the latest release of Nagios (version 4.2.1 at the time of writing this article) from www.nagios.com :

anupam@ubuntu:/tmp$ wget https://assets.nagios.com/downloads/nagioscore/releases/nagios-4.2.1.tar.gz

• Extract the package and navigate to the /tmp/nagios-4.2.1 directory:

anupam@ubuntu:/tmp$ tar –zxvf nagios-4.2.1.tar.gz

anupam@ubuntu:/tmp$ cd nagios-4.2.1

anupam@ubuntu:/tmp/nagios-4.2.1$

• Compile and install Nagios:

# Run the Nagios configure script, passing the name of the group you created earlier

anupam@ubuntu:/tmp/nagios-4.2.1$ ./configure --with-command-group=nagcmd

# Compile the Nagios source code

anupam@ubuntu:/tmp/nagios-4.2.1$ make all

# Install the compiled files, CGI and HTML files in /usr/local/nagios

anupam@ubuntu:/tmp/nagios-4.2.1$ sudo make install

# Install the init file in the /etc/init.d

anupam@ubuntu:/tmp/nagios-4.2.1$ sudo make install-init

# Install and configure permissions on the directory for holding the external command file

anupam@ubuntu:/tmp/nagios-4.2.1$ sudo make install-commandmode

# Install sample config files in /usr/local/nagios/etc

anupam@ubuntu:/tmp/nagios-4.2.1$ sudo make install-config

• Next step for us would be to install the Nagios web configuration files. However, on Ubuntu 16.04.01, apache2 configuration files are installed in /etc/apache2. As a result, when you try to install the Nagios web configuration files using “sudo make install-webconf”, it will fail because it is unable to find /etc/httpd directory. So, in order to fix it, we will have to copy the sample httpd.conf configuration file manually in /etc/apache2/conf-available and then enable it.

# Install nagios web configuration files

anupam@ubuntu:/tmp/nagios-4.2.1$ sudo make install-webconf

/usr/bin/install -c -m 644 sample-config/httpd.conf /etc/httpd/conf.d/nagios.conf

/usr/bin/install: cannot create regular file '/etc/httpd/conf.d/nagios.conf': No such file or directory

Makefile:296: recipe for target 'install-webconf' failed

make: *** [install-webconf] Error 1

# Let’s copy the sample httpd.conf to the apache2 configuration files directory

anupam@ubuntu:/tmp/nagios-4.2.1$ sudo cp sample-config/httpd.conf /etc/apache2/conf-available/nagios.conf

# Enable the nagios’ apache2 configuration file

anupam@ubuntu:/tmp/nagios-4.2.1$ cd /etc/apache2/conf-available

anupam@ubuntu:/etc/apache2/conf-available$ sudo chmod 644 nagios.conf

anupam@ubuntu:/etc/apache2/conf-available$ sudo a2enconf nagios

anupam@ubuntu:/etc/apache2/conf-available$ cd ../conf-enabled

anupam@ubuntu:/etc/apache2/conf-enabled$ ls –l nagios.conf

lrwxrwxrwx 1 root root 29 Oct  7 08:22 nagios.conf -> ../conf-available/nagios.conf

• Copy the Event handler directory and change its ownership:

anupam@ubuntu:/etc/apache2/conf-available$ cd /tmp/nagios-4.2.1

anupam@ubuntu:/tmp/nagios-4.2.1$ sudo cp –rvf contrib/eventhandlers/ /usr/local/nagios/libexec/

anupam@ubuntu:/tmp/nagios-4.2.1$ sudo chown -R nagios:nagcmd /usr/local/nagios/libexec/eventhandlers

• Create nagiosadmin user and generate password of nagiosadmin using htpasswd command. Please make sure that you keep this password safe and remember it as we will use nagiosadmin user to login to the nagios web console.

anupam@ubuntu:/tmp/nagios-4.2.1$ sudo htpasswd -c /usr/local/nagios/etc/htpasswd.users nagiosadmin

• Enable the nagios service and add it to start at the next boot. Also restart the apache2 service to reflect the configuration changes done earlier.

anupam@ubuntu:/tmp/nagios-4.2.1$ sudo systemctl restart apache2.service

anupam@ubuntu:/tmp/nagios-4.2.1$ sudo systemctl enable nagios

anupam@ubuntu:/tmp/nagios-4.2.1$ sudo systemctl start nagios.service

• Check the service status to make sure that they are up and running:

anupam@ubuntu:/tmp/nagios-4.2.1$ systemctl status apache2

anupam@ubuntu:/tmp/nagios-4.2.1$ systemctl status nagios

• You can access the Nagios web interface by opening your browser and then pointing to the URL http://localhost/nagios. It will prompt you to enter the username and password that we had created earlier.

In the above screenshot, you are seeing errors because we have not installed the nagios plugins and so the check scripts are not present yet.

Step 2: Install the Nagios Plugins Package on Ubuntu 16.04.01

The official Nagios plugins package contains over 50 plugins that provide basic monitoring for hosts, devices, services, protocols and applications.

• Download the official nagios-plugins package from nagios-plugins.org and extract it:

anupam@ubuntu:/tmp$ wget https://nagios-plugins.org/download/nagios-plugins-2.1.2.tar.gz

anupam@ubuntu:/tmp$ tar -zxvf nagios-plugins-2.1.2.tar.gz

anupam@ubuntu:/tmp$ cd nagios-plugins-2.1.2/

• Before you start compiling and installing the nagios-plugins, you need to know that some of these nagios-plugins require additional pre-requisites installed on your system before they can be used.  Plugins that are dependent on pre-requisites that are missing are usually not compiled. For more details about the pre-requisites required for each plugin in the nagios-plugins package, please read the /tmp/nagios-plugins-2.1.2/REQUIREMENTS file.

Here we are going to install the following pre-requisites:

• SNMP tools and utilities
• SNMP Agent
• Perl Net::SNMP module
• MySQL Client development libraries
• OpenSSL development libraries

# Install SNMP Tools and Utilities

anupam@ubuntu:/tmp$ sudo apt-get install snmp libsnmp-perl

# Install Perl Net::SNMP module

anupam@ubuntu:/tmp$ sudo apt-get install libnet-snmp-perl

# Install SNMP Daemon

anupam@ubuntu:/tmp$ sudo apt-get install snmpd libperl-dev

# Install MySQL client development libraries

anupam@ubuntu:/tmp/nagios-plugins-2.1.2$ sudo apt-get install libmysqlclient-dev libmysqlclient20 mysql-common

# Install OpenSSL development libraries

anupam@ubuntu:/tmp/nagios-plugins-2.1.2$ sudo apt-get install libssl-dev libssl-doc

• Compile and install the nagios-plugins package:

anupam@ubuntu:/tmp/nagios-plugins-2.1.2$ ./configure --with-nagios-user=nagios --with-nagios-group=nagcmd

anupam@ubuntu:/tmp/nagios-plugins-2.1.2$ make

anupam@ubuntu:/tmp/nagios-plugins-2.1.2$ sudo make install

• After installing the nagios-plugins package, you can see in the Nagios web interface that the errors that were present earlier because of unavailability of check scripts have gone away:

Step 3: Install Pre-Requisites for Dell OpenManage Plug-In for Nagios-Core

Prior to installing Dell OpenManage Plug-in for Nagios-Core and Nagios XI on a management node, there are certain prerequisites or dependencies that must be installed on the management node. However, we have already installed most of the prerequisites in previous steps. Following is the list of pre-requisites and their criticality (mandatory or optional) for Dell OM Plug-In:

• Perl Net-IP Module [mandatory]: It should already be installed on your management node as part of Ubuntu 16.04.01 LTS
• Perl Net-SNMP Module [mandatory]: We already installed it as a pre-requisite for nagios-plugin package installation in above steps
• Perl Socket6 Module [optional]: It should already be installed on our management node as part of Ubuntu 16.04.01 LTS
• Perl bindings for Open-WSMAN (WS-Management) [mandatory]
• Perl SNMPTT (SNMP Trap Translator) Module [optional]
• Dell RACADM (Remote Access Controller Admin) [optional]

Installing Perl Bindings for OpenWSMAN

On Ubuntu 16.04.01 LTS, Perl bindings for OpenWSMAN are not available as a .deb package from official and OpenSUSE repositories. So, we will install Perl bindings by compiling Openwsman from source and then installing it. Please note that the below steps will install openwsman server, client and all bindings except Ruby on your management node.

• Before you build and install Openwsman from source, following prerequisites must be installed on your management node (please ignore the following steps if they are already installed):

# Install autoconf (Automatic configure script builder) and associated dependencies

[anupam@ubuntu]:~$ sudo apt-get install autoconf automake autotools-dev libsigsegv2 m4

# Install Cmake and associated dependencies

[anupam@ubuntu]:~$ sudo apt-get install cmake cmake-data libjsoncpp1

# Install Default JDK and associated dependencies

[anupam@ubuntu]:~$ sudo apt-get install ca-certificates-java default-jdk default-jdk-headless default-jre default-jre-headless fonts-dejavu-extra java-common libbonobo2-0 libbonobo2-common libgif7 libgnome-2-0 libgnome2-common libgnomevfs2-0 libgnomevfs2-common liborbit-2-0 openjdk-8-jdk openjdk-8-jdk-headless openjdk-8-jre openjdk-8-jre-headless

# Install PAM (pluggable authentication module) development module

[anupam@ubuntu]:~$ sudo apt-get install libpam0g-dev

# Install Curl OpenSSL Development Libraries

[anupam@ubuntu]:~$ sudo apt-get install libcurl4-openssl-dev

# Install development files for the GNOME XML Libraries

[anupam@ubuntu]:~$ sudo apt-get install icu-devtools libicu-dev libxml2-dev

# Install SWIG (Simplified Wrapper & Interface Generator) for wrapping C/C++ functions for use with a script generator

[anupam@ubuntu]:~$ sudo apt-get install swig3.0

# Install sblim-sfcc (Small Footprint CIM Client) libraries

[anupam@ubuntu]:~$ sudo apt-get install libcimcclient0 libcimcclient0-dev

# Install python development libraries

[anupam@ubuntu]:~$ sudo apt-get install libpython-dev

• Download the latest committed release openwsman-2.6.3.tar.gz source tar ball from the github url and extract it:

[anupam@ubuntu]:~$ cd /tmp

[anupam@ubuntu]:/tmp$ wget https://github.com/Openwsman/openwsman/archive/v2.6.3.tar.gz -O /tmp/openwsman-2.6.3.tar.gz

[anupam@ubuntu]:/tmp$ tar –zxvf openwsman-2.6.3.tar.gz

• Let’s disable the Ruby bindings so that you don’t run into Ruby installations errors. In order to do so, please navigate to openwsman-2.6.3 directory and edit the top-level CMakeLists.txt file and set the BUILD_RUBY option to NO.

[anupam@ubuntu]:/tmp$ cd openwsman-2.6.3

[anupam@ubuntu]:/tmp/openwsman-2.6.3$ perl –p –i –e "s/(\\$\{CURL_LIBRARIES\})/\1 ssl crypto/g" src/lib/CMakeLists.txt

[anupam@ubuntu]:/tmp/openwsman-2.6.3$ vi CMakeLists.txt

Find and edit the BUILD_RUBY target option to NO:

OPTION( BUILD_RUBY “Build Ruby Bindings” YES)

                           To

OPTION( BUILD_RUBY “Build Ruby Bindings” NO)

• Run the following commands to build and install openwsman and its associated perl bindings:

[anupam@ubuntu]:/tmp/openwsman-2.6.3$ mkdir build && cd build

[anupam@ubuntu]:/tmp/openwsman-2.6.3/build$ cmake .. -DLIB=/lib/x86_64-linux-gnu -DCMAKE_LIBRARY_ARCHITECTURE=x86_64-linux-gnu -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=TRUE

[anupam@ubuntu]:/tmp/openwsman-2.6.3/build$ make

[anupam@ubuntu]:/tmp/openwsman-2.6.3/build$ sudo make install

[anupam@ubuntu]:/tmp/openwsman-2.6.3/build$ openwsmand --version

openwsman 2.6

Installing and Configure SNMPTT (SNMP Trap Translator)

On Ubuntu 16.04.01 LTS, SNMPTT package can be installed from the Ubuntu universe repository. We need to install snmptrapd to receive and log the SNMP trap messages before we install snmptt.

• Install snmptrapd from the universe repository:

[anupam@ubuntu]:~$ sudo apt-get install snmptrapd

• Install snmptt and associated dependencies from the Ubuntu universe repository:

[anupam@ubuntu]:~$ sudo apt-get install snmptt libconfig-inifiles-perl

• Edit the /etc/snmp/snmptt.ini file to configure snmptt to run as a daemon rather than in standalone mode. Let us also enable the DNS resolution and enhanced logging options.

[anupam@ubuntu]:~$ sudo vi /etc/snmp/snmptt.ini

# snmptt.ini

[General]

dns_enable = 1

net_snmp_perl_enable = 1

translate_log_trap_oid = 1

[Logging]

stdout_enable = 1

log_enable = 1

log_file = /var/log/snmptt/snmptt.log

log_system_enable = 1

log_system_file = /var/log/snmptt/snmpttsystem.log

unknown_trap_log_enable = 1

unknown_trap_log_file = /var/log/snmptt/snmpttunknown.log

[Debugging]

DEBUGGING = 1

DEBUGGING_FILE = /var/log/snmptt.debug

DEBUGGING_FILE_HANDLER = /var/log/snmptt/snmptthandler.debug

• Save the file and restart the snmptt service:

[anupam@ubuntu]:~$ sudo systemctl restart snmptt.service

[anupam@ubuntu]:~$ systemctl status snmptt.service

● snmptt.service - LSB: SNMP Trap Translator

   Loaded: loaded (/etc/init.d/snmptt; bad; vendor preset: enabled)

   Active: active (running) since Fri 2016-10-14 04:41:57 PDT; 11s ago

     Docs: man:systemd-sysv-generator(8)

  Process: 26472 ExecStop=/etc/init.d/snmptt stop (code=exited, status=0/SUCCESS

  Process: 26483 ExecStart=/etc/init.d/snmptt start (code=exited, status=0/SUCCE

   CGroup: /system.slice/snmptt.service

           ├─26494 /usr/bin/perl /usr/sbin/snmptt --daemon

           └─26495 /usr/bin/perl /usr/sbin/snmptt --daemon

Oct 14 04:41:56 ubuntu systemd[1]: Starting LSB: SNMP Trap Translator...

Oct 14 04:41:56 ubuntu snmptt[26483]: Redundant argument in sprintf at /usr/lib/x86_64-linux-gnu/perl/5.22/Sys/Syslog.pm line 423.

Oct 14 04:41:56 ubuntu snmptt-sys[26492]: SNMPTT v1.4 started

Oct 14 04:41:57 ubuntu snmptt[26483]: Redundant argument in sprintf at /usr/lib/x86_64-linux-gnu/perl/5.22/Sys/Syslog.pm line 423.

Oct 14 04:41:57 ubuntu snmptt-sys[26492]: Loading /etc/snmp/snmptt.conf

Oct 14 04:41:57 ubuntu snmptt[26483]: Redundant argument in sprintf at /usr/lib/x86_64-linux-gnu/perl/5.22/Sys/Syslog.pm line 423.

Oct 14 04:41:57 ubuntu snmptt-sys[26492]: Finished loading 64 lines from /etc/snmp/snmptt.conf

Oct 14 04:41:57 ubuntu snmptt[26483]: PID file: /var/run/snmptt.pid

Oct 14 04:41:57 ubuntu snmptt-sys[26495]: Changing to UID: snmptt (122)

Oct 14 04:41:57 ubuntu systemd[1]: Started LSB: SNMP Trap Translator.

Install Perl Socket6 Module

• On Ubuntu 16.04.01 LTS, libsocket6-perl package is installed by default. If it is not installed on the management node, then you can install it from the main repository:

 [anupam@ubuntu]:~$ sudo apt-get install libsocket6-perl

Install Dell RACADM (Remote Access Controller Admin)

RACADM is an optional prerequisite for the OpenManage plug-in and is required for monitoring component attribute information of Dell Chassis (M1000e, VRTX, FX2/FX2s) such as fan speed (RPM), amperage (A), voltage (V), power of PSUs and health of I/O modules. RACADM is packaged as part of the OpenManage Server Administrator (OMSA) package and can be installed from the Dell Linux repository.

NOTE: At the time of writing this manual, we only have the OpenManage packages available for Ubuntu 14.04 LTS (Trusty Tahr) release.

Please follow the below steps to install RACADM on your management node running Nagios:

• Create the file '/etc/apt/sources.list.d/linux.dell.com.sources.list'.

[anupam@ubuntu]:~$ sudo touch /etc/apt/sources.list.d/linux.dell.com.sources.list

• Now, we will add the Dell OpenManage Ubuntu repository (http://linux.dell.com/repo/community/ubuntu/) to the software sources. Cut and paste the command below (if typing by hand, note carefully the spacing).

[anupam@ubuntu]:~$ sudo echo 'deb http://linux.dell.com/repo/community/ubuntu trusty openmanage' | sudo tee -a /etc/apt/sources.list.d/linux.dell.com.sources.list

• If you would like to restrict your system to a specific OpenManage release, such as the 8.3 release, you can specify it like this:

[anupam@ubuntu]:~$ sudo echo 'deb http://linux.dell.com/repo/community/ubuntu trusty openmanage/830' | sudo tee -a /etc/apt/sources.list.d/linux.dell.com.sources.list

• To verify OMSA packages, add the repository key to apt.

[anupam@ubuntu]:~$ sudo gpg --keyserver pool.sks-keyservers.net --recv-key 1285491434D8786F

[anupam@ubuntu]:~$ gpg -a --export 1285491434D8786F | sudo apt-key add -

• If you are behind a firewall that only allows outbound traffic over port 80, you may need to use this instead. In the first line below, you possibly need to add "--keyserver-options http-proxy=http://<user>:<password>@<proxy>:<port>".

[anupam@ubuntu]:~$ sudo gpg --keyserver hkp://pool.sks-keyservers.net:80 --recv-key 1285491434D8786F

[anupam@ubuntu]:~$ gpg -a --export 1285491434D8786F | sudo apt-key add -

• Make apt aware of the new software repository by issuing the following command:

[anupam@ubuntu]:~$ sudo apt-get update

• Install the following packages to get RACADM installed:

[anupam@ubuntu]:$ sudo apt-get install argtable2 libopenipmi0 libsmbios2v5 openipmi python-libsmbios smbios-utils srvadmin-deng srvadmin-hapi srvadmin-idracadm7 srvadmin-idracadm8 srvadmin-omilcore

Step 4: Install Dell OpenManage Plug-In for Nagios-Core

• Download the latest Dell OpenManage Plug-in Version 2.0 for Nagios Core installer from the Dell support website at support.dell.com or from Nagios exchange at exchange.nagios.org .The installer is packaged as a .tar.gz file named “Dell_OpenManage_Plugin_Nagios_Core_41Y2V_RHEL6_2.0_A00.tar.gz”.
• Navigate to the location where you have downloaded the tar.gz file and run the following command to extract its contents:

[anupam@ubuntu]:/tmp$ tar -zxvf Dell_OpenManage_Plugin_v2.0_Nagios_Core_A00.tar.gz

• Verify that the following folder and files are extracted:

[anupam@ubuntu]:/tmp$ ls -lrt

total 936

drwxr-xr-x 8 anupam anupam   4096 Oct 14  2015 Dell_OpenManage_Plugin

-rw-r--r-- 1 anupam anupam  62759 Oct 14  2015 license_en.txt

-rw-r--r-- 1 anupam anupam  12849 Oct 14  2015 Dell_OM_Plugin_2_0_For_NagiosCore_ReadMe.txt

-rw-r--r-- 1 anupam anupam 234152 Oct 14  2015 Dell_OM_Plugin_2_0_For_NagiosCore_IG.pdf

• Navigate to the Dell_OpenManage_Plugin/Install folder, and then run the install.sh script with the root privileges to install the Dell OM Plug-In:

[anupam@ubuntu]:/tmp/Dell_OpenManage_Plugin/Install$ sudo bash install.sh

Dell OpenManage Plug-in v2.0 for Nagios Core requires Nagios Core v3.5.0 or later.

Press 'Y' to continue if Nagios Core version is 3.5.0 or later.

Press any other key to exit installation (default: 'Y'): 

Provide the installed location of Nagios Core (Press ENTER to continue with the default location: '/usr/local/nagios'):

     Using the default Nagios Core installed location: /usr/local/nagios

     Nagios Core installed location verified: /usr/local/nagios

Checking prerequisites...

     Perl Module Net-IP is installed.

     Perl Module Net-SNMP is installed.

     Perl Module OpenWSMAN is installed.

     Perl Module Socket6 is installed.

     SNMPTT is installed.

     RACADM is not installed or not resolvable. Few chassis specific attributes will not be available.

     Press 'Y' to continue.

     Press any other key to exit installation (default: 'Y'): 

     JAVA is installed.

Read the Dell End User License Agreement (EULA) license file (license_en.txt) packaged with this product before proceeding with the installation.

Press 'Y' to accept the license.

Press any other key to exit installation (default: 'Y'): 

Installing "dell" Plug-in specific folders and files...

Enabling HTML tags...

The attribute "escape_html_tags" in file "cgi.cfg" is set to 1. Set it to 0 for better readability in Nagios Core console (recommended).

Press 'Y' if you would like to set it to '0' (default: 'N'): Y

Updating nagios.cfg...

     The following entry is added for configuring Dell OpenManage Plug-in config directory:

     --------------------------------------------------

     cfg_dir=/usr/local/nagios/dell/config

     --------------------------------------------------

Provide the file path where snmptt.ini is installed (Press ENTER to continue with the default file path: '/etc/snmp/snmptt.ini'):

     Provided file path /etc/snmp/snmptt.ini is valid.

Updating snmptt.ini...

     The following entry is added for supporting Dell device traps:

     ---------------------------------------------------------------------

/usr/local/nagios/dell/config/templates/Dell_Agent_free_Server_Traps.conf

/usr/local/nagios/dell/config/templates/Dell_Chassis_Traps.conf

/usr/local/nagios/dell/config/templates/Dell_Compellent_Traps.conf

/usr/local/nagios/dell/config/templates/Dell_EqualLogic_Traps.conf

/usr/local/nagios/dell/config/templates/Dell_PowerVaultMD_Traps.conf

     ---------------------------------------------------------------------

Provide the file path where JAVA is installed (Press ENTER to continue with the default file path: '/usr/bin/java'):

     Provided file path /usr/bin/java is valid.

Updating dellconfig.cfg...

SUCCESS: Dell OpenManage Plug-in version 2.0 is installed successfully.

For the Dell OpenManage Plug-in changes to take effect, verify the Nagios and SNMPTT configuration entries as per product guidelines and then restart the Nagios and SNMPTT services.

• To verify that the Nagios Core configuration entry is valid, run the following command:

[anupam@ubuntu]:~/tmp/Dell_OpenManage_Plugin/Install$ sudo /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

Nagios Core 4.2.1

Copyright (c) 2009-present Nagios Core Development Team and Community Contributors

Copyright (c) 1999-2009 Ethan Galstad

Last Modified: 09-06-2016

License: GPL

Website: https://www.nagios.org

Reading configuration data...

   Read main config file okay...

Warning: failure_prediction_enabled is obsoleted and no longer has any effect in service type objects (config file '/usr/local/nagios/dell/config/templates/dell_templates.cfg', starting at line 88)

   Read object config files okay...

Running pre-flight check on configuration data...

Checking objects...

     Checked 8 services.

     Checked 1 hosts.

     Checked 4 host groups.

     Checked 0 service groups.

     Checked 2 contacts.

     Checked 2 contact groups.

     Checked 34 commands.

     Checked 7 time periods.

     Checked 0 host escalations.

     Checked 0 service escalations.

Checking for circular paths...

     Checked 1 hosts

     Checked 0 service dependencies

     Checked 0 host dependencies

     Checked 7 timeperiods

Checking global event handlers...

Checking obsessive compulsive processor commands...

Checking misc settings...

Total Warnings: 0

Total Errors:   0

Things look okay - No serious problems were detected during the pre-flight check

• Restart the Nagios Core services:

[anupam@ubuntu]:~$ sudo systemctl restart nagios.service

• If you have installed SNMPTT, then restart the SNMPTT services:

[anupam@ubuntu]:~$ sudo systemctl restart snmptt.service

• Now, let’s try to discover a Dell iDRAC using the /usr/local/nagios/dell/scripts/dell_device_discovery.pl script to make sure that everything is working as expected.

NOTE: The default permissions on the /usr/local/nagios/dell directory and file structure is 750, so that means that either you need to run the Dell OM perl scripts as nagios user or you can use sudo.

anupam@ubuntu:~$ sudo /usr/local/nagios/dell/scripts/dell_device_discovery.pl -H 100.100.240.173 -P 2 -f

[sudo] password for anupam:

Starting Dell device discovery...

The following services are configured for the Dell device(s) to be discovered, as applicable.

Dell Chassis Information

Dell Chassis Overall Health Status

Dell Chassis Traps

Dell Server Information

Dell Server Overall Health Status

Dell Server Traps

Dell Storage Compellent Controller Information

Dell Storage Compellent Controller Overall Health Status

Dell Storage Compellent Controller Traps

Dell Storage Compellent Information

Dell Storage Compellent Management Traps

Dell Storage Compellent Overall Health Status

Dell Storage EqualLogic Group Information

Dell Storage EqualLogic Member Information

Dell Storage EqualLogic Member Overall Health Status

Dell Storage EqualLogic Member Traps

Dell Storage PowerVault MD Information

Dell Storage PowerVault MD Overall Health Status

Dell Storage PowerVault MD Traps

     Press Y and then press Enter to continue.

     Press any other key and then press Enter or press Enter to exit.

Y

Dell device discovery is in progress...

Total number of Dell device(s) attempted               :1

Total number of Dell device(s) unreachable             :0

Total number of Dell device(s) with error response     :0

Total number of Dell device(s) with no response        :0

Total number of Dell device(s) already discovered      :1

Total number of Dell Agent-free Server(s) discovered   :1

Total number of Dell Chassis discovered                :0

Total number of Dell Storage Arrays discovered         :0

Total number of Dell device(s) discovered successfully :1

Dell device discovery completed.

Please verify the Nagios configuration and restart the Nagios service.

• Restart the nagios core service:

anupam@ubuntu:~$ sudo systemctl restart nagios.service

• You can now login to the Nagios web interface and verify that the Dell iDRAC host has been discovered and the services for this host have been configured and scheduled for monitoring:

Dell OpenManage Plug-in for Nagios Core provides a proactive approach to data center management that delivers features for monitoring 12th and later generations of Dell PowerEdge servers through an agent-free method using integrated Dell Remote Access Controller (iDRAC) with Lifecycle Controller technology, Dell chassis and Dell storage devices in the Nagios Core console. With this plug-in, customers have comprehensive hardware-level visibility of Dell PowerEdge servers, Dell chassis, and Dell storage including overall and component-level health monitoring for quicker fault detection and resolution.

Dell OpenManage Plug-in for Nagios Core Version 2.0 features

• Discover and monitor following Dell devices:
  
  • Dell PowerEdge 12th and later generation of servers
    
  • Dell PowerEdge M1000e, Dell PowerEdge VRTX, and Dell PowerEdge FX2/FX2s chassis
  • Dell EqualLogic PS-Series Storage Arrays
  • Dell Compellent Storage Arrays
  • Dell PowerVault MD 34/38 Series Storage Arrays

• Provide basic system information including component-level details the following Dell devices:
  
  • Dell PowerEdge 12th and later generation of servers
    
  • Dell PowerEdge M1000e, Dell PowerEdge VRTX, and Dell PowerEdge FX2/FX2s chassis
  • Dell EqualLogic PS-Series Storage Arrays
  • Dell Compellent Storage Arrays
  • Dell PowerVault MD 34/38 Storage Arrays

• Monitor health of the following components of the supported Dell devices:
  
  • Power Supply, Fan, I/O, Slot, and KVM of the supported Dell chassis
  • Enclosure, Controller, Physical Disk, and Virtual Disk of Dell PowerEdge VRTX Chassis
    
  • PCIe of Dell PowerEdge VRTX and PowerEdge FX2/FX2s chassi
  • Member Physical Disk, Storage Pool, and Group Volume of Dell EqualLogic PS-Series Storage Arrays
  • Physical Disk and Volume of Dell Compellent Storage Arrays

• Provide warranty information of the supported Dell devices

• Monitor SNMP alerts from all the supported Dell devices
  
  
• View alert Knowledge Base (KB) information of the following Dell devices corresponding to a SNMP alert for faster troubleshooting:
  • 12th and later generations of Dell PowerEdge servers
  • Dell PowerEdge M1000e, Dell PowerEdge VRTX, and Dell PowerEdge FX2/FX2s chassis
  • Dell EqualLogic PS-Series Storage Arrays

• Launch the following web consoles from Nagios Core to perform further troubleshooting, configuration, or management activities:
  • Dell iDRAC web console
  • Dell Chassis Management Controller (CMC) Console
  • Dell EqualLogic Group Manager Console
  • Dell Compellent Storage Manager Console

Business benefits

• Protect existing investment in Nagios Core product to easily integrate and monitor Dell servers, chassis and storages within customer’s infrastructure

• Improve operational efficiency and flexibility in managing large heterogeneous data center environment

• Increase productivity by reducing time to maintain, monitor and troubleshoot any issue in server infrastructure

• Make informed and rapid decisions impacting the availability of data center resources

Dell OpenManage Plug-in version 2.0 for Nagios Core is available as a software download offered at no charge.

Download 

• Dell OpenManage Plug-in for Nagios Core

Documentation

Learn

• Installalation of Dell OpenManage Plug-In for Nagios Core on Ubuntu OS (NEW)
• Using Dell OpenManage Plug-in for Nagios Core on CentOS and Ubuntu OS
• SNMP Parameters Configuration script for Dell iDRACs in a large customer environment using RACADM

Whitepapers

• Agent-free Monitoring of Dell PowerEdge 12G Servers in Nagios Core and Nagios XI Whitepaper (BETA release on Nagios Exchange)

Videos

• Overview of Dell OpenManage Plug-in v2.0 for Nagios Core(Please visit the site to view this video)

• Upgrading to Dell OpenManage Plug-in version 2.0 for Nagios Core (Please visit the site to view this video)

• Overview of Dell OpenManage Plug-in v1.0 for Nagios Core
  (Please visit the site to view this video)

• Installation of Dell OpenManage Plug-in for Nagios Core
  (Please visit the site to view this video)

• Integrating SNMP traps in Dell OpenManage Plug-in for Nagios Core
  (Please visit the site to view this video)
  

• Uninstallation of Dell OpenManage Plug-in for Nagios Core
  (Please visit the site to view this video)