1.Install 

1.Q: Can I upgrade my OME 1.0 Open Evaluation installation to the new OME 1.0.1 version?
A: Yes.  When OME 1.0.1 ships, you will be able to easily install it over your 1.0 Open Evaluation instance.

2.Q: I cannot install OpenManage Essentials using a remote SQL Database Named instance?
A: SQL Server with named instances requires ‘SQL Server Browser’ service to be running to connect remotely.

3.Q: Will OpenManage Essentials support SQL Server ‘evaluation’ edition?
A: No, SQL Server ‘evaluation’ edition is not supported because this is a prerelease version.

4.Q:  What if I see this error when I launch the console – “HTTP Error 500.19 - Internal Server Error the requested page cannot be accessed because the related configuration data for the page is invalid.”
A:  Remove/Disable the XPress compression scheme from the configuration using the command below:

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

OR

Add an attribute of "precondition= "64bitness" for this module entry so that it loads only in 64bit application pools.

5.Q: What if IPMI is disabled after installing BMC Utility?
A: Try restarting DSM Essentials Network Monitor Service, DSM Essentials Task Manager service and restart IIS.

6. Q: How do I change OME web service/console port after OME installation?
A: After OME installation, follow these steps:

- From Start->Run, type "regedit" and hit "Enter" to open Windows      registry.

- Navigate to HKEY_LOCAL_MACHINE->SOFTWARE->Wow6432Node->Dell Computer  Corporation->Dell OpenManage Essentials->Connection Service

- Update "ConsolePort" on the right hand side.

- Launch Start->Administrative Tools->Internet Information Services  (IIS) Manager

- Navigate to <SystemName>->Sites->OpenManage Essentials

- Right click on "OpenManage Essentials" and click "Edit Bindings".

- Edit https port number "2607".

- Restart OME Netmon, Task manager and IIS services

Note: Please do not modify http port number either in registry or IIS.

7. Q: Installation of OME takes longer on Windows 2008 SP2 X64bit. Why?
A: Installation of IIS roles services takes longer to install on Windows 2008 SP2 X64bit which causes OME installation time to increase.

2.Tasks

1.Q: What troubleshooting can I do if a software update task or remote task fails to be created or executed?
A: Make sure DSM Essentials Task Manager service is running in Windows services.

2.Q: Why am I not receiving emails after setting up email alert action?
A:  If you have an Antivirus Client installed on your system, you will need to configure it to allow emails.

3.Q: Does OME support Power control options for 8G servers?
A: Yes, Power ON (option available in Server Power Options Task), and Power OFF (option available when used in IPMI command line task, in Arguments field use: chassis power off) works on 8G servers with BMC. 

Note: If the 8G server has a DRAC4 over BMC, make sure the DRAC4 IP is pingable in Troubleshoot tool using IPMI protocol. If the RMCP ping fails, the power tasks will likely be failing. This simple check will also help to know if the connection to the RAC devices for any generation server is passed. 

4.Q: Why does the update using iDRAC taking a long time?
A:  Check your credentials. Wrong credentials may cause OME to wait for communication timeout which will result in failed task after the timeout period. If you are updating 10+ devices with wrong credentials it may take up to 2-3 hours before reporting failure.

5.Q: How can I stop command Line task with single target? 
A: A task with only one device cannot be stopped once the execution has started.

6. Q: Why does the OME Task Manager crash when the username used has a \p in remote tasks. For example: veggie\pizza.
A: This is a limitation in OME parsing logic. The workaround is to create and use a username that does not have a \p in it.

3.Discovery

1.Q: What troubleshooting can I do if a discovery task fails to be created or executed?
A: Make sure DSM Essentials Task Manager service is running in Windows services

2.Q: Why are devices discovered with WMI getting classified as Unknown?
A: WMI discovery will classify a device as unknown when the credentials for a user account in the Administrators group (not Administrator) are supplied for the discovery range in some cases.If you are seeing this issue, read the following KB article and apply the registry work around described therein.

So far, this applies to managed nodes with Windows Server 2008 R2.http://support.microsoft.com/?scid=kb;en-us;951016

3.Q. My ESXi servers are getting classified as unknowns.
A: If you are using ESXi 5.0 update 1, please install OM 7.0 VIB available at 

http://www.dell.com/support/drivers/us/en/555/DriverDetails/DriverFileFormats?DriverId=VPTVV.

You can also try increasing the timeout (setting to 10) and retry (setting to 4) values in the WS-MAN page for discovery wizard.

4.Q. My ESXi servers after few days of monitoring, becomes unknown
A:  VMware has identified an issue affecting VMware ESXi 5.0x and 5.1x where CIM monitoring applications fail to authenticate with “No space left on device” error in /var/log/syslog.log:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2043464.

This issue can cause previously discovered systems to move to an unknown status, fail to discover, or not show in both OpenManage Essentials (OME) and Dell Management Plugin for VMware vCenter (DMPVV).

The current workaround is to issue “/etc/init.d/wsman restart” on the ESXi host shell.While a permanent solution to this issue has not been identified by VMware as of 13 March 2013, the following steps can be followed to create a persistent cron job to restart the wsman service once a day.

Add the following to /etc/rc.local (for ESXi 5.1 systems edit: /etc/rc.local.d/local.sh):

# Added by Dell to add cronjob for restarting wsman 12:15 AM/PM

/bin/kill $(cat /var/run/crond.pid)

/bin/echo '15   0,12 *   *   *   /etc/init.d/wsman restart' >> /var/spool/cron/crontabs/root

/bin/busybox crond

Execute auto-backup.sh (sh /sbin/auto-backup.sh) after making edits.

Reboot the system.

On reboot “cat /var/spool/cron/crontabs/root” should show:

#min hour day mon dow command

1    1    *   *   *   /sbin/tmpwatch.py

1    *    *   *   *   /sbin/auto-backup.sh

0    *    *   *   *   /usr/lib/vmware/vmksummary/log-heartbeat.py

*/5  *    *   *   *   /sbin/hostd-probe

15   0,12 *   *   *   /etc/init.d/wsman restart

NOTE: In previous releases of ESXi, you could add custom commands in /etc/rc.local which would automatically execute after all startup scripts have finished. With the latest release of ESXi 5.1, this functionality has been moved to /etc/rc.local.d/local.sh.

5.Q: What is the most important thing to know about Discovery?
A: You must install Dell OpenManage Server Administrator (aka OMSA) on all of the PowerEdge Servers that you want to discover and manage using SNMP protocol.  OMSA can be installed from the OME console.

You can also discover PowerEdge Servers using WMI without OMSA installed. Your servers will not be classified as a "Dell Computer", but rather, "Unknown" or just "Computer".  Management capabilities in OpenManage Essentials are limited if OMSA is not installed.

6.Q: Why do my Servers appear under the "Unknown" node in the device tree?
A: Systems discovered with SNMP only, and without OMSA installed on them, will be classified as "Unknown" and displayed under the "Unknown" device group.  If you have confirmed that OMSA is correctly installed on the managed node, then check the SNMP settings.  

Note: SNMP community strings are *case sensitive*.

Bring up services.msc on the managed node and go to the properties page for "SNMP Service".

On the Security tab, there is a radio button for "Accept SNMP Packets from any host" and "...packets from these hosts". You need to be sure and specify your OME server here, or select the radio button for "any host".  

If you select "any host" consult the Microsoft documentation for any security implications.

For Linux machines, make sure to run '/etc/init.d/dataeng enablesnmp' followed by '/etc/init.d/dataeng restart'

Finally, the Dell Troubleshooting Tool, installed as part of OME, is very useful in helping with Discovery problems.

Run the "Services" test as well from the Troubleshooting tool and see if you are finding the following entry in the test result
dsm_sa_datamgrd
dsm_sa_eventmgr
dsm_sa_snmpd
dsm_om_shrsvcd
dsm_om_connsvcd
These are OMSA services running on the remote box. If these entries are present in the result and if you are allowed to restart these services on that remote production system, Please do. Services can restarted from the service manager (Service names are prefixed with "DSM SA")

7.Q: Are there any considerations when trying to discover servers that have Windows 2008 as the operating system?
A: When using SNMP, in order to discover a system that is running Windows Server 2008, the "Network discovery" feature must be enabled.

Perform the following steps to enable "Network discovery" on the target Server:

-Navigate to the target system's Control Panel

-Select "Network and Sharing Center"

-In the "Sharing and Discovery" section, set "Network discovery" to "On"

8.Q: Looking at my systems, I see "System Is Down" for a server - can you tell me how this is determined? And also, how often is it re-checked?
A: The connection state shows 'ON or 'OFF' under device summary table in the LHS. When the system /device is removed from the network either power off or NIC cable removed then the state for the system is shown as 'system is down'. Basically when the server is not pingable we see server as down. By default polling for connection state is 1 hour. User has option to configure the frequency of polling.

9.Q: What troubleshooting can I do if a server is showing up as unknown or not returning inventory data even after SNMP is enabled and OMSA is installed on the target server?
A: Make sure DSM SA Data Manager Service is running in Windows services on the target server.  If it is stopped, restart the service and re-run the inventory task. 

