OmniVista 3.0 Release Notes
./OmniVista/3.0.0/ov30_release_notes/OV_ReleaseNotes.html

Release Notes

OmniVista 2500 Version 3.0 PolicyView 2730 Version 3.0 SecureView-SA 2750 Version 3.0 SecureView-ACL 2760 Version 3.0 Quarantine Manager 2770 Version 3.0

April 2006

Revision BE Part Number 031858-10 READ THIS DOCUMENT Includes OmniVista for Windows Server 2003/Windows XP Sun Solaris Systems Red Hat Linux Suse Linux Alcatel Corporation 26801 West Agoura Road Calabasas, CA 91301 (818) 880-3500 (818) 880-3505 Fax

Table of Contents

1. Introduction 1.1 Technical Support Contacts 1.2 Documentation What's New?
Page 1 of 49 Wednesday, April 12, 2006 15:18:00
1.3 What s New? 1.4 Feature Set Support 2. System Requirements 2.1 Requirements for All Platforms 2.2 System Requirements for Microsoft Windows 2.3 System Requirements for Sun Solaris 2.4 System Requirements for Linux 3. Installation 3.1 Installing OmniVista on Windows Systems 3.2 Installing OmniVista on Sun Solaris Systems 3.3 Installing OmniVista on Linux Systems 3.4 Installing Add-On Applications 3.5 Upgrade Procedures 3.6 Upgrading an Evaluation OmniVista License to a Permanent License 3.7 Upgrading Licenses for Optional OmniVista Applications 4. Launching OmniVista 4.1 Launching OmniVista on Windows 4.2 Launching OmniVista on Sun Solaris 4.3 Launching OmniVista on Linux 5. Uninstalling OmniVista 5.1 General Concepts 5.2 Uninstalling on Windows 5.3 Uninstalling on Sun Solaris 5.4 Uninstalling on Linux 6. Server 6.1 Maintenance 6.2 Troubleshooting 7. Known Problems 7.1 Known General Problems 7.2 Known Statistics Problems 7.3 Known Topology Problems 7.4 7.5 7.6 7.7 7.8

Page 2 of 49

Known Resource Manager Problems Known Locator Problems Known Telnet Problems Known Other Problems Known PolicyView Problems
Wednesday, April 12, 2006 15:18:00
7.9 Known SecureView-SA Problems 7.10 Known Quarantine Manager Problems 7.11 Known VLAN Problems 7.12 Known Server Backup Problems 8. 9. 10. 11. 12. 13. 14. 15. 16. Problems Fixed Since 2.4.2 Problems Fixed Since 2.4.1 Problems Fixed Since 2.4.0 Problems Fixed Since 2.3.0 Problems Fixed Since 2.2.5 Problems Fixed Since 2.2.4 Problems Fixed Since 2.2.3 Problems Fixed Since 2.2.2 Problems Fixed Since 2.2.1
17. Problems Fixed Since 2.2.0 18. Problems Fixed in PolicyView Revision History
Release 1.0 1.1 2.0 2.0.1 2.1.0 2.1.0 2.1.0 2.2.0 2.2.0 2.2.1 2.2.2 2.2.3 2.2.4

Page 3 of 49

Revision A B E F H J K L M N O P Q
Date 06/01/01 10/11/01 07/12/02 08/27/02 11/08/02 11/22/02 01/10/03 07/11/03 08/29/03 10/16/03 02/26/04 04/22/04 07/13/04
Description of Changes General Availability Release General Availability Release General Availability Release General Availability Release Alpha Release for OmniSwitch 6648, 6624, and 8800 Beta Release General Availability Release Beta Release General Availability Release Maintenance Release Maintenance Release Maintenance Release Maintenance Release
2.2.5 2.2.6 2.3.0 2.3.0 2.3.0 2.4.0 2.4.1 2.4.1 2.4.2 2.4.1 3.0 3.0 3.0 3.0
R S T U V W X Y Z AA BB BC BD BE
08/03/04 08/24/04 09/03/04 10/27/04 11/02/04 01/14/05 05/26/05 07/22/05 09/15/05 11/17/05 02/09/06 03/08/06 03/31/06 04/12/06
Maintenance Release Internal development release only Beta Release GA Release Post GA GA Release GA Release (Quarantine Manager) Release Notes update in Support Build Maintenance Release for Quarantine Manager Release Notes update GA Release Release Notes update Release Notes update Release Notes update

1 Introduction

