OpenManage Essentials FAQ - Systems Management - Wiki - Systems Management - Dell Community
Wikis - Title

OpenManage Essentials FAQ

Systems Management

Systems Management
Dell Systems Management Solutions: Dell OpenManage, iDRAC, Repository Manager, Microsoft SCCM, Chassis Managment Controller, and more

Systems Management - Wiki

OpenManage Essentials FAQ

Systems Management - Wiki

Last update: 16 Aug 2017

OpenManage Essentials 2.3 Frequently Asked Questions

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.

 

8. Q: Fresh Installation of OME 2.3 on Windows Server 2016 fails with the prereq missing message. Why?

A: Refer this link for more details around problem & available solutions: http://en.community.dell.com/techcenter/systems-management/f/4494/t/20018103

 

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

0
Comments
  • This is a great FAQ, but is there a way to run this command (vicfg-snmp.pl --username root --password <yourpassword> --server <yourserver> --hwsrc sensors) for the blade chassis itself? I have successfully run it for the individual blades but am still not getting alerts.

    Thanks in Advance for your help.