10.Q: How should I discover my EqualLogic storage array?
A: EqualLogic arrays are discovered with the SNMP v2 protocol.  So in your OME discovery wizard, choose SNMP along with the appropriate ‘read’ community string.  Also, you should include the IP address of the EqualLogic Group and IP addresses for all the members in the discovery range.

11.Q: Why is the iDRAC 6 IP address shown as 0.0.0.0 in OME?
A: If the iDRAC firmware version on the Rack/Tower servers is <= 1.70 and on Modular servers is <= 3.30, the IP address is returned as 0.0.0.0.

Please update the iDRAC firmware on Rack/Tower servers to 1.80 and on modular servers to 3.30, to resolve this issue.

12.Q: I have VRTX devices discovered in OME versions prior to 1.2, but when upgrading to version 1.2 they do not show up under VRTX group in the device tree. How can I fix this?
A: Delete the devices from the device tree and then re-run discovery/inventory on the proper ranges to appropriately classify the VRTX devices in the VRTX device group.

13.Q: Why is my EqualLogic blade device not classified under the Modular group?
A: Make sure the chassis service tag in EqualLogic is populated for that to be classified under Modular group.

14.Q: Why does the discovery of PC 8132 with FW version: 5.0.0.4 take more than 2 minutes?
A: This is a known issue with this firmware.  Please update to the latest firmware if available.

15. Q: Why is KVM 4332DS not getting classified under KVM?
A: Update the KVM to the latest firmware (version 1.16 or later ) to classify it correctly.

16. Q: Why are my iDRACs are being deleted and re-added during a long discovery and inventory?
A: To enable the DNS iDRAC<>Server name correlation, the discovery name resolution was changed from DNS to NetBIOS. As a result servers and iDRACs that are initially discovered correctly, upon subsequent inventory and discovery, are removed and re-added to the GUI. There is no other impact to the device list. When discovery completes, all iDRACs are correctly re-added.

17. Q: DSA (LASSO) collection of logs from EqualLogic group upon receiving an event is either not proper, or, is incomplete. Why?
A: Discover EqualLogic storage groups using the Group Management or Storage Group IP address only, and not include any of the member IP addresses in the discovery range configuration.

18. Q: What troubleshooting can I do if tasks such as OMSA deployment, iDRAC Service Module deployment, or system update fail with an "invalid package signature" error?
A: Install the VeriSign Class 3 Public Primary Certification Authority - G5 certificate on the server running OpenManage Essentials.

19 Q: Why does my Dell Server appear in the OEM device group?
A: It is possible that the firmware on your Dell Server is returning an invalid or blank model type when queried. You may need to perform a Lifecycle Controller wipe option, using winrm from a computer on the same network. Below is the command.

Note: The LifeCycle Controller wipe operation is *destructive*. This might wipe out your iDRAC License key so export it first so you can restore it later. Or be prepared to request a new iDRAC License key through your support portal or via phone. If you are uncomfortable with this operation or have any questions please contact Dell Support before proceeding.

winrm i LCWipe http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService?SystemCreationClassName=DCIM_ComputerSystem+CreationClassName=DCIM_LCService+SystemName=DCIM:ComputerSystem+Name=DCIM:LCService -u:[iDRAC_root] -p:[iDRAC_PWD] -r:https://[iDRAC_IP]/wsman -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic

If successful, you will get a ReturnValue of 0. The iDRAC will no longer be accessible for a few minutes. After about 5 minutes you will hear all of the fans spin up to max RPM and stay there for a bit. When they calm down, the iDRAC will be back to a default state with an IP address of 192.168.0.120.

Then reboot your server, so that server inventory (CSIOR) is run on restart. If CSIOR is not enabled, you need to enable it in the LifeCycle Controller options. Then re-run OME discovery in order to re-categorize the server in the device tree.

20. Q: I am unable to discover idrac/chassis/ESXi servers using WSMAN protocol. Why?
A: Check if the devices have valid certificates installed. If the certificate used for WSMAN communication is expired or not yet valid, then OME will not be able to discover the device.

4.Inventory

1.Q: What troubleshooting can I do if an inventory task fails to be created or executed?
A: Make sure DSM Essentials Task Manager service is running in Windows services.

2.Q:  What do I need to do if I do not see any inventory data for a Dell Server running ESXi 5.0?
A: To properly discover, inventory and classify a Dell Server running ESXi 5.0 you must install OpenManage Offline Bundle and VIB 6.5 A02 from support.dell.com which will be available in Q4 2011.

3.Q: How do I update the inconsistent data seen in the device details and Modular Enclosure Information report for a PowerEdge VRTX CMC (chassis management controller), after performing discovery and inventory using WS-Man when all the server slots of the chassis are empty?
A: PowerEdge VRTX only reports data for server slots with a modular server present and does not report any data for empty server slots.

OME does not update the inventory of a device if no changes are seen in the existing data for the device. Since empty server slots in the VRTX chassis are not reported, OME does not see any updated data for the VRTX CMC inventory and thus does not update the device inventory details.

This behavior is not seen if the PowerEdge VRTX chassis has at least one modular server present at the time of inventory.The Modular Enclosure Information report may show a row with empty values for Slot Number, Slot Name columns and "Unknown" value for the Slot Availability column when the PowerEdge VRTX chassis is discovered and inventoried while all the server slots are empty.  

In order to show the most current device inventory details of an empty PowerEdge VRTX chassis, you must remove the instance of the device from the device tree and re-discover and inventory the IP address or hostname of the CMC in question. 

4.Q: Why does the PCIe Information and Virtual Adapter Information table in the PowerEdge VRTX device details page continue to show the server name of a modular server that has been removed from the VRTX chassis, after the CMC has been re-inventoried?
A: The device details of a PowerEdge VRTX modular chassis will not update successfully if the VRTX Chassis Management Controller is re-inventoried when all the chassis server slots are empty.  

This behavior will impact data tables which show association of the modular server slots to the PowerEdge VRTX chassis resources, such as the PCIe Information, Virtual Adapter Information and Virtual Disk Access Policy Information tables.  To update these tables to reflect the correct data, in this scenario, the instance of the VRTX CMC must be removed from the device tree and re-discovered and inventoried.

5. Q: Why is the output power supply shown as 0 watts in the PowerSupply info table for my server with a cabled PSU?
A: For servers with cabled PSU, the output power supply info will be shown as 0 watts. E.g.: T430 server.

5.Health

1.Q: Does OMSA need to be installed on a server to retrieve health status?
A: For servers discovered via WMI where OMSA is not installed and running, health status will only be what the OS provides.  For maximum hardware health status you should install OMSA.

2.Q: Why does OME show power supply health as Normal when the redundant power supply has lost an AC power source?
A: This is the issue with Server Administrator version 6.x. To avoid this issue, please install/upgrade to Server Administrator version 7.0 or higher.

3. Q: Why is Device count and Rollup health showing 0 when REST API command is used for a group marked hidden in the OpenManage Essentials Console?

A: The REST API used to return information about a Device Group ( <base-uri>/DeviceGroups/{deviceGroupId} ) should not be used on device groups that are marked hidden in the OpenManage Essentials console.The information returned using this command is not correct since the data for a hidden device group is inaccessible.

4. Q: Why is my PowerConnect W series switch not showing device health?
A: The health attribute is only available if the PowerConnect W switch is in the master role.

6.System Update

1.Q: I can’t load a Dell catalog for software update or am getting errors when trying to run software update tasks, what might be the problem?
A:  First, try downloading the catalog to the OpenManage Essentials system directly or use an SUU DVD in the local system drive.

-Browse for catalog.xml file on the local system or DVD (not on a file share.  

It is possible to use a file share, but for troubleshooting, do not use file share)

-Load catalog and verify it shows as loaded in OpenManage Essentials. You may also wish to try using the FTP download to get the latest catalog for troubleshooting purposes if you can’t load other catalogs.

-Now create software update tasks.  If tasks fail, more information can be found in the task details.

-Try setting all internet explorer security settings to LOW if tasks will not run when executed.

2.Q: What do I need to do if Linux servers show under 'Non--Inventoried systems' even after I performed inventory on the discovered Linux servers 'N' number of times?

A: For RHEL 5.5, SLES10 and SLES11

1.Mount OMSA6.5 DVD in the Linux server.

2.Install 'srvadmin-cm' rpm.

3.Restart OMSA services.

4.Make sure OMSA inventory collector is working fine(Run ./invcol -outc=/home/inv.xml from /opt/dell/srvadmin/sbin/invcol location).

5.Re-inventory the Linux server in OME.

Now the Linux server will be either listed under 'Compliant systems' or 'Non-Compliant systems'.

3.Q: What order are packages installed on a system?
A: Packages are applied in the following order.-Driver-Firmware-Firmware ES-BIOS-Application

4.Q: What do I need to do when I see this error “Attempted to perform an unauthorized operation.” when performing a catalog import task?
A: The user needs to modify the permissions of the folder on the network share to allow the local user access.  When you are in a workgroup and not on a domain, access to a network share will be restricted so if you need to utilize a network share you will need to make sure OME is running on a machine on a domain.  

The OpenManage Essentials user has to be authenticated on the domain and the network share has to be authenticated on that domain as well.
When using Repository manager as you catalog source make sure that the packages associated with the RM generated catalog are present in the same folder as the catalog.
If the packages are not present in that folder you would see an invalid path result for the packages.

