Release Notes
SNMP connectivity from Essentials may fail if the SNMP ports on the management station and managed system are
different. If some management applications change the default SNMP port, it could lead to SNMP connectivity failure
from Essentials.[175442]
If you manually change the host name of the server which has already been discovered in OpenManage Essentials, then
duplicate entries appear in the device list corresponding to the IP address of the device whose host name has been
changed. The new host name also corresponds to same IP address and the duplicate entry of the earlier host name is
not automatically deleted. OpenManage Essentials displays both the new and the old host names.[247879]
If a server is discovered using both SNMP and IPMI (in-band and out-of-band IP addresses respectively) Essentials will
correlate the two and display a single device under the "Servers" group in the devices view. If IPMI is then disabled, a
new device would appear under the "Unknown" group, corresponding to the out-of-band interface. The device details
under the Servers group continue to display the out-of-band IP address as well. After you re-enable IPMI, the device
under Unknown group can be removed by right-clicking it and selecting "Remove". [262869]
When a "Power Monitoring Capable" Server is discovered through the CIM protocol, on the "Device Details" screen,
Essentials may display "No" under the "Power Management" column in "Power Supply Information" section. To display
the correct information, discover the server with either SNMP, or both SNMP and CIM protocols. [300080]
Even after performing inventory on the discovered Linux servers 'N' number of times, the Linux servers are still listed
under Non-Inventoried systems'. To resolve this issue perform the following steps:
ForRedHatEnterpriseLinux5.5,SUSELinuxEnterpriseServer10,SUSELinuxEnterpriseServer11
1.
Mount the OpenManage Server Administrator dvd in the Linux server
2.
Install 'srvadmin-cm' rpm.
3.
Restart OpenManage Server Administrator services.
4.
Ensure OpenManage Server Administrator inventory collector is working fine
(Run ./invcol -outc=/home/inv.xml from /opt/dell/srvadmin/sbin/invcol location)
5.
Reinventory the linux server in OpenManage Essentials.
6.
Now your the Linux server is either listed under 'Compliant sytems' or 'Non-Compliant systems'.
An exception might be seen in the OpenManage Essentials Console, when a discovered virtual machine of a Vmware
Classic ESX server is selected from the "Unknown" node in the "All Devices" tree.[516274]
The RAC Console application launch point is available when SNMP protocol is used to discover the DRAC (Dell Remote
Access Controller) devices.[515308]
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.
When you create a custom group you have the ability to select a pre-defined device search query or the ability to
select individual devices and groups to form your newly created custom group.
If you select a device search query as your basis for your custom group content and you subsequently decide to modify
the device search query, the results of the modified device search query is not reflected in the custom group. You will
have to delete the custom group and recreate it using the newly modified device search query group.
If you create a custom group using a device search query, you subsequently modify the device search query and then
attempt to edit the custom group that used the device search query in question, the original device search query group
gets deleted. So, once you create a custom group based on a device search query, do not edit it. If you need to modify
it, delete it first and then re-create it.
HA Clusters can be discovered using SNMP only. The discovery task that is intended to discover HA Clusters must have
SNMP enabled and the associated credentials must be correct for the target devices.