Dell PowerConnect OpenManage Network Manager Release Notes 5.0 - Page 7
Workaround, Workarounds, Discovery
View all Dell PowerConnect OpenManage Network Manager manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 7 highlights
7 • Exporting to Excel does not work in Internet Explorer. Workaround: Ctrl + click the Excel export button in OpenManage Network Manager. (13456) • Clicking My Assets in the toolbar repeatedly may halt portlets. Workaround: Restarting the browser, or signing out and signing back in lets things work again. This is the result of built-in phishing protection. (10942) • Mutlitab browsing is not supported and may produce unpredictable results. (10963) • In a job viewer window, some audit trail messages may appear too narrow to read in their entirety. Workaround(s): Enlarge the browser and the job viewer window grows bigger (maximized, you will see more of the message). The job viewer window lets you copy and paste the message text into applications like notepad for less restricted viewing and for additional message analysis. (16320) • In some cases a single managed object may be discoverable via multiple IP addresses. Each discovered IP creates a new inventory object and will count against any licensed Right To Manage total. Workaround: Network elements should be managed through a single interface/IP. Additional discovered interfaces should be deleted leaving only one managed object in inventory. (11540) • Discovery-When specifying network addresses using the Subnet type, you must specify the Network address at the beginning of the subnet since OpenManage Network Manager assumes it is the starting IP address for the range. If you specify an address in the middle of the subnetwork then OpenManage Network Manager may discover devices outside of that subnetwork. This also means that IP addresses in the network that precede the specified address are not discovered. To avoid these issues, use the CIDR specification of the network to discover rather that the subnet ID. (16803) • Link discovery currently does not find one-ended links. (16305) • Devices not implementing LLDP MIBs with complete and correct data will prevent OMNM from discovering links for the device. Also some devices encode STP data collected via SNMP in a way that is difficult to decipher. In these cases, the algorithm OMNM logs a warning message "Problem determining designated port encoding algorithm" during device link discovery. (16438) • The Red Hat system clock can differ one hour from the application server clock. (15524) • When OMNM status icon in the tray is green and you select procman ("process manager") restart from Windows' Control Panel services, an error message appears saying the service did not stop properly. The tray icon then turns white. Since the application server is still running, when you try to restart procman again from control panel, the icon turns red. Workaround: Stop all Java and WMI processes in the process manager. A system reboot also re-initializes the OWProcMan (process monitor). Note that the service name may be different if your package has been specifically branded. The executable path for the service is \....\oware\bin\owprocman.exe. (16335)