5.Q:  How do I configure Internet Explorer with Enhanced Security Configuration to ensure OpenManage Essentials can utilize all features that use resources from Dell Online?
A: To insure that these features work in the Dell Open Manage Essentials console on an environment with Internet Explorer Enhanced Security Configuration enabled.

The user needs to add *.dell.com to the Trusted sites zone.Import Catalog and System Update require internet access when the user selects Dell Online as the source.

The warranty report also uses Dell Online resources to retrieve information and also will not return data without it.

6.Q: When I try to run system updates in OME I get the following error- “Access to path ‘C:\Program Files (x86)\Dell\SysMgt\Essentials\SystemUpdate is denied”.
A: This is due to Windows 2008 R2 folder restrictions in the program files directory.  

Open folder – C:\Program Files (x86)\Dell\SysMgt\Essentials\In the Essentials folder make a new folder named: SystemUpdate

-Right Click

– SystemUpdate folder

-Select Properties

-Select Security tab

-Click Edit

-Select Users

-Select Full control

-Click OK

-Click OK

Then recreate the update task.

7.Q: Why does System update task show as failed in spite of successfully updating the server?
A: After executing the software update task which requires target server to be restarted, if target server does not come up within 30 minutes the task will show as failed in spite of successfully updating the server.  In that case you will have to run the inventory for the server separately to see the updated version on inventory page and compliance report.

8.Q: Why am I not seeing software inventory for a server or why does the server show up in the non-inventory state even though I executed an inventory task against it?
A: Do the following:Make sure OMSA is installed the server.

Check: C:\Program Files\Dell\SysMgt\oma\log

Delete all of the files except for the cachecfg.txt. Once the files are removed you will need to restart the DSM SA Shared Services within Services.msc. Once the DSM SA Shared Services has successfully restarted it may take up to 90 secs to repopulate the updated inventory files (Note: The new files will consist of the cachecfg.txt, Inventory.xml.1 and InvLog.xml)

9. Q: I have OpenManage Essentials installed and successfully discovered and inventoried my 11G servers. I downloaded the update catalog and have identified some servers that our non-compliant. When I run the update task it goes to 100% complete in less than 2 seconds and no update occurs.....any ideas?
A: Providing full control NTFS permissions to the C:\Program Files (x86)\Dell\SysMgt\Essentials\SystemUpdate folder has corrected the problem. The job runs successfully now.

10.Q: Can you re-run system update tasks on the same target that have not completed?
A: Previously Executed System update tasks can be re-run. It is not recommended to re-run the system update task for the same target while the first one is not complete as it will result in OME resending the same updates again.

11.Q: What do I do if SUU Import Catalog for System Update failed with this error “Exception message: Error: 1205, Procedure: usp_Catalog_Insert, Message: Transaction (Process ID 69) was deadlocked"?
A: Daemon Lite is not supported for mounting the ISO. If you are using Daemon Lite to mount the ISO, use MagicDisk or Virtual Clone Drive.

12.Q: I am unable to push updates to VRTX Chassis, why?
A: The VRTX chassis must be discovered and inventoried using WS-Man protocol for OpenManage Essentials to push updates. OpenManage Essentials does not support the update feature for the VRTX chassis using SNMP discovery and inventory.

13.Q: My compliance report pie chart disappeared or is not showing. How do I make it visible again?
A:  

-Refresh your browser.Or

-Click the ‘Filtered by: All Update Devices’ link next to the ‘System Update’ portal title.

-Check ‘All Update Devices’ in the device selection tree.

-Click ‘Apply’.

Within 30 seconds the pie chart will reappear.Note: If the chart still does not appear, make sure all devices are discovered and inventoried, and verify your catalog.

14. Q: When Plasma HA has 2 PERC controllers with different versions, the one with the lower version is shown in the software inventory information table. Why?
A: OME shows a single PERC because the two PERCs cannot be differentiated in the OME inventory. If the Plasma HA PERC versions are different then the user needs to update the PERC manually from the CMC console.

15. Q: Why does my update sent via iDrac fail even though I have provided the right credentials and there is no connection problem?
A: It is possible that the iDRAC SSL configuration need to be reset to correctly authenticate the connection, in order to successfully update any system components via WSMAN. Execute the below command for every iDRAC that fails updates and then rerun the update task.

racadm sslresetcfg

16. Q: The iDRAC is not able to download the packages and update tasks using WSMAN fail. The IP address of the OME server in the URI is blank.
A: OME uses DNS to create the URI to download the DUPs to iDRAC. Ensure your DNS is configured correctly and hostname resolves to IP Address. Also ensure that the DNS does not accidentally have a loopback address alone.

17. Q: When the server (MN) inventory is within 5mins after the reboot, older version of the firmware is displayed in OME UI.
A: You can manually run the inventory again or wait for the scheduled inventory cycle in OME to see the updated versions in OME.

18. Q: System with iDRAC firmware version 1.30.30 is not showing up as compliant. Why?
A: System iDRAC version 1.30.30 will never show up as complaint because the systemID return by the OME inventory is invalid.
The iDRAC need to be upgraded to version 1.40.40 or above to see valid systemID.

19. Q: I don't see upgrades for 9G and 10G servers when the catalog source is SUU.Why?
A: There are separate catalogs. 9G and 10G server updates are present in one SUU whereas 11G and 12G are present in another SUU.

20. Q: What do I need to do if an out-of-band system update task fails and the task description displays a message stating that "The specified URI is invalid."?
A: To resolve the issue, do one of the following:
     Ensure that the following ports are open on the firewall:
         - Port 442 (for WS-Man)
         - Port 80 (for HTTP)
         - Port 1279 (for task manager)
     Disable the firewall

21 Q: Linux target in-band updates fail to execute. It appears that an in-band update will never be extracted and executed. why?
A: Ensure that tar and gunzip are installed and are in the path. If using "sudo", ensure that the “NOPASSWD:ALL” setting is present for the sudoers group. Then re- attempt.

7.Reports

1.Q:  Why is Virtual Machine Information and Virtual Machine Host Product information Tables missing in ESX Sever Device Details? 
A: The SNMP agent for this system may not be properly configured and is not returning any data for the VMWARE OID.

2.Q: On the Reports page, why does Device name shows as IP Address instead of the actual Device Name?
A: The IP address will be displayed instead of device names only when devices from which the alerts received is not discovered in OME.

3.Q: What do I need to do if the warranty report is not getting populated after running inventory?
A:  This can happen if OME cannot communicate with Dell Warranty websites if you have enhanced security configuration enabled for Internet Explorer. You can add api.dell.com and lt.dell.com websites to the trusted list for warranty report to work. Alternatively you can disable the enhanced security configuration.

4. Q: Why are the reports on home portal missing after upgrade from 1.2 to 1.3?
The custom portal layout saved in the database in OME 1.2 is not compatible with the custom portal layout in OME 1.3.
On upgrade from OME 1.2 to OME 1.3 if a user had a custom portal layout saved, this layout will be discarded and the default portal layout will be presented to the user.

8.Preferences

1.Q: Can I increase the console maximum timeout setting from 6 hours.
A: No, 6 hours is the maximum timeout setting.  The session timeout gives the application the ability to clean up the database.



9.Troubleshooting

1.Q: Where can I find the logs to help troubleshoot install issues? 
A: Check the ‘InstallUtil.log’ file for any install issues. This file is located in your windows temp directory.

2.Q: What do I need to do if I see this message "You do not have permissions to alter these settings.  Please contact your system administrator. "?
A: If you used a domain account to install OpenManage Essentials you will need to add that account to the local administrators group and run iisreset from the command line.

3.Q: When I try to run system updates in OME I get the following error- “Access to path ‘C:\Program Files (x86)\Dell\SysMgt\Essentials\SystemUpdate is denied”?

A: This is due to Windows 2008 R2 folder restrictions in the program files directory.  

-Open folder

– C:\Program Files (x86)\Dell\SysMgt\Essentials\-

In the Essentials folder make a new folder named: SystemUpdate
1.Right Click – SystemUpdate folder

2.Select – Properties

3.Select – Security tab

4.Click – Edit

5.Select – Users

6.Select – Full control

7.Click – OK

8.Click – OK
-Then recreate the update task.

4.Q: What do I do if I can’t find the right click option for OMSA launch although OMSA is installed on the target server?
A: You can delete and rediscover the same device which will show the right click option for launching OMSA.

5.Q: What do I need to do if all SNMP traps from an ESXi 5 host show up in OME as unknown?
A:  You have to change the hardware event source in the SNMP config on the ESXi 5 host from CIM to IPMI.

Run the following commands:

vicfg-snmp.pl --username root --password <yourpassword> --server <yourserver> --hwsrc sensors

The output of the --show command then should be:

Current SNMP agent settings:

Enabled  : 1

UDP port : 161

Communities : public

Notification targets : <myOMEservername>@162/public

Options : EnvEventSource=sensors

6.Q: What do I need to do if the warranty report is not getting populated after running inventory?
A:  This can happen if OME cannot communicate with Dell Warranty websites if you have enhanced security configuration enabled for Internet Explorer.

