Andover, MA 01810
(978) 684-1000
|
|
50 Minuteman Rd. Andover, MA 01810 (978) 684-1000
CUSTOMER RELEASE NOTES |
NetSight Atlas Console 2.0 introduces a Client-Server architecture to the proven capabilities of NetSight Atlas Console. It includes a collection of tools to help you manage networks of varying complexity from one or more client workstations. It is designed to facilitate specific network management tasks while sharing data and providing common controls and a consistent user interface. NetSight Atlas is a family of products comprised of NetSight Atlas Console and a suite of plug-in applications.
| CAUTION: | The database and topology maps used/created in a beta release may not be compatible with the general release of NetSight Atlas Console 2.0. |
|---|
When updates have been obtained using the NetSight Atlas Web Update feature, the Addendum section at the end of these release notes will contain the updated release information.
The most recent version of these release notes can also be found on the NetSight Documentation web page: http://www.enterasys.com/support/manuals/netsight.html.
| NOTE: | When this topic is opened from the CD-ROM, the links from this topic to other help topics will not work (404 - not found). Links within the topic will work and once you've installed NetSight Atlas Console, you can launch the help system and access help for all topics.
|
|---|
Topology Manager's physical map views are based upon protocols such as CDP and 802.1d spanning tree that show the physical connectivity between devices. Logical map views are based upon protocols that show logical connectivity between devices, as it applies to a specific protocol. Map overlays add visual context to the map, by showing link color, link weights, and various endpoint symbols that are meaningful to a particular logical view. For example, activating the Spanning Tree overlay in a map view identifies master ports, active links, and Root Bridges by highlighting active links and attaching symbols to devices and ports in the view.
Graphing, Printing and Exporting
FlexViews are also capable of presenting information as a pie graph, bar graph, or line graph and printing or exporting information to a file or printer. The exported data is saved in CSV or HTML formats and graphs can be exported as BMP, JPG, PNG or TIFF formatted files.
FlexView Properties You can use the FlexView Properties to customize pre-defined views and create your own FlexViews to provide the kind of information you need to manage your network.
| WARNING: | NetSight Atlas Console 2.0, either fully licensed or for evaluation, should not be installed on a system with an earlier version NetSight Atlas Console that is integrated with HP OpenView. The 2.0 version will overwrite the earlier version, making the earlier version of Console unavailable from the HPOV menus. |
|---|
| It is recommended that you thoroughly review these release notes prior to the installation or upgrade of this product. |
NetSight Atlas Console is designed to support all Enterasys hardware product families. Refer to the Firmware Release Notes for the list of MIBs supported for the following product families:
Matrix C1
Matrix C2
Matrix E1
Matrix E5
Matrix E6/E7
Matrix N-Series
RoamAbout
Vertical Horizon
X-Pedition Routers
| NOTE: | Console performs a number of CPU-intensive tasks during Discovery and while creating device groups and the hierarchy of the left panel. You may notice some reduced performance while these processes are being performed. You may choose to use this time to become familiar with the documentation or to explore some of the menus and features of NetSight Atlas Console.
|
|---|
The NetSight Atlas Installer (InstallAnywhere® by Zero G Software, Inc.) leads you through a series of windows that ask you for all the information required in order to install NetSight Atlas Console. When you finish with the series of windows, NetSight Atlas Console is installed according to your specification. For complete
installation information and instructions, refer to the Installation help topic, and the instructions available on the web site: www.enterasys.com/netsight/.
The evaluation period for Console starts when the evaluation installation finishes and expires 30 days later. To convert from an evaluation copy of NetSight Atlas Console to a purchased copy, contact your Enterasys Networks Representative to purchase the software and receive a License Key. You do not need to reinstall the software to perform the conversion.
| WARNING: | NetSight Atlas Console 2.0, either fully licensed or for evaluation, should not be installed on a system with an earlier version NetSight Atlas Console that is integrated with HP OpenView. The 2.0 version will overwrite the earlier version, making the earlier version of Console unavailable from the HPOV menus. |
|---|
It is possible to update Console to change from a Stand-Alone to a Client-Server configuration. However, on Windows systems, this requires re-installing Console 2.0 using the Client-Server license key. This update can be done on UNIX and Linux systems without re-installing. Refer to Upgrading Console for more information on upgrading from Stand-Alone to Client-Server operation.
| NOTE: | It is not possible to upgrade from a Client-Only configuration to either a Standalone or Client-Server configuration without re-installing with the upgraded license key. |
|---|
| WARNING: | NetSight Atlas Console 2.0, either fully licensed or for evaluation, should not be installed on a system with an earlier version NetSight Atlas Console that is integrated with HP OpenView. The 2.0 version will overwrite the earlier version, making the earlier version of Console unavailable from the HPOV menus. |
|---|
| NOTE: | When re-installing Console, the installation program saves copies of any FlexViews that you have created/modified in the <install area>\Enterasys Networks\NetSight Atlas Console 2.0\backup\FlexViews folder.
|
|---|
| CAUTION: |
When re-installing Console, MIBs that you have added to the <install area>\Enterasys Networks\NetSight Atlas Console 2.0\client\etc\mibs directory will be removed during installation. You should always add MIBs <install area>\Enterasys Networks\NetSight Atlas Console 2.0\client\etc\mibs\MyMIBs directory. The MyMIBs directory is saved and restored during re-installation. Refer to How to Add MIBs for more information.
|
|---|
netstat –pel | grep <socket>
netstat –pel | grep 4588
This socket should be in LISTEN mode – localhost:4588 listen.
netstat –pel | grep 4589
This sockets should be in LISTEN mode – localhost:4589 listen.
If either socket is not in LISTEN mode, then it is likely that the database has failed to start, or that the server did not load properly. If this happens, consult the server log, these problems generate traces.
netstat –pel | grep 4532
This socket should be in LISTEN mode - *:4532. If it is anything but asterisk (*) (eg., localhost:4532, or 127.0.0.1:4532), the server is listening locally.
JBOSS_HOSTNAME=”1.2.3.4”
For customers who have installed a NetSight Server on a Linux or Solaris platform, this section provides information on manually starting and stopping the server, as well as running the server in a non-DNS environment and limiting client connections to the server.
Instructions on:
<installdir>/server/startserver.sh
<installdir>/server/stopserver.sh
<installdir>/server/netsightdatabase.sh {start|stop}
<installdir>/server/netsightserver.sh {start|stop}
.
| NOTE: | X-Pedition devices cannot have SSH and RADIUS authentication enabled at the same time. Refer to
the SSH Protocol Versions in the Enterasys X-Pedition User Reference Manual for more
information. |
|---|
| (Windows 2000/XP/Server 2003 only) An evaluation of your system is not automatically performed during the installation. If system requirements are not met, the install will take place, but results will be unpredictable. | |
| Solution: | Verify that all Windows 2000/XP system requirements are met prior to installing NetSight Atlas Console. |
| (Solaris only) In the Select Destination window of the Installer, if you click Browse and then double click to select a directory, the OK button doesn't work. | |
| Solution: | You must select the directory using a single click instead of a double click. |
| (Solaris only) The Installer does not come up due to path problems. | |
| Solution: | Ensure that /usr/usb does not precede /bin in your path. To do this, in a Unix window, type which chown. If the result is /usr/ucb/chown, replace /usr/ucb with /bin in your path. If the result is /bin/chown, the path is not the problem. |
| (Solaris only) When the Installer is started, the following message is reported:
Warning: Cannot convert string "-monotype-arial-regular-r-normal--*-140-*-*-p-*-iso8859-1" to type FontStruct. |
|
| Solution: | No action is required. The Installer will use a default font. |
| (Solaris only) The NetSight Atlas Uninstall program cannot warn you that the Console is running when you attempt to uninstall. When this happens, some components are not removed and subsequent installation and operation is unspecified. | |
| Solution: | Exit from the NetSight Atlas Console and stop all services prior to starting Uninstall on Solaris workstations. |
| During installation, the license information will be unreadable if your display settings are set for a black background (e.g., High Contrast#1, High Contrast #2, or High Contrast Black). | |
| Solution: | Set your display Properties > Appearance > Color Scheme to something other than a black background during installation. |
|
|
When there is insufficient space in the selected install area, the installer reports the situation and lets you select an alternate location. If the alternate location does not provide the required space, the installer again reports the shortfall, but instead of showing the alternate path, it incorrectly shows the path to the original install area. The space provided by the alternate path is analyzed correctly; only the path that is reported is wrong. |
| Solution: | Select an install area that provides the required disk space. Refer to System Requirements for more information. |
|
|
(Linux Enterprise v3 ES only) During install, the installation program reports the obsolete use of an option for the tail command and an inability to check for available disk space: For example:
Preparing to install... |
| Solution: | This is a problem with the install program and the messages can be ignored. |
|
|
The ThirdPartyDeviceMenu.txt file is overwritten when installing Console 2.0 as an update to Console 1.5 or if installing to co-exist with Console 1.5. This removes links to your applications from the device-level right-click menu. |
| Solution: | Prior to installing Console 2.0, save the ThirdPartyDeviceMenu.txt file to a safe location. Then, after installing Console 2.0, restore the original file to the Enterasys Networks directory or merge portions of your original file with information in the new ThirdPartyDeviceMenu.txt file. Refer to How to Add Applications to the Device-Level Right-click Menu topic for more information. |
|
|
Although rare, a timing problem could cause the database initialization to fail. The install program reports that the installation completed with errors. Check the install log for the following error:
java.lang.NoClassDefFoundError:
|
| Solution: | Restart the database initialization as follows:
|
|
|
Installing Console 2.0 over a previoiusly installed version of Console 2.0 reports the following errors reported in the install log:
BackupFiles
|
| Solution: | These warnings can be safely ignored. The problem will be corrected in a future release. |
|
|
(SuSE Linux only) The install log will report errors and the server and database cannot be launched. This is because the installation cannot detect a SuSE operating system to allow installing the correct system-specific scripts for launching several services and the database and the server. The Console 2.0 installer uses the dmesg command on linux to determine if it is being installed on a SuSE system. However, sometimes the information necessary to determine this is not always in the system buffer that is read. |
| Solution: | Reboot the system just prior to installing Console on a SuSE system to ensure that the system buffer contains the necessary information. |
| The Sort, Filter, and Find Toolbars cannot be isolated vertically. When you try to drag a bar vertically, the bar gets bigger, not isolated, and then you can no longer isolate the bar at all. This is a Java bug and does not interfere with the operation of the application. | ||||
| When different generations of SmartSwitch 6000/Matrix E7 family switches are mixed within a single chassis, the Console will create multiple Grouped by Chassis groups for the chassis.
For example:
Grouped By
|
||||
| Solution: | Examine the serial number associated with each chassis to determine when multiple groups represent the same chassis. | |||
When an X-Pedition is configured to run the OSPF routing protocol, it is possible during TFTP transfer that the device will send TFTP packets from different source ports. This will cause the transfer to fail with a TFTP Error: Undefined error. For security reasons this is not supported by the NetSight Atlas TFTP Server.
|
||||
| Solution: | When OSPF routing protocol is being used on your network, you must configure your X-Pedition devices to use a single port for TFTP traffic. Refer to the X-Pedition User Reference Manual for information about using the system set tftpsource command. | |||
| (Solaris only) NetSight Atlas Console may not accept input from the keyboard's numeric keypad. | ||||
| Solution: | Installing the latest patches for your operating system should fix the problem. You can download the most recent operating system patches from www.sunsolve.sun.com. | |||
| Device List > Import From File operations fail if the device list includes values with <space> characters (e.g., "authpwd=pass word" vs. "authpwd=password"). | ||||
| Device lists do not support <space> characters in their parameter values. Remove any <space> characters from your values and then re-import the device list. Alternately, you can delete the device (that has <space> characters in its values) from the device list and use the Add Device window (which accepts values with <space> characters) to create the device. | ||||
| Device List > Import From Console operations fail to contact devices that have <space> characters in their community names or SNMPv3 user names and passwords (e.g. "pass word" vs. "password"). The device and profile are created, but the device icon displays a red down arrow. | ||||
| Correct the community name or SNMPv3 user name and password using the Console Profile Editor. With the next poll cycle, the device will be contacted. | ||||
Ping does not work when running Console as a user without Administrative privileges on a Windows platform. Ping-related features will not work on the Console Client when running as a user without Administrative privileges:
|
||||
| Solution: | Run Console as a user with Administrative privileges. | |||
| When the EngineID is changed for a device using an SNMPv3 credential, Console will lose contact with the device and will not re-negotiate with the device to learn the new EngineID to re-establish contact with the device. This condition can be verified by attempting to contact the device using MIB tools. | ||||
| Solution: | If querying the device with MIB tools is successful, shut down and restart Console to re-establish contact with the device. | |||
| Importing a large number of devices (500 or more) will hang the application. | ||||
| Solution: | Divide the device import into smaller groups. While poll (Options) settings and the level of network traffic will affect the number of devices that can be imported without encountering this problem, blocks of 300 devices should import properly on systems using Console's default poll settings. | |||
| Auto Negotiation mode (ifMauAutoNegAdminStatus) cannot be managed using an SNMP set from NetSight Atlas Console (Port Properties, FlexViews, or MIB Tools). The set does not report a failure, but the set does not occur on the device. This problem was reported on firmware releases E9.0.7.0 and E9.0.7.2. | ||||
| Solution: | Use the device Local Management (CLI) to set Auto Negotiation mode. | |||
|
|
Attempting to perform other operations while the mouse pointer is shown as an hourglass causes a Java Exception, and requires closing and restarting Console. In particular, when deleting a large number of devices from the Properties tab, the mouse pointer is changed to an hourglass, but does not prevent you from performing other operations. | |||
| Solution: | Wait; do not perform other operations while the mouse pointer is an hourglass. | |||
|
|
The Refresh (Rediscover) feature shows a Completed status message before the refresh is actually finished. Any requests that you make before the refresh is done will either be blocked (indicated by a Tree is busy message) or could produce unpredictable results. | |||
| Solution: | If you are refreshing a large number of devices, check the CPU utilization and wait until it has settled down to 0% before requesting the next action. | |||
| (Linux and UNIX only) You cannot specify a range of pages when printing from tables on UNIX or Linux systems. If you select Print from the Table Tools popup menus, the resulting print settings window does not open to a sufficient size (and cannot be resized) to allow access to the page range fields. | ||||
| Solution: | For these systems, the only option is to print the entire table. | |||
|
|
(Linux only) Linux remembers if a window was previously maximized, and if the help window is maximized prior to being dismissed, the next time it is opened, the information does not completely fill the maximized window. | |||
| Solution: | Resize the window to restore a normal presentation. | |||
|
|
(Linux only) An initial Discover, performed immediately after install, stops prematurely. Console stops sending discover packets. Subsequent Discovers work properly. | |||
| Solution: | Wait 3-5 minutes following installation or system reboot before starting a Discover on Linux systems. | |||
|
|
The SNMPTrap Service synchronizes its timestamp with your system's clock when the service is launched, but does not recognize changing to or from Daylight Savings Time while running. This causes a one hour discrepancy in the timestamps for Traps and Informs that appear in Console after making the change. | |||
| Solution: | Stop and Restart the SNMPTrap Service when changing to or from Daylight Savings Time. | |||
|
|
(Windows2000, XP, 2003 Server) When the Console Server is run as a service, programs (GUI based executables) that have been configured to be launched as an Alarm Action do not launch correctly. The process starts, but the application's graphical user interface fails to open. | |||
| Solution: | Contact Enterasys GTAC for a workaround for this problem. | |||
|
|
Launching SSH from the right-click menu when a device is selected in the left panel does not work if there are multiple copies of the cygwin1.dll file on your system. | |||
| Solution: | Search for cygwin1.dll using the Windows Start > Find/Search facility and delete all but the most recent version. The most recent version should reside in x:\cygwin\bin, where x is the drive on which you have installed the cygwin distribution. | |||
|
|
Hovering the mouse pointer over an object Console's main window (long enough to display a tooltip) while there is another window open (Discovery, FlexView Properties, etc.) will occasionally cause the main window to assume focus (move to the front), thereby hiding the other window. This appears to be related to a known Java problem. | |||
| Solution: | Restore focus to the hidden window by moving the main window to one side and clicking on the hidden window or selecting the hidden window from the Taskbar. | |||
|
|
The Hide/Show Acknowledged Events button ( ) restores cleared events to the Events View. This button should not restore cleared events. Instead, it should only hide or show Acknowleged events that are logged after the table is cleared. |
|||
| Solution: | This problem will be corrected in a future release. | |||
|
|
The Authorization Group that appears in the title bar in the title of Console's main view is not updated when the group membership of the current user is changed in the Groups and Users tab of the Authorization and Device Access window. | |||
| Solution: | The title shows the correct Authorization Group when a new Console Client session is started. This problem will be corrected in a future release. | |||
|
|
Console may hang when attempting Retrieve Properties that cause the table to expand into thousands of rows. For example, Port Properties on several devices with a large number of ports in a single operation. It is not possible to define a finite limitation. The table size is related to your system's memory resources. | |||
| Solution: | Retrieve Properties for fewer devices at a time and/or increase the available memory. | |||
|
|
If Discover finds a device that already exists in the database, but the existing device is configured with a different profile, the device appears in the Discovered Devices table, noted as Exists with the current profile for the existing device within angle brackets. The same informaiton should appear in a tooltip, however that profile information is blank in the tooltip. Saving the device changes the existing profile to the one listed in the Profile column. | |||
| Solution: | This problem will be corrected in a future release. | |||
|
|
The MatrixV2 does not support sets to the MAU MIB. Therefore you cannot use the Console's Properties - Port View to configure ifMauEntry or ifMauAutoNegEntry MIB objects. | |||
|
|
Performing IP Range Discover for a large range of devices (greater than 200 devices) using only an SNMPv3 profile fails. The Status Bar reports "Timed Out." For example: 254 IPs Queried, 1 Completed, 224 Timed Out, 0 Discovered Devices. | |||
| Solution: | Increase the SNMP Timeout for Discover to be 5 seconds. Refer to How to Set Options - Discover for more information. | |||
|
|
Database conversion fails to complete. This may occur if you are trying to convert one of multiple databases that existed for Console 1.5 and specifically, if the database being converted was not the one that was last opened in Console 1.5. This is because the default profile for the last opened database is stored in the Atlas.ini file and, if that profile doesn't exist in the database being converted, the conversion will fail. | |||
| Solution: | Rename the Atlas.ini file (<install area>\Enterasys Networks\NetSight Atlas Console\Resources\Atlas.ini) in the Console 1.5 area before attempting to convert the database. It doesn't matter what name is chosen as long it is not Atlas.ini. |
|
|
(Windows2000, XP, 2003 Server) When the Console Server is run as a service, programs (GUI based executables) that have been configured to be launched as an Alarm Action do not launch correctly. The process starts, but the application's graphical user interface fails to open. |
|---|---|
| Solution: | Contact Enterasys GTAC for a workaround for this problem. |
|
|
(Linux Systems):
Red Hat Linux:
On SuSe Linux:
|
| Solution: | This problem will be corrected in a future release. |
| Attempting to Enforce values for MIB objects that are not supported in a device will report a Set Failure. In particular, this will occur when attempting to map a transmission priority to a traffic class in Matrix E5 or Vertical Horizon devices using FlexView Table Editor to map priority using the dot1dTrafficClass MIB. This also poses a problem for Matrix E1 devices. While the device does recognize the dot1dTrafficClass MIB, attempting to SET a value fails. This occurs because although these devices do support mapping of Priorities 0-7 to four separate Traffic Classes, the mapping is global to each Priority as opposed to each instance of that Priority. FlexView attempts to perform the mapping per instance (dot1dTrafficClass) and the SET fails. | |
| Some MIB tables may not work in FlexViews. Any column in a FlexTable that is instanced by TimeFilter may be left empty for devices whose firmware improperly implement TimeFilter. | |
| Solution: | The MIB tables may have time filters in them. MIB tables with time filters do not work in FlexViews. |
|
|
FlexViews may not present the correct order of bits for writeable, enumerated MIB objects. When a device returns bits for an enumerated object in the incorrect (reverse) order, the value will be displayed incorrectly in the FlexView. When the value appears incorrectly in a FlexView, it cannot be reliably used to edit and enforce values for enumerated OIDs on devices. You can verify whether the bits are returned in the correct order by examining the raw bit value, either through MIB Tools or by creating an expression column that displays the raw value for the column containing the Bits values. |
| Solution: | Verify the correct order of bits, as suggested, or use MIB Tools to edit and set writeable enumerated OIDs. |
|
|
Changes made to Unconnected Nodes or Removed by Synchronize submaps are not be retained when the map containing them is saved. |
|---|---|
| Solution: | This problem will be corrected in a future release. |
|
|
Background images cannot be tiled in Topology Manager. If you have converted maps from an earlier release of Console that contained a tiled background, the image will appear un-tiled in Topology Manager. |
|
|
Customized device icons are not supported in Topology Manager. If you have converted maps from an earlier release of Console that contain device icons that you changed in the prior release, they will appear in Topology Manager with the standard icon for the device type. |
|
|
Manually-created connections between map objects, other than devices, are not supported in Topology Manager. If you have converted maps from an earlier release of Console that contain these manually-created connections, they are dropped in the conversion and will not appear in Topology Manager. Manually created-connections between devices are converted. |
|
|
Labels associated with Symbols in maps that you've converted from an earlier release of Console are dropped in the conversion and will not appear in Topology Manager. The Symbol is treated as an Image, without a label. |
|
|
GoTo shortcuts in maps that you've converted from an earlier release of Console are dropped in the conversion and will not appear in Topology Manager. |
|
|
Topology Manager does not support background colors. If you have converted maps from an earlier release of Console that contained a background color, the background is dropped in the conversion and will not appear in Topology Manager. |
| False failure message when enforcing VLANs to a device (e.g., RoamAbout2) that does not support CreateAndWait and NotInService. The VLAN is created successfully. | |
| Solution: | Select the device in the left panel, access the VLAN tab and  (Retrieve) the Device VLAN information to verify that the VLAN was successfully created. |
|
|
On an X-Pedition router, a VLAN definition cannot be overwritten to an existing VID that is used by the System Static VLAN (e.g., SYS_L3_InterfaceName).
When such VLAN Definition is compared in the VLAN Details window, the following information is displayed:
Setting Name | VLAN Config | | Device Config The message is misleading because:
1. You cannot overwrite the System Static VLAN on a router.
|
| Solution: | MERGE the VLAN from the router into the VLAN Model. |
|
|
On an X-Pedition (SSR) router, you cannot directly change the PVID for a Basic Port from one non-Default VLAN to another non-Default VLAN.
For example, changing PVID 7 |
| Solution: |
Change the PVID to the Default VLAN and then change the PVID to the new non-Default VLAN.
For example, change PVID 7 |
|
|
On the X-Pedition Router, assigning a PVID (that exists on the device) in the Basic Port view and enforcing may incorrectly report an error, placing a red X in the PVID table cell. |
| Solution: | Refresh the table by performing a Retrieve to remove the X. |
| Console Device Manager will report a Set Fail when attempting to set a value for a MIB object that is not supported in the device. In particular, this will occur when attempting to map a transmission priority to a traffic class in Matrix E5 or Vertical Horizon devices using Bridge Extension Port Traffic Class window in Device Manager. With the exception of the VH-2402S-L3 and the VH-8G-L3 which only support one traffic class, these switches support only two Traffic Classes: 0 (Low) which maps to Priority 0-3 and 1 (High) which maps to Priority 4-7. Device Manager attempts to perform the mapping even though these switches cannot map transmission priorities to traffic classes. This also poses a problem for Matrix E1 devices. Although these devices do support mapping of Priorities 0-7 to four separate Traffic Classes, the mapping is global to each Priority as opposed to each instance of that Priority. Device Manager attempts to perform the mapping per instance (dot1dTrafficClass) and the SET fails. | |
When using the Configuration Upload/Download feature to receive configuration information from a device, a filename for an existing file must be specified; if a File Name is specified for a file that does not exist in the
TFTP root directory, the upload will fail reporting, tftpServerError(8). This occurs when the tftpd process has been started automatically with NetSight Atlas Console (the normal case) or if it is started from the Services Manager menu from the Windows Task Bar, or via /etc/rc2.d/S99NsTftp start on Solaris.
|
|
| You must specify an existing file, as the File Name in the Configuration Upload/Download window. If a particular file does not exist, create an empty text file with that filename in the
TFTP root directory that can be used with the Configuration Upload/Download.
As an alternative, you can start the For example:
|
|
|
|
(Solaris) Launching Device Manager from HPOV on Solaris fails. |
| Solution: | Edit two files:
|
|
|
Continuous (packet) capture is not supported for Matrix E1. Continuous capture packet download on the E1 does not wrap when buffer is full. Selecting continuous capture on an E1 behaves the same as stop when full. |
|
|
Packets using Cabletron Interswitch Message Protocol traffic are not decoded and the Default view in the RMON Packet Capture Buffer window is alwasy Hex/Ascii for these packets. |
|
|
Device Manager crashes when launched on a Linux host running on VMWare ESX-Server. |
| Solution: | This problem will be corrected in a future release. |
|
|
Matrix N Series (DFE) allow a maximum number of two historyControlEntries per port. The default configuration includes two entries for each port and attempting to create another will appear to be successful however, the index status cannot be set to valid. |
| MIB Tools will report a Set Failure with a No Such Name error when attempting to set a value for a MIB object that is not supported in the device. In particular, this will occur when attempting to map a transmission priority to a traffic class in Matrix E5 or Vertical Horizon devices using MIB Tools to map priority using the dot1dTrafficClass MIB. This also poses a problem for Matrix E1 devices. While the device does recognize the dot1dTrafficClass MIB, attempting to SET a value fails. This occurs because although these devices do support mapping of Priorities 0-7 to four separate Traffic Classes, the mapping is global to each Priority as opposed to each instance of that Priority. | |
| Closing MIB Tools with a drop-down list open (for example the IP Address or Community Name drop-down list) causes a Java exception in the Alarms and Events view of Console. This is a Java bug. | |
| Auto Negotiation mode (ifMauAutoNegAdminStatus) cannot be managed using an SNMP set from NetSight Atlas Console (Port Properties, FlexViews, or MIB Tools). The set does not report a failure, but the set does not occur on the device. This problem was reported on firmware releases E9.0.7.0 and E9.0.7.2. | |
| Solution: | Use the device Local Management (CLI) to set Auto Negotiation mode. |
|
|
Cabletron trap OIDs (1.3.6.1.4.1.52.0*) cannot be displayed in the MIB tree in MIB Tools. This branch in the MIB tree has been disabled to avoid naming conflicts. |
| Solution: | To see the trap description for a particular trap, type the OID for the trap into the Current Object field and press Enter. The description will be displayed in the Details panel. |
|
|
The enterasys-link-flap-mib.txt fails to load when the loadmibs script is executed. |
|---|---|
| Solution: | This problem will be corrected in a future release. |
| Links to topics selected in the Contents may not work correctly following a search operation. If you use the JavaHelp search to find a term, then return to the Contents and navigate to a topic, the viewer may take you to the wrong place in the topic. If the topic you select contains the term just sought using the search, the viewer will take you to the term instead of the topic you chose from the Contents. | |
| Solution: | Click the Search tab, clear the entry and type Return. Go back to the Contents tab and the navigation will work correctly. |
| Scrolling rapidly (using the arrow keys) through the Contents panel in the help and, less frequently, scrolling within a topic (right panel) will cause a Java Exception. This is related to a JavaHelp bug. | |
| Solution: | Use the scroll bar in the help topics or use mouse clicks to navigate in the Contents panel. |
| Printing help files from the Console Help viewer may cause the application to hang. | |
| Windows users should use Task Manager to end the
Console Help task. Solaris users should kill the Console Help process.
If you encounter this problem, print help files from a browser by accessing the NetSight Documentation Web page at
|
|
|
|
(Linux only) Linux remembers if a window was previously maximized, and if the help window is maximized prior to being dismissed, the next time it is opened, the information does not completely fill the maximized window. |
| Solution: | Resize the window to restore a normal presentation. |
| SmartSwitch 6000 with firmware version, 04.05.06 inserts hex Fs into the chassis
serial number. This causes an extra Grouped By/Chassis group to be created in the Console left panel.
For example when Fs are inserted into the serial number, the following two groups :
Grouped By
|_ SmartSwitch 6000 [00001D837BD7] (3)
| ||||
| Solution: | Upgrade firmware to a version that is fully supported with NetSight Atlas Console. | |||
| The Matrix E5 always reports TFTP firmware download as successful, even when the TFTP
firmware download fails because of a problem with the firmware filename.
A TFTP firmware download or TFTP configuration upload will fail if the length of the entry for the Last Filename is longer than the Full Image Path entry for the firmware being downloaded. The corruption is caused by remnants of the longer (earlier) filename.
For example, attempting to download firmware with a Full Image Path of |
||||
| Solution: | This problem will be corrected by firmware version 03.00.11. | |||
|
|
X-Pedition Routers running firmware revision E9.1.7 do not provide information about port auto-negotiation capabilities. As a result, the capabilities columns in the Port Properties view displays N/A for all of the capabilities columns for these devices. | |||
| Solution: | This problem will be corrected in a future revision of the firmware. | |||
|
|
Using NetSight Atlas Console or MIB Tools to set values for sysName, sysLocation, and sysContact on a Roamabout R2 is successful. However, those values are not persisted after resetting the device. | |||
| Solution: | Telnet to the device and, using Local Management navigate to the Network Configuration View and Save the configuration. |
Any other problems than those listed above should be reported to our Technical Support Staff.
Click here for a list of the IETF and Private Enterprise MIBs supported by NetSight Atlas Console as of its initial release. For information regarding the latest software available, recent release note revisions and changes to the supported MIBs, visit the NetSight Atlas Console section at the following Web site:
http://www.enterasys.com/support/manuals/netsight.html.
Additional (indexed) MIB documentation is also available at the following Web site:
http://www.enterasys.com/support/mibs
For information regarding the latest software available, recent release note revisions, or if you require additional assistance, please visit the Enterasys Support web site.
http://www.enterasys.com/support
PVID 8 will not work.