Installation guide

34
Release Notes for Catalyst5000 Family Software Release4.x
OL-2306-01
Open and Resolved Caveats in Software Release 4.5(5)
Workaround: Configure standby use-bia on the router interfaces for the HSRP (standby uses the
interfaces burned in address [bia]). (CSCdp51787)
• If you save a configuration file from a switch where Token Ring is not configured, and then apply
the saved configuration file to that same switch, it is safe to ignore messages about TRBRF and
TrCRF VLANs. These messages are caused by the default Token Ring VLAN configuration, which
is always present regardless of the specific configuration of the switch. (CSCdm92714)
• If you have multiple ATM fabric integration modules (WS-X5165) installed and you have more than
50 LECs configured on each module, a multiple-module software download to the modules can take
an excessively long time to complete. For this reason, we recommend that you download software
images one module at a time (by specifying the module number in the download command).
(CSCdk55355)
• On the Gigabit EtherChannel module (WS-X5410), if a host allowed on one secured port is moved
to another, previously unused secured port on the same module, the host cannot connect to the
network on the second port.
Workaround: Di sable port security on the first port, move the host to the second port, and then
reenable port security on the first port (if desired). (CSCdk31747)
• In some cases, after a switchover from the active to the standby supervisor engine, the SPAN
destination port might not function correctly. (CSCdk55360)
• Frame Priority is set incorrectly from Ethernet to FDDI. A new command, set option fddi-user-pri,
has been added to enable the priority field in the FDDI packets. The command requires FDDI
software release 3.2(1a) and supervisor engine software release 5.5(2) or later. This problem is
resolved in software release 5.5(2). (CSCdr42228)
• The Catalyst 5000 family switch is unable to resolve DNS names if the DNS server has more than
7 entries. (CSCdr808353)
• If a VLAN is cleared from a trunk port and spanning tree is disabled on the switch, STP BPDUs for
that VLAN are still received on the trunk port, and the switch in turn floods the BPDUs to all other
ports in that VLAN. This might lead to spanning tree instabilities and Fast EtherChannels getting
err-disabled. (CSCdr228643)