You can add api.dell.com and lt.dell.com websites to the trusted list for warranty report to work. Alternatively you can disable the enhanced security configuration.

7.Q: Why is OME unable to create a connection to SQL Server?
A: This is only 1 of many possible solutions:

Make sure TCP/IP is enabled using SQL Server Configuration Manager-Start Menu \ All Programs \ Microsoft SQL Server 2008 R2 \ Configuration Tools \ SQL Server Configuration Manager-Under SQL Server Network Configuration select ‘Protocols’ for each instance, Set the TCP/IP to Enabled.

8.Q: What can I do if my health status shows as unknown for my VM ESXi 5.x hosts?
A: For 12G servers, discover the iDRAC7 using WSMAN protocol to retrieve hardware inventory and health status. For older generation of servers, follow these steps:
Run this command from OS command prompt in OME server:

winrm i SendCmd cimv2/DCIM_OEM_DataAccessModule?__cimnamespace=root/dcim/sysman+InstanceID=DCIM_OEM_DataAccessModule1 @{CommandAndArguments="omacmd=getchildlist showbody=true showobjhead=true recurse=true computeobjstatus=true byobjtype=17 poid=2 comp=MainChassis daname=dceda"} -r:https://ESXiIPAddress:443/wsman -u:Username -p:Password -skipCNcheck -skipCAcheck -skipRevocationcheck -a:Basic -encoding:utf-8

Make sure to provide actual values for these three fields in the above syntax:

ESXiIPAddress

Username

Password

The command should return this info:

SendCmd_OUTPUTResultCode = 0ReturnValue = <MainSystemChassis ons="Root/MainSystemChassis" instance="0" creatoralias="dsm_sa_datamgr32" creatordisplay="Systems Management Data Manager"><oid>2</oid><objtype>17</objtype><objstatus>4</objstatus></MainSystemChassis><ObjCount>1</ObjCount><computedobjstatus strval="CRITICAL">4</computedobjstatus><SMStatus s32val="0" strval="SUCCESS">0</SMStatus>

If the command fails or does not return the above data, you may need to troubleshoot further:Reboot the ESXi server host once and run the command again. Make sure OMSA VIB is installed on the ESXi host.

9.Q: After installing OME 1.2 on Windows 2012, the UI goes blank automatically when the system is idle and is only refreshed on mouse over or browser refresh.
A: Try Installing latest MS-

Updates from Microsoft using “Control panel > Windows Updates” and verify IE10 version has to be greater than >16384.

10.Q: Why is my EqualLogic blade device not classified under the Modular group?
A: Make sure the chassis service tag in EqualLogic is populated for that to be classified under Modular group.


10.Misc.

1.Q: What ports and protocols are needed to be opened for proper access to the Essentials server?
A: Many ports and protocols...snmp, http, https, omremote, rpc, smb, 2607… and also add exe file copy over http.  

2.Q: What are SNMP “authentication traps”?
A: An authentication trap is sent when the SNMP agent is hit with an inquiry with a community name it does not recognize. These are case-sensitive also.The traps are useful to know if someone is probing your system, although its better nowadays to just sniff packets and find out the community name that way.If you use multiple community names on the network, and some management might overlap, people may want to turn these off as they become false positives (annoyances).

