50 Minuteman Rd.
Andover, MA 01810
(978) 684-1000

CUSTOMER RELEASE NOTES

Enterasys NetSightTM Atlas Console
 Version 1.5.1
September 2004

INTRODUCTION:

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.

NetSight Atlas Console provides a collection of software tools that can help you manage networks of varying complexity. 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 the NetSight Atlas Console and a suite of plug-in applications.

NetSight Atlas Console

Console serves as a control panel for integral Atlas functions and optional plug-in applications. It lets you monitor device status, define network configuration, and automate troubleshooting tasks.

NetSight Atlas Console Features

Discovery
Discovery populates the Console database, discovering devices based on Subnet address or IP range. The discovered devices can be saved to the database, where they are automatically placed in one or more system-created device groups. The system-created device groups sort the devices into appropriate product families, subnets, etc.
Device Groups, User-defined Groups
By default, device groups are created by product families such as Matrix, Vertical Horizon, X-Pedition, etc. In the left panel tree, groups appear as folders containing devices. You can create your own groups organized to show your network in a way that makes sense to you. As an example, you can define a group for a building, or a sub-group within the building as a floor or even another sub-group for a closet. You can create groups based on departments, engineering, sales, etc., or even create groups based on the subnet.
Maps and Icons
Maps let you expand your view of the devices in the tree, making it easier to visualize their network layout. They allow you to arrange your networks in a way that is less abstract, graphically depicting links between devices, and showing device groupings. You can also import maps created in Spectrum Element Manager 2.3, and NetSight Element Manager 3.0 and 3.1. (Windows only; this feature is not available on Linux or UNIX systems).
Device icons provide a graphical representation of the device and its status. Color-coded arrows provide a visual indication of the status of the device, up or down. You can also change the image (GIF image file) that you want to represent a particular device.
FlexViews
NetSight Atlas Console provides pre-defined views of the network devices. These views provide information and configuration capabilities across the entire system. In addition, NetSight Atlas Console provides the capabilities to create your own FlexViews or modify and filter those provided with Console. The FlexView tables can be filtered, searched, and sorted, making it possible to view specific network conditions: for example, the top ten instances of an object such as the Highest CRC count on ports or the highest packet transmissions by port.

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.

MIB Tools
MIB Tools lets you examine the MIBs supported by an active device on your network and change the value of a writable MIB object. You can use the MIB Tools window to contact a device, view its supported MIBs, query the device for MIB values, and set a new value for a MIB object at the device.
VLAN Tools
The VLAN tools provide a system-wide deployment of VLAN configuration and monitoring capabilities. Use them to create VLAN configuration parameters that are deployed to multiple devices or groups of ports easily and in an automated fashion.
Compass
Compass is where you can search for information about end-users or computers. It answers questions such as: Where is this IP address in the network? Where are all members of this IP subnet in the network? Which users are authenticated on this switch, in this building, in the entire network? Where is user Bob Smith logged on currently? Answers to these types of questions help network administrators with information about users and where they are connected. In today's mobile work force it is imperative to be able to find information about users quickly.
Alarms and Events
The alarms and events feature of NetSight Atlas Console can help to make you aware of a variety of situations that demand your attention. The information available from Alarm and Event tabs can be exported, printed, searched, filtered, and sorted. NetSight Atlas Console also provides configuration tools that let you add and customize Alarm and Event tabs and let you trigger e-mail notification or launch an application for certain alarms, events, and traps.
NetSight Atlas Automated Security Manager
NetSight Atlas Automated Security Manager combines the features of a comprehensive intrusion detection system, such as Enterasys' Dragon Intrusion Defense System, with NetSight Atlas Compass' search capabilities to provide an effective defense against threats to your network's security. The Automated Security Manager can be configured to automatically disable the source of a threat or, when NetSight Atlas Policy Manager is installed, apply a Quarantine policy.
Device Manager
Provides status and administrative tools to help you manage the devices in your network.
HP OpenView - Network Node Manager Integration
You can integrate NetSight Atlas Console with Hewlett-Packard's HP OpenView Network Node Manager (NNM), versions 6.1 or 6.2 software. This feature lets you launch NetSight Atlas Device Manager from a device in NNM.

