
12
Release Notes for Cisco Network Assistant 5.0 and Later
OL-12210-03
Limitations and Restrictions
• When there are Catalyst 2950 and 2955 devices in a cluster, and you start the QoS Queue window
to configure the devices, and then try to view the settings for other devices by using the device
selection menu, Network Assistant halts after 20 to 30 selections.
The workaround is to close and then to restart Network Assistant. (CSCed39693)
• A Java exception error occurs when Network Assistant is in read-only mode and you start the Port
Settings window. This only occurs on Catalyst 3500 XL, 2950 LRE, and 2900 XL switches.
The workaround is to open the Port Settings window with Network Assistant in read-write mode.
(CSCee25870)
• After a cluster member loses connectivity, the connect icon in the status bar incorrectly displays a
connect status instead of a disconnect status.
There is no workaround. (CSCee93695)
• If a Catalyst 2970 switch is a cluster command device and a Catalyst 3750 or 3550 switch is a cluster
member, enabling IGRP on a network on the Catalyst 3750 or 3550 switch creates a Premature EOF
error.
There is no workaround. Make the Catalyst 3750 or 3550 switch the command device.
After you click Finish, you see the commands that are actually applied to the device. (CSCeg60365)
• Zooming in or zooming out on the time axis of a bandwidth graph when the axis approaches noon
or midnight might cause the time increments to be incorrectly labeled.
Close the Bandwidth Graph window, reopen it, and zoom in or out again. (CSCej02776)
Community and Cluster Limitations
These limitations apply to both communities and clusters:
• Network Assistant fails when a device is running the cryptographic software image and the vty lines
have been configured with the transport input ssh and line vty 0 15 global configuration
commands to use only SSH. The workaround is to use the transport input ssh telnet and
line vty 0 15 global configuration commands to allow SSH and Telnet access through the vty lines.
(CSCdz01037)
• When the Link Graphs application has run for hours displaying packet drop and error information,
sometimes the X-axis crosses the Y-axis at a negative Y value instead of at Y= 0. This condition
occurs with all supported operating systems, browsers, and Java plug-ins. There is no workaround.
(CSCdz32584)
• After you click Apply or Refresh in the Simple Network Management Protocol (SNMP) window,
the window size changes. (CSCdz75666, CSCdz84255)
• When you enable log scaling for Link Graphs, the Y-axis scale becomes illegible. There is no
workaround. (CSCdz81086)
• If an access control list (ACL) is deleted from a device, all QoS classes on Catalyst 2970 and 3750
switches that use this ACL for traffic classification become unusable. The modification of these
classes to use any other traffic classification (match statement) fails. The workaround is to delete the
QoS class that uses the undefined ACL, and then to recreate it with the intended traffic classification
(match statement). (CSCed40866)
• When an Open Shortest Path First (OSPF) summary address is added for a 10.x.x.x network, a
Windows exception error sometimes occurs.
The workaround is to add the address by using the router ospf <process-id>, area <area-id>, and range
<address> <mask> configuration commands. (CSCed87031)
Komentarze do niniejszej Instrukcji