Installation guide

61
Release Notes for Catalyst5000 Family Software Release4.x
OL-2306-01
Open and Resolved Caveats in Software Release 4.3(1)
• When upgrading to software release 4.2(1) from a previous release, if you download the software
image file and then hot insert a second supervisor engine before you reset the system, the standby
supervisor engine does not synchronize with the primary. This problem is resolved in software
release4.3(1). (CSCdk31881)
• In some cases, a Catalyst 5000 family switch continues to send authentication failure traps to the
trap receiver when the switch is polled with the incorrect community string, even when you have
entered the set snmp trap disable auth command. This problem is resolved in software
release4.3(1). (CSCdk31799)
• When you open a Telnet session to a Catalyst 5000 family switch with a Supervisor Engine III,
TACACS+ might allow more than the configured number of login attempts. This problem is
resolved in software release4.3(1). (CSCdk24291)
• When Connectionless Network Service/Intermediate System-to-Intermediate System (CLNS/ISIS)
routing is enabled on a neighboring router, the Catalyst 5000 family switch might drop CDP packets,
preventing some neighboring devices from appearing in the show cdp neighbors command output.
This problem is resolved in software release 4.3(1). (CSCdk34032)
• In some cases, a router entry might incorrectly be aged out of the CAM table, preventing the proper
creation of MLS cache entries. This problem is resolved in software release 4.3(1). (CSCdk36438)
• Removing a 1000BASE-SX GBIC from the three-port Gigabit Ethernet module (WS-X5403) and
replacing it with a 1000BASE-LX/LH GBIC might cause the switch to reset. This problem is
resolved in software release 4.3(1). (CSCdk34862)
• In some cases, the output of the show cam mac_addr command does not correctly identify MLS
router entries with an “R” suffix in the display. This problem is resolved in software release 4.3(1).
(CSCdk38054)
• In some cases, when a cold start SNMP trap is generated, the network address portion of the trap
might incorrectly have the address 0.0.0.0. This problem is resolved in software release 4.3(1).
(CSCdk35617)
• In some cases, RMON traps contain incorrect utilization values, and utilization threshold alarms are
generated for ports that are disabled or are not connected. This problem is resolved in software
release 4.3(1). (CSCdk31934)
• In some circumstances, VLANs that are not allowed on a trunk port are listed incorrectly as “Vlans
in spanning tree forwarding state and not pruned” in the output of the show trunk command. This
problem is resolved in software release 4.3(1). (CSCdk31784)
• When enabling hardware broadcast suppression (using the set port broadcast mod_num/port_num
threshold% command) after enabling software broadcast suppression (using the set port broadcast
mod_num/port_num threshold_in_pps command) on a module that supports both, software
broadcast suppression is still enabled even though the output of the show port command indicates
that hardware suppression is enabled. This problem is resolved in software release4.3(1).
(CSCdk40580)
• In certain situations, after a switchover from the active to the standby supervisor engine, SNMP
module up/down traps are not generated when modules are inserted into or removed from the switch
until the switch is reset. This problem is resolved in software release4.3(1). (CSCdk45450)
• In some situations, spanning tree reconvergence might not be optimal after a failure when you
configure parallel Fast EtherChannel trunks for VLAN load-balancing using the set spantree
portvlanpri command. If one of the links in a channel fails (causing all VLAN traffic to pass over
the remaining channel) and is later reestablished, spanning tree will converge but load-balancing
does not occur. The second channel is placed in blocking mode. This problem is resolved in software
release 4.3(1). (CSCdk40289)