NetSight Atlas Plug-In Applications

These are optional applications that can be launched from the Console and take advantage of suite-wide options. Each plug-in application serves to facilitate specific network management tasks. Plug-in applications available with Atlas include:

It is recommended that you thoroughly review these release notes prior to the installation or upgrade of this product.

SOFTWARE CHANGES AND ENHANCEMENTS

The following restrictions and limitations have been removed for this release of NetSight Atlas Console:

The problem of matching only the last (alphabetically listed) phrase when comparing Custom Alarm Criteria has been corrected.
SSR trap information now appears correctly in the Console Event View.
(Linux only) The problem of re-processing Syslog/Trap information that had already been processed when Console is relaunched has been corrected.
Incident numbers now appear correctly in the Automated Security Manager tab in Console's Events View.

Software Enhancements

The following enhancements have been implemented in this release of NetSight Atlas Console:

SYSTEM REQUIREMENTS

Supported Platforms

The system requirements for operating NetSight Atlas Console are listed here.

PRODUCT FIRMWARE SUPPORT:

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

Devices

NetSight Atlas Console supports up to 1500 devices. SNMP must be configured on your devices to allow them to be managed by NetSight Atlas Console.

  NOTE: The 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.

INSTALLATION INFORMATION:

NetSight Atlas Console can be installed on the following platforms:

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/.

  NOTE: Any pre-defined FlexViews that you modified and saved in a prior installation of Console (either updating from a prior release or re-installing the same release), will be overwritten with this installation. However, as part of the installation, your modified FlexViews are retained in the <install area>/Enterasys_Networks/NetSight_Atlas_Console/backup/FlexViews directory.

  CAUTION: MIBs that you have added to the <install  area>/Enterasys_Networks/NetSight_Atlas_Console/Resources/mibs directory will be deleted during installation (either updating from a prior release or re-installing the same release). They are not preserved by the install program.

You should save these MIBs to a safe area and add them again after installing. Refer to How to Add MIBs to NetSight Atlas Console.

Upgrading Console

If you are upgrading from a prior version of NetSight Atlas Console, your upgrade includes an evaluation copy of Automated Security Manager that you can try for 30 days. If you decide to convert an evaluation copy of Automated Security Manager at the end of the evaluation period, you should contact your Enterasys Networks Representative to purchase the software and receive a License Key.

Evaluation Copy

When you install NetSight Atlas Console, you can select to install a 30-day Evaluation Copy. The evaluation copy installs NetSight Atlas Console and Automated Security Manager.

Evaluation periods for Console and Automated Security Manager (ASM) are activated separately. The evaluation period for Console starts when it is launched for the first time and expires 30 days later. The evaluation period for ASM starts the first time ASM is launched from Console's Applications menu and expires either 30 days later or with the expiration of the Console evaluation period, whichever occurs first.

To convert from an evaluation copy of NetSight Atlas Console or NetSight Atlas Console with Automated Security Manager 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.

HP OpenView Network Node Manager

NetSight Atlas Console supports versions 6.1 and 6.2 of Hewlett-Packard's HP OpenView Network Node Manager (NNM) software.

CONFIGURATION CONSIDERATIONS

NetSight Atlas Console

  1. NetSight Atlas Console includes an SNMP trap daemon that must be the only trap daemon running on your system. If you are running the OS trap daemon on your system, you must shut it down before launching the Console.
    1. Open Services window on your system (on Window2000 or NT systems - Control Panel > Services -- on Windows XP - Control Panel > Administrative Tools > Services).
    2. Scroll down to find the SNMP Trap Service in the list.
    3. Right click on the trap service and select Stop from the right-click menu.
    4. Right click on the trap service again and select Properties from the right-click menu.
    5. In the Properties window, set the Startup Type for the SNMP Trap Service to Manual.
    6. Close the Properties and Services windows.
    7. Open the Task Manager and check to be sure that the process is not running.
    8. Close the Task Manager.
  2. 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). Set your display Properties > Appearance > Color Scheme to something other than a black background during installation.
  3. NetSight Atlas Automated Security Manager 1.1.1 requires NetSight Atlas Console version 1.5.1.

