|
|
|
|
|
|
| Features in |
|
|
| 11 | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR | Module | Level | Description | AR44x / AR450 | AR7x5 | AR750S |
| Rapier i |
| ||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012013 | VLAN | 2 | When MLD snooping was enabled and the switch received IPv6 multicast packets | - | - | - |
| Y | Y | - |
| - | Y | Y | Y |
|
|
| (such as MLD Query, Report or Done messages; IPv6 NS packets; and IPv6 RA |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| packets) on a |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| out the master port. This resulted in a packet loop. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012067 | OSPF | 2 | A summary LSA was not turned into a route if the destination and mask fell inside | Y | Y | Y |
| Y | Y | Y |
| Y | Y | Y | Y |
|
|
| one of the router or switch’s active ranges, unless it exactly matched the active |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| range’s address and mask. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This complied with RFC 1583 section 16.2. However, the recommended |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| behaviour has been modified in RFC 2328 section 16.2. To comply with this, the |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| LSA is now calculated if it falls inside one of the router or switch’s active ranges. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012096 | Core, LLDP, | 2 | The LLDP module and several monitoring features started up when they were not | Y | - | - |
| - | - | - |
| - | - | - | - |
| Switch, Utility |
| needed. This impacted on performance. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved, and therefore performance has been improved, |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| especially for the AR440S router. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012108 | Switch | 2 | The command disable switch | - | - | - |
| - | - | - |
| - | - | Y | - |
|
|
| correctly disable the link for port 12 or 24 on |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ports 12 and 24 in software. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CR00012119 | Load balancer | 2 | Previously, only one resstate trigger could be created for each load balancer | Y | Y | Y |
| Y | Y | - |
| - | Y | Y | Y |
|
|
| resource. This meant, for example, that you could create a trigger to activate a |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| script when a resource went down, but could not activate another script when |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| the resource came back up again. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| This issue has been resolved. You can now define different triggers to trigger off |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| each of the different states available for a given resource (such as lbstate=up |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| and lbstate=closing). |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version