Release Notes for Cisco Network Assistant 6.0 and Later
Available Languages
Table of Contents
Release Notes for Cisco Network Assistant 6.0 and Later Releases
Upgrading a Switch by Using Network Assistant
Minimum Cisco IOS Release Supported by Network Assistant
Cluster Limitations and Restrictions
Network Assistant Limitations and Restrictions
Community and Cluster Limitations
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Network Assistant 6.0 and Later Releases
These release notes include important information about Cisco Network Assistant 6.0 and later releases, and any limitations, restrictions, and caveats that apply to the releases.
Contents
This information is in the release notes:
- New Features
- System Requirements
- Devices Supported
- Downloading Network Assistant
- Upgrading a Switch by Using Network Assistant
- Minimum Cisco IOS Release Supported by Network Assistant
- Limitations and Restrictions
- Important Notes
- Open Caveats
- Obtaining Documentation and Submitting a Service Request
- Related Documentation
New Features
With Cisco Network Assistant 6.3, you can manage these devices:
Cisco Network Assistant 6.3 also includes the following enhancements:
- Support for Cisco IOS XE Denali 16.1.x. on Cisco Catalyst 3850 Series Switches and Cisco Catalyst 3650 Series Switches
- Integration of upgrade process with Automated Software Distribution (ASD)
- Support for Japanese version of Cisco Network Assistant
With Cisco Network Assistant 6.2, you can manage these devices:
With Cisco Network Assistant 6.1.0, you can manage these devices:
–
WS-C3650-24PS-E, WS-C3650-24PS-L, WS-C3650-24PS-S
– WS-C3650-24TS-E, WS-C3650-24TS-L, WS-C3650-24TS-S
– WS-C3650-48FS-E, WS-C3650-48FS-L, WS-C3650-48FS-S
– WS-C3650-48PS-E, WS-C3650-48PS-L, WS-C3650-48PS-S
– WS-C3650-48TS-E, WS-C3650-48TS-L, WS-C3650-48TS-S
– WS-C3650-24PD-E, WS-C3650-24PD-L, WS-C3650-24PD-S
– WS-C3650-24TD-E, WS-C3650-24TD-L, WS-C3650-24TD-S
– WS-C3650-48FD-E, WS-C3650-48FD-L, WS-C3650-48FD-S
– WS-C3650-48PD-E, WS-C3650-48PD-L, WS-C3650-48PD-S
– WS-C3650-48TD-E, WS-C3650-48TD-L, WS-C3650-48TD-S
– WS-C3650-48FQ-E, WS-C3650-48FQ-L, WS-C3650-48FQ-S
– WS-C3650-48PQ-E, WS-C3650-48PQ-L, WS-C3650-48PQ-S
– WS-C3650-48TQ-E, WS-C3650-48TQ-L, WS-C3650-48TQ-S
– SF500-24, SF500-24P, SF500-48, SF500-48P
– SG500-28, SG500-28P, SG500-28MPP, SG500-52, SG500-52P, SG500-52MP, SG500X-24, SG500X-24P, SG500X-48
– SF300-08, SF302-08, SF302-08MP, SF302-08P, SF302-08PP, SF302-08MPP, SF300-24, SF300-24P, SF300-24MP
– SF300-24PP, SF300-48, SF300-48P, SF300-48PP
– SG300-10, SG300-10MP, SG300-10MPP, SG300-10SFP, SG300-10P, SG300-10PP, SG300-20, SG300-28, SG300-28P
– SG300-28PP, SG300-28MP, SG300-52, SG300-52P, SG300-52MP
– SF200-24, SF200-24P, SF200-24FP, SF200-48, SF200-48P
– SG200-08, SG200-08P, SG200-10FP, SG200-18SG200-26,SG200-26P,SG200-26FP, SG200-50, SG200-50P, SG200-50FP
With Cisco Network Assistant 6.0, you can manage these devices:
– AIR-CAP1532I-A-K9, AIR-CAP1532E-A-K9
– AIR-CAP1532I-C-K9, AIR-CAP1532E-C-K9
– AIR-CAP1532I-D-K9, AIR-CAP1532E-D-K9
– AIR-CAP1532I-E-K9, AIR-CAP1532E-E-K9
– AIR-CAP1532I-F-K9, AIR-CAP1532E-F-K9
– AIR-CAP1532I-H-K9, AIR-CAP1532E-H-K9
– AIR-CAP1532I-K-K9, AIR-CAP1532E-K-K9
– AIR-CAP1532I-M-K9, AIR-CAP1532E-M-K9
– AIR-CAP1532I-N-K9, AIR-CAP1532E-N-K9
– AIR-CAP1532I-Q-K9, AIR-CAP1532E-Q-K9
– AIR-CAP1532I-R-K9, AIR-CAP1532E-R-K9
– AIR-CAP1532I-S-K9, AIR-CAP1532E-S-K9
– AIR-CAP1532I-T-K9, AIR-CAP1532E-T-K9
– AIR-CAP1532I-Z-K9, AIR-CAP1532E-Z-K9
CNA 6.0 also includes these enhancements:
- Multiple credentials can be entered at one single popup window to avoid multiple authentication popup windows while creating a community.
- Enhanced SSID creation for multiple access points using the Wireless Quick Start menu.
- Performance improvement in configuring various wireless parameters for multiple autonomous Access Points.
- Cisco logo in the menu bar to launch the Cisco.com website.
- New feedback button for sending feedback to the CNA alias.
System Requirements
The system requirements are described in these sections:
Installation Requirements
The PC on which you install Network Assistant must meet these minimum hardware requirements:
- Processor speed: 1 GHz
- DRAM: 1 GB
- Hard-disk space: 50 MB
- Number of colors: 65536
- Resolution: 1024 x 768
- Font size: small
These operating systems support Network Assistant:
- Windows 7 Enterprise (64-bit and 32-bit)
- Windows 7 Professional (32-bit)
- Windows 8 Professional (32-bit)
- Windows Vista (64-bit and 32-bit)
- Windows XP Professional, Service Pack 3 (64-bit and 32-bit)
- Windows 2008 (64-bit and 32-bit)
- Windows 2003 Server (64-bit and 32-bit)
- Macintosh OS X
Note To run Network Assistant on MAC OS X (10.7 Lion and above), follow these steps:
- From the System Preferences window, select Security and Privacy.
- From the Security and Privacy window, select the General tab and click Anywhere.
Devices Supported
Table 1 lists the devices that Network Assistant supports. It supports the Catalyst Express 500 devices only as community members; these devices cannot be cluster members.
Note The Topology view of Network Assistant supports Catalyst 65 00 switches. You cannot add these devices to a community or cluster, but you can start Device Manager for them from the Topology view.
Access Points
Cisco Aironet 350, 1100, 1200, and 1242 series. Network Assistant supports them only if they run a Cisco IOS image.
Note Network Assistant supports only autonomous access points. Access points that are managed by a wireless LAN controller are not supported.
Firewalls
Cisco PIX 515E firewalls. PIX firewalls do not support the Cisco Discovery Protocol, so they are not automatically shown as neighbors in the Topology view. They are shown only after you add them to a community by using a Create Community or Modify Community window. To see a PIX firewall link to another community member, you must add the link manually by selecting Add Link in a Topology popup menu.
Cluster Compatibility
This section describes how to choose command and standby command devices when a cluster consists of a mixture of Catalyst switches. When creating a device cluster or adding a devices to a cluster, follow these guidelines:
- When you create a device cluster, we recommend configuring the highest end device in your cluster as the command device.
- If you are managing the cluster through Network Assistant, the device that has the latest software release should be the command device.
- The standby command device must be the same type as the command device. For example, if the command device is a Catalyst 3750 switch, all standby command devices must be Catalyst 3750 switches.
Note Catalyst 4500 series switches cannot be configured as standby command devices.
Downloading Network Assistant
Note The Application Updates feature is currently not available.
To download a new version of CNA, follow these steps:
1. Go to this Web address: http://www.cisco.com/en/US/products/ps5931/index.html
2. You must be a registered Cisco.com user, but you need no other access privileges.
3. Click the Download Software link, and select the version you want to download.
4. Find the Network Assistant installer.
5. Download the Network Assistant installer, and run it. (You can run it directly from the Web if your browser offers this choice.)
6. When you run the installer, follow the instructions. In the final panel, click Finish.
For information on installing, starting, and connecting to Network Assistant, see Getting Started with Cisco Network Assistant at this site:
http://www.cisco.com/en/US/products/ps5931/prod_installation_guides_list.html
Updating Network Assistant
To update Network Assistant to a later release, follow these steps:
2. Choose Applications > Application Updates.
3. In the Authentication window, enter your Cisco.com username and password, and then click OK.
4. If an upgrade version is available, Network Assistant prompts you to confirm if you want to install the updates.
5. If the K9 agreement dialog box displays, accept the agreement and click OK.
6. In the Cisco End User License Agreement dialog box, click Yes to proceed.
7. In the EULA Details dialog box, click Accept, and then click OK. A dialog box displaying the progress of update is displayed.
8. In the Application Updates window, select Yes to install the latest updates.
9. In the Authentication window, enter your Cisco.com username and password.
10. When the update is complete, click Restart to restart Network Assistant.
Upgrading a Switch by Using Network Assistant
You can upgrade switch software in two ways by using Network Assistant:
Note Prior to doing a software upgrade, check if there is enough memory space is available to upgrade the device.
Minimum Cisco IOS Release Supported by Network Assistant
See the switch release notes for the minimum Cisco IOS software release for the devices that Network Assistant manages.
Limitations and Restrictions
You should review this section before you begin working with the device. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the device hardware or software.
These sections describe the limitations and restrictions:
- “Cluster Limitations and Restrictions” section
- “Network Assistant Limitations and Restrictions” section
Cluster Limitations and Restrictions
These limitations apply only to the Catalyst 4500 series switches:
- By default, clustering is disabled on the Catalyst 4500 series switches.
- You must assign an IP address to the Catalyst 4500 series switch if it is a cluster command switch candidate. If the switch is a cluster member candidate, you might not need to assign an IP address.
- By default, the HTTP server is disabled on the Catalyst 4500 series switch. To connect the switch to Network Assistant, you must enable the HTTP server on all cluster members.
- The HTTP port number on Network Assistant and the Catalyst 4500 series switch must match.
- A Catalyst 4500 switch can be a cluster member only if another Catalyst 4500 switch is the command device.
- By default, the Catalyst 4500 series switch is configured with five vty lines. If the switch (such as a cluster command device with multiple cluster members) is connected to Network Assistant, you must configure at least eight + n vty lines, where n is the number of vty lines used by other applications. You can configure a maximum of 16 vty lines.
- Create a switch virtual interface (SVI) to use for intracluster communication. The SVI must be in the no shut state.
This limitation applies only to the Catalyst 4500 series and Catalyst 3750, 3560, 3550, and 2970 switches:
- If a Catalyst 2900 XL or 3500 XL cluster command device is connected to a Catalyst 3550 or a 3750 switch, the command device does not find any cluster candidates other than the 3550 or the 3750 switch candidates. You must add the 3550 or the 3750 switch to the cluster to see other cluster candidates. (CSCdt09918)
This limitation applies only to the Catalyst 4500 series and Catalyst 3750, 3560, 3550, and 2970 switches:
- If both the active command device and the standby command device fail at the same time, the cluster is not automatically recreated. Even if there is a third passive command device, it might not recreate all cluster members because it might not have all the latest cluster configuration information. You must manually recreate the cluster if both the active and standby command devices simultaneously fail. (CSCdt43501)
- When the active device fails in a device cluster that uses Hot Standby Routing Protocol (HSRP) redundancy, the new active device might not contain a full cluster member list.
The workaround is to ensure that the ports on the standby cluster members are not in the Spanning Tree Protocol (STP) blocking state. See the “Configuring STP” chapter in the software configuration guide for more information about verifying port status. (CSCec31495)
This limitation applies only to the Catalyst 3750 and 3750-E switches:
On Catalyst 3750 and 3750-E switches, when running on-demand diagnostic tests on both the stack master and stack member switches, sometimes the tests execute only on the stack master.
– Execute the tests on the stack members first, and then run the tests separately on the stack master.
– Schedule the tests to run once on both the stack master and stack member switches.
This limitation applies only to the Catalyst 2955, 2950, and 2940 switches:
Network Assistant Limitations and Restrictions
These limitations apply to all the devices described in the “Devices Supported” section:
- Health Metrics feature is now available for multi core supported devices also. But, the metrics are still displayed for the single core only.
- CNA supports the standard ASCII character set. Do not enter characters from extended ASCII character sets in GUI fields for feature options.
- When CNA is managed over a VPN, the device data upload fails to appear on the Customer Active Advisor even though internet access is allowed. The device data upload fails only when the user skips the CCO user authentication process before connecting to the device in CNA.
- A red border appears around the text-entering area of some Network Assistant windows. The color of the border changes to green when text is entered. The colored border does not prevent you from entering text. (CSCdv82352)
- You cannot switch modes (for example, from guide mode to expert mode) for an open Network Assistant window. The workaround is to close the open window, select the mode that you want, and then reopen the Network Assistant window. For the mode change to take effect on any other Network Assistant window that is open, you need to close that window and then reopen it after you select the new mode. (CSCdw87550)
- If you open a window in which you can enter text, open another window, and return to the first window, right-clicking in the text field might make the cursor in this field disappear. You can still enter text in the field. (CSCdy44189)
- When the active device fails in a device cluster that uses HSRP redundancy, the new active device might not contain a full cluster member list.
The workaround is to ensure that the ports on the standby cluster members are not in the STP blocking state. See the "Configuring STP" chapter in the software configuration guide for information about verifying port status. (CSCec31495)
- In the Port Settings window, you must apply a change to some speed settings before you can change a duplex setting.
After you configure a speed setting, click Apply, and then configure a duplex setting. (CSCeh43889)
- When there are more than one neighbor devices of the same device type and they have same hostname, the Topology view displays only one neighbor device instead of displaying all the neighbor devices.
The workaround is to not have same hostname for more than one device. (CSCsb50280).
The Smartports window shows the NME-XD-24ES-1S-P EtherSwitch service module with two Mode buttons instead of one.
In the Modify VLAN window if you switch the vlan IDs of the isolated VLAN and the community VLAN and then click OK and Apply, these changes do not appear in the VLANs window.
The workaround is to do the same steps again. This time the changes take place.
Catalyst 4500 Series Switches
On Catalyst 4500 series switches, Network Assistant supports only the features shown in Table 2 .
These limitations apply to the Catalyst 4500 Series switches:
- In Network Assistant, some windows, such as VLAN, Hostname, and so on, might not open from the Front Panel view popup menu for Catalyst 4500 series switches.
The workaround is to close Network Assistant and restart it. (CSCef67553)
- You cannot see the PoE columns in the Port Settings window for Catalyst 4503, 4506, or 4507R switches that run Cisco IOS 12.2(20)EWA and have a WS-4548, WS-4524, or WS-4506-GB-T PoE line card.
The workaround is to upgrade the software on the switch to a later version of Cisco IOS. (CSCeh75133)
Community Limitations
These limitations apply only to communities:
- A community can contain up to 40 devices. This limit is enforced whenever you add devices to a community.
- CSCsd04956
The Topology view does not show the internal Gigabit Ethernet link between routers and the EtherSwitch service modules NME-16ES-1G and NME-X-23ES-1G.
- Changes to the topology or the network do not propagate across all open Network Assistant sessions connected to the same community. You see this inconsistency when multiple Network Assistant sessions are open on one desktop and they are pointing to the same community.
Open one Network Assistant session per desktop per community. (CSCeh53619)
- In the Topology view, the redundant link for an HSRP group is not shown. There is no workaround. (CSCeh54526)
- If a community has members that are connected to a member through a hub or a Gigastack module, the Topology view shows all the connections. However, if nonmembers are connected to a community member through a hub or a Gigastack module, the Topology view shows only the connection of the first nonmember.
- Accessing a community through a router running Network Address Translation (NAT) is not supported.
- When a device with a device ID that exceeds 40 characters is added to the community, its link disappears. The device ID is usually the hostname, but if a domain name is specified, the device ID is in the form hostname.domain-name. There is no workaround, other than to limit the size of the device ID to 40 characters or less. (CSCsi77210)
Cluster Limitations
These limitations apply only to clusters:
- When you add a new member with a username and password that is different from the existing cluster member usernames and passwords, Network Assistant produces an exception error because of an authentication failure.
The workaround is to add the new member without a username and password. When the new member is added to the cluster, remove the existing username and password from the Username and Password fields, enter a new username and password, and then apply it to all cluster members. (CSCdz07957)
- Changing the password or current authentication while Network Assistant is running causes HTTP requests to fail.
The workaround is to close all Network Assistant sessions and then to restart it. (CSCeb33995)
- When TACACS authentication is enabled only on a command device, member devices cannot be configured.
The workaround is to enable TACACS authentication on the member devices. (CSCed27723)
- When there are Catalyst 2950 and 2955 devices in a cluster, and you open 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:
- 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, 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)
- Hostnames and Domain Name System (DNS) server names with commas for a cluster command device, member device, or candidate device can cause Network Assistant to behave unexpectedly.
You can correct this by not using commas in hostnames or DNS names. Do not enter commas when also entering multiple DNS names in the IP Configuration tab of the IP Management window in Network Assistant.
- Access control entries (ACEs) that contain the host keyword precede all other ACEs in standard ACLs. You can reposition the ACEs in a standard ACL with one restriction: No ACE with the any keyword or a wildcard mask can precede an ACE with the host keyword.
- If Network Assistant loses IP connectivity to the switch and an action is performed in the IP Address window, a Java exception error occurs.
The workaround is to close and to reopen the IP Address window when connectivity is restored. (CSCee91784)
- When you reload a device by using Network Assistant, it saves the running configuration. If you want to reload without saving the running configuration, use the CLI. (CSCeh24259)
- If a dual-media port on a Catalyst 4500 switch, model WS-C4948 or model WS-X4506-GB-T, is configured to RJ-45 and you apply a Smartports port role, the port is changed to SFP, the default setting. The connection to the port is lost.
The workaround is to reconfigure the media type to RJ-45 through the Port Settings window. (CSCeh31699)
- If you open the Modify Port Settings or the Modify Port Mode window twice in succession from the Front Panel view by right-clicking a port, selecting Port Settings or VLAN from the popup menu, and repeating these actions for another port, the windows display the settings for the port that you selected first.
The workaround is to ensure that the Interface field in these windows applies to the port that you selected. Be sure to close these windows between port selections. (CSCei17154)
- After you perform a search, the TAB key moves the focus in the search results. If you press the TAB key enough to reach the end of the results, the next TAB keystroke moves the focus out of the search results and into the next-in-focus window on the Network Assistant desktop.
The workaround is to Press ALT-s to return to the search results. (CSCei68648)
- Network Assistant does not verify whether the VLAN and the native VLAN are the same on the access point and the switch port that is connected to the access point. VLAN differences might cause wireless connectivity problems when you use the Secure Wireless feature.
The workaround is to ensure that the VLANs and the native VLAN are the same on the access point and the switch port. (CSCsb77434)
Important Notes
These sections contain important notes related to Network Assistant:
- “Switches Running in VSS” section
- “Installation Notes” section
- “Compatibility with Cisco IOS” section
- “Cisco IOS Notes” section
- “Community Notes” section
- “Cluster Notes” section
- “Network Assistant Notes” section
Switches Running in VSS
Network Assistant does not manage switches that are running in VSS (Virtual Switching System). If a device is discovered running in VSS, Network Assistant won’t support the configuration of any features, and you might see unexpected results if you try to configure any features.
Installation Notes
These are the installation notes that apply to Network Assistant:
- When you start Network Assistant, Java determines whether the resources it needs are available. If they are not, Java displays the message Could not create Java Virtual machine, and the session ends. To overcome this problem, open the file C:\Program Files\Cisco Systems\CiscoSMB\Cisco Network Assistant\startup\startup.properties (the default installation path), and modify this entry:
Replace 1024m with a lower setting that does not exceed the available RAM. There is no way to foresee what value will work. Try 512m, and lower it further if necessary. You can use the dial peer tag range 2500 to 2999 out-of-band to define your own dial peers.
Compatibility with Cisco IOS
If you run Cisco IOS 12.2(25)SEE or later, Cisco IOS 12.2(25)SEG or later, or Cisco IOS 12.1(22)EA7 or later, you must run Network Assistant 4.0 or later.
Cisco IOS Notes
- When upgrading IOS on a switch stack using Network Assistant, one of the member switches reboots after the upgrade even if you select No when prompted to reload the switch after the image upgrade. With the latest available Cisco Catalyst 2960S switch image (Cisco IOS Release 15.2(2)E5), this issue is resolved and the switch does not reload when you choose No on the prompt to reload after an image upgrade.
Workaround is to use archive download-sw /overwrite command to manually configure it or use the image version Cisco IOS Release 15.2(2)E or later.
- 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 only use 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. After you upgrade to Cisco IOS 12.2(25)SE or higher, you can enable http or https separately from Telnet. (CSCdz01037)
- Catalyst 3750 or 3560 switches with a 16-MB flash memory can experience problems due to flash memory constraints, especially if they are using larger size images, such as c3750-ipservicesk9-tar, c3560-ipservicesk9-tar, c3750-ipbasek9-tar. or c3750-ipbasek9-tar images. These are the affected switches:
Catalyst 3560: WS-C3560-24PS and WS-C3560-48PS
Catalyst 3750: WS-C3750-24PS, WS-C3750-24TS, WS-C3750-48PS, WS-C3750-48TS, WS-3750G-24T, WS-C3750G-12S, WS-C3750G-24WS, WS-C3750G-24TS, WS-C3750G-16TD
The workaround for these switches is to use the corresponding lm images, such as the c3750-ipserviceslmk9-tar or c3560-ipserviceslmk9-tar images, which require less memory. In future releases, images are expected to grow more in size, requiring more need for the lm images.
Community Notes
- Config Export: If you want to use and manage the same community on multiple devices, you can copy your community xml file (for example EnergyWiseTest.xml) from one device to another. This file is stored in the following location:
– For OS X: $HOME/.networkassistant/communities
– For Windows: C:\Documents and Settings\<userid>\.networkassistant\communities
- This note applies to a community on all the devices described in the “Devices Supported” section.
All the devices for the topology of a community are derived from the “Cisco IOS CDP (Cisco Discovery Protocol)” table. Therefore, the Topology view shows duplicate devices when CDP discovers duplicate devices. This happens for a single device when you enter the show cdp neighbor command. Two devices appear: one with the actual hostname (for example, abc), the other with hostname.domainname (for example, abc.cisco.com).
Cluster Notes
This note applies to cluster configuration only on the Catalyst 3550 switches:
The cluster setup privileged EXEC command and the standby mac-address interface configuration command have been removed from the command-line interface (CLI) and the documentation because they did not function correctly.
Network Assistant Notes
These notes apply to Network Assistant configuration on all the devices described in the “Devices Supported” section:
– From the System Preferences window, select Security and Privacy.
– From the Security and Privacy window, select the General tab and click Anywhere.
- The HTTP server interface must be enabled to display the network assistant. By default, the HTTP server is enabled on the switch. Use the show running-config privileged EXEC command to see if the HTTP server is enabled or disabled.
If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch.
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
The network assistant uses the HTTP protocol (the default is port 80) and the default method of authentication (the enable password) to communicate with the switch through any of its Ethernet ports and to allow switch management from a standard web browser.
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.
- If you use Network Assistant on Windows 2000, it might not apply configuration changes if the enable password is changed from the CLI during your Network Assistant session. You have to restart Network Assistant and enter the new password when prompted. Platforms other than Windows 2000 prompt you for the new enable password when it is changed.
- Network Assistant does not display QoS classes that are created through the CLI if these classes have multiple match statements. When using Network Assistant, you cannot create classes that match more than one match statement. Network Assistant does not display policies that have such classes.1
- Within an ACL, you can change the sequence of ACEs that have the host keyword. However, because such ACEs are independent of each other, the change has no effect on the way the ACL filters traffic.
- In the Front Panel view or Topology view, Network Assistant does not display error messages in read-only mode for these devices:
– Catalyst 3550 member switches running Cisco IOS Release 12.1(6)EA1 or earlier
– Catalyst 2950 member switches running Cisco IOS Release 12.0(5)WC2 or earlier
– Catalyst 2900 XL or 3500 XL member switches running Cisco IOS Release 12.0(5)WC2 or earlier
In the Front Panel View, if the device is running one of the software releases listed previously, the device LEDs do not appear. In Topology View, if the member is an LRE switch, the CPE devices that are connected to the switch do not appear. The Bandwidth and Link graphs also do not appear in these views.
- To use the Network Assistant on Windows Vista, you must first install the Telnet utility. Unlike earlier versions of Microsoft Windows, Telnet is not installed by default. You install Telnet as you would other Window components, from the programs folder in the control panel. (CSCsj37409)
- To successfully install and use the Network Assistant on Windows Vista, install the Network Assistant application in a folder that has full access privileges for the Network Assistant user. Otherwise, unexpected behavior can occur. (CSCsj50074)
- After installing the Network Assistant on Windows Vista, a warning message might appear that says the program might not have installed correctly. If this occurs, perform the following steps:
1. Click What settings are applied?
2. Click What is program compatibility ?
3. Click Click to open the Program Compatibility Wizard ; then click Next.
4. Click I want to choose from a list of programs.
5. Click Cisco Network Assistant ; then click Next.
6. Click Do not apply a compatibility mode ; then click Next.
7. Check Disable visual themes ; then click Next. This option assures that the minimize, maximize, and close buttons display correctly. (CSCsj26429)
Windows Vista launches the Network Assistant and asks if the program ran properly. If the program did not run correctly, select No, and follow the onscreen prompts.
9. If the Network Assistant opened correctly, click This program installed correctly. Otherwise, select No, and follow the onscreen prompts.
- You should now be able to remove both access and data VLAN entries using Network Assistant. Earlier, removing either access or data VLAN entries (CSCvb89752) were not supported.
- Network Assistant now supports connecting to a device through HTTPS using TLS protocol. Earlier, Network Assistant could not connect to devices (TLS supported IOS) through HTTPS (CSCvb89695, CSCvf57426 and CSCvi29047).
- Network Assistant connects TLS enabled devices through HTTPS protocol only using Windows OS. This feature is not enabled on Mac OS.
Open Caveats
These sections describe the open caveats that could create possibly unexpected activity in this software release.
Unless otherwise noted, these caveats apply to all the devices described in the “Devices Supported” section:
The software upgrade on the Catalyst 3750-X switch might fail if you use Network Assistant to upgrade the switch.
The workaround is to upgrade the switch by using the CLI through the console.
On a Catalyst 3750-X switch, you cannot delete a directory containing hundreds of files by using the Files tab of the Maintenance > File Management window.
The workaround is to delete the files individually or in groups of 100 or less.
In Configuration Settings tab of the Configure > Ports > Port Settings window, you cannot set the speed for SFP+ ports on Catalyst 3750-X and 3560-X switches. The ports operate at 10 Gb/s.
The upgrade fails when you try to upgrade the WS-C3560CPD-8PT-S switch from Cisco IOS Release 12.2(55)EX2 to IOS Release 12.2(55)EX3 by using the Software Upgrade > Upgrade Settings window and selecting the Standard Mode.
The workaround is to select the Remote TFTP Mode option from the Software Upgrade> Upgrade Settings window.
When you select the Trap Managers tab of the Configure > Device Properties > SNMP Management window and check Enable SNMP, Enable Traps, and Send All Traps, and apply the changes, the changes are not saved. In this case it adds all the available types of traps.
The workaround is to create a trap manager with limited types of traps to send and you need to uncheck the Send All Traps checkbox.
When you use the Configure > Ports > EtherChannels > Create EtherChannels window to create an EtherChannel on an interface that has voice VLAN enabled, an error message is displayed, and the EtherChannel is saved without the interface details.
The workaround is to use the Configure > Switching > Voice VLAN window to change the setting to None on the specific interface before you create the EtherChannel.
The cluster to community conversion feature does not work when the password store feature is enabled.
The workaround is to disable the password store feature.
The Sync Stored Credentials with Cisco CCO window fails to display if you enter the wrong old credentials more than four times under these conditions:
1. You reset your CCO credentials on Cisco.com and launch Network Assistant.
2. You enter the new credentials in the Authenticate to Cisco CCO window, and the Sync Stored Credentials with Cisco CCO is displayed.
3. You then enter the community name in the Connect window, and click OK. If you exit and launch Network Assistant again, the Sync Stored Credentials with Cisco CCO window does not appear.
The workaround is to enter the valid device credentials, or to re-create your communities.
You cannot enable or disable the Routing Information Protocol (RIP) protocol by using the RIP tab in the Configure > Routing > Protocols window.
The workaround is to enable or disable RIP by using the CLI.
The software upgrade fails when you try to upgrade the switch by using the Software Upgrade > Upgrade Settings window and selecting the Standard mode.
The workaround is to upgrade the switch by using the CLI. See the switch release notes for information on upgrading the switch by using the CLI.
The software upgrade fails when you try to upgrade the switch by using the Software Upgrade > Upgrade Settings window and selecting the Remote TFTP Server mode.
The workaround is to upgrade the switch by using the CLI. See the switch release notes for information on upgrading the switch by using the CLI.
The output displayed in the uploaded configuration file for the show snmp command does not match actual CLI output.
Network Assistant produces an exception error when you try to configure MAC addresses by using the Configure > Switching > MAC Addresses window.
The workaround is to configure MAC addresses by using the CLI. See the switch software configuration guide for information.
Network Assistant produces an exception error when you try to configure the Enhanced IGRP (EIGRP) and Open Shortest Path First (OSPF) protocols by selecting the EIGRP tab and the OSPF tab in the Configure > Routing > Protocols window.
The workaround is to configure the EIGRP and OSPF protocols by using the CLI. See the switch software configuration guide for information.
If the EIGRP and OSPF protocols are not configured, and you click the Advanced button in the EIGRP tab of the Configure > Routing > Protocols window, the system stops responding.
You cannot upgrade the Catalyst 3850 switches by using the Software Upgrade> Upgrade Settings window and selecting the Standard Mode.
The workaround is to upgrade the switch by selecting the Remote TFTP Mode option from the Software Upgrade> Upgrade Settings window.
The online help does not appear in the VLAN windows when you access the VLAN feature in guide mode (Switching > VLANs).
The workaround is to use the VLAN feature in expert mode if you want to view the online help.
You cannot enter the TFTP server path when you use the Software Upgrade> Upgrade Settings window and select the Remote TFTP Mode option.
The workaround to use the TFTP mode in the Upgrade Settings window, is to run the TFTP server in the local machine.
The software upgrade using Cisco Network Assistant fails on Catalyst 3650 switches when using the Standard mode as well as the Remote TFTP Server mode. On Small Business switches, the upgrade fails when using the Standard mode.
The workaround is to upgrade the Small Business switches using the TFTP mode and the Catalyst 3650 switches using the CLI.
When upgrading the IOS on a switch stack using Network Assistant, one of the member switches reboots after the upgrade even if you select No in the dialog box that prompts you to reload the upgraded devices.
The workaround is to upgrade the switch by using the CLI through the console.
Immediately after opening Network Assistant, you observe that the startup screen flickers during the application startup process.
When you try to uninstall Network Assistant, the application prompts to navigate to the location where Java executable is available.
The work around is to locate the Java executable during the uninstallation process.
For Mac OS, the upgrade requires JRE 1.7+ to enable TLS protocol over HTTPS. Currently when you try to connect the device through HTTPS, it displays the following error. “Unable to connect. SSL Handshake process failed. The secure connection through HTTPS could not be established.”
These caveats apply to Cisco EtherSwitch service modules:
The Front Panel view on EtherSwitch service modules NME-16ES-1G-P, NME-X-23ES-1G-P, NME-XD-24ES-1S-P, and NME-XD-48ES-2S-P shows the EN-LED as not enabled.
When running Network Assistant with Cisco IOS Release 12.2(40) SE and later, you cannot enable EIGRP routing protocols using the IP Routing Protocols window in Network Assistant.
The workaround is to configure EIRGP by using the CLI.
You cannot upgrade the switch using.tar files by selecting the Remote TFTP Mode option from the Software Upgrade> Upgrade Settings window.
Resolved Caveats
These caveats were resolved in Network Assistant 6.3:
The LEDs on the Front Panel view of a Cisco Catalyst 2960-X switch display correctly now. Also, the software upgrade on the switch completes successfully.
All the switch members in a stack now display the LED port status accordingly.
Configuring VLAN using Network Assistant is resolved in Cisco IOS XE Release 3.6.6E, Cisco IOS XE Release 16.5.1 and Cisco IOS releases 15.2(5)E1, 15.2(6)E or later.
The Front Panel view of a Cisco Catalyst 2960-X-24TS-LL switch now displays on Network Assistant.
Network Assistant saves the port settings without any errors.
You can now remove both Data and Voice vlan MAC address from the Secure Address tab of the Configure > Security > Port Security window.
Network Assistant can now access devices through HTTPS with TLS protocol. The latest Cisco IOS images has TLS support.
Using Network Assistant, you can delete sticky MAC address for data VLAN on interfaces that are not configured with voice VLAN for a Cisco Catalyst 2960-X switch (WS-C2960X-48FPS-L).
Using Network Assistant, you can remove sticky VLAN, access and data VLAN entries.
The LED mode display on the Front Panel view of a WS-C2960X-24PD-L device displays LEDs correctly for connected ports.
The Reports > Inventory window now displays the software versions of a device with the following configuration (Model: WS-C2960-48TC-L, IOS version: Cisco IOS Release 12.2(55)SE11, Image: C2960-LANBASEK9-M).
The Modify Port Settings window now displays the details of a Cisco Catalyst 2960-X switch properly. On the Front Panel view of a WS-C2960X-24PD-L switch, right-click on the port and click Port Settings to open the Modify Port Settings window.
Network Assistant now supports Russian switch models for the Cisco Catalyst 3850 switch (WS-C3850R-48T, WS-C3850R-24T, WS-C3850R-48U, C3850R-48P)
MAC Addresses tables in the Configure > Switching > MAC Addresses window open without errors for a WS-C3560G-48TS-S switch.
The Smartports feature is now available under Configure menu.
Smartports feature is available for Cisco Catalyst 3850-XE switch.
The VLAN name for a Cisco Catalyst 3850 switch can be changed with Cisco IOS XE Release 3.6.7E and Cisco IOS releases 15.2(4)E5, 15.2(2)E7 & 15.2(6)E or later.
The uplink ports (Gigabit Ethernet interfaces) are now displaying properly in the list when trying to assign an ACL (Security > ACL) to the interfaces of a Cisco Catalyst 2960-X switch (WS-C2960X-48TS-L).
Network Assistant now supports WS-C4900M models.
Health Metrics feature is now available for multi core supported devices also.
Network Assistant supports new supervisor engine model (WS-X45-SUP8-E).
Network Assistant supports new power supply model (PWR-C45-9000ACV).
Network Assistant now supports Topology view.
Network Assistant connects TLS enabled devices through HTTPS protocol only using Windows OS. This feature is not enabled on Mac OS.
TLS v1.2 support has been verified using the below models and software versions:
Model: Cisco Catalyst 2960X-24TS-L, IOS version: Cisco IOS XE Release15.2.6E
Model: Cisco Catalyst 3850-48T-S and Cisco Catalyst 3850-24T-E, IOS version: Cisco IOS XE Release 16.3.5b
The front panel view of the Cisco IE 3000 / Stratix 8000 switch in Network Assistant displays the live or LED status appropriately.
Network Assistant supports Cisco Catalyst 3850-48PS stacked switch with Cisco IOS XE Denali 16.3.3.
Network Assistant displays the LED status and port settings correctly for the Cisco Catalyst 3850 switch.
Network Assistant now supports WS-C3850-24XS models.
Network Assistant now allows user to discover and add Aironet 1600i AP to community. Earlier Network Assistant displays “Unsupported Device Type: AIR-SAP1602I-S-K9 and cannot add the device to community” error message when the user tries to discover and add Aironet 1600i AP to community.
Network Assistant connects TLS v1 enabled devices through HTTPS protocol using legacy IOS or XE versions whereas the SSL protocol is disabled.
TLS v1 support has been verified using the below device types and software versions:
Model: Catalyst 3750 V2 24PS, IOS version: Cisco IOS Release15.0(2)SE11
Model: Catalyst 3850 48P, IOS version: Cisco IOS XE Release 3.7.4.E
Model: Aironet 1600i, IOS version: Cisco IOS Release 15.3(3)JF1
Network Assistant now supports Russian switch models for the Cisco Catalyst 2960 switch (WS-C2960R+24TC, WS-C2960R+24PC, WS-C2960R+48TC, WS-C2960R+48PST, WS-C2960RX-48FPS, WS-C2960RX-48LPS, WS-C2960RX-48FPD, WS-C2960RX-48LPD, WS-C2960RX-48TS, WS-C2960RX-24TS, WS-C2960RX-24PS).
Network Assistant now supports WS-C3850-12XS models.
These caveats were resolved in Network Assistant 6.0:
The software upgrade now works when you try to upgrade the switch by using the Software Upgrade > Upgrade Settings window and selecting the Standard mode.
In the Front Panel view, the port numbers are no longer jumbled, and the connected ports are indicated by the green color.
These access points are now supported:
The software upgrade now works when you try to upgrade the switch by using the Software Upgrade > Upgrade Settings window and selecting the Standard mode or Remote TF.TP Server mode.
Network Assistant now allows you to configure more than one address in the Maximum Address Count field under Port Security.
When you use the Configure > Switching > Stack Settings window, change the priority, and save the configurations, the new values take effect.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
Related Documentation
This online document provides complete information about Network Assistant:
Getting Started with Cisco Network Assistant
http://www.cisco.com/en/US/products/ps5931/prod_installation_guides_list.html
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)