Caveats

•CSCdk01961

If you use VTP pruning with Fast EtherChannel, losing one connection on one high-speed link prevents pruning from working properly. This does not cause connectivity problems, but flood traffic is sent to the neighboring switch (which should drop such traffic, resulting in minimal degradation to network performance). Pruning still works in the neighboring switches.

The workaround is to disconnect the remaining link and then to reconnect both links to restore proper operation of VTP pruning.

•CSCdp08683

When a Catalyst 1900 or Catalyst 2820 switch is operating at the edge of a VTP domain and is subsequently configured for VTP transparent mode, trunk ports will not be in the correct pruning state.

The workaround is to reestablish the trunk after changing the VTP mode to transparent in one of these ways:

–Remove, and then reconnect the trunk cable to the switch.

–Disable, and then re-enable the trunk either by using the trunk off and trunk on commands or by using the Port Configuration Menu [S] Status of Trunk option.

–Reset the switch.

•CSCdk03911

After you select Auto-negotiate as the 100BASE-TX port duplex mode from the Catalyst 1900 Port Management page and click Apply, Auto-negotiateappears in the Actual field while the switch and the other device negotiate the duplex mode.

The workaround is to click the Port option on the switch manager menu bar to display the final duplex state of the port.

•CSCdj92758

If you try to upgrade the module firmware from the Catalyst 2820 Switch Manager and the Module (Slot A or B) TFTP Upgrade button is not on the Console and Upgrade Configuration page, the module firmware is corrupted.

The workaround is to stop the upgrade attempt from the switch manager. Use the management console to upgrade the module firmware.

•CSCdm69165

When the switch does not have its own IP address and is a cluster member, the Telnet link on the Catalyst 1900 or Catalyst 2820 Switch Manager Home page is disabled.

The workaround is to use the rcommand member-numbercommand from the command-switch CLI to Telnet to the switch.

•CSCdj55509

When a switch port is assigned to be the network port, unknown unicast address packets are only sent to that port. If an attached device, such as a server, is idle for longer than the specified address aging time value, the switch removes the device address from its address table. Therefore, if a network port is assigned, the switch does not forward any unknown unicast address packets destined to that device.

The workarounds are to

–Configure a static address for the server.

–Increase the address aging time to a value higher than the maximum idle time for the server.

Release Notes for the Catalyst 1900 and Catalyst 2820 Series Switches, Version 9.00.06

	OL-2901-01	9