While Dell_OpenManage_Plugin_v2.0_Nagios_Core_A00.tar.gz package (available in Product Download section here) is officially supported on RHEL and SLES Linux operating systems as mentioned in the Systems Requirements section in product Installation Guide, it can also be deployed on other Linux distributions such as Ubuntu, CentOS, Scientific Linux, Oracle Linux etc.

The OpenManage Plug-in for Nagios-Core is Dell community supported for CentOS and Ubuntu platforms. For CentOS and Ubuntu related queries, use: Dell OpenManage Connections Forum

Learn

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.

21. Q: The devices in Device tree disappears during discovery. Why?
A: This happens when there are duplicate MAC addresses and is seen when virtual devices have MAC address that contain only 16 zeros. To fix this issue
1. Open dconfig.ini located in SysMgt\Essentials\configuration
2. Edit the following line PRIVATE_MAC_EXCLUDE_LIST to
PRIVATE_MAC_EXCLUDE_LIST=127.0.0.1,0.0.0.0,005345000000,33506F453030,505054503030,0000FFFFFFFF,204153594EFF,000000000000,00000000000000e0,020054554e01,204153594eff,0000000000000000
3. Save and restart OME services

Note: To edit dconfig file, the user should have administrative privileges on the OS. Also make a backup copy of dconfig.ini file before making changes.

22. Q: Why does the iDRAC or CMC display an “unknown” status after upgrading to the latest firmware version?
A: With the latest iDRAC or CMC firmware (iDRAC >= 2.40.40.40, M1000e CMC >= 5.2, FX2 CMC >= 1.4, VRTX CMC >= 2.2), TLS 1.1 is the default communication protocol. If your browser or operating system where OpenManage Essentials is installed does not support TLS 1.1 protocol, then the device displays an “unknown” status.

To resolve this issue, see “Step 2: Verifying Dell Management Consoles” in the following KB article: http://www.dell.com/Support/Article/us/en/19/SLN302365.

NOTE: Ensure the required registry updates are done either manually or using the “Easy Fix” described in the Microsoft support article - "Update to enable TLS 1.1 and TLS 1.2 as a default secure protocols in WinHTTP in Windows".

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 1278 (for package server port)
     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.

22 Q: System update via iDRAC is created. The task fails with error message "Error occured: The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again. " why?
A: To fix below error authentication level Basic has to be enabled for WinRM. 

Below is the expected configuration for winrm to work 

>winrm get winrm/config/client

Client
    NetworkDelayms = 5000
    URLPrefix = wsman
    AllowUnencrypted = false
    Auth
     Basic = true
     Digest = true
     Kerberos = true
     Negotiate = true
     Certificate = true
     CredSSP = false
    DefaultPorts
     HTTP = 5985
     HTTPS = 5986
TrustedHosts

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.

11. Q: I created an alert action which has the same name as existing Alert view filters. I re-launched OME and this the new alert action that was created is no longer seen in OME. Why?
A: This is the limitation of OME. Create an alert action with the different name than the existing alert view filters.

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.

12. Q: OME does not work when high availability features of SQL Servers are used. Why?
A: OME currently does not support high availability features within SQL Server.
Enabling the features on the database may cause OME to no longer function.

• SQL Server 2012+
https://msdn.microsoft.com/en-us/library/ms190202(v=sql.110).aspx

• SQL Server 2008+
https://msdn.microsoft.com/en-us/library/bb510414(v=sql.105).aspx

For large environments we recommend database backups scheduled within SQL Server.

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

Quick Links:

What is the Dell Chassis Management Controller (CMC)?

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

• Multiple servers
• Networking
• Storage

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

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

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

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

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

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

Platform CMC Specific Information

  ( top )

Quick Links:

DCIM Extensions Library Profile Collection

iDRAC8 (13th Generation PowerEdge - 2.40.40.40)

iDRAC8 (13th Generation PowerEdge - 2.30.30.30)

iDRAC8 (13th Generation PowerEdge - 2.20.20.20)

iDRAC8 (13th Generation PowerEdge - 2.10.10.10) 

iDRAC8 (13th Generation PowerEdge - 2.00.00.00 & 2.05.05.05)

iDRAC7 1.55.55 with Lifecycle Controller 2 1.4.0

iDRAC7 1.51.51 with Lifecycle Controller 2 1.3.0

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

CMC  for VRTX  2.1.0

CMC  for VRTX  1.3.0

CMC  for VRTX  1.2.5

CMC  for VRTX  1.0

CMC  for M1000e

iDRAC7 with Lifecycle Controller Technology   2.1.0

  iDRAC7 with Lifecycle Controller Technology 2.0.0

 iDRAC6 with Lifecycle Controller Technology  1.5.1

 iDRAC6 with Lifecycle Controller Technology  1.4.0

 iDRAC6 with Lifecycle Controller Technology  1.3.0

 iDRAC6 with Lifecycle Controller Technology  1.2.0

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

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

What is iDRAC?

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

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

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

Download the iDRAC8 with Lifecycle Controller Specification Sheet here.

( top )

 ( top )

  ( top )

iDRAC with Lifecycle Controller Technology Licensing Summary

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

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

General Overview

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

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

OpenManage Systems Management with iDRAC, iSM, & OMSA: selecting the right components for specific server management requirements(NEW - Jan 2016)

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

PowerEdge C6320 Power Capping (New for 13G)

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 April 2016)

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

RESTful Server Configuration with iDRAC REST API(NOV 2016) 

Dell PowerEdge Redfish API Overview

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

Dell Response to CVE-2016-2108 (OpenSSL) (18 May 2016)

Dell OpenManage Response to CVE-2015-7547, glibc overflow(March 2016)

Dell OpenManage Response to CVE-2016-0800, CVE-2016-0703 and CVE-2016-0704(March 2016)

Dell iDRAC Response to recent CVE notices(Dec 2015)

Security with iDRAC8 (and 7)(updated April 2016)

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