These Release Notes cover the basic feature set supported by OmniVista 3.0 for the following supported platforms: Windows Server 2003/Windows XP Sun Solaris 2.9 Linux (Red Hat Linux Enterprise Workstation) Linux Suse Professional 9.3. Known problems, limitations, and workarounds are included. Please read the applicable sections in their entirety as they contain important operational information that may impact successful use of the application. These Release Notes cover both versions of OmniVista: OmniVista Basic 2540 Multi-User - allows installation of the server software on a physically separate machine for support of multiple client machines. OmniVista Basic 2520 Single User - the client and server software are installed on the same machine and additional client installations are not an option. Unless otherwise specified, all information in this document is applicable to both systems. See the table below for a summary of supported versions and platforms:

1.3.4 Release 2.4.0

Support for 6800 Switches The new OmniSwitch 6800 family of switches (OS6800-24 and OS6800-48) are now supported. Trap Display When viewing traps for a specific switch in the Notifications application, all traps received from any valid IP address associated with the switch are now displayed. In previous releases, only traps with a source IP address matching the management address used by OmniVista were displayed. Polling for Missing Traps AOS switches already send traps labeled with a sequence number, which can be used to detect missing traps. The switch can be asked to replay traps for a given listener, starting with a given sequence number. Upon detecting a gap in the sequence numbers of received traps from a switch, OmniVista will immediately request that the switch send the missing traps, starting from the beginning of the oldest known gap which has data available on the switch. Trap Forwarding Feature Traps can be forwarded to a specific IP address.

Page 11 of 49

New Column Added to Notifications Table A new column was added to the Notifications Table in the Notifications application. The "Agent Name" column displays the value of the "sysName" variable from the switch. Custom Menu "Scope" Option in the Preferences Application A "scope" option was added to the "Customized Menu Commands" option in the Preferences application. This enables users to configure custom pop-up menus for different devices. The customized pop-up menu can be configured with the following parameters: All - Matching the behavior of 2.3. Custom menu commands appear for all applicable devices. This is the DEFAULT value. Mibset - Specifies one or more mibsets names. All devices that use these mib sets will include the custom menu item. OID - Specifies an explicit OID string. All devices whose "sysObjectID" value starts with the values specified will include the custom menu item.

1.3.5 Release 2.3.0

Support for AOS 5.1.5 Basic discovery and monitoring support has been added for all AOS 5.1.5 devices. This includes chassis/module display, statistics support, and updated MIBs. Support for 6600-U24, 6600-P24, 6602-24, and 6602-48 Switches The new OmniSwitch 6600 family of switches (OS6600-U24, OS6600-P24, OS6602-24, and OS6602-48) are now supported. Support for OS6300-24 Switches The OS6300-24 switches are now supported. OmniVista Data Backup/Restore A new application called "Server Backup" has been added that provides live backups of discovery, security, MIB caching, and all application-specific data. In addition, the contents of its data store and the LDAP server component are also backed up at the same time. Coexistence with 4760 Server on Same PC Both OmniVista 4760 and 2500 can now exist on the same workstation. If both the OmniVista 2500 and 4760 are installed on the same server, they will each include their own private LDAP server. Subnet Mask Control OmniVista 2.3 offers controls to define subnets of arbitrary granularity, and define arbitrary names for the subnets. Polling Enhancements In 2.2, there was no indication in the GUI when regular polling cycles are invoked. With 2.3, a set of 5 indicator lights in a horizontal row has been added for this purpose. The display is at the lower right-hand corner, to the left of "Status Indicator Light". AMAP Support for OS6300-24 Switches The OS6300-24 switches now support AMAP adjacency protocol, and with this release of OmniVista we use that capability to place these switches on the topology maps automatically. AMAP Support for 6600-U24, 6600-P24, 6602-24, and 6602-48 Switches The OS6600-U24, OS6600-P24, OS6602-24, and OS6602-48 switches now support AMAP adjacency protocol, and with this release of OmniVista we use that capability to place these switches on the topology maps automatically. Integrated SSH2 In release 2.3 both Telnet and SSH, including SSH version 2, are supported directly from the OmniVista GUI using a licensed third party product.

2 System Requirements

The following minimum builds are required to run OmniVista 3.0: AOS 7000, 8800, 6000 - 5.1.6.R02 and 5.1.5.R- 5.3.1.R- 6.1.1.R01 XOS OmniSwitch, OmniSwitch Router - 4.4.5 GA 4024 - 4.3.3.B OEM 6124/6148 - 3.40.x 6300 - 2.2.0.1x OmniVista 3.0 upgrade paths supported 2.3 to 3.0
Page 14 of 49 Wednesday, April 12, 2006 15:18:03