WindowsTM 2000

  1. You should disable the Guest account when running NetSight Atlas Console on a WindowsTM 2000 host system. Windows 2000 allows a user without an account on the machine to login using the Guest account. This is a potential security problem.

Devices

  1. NetSight Atlas Console supports secure command line connections to devices using Secure Shell (SSH). Refer to the specific device user reference manuals for configuration information related to SSH.
      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.
  2. Compass resolves IP addresses to MAC addresses using information from router MIBs (ipNetToMediaTable, ipCidrRouteTable, and ipRouteTable), but only if devices that can be modeled as a switch or a router (e.g., Matrix N7 and DFE) are created in the Console database using the router's IP address. Compass cannot query information from the router MIBs unless devices are created using an IP address for the router interface.

OPERATING SYSTEM PATCHES

Before installing NetSight Atlas Console on the UNIX platform, be sure to install the latest patches for your operating system. You can download the most recent operating system patches from http://sunsolve.sun.com/.

KNOWN RESTRICTIONS AND LIMITATIONS

The known restrictions and limitations for this release of NetSight Atlas Console are listed below. Solutions for these restrictions and limitations are noted, if available.

Install/Uninstall

Problem 1: (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 NT/2000/XP system requirements are met prior to installing NetSight Atlas Console.
Problem 2: (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.
Problem 3: (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.
Problem 4: (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.
Problem 5: (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.
Problem 6: 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.
Problem 7: 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.
Problem 8: (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...
tail: `-1' option is obsolete; use `-n 1'
Try `tail --help' for more information.
Console14_9.bin: line 330: [: `)' expected, found -z
WARNING! The amount of /tmp disk space required and/or available
could not be determined. The installation will be attempted anyway.
Extracting the JRE from the installer archive...
Unpacking the JRE...
Extracting the installation resources from the installer archive...
Solution: This is a problem with the install program and the messages can be ignored.
Problem 9: When upgrading to Console 1.5, you must install Console 1.5 directly over Console 1.4. In other words, do NOT uninstall Console 1.5 first and then install Console 1.4. (When you install Console 1.5, it will automatically uninstall Console 1.4.) Otherwise, the snmptrapd.conf file won't be saved.
Solution: If you have already uninstalled Console 1.4 first and then installed Console 1.5, you must re-configure the snmptrapd.conf file and then restart the SNMPTrap daemon process.
Problem 10: If you are using the Solaris or LINUX platform, the text panel for supplying the Dragon EMS IP addresses does not accept input.
Solution: After the product is installed and launched, use the Tools > Options feature to supply the Dragon EMS information.

NetSight Atlas Console

General

Problem 1: The Sort, Filter, and Find Toolbars cannot be isolated vertically. When you try to drag a bar vertically, the bar gets bigger but 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.
Problem 2: 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
  |_ Chassis
    |_ SmartSwitch 6000 [00001D837733] (2)
      |_ 172.16.34.5

      |_ 172.16.34.7
    Matrix E7 [00001D837733] (1)
       |_ 172.16.34.6

  NOTE: The serial number is the same for both groups.

Solution: Examine the serial number associated with each chassis to determine when multiple groups represent the same chassis.
Problem 3: 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.
Problem 4: (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.
Problem 5: Device List > Import From File operations fail if the device list includes values with <space> characters (e.g. "authpwd=pass word" vs. "authpwd=password").
Solution: 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.
Problem 6: 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.
Solution: 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.
Problem 7: Sorting the left-panel tree while devices are being added to or removed from groups causes the devices to stay in the wrong groups.
Solution: For the devices that are in the wrong groups, select the devices in the Properties tab and use the Add Devices to Group option available from the right-click menu.
Problem 8: Ping does not work when running Console as a user without Administrative privileges on a Windows platform. Ping-related features will not work when running Console as a user without Administrative privileges:
  • Discovery using Ping
  • Device operational status cannot be determined for devices with their Poll Type set to Ping only (set Poll Type to SNMP)
  • Ping-related Compass functions
Solution: Run Console as a user with Administrative privileges.
Problem 9: 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.
Problem 10: (Windows only) NetSight Atlas Console's desktop icon appears with a white border.
Solution: The Windows icon cache must be refreshed as follows:
  • Right click on your desktop and select Properties to open the Display Properties window.
  • Select the Appearance tab.
  • Click Advanced.
  • Select Icon from the drop-down Item list.
  • Set the Size to 31 and click OK.
  • Click Apply in the Display Properties window.
  • Repeat steps 3, 4, and 5, but this time restore the Size to 32.
  • Click OK in the Advanced window and in the Display Properties windows.
Problem 11: 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.
Problem 12: 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.
Problem 13: 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.
Problem 14: When discovering a large range of the network (over 100 devices) across an XSR router, not all IP addresses are discovered. The problem is the number of ARP cache entries that the XSR router can hold.
Problem 15: 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.
Problem 16: 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.
Problem 17: (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.
Problem 18: (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.
Problem 19: The Length of SNMP Timeout option should not be set to a value greater than 20. Although any value can be entered, 20 (seconds) is the maximum timeout that should be specified in Console's Status Polling Options Window. While entering a value greater than 20 appears to be successful, Status Polling actually reverts to the default timeout of 3 seconds without any notification.
Solution: Do not enter a value greater than 20 (seconds) for a Status Polling timeout.
Problem 20: (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.
Problem 21: 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 and Automated Security Manager after making the change.
Solution: Stop and Restart the SNMPTrap Service when changing to or from Daylight Savings Time.
Problem 22: There are multiple profiles with the same name in the Profile Editor, and the duplicates cannot be deleted.
Solution: Create a new profile to replace the profile that has duplicates. Go to the Access radio of the Properties view and change the profile of all devices using the duplicate profile to use the new profile you created. Delete all instances of the previous profile.

Alarms and Events View

Problem 1: When running NetSight Atlas Console an a system using a FAT32 file system, any traps that are received do not appear in the Event view Traps tab until the trap file is closed, either by an snmptrapd stop, restart, or when the file rolls over to a new file.
Solution: This problem does not exist on an NTFS file system and will be fixed for FAT32 systems in a future release of NetSight Atlas Console.

FlexViews

Problem 1: 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.
Problem 2: 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.
Problem 3: 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 Menthols to edit and set writeable enumerated OIDs.
Problem 4: A query for a FlexView that references an invalid or unavailable value (using the Instance Column feature) will cause the entire query to fail. The Instance Column feature allows using the value returned in the referenced column as the instance for the MIB object selected for a column.
Solution: Correct or remove the incorrectly referenced Instance Column.

Map View

Problem 1: Imported maps do not retain certain properties: the outline width on shapes and the underline in underlined text.
Solution: Apply properties from those available with NetSight Atlas Console, after the map is imported.
Problem 2: (Windows only) While importing a Spectrum or NetSight Element Manager map into Console, the discover fails. In addition, you can no longer add a device to the tree using Add Device (right-click menu option).
Solution: Element Manager allowed the creation of map device icons that did not have an IP address or community name, using the Edit > Paste Special (No IPs) feature. These devices have a gray background and “N/C” as a caption. Remove any of these devices from your Element Manager maps before importing them into Console. Relaunching the application restores use of the Add Device right-click menu option.
Problem 3: Copying or cutting a group from one location in the tree and pasting it to a new location fails to retain the map associated with the group.
Solution: This feature will be added in a future release.
Problem 4: Importing a SPEL/EMAN map will add devices to the Console database, regardless of the current user's ability to add devices (Add Device setting in the Authorization Configuration for the group where the current user is a member). However, once added to the database, access is determined by the current profile associated with the imported devices and the privileges granted to the current user.
Solution: This will be resolved in a future release.
Problem 5: (Imported Maps only) Double clicking the GoTo Map icon does nothing. This can occur when an imported map contains a GoTo Map icon, whose target map does not exist in the database. There is no message indicating that the target cannot be found.
Solution: Delete the GoTo Map icon and recreate it with a valid target.
Problem 6: When printing maps, the background colors and images in maps are not printed.

VLAN

Problem 1: 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  (Retrieve) the Device VLAN information to verify that the VLAN was successfully created.
Problem 2: Sorting the left-panel tree while retrieving data in the Device radio of the VLAN tab causes the button state to transition to a green arrow even though the retrieve is still in progress.
Solution: Before executing a Sort on the tree, insure that any retrieve operations are complete. Similarly, insure that any sort operations are complete before executing a Retrieve.
Problem 3: 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
==================+=============+====+===============================
VLAN Name         | Not Defined |    | SYS_L3_InterfaceName
VID               | 3           |    | 3
Write To Device   | N/A         | != | Undefined VLAN will be removed
                  |             |    | on enforce

The message is misleading because:

1. You cannot overwrite the System Static VLAN on a router.
2. Since the VLAN Definition with VID=3 is not defined in a VLAN Model the Enforce operation does not make sense.

Solution: MERGE the VLAN from the router into the VLAN Model.
Problem 4: 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   PVID 8 will not work.

Solution: Change the PVID to the Default VLAN and then change the PVID to the new non-Default VLAN.

For example, change PVID 7   PVID 1  PVID 8.
Problem 5: 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.

Device Manager

Problem 1: 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.
Problem 2: 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.
Solution: 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 tftpd process from the command line with a -c option. When started with the -c option, tftpd is allowed to create files if they do not already exist. tftpd is located in the Enterasys_Networks/NetSight_Atlas_Shared/bin directory in the NetSight Atlas Console install area.

For example:

  1. Stop tftpd from the Services Manager.
  2. Navigate to the Enterasys_Networks/NetSight_Atlas_Shared/bin directory.

    Solaris:
    cd <install area>/Enterasys_Networks/NetSight_Atlas_Shared/bin

    Windows:
    cd <install area>\Enterasys Networks\NetSight Atlas Shared\bin

  3. Restart tftpd using the -c option.

    tftpd -c

MIB Tools

Problem 1: 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.
Problem 2: 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 Console tab of the Alarms and Events view. This is a Java bug.
Problem 3: 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.
Problem 4: 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.

Help System

Problem 1: Links to topics selected in the Contents will 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: Return to the Search tab, clear the entry and click Search. Go back to the Contents and the navigation will work correctly.
Problem 2: 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.
Problem 3: Printing help files from the Console Help viewer may cause the application to hang.
Solution: Windows users should use Task Manager to end the Console Help task. Solaris users should kill the Console Help process.

Print help files from a browser by accessing the NetSight Documentation Web page at http://www.enterasys.com/support/manuals/netsight.html, or by printing the .html files in the NetSight Atlas Console\docs directory.
Problem 4: (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.

Device Firmware

Problem 1: 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
   |_ Chassis
     |_ SmartSwitch 6000 [00001DFFFF837BFFFFD7] (2)
       |_ 172.16.34.11  This board running FW 04.05.06
       |_ 172.16.34.12  This board running FW 04.05.06

     |_ SmartSwitch 6000 [00001D837BD7] (3)
       |_ 172.16.34.13  This board running FW 04.10.22
       |_ 172.16.34.10  This board running FW 04.11.06
       |_ 172.16.34.13  This board running FW 05.00.49

  NOTE: The serial number is the same, with the exception of the inserted Fs.

Solution: Upgrade firmware to a version that is fully supported with NetSight Atlas Console.
Problem 2: 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 firmware/03.00.07 when the Last Filename is images/E5/Lowrider/03.00.06 results in a corrupted filename of firmware/03.00.07r/03.00.06. The r/03.00.06 portion of the corrupted filename is a remnant of the Last Filename.

Solution: This problem will be corrected by firmware version 03.00.11.
Problem 3: 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.

Any other problems than those listed above should be reported to our Technical Support Staff.

SUPPORTED MIBs

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

IMPORTANT URLS:

The following Enterasys URLs provide access to NetSight software products and product information. *Software license keys are version dependent and will only operate with the version of software related to the license key.

GLOBAL SUPPORT

By Phone: (603) 332-9400
By Email: mailto: support@enterasys.com
By Web: http://www.enterasys.com/support
By Fax: (603) 337-3075
By Mail: Enterasys Networks, P.O. Box 5005, Rochester, NH  03867-5005

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

ADDENDUM:

This section provides updated release information, available to current NetSight Atlas Console customers through the web update operation. Use the Check for Updates feature to determine if updates are currently available. The updates are listed by date, with the most recent updates listed first.

9/2004      P/N:  9038119-06   Subject to Change Without Notice    F0615-E