Dell PowerConnect OpenManage Network Manager Release Notes 4.4 - Page 8

8 Open Manage Network Manager - Release Notes • Do Not Install Downgrades-While this application supports an upgrade from a previous version, it does not support installing an older version over a newer one. (2398) • In addition to any licensing limitations, the IP Address filtering in discovery currently does not support an IP Range of more than 1000 IP addresses. The filter limits the query to starting the starting IP address in the range and 999 more addresses. (1995) • You may be unable to edit a Task after making Schema (attribute) changes. Workaround: Create a new Task to replace the one you are editing, and make the attribute changes to it. (2202) • When you set No. of failed cycles to two or larger in the Heartbeat function, the Device Down alarm does not appear, even if the device does not respond. (2208) • Link discovery does not find OSPF links. (2200) • Occasionally, when you invoke a help screen, a benign error appears in the client shell (EOFException: no more data available). You can safely ignore this. (1897) • Currently in this application manages Device Authentication Configurations separately from User Groups. When you copy a user group like Administrators, the User Group manager does not coordinate Device Authentication Configurations that refer to the Administrators group. • For a new User Group to have access to existing devices you must manually add them to the approved groups list in the Authentication Configuration. (1493) • Cannot start application server manually. Workaround: Install with application server installed as a process (so it starts with Process monitor) or go to \Dell\OpenManage\Network Manager\oware\bin\owcommonfunctions , and modify the section starting GetServerVMHeapSize to set MaxPermSize=128m (1831) • The Discovery Wizard sticks at Select Devices to be discovered panel if a device is marked licensed -> No and you check the box indicating the device is to be saved. Workaround: Unselect the check box. (Note: this may only happen when Other is licensed and the actual device's license is not enabled.) (1536) • If you do not shut down clients before restarting application servers, warnings like the following appear in the application server log/shell: 2009-01-08 10:58:35,425 WARN [org.jboss.ha.framework.interfaces.HAPartition.APP-T1000Partition] javax.naming.NameNotFoundException: ServerStatus not bound (1237) For Windows XP, you must install service pack 3, and installing .NET v. 3 is strongly recommended, particularly if you are monitoring the performance of Windows equipment. • Upgrade / Data Migration Fails-If an upgrade installation fails with the message with the app_setup.log error Connecting to database...>>>>> ERROR: OWSessionIDRDBMS : Failed to make database connection, the problem is that the database is not running on the host being upgraded. To cure this problem, manually start the database, and then re-try the upgrade