2.4.1 to 3.0

2.1 Requirements for All Platforms

2.1.1 Java Requirements

OmniVista includes the Java 2 Runtime Environment (JRE) Version 1.5 for each of the following supported platforms: Windows Server 2003/ Windows XP, Solaris 2.9 and Linux. The correct version of JRE is bundled with the installers for all supported platforms, and is automatically installed with OmniVista. Because the bundled JRE is installed in the OmniVista installation directory, it should NOT affect or conflict with any other JRE or Java Virtual Machine previously installed on your machine. The Element Managers must be installed on the clients that will use them. Because of the different Element Manager implementations, hardware and software installation requirements vary. Refer to the release notes for the desired element manager for system and installation requirements for each Element Manager. Note that with the exception of the Web-Based Managers, the Element Managers are not included with OmniVista.
2.1.3 Server Platform Requirements
The OmniVista Server should be installed on a machine with a static IP address.
2.1.4 OmniVista Basic 2520 Single User Platform Requirements
The system requirements for OmniVista Basic 2520 Single User are the same as those for the OmniVista Basic 2540 Multi-User Server and/or the requirements for the desired Element Managers, which ever is greater.
2.2 System Requirements for Microsoft Windows
The minimum system requirements for running OmniVista 3.0 on Microsoft Windows are: Windows Server 2003 or Windows XP Client machine: Pentium IV 1 GHz minimum, 2 GHz recommended 1 GB RAM minimum 2 GB of free disk space on the drive on which you will be installing OmniVista. Server machine: Pentium IV 2 GHz minimum, 3 GHz recommended 2 GB RAM minimum 5GB of free disk space on the drive on which you will be installing OmniVista "Server" versions of windows -Windows 2003 Server, 20 GB if managing 1,500 switches or more Note: Minimum configuration not recommended for managing more than 500 switches. For managing more than 1,500 switches, recommend 3 GB RAM on server, 2 GB RAM on client. You can allocate up to 1280 MB of RAM to the client and/or server.

Page 19 of 49

Wednesday, April 12, 2006 15:18:04
3.4.1.4 PolicyView Post-Installation Configuration For all platforms, in order for OmniVista to correctly determine the state of devices, you must subscribe to the following traps: For XOS switches: policyEvent For AOS switches: policyEventNotification. Trap Configuration can be performed in the Topology and Notifications applications; just click the bell icon on the tool bar and refer to the online help using the Help button that appears on each dialog of the Trap Configuration wizard. Note: On UNIX systems, it is recommended that you modify a startup script to launch the Netscape Directory Server automatically when you turn on or restart the computer.
3.4.2 Installing SecureView-SA
3.4.2.1 Installing SecureView-SA on Windows To install SecureView-SA on Windows, you must log on with a User Profile that has administrative rights. #. #. #. #. #. #. #. Insert the OmniVista NMS CD into the CD-ROM drive. change to the SecureView directory. Double-click the Disk1 folder. Double-click the InstData folder. Double-click the Windows folder. Double-click the install_win.exe icon. Follow the instructions in the installer to completion.
3.4.2.2 Installing SecureView-SA on Sun Solaris To install SecureView-SA on Sun Solaris, you must log on with a User Profile that has administrative rights. #. #. #. #. #. #. #. Insert the OmniVista NMS CD into the CD-ROM drive. At the command prompt, change to the SecureView directory. In the CD-ROM drive window, open the Disk1 folder. In the Disk1 window, open the InstData folder. In the InstData window, open the Solaris folder. Enter./install_sol.bin. Follow the instructions in the installer to completion.
3.4.2.3 Installing SecureView-SA on Linux To install SecureView-SA on Red Hat or Suse Linux, you must log on with a User Profile that has administrative rights. #. #. #. #. #. #. #. Insert the OmniVista NMS CD into the CD-ROM drive. At the command prompt, change to the SecureView directory. In the CD-ROM drive window, open the Disk1 folder. In the Disk1 window, open the InstData folder. In the InstData window, open the Linux folder. Enter./install_lin.bin. Follow the instructions in the installer to completion.

