Release Notes

Issue 19:
Description: Dell Fibre Channel switches (modular) are classified under Network DevicesSwitches
and not under Modular Systems in the device tree. [36990]
Issue 20:
Description: When the name resolution on an IP address to a host name fails using DNS, OpenManage
Essentials attempts to resolve the name using the NetBIOS name query. This action may cause the device
to appear in Essentials with the NetBIOS name even if it does not have a DNS entry. [138013]
Issue 21:
Description: In case of SNMP discovery, when the name resolution on an IP address to a host name fails
using DNS, Essentials attempts to resolve the name using the MIB2 name query. If the MIB2 name query
also fails, then Essentials displays the IP address of the device as the device name.
Issue 22:
Description: For Remote Access Controllers (RACs) that have instrumentation installed and that are
running on the host operating system, the RAC IP addresses are shown in the RAC Device table. [134365]
Issue 23:
Description: For NIC information on systems, Essentials uses the operating system's provider(s) to
retrieve data rather than Server Administrator. This behavior can result in discrepancies in reporting NIC
information between Essentials and Server Administrator. For example:
On Linux systems, adapters may be named differently between OpenManage Essentials and Server
Administrator. For example, OpenManage Essentials may report a NIC adapter as eth0, while Server
Administrator shows the actual manufacturer name of the NIC.
If more than one NIC card is not configured with an IP address, OpenManage Essentials may show
only one of the cards with an IP address of 0.0.0.0.
OpenManage Essentials may not report disabled NIC adapters.
Issue 24:
Description: While performing discovery, if a device is discovered using host name, and if its IP address
changes at a later time, OpenManage Essentials displays two devices after the next discovery cycle. One
device displays the old IP address and status as Power Down, while the other displays the new IP address.
This problem is likely to affect systems that have DNS-DHCP IP addressing and for which the IP addresses
frequently change. [148069]
Resolution: A workaround to eliminate duplicate device is to delete the device with the old IP address.
Issue 25:
Description: The choice of protocols specified for discovering and managing the devices can result in
varying levels of manageability. For instance, if you choose to manage devices in your network using only
WMI, the devices with only SNMP agent (example DRAC) are classified under the Unknown group and
consequently, you may not get the Application Launch (example RAC console) functionality for the
device. To avoid such issues, make a careful choice of the protocols while configuring discovery ranges,
15