Features in | 4 |
Features in 276-02
Software Maintenance Version
■“Y” indicates that the resolution is available in Version
■
Level 1
CR | Module | Level | Description | AR44x / AR450 | AR7x5 | AR750S | Rapier i | ||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00011691 | Switch | 1 | Previously, if trunk ports were configured and/or STP was enabled, the CPU | - | - | - | Y | Y | Y | Y | Y | Y | - |
|
|
| flooded GARP frames in an incorrect manner, which could cause network loops. |
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. GMRP frames are (correctly) flooded, and GVRP |
|
|
|
|
|
|
|
|
|
|
|
|
| frames are now only flooded if GARP is disabled. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00011694 | Core, | 1 | If the switch had learned a very large number of routes from BGP and the | - | - | - | Y | Y | - | - | Y | Y | Y |
| Switch |
| interface went down, IP ran out of memory when recalculating the best routes |
|
|
|
|
|
|
|
|
|
|
|
|
| to use. This was exacerbated when the high memory usage triggered the BGP |
|
|
|
|
|
|
|
|
|
|
|
|
| backoff mechanism which in turn disabled the BGP peers, which caused IP to |
|
|
|
|
|
|
|
|
|
|
|
|
| recalculate even more routes. The switch eventually rebooted due to memory |
|
|
|
|
|
|
|
|
|
|
|
|
| exhaustion. |
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved by improvements to memory allocation and IP route |
|
|
|
|
|
|
|
|
|
|
|
|
| queuing, and by enforcing limits on the number of IP routes. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012097 | Switch | 1 | When PIM6 was configured on the switch, and it received an IPv6 multicast | - | - | - | Y | Y | - | - | Y | Y | Y |
|
|
| stream for which it had no downstream interface to forward the stream to, a |
|
|
|
|
|
|
|
|
|
|
|
|
| reboot could occur. |
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version