Wednesday, April 12, 2006 15:18:06
7.1.1 OmniVista Server Must Be Run As "ROOT"
On Unix platforms, the OmniVista server must be run as "root". To receive traps on the default port of 162 on Unix, the receiving process must be running as the super user (root). So, the OmniVista server must be run on UNIX as root to receive traps properly. Workaround: On Unix, become the super user before starting up the "runserver" script, or start it up from the Unix boot process. PR# 38215
7.1.2 ESC Used in Progress Dialogs Does Not Select the Cancel Button in the Progress Dialog
Pressing "ESC" in Progress Dialogs does not select the Cancel button in the Progress Dialog. Workaround: Use the Cancel button rather than pressing the ESC key. PR# 66257
7.1.3 Audit Tables Only Autoscroll to Second to the Last Row
If you're viewing a log with the Audit application, and a new row gets added to the log, the table doesn't autoscroll so that the new row is visible. If another row gets added, the table autoscrolls down one row, but the last row is still hidden. Workaround: Click on the scroll arrow to see the last entry in the list. PR# 72113
7.1.4 Configuring Traps on AOS Switches With OmniVista Does Not Work Properly if Configured With SNMP Community Map Mode Enable
Configuring traps on an AOS switch with OmniVista will not work properly if the switch has been configured with "snmp community map mode enable". The entries created by OmniVista in the switch station table will use the community string that the switch was discovered by, for the "user name" that that table requires. If community map mode is enabled, the community string will likely not be the name of an snmp-enable user, so the traps will not be sent. No error messages will appear in OmniVista trap configuration. Workaround: The user name to be used must be specified to OmniVista in the "Trap Station User name" field of the switch "edit" dialog. PR# 73566
7.1.5 Cannot Specify the Order In Which Ping Sweep Ranges Will Be Searched
Although OmniVista allows the user to enter more than one Ping Sweep range in the AutoDiscovery Wizard, there is no way to specify the order in which these ranges will be searched. A switch which appears in multiple subnets may be discovered by any of the addresses that it responds to, and will thereafter be known to OmniVista by that IP address, even though the user may have preferred it to be known by one of its other addresses. Workaround: If a switch is automatically discovered by one address, but you'd prefer it to be known to OmniVista by a different address, simply edit the device in OmniVista and select the desired alternate address manually. Thereafter, OmniVista will remember to use that address for that switch. (Bring up the Topology application, click on the Switches node, then right-click on the appropriate switch and select "Edit" from the pop-up menu. Then pick the desired alternate address from the "IP Address" drop-down menu). PR# 74278

7.1.6 Firmware Backups Performed Using Previous Versions of OmniVista Are Not Compatible After Upgrades to OmniVista 2.3
After a backup to OmniVista 2.3, firmware backups performed using previous versions of OmniVista are not compatible and cannot be seen/restored using OmniVista 2.3. However, these files are not erased and use extra disk space. Workaround: As soon as the upgrade to OmniVista 2.3 is complete, backups of all switches deemed important must be performed. These new backup files will, of course, be fully compatible with OmniVista 2.3, allowing successful restore operations to be performed. Old files must be manually removed from [OmniVista Root Directory]/data/configadmin/snaphosts/ PR# 74984

Page 29 of 49

7.1.7 Installer Prompts For Maximum Memory Size For the Client and Server, But There is No User Interface for Changing Them
The installer prompts for a maximum memory size for the OmniVista client and the OmniVista server, but there is no user interface for changing these values once the product has been installed. Workaround: If you want to change the server's maximum memory on Windows, you must modify the OVServer.lax file, run bin\regsync.exe, and finally restart the service. To change the server's maximum memory on other platforms, you must modify the RunOVServer.lax file and restart the server. To change the maximum memory for OmniVista client (on any platform), edit the OmniVista.lax file using a text editor such as vi or notepad and search for "-Xmx". You will find something like "-Xmx384m". Change the number in this argument to the desired limit in megabytes, e.g. "-Xmx512m". Do not forget the 'm' at the end. PR# 75063
7.1.8 Upgrade OV2.0->OV2.3: Errors in Server Log From Scheduled "configadmin" Tasks
Upgrade OV2.0->OV2.3: Errors in server log from Scheduled "configadmin" tasks Workaround: Delete all the entries from the data/configadmin directory and remove the configadmin directory before upgrading to 2.3. PR# 76160
7.1.9 Installer Will Not Upgrade an Existing 2.0 or 2.1 "Single User" Version to 2.3
The installer will not upgrade an existing 2.0 or 2.1 "Single User" version to the 2.3. Even though the new 2.3 version being installed is a single-user version, it will say "Cannot install Client-only or Multi-user over an Existing Single-user installation". Workaround: Uninstall the earlier version and install 2.3 Single-user into the same directory. PR# 76233

