Datasheet
27
Release Notes for Catalyst 4500 Series Software Release 7.x
OL-1983-28
Open and Resolved Caveats in Software Release 7.6(8)
• Disabling or enabling port negotiation does not work correctly if you specify more than a single port
or single range of ports. For example, if you enter set port negotiation 3/1,3/5-6 disable, ports 1
through 6 are disabled. This problem is resolved in software release 7.6(8). (CSCee52831)
• Doing a minimal entry (entering only the first part of a command syntax): set errdisable, set option,
and show cdp port mod/port, on the following commands results in either a missing key word or no
error message. This problem is resolved in software release 7.6(8). (CSCed92864)
• If you have an EtherChannel configured across modules, the EtherChannel configuration might
change after disabling PortFast, BPDU filter, and BPDU guard and then resetting the switch. This
problem is resolved in software release 7.6(8). (CSCee67595)
• An SNMP query for cvbStpForwardingMap might return an invalid port state. This problem is not
resolved by a power cycle, module reset, disabling and enabling the port, or swapping modules. This
problem is resolved in software release 7.6(8). (CSCee58481)
• If the default community strings are cleared, community strings configured by entering the set snmp
community-ext command do not work after resetting the switch. This problem is resolved in
software release 7.6(8). (CSCee66094)
• With a Supervisor Engine 2, when ports are added to an EtherChannel one port at a time, the
calculated value of a path cost might be incorrect. In some cases, the path cost value displayed with
the show spantree mistp-instance command is correct, but the path cost value displayed with the
show spantree statistics command might be incorrect. Miscalculated path cost values result in ports
going into the blocked state and create spanning tree topology discrepancies. This problem with the
MISTP path cost feature appears in all software releases up to and including release 6.4(10). This
problem is resolved in software release 7.6(8). (CSCee82347)
• A switch running software release 7.6(7) and rapid spanning tree (the switch is not the root bridge),
might log the following events in the syslog if it received a corrupt BPDU:
2001 Apr 07 23:40:16 %SPANTREE-2-LOOPGUARDUNBLOCK: Port 4/2 restored in MST instance 1
2001 Apr 07 23:40:28 %SPANTREE-2-LOOPGUARDBLOCK: No BPDUs were received on port 4/2 in
MST instance 1. Moved to loop-inconsistent state
2001 Apr 07 23:40:28 %SPANTREE-2-LOOPGUARDUNBLOCK: Port 4/2 restored in MST instance 1
2001 Apr 07 23:40:42 %SPANTREE-2-LOOPGUARDBLOCK: No BPDUs were received on port 4/2 in
MST instance 1. Moved to loop-inconsistent state
2001 Apr 07 23:40:42 %SPANTREE-2-LOOPGUARDUNBLOCK: Port 4/2 restored in MST instance 1
2001 Apr 07 23:40:59 %SPANTREE-2-LOOPGUARDBLOCK: No BPDUs were received on port 4/2 in
MST instance 1. Moved to loop-inconsistent state
2001 Apr 07 23:40:59 %SPANTREE-2-LOOPGUARDUNBLOCK: Port 4/2 restored in MST instance 1
2001 Apr 07 23:41:13 %SPANTREE-2-LOOPGUARDBLOCK: No BPDUs were received on port 4/2 in
MST instance 1. Moved to loop-inconsistent state
2001 Apr 07 23:41:13 %SPANTREE-2-LOOPGUARDUNBLOCK: Port 4/2 restored in MST instance 1
These symptoms are usually seen when there is more than one MST instance configured. This
problem is resolved in software release 7.6(8). (CSCee77039)
• In text configuration mode, with the switch configured to send a “cold start” trap when the switch
is reloaded, the switch does not send the trap after a reload. This problem does not appear when the
configuration mode is set to binary. This problem is resolved in software release 7.6(8).
(CSCee81130)
• With UplinkFast enabled, invalid dummy multicast packets might be sent out from the switch,
resulting in communication failure.
Workaround: Clear the ARP cache. This problem is resolved in software release 7.6(8).
(CSCee22626)