27
Release Notes for 07.8.04 Software Fixes
29670 If you enable 802.1w (spanning-tree command) on
a port-based VLAN before configuring the port as
tagged or untagged, 802.1w fails to initialize. In
addition, the show 802-1w command output shows
that Rapid Spanning Tree Protocol (RSTP) is not
configured. Note that if you define the port as
tagged or untagged before enabling 802.1w, this
problem does not occur.
RSTP - IEEE
802.1w
07.8.01
29755 The following display message contains a typo:
mtu config change detected, if NOT hot
swaping, please save and reload!
The message should read “swapping” instead of
“swaping”.
Jumbo IP
Packet
Support
07.8.01
29759 If jumbo packets (default-mtu 14336 command)
are enabled globally on a routing switch and the
switch has an empty module slot or slots, the ports
on the empty module slots are configured with mtu
1518 instead of mtu 14336. This occurs after you
enter the write memory command.
Jumbo IP
Packet
Support
07.8.01
29846 If you hot swap a module by inserting it in a switch
that is globally configured to support jumbo frames
(default-mtu 14336 command), the newly installed
module should automatically inherit the jumbo
configuration without requiring a system reload.
However, this does not occur and jumbo frame
support is not recognized on the newly installed
module unless you reload the switch.
Jumbo IP
Packet
Support
07.8.01
30248 If a routing switch has numerous BGP entries, the
page break (page display) does not work properly
with the show ip bgp peer command. After
entering the show ip bgp peer command, the
command output scrolls continuously on the screen
at first, then goes into page-by-page prompting
mode.
BGP 07.8.01
30685 A routing switch deletes a route from the routing
table even though the same entry exists in the
OSPF LSA database.
OSPF 07.8.01
30702 The no ip ospf cost command does not apply the
default value to the OSPF cost.
OSPF 07.8.01
30998 A routing switch prefers OSPF routes instead of
EBGP routes after a system reload. If you clear
BGP sessions or IP routes, this problem does not
occur.
BGP 07.8.01
31047 If a routing switch has one BGP neighbor, the
switch increases the ARP timer and eventually ages
out the ARP entry for the peer. This error does not
occur if there are two BGP neighbors. In this case,
the ARP timers remain between 0 and 1.
BGP4+ 07.8.01
Bug ID Bug Description Protocol/
Feature
Version
Found
Version
Fixed