7.1.10 Previously Existing Filters For VLAN Tables and Security's "Users and Groups" are No Longer Available After Upgrading From Earlier Versions
When upgrading from earlier versions of OmniVista to OmniVista 2.3, the previously existing filters for VLAN tables and Security's "Users and Groups" are no longer available. Workaround: The filters can be reentered, if desired. PR# 76251
7.1.11 OmniVista Server Fails to Restart If Running in a Command Line Window on Windows
The server will fail to restart when using the Control Panel's "Restart" function or the Server Backup's "Backup" or "Restore" functions. Workaround: Run the OmniVista Server as a Windows Service when on the Windows platform (this is the normal way that OmniVista is installed). PR# 90820
7.1.12 Out of Memory and JVM Crash on Server if -Xmx Setting Too High
If the -Xmx setting is too high, the server will crash. Workaround: If running the OmniVista server on a PC it is recommended that you do not run with an -Xmx setting of higher than 1440m. The maximum memory allocation for a windows platform should be 1.4 GB, or "-Xmx1440m" when editing the command line. Note: For Windows installations, do not set the server memory higher than 1280 during an install. If the server has already been installed with the memory set to a higher number, it can be changed using the procedure in Section 7.1.7. PR# 91414

Page 30 of 49

7.1.13 Firmware Cannot Be Backed Up When Backing Up OS-6100 Series Switches
When backing up OEM OmniStack switches, there is no way to backup the firmware: only the configuration files can be backed up. Workaround: There is no known workaround at this time. PR# 74855
7.1.14 OS6024 Devices With 16 MB CMM Return Invalid OID Errors During Discovery
OS6024 devices with (16 MB CMM ) return invalid OID errors during discovery. This prevents the Software Version for the device in the Devices Table to be empty and failure to display Spanning Tree status in the VLAN application. Workaround: Please install Software for OmniStack OS6024 - 16 MB CMM - version "V2.6.202" or better. PR# 75055
7.1.15 Alcatel Router 7750 and Fortigate Have "Unknown" Type in OmniVista
Fortigate devices that are discovered as third-party devices will display "unknown" in the "Type" column of the device table in the Topology application. Workaround: Select the individual device display to show additional information about this device. PR# 92305
7.1.16 Unknown or Invalid 'Mailhost' Error Should Display in the Client's Status Window
When a responder attempts to send an e-mail to an unknown or invalid SMTP, an exception is written to the server.txt. Workaround: After configuring an SMTP server, got to the E-Mail Preferences screen in the Preferences application to send a "Test" e-mail. Make sure that the e-mail was delivered, and check for error messages in the server.txt log using the Audit application. PR# 92158

7.1.21 OV LDAP Server Starts Automatically After Install, But Not After System Restart (UNIX/Linux)
On UNIX/Linux installations, the LDAP Server starts automatically and the last installation screen tells the user to run OV Server. If at some point after that, the server machine is rebooted, the LDAP Server does not automatically restart and the OV Server complains that it cannot connect to the LDAP Server. Workaround: After a UNIX/Linux machine is rebooted, manually restart both the LDAP Server and the OmniVista Server. PR# 98003
7.1.22 On Windows Installations, OmniVista Logs the User Out After Disabling/Enabling the PC NIC
When an OmniVista server is running on a windows platform, if the windows PC loses total connectivity to the network (by unplugging the network cable or disabling re-enabling the network interface) any OmniVista clients will be logged out, even if they are running on the same machine. This is due to a windows behavior of shutting down all local network connections when remote connectivity is lost. Workaround: When the network access is restored, log into the server again. PR# 80952

Page 32 of 49

7.1.23 Client Received OutOfMemory Error Messages
Setting the number of lines in the Audit Log File to a very large number can cause the client or server to run out of memory. Workaround: Customers with more than 1,000 switches running OmniVista Server on Windows should probably not increase the default "Maximum Audit Entries" much past the 2,000-line default. Customers running Linux and 32-bit Solaris machines that have at least 2GB of memory should be able to increase this number to 4,000 lines without trouble. Note that there is no memory penalty for setting the "Maximum Audit File Copies" to a large number. This only increases the amount of disk space consumed, to store the additional rolled-out log files, which are still available for viewing in Audit View. This can be a good workaround to make a longer audit trail available on machines with limited memory. PR# 99142
7.2 Known Statistics Problems
7.2.1 Existing Profiles in the Statistics Application, Based on the Original IP Address, Do Not Get Updated to the Alternate IP Address
In Topology, it is possible to modify the discovery list by changing an IP address to an alternate IP address using the "Edit Discovery Manager Entry" dialog. However, existing profiles in the Statistics application, based on the original IP address, do not get updated to the alternate IP address and result in no new data being collected. Workaround: If an IP address is changed to an alternate IP address, existing profiles based on the original IP address will need to be updated manually if the collection of new data is required. This can be done by removing the performance variable in the Legend Table containing the original IP address and replacing it with the same performance variable using the alternate IP address. PR# 74463

