Release Notes for 07.8.04 |
|
| Software Fixes | |
|
|
|
|
|
Bug ID | Bug Description | Protocol/ | Version | Version |
|
| Feature | Found | Fixed |
|
|
|
|
|
29670 | If you enable 802.1w | RSTP - IEEE |
| 07.8.01 |
| a | 802.1w |
|
|
| tagged or untagged, 802.1w fails to initialize. In |
|
|
|
| addition, the show |
|
|
|
| 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. |
|
|
|
|
|
|
|
|
29755 | The following display message contains a typo: | Jumbo IP |
| 07.8.01 |
| mtu config change detected, if NOT hot | Packet |
|
|
| Support |
|
| |
| swaping, please save and reload! |
|
| |
|
|
|
| |
| The message should read “swapping” instead of |
|
|
|
| “swaping”. |
|
|
|
|
|
|
|
|
29759 | If jumbo packets | Jumbo IP |
| 07.8.01 |
| are enabled globally on a routing switch and the | Packet |
|
|
| switch has an empty module slot or slots, the ports | Support |
|
|
| on the empty module slots are configured with mtu |
|
|
|
| 1518 instead of mtu 14336. This occurs after you |
|
|
|
| enter the write memory command. |
|
|
|
|
|
|
|
|
29846 | If you hot swap a module by inserting it in a switch | Jumbo IP |
| 07.8.01 |
| that is globally configured to support jumbo frames | Packet |
|
|
| Support |
|
| |
| 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. |
|
|
|
|
|
|
|
|
30248 | If a routing switch has numerous BGP entries, the | BGP |
| 07.8.01 |
| 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 |
|
|
|
| mode. |
|
|
|
|
|
|
|
|
30685 | A routing switch deletes a route from the routing | OSPF |
| 07.8.01 |
| table even though the same entry exists in the |
|
|
|
| OSPF LSA database. |
|
|
|
|
|
|
|
|
30702 | The no ip ospf cost command does not apply the | OSPF |
| 07.8.01 |
| default value to the OSPF cost. |
|
|
|
|
|
|
|
|
30998 | A routing switch prefers OSPF routes instead of | BGP |
| 07.8.01 |
| EBGP routes after a system reload. If you clear |
|
|
|
| BGP sessions or IP routes, this problem does not |
|
|
|
| occur. |
|
|
|
|
|
|
|
|
31047 | If a routing switch has one BGP neighbor, the | BGP4+ |
| 07.8.01 |
| 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. |
|
|
|
|
|
|
|
|
|
|
|
|
|
27