13G iDRAC8 Dell Test Event Notification Message Reference

Dell PowerEdge C6320 platform options and systems management (Oct 2015)

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 iDRAC SNMP-Gets Migration Guide (updated Aug '16)

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

Overview

In this technical article, we will cover the installation of Nagios-XI and Dell OpenManage Plug-In for Nagios-XI on a management node running CentOS. Following sections describe in detail the step-by-step instructions for installation and configuration of not only Nagios-XI and Dell OpenManage Plug-In but also the prerequisites that need to be installed and configured as well. These steps have been performed on the latest version of Nagios XI 64-bit virtual appliance running in VMware Workstation Player 12 on a Windows 7 Enterprise Edition host OS.

Step 1: Install Nagios XI Virtual Appliance

Nagios XI is available as a virtual machine (VM) image which can be downloaded from the official Nagios product download page. This is really useful as with a few additional configuration you can have a fully functional Nagios XI setup running and monitoring your data center or IT infrastructure in no time.

• Download VMware 64 bit virtual machine image from https://www.nagios.com/downloads/nagios-xi/. At the time of writing this article, the latest Nagios XI VMware 64 bit OVA image is running:
  • Linux OS: CentOS 6.8
  • Nagios XI v5.3.2 with Nagios-Core v4.1.1
• You will need a ESX Server, VMware Workstation, Player or VirtualBox to run the virtual machine. In this article, we are using VMware Workstation Player 12 running on a Windows 7 Enterprise Edition host OS to run the Nagios-XI VM.
• Please read the Virtual Machine Documentation to setup and configure the Nagios XI. We strongly recommend that you also go through a very useful article on Additional Configuration Steps after Deploying the Nagios-XI VM available on Nagios-Exchange.

Step 2: Install Pre-requisites for Dell OpenManage Plug-In for Nagios XI

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

• Perl Net-IP Module [mandatory]: provides functions to deal with IPv4/IPv6 addresses that are used by the OpenManage Plug-in’s check scripts for host and services discovery.
• Perl Net-SNMP Module [mandatory]: provides high-level interfaces to retrieve or update information on a remote host using the SNMP protocol and is used by the OpenManage Plug-in’s check scripts for SNMP communication with Dell devices.
• Perl Socket6 Module [optional]: provides glue routines to the various IPv6 functions that are used by the OpenManage plug-in for IPv6 host and services discovery and monitoring.
• Perl bindings for Open-WSMAN (WS-Management) [mandatory]: provides the Perl bindings for the Openwsman client API. Openwsman is an open source implementation of the WS-Management protocol and is used by OpenManage plug-in for the Agent-less monitoring of Dell devices using iDRAC.
• Perl SNMPTT (SNMP Trap Translator) Module [optional]: SNMP trap handler written in Perl for use with Net-SNMP / UCD-SNMP snmptrapd program. This module is an optional prerequisite and required for monitoring incoming SNMP traps from Dell devices.
• Dell RACADM (Remote Access Controller Admin) [optional]: command line tool that allows for remote or local management of Dell servers via the iDRAC. RACADM is required for monitoring component attribute information of Dell Chassis such as fan speed (RPM), amperage, voltage and power of PSUs and health of I/O module.

Install Perl Net-IP Module

Dell OpenManage Plug-In requires Perl Net-IP module version 1.26 or above to be installed. On CentOS 7, Perl Net-IP v1.26 can be installed using 'yum' package manager from the 'base' repository, whereas, on CentOS 6.8, the version of Perl Net-IP module that is available in the base respository is v1.25.

So, we will download and install the version 1.25 of Perl Net-IP module manually from source for CentOS 6.8.

Install Perl Net-SNMP Module

Dell OpenManage Plug-In requires Perl Net-SNMP module version 6.0.1 or above to be installed. Perl Net-SNMP module versions that is available on the update repository for both CentOS 7 and 6.8 is older than 6.0.1. So, like Net-IP module above, we will download and install the latest perl-Net-SNMP module manually from source.

Install Perl Socket6 Module

Dell OpenManage Plug-In requires Perl Socket6 module version 0.23 or later to be installed. On CentOS 6.8 as well as CentOS 7, Perl Socket6 v0.23 can be installed using yum package manager from the base repository. In this case, Nagios XI virtual machine already come pre-installed with perl Socket6 v0.23. However, if you still need to install it then please follow the instructions listed below:

Install Perl bindings for Openwsman

Perl bindings for Openwsman and all of its associated dependencies can be installed on both CentOS 7 and CentOS 6.8 using the yum package manager from the EPEL repository.

Install Perl SNMPTT (SNMP Trap Translator) Module

• SNMPTT can be installed using yum package manager from the EPEL repository on both CentOS 6.8 and CentOS 7. We will also install net-snmp-perl module since snmptt requires it.
  
  

  [root@localhost ~]# yum install snmptt [root@localhost ~]# yum install net-snmp-perl

• Edit snmptt.ini: Once installed, we will configure SNMPTT to run as a daemon process rather than a standalone process by editing the /etc/snmp/snmptt.ini configuration file. Let us also enable the DNS resolution and enhanced logging options.
  
  

  [root@localhost ~]# vi /etc/snmp/snmptt.ini # SNMPTT v1.4beta2 Configuration File [General] dns_enable = 1 net_snmp_perl_enable = 1 translate_log_trap_oid = 1 [Logging] stdout_enable = 1 log_enable = 1 log_file = /var/log/snmptt/snmptt.log log_system_enable = 1 log_system_file = /var/log/snmptt/snmpttsystem.log unknown_trap_log_enable = 1 unknown_trap_log_file = /var/log/snmptt/snmpttunknown.log [Debugging] DEBUGGING = 1 DEBUGGING_FILE = /var/log/snmptt.debug DEBUGGING_FILE_HANDLER = /var/log/snmptt/snmptthandler.debug

• Edit snmptrapd.conf: We will need to also modify the snmptrapd configuration file to set snmptt as the default SNMP trap handler.
  
  

  [root@localhost ~]# vi /etc/snmp/snmptrapd.conf # Add the following lines traphandle default /usr/sbin/snmptthandler disableAuthorization yes

• Configure both snmptt and snmptrapd services to start on OS boot:
  
  

  [root@localhost ~]# chkconfig snmptrapd on [root@localhost ~]# chkconfig snmptt on

• Restart both the snmptt and snmptrapd services.
  
  

  [root@localhost ~]# service snmptt start [root@localhost ~]# service snmptrapd start

Install Dell RACADM

RACADM can be installed from the Dell linux repository. In order to do this, we will setup the Dell linux repository first and then use the yum package manager to install the srvadmin-idrac7 package and all of its associated dependencies. After installation is complete, it is recommended to log out and then login so that $PATH variable is updated to use the racadm from command line.

Step 3: Install the Dell OpenManage Plug-In for Nagios XI

Now that we have successfully installed all the pre-requisites, it is time to get on with the installation of OpenManage Plug-In.

• Please download and install the Dell OpenManage Plug-In for Nagios XI as per the installation instructions provided in the Installation Guide packaged with the plugin zipped tarball.
• We also recommend that you go through post-installation section in the Installation Guide to configure the SNMP alerts / traps and Alert Knowledge Base (KB) articles.

Unlike the traditional ESX software, the ESXi software does not have a service console. It helps reduce the installation footprint of the software and can allow the hypervisor to be directly installed on the system’s internal flash storage or a USB key.

At the moment I am investigating moving to ESXi from ESX. After resolving the DSET issue, I was then faced with the management of the ESXi hosts, currently the full fat ESX hosts have the Dell open management agent installed on them and SNMP configured. This allows the Dell management server to keep track of the underlying hardware and report any hardware issues or firmware updates.

But what happens with ESXi 4.0 and the removal of the service console? Earlier with ESXi 3.5, OpenManage components were integrated with the downloadable Dell ESX3i ISO image but from ESXi 4.0 onwards, VMware introduced a new concept called vSphere Installation Bundle (VIB). This allows the end users to download VIB files and install it directly into ESXi 4.0. Dell is now posting their OpenManage component as a VIB on support.dell.com.

To help reduce the system footprint and to simplify deployment, the ESXi software does not have a traditional service console management interface where Dell OpenManage agents are installed. Instead, to provide the required hardware manageability, VMware has incorporated the standard Common Information Model (CIM) management profiles into the ESXi software.

The CIM framework is an open standard framework that defines how managed hardware elements in a system are represented.The CIM framework consists of CIM providers developed by hardware vendors to enable monitoring and managing of the hardware device. By representing the hardware elements using standard CIM, ESXi provides any management tool (that implements the same open standards) the ability to manage the system.

The installation manual takes you through the install of this VIB using the RCLI and the vihostupdate command, but if you are like me and wish to automate these tasks you could use the following PowerCLI script to install the VIB. This script not only installs the VIB, but will also setup SNMP and the Advanced Configuration setting which tells ESXi to use the installed Dell components to report on the hardware via CIM.

# Set the following variables
$ESXHost = "testesx4i"
$SNMPCommunity = "public"
$SNMPTargetHost = "192.168.0.50"
$FolderName = "oem-dell-openmanage-esxi_6.2.0-A00"
$DellOMSA = "c:\temp\$FolderName"

Connect-VIServer $ESXHost
Write "Retriving $ESXHost object"
$VMHostObj = Get-VMHost $ESXHost
Write "Checking for OMSA install files"

if (-Not (Test-Path "$DellOMSA\metadata.zip")){
Write "$DellOMSA does not exist, please make sure this is the OMSA zip file extracted contents."
Exit
} Else {
Write "Install files found"
}
Write "Copying OMSA client to the host datastore"
$ds = $VMHostObj | Get-Datastore | Select -first 1
Copy-DatastoreItem $DellOMSA $ds.DatastoreBrowserPath -Recurse

Write "Installing Dell OMSA"
$DSName = $ds.Name
$InstalledOMSA = $VMHostObj | Install-VMHostPatch -HostPath /vmfs/volumes/$DSName/$FolderName/metadata.zip

Write "Enabling CIM OEM Providers"
Set-VMHostAdvancedConfiguration -Name UserVars.CIMOEMProvidersEnabled -Value 1 | Out-Null

Write "Removing Install files"
$urlPath = "https://" + $esxhost + "/folder/" + $FolderName + "?dcPath=ha-datacenter&dsName=" + $dsName
$fileMgr = Get-View (Get-View ServiceInstance).Content.FileManager
$fileMgr.DeleteDatastoreFile_Task($urlPath,$null)

If ($InstalledOMSA.NeedsRestart -eq $true){
$Reboot = Read-Host "A reboot is needed type YES to reboot now or press enter to complete the install:"
If ($Reboot -eq "YES"){
Write "Putting host into maintenance Mode"
Set-VMHost $VMHostObj -State Maintenance -Confirm:$false | Out-Null
Write "Rebooting host now"
Restart-VMHost $VMHostObj -Confirm:$false | Out-Null
} Else {
Write "A reboot is needed before the DELL OMSA will work correctly"
}
}

If ((Get-VMHostSnmp).ReadOnlyCommunities -ne $SNMPCommunity){
Write "Setting SNMP Configuration"
$VMHostObj | Get-VMHostsnmp | Set-VMHostSnmp -TargetHost $SNMPTargetHost -TargetCommunity $SNMPCommunity -AddTarget -ReadOnlyCommunity $SNMPCommunity -Enabled:$true
}

Write "OMSA Install Completed"

To use the above script:

• Install PowerShell v2 and PowerCLI 4.0u1 at least.
• Download the latest version of the VIB (currently 6.2.0 here).
• Extract the downloaded zip to a folder with the same name.
• Adjust the Foldername and DELLOMSA variables to reflect the path and folder name.
• Alter the ESXHost variable with the hostname or IP address of the server you will be installing to.
• Alter the SNMPCommunity variable to your settings.
• Alter the SNMPTargetHost variable to your setting (ITA server).
• Run the script from a PowerCLI prompt.

The hardware management data is provided to management applications using CIM Extensible Markup Language (XML) as well as WS-Management (WSMAN).
The VMware Infrastructure (VI) client provides hardware health status of various hardware devices. The VI client uses CIM XML to read hardware information provided by the CIM providers. Each of the monitored hardware devices are listed along with the health status.

Once this has been installed, you will still not be able to access the normal OMSA Web site which is accessed via https://<hostname>:1311/ if you do want to access this you will need to install the ‘Dell OpenManage Server Administrator Managed Node’ onto a Windows or Linux box which acts as a proxy and relays the information back to the webpage as below:



You will also be able to discover the host in your Dell OpenManage IT Assistant (ITA) using SNMP, but it will not have the full functionality which was offered in the full fat version of ESX with OMSA installed. You can add limited network discovery and health monitoring by using the DRAC card and allowing ITA to find this, the below diagram gives an overview of ESXi management for Dell systems:


So the conclusion is just to keep in mind that the management interfaces which you may use at the moment for Dell servers to report on hardware and health performances may have changed and this will require your internal processes and monitoring to be adapted when adopting ESXi.

For further information on Dell system management for ESXi, please see this document.

For more PowerCLI and PowerShell scripts for your VMware environment, visit my blog at the following address: http://virtu-al.net

Contents: Download - Documentation - Videos - Whitepapers - Discussion Forum

Overview

Dell OpenManage Plug-in for Nagios XI provides capabilities for monitoring 12th and later generations of Dell PowerEdge servers through an Agent-Freemethod using Integrated Dell Remote Access Controller (iDRAC) with Lifecycle Controller (LC), Dell Modular Infrastructure and Dell Storage devices directly from within the Nagios XI 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.

What are the Key Features?

• An automated and guided Dell Configuration Wizard for discovery and monitoring configuration for 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 of 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 Overall Health including health of the following components of the supported Dell devices:

  • CPU, Memory, Physical Disk, Virtual Disk, Controller, Fan, Power Supply, Battery, Temperature Probe, Voltage Probe, Network Device, SD Card, Amperage Probe, Intrusion and FC NIC of the Dell PowerEdge Servers

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

  • 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 and alert based on days remaining for warranty expiration

• SNMP alerts monitoring 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 1:1 and 1:Many web consoles from Nagios XI to perform further troubleshooting, configuration, or management activities:

  • Dell iDRAC web console

  • Dell Chassis Management Controller (CMC) Console

  • Dell EqualLogic Group Manager Console

  • Dell Compellent Storage Manager Console

Business Benefits

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

• This eases the administrator’s burden by having a single pane of glass to monitor the heterogeneous hardware platforms, which eventually improve the operational efficiency and flexibility in data center management

• 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

Licensing Details

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

Download

• Dell OpenManage Plug-in for Nagios XI

Documentation

Technical Article & Wikis

• Installation of Dell OpenManage Plug-In for Nagios XI on CentOS (NEW)
• Installation of Dell OpenManage Plug-In for Nagios Core on Ubuntu OS (NEW)
• Agent-free Monitoring of Dell PowerEdge 12G Servers in Nagios Core and Nagios XI Whitepaper

Videos

• Overview of Dell OpenManage Plug-in for Nagios XI

(Please visit the site to view this video)

• Installation of Dell OpenManage Plug-in for Nagios XI 

(Please visit the site to view this video)

Welcome to Dell Repository Manager

Dell Repository Manager (DRM) is an application that allows IT Administrators to easily manage system updates. Dell Repository Manager provides a searchable interface used to create custom software collections known as bundles and repositories of Dell Update Packages (DUPs).

These bundles and repositories allow for the deployment of multiple firmware updates at once. 

A Dell Update Package (DUP) is a self-contained executable in a standard package format that updates a software element on a Dell server such as the BIOS, a device driver, firmware, and other similar software updates.

Additionally, Dell Repository Manager makes it easier to locate specific updates for a particular platform, which saves time.

See a screenshot of the Data Center Version GUI

 How does Dell Repository Manager Work?

DRM connects to Dell's online catalog of updates that contains information on the available Dell Update Packages (DUPs). Once you have selected your updates, Dell Repository Manager downloads the specific file(s) you have requested.

Repository Manager can also compare differences between two repositories at both the bundle and component level. It allows you to create deployment tools using your custom repository. Repository Manager is available for Dell Data Center (Server, Storage, Networking) and Dell Enterprise client products. The Data Center version can create and manage repositories for Dell PowerEdge servers, select EquaLogic, PowerVault & Compellent storage as well as select PowerConnect and Force10 networking switches.  The Dell Client version manages updates for Dell Latitude, Precision Workstation and OptiPlex client systems.

Dell Repository Manager integrates with Dell systems management products such as Dell OpenManage Essentials console and the Dell Management Plug-in for VMware vCenter. Dell Repository Manager automates creation of custom repositories by reading inventory information from these consoles and creating of a set of updates that is newer than what is currently installed.  

What's New + Downloads

  ( top )

( top )

  ( top )

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

This video gives an overview of what the integration can for your an administrator.

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?

December 9th, 2016 - v3.1.1 

•    Public hotfix for the communication layer in OMIVV to support TLS 1.1 and 1.2
•    Hotfix only; requires OMIVV v3.1 initial installation, then an RPM update.
•    Supports communication with default iDRAC 2.40.40.40 TLS updates
•    Supports communication with default CMC FX 1.40, M1000e 5.20, and VRTX 2.20 updates

For installation of the hotfix, please reference Upgrading OpenManage Integration Plugin from 3.0 version to the current, page 14, of the Install Guides for step by step instruction.

General 3.1 enhancements:

•    Support for vSphere v5.5 Update 3, v6.0 Update 1, and v6.0 Update 2
•    Support for the PowerEdge R230, R330, T130, and T330
•    Support for 64bit firmware updates
•    Support for non-admin privileged registration

OMIVV Features

OMIVV Downloads

New! 3.1
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.1
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 vCenteron Dell.com

What is Catalog?

Biz Client Catalog

Biz Client Catalog is an aggregation of all Dell Update Packages’ (DUP) metadata carried for Dell Optiplex, Dell Latitude, Dell Precision and Dell Tablet brands of systems. These are utilized through end-user products like Dell Command Update/ Dell Client System Update, Dell Repository Manager and Software Centre Configuration Manager / Software Center Update Publisher.

Biz Client Catalogs are released every fortnight on the 2nd and 4th Tuesday of every month.

Enterprise Catalog

Enterprise Catalog is an aggregation of all Bundles and Dell Update Packages’ metadata carried for Dell PowerEdge, Dell PowerVault and Dell EqualLogic Servers

Enterprise Catalogs are released every month on the 2nd and 4th Friday

What's New + Downloads

 What is Dell Update Package?

A Dell Update Package (DUP) is a self-contained executable in a standard package format that updates a single software element on the system. Using DUPs, you can update a wide range of system components simultaneously and apply scripts to similar sets of Dell systems to bring the system components to the same version levels.

You can use DUPs to:

• Apply an individual update to a system by using an interactive command line interface (CLI).
• Install device drivers in interactive and non-interactive modes.
• Execute multiple updates on the system by using a script comprised of non-interactive commands that you write using the CLI feature.
• Leverage the scheduling of your operating system and software distribution utilities to apply updates remotely to any number of systems.

DUPs are available for the following software components:

• System BIOS
• System firmware, also known as the Embedded Systems Management (ESM) firmware
• Network firmware and drivers
• Remote Access Controller (RAC) firmware
• RAID controller firmware and device drivers
• Software RAID 3.0 (S130) driver
• Hard-disk drives (HDDs), Serial Advanced Technology Attachment (SATA), Serial Attached SCSI (SAS), and solid-state drives (SSDs)
• Lifecycle Controller
• Dell Diagnostics and Driver Pack
• Backplane and Expander
• Tape drives
• Enclosures (MD12xx, MD14xx)
• OS Collector
• Chipset Drivers

 What's New + Downloads

DUP supports the Dell PowerEdge FD332 servers.

Documentation

 ( top )

Video Demos

 ( top )

 White Papers & Best Practices

 ( top )

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

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

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

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

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

Supported Platforms:

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

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.

Remote iDRAC hard reset

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

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

iDRAC access via Host OS (Experimental Feature)

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

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

In-band support for iDRAC SNMP alerts

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

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

Links:

Linux download v2.4

Windows download v2.4

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

This is a placeholder for Redfish documentation.

test

What is DELL EMC System Update (DSU)

Dell System Update (DSU) ensures that the Dell systems are up-to-date with the latest BIOS, firmware, and software. DSU contains

• OpenManage Server Administrator.
• BIOS and firmware updates for server platforms

Getting DSU

DSU is available as a Dell Update Package (DUP).  DSU DUP

DSU RPM for RHEL/SLES is also available.  DSU RPM

Supported Operating Systems

Linux (RHEL and SUSE)

• Red Hat Enterprise Linux 6.8 (x86_64)
• Red Hat Enterprise Linux 7.2(x86_64)
• SUSE Linux Enterprise Server 11SP4 (x86_64)
• SUSE Linux Enterprise Server 12SP1 (x86_64)

Note:  "rebuilt" versions of the above such as CentOS or ScientificLinux and community distros like Fedora and OpenSUSE are not tested with this repository.

Microsoft Windows

• Microsoft Windows Server 2008 R2 (x86_64)
• Microsoft Windows Server 2012(x86_64)
• Microsoft Windows Server 2012 R2 (x86_64)
• Microsoft Windows Server 2016 (x86_64)

Support for Ubuntu operating systems

Starting with DSU 1.4, support for Ubuntu operating systems is pre-enabled  and the support is limited. All the DSU commands may function as usual without any issues. For more information
on the catalog that has the updates for Ubuntu operating system, refer Ubuntu Catalog

• Ubuntu LTS 14.04
• Ubuntu LTS 16.04
  

Note:  Support for Ubuntu is pre-enabled only on 12th and 13th generation of PowerEdge systems.

What is Catalog?

DELL EMC PowerEdge Server Catalogs

DELL EMC PowerEdge Server Catalogs are an aggregation of all Bundles and Dell Update Packages’ metadata carried for Dell EMC PowerEdge 11G, 12G and 13G servers, as well as select Dell PowerVault and Dell EqualLogic Servers

DELL EMC PowerEdge Server Catalogs are refreshed every month on the 2nd and 4th Friday.

DELL EMC Online Catalog:  General catalog that is used by many DELL EMC tools such as DELL EMC Repository Manager, OpenManage Essentials, ASM and other tools.

DELL EMC LC Catalog:  Same content as the DELL EMC Online Catalog, but saved in .gz format for use with DELL EMC Lifecycle Controller

DELL EMC SDP Catalog:  Same content as the DELL EMC Online Catalog, but saved in the format required my Microsoft SCUP.

**Note:  Dell PowerEdge 9G and 10G servers have reached end of support life, new catalogs do not carry content for these platforms.

What's New + Downloads

Online Catalog

This wiki post is written by Shine KA and Hareesh V from Dell iDRAC team

Introduction

     iDRAC includes a Web server that is configured to use the industry-standard SSL security protocol to transfer encrypted data over a network. Built upon asymmetric encryption technology, SSL is widely accepted for providing authenticated and encrypted communication between clients and servers to prevent eavesdropping across a network. iDRAC Web GUI, Remote Racadm, WSMAN and VMCLI uses SSL certificate for communication.

     The encryption process provides a high level of data protection. iDRAC employs the 128-bit SSL encryption standard, the most secure form of encryption generally available for Internet browsers.

     iDRAC Web server has a Dell self-signed unique SSL digital certificate by default. You can replace the default SSL certificate with a certificate signed by a well-known Certificate Authority (CA). A Certificate Authority is a business entity that is recognized in the Information Technology industry for meeting high standards of reliable screening, identification, and other important security criteria. Examples of CAs include Thawte and VeriSign. This document will describe different methods supported by iDRAC for replacing default self-signed certificate of iDRAC.

1. Uploading SSL/Signing Certificate to iDRAC

There are three different ways where you can upload custom SSL certificate to iDRAC. We can user iDRAC WEB GUI, Racadm or WSMAN interface for uploading SSL certificate to iDRAC.

• Uploading SSL Certificate to iDRAC using CSR created from iDRAC
• Uploading SSL Certificate to iDRAC using private / public key
• Uploading Signing certificate to iDRAC

Note : iDRAC will restart and will not be available for some time after upload.

1.1.  Uploading SSL Certificate to iDRAC using CSR method

     This method will use CSR (Certificate Signing Request) created from iDRAC for uploading SSL certificate to iDRAC. You need to sign the CSR file created from iDRAC and upload it back to iDRAC. iDRAC will support only certificate in Base 64 format. You can use Racadm or Web GUI interface for configuring SSL on iDRAC using this method. Before creating CSR from iDRAC, you can specify following certificate properties in iDRAC. These properties will be used by iDRAC for creating CSR.

CommonName

OrganizationName

OrganizationUnit

LocalityName

StateName

CountryCode

EmailAddr

KeySize

Note: Key size can be configured only through racadm

Using Racadm

            You need to follow below four steps if you want to upload SSL certificate to iDRAC using racadm

Step 1: Configure Certificate properties on iDRAC

If you have iDRAC7 with 1.30.30 or above firmware or iDRAC8, you can run following racadm commands also to configure certificate properties.

Configuring the iDRAC security CSR key size

The command that is used to configure this property is:

racadm set iDRAC.Security.CsrKeySize <Key size>

Configuring the iDRAC security CSR common name

The command that is used to configure this property is:

racadm set iDRAC.Security.CsrCommonName <common name>

Configuring the iDRAC security CSR organization name

The command that is used to configure this property is:

racadm set iDRAC.Security. CsrOrganizationName <Organization Name>

Configuring the iDRAC security CSR organization unit

The command that is used to configure this property is:

racadm set iDRAC.Security. CsrOrganizationUnit <Organization Unit>

Configuring the iDRAC security CSR Locality Name

The command that is used to configure this property is:

racadm set iDRAC.Security. CsrLocalityName <Location>

Configuring the iDRAC security CSR State Name

The command that is used to configure this property is:

racadm set iDRAC.Security. CsrStateName <State Name>

Configuring the iDRAC security CSR Country Code

The command that is used to configure this property is:

racadm set iDRAC.Security. CsrCountryCode <Country Code>

Configuring the iDRAC security CSR Email Address

The command that is used to configure this property is:

racadm set iDRAC.Security. CsrEmailAddr<Email Address>

Once all the Sub-Attributes of the group “iDRAC.Security” had been configured, you can run below command to verify the setting

 If you have iDRAC6 or  iDRAC7 with firmware level less than 1.30.30 you can run following Racadm command to configure certificate properties. These commands can be run from Local, Remote or Firmware Racadm.

Configuring the iDRAC security CSR Key Size

The command that is used to configure this property is:

racadm config -g cfgRacSecurity –o cfgRacSecCsrKeySize <Key size>

Configuring the iDRAC security CSR CommonName

The command that is used to configure this property is:

racadm config -g cfgRacSecurity –o cfgRacSecCsrCommonName <Common Name>

Configuring the iDRAC security Organization name

The command that is used to configure this property is:

racadm config -g cfgRacSecurity –o cfgRacSecCsrOrganizationName <Organisation Name>

Configuring the iDRAC security CSR Organization Unit

The command that is used to configure this property is:

racadm config -g cfgRacSecurity –o cfgRacSecCsrOrganizationUnit <Organisation Unit>

Configuring the iDRAC security Locality name

The command that is used to configure this property is:

racadm config -g cfgRacSecurity –o cfgRacSecCsrLocalityName <Location>

Configuring the iDRAC security State name

The command that is used to configure this property is:

racadm config -g cfgRacSecurity –o cfgRacSecCsrStateName <State Name>

Configuring the iDRAC security CSR Country Code

The command that is used to configure this property is:

racadm config -g cfgRacSecurity –o cfgRacSecCsrCountryCode <Country Code>

Configuring the iDRAC security CSR Email Address

The command that is used to configure this property is:

racadm config -g cfgRacSecurity –o cfgRacSecCsrEmailAddr <Email Address>

Once all the Sub-Attributes of the group “cfgRacSecurity” had been configured, you can run below command to verify the setting

Step 2: Create and Download CSR from iDRAC

You can run the following command to generate and download CSR from iDRAC. This command is only supported from Local and Remote Racadm

The sslcsrgen command has the following option:

Racadm sslcsrgen –g –f < filename.txt>

-g: Generate new Certificate signing request(CSR).

-f: Specifies the file which will hold the CSR.

Step 3: Sign the CSR downloaded from iDRAC using any third party certificate authority

Sign the CSR file downloaded from iDRAC using any third party certificate authority.

Step 4: Upload signed certificate back to iDRAC

Once you have signed certificate, you can upload signed certificate back to iDRAC using following Racadm command. This command is only supported from Local and Remote Racadm. Once you upload the certificate, iDRAC will reboot and will not be accessible for some time.

Using WEBGUI

Step 1: Configure Certificate properties on iDRAC

To upload certificate using CSR you need to first configure certificate properties on GUI. Login to iDRAC and traverse to iDRAC Settings -> Network -> SSL page and select “Generate Certificate Signing Request (CSR)” option for creating CSR. On “Generate Certificate Signing Request (CSR)” page update all fields with certificate information

Step 2: Create and Download CSR from iDRAC

To generate and save CSR from iDRAC click on the “Generate” button and save the file

Step 3: Get CSR signed by using any third party certificate authority

Get the CSR file got from iDRAC signed by any third party certificate authority.

Step 4: Upload signed certificate back to iDRAC

You can traverse to iDRAC Settings -> Network -> SSL page to upload Server Certificate. Select “Upload Server Certificate” option to upload the certificate. Browse the signed certificate file and click on Apply to upload signed certificate. iDRAC will reset once certificate is uploaded

1.2.  Uploading SSL Certificate to iDRAC using Key Pair

     In this method you need to create private key and signed certificate with public key from a CA. Once key and certificate is created you can use Racadm, WSMAN or Web GUI interfaces to upload the key and certificate to iDRAC.

Using Racadm

In Racadm first you need to upload private key to iDRAC. This private key should not have a passphrase. Once you upload the private key you can upload the corresponding certificate using Racadm.

Step 1: Uploading private key to iDRAC

      You can run “sslkeyupload” racadm command to upload private key to iDRAC. This command is supported from Local and Remote Racadm interface.

Step 2: Uploading certificate to iDRAC

You can run “sslcertupload” racadm command to upload the certificate to iDRAC. This command is supported from Local and Remote Racadm interface.

Using Web GUI

Using Web GUI you cannot upload private key. So you need to first upload the key using racadm as mentioned in above step. Once private key is uploaded you can use iDRAC Web GUI to upload certificate. You can login to iDRAC and traverse to iDRAC Settings -> Network -> SSL page to upload Server Certificate. Select “Upload Server Certificate” option to upload the certificate. iDRAC will reset once certificate is uploaded

Using WSMAN

For uploading certificate using WSMAN you first need to create base64 format PKCS file with certificate and private key. This private key should not have a passphrase. Once private key and certificate is created follow below steps for uploading certificate to iDRAC.

Step 1: Create a base64 format PKCS file with private key and certificate

In this step you will create a PKCS file of private key and certificate in base 64 format using. You need to use openssl commands to achieve this.

1. 1. Combined private key and certificate to a single file

      Use Linux cat command to combine custom certificate and private key without pass phrase to a single file

   2. Create PKCS file

      Use Linux openssl pkcs command to create pkcs12 file from certificate and private key file. Provide a password when asked.

   3. Convert PKCS file to Base 64 format

1. 1. “pkcsCertificateb64.p12” is the base64 encoded PKCS file. Content of this file will be used while uploading certificate using WSMAN.

Step 2: Upload base 64 PKCS certificate to iDRAC

            Now you need to upload the base 64 format PKCS certificate to iDRAC using WSMAN command. For this we will create one xml file with certificate data then upload the file to iDRAC using WSMAN command

1. 1. Create XML file with certificate details

In this step you need to create an xml file with certificate details. Refer screenshot below for sample xml file

Note: Type need to be “server”. Between <p:PKCS12> and </p:PKCS12> Copy content of base 64 PKCS certificate file obtained in Step 1c. You need to mentioned PKCS file password in PKCS12pin field

b.  Upload certificate to iDRAC using WSMAN

Run below wasman command to upload certificate to iDRAC.

Note: “uploadCertificate.xml” is the file with certificate content as shown in previous step 2a

1.3.  Uploading Signing Certificate to iDRAC

This feature is only supported on iDRAC7 from 1.30.30 firmware onwards. Using this method, you can make sure every iDRAC have a unique signed SSL certificate. This can be achieved without creating and uploading separate unique signed certificate to iDRAC. You need to upload signing certificate from CA to each iDRAC. iDRAC will create a certificate using iDRAC DNS name or host name (if DNS name is not available) or IPv4 address (if DNS name or hostname is not available) as common name. This certificate will be signed by uploaded signing certificate.

Signing certificate need to be in PKCS12 format and PKCS file should have private key as well. PKCS file can be with or without pass phrase.

Using Racadm

            You need to use “sslcertupload” racadm command to upload signing certificate to iDRAC. This command is only supported from Local or Remote racadm.

Upload signing certificate without pass phrase     

Upload signing certificate with pass phrase

Using Web GUI

You can upload signing certificate using iDRAC Web GUI also. PKCS#12 password is an option field and is only required if the PKCS file have a password

2. Viewing SSL/Signing certificate on iDRAC

Once custom SSL or signing certificate is uploaded to iDRAC you can use Racadm and iDRAC GUI interface to check currently uploaded SSL and singing certificate

2.1.  Viewing SSL certificate on iDRAC

To view SSL certificate on iDRAC you can use racadm or web GUI. You can use this method to view SSL certificate regardless of method used for uploading the certificate.

Using Racadm

You can use racadm sslcertview command to view iDRAC SSL certificate. This command can be executed from Local, Remote or Firmware racadm

Using Web GUI

You can login to iDRAC and traverse to iDRAC Settings -> Network -> SSL page to view current iDRAC SSL Certificate.

2.2.  Viewing Signing certificate on iDRAC

Viewing signing certificate on iDRAC is only supported through web GUI.

Using Web GUI

You can login to iDRAC and traverse to iDRAC Settings -> Network -> SSL page to view signing Certificate. Signing certificate information will be shown under “Custom SSL Certificate Signing Certificate” section.

3. Downloading SSL/Signing certificate from iDRAC

Once custom SSL or signing certificate is uploaded to iDRAC you can download these certificate back from iDRAC. You can use Racadm Web GUI and WSMAN interface to download certificates.

3.1.  Downloading SSL certificate from iDRAC

You can use Racadm and Web GUI to download SSL certificate from iDRAC.

Using Racadm

You can use racadm sslcertdownload command to download SSL certificate from iDRAC. This command is only supported from Local and Remote Racadm.

Using Web GUI

You can login to iDRAC and traverse to iDRAC Settings -> Network -> SSL page and use “Download SSL Certificate” option to download SSL certificate from iDRAC.

3.2.  Downloading Signing Certificate from iDRAC

You can use Racadm, Web GUI and WSMAN interface to download “Custom SSL Certificate Signing Certificate” from iDRAC.

Using Racadm

You can use racadm sslcertdownload command to download “Custom SSL Certificate Signing Certificate” from iDRAC. This command is only supported from Local and Remote Racadm.

Using Web GUI

You can login to iDRAC and traverse to iDRAC Settings -> Network -> SSL page and use “Download Custom SSL Certificate Signing Certificate” option to download “Custom SSL Certificate Signing Certificate” from iDRAC.

Using WSMAN

You can also use WSMAN to download Custom SSL Certificate Signing Certificate from iDRAC. You need to use “DCIM_LCService.ExportCertificate” method to download certificate from iDRAC. This method will download Custom SSL Certificate Signing Certificate to CIFS or NFS share

Run below WSMAN command to export iDRAC Custom SSL Certificate Signing Certificate to CIFS share

winrm I ExportCertificate cimv2/2/root/dcim/DCIM_LCService?__cimnamespace=root/dcim+SystemCreationClassName=DCIM_ComputerSystem+SystemName=DCIM:ComputerSystem+CreationClassName=DCIM_LCService+Name=DCIM:LCService -u:root -p:calvin -r:https://10.94.195.107/wsman -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic @{Type="2";IPAddress="10.94.194.31";ShareName="/nfs";ShareType="0"}

This command will initiate Custom Certificate download process and return Job ID.

Run below WSMAN command to export iDRAC Custom SSL Certificate Signing Certificate to NFS share

winrm I ExportCertificate cimv2/2/root/dcim/DCIM_LCService?__cimnamespace=root/dcim+SystemCreationClassName=DCIM_ComputerSystem+SystemName=DCIM:ComputerSystem+CreationClassName=DCIM_LCService+Name=DCIM:LCService -u:root -p:calvin -r:https://10.94.195.107/wsman -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic @{Type="2";IPAddress="10.94.194.31";ShareName="Share";ShareType="2";Username="Share Username";Password="Share Password"}

This command will initiate Custom Certificate download process and return Job ID.

 Run below WSMAN command to check job status

4. Deleting SSL/Signing certificate from iDRAC

Once custom SSL or signing certificate is uploaded to iDRAC you can delete this certificate to load iDRAC default certificate.

4.1.  Deleting Custom SSL certificate from iDRAC

Using Racadm

You can use racadm sslresetcfg command to delete custom SSL certificate and load default self-signed certificate back to iDRAC. This command can be executed from Local, Remote and Firmware racadm.

4.2.  Deleting Signing Certificate from iDRAC

You can delete “Custom SSL Certificate Signing Certificate” using racadm or Web GUI. Once you delete custom SSL certificate signing certificate, default self-signed certificate will be loaded on iDRAC.

Using Racadm

You can run racadm sslcertdelete command to delete “Custom SSL Certificate Signing Certificate” This command can be executed from Local, Remote and Firmware racadm. After deleting Custom SSL Certificate Signing Certificate iDRAC will reboot to apply the setting.

Using WebGUI

You can login to iDRAC and traverse to iDRAC Settings -> Network -> SSL page and use “Delete Custom SSL Certificate Signing Certificate” option to delete “Custom SSL Certificate Signing Certificate” from iDRAC.

Dell offers a comprehensive range of software based, hardware based and appliance based server Systems Management products designed to manage your datacenter and fit any IT department's needs. This page is your starting point to learn about Dell products such as OpenManage, KACE, DMC, iDRAC, Lifecycle Controller, and more.

To discover more about each Dell Systems Management product and to find out which one is the right fit for you, click on one of the links below or read the Introduction to Dell Systems Management.

If you need help knowing finding out where to start based on your needs, consult the Dell Systems Management Advisor

Dell Systems Management Consoles and Products

The following products provide the ability to easily monitor, manage, update, and deploy to servers in your datacenter from a single console. To learn more about the advantages of each Dell hardware / datacenter systems management product, click on the links below:

• Dell OpenManage Systems Management Suite
• Dell KACE Systems Management Appliances
• Dell OpenManage Essentials
• Dell OpenManage Power Center

Dell Embedded Systems Management

The following are embedded on a Dell server motherboard or in a Dell Blade Chassis. The DRAC and LifeCycle Controller are hardware components that allow for agentless out-of band monitoring, management, update, and firmware backup of your Dell server. The CMC goes one level higher up than the DRAC and gives Adminis the ability to monitor multiple blade servers and shared components in a Dell blade chassis.

• Chassis Management Controller (CMC) - Blades Management
• Dell Remote Access Controller (DRAC)
• Dell Lifecycle Controller

Dell Client Systems Management

In addition to products for servers, Dell provides tools to manage Dell workstations and laptop systems.

• Dell KACE Systems Management Appliances
• Dell Enterprise Client on Dell TechCenter
• Dell Client System Update
• Dell Repository Manager for Clients

Dell Cloud \ Virtualization Systems Management

Dell has Systems Management products that can help you both manage and scale physical systems and virtual resources in the cloud (including servers, storage, networking and hypervisors). The Dell Management Plug-In for VMware vCenter allows you to manage both physical and virtual machines through the vSphere console.

Dell Active System Manager provides an intuitive, automated, template-based experience for the deployment, orchestration and lifecycle management of physical and virtualized converged infrastructure. 

• Dell Management Plug-In for VMware vCenter
• Dell Active System Manager