From MS (http://technet.microsoft.com/en-us/library/cc959663.aspx):Send Authentication Traps. When an SNMP agent receives a request that does not contain a valid community name or the host that is sending the message is not on the list of acceptable hosts, the agent can send an authentication trap message to one or more trap destinations (management systems). The trap message indicates that the SNMP request failed authentication. This is a default setting. 

3.Q:  Why is OME CLI functionality not working?
A: OME CLI functionality will not work when non default port is used for installing OME. If you want to use the CLI functionality, make sure that the default port 2607 is used during installation.

4.Q: Unable to delete nested custom groups from OME CLI, Why?
A: OME CLI functionality will not work when non default port is used for installing OME. If you want to use the CLI functionality, make sure that the default port 2607 is used during installation.

5.Q: Where can I get the files used to install OMSA?
A: See below links:

Microsoft Windows

Install and upgrades

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-WIN-6.5.0-2247_A01.10.exe

Major Upgrades

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-DUP-WIN-6.5.0-2247_A01.8.exe

Minor Upgrades

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-SP-WIN-6.5.0-2247_A01.12.msp

Citrix XenServer

Version 5.6

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.XenServer56_A01.11.iso

VMware ESXi Version 4.1

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-6.5.0-2247.VIB-ESX41i_A01.zip

Linux Distribution Bundle containing the below listed packages (they can also be downloaded individually)

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247_A01.15.tar.gz

VMware ESX Version 4.1

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.ESX41.i386_A01.tar.gz

Red Hat Enterprise Linux 

Version 5 i386

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.RHEL5.i386_A01.3.tar.gz

Version 5 x86 and x64

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.RHEL5.x86_64_A01.4.tar.gz

Version 6 x86 and x64

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.RHEL6.x86_64_A01.5.tar.gz

SUSE Linux Enterprise

Version 10 i386

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES10.i386_A01.13.tar.gz

Version 10 x86 and x64

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES10.x86_64_A01.6.tar.gz

Version 11 i386

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES11.i386_A01.14.tar.gz

Version 11 x86 and x64

ftp://ftp.dell.com/sysman/OM-SrvAdmin-Dell-Web-LX-6.5.0-2247.SLES11.x86_64_A01.7.tar.gz

6.Q. Why are the alerts and task schedules in OME display a timestamp which is off by 1 hour?
A: Check the location settings for the server in “Regional and language settings” under control panel to make sure the location for the server and date/time formats are set appropriately for the region where the server is located.

7. Q: Why is OME taking a long time to launch or traverse through various pages?
A: Please check if the windows update is running in the background. Windows update impacts the SQL performance if the update is related to SQL which in turn affects OME’s performance. Once the update is complete, Reboot your machine and launch OME again.

8.Q:  OME does not launch and throws an error message stating “An add-on for this website failed to run”
A: Add the OME URL to the exceptions list in the Internet Explorer options -> Security -> Local Intranet -> Sites -> Advanced ->

9. Q:  OME memory consumption shoots up when I have logged in as a domain user. What do I do to fix this issue?
A: Disable/Uncheck the following settings in the IE browser

• Check for Publisher’s certificate revocation

• Check for server certificate revocation

10. Q:  After running Discovery /Inventory on a system running Linux, command line task is failing with error message "unable to generate a Trusted Key for Linux"
A: Run an OMSA Deployment Task  which will successfully generate the Trusted Key. Once the OMSA deployment task complete you can run the Command Line Task on the target  because the new SSH Key would have been generated 

11. Q: I am using IE 11 and have enabled ActiveX, but I cannot launch the Troubleshooting Tool. Why?
A: Make sure you have the latest updates from Microsoft installed on the system. Older versions of IE 11 may have compatibility issues.

11.Compellent Known Issues

1.Q: The health status is not returned correctly by the Dell-Compellent device and OME shows the health state as unknown.
A: The fix is part of the Dell-Compellent firmware version 6.3.10 or above. Please make sure your Dell-Compellent device has the latest firmware installed.

2.Q: OME shows the Dell-Compellent Agent Version as 'M'.
A: The fix is part of the Dell-Compellent firmware version 6.3.10 or above. Please make sure your Dell-Compellent device has the latest firmware installed.

3.Q: Inventory details are not shown for most of the tables and it is shown as N/A in OME for Dell-Compellent viz Controller Information table, Enclosure Information table, Physical Disk Information table OR Most of the details in the reports for Dell Compellent are empty.
A: The fix is part of the Dell-Compellent firmware version 6.3.10 or above. Please make sure your Dell-Compellent device has the latest firmware installed.

4.Q: Service tag is not shown for Dell-Compellent device by OME.
A: The fix is part of future Dell-Compellent firmware. Please make sure your Dell-Compellent device has the latest firmware installed.

5.Q: OME does not show the model information for Dell-Compellent.
A: The fix is part of future Dell-Compellent firmware. Please make sure your Dell-Compellent device has the latest firmware installed

6. Q: When I discover a RAC device for my Compellent storage, I don’t see an entry for it in the OME device tree under the RAC device group.
A: When both the Compellent storage device and the RAC device are discovered in OME, OME 1.3 correlates the RAC device for Compellent. The information for the RAC device can be seen under Dell Compellent Arrays group by looking at the inventory information of the Compellent Storage device.

12. Configuration

1. Q: Are there restrictions on attributes like device name when using the Create Template feature to get a Chassis configuration?
A: For attributes that a user can create, we require that they do not contain brackets (‘[‘ or ‘]’).

2. Q: I set new minimum bandwidths for my partitioned NIC and deployment fails.The total minimum bandwidth I set adds up to 100 per partition.Why would I get an error on “MinBandwidth”?
A: When you deploy new bandwidths they are processed one at a time in order.If the new value increases the total “MinBandwidth” over 100 it will fail to deploy.Set the new values to zero as an intermediate step before applying the desired values if you get this error.

Example

MinBandwidth
OLD     20, 20, 30, 30
NEW     70, 10, 10, 10 – This will FAIL with old value 20 and new value will be blank

Contents: Download - Documentation - Whitepapers - Forum

The Dell MD Storage Array Management Pack Suite for Microsoft System Center 2012 Operations Manager SP1, System Center 2012 Operations Manager, System Center Operations Manager 2007 R2 and System Center Essentials 2010 integrates Dell PowerVault MD Storage Arrays monitoring into Operations Manager. The Management Packs provide a list of Dell-specific views that you can use to observe and drill down the system status in a network.

The latest version is 6.0 (released in November 2014) and can be downloaded from http://www.dell.com/support/home/ar/en/ardhs1/Drivers/DriversDetails?driverId=T7G6T

Key new features in Dell MD Storage Arrays Management Pack Suite 6.0:

• Support for the following Dell PowerVault MD Storage Arrays:    MD3800f, MD3800i, MD3820f, MD3820i, MD3860f, MD3860i, MD3400, MD3420, MD3460
• Added support for Controller Firmware: 08.10.
• New support for SNMP Traps from MD Storage Arrays for Microsoft System Center 2012 Operations manager consoles.
• Added support for new recovery failures.
• Revised and updated knowledge articles for recovery failures.

• Dell Modular Disk (MD) Storage Array Management Pack for System Center Operations Manager & System Center Essentials Version 6.0

• Dell Modular Disk (MD) Storage Array Management Pack for System Center Operations Manager & System Center Essentials Version 5.0
  
  
• Dell MD Storage Array Management Pack Suite for System Center Operations Manager Version 4.1

• Dell MD Storage Array Management Pack Suite for System Center Operations Manager Version 4.0

Product Documentation

Version 6.0 Documentation

Version 5.1 Documentation

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

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.

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.

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.

What's New

( top )

( top )

( top )

( top )

Hardware

( top )

  ( top )

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

What's New

( 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.

Contents: Download - Documentation - Whitepapers - Videos - Forum - Blogs - FAQ 

OpenManage Essentials (OME) is a systems management console that provides simple, basic Dell hardware management and is available as a free download.

The latest release is OME 2.1 and it launched on September 15, 2015.  It brings a lot of great new features to the product.

Dell OpenManage Essentials (OME) version 2.1 is the latest release of our easy to install, intuitively simple to use, and customer-acclaimed, One-to-Many systems management console that is optimized to provide comprehensive lifecycle management of Dell PowerEdge converged, rack and tower servers.  OpenManage Essentials also delivers extensive infrastructure health monitoring, control, and support for Dell servers, storage, networking, business clients, firewall appliances, and 3^rd party hardware.   

Key NEW  features  available with OpenManage Essentials v2.1:

• Stateless computing with centralized management of server virtual I/O addresses within OME - Server Configuration Management
  • Simplify server provisioning through profile-based deployments
  • Enable elasticity of compute resources through definition of a stateless computing pool in a Boot-from-SAN environment
  • Enable simplified server migration for disaster recovery operations
• Simplified discovery for Dell PowerEdge converged platforms (M1000e, FX2 and VRTX)
  • • Elimination of multiple steps in establishing discovery ranges for various components (CMC, iDRACs, and IOAs)
    • Automated speedy discovery of Dell converged platforms through use of a single CMC credential 
• Full lifecycle management (discovery/inventory, monitoring, update and server configuration management) is now enabled for the followingDell PowerEdge C-series servers:    
  • • PowerEdge C4130
    • PowerEdge C6320
• Report enhancements include the availability of additional reports and categorizations
• Alert enhancements provide root-cause sources and recommendations on how to resolve issues

Existing OpenManage Essentials features also available now in OME v2.1:

• Anytime, anywhere mobile access to data center health status information with OpenManage Mobile
• Integration with Dell ProSupport SupportAssistforproactive remote support, automated support case creation and hardware failure notification sent securely to Dell technical support for intelligent issue analysis, diagnosis, and part-replacements upon customer request
• Comprehensive, deep management visibility and control for Dell blades and Chassis Management Controller (CMC), Dell storage and networking devices, and Dell AppAssurethrough a context sensitive link and launch of the respective element management interface
• Geographic View at-a-glance visibility of VRTX systems’ physical locations geographically mapped
• Agent-free OOB inventory and update of Dell 11G and 12G PowerEdge servers
• Agent-free monitoring of Dell PowerEdge 12G servers
• Traditional agent-based systems management functionality in all supported 9-12G servers
• Management of Dell PowerEdge C platforms with IPMI
• Monitoring of non-Dell HW devices through import of 3^rd party HW SNMP MIBs
• Reporting of Warranty expiration and comprehensive inventory reports
• Hardware component-level monitoring and updates for Dell PowerEdge servers, blade systems and internal storage arrays
• Support and control of Dell hardware in Windows, Linux, VMware, Hyper-V and OpenSource  environments
• Enhanced management functionality through integration with the following Dell solutions :

• Dell KACE K1000 Appliance– comprehensive, economical and straightforward management of both clients and servers through a single interface
• Dell Repository Manager– version control and scheduling of PowerEdge server updates 
• Dell OpenManage Power Center– optimization of  PowerEdge power usage

Dell OpenManage Essentials Core Features:

OpenManage Essentials is available as a free download from the Dell Support Site. The OME console's inventory function integrates with the Dell Repository Manager to automatically facilitate the creation of custom repositories of new updates for your systems.  

If you are new to the product, Take the Quick Tour or watch the OME Overview Video below:

Download  

• Download OpenManage Essentials 2.1 
  • previous versions available in the Archive section

• Dell Troubleshooting Tool for OME v2.1
• Dell MIB Import Tool for OME v2.1
• Download the Dell SNMP Configuration Tool

Discuss

• OpenManage Essentials Discussion Forum 

• OpenManage Essentials Blog Posts 

Learn

• OpenManage Essentials 2.1 Documentation - (Release Notes, Manuals, Support Matrix, User's Guide, Whitepapers) coming soon!
• OpenManage Essentials 2.0.1 Documentation - (Release Notes, Manuals, Support Matrix, User's Guide, Whitepapers)
• OpenManage Essentials 2.0 Documentation - (Release Notes, Manuals, Support Matrix, User's Guide, Whitepapers)

• OME Frequently Asked Questions (FAQ) 
• OME Tips and Tricks
• OME vs Dell IT Assistant
• OME Quick Tour
• Tutorial videos as the bottom of this page
• Service Offering: Remote Installation and Configuration of OME

Whitepapers and Best Practices

Video 1: Adding Devices to the Bare Metal and Re-purpose Device Group

 (Please visit the site to view this video)

Video 2: Configuring Credentials and Scheduling Inventory

 (Please visit the site to view this video)

Video 3: Configuring a Deployment Share

 (Please visit the site to view this video)

Video 4: Creating a Configuration Template

 (Please visit the site to view this video)

Video 5: Deploying a Bare Metal Device

 (Please visit the site to view this video)

Video 6: Detecting Configuration Drift

 (Please visit the site to view this video)

Video 7: Auto Deploying Bare Metal Devices

0:08 - Installing OpenManage Essentals 
0:56 - Discovery and Inventory 
2:03 - Monitoring Health of Devices 
2:43 - Using the Home Portal
5:58 - Deploying Updates
7:03 - KACE Integration + MonitoringOpenManage 

	OpenManage Essentials and Repository Manager Integration
	Enable SNMP on OpenManage Server Administrator for ESXi4
	Enable SNMP on OpenManage Server Administrator for Windows
	Enable SNMP on OpenManage Server Administrator for Linux (RHEL)
	Dell OpenManage Essentials with KACE Integration
	OpenManage Essentials Custom Alerts
	OpenManage Essentials Apply System Updates
	Installing Dell OpenManage Essentials
	OpenManage Essentials Discovery and Inventory
	Dell OpenManage Essentials Discovery

Contents: Manuals - Download - Videos

Dell OpenManage Storage Services (OMSS), also known as Dell OpenManage Server Administrator Storage Management is designed for system administrators who implement hardware RAID solutions and understand corporate and small business storage environments. OMSS allows you to configure the storage components attached to your system. These components include RAID and non-RAID controllers and the channels, ports, enclosures, and disks attached to them.

Using OMSS, you can configure and manage controller functions without accessing
the BIOS. These functions include configuring virtual disks and applying RAID levels and hot spares for data protection. You can initiate many other controller functions like rebuilds, troubleshooting, setting thresholds, and so on. Most functions can be configured and managed while the system remains
online and continues to process requests.

Manuals

• Various OpenManage
• Various Server Administrator

Dell OpenManage version 8.2 Documentation

• Documentation (Events,  Management Tools, Release Notes etc.)

Dell OpenManage version 8.1.1 & version 8.1 Documentation

• Documentation (Events,  Management Tools, Release Notes etc.)

Dell OpenManage version 8.0.1 Documentation

• Documentation (Events,  Management Tools, Release Notes etc.)

 Dell OpenManage version 8.0.2 Documentation

• Documentation (Events,  Management Tools, Release Notes etc.)

Server Administrator v8.2 Documentation

You can refer to all the following and more documents from the Server Administrator Manuals page.

• Server Administrator Storage Management Guide
• Server Administrator CIM Reference Guide.
• Server Administrator SNMP Reference Guide.
• Server Administrator CLI (Command Line Interface) Guide.
• Server Administrator User's Guide
• Server Administrator Readme
• Server Administrator Release Notes
• Server Administrator Installation Guide
• Storage Management User's Guide

Server Administrator version 8.1.1 & version 8.1 Documentation

You can refer to all the following and more documents from the Server Administrator Manuals page.

• Server Administrator Storage Management User's Guide
• Server Administrator CLI (Command Line Interface) Guide.
• Server Administrator User's Guide
• Server Administrator Installation Guide
• Server Administrator Release Notes

Server Administrator version 8.0.1 Documentation

You can refer to all the following and more documents from the Server Administrator Manuals page.

• Server Administrator Storage Management User's Guide
• Server Administrator CLI (Command Line Interface) Guide.
• Server Administrator User's Guide
• Server Administrator Installation Guide
• Server Administrator Release Notes

Server Administrator version 8.0.2 Documentation

You can refer to all the following and more documents from the Server Administrator Manuals page.

• Server Administrator Storage Management User's Guide
• Server Administrator CLI (Command Line Interface) Guide.
• Server Administrator User's Guide
• Server Administrator Installation Guide
• Server Administrator Release Notes

Download

OMSA version 8.2 Download

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

Microsoft Windows:

• x86 (190MB)
• x64 (200MB)

Linux:

• Consolidated Package  (1008 MB)
• Red Hat Enterprise Linux 7 (x64) (Distribution Package, 258 MB)
• Red Hat Enterprise Linux 6 (x64) (Distribution Package, 261 MB)
• Novell SuSE Linux ES 11(x64) (Distribution Package, 250 MB)
• Novell SuSE Linux ES 12(x64) (Distribution Package, 238 MB)

VMware vSphere (ESXi) VIB:

• ESXi 6.0 (7 MB)
• ESXi 5.5 (7 MB)
• 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 version 8.1.1 Download

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

Microsoft Windows:

• x86 (186MB)
• x64 (187MB)

Linux:

• Consolidated Package  (712 MB)
• Red Hat Enterprise Linux 7 (x64) (Distribution Package, 199 MB)
• Red Hat Enterprise Linux 6 (x64) (Distribution Package, 193 MB)
• Novell SUSE Linux Enterprise Server 11 (Distribution Package, 163 MB)

Citrix XenServer (Supplemental Pack):

• XenServer 6.5 (120 MB) 

OMSA version 8.1 Download

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

Microsoft Windows:

Linux:

VMware vSphere (ESXi) VIB:

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

Videos

OMSS - Enhancements in Virtual Disk Creation Wizard

Enhancements in Virtual Disk Creation Wizard

The following video explains the methods of OpenManage Storage Services (OMSS) aided Virtual Disk creation via Express and Advanced Wizard on Dell PowerEdge™ systems. 

Enhancements in Virtual Disk Creation Wizard feature from OpenManage Storage Services (OMSS) are available from OpenManage version 7.2 onwards.

This feature provides an improved algorithm that allows you to create RAID volumes in a more usable and effective approach. The feature has been developed keeping legacy compatibility in mind, therefore retaining all other feature and support which were available in the previous versions.

As a new feature of OM 7.2 – OMSS – Virtual Disk Creation Wizard, an improved algorithm that allows customers to create (any supported) RAID volumes in a more usable and effective approach is implemented. This video primarily showcase the user interactive pages of the same.

Video shows screen by screen deep dive for:

• Virtual Disk creation using the Express Wizard
• Virtual Disk creation using the Advanced Wizard with Dedicated Hot spare
• Virtual Disk creation using the Advanced Wizard with Dedicated Hot spare and Encryption

(Please visit the site to view this video)

OMSS - Configuring RAID 5 Virtual Disk using Server Administrator

The following video explains how to Configure RAID 5 using Server Administrator on Citrix XenServer 6.2.

RAID is a way to virtualize multiple, independent hard-disk drives into one or more arrays to improve performance, capacity, and reliability (availability).

RAID Level 5 (Striping With Distributed Parity) - RAID 5 provides data redundancy by using data striping in combination with parity information. Rather than dedicating a physical disk to parity, the parity information is striped across all physical disk drives in the disk group.

Using OpenManage Server Administrator (OMSA), you can configure or reconfigure RAID from within the operating system. There is no need to restart the server to access the controller BIOS.

(Please visit the site to view this video)

OpenManage Server Administrator

Configuring RAID 5 Virtual Disk using Server Administrator

Server Administrator v8.2 Documentation

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

• Server Administrator Storage Management Guide
• Server Administrator CIM Reference Guide.
• Server Administrator SNMP Reference Guide.
• Server Administrator CLI (Command Line Interface) Guide.
• Server Administrator User's Guide
• Server Administrator Readme
• Server Administrator Release Notes
• Server Administrator Installation Guide
• Storage Management User's Guide

Why do I want to use this tool?

Dell Troubleshooting Tool enables you to gather information about problems that may occur while using OpenManage Essentials. This tool can be used to diagnose discovery-related problems that may occur while connecting to managed nodes using various protocols such as SNMP, WMI, SSH, WS-Man, PowerVault modular disk specific connection, and so on. This tool also helps you to verify the SMTP specific settings, SNMP trap listening, SNMP trap forwarding, and TCP/UDP port availability. You can also use the tool to diagnose issues that may occur while updating patches through in-band method and also verify connectivity issues that may occur during deployment using a network share. This tool also includes several other tests that enable you to verify issues that may occur while using OpenManage Essentials. For more information, see the tool’s Help and readme file.

Download the standalone Dell Troubleshooting Tool

• Version 3.4.3 (latest)
• Version 3.4.2
• Version 3.4.1
• Version 3.3
• Version 3.2
• Version 3.1

Examples:

The following are some example use cases:

• You are either unable to discover a supported device in OpenManage Essentials or the device is classified as an unknown device while using SNMP protocol. Run this tool and select the SNMP protocol, specify protocol specific settings, and provide remote system IP Address. For Dell PowerEdge servers, verify whether the tool provides Server Administrator version in the result area for a successful test (using the SNMP Protocol for an in-band server discovery).
• You can verify if you can ping a remote device (using Ping/ICMP protocol) and also check if you can resolve the host name of the device from the management station (using Name Resolution protocol).
• You can verify if the Dell OpenManage Server Administrator services are running on a remote device (using Services protocol).
• You can check warranty status of any Dell server (using Service Tag).
• You can execute a command on the remote system and verify its output.
• You can listen to incoming SNMP traps.
• You can use this tool to forward test SNMP traps.
• You can use this tool to verify the SMTP settings to ensure that OpenManage Essentials can successfully run the Alert Emails action.
• You can use this tool to verify the availability of the local or remote ports.
• You can identify the user groups of the active user.
• You can view or delete the pending system update jobs in an iDRAC.
• You can verify connectivity to the deployment file share.

About Dell Troubleshooting Tool:

Using this tool you can gather more information about failures and issues with the discovery of the network devices (for example, Dell servers, clients, or any other network resources) in Dell OpenManage Essentials.

Dell Troubleshooting Tool also has the ability to verify Emails, SMTP settings, check for the availability of ports, run a command on a remote device, send and listen for SNMP traps, check warranty status, verify connectivity issues to a network share and iDRAC while deploying files.

Dell Troubleshooting Tool has tests that you can use to debug issues during in-band system update, find detailed information about iDRAC jobs or delete iDRAC jobs, and verify the IP address formed during out-of-band system update.

This tool is optional and is only required if you want to debug issues. The tool is also available as part of the OpenManage Essentials installer media. The tool helps you identify the issue. However, you have to manually resolve the issue outside of the tool.

Installation Requirements:

Troubleshooting Tool is a 64-bit application that requires the following

• Supported Operating System

• • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2012
  • Microsoft Windows 2008 R2 SP1
  • Microsoft Windows 2008 SP2
  • Windows 8.1 (x64)
  • Windows 8 (x64)
  • Windows 7 (x64)

• Microsoft .NET framework 4.0 or later
• You should have write permission on the folder where you have installed this utility. This is required to execute the require tests and show the results successfully
• You require administrator permissions to run the tool executable

Please review the readme file after you install the utility. Feel free to post updates on the www.delltechcenter.com/ome forum if you are not able to make use of this utility in a given scenario or need further help related to either this tool or OpenManage Essentials. That will be helpful to the community. 

 For more information about OpenManage Essentials, go to www.DellTechCenter.com/OME

Troubleshooting tool Videos:

(Please visit the site to view this video)

Why do I want to use this tool?

OpenManage Essentials provides support for formatting hardware alerts (i.e., SNMP traps) for most Dell enterprise hardware. If you want to monitor non-Dell devices, you can use the OpenManage Essentials MIB Import Utility to define new alerts for OpenManage Essentials. Defining alerts enables OpenManage Essentials to monitor a wider range of hardware and to set up email and forwarding rules for these devices.  The MIB Import Utility is an optional tool that is only required if you want to add support for formatting alerts received from third-party devices.

The details:

Dell OpenManage Essentials MIB Import Utility enables you to extract trap definitions from SMIv1 or SMIv2 management information base (MIB) files. The extracted traps can be viewed and edited before importing them to OpenManage Essentials. This tool also enables you to manually define and manage traps. Using the imported and manually-managed trap definitions, OpenManage Essentials classifies the incoming trap from a specific device as expected.

If you want to monitor (classify incoming SNMP traps) a SNMP supported device that is not currently supported by OpenManage Essentials, use MIB Import Utility to import or manually define that device’s SNMP trap definitions for OpenManage Essentials.

Please review the readme file after you install this tool.  The readme also provides a list of some of
the MIBs that have been tested using this tool. Feel free to post updates on the DTC/OME forum including MIBs that you have imported using this tool.  Your posts would be of help to the community. 

Understandably, all MIBs are different and not all MIBs adhere to the specifications. This tool tries to accommodate these differences, but if you notice any issues with a MIB you are trying to import, post a question on the OpenManage Essentials forum.

Ensure the following before using this utility:

• The remote device supports SNMP (v1/v2) protocol.
• SNMP services on the remote device are working fine and trap destination point to
  the OME system.
• You have the device specific SNMP MIB files (main MIB and its reference MIBs).
• Validate these specific MIB(s) using a standard MIB compiler tool.

Download: OpenManage Essentials MIB Import Utility v1.5 (for OME v2.1)

Download: OpenManage Essentials MIB Import Utility v1.4 (for OME v2.0)

Download: OpenManage Essentials MIB Import Utility v1.3 (for OME v1.3)

Download: OpenManage Essentials MIB Import Utility v1.2 (for OME v1.2)

Download: OpenManage Essentials MIB Import Utility v1.1 (for OME v1.1)

Download: OpenManage Essentials MIB Import Utility v1.0 (for OME v1.0.1)

Whitepaper: Monitoring Force 10 Switches in OpenManage Essentials   (Deprecated)

Whitepaper: Monitoring HP Servers and Third Party Hardware in OpenManage Essentials  

Videos:

MIBImport Utility Overview:

(Please visit the site to view this video)

Adding a trap definition:

(Please visit the site to view this video)

Deleting a trap definition:

(Please visit the site to view this video)

Editing a trap definition:

(Please visit the site to view this video)

Reverting a trap definition:

(Please visit the site to view this video)

For more information about OpenManage Essentials, go to www.DellTechCenter.com/OME

What is the OpenManage Integration for VMware vCenter?

The OpenManage Integration for VMware vCenter (OMIVV) is designed to streamline the management processes in your data center environment by allowing you to use VMware vCenter to manage your entire server infrastructure - both physical and virtual. From monitoring system level information, bubbling up system alerts for action in vCenter, rolling out firmware updates to an ESXi cluster, to bare metal deployment, the OpenManage Integration will expand and enrich your data center management experience with Dell PowerEdge servers.

OpenManage Integration for VMware vCenter - Value proposition

Getting started

To download a free 5 host, 90 day evaluation appliance for version 3.0, please click here. The following video steps through the installation process:

(Please visit the site to view this video)

What's new?

October 5th, 2015 - v3.0 Respin

•    Support for vSphere v6.0
•    Enhanced resources for the OMIVV virtual appliance
•    Requires new OVF deployment, compatible with v2.x licensing
•    Resource allocation changes for better scalability

OMIVV Features

OMIVV Downloads

New! 3.0
2.3.1
2.3
2.2
2.1
2.0
1.7
1.6
1.5.1
1.5

OMIVV Manuals

New! 3.0
2.3.1
2.3
2.2
2.1
2.0
(Under the name Dell Management Plug-in for VMware vCenter)
1.7
1.6
1.5.1
1.5

Additional Videos

Features Overview
Chassis integration setup
Chassis information deep dive

Whitepapers

Technical overview
How licensing works
Migrating from v1.6 / 1.7 to v2.x
Migrating from v2.x to v3.0
How to connect servers
Generating reports
How to use bare-metal server discovery
Hypervisor deployment
Using Dell Repository Manager with OMIVV
How to do firmware updates
How to update using a local update directory

Other Resources

OpenManage Integration for VMware vCenter on Dell.com

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.

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.

iDRAC8 Quick Sync with OpenManage Mobile

(Please visit the site to view this video)

( 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/).

General Overview

iDRAC 7 & 8 Feature and Licensing Information Sheet (New for 13G)

iDRAC8 with Lifecycle Controller Tech Chat slides (new for 13G)

Introducing iDRAC8 with Lifecycle Controller for Dell 13th Generation PowerEdge Servers (new for 13G)

Overview of Dell Systems Management using IPMI (updated for 13G)
PowerEdge Software Licensing (new for 13G)

Principled Technologies' Review of 13G PowerEdge OpenManage(New for 13G)

Understanding Physical Computer System View Profile Implementation (New for 13G)

Configuring Low-Latency Environments in PowerEdge Servers

Dell iDRAC7 Licensing Whitepaper - Differences between iDRAC6 and iDRAC7

iDRAC7 with Lifecycle Controller - Feature Guide

Lifecycle Controller Workflow Optimization

New Feature Overview: December 2013 Releases of iDRAC7 and Lifecycle Controller 2

New Features and Usability Enhancements to RACADM Commands in iDRAC7

Networking and I/O configuration

Disabling a Third-Party PCIe Card Cooling Response with Dell PowerEdge Servers (new for 13G)

Dell Network Adapters with iDRAC (Updated Sept 2015)

IPv6 Best Practices using iDRAC (new for 13G)

Managing IO Identity and Server State Information (New for 13G)

Optimizing I/O Identity and Applying Persistence Policy on Network and Fibre Channel Adapters (new for 13G)

Retrieving Server OS Networking Information through iDRAC (New for 13G)

Understanding PreBoot Networking on Dell PowerEdge Servers (new for 13G)

Auto Dedicated NIC Feature in iDRAC7

Auto-Discovery Network Setup Specification

Configuring BIOS and NIC Using RACADM through Dell iDRAC

Converged Network Adapters with NIC, iSCSI, and FCoE Support

OS to BMC Pass-through operation

FCoE Boot Configuration Setup on Intel Card

FCoE boot using Broadcom card

iDRAC7 Network and Virtual Media Performance

iDRAC7 Networking and Improved Remote Access Performance

Network IO Identity

Reinitiate Auto-Discovery

Remote NIC Configuration Management  

Scripting and Server Configuration Profiles

AutoConfig - Enabling rapid configuration of Dell servers using DHCP (12G and 13G)

Creating Applications using the WSMAN API (New for 13G)

Methods to Save and Restore PowerEdge Server Configuration Settings and Firmware Images (New for 13G)

Using Filter Dialects with the WSMAN API (New for 13G)

Automatic Backup Server Profile

Creating and Managing Server Configuration Profiles

Hardware Inventory Viewing Script

How to Build Inventory Reports 

iDRAC Cloning

Import and Export Server Profiles

Lifecycle Controller Backup and Restore in Dell PowerEdge 12th Generation Servers

Programmatic Scripting with WSMAN

Scripting WSMAN to Deploy OS Drivers

Scripting WSMAN to Deploy OS using Remote ISO Image to Stage and Boot

Scripting WSMAN to Deploy OS using vFlash to Stage and Boot to ISO

Server Cloning with Server Configuration Profiles

Server Configuration Profile - XML File Structure (files )

Understanding the iDRAC Power State Management in Base Server Profile

Understanding the iDRAC Power State Management Profile

Using Microsoft Windows PowerShell CIM Cmdlets with Dell iDRAC

BIOS and UEFI

BIOS POST Troubleshooting Guide for 13th Generation PowerEdge Servers(new for 13G)

BIOS Setup User Guide for 13th Generation PowerEdge Servers(new for 13G)

Defining a Secure Boot Policy (new for 13G)

Updating BIOS on Dell 12G PowerEdge Servers (iDRAC7 - 12G only) 

Updating BIOS on Dell 13G PowerEdge Servers (iDRAC8 - 13G only) (New for 13G)

Using Lifecycle Controller to Configure UEFI Secure Boot and OS Deployment(new for 13G)

Configuring BIOS and NIC Using RACADM through Dell iDRAC

OS deployment

Unattended Installation of Red Hat Enterprise Linux 7 Operating System on Dell PowerEdge Servers Using iDRAC With Lifecycle Controller(new for 13G)
Unattended Installation of Windows 2012 (12G and 13G)

Operating System Deployment in PowerEdge Servers

Operating Systems Deployment using iSCSI or FCOE LUN

Updates

Automatic Updates in Dell PowerEdge 12G servers  

Creating and updating iDRAC repository with Repository Manager

Lifecycle Controller Platform Update in Dell PowerEdge 12th Generation Servers

Lifecycle Controller with Dell Repository Manager

PowerEdge Updates with Repository Manager Best Practices Guide

Recommended methods of Updating Firmware on Dell Servers

Recommended Workflow for Performing Firmware Updates on PowerEdge Servers

Remote Firmware Update

Updating Firmware on PowerEdge Servers Using the iDRAC7 Web Interface

Using Dell Repository Manager to create a Bootable ISO and perform updates

Storage & PERC

Dell’s vFlash SD Flash Media Card – Better Endurance and Performance via Over-Provisioning

Understanding Real Time Storage Configuration for PERC9(new for 13G)
Managing Web Server Certificates on iDRAC (New for 13G)
Express Flash NVMe PCIe SSD Devie Monitoring, Inventory, and Configuration (New for 13G)
vFlash Overview

vFlash Partition Management 

vFlash using the Lifecycle Controller GUI

Security

Security with iDRAC8 (and 7)(New!)

Managing Web Server Certificates on iDRAC (New for 13G)

System Erase in Dell 13th Generation PowerEdge Servers (New for 13G)
New Security Features in Integrated Dell Remote Access Controller 7

Active Directory Integration & Certificates

Active Directory using Lifecycle Controller 

Integrate iDRAC8 with Active Directory (New for 13G)
Integrating iDRAC7 with Microsoft Active Directory

iDRAC Web Server Certificate Management

Monitoring and Alerting

iDRAC QuickSync Technical Guide- Nov. 2014

Managing Backplane Split Mode(new for 13G)
Web Services Eventing Support for Hardware Inventory and Monitoring(New for 13G)

Pre-failure alerts provided by Dell server systems management - updated!

PSU Mismatch System Behavior for Dell PowerEdge Servers(For 12G & 13G)

Using VNC with iDRAC(New for 13G)
Enhanced Out of Band Performance Monitoring(New for 13G)
FAQ: iDRAC Quick Sync & OpenManage Mobile - October 2014 (New for 13G)

Agent-free Inventory and Monitoring for Storage and Network Devices

Discovering Features in the iDRAC Remote Services API

Gathering information from iDRAC7 using SNMPv3

OMSA / OMSS to iDRAC7 SNMP-Gets Migration Guide

Using OpenManage Essentials to configure iDRAC7 Action Alerts

Using the iDRAC7 Video Capture Feature

Web Service Eventing for iDRAC7 1.30.30 or later versions

Support Assist & Part Replacement

Generating Tech Support Report on 13th Generation Dell PowerEdge Servers (New for 13G)
Motherboard Replacement

Lifecycle Controller Part Replacement

Part Replacement

Restoring iDRAC7 License after System Board Replacement

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.

Product 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
• Upgrade from previous Dell OpenManage Plug-in Version 1.0 to the current Dell OpenManage Plug-in Version 2.0 for Nagios Core
  

Business benefits

• Protect existing investment in Nagios Core product to easily integrate and monitor Dell servers 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

Customers can choose to monitor Dell servers without software agents by leveraging agent-free, out-of-band technology using iDRAC with Lifecycle Controller. By using out-of-band management, IT administrators no longer need to install or periodically certify/validate the traditional in-band OpenManage Server Administrator (OMSA) agent installed in the server Operating System (OS). This out-of-band management technology allows IT administrators to effectively monitor Dell systems with increased availability from any location, and without the use of agents. It accomplishes this regardless of operating system or hypervisor presence or state.

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

Supported Dell devices:

• Dell PowerEdge Servers 12th Generation (12G) and 13th Generation (13G)

Product Download 

• Dell OpenManage Plug-in version 1.0 for Nagios Core

Product Documentation

Learn

• 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 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)

Quick Links:

DCIM Extensions Library Profile Collection

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  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

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.

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.

iDRAC8 Quick Sync with OpenManage Mobile

(Please visit the site to view this video)

( 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/).

General Overview

iDRAC 7 & 8 Feature and Licensing Information Sheet (New for 13G)

iDRAC8 with Lifecycle Controller Tech Chat slides (new for 13G)

Introducing iDRAC8 with Lifecycle Controller for Dell 13th Generation PowerEdge Servers (new for 13G)

Overview of Dell Systems Management using IPMI (updated for 13G)
PowerEdge Software Licensing (new for 13G)

Principled Technologies' Review of 13G PowerEdge OpenManage(New for 13G)

Understanding Physical Computer System View Profile Implementation (New for 13G)

Configuring Low-Latency Environments in PowerEdge Servers

Dell iDRAC7 Licensing Whitepaper - Differences between iDRAC6 and iDRAC7

iDRAC7 with Lifecycle Controller - Feature Guide

Lifecycle Controller Workflow Optimization

New Feature Overview: December 2013 Releases of iDRAC7 and Lifecycle Controller 2

New Features and Usability Enhancements to RACADM Commands in iDRAC7

Networking and I/O configuration

Disabling a Third-Party PCIe Card Cooling Response with Dell PowerEdge Servers (new for 13G)

Dell Network Adapters with iDRAC (Updated Sept 2015)

IPv6 Best Practices using iDRAC (new for 13G)

Managing IO Identity and Server State Information (New for 13G)

Optimizing I/O Identity and Applying Persistence Policy on Network and Fibre Channel Adapters (new for 13G)

Retrieving Server OS Networking Information through iDRAC (New for 13G)

Understanding PreBoot Networking on Dell PowerEdge Servers (new for 13G)

Auto Dedicated NIC Feature in iDRAC7

Auto-Discovery Network Setup Specification

Configuring BIOS and NIC Using RACADM through Dell iDRAC

Converged Network Adapters with NIC, iSCSI, and FCoE Support

OS to BMC Pass-through operation

FCoE Boot Configuration Setup on Intel Card

FCoE boot using Broadcom card

iDRAC7 Network and Virtual Media Performance

iDRAC7 Networking and Improved Remote Access Performance

Network IO Identity

Reinitiate Auto-Discovery

Remote NIC Configuration Management  

Scripting and Server Configuration Profiles

AutoConfig - Enabling rapid configuration of Dell servers using DHCP (12G and 13G)

Creating Applications using the WSMAN API (New for 13G)

Methods to Save and Restore PowerEdge Server Configuration Settings and Firmware Images (New for 13G)

Using Filter Dialects with the WSMAN API (New for 13G)

Automatic Backup Server Profile

Creating and Managing Server Configuration Profiles

Hardware Inventory Viewing Script

How to Build Inventory Reports 

iDRAC Cloning

Import and Export Server Profiles

Lifecycle Controller Backup and Restore in Dell PowerEdge 12th Generation Servers

Programmatic Scripting with WSMAN

Scripting WSMAN to Deploy OS Drivers

Scripting WSMAN to Deploy OS using Remote ISO Image to Stage and Boot

Scripting WSMAN to Deploy OS using vFlash to Stage and Boot to ISO

Server Cloning with Server Configuration Profiles

Server Configuration Profile - XML File Structure (files )

Understanding the iDRAC Power State Management in Base Server Profile

Understanding the iDRAC Power State Management Profile

Using Microsoft Windows PowerShell CIM Cmdlets with Dell iDRAC

BIOS and UEFI

Enabling iSCSI Boot Under UEFI Boot Mode on 13th Generation PowerEdge Servers

BIOS POST Troubleshooting Guide for 13th Generation PowerEdge Servers(new for 13G)

BIOS Setup User Guide for 13th Generation PowerEdge Servers(new for 13G)

Defining a Secure Boot Policy (new for 13G)

Updating BIOS on Dell 12G PowerEdge Servers (iDRAC7 - 12G only) 

Updating BIOS on Dell 13G PowerEdge Servers (iDRAC8 - 13G only) (New for 13G)

Using Lifecycle Controller to Configure UEFI Secure Boot and OS Deployment(new for 13G)

Configuring BIOS and NIC Using RACADM through Dell iDRAC

OS deployment

Unattended Installation of Red Hat Enterprise Linux 7 Operating System on Dell PowerEdge Servers Using iDRAC With Lifecycle Controller(new for 13G)
Unattended Installation of Windows 2012 (12G and 13G)

Operating System Deployment in PowerEdge Servers

Operating Systems Deployment using iSCSI or FCOE LUN

Updates

Automatic Updates in Dell PowerEdge 12G servers  

Creating and updating iDRAC repository with Repository Manager

Lifecycle Controller Platform Update in Dell PowerEdge 12th Generation Servers

Lifecycle Controller with Dell Repository Manager

PowerEdge Updates with Repository Manager Best Practices Guide

Recommended methods of Updating Firmware on Dell Servers

Recommended Workflow for Performing Firmware Updates on PowerEdge Servers

Remote Firmware Update

Updating Firmware on PowerEdge Servers Using the iDRAC7 Web Interface

Using Dell Repository Manager to create a Bootable ISO and perform updates

Storage & PERC

Dell’s vFlash SD Flash Media Card – Better Endurance and Performance via Over-Provisioning

Understanding Real Time Storage Configuration for PERC9(new for 13G)
Managing Web Server Certificates on iDRAC (New for 13G)
Express Flash NVMe PCIe SSD Devie Monitoring, Inventory, and Configuration (New for 13G)
vFlash Overview

vFlash Partition Management 

vFlash using the Lifecycle Controller GUI

Security

Security with iDRAC8 (and 7)(New!)

Managing Web Server Certificates on iDRAC (New for 13G)

System Erase in Dell 13th Generation PowerEdge Servers (New for 13G)
New Security Features in Integrated Dell Remote Access Controller 7

Active Directory Integration & Certificates

Active Directory using Lifecycle Controller 

Integrate iDRAC8 with Active Directory (New for 13G)
Integrating iDRAC7 with Microsoft Active Directory

iDRAC Web Server Certificate Management