![CR00011490](/images/new-backgrounds/124776/12477621x1.webp)
Features in | 11 |
CR | Module | Level | Description |
AR44xS/ AR450S
AR7x5
AR750S
Rapier i
CR00011490 | MLD, | 2 | The following issues occurred: |
| MLD Snooping |
| ■ an MLDv2 Report message parsing issue meant that sometimes the router or |
|
|
| switch recognised only the first multicast group address in the message. |
|
|
| ■ if the robustness, qinterval or qrinterval were changed, groups’ initial |
|
|
| timeout period was sometimes set to 260 instead of being calculated by using |
|
|
| the following formula from RFC 3810: |
|
|
| robustness * qinterval + qrinterval |
|
|
| ■ the Other Querier |
|
|
| Router” |
|
|
| RFC 3810: |
|
|
| robustness * qinterval + qrinterval/2 |
|
|
| ■ When robustness, qinterval or qrinterval were set to |
|
|
| the timeout values (or MA timers) of newly reported multicast address groups |
|
|
| were not updated to reflect these changed values. |
|
|
| ■ MLD & MLD Snooping groups were sometimes incorrectly set with a timer |
|
|
| value that was inconsistent with the internally maintained individual port |
|
|
| timers. Therefore, registered groups could lose port members temporarily. |
|
|
| These issues have been resolved. This CR also included enhancements to MLD |
|
|
| and MLD Snooping; see “Enhancements to MLD and MLD Snooping |
|
|
| (CR00011490)” on page 65. |
CR00011638 | PIM 6 | 2 | Occasionally, PIM6 Sparse Mode did not elect the router or switch as the BSR |
|
|
| when no other PIM neighbour was present. |
|
|
| This issue has been resolved. When no other BSR candidates are present, the |
|
|
| router or switch correctly becomes the BSR. |
Y - | Y Y Y - | - | - | - | - |
|
|
|
|
|
|
Y | - | Y Y Y - | - | - | - | - |
|
|
|
|
|
|
|
Version