Page 34 of 49

7.3.1 AMAP links for 6148/6124 Stack to 6300-24 Do Not Show Up in Topology Map
AMAP links for 6148/6124 stack to 6300-24 do not show up in Topology Map. Workaround: The AMAP entry is OK when the connection is between the 6148M (master) and the 6300-24. PR# 86423
Client/Server Out of Memory Rearranging a Large Number of Switch Icons on Topology Map
The topology GUI application may run out of memory if too many switches are included in a single topology map. Workaround: Limit the number of switches on a single topology map to 600 or less. PR#s 91020, 91837
7.3.3 Arranging a Hub of Switches as Networked Does Not Work The First Time
If group of devices are connected and their initial placement is in same straight line horizontally or Vertically, then using the "Arrange Icon" Networked doesn't work. Workaround: This initial alignment is possible only for very small networks but if it happens using the "Arrange Icon" Circular before using the "Arrange Icon" Networked will resolve the problem. PR# 86618
7.3.4 Cannot Edit Manual Links Slot/Port Fields
When editing manual links using the Topology application, only the LAG fields are open for Edit. Workaround: Remove the link and add it again, specifying the slot/port fields. PR# 91573
7.3.5 Toolbar in Topology Physical Map Refers to Mobility Drop-Down from VLANs
When a device is selected in the VLANs application and one of its children nodes is selected ( 'Mobility)', if the user switches to another application and the information pertaining to this device is refreshed, the navigation drop-down at the top of OmniVista's screen will be mistakenly refreshed to display the currently selected VLAN node. Workaround: To avoid this behavior, make sure that no tree node under a switch node is selected in VLANs when using another OmniVista application. PR# 98497
Known Resource Manager Problems
Resource Manager (Version 2.3 and Up) Only Supports Upgrades from 2.x.x.x and Up on the OS6300-24
OmniVista Resource Manager (Version 2.3 and up) only supports upgrades from software version 2.x.x.x and later on OS6300-24 switches. Do not attempt to upgrade from 1.x.x.x with Resource Manager. Workaround: Upgrade OS6300-24 switches with 1.x.x.x manually to 2.x.x.x. Once you do this, you will be able to use Resource Manager to perform the upgrade. PR# N/A

7.5.3 Locator Does Not Show VLAN of Host for L2 Linkagg 802.1q Port, AOS/XOS Only
VLAN data may not appear in AOS switches with older builds. Locator VLAN reporting will operate properly under the following releases of AOS software and above: 5.1.5.193.R04 5.1.6.434.R01 5.1.6.103.R02 5.3.1.175.R02 6.1.1.340.R01. Workaround: Upgrade problem-AOSs to their respective 'working' software. PR# 95451
7.5.4 Cannot Restart Locator Browse After It's Been Canceled
If a Locator Browse function is canceled by selecting the Search tab while the browse is underway and clicking the Cancel button, the browse function cannot be properly restarted. Workaround: If a Locator Browse must be canceled in this manner, closing and reloading the Locator application will re-enable the browse function. PR# 100093
7.5.5 Locator Browse Results Table Shows Previous Results Until New Search Is Complete
Locator browse results panel may show previous results until the current browse has been completed. Workaround: Wait for the current browse operation to complete, and the old data will be replaced. PR# 99837
7.6 Known Telnet Problems
7.6.1 OmniVista Telnet Menu Bar Edit Drop-Down Menu Is Never Enabled
The Edit drop-down menu in the OmniVista window frame does not enable the editing or deletion of scripts. Workaround: Use the Edit or Delete buttons in the Create Scripts tab. PR# 91909

7.7 Known Other Problems

Page 37 of 49
7.7.1 OmniVista Trap Configuration is Not Available for the OmniStack 5010, 5022, and 5052
OmniVista trap configuration is not available for the OmniStack 5010, 5022, and 5052. Workaround: Use telnet and the switch's Command Line Interface or User Interface to configure the switch for traps. Refer to the switch's user manual. PR# 69127
7.7.2 OmniVista Client/Linux/DHCP Cannot Log Into Remote OV Server. Works if Static IP
When a Linux OmniVista client runs on a box that gets its IP address from a DHCP server, this client may not be able to connect to OmniVista Server. This is because the client needs to know the hostname associated with that IP address. Workaround: Setup a DNS Server that will provide reverse resolution for the pool of DHCP IP addresses by either configuring the client to use that DNS Server (preferred); or using a DHCP Server that is capable of automatically configuring the Linux client to use that DNS Server. Alternatively, the whole pool of IP addresses could be resolved using another method such as storing the information in the client's /etc/hosts system file; but this is much less convenient. PR# 83449
7.7.3 The Server Process Should Disassociate With Its User Session on UNIX/Linux
When OmniVista is installed and/or the OmniVista server is started using X Window, the server gets terminated when the user logs out from the system. Workaround: After completing the OmniVista installation either locally or remotely using X Window, log out of the system and use rlogin/rsh/ssh/telnet instead to start the OmniVista server. PR# 85553

7.10.2 Attack from Outside the Managed Network Cannot Be Quarantined
A quarantine cannot be applied without determining a local MAC address to be blocked, so an attack coming from outside the managed network can be detected but not quarantined. When this happens, an entry will be written to the Quarantine log stating that the MAC address could not be found for the source IP of the attack. Workaround: Periodically check messages posted in the OmniVista Audit application quarantine.log to find any entries where QM was not able to determine the associated MAC address from the Locator database. If the switch the attack is coming through a device that is not managed by OmniVista, adding that switch to the OmniVista managed devices should allow Quarantine Manager to find the MAC address of the attacking IP. PR# 92017
7.10.3 Quarantined MAC Group Address Cannot Be 00:00:00:00:00:00
The "Dummy" MAC address recommended for the Quarantined MAC group (written into the Telnet canned script) is invalid in Policy Manager on the switch. It rejects such a MAC group created in L2 Groups in OmniVista and send via SecureView; and the Policy Manager events log does not identify the problem. Workaround: Do not use all zeros in the MAC group for SecureView ACLs. PR# N/A

7.11 Known VLAN Problems

7.11.1 Spanning Tree Status Changes Fail for OEM OmniStack Devices
Trying to change Spanning Tree setting for OS6124 or OS6148 devices in OmniVista VLAN application does not work. Workaround: OS6124 or OS6148 devices do not support per VLAN Spanning Tree. OmniVista reports current Spanning Tree status for these devices. Use Telnet or Web Browser to modify the Spanning Tree for these devices. PR# 95561
7.11.2 Unable to Change the VLAN ID When Editing an IP Interface
When editing IP Interfaces for a device in VLAN application, the VLAN ID does not change when editing an IP Interface using switches with software level 5.1.6. Workaround: Delete the IP Interface entry and recreate a new entry with proper values or use WebView to make this change. This problem is fixed in switch software 6.1.1 or better. PR# 97789
7.12 Known Server Backup Problems
7.12.1 Server Backup File Size Limited on 32-Bit Platform
A 32 bit platform is limited to Server Backup file size of 2GB when using FTP. For larger backups local file system should be used. Workaround: The maximum size of the backup file supported will depend on Operating System. PR# N/A

7.12.2 Server Backup Can Fail if FTP Is Not Used for Backup or Restore
Schedule Backup or Restore can fail with "Can't update Scheduled Task Manager" error. This error only shows up in cases when FTP is not used for Server backup or restore. Workaround: When defining the Backup or Restore task, make sure to create the definition with FTP enabled. Once the FTP Port number is set and saved, the FTP setting can be disabled and this error will not appear. PR# 98432

Page 42 of 49

8. Problems Fixed Since 2.4.2
8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 Combination of Spacebar and Enter Keys Automatically Logs Off AOS Telnet Sessions (PR 86252) SSH Scripting Hangs for Switches Discovered via EMP Port (PR 91315) No Canned Scripts for OV Admin Users Other Than Default (Admin, Switch) (PR 88887) "Show Traps State In Switch." is a Per-User Preference, Not System-Wide (PR 80956) Loading from Certified Directory and Rebooting the Entire Switch Causes OmniSwitch 9000 to Fail (PR 96347) Discovery Loses its Progress Reporting After Being Canceled and Restarted ( PR 91788) If Recurrence Time Equal or Exceeds 4 Weeks, Then Scheduled Profile Will Not Start Again (PR 85096) SwitchManager not Working with OmniStack 63xx (PR 78593) For Upgrade Installs, Fields Should be Pre-Filled with Existing Settings, Rather than Default Values (PR 91805)
8.10 Cryptic Error Message Return When Trying to Set a Rule for 127.0.0.0/8 (PR 88831) 8.11 8.12 8.13 8.14 8.15 Cryptic Error Message When Setting a Rule for Host 155.14.12.1/255.255.255.255 (PR 88832) QM Should Replace Existing MAC Rule So it Can Create a New MAC Rule in Quarantined VLAN (PR 93110) QM Should Replace Existing DHCP MAC Rule So it Can Create a New DHCP MAC Rule in Quarantined VLAN (PR 93111) After Notifying a AOS Switch to Load New Policy, the Status Panel Displays Inappropriate Error Message (PR 80468) For Invalid SMTP Server, the server.txt Error Should Name the Invalid Server Rather Than 'Mailhost' (PR 92156)
8.16 OV Server Does Not Shutdown Gracefully When Solaris Box is Rebooted (PR 91710) 8.17 Setting OV Server's -Xmx Setting to the Maximum When Installing in 32-bit Environments Can Cause "OutofMemory" Errors (PR 96104)
8.18 Vertical Scrollbar Does Not Track for Extremely Large Data Values (PR 75433) 8.19 8.20 Unsaved Changes to a Map Are Lost If Additional Changes Are Made By Another and Saved at the Same Time (PR 75257) OmniVista Topology Switch Connection is Lost When a Redundant Link Goes Down (PR 91182)

Page 47 of 49

17. Problems Fixed Since 2.2.0
17.1 Reverse DNS lookup causes client running Control Panel to temporarily freeze up (PR 76231) 17.2 Canceling a multiple-switch restore only cancels one switch (PR 76258) 17.3 Resource Manager slow, issues many discovery client requests if backup row is selected when polling occurs (PR 76239) 17.4 "Completed Reading Backup Files" message displays before table finishes displaying (PR 76244)
17.5 All rows not removed from Backup/Restore table when deleting multiple backups (PR 76269) 17.6 Memory leak switching tabs in Resource Manager (PR 76243) 17.7 Resource Manager unable to backup an XOS switch (PR 76556) 17.8 Client is not notified if OEM OmniStack Restore (or Install) exceeds retransmit limit (PR 76314) 17.9 Expert Mode: MAC wildcards not written to LDAP as colon separated value - Policy Manager rejects (PR 76610) 17.10 Server can run out of memory if it can't send Discovery Events to Logged-In Client (PR 76840) 17.11 Reload from OmniVista 2.2 of a 6600 does not work (PR 76811) 17.12 Topology takes a long time to load when the discovery list has many switches (PR 77241) 17.13 Ports OmniStack tab calls up the XOS tab help instead of OmniStack tab help 17.14 Click on OS device to display VLAN definitions, then Help and wrong help file displays 17.15 OS Ports dot1qPortVlan table help displays Mobility help file
18. Problems Fixed in PolicyView
18.1 18.2 PolicyView OneTouch Voice Sets Both Layer2 and Layer3 Policies in the Switch(es) (PR 69198) PolicyView OneTouch Data Will Not Be Applied Unless Classify Layer3 Bridge is Enabled (PR 69199)
18.3 Protocol TCP/UDP Ports Cannot be Modified or Deleted (PRs 57684, 61223) 18.4 Intermittent LDAP Access (SNMP Timeout) Errors If You Install, Uninstall, and Then Reinstall (PR# 61141)

Page 48 of 49

18.5 One Touch Policy Actions for XOS 4.5 or Less Cannot Contain 802.1p Priority (PR# 61629) 18.6 Environment Unstable After PolicyView Install is Updated (PR# 61918) 18.7 LDAP Database May Be Left with Unused Roles (PR# 65052) 18.8 In Expert Mode, A Canceled Policy Still Shows Up in the "Switches Pending Notification" Screen (PR# 75592)
18.9 Additional LDAP Server Set-Up is Required When Upgrading to PolicyView or SecureView-SA 2.2 (PR# 76285) 18.10 Changing Computer Name Fails PolicyView to Launch (PR# 86923)

Page 49 of 49

Wednesday, April 12, 2006 15:18:11