Filter
Top Products
7
Release Notes for the Catalyst 1900 and Catalyst 2820 Series Switches, Version 9.00.06
OL-2901-01
Caveats
• While performing a firmware upgrade, the switch might not respond to commands for as long as
1 minute. This is normal and correct. If you interrupt the transfer by turning the switch off and on,
the firmware could be corrupted. If this happens, follow the procedure in “Using the Diagnostic
Console” in the “Troubleshooting” chapter of the Catalyst 1900 Series Installation and
Configuration Guide or the Catalyst 2820 Series Installation and Configuration Guide.
Caveats
These sections describe open and resolved caveats in firmware versions 9.00.00 through 9.00.06.
Open Caveats
This section describes possible unexpected activity in firmware versions 9.00.00 through 9.00.06.
• CSCdj85607
When using Netscape Communicator 4.xx on PCs and Sun workstations, minimized, maximized and
resized pages of the Catalyst 1900 and Catalyst 2820 Switch Manager might not refresh properly.
The workaround is to click Reload to refresh the page.
• CSCdj95153
When using Netscape Communicator 4.xx on Windows 95, clicking Apply after making changes to
the Port Security Table page sometimes displays a blank page.
The workaround is to click Stop to redisplay the Port Security Table page with your saved changes.
• CSCdp16523
The Catalyst 1900 and Catalyst 2820 switches do not support the hidden-enable password. If the
switch inherits the command-switch hidden-enable password, the switch stores the password as an
unencrypted password.
The workaround is to assign a secret enable password to the command switch when your cluster
contains Catalyst 1900 and Catalyst 2820 member switches.
• CSCdj87375
Do not use these settings for the console port when upgrading the switch through the XMODEM
protocol: 9600 baud, 7 data bits, 2 stop bits, and even parity.
The workaround is to use other settings or the console port default settings (9600 baud, 8 data bits,
1 stop bit, and no parity).
• CSCdk01665
If you use bridge groups and Spanning Tree Protocol (STP) is disabled on a bridge group, the switch
does not forward the bridge protocol data units (BPDUs) received on any ports in the bridge group
to other members of the bridge group. If you are running STP on the rest of your network, network
loops might result if the switch connects to other switches.
The workaround is to disable STP on all bridge groups so that the switch forwards received BPDUs
if you want to use bridge groups with STP disabled. Assign at least one port to all bridge groups,
and then disable STP for each bridge group, using the Bridge Group Spanning Tree Configuration
menu (or CLI or SNMP). You can then reassign the ports to whichever group you wish.