Résumé du contenu de la page N° 1
Software Maintenance Release Note
Version 276-05
for AR450S and AR44xS series routers, and
Rapier i and AT-8800 series switches
This software maintenance release note lists the issues addressed and enhancements made in Maintenance Version 276-05 for Software Release 2.7.6. Release
details are listed in the following table:
Models Series Release File Date Size (bytes) GUI file
AR440S, AR441S, AR450S AR400 54276-05.rez 8 September 2006 4512716 d440se27.rsc, d441se27.rsc, d450se27.rsc
Rapier 24i,
Résumé du contenu de la page N° 2
Enabling and Installing this Release 2 Enabling and Installing this Release To use this maintenance release you must have a base release license for Software Release 2.7.6. Contact your distributor or reseller for more information. To enable this release and install it as the preferred release, use the commands: enable rel=xx276-05.rez num=2.7.6 set install=pref rel=xx276-05.rez where xx is the prefix to the filename, as shown in the table on page 1. For example, to install the release on an AR
Résumé du contenu de la page N° 3
Features in 276-05 3 Features in 276-05 Software Maintenance Version 276-05 includes all resolved issues and enhancements in earlier versions, and the resolved issues and enhancements in the following tables. In the tables, for each product series: ■ “Y” in a white column indicates that the resolution is available in Version 276-05 for that product series. ■ “-” in a white column indicates that the issue did not apply to that product series. ■ a grey-shaded column indicates that Version 276-05
Résumé du contenu de la page N° 4
Features in 276-05 4 Level 2 CR Module Level Description STP 2 Processing of an invalid STP packet could result in an STP timeout value being - - -Y Y - - - - - CR00012606 incorrectly set to 0. This issue has been resolved, so the timeout can never be set to 0. Level 3 CR Module Level Description ATM 3 An SNMP Walk of the ATM MIB would fail to complete properly, as it would not Y - -- - - - - - - CR00013672 advance through the channel list. This issue has been resolved. Level 4 No level 4 issues
Résumé du contenu de la page N° 5
Features in 276-05 5 Enhancements CR Module Level Description IP Gateway - The IP implementation has been enhanced to accept IP interfaces with a /31 Y - -Y Y - - - - - CR00012881 netmask. This results in a slightly non-standard subnet that has no network address or broadcast address. This has become a popular extension to IP, because it reduces wastage of IP addresses on point-to-point links. IP Gateway - RIPv2 can now use authentication passwords that contain almost any printable Y - -Y Y -
Résumé du contenu de la page N° 6
Features in 276-04 6 Features in 276-04 Software Maintenance Version 276-04 includes all resolved issues and enhancements in earlier versions, and the resolved issues and enhancements in the following tables. In the tables, for each product series: ■ “Y” in a white column indicates that the resolution is available in Version 276-04 for that product series. ■ “-” in a white column indicates that the issue did not apply to that product series. ■ a grey-shaded column indicates that Version 276-04
Résumé du contenu de la page N° 7
Features in 276-04 7 CR Module Level Description IPsec 1 When both Software QoS and IPSec were configured on the router or switch, it Y -Y Y --- - - - CR00011994 sometimes rebooted. This happened if the IPSec SA bundle was suddenly deleted while packets were still queued in Software QoS. For example, this issue was more likely to occur if the expirykbytes parameter of the create ipsec bundlespecification command was configured, and the hard expiry kilobyte limit for an IPSec SA bundle was re
Résumé du contenu de la page N° 8
Features in 276-04 8 CR Module Level Description IP Gateway, 1 If the router or switch was configured with a local interface IP address and the Y - Y YYYY - - - CR00013413 Load Balancer interface to which this address belonged did not have a logical interface with index 0, a number of connectivity issues from this router or switch occurred, in which the router or switch was not able to communicate with UDP, TCP or PING. This issue has been resolved. VLAN 1 When ports were added to a currently-
Résumé du contenu de la page N° 9
Features in 276-04 9 Level 2 CR Module Level Description MLD 2 When MLD snooping creates an All Router group, it also (correctly) adds router - --Y Y - - - - - CR00009079 Snooping, ports to other groups. However, when MLD Snooping detected that there were IPv6, Switch no more router ports in the network, it deleted the All Router group but did not delete the router ports from the other groups. This issue has been resolved. Bridge 2 The Bridge cannot be configured to bridge PPPoE packets from
Résumé du contenu de la page N° 10
Features in 276-04 10 CR Module Level Description Firewall 2 When a session had been initiated from the LAN side of the firewall and the SIP Y -Y Y Y -- - - - CR00010177 ALG received a re-invite packet for that session from the WAN side, the SIP ALG did not replace the Call ID string in the re-invite packet. This issue has been resolved. BGP, 2 BGP did not update its route table when a blackhole route changed in IP. Y -Y Y Y -- - - - CR00010513 IP Gateway This issue has been resolved. IPv6 2 Th
Résumé du contenu de la page N° 11
Features in 276-04 11 CR Module Level Description MLD, 2 The following issues occurred: Y -Y Y Y -- - - - CR00011490 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 + qrint
Résumé du contenu de la page N° 12
Features in 276-04 12 CR Module Level Description IP Gateway 2 Previously, if the IP Helper attempted to redirect packets to an address that Y - Y Y YYY - - - CR00011907 matched the network broadcast address of the egress interface, the packets were only forwarded if directedbroadcast=yes for the egress interface. By default, directedbroadcast=no, so such packets were dropped. This issue has been resolved. IP can now distinguish between packets redirected by the IP Helper and real directed br
Résumé du contenu de la page N° 13
Features in 276-04 13 CR Module Level Description VRRP, 2 Under certain network conditions in which VRRP entities become temporarily Y - Y Y YYY - - - CR00012624 IP Gateway unsynchronised, the router or switch could receive a gratuitous ARP from a self- elected VRRP master when the router or switch was still the master. This caused the existing master to create an ARP entry that incorrectly redirected packets towards the other VRRP entity even after the other entity had become a slave again.
Résumé du contenu de la page N° 14
Features in 276-04 14 CR Module Level Description IP Gateway 2 When a device that is connected to a router or switch interface leaves a multicast Y - Y Y YYY - - - CR00012743 group, the router or switch (correctly) responds by sending out a Query message over that interface. In the default configuration, it also sends a second Query message one second later, for redundancy. Previously, if the router or switch interface was deleted after the first Query but before the second Query, the router
Résumé du contenu de la page N° 15
Features in 276-04 15 CR Module Level Description ASYN, Log 2 The following issues occurred with sending log messages to an asynchronous Y - Y Y YYY - - - CR00012846 port: ■ The log messages output on an asynchronous port were corrupt. ■ When log messages were output to an asynchronous port, that port was (correctly) locked. However, the port remained locked after the asynchronous log output definition was destroyed, and after the log output's destination was changed from asynchronous to some
Résumé du contenu de la page N° 16
Features in 276-04 16 CR Module Level Description Bridge 2 If a tagged packet was bridged out of a VLAN interface, the interface always Y -Y - --- - - - CR00012952 added a VLAN tag into the packet, even though the packet was already tagged. This issue has been resolved. ATM 2 The maximum allowed value of the vpi parameter in the commands add and set Y --- --- - - - CR00012991 atm channel has been increased from 8 to 15. OSPF 2 An issue occurred when OSPF was configured to create passive interfa
Résumé du contenu de la page N° 17
Features in 276-04 17 CR Module Level Description TACACS+, User 2 After a very large number of successful logins via TACACS+ authentication, the Y - Y Y YYY - - - CR00013083 router or switch would reboot. This issue has been resolved. IPv6 2 When the router or switch learned a better IPv6 route to exactly the same Y -Y Y Y -- - - - CR00013096 destination as an existing route, the router or switch did not always change CR00013718 existing data flows so that they used the new route. This meant th
Résumé du contenu de la page N° 18
Features in 276-04 18 CR Module Level Description SCC 2 If a PRI or BRI interface had severe transmission difficulties due to a faulty Y -Y Y --- - - - CR00013437 communications link, it could cause the router or switch to reboot. This issue has been resolved. A faulty PRI or BRI communications link can no longer take the whole router or switch down. PIMv6 2 When the router or switch used PIM for multicast routing, and an IPv6 multicast Y -Y Y Y -- - - - CR00013529 client joined a group, then l
Résumé du contenu de la page N° 19
Features in 276-04 19 Level 3 CR Module Level Description Switch 3 The following issues occurred with the counters that are displayed by the show - --Y Y Y Y - - - CR00008192 interface=port-number counter command: ■ If a switch port received a broadcast or multicast packet with an error (such as a bad CRC error), the ifInUcastPkts counter—the number of unicast packets received— was incremented. This issue has been resolved. ■ On AT-9800 series switches, the ifInErrorOctets counter is a count o
Résumé du contenu de la page N° 20
Features in 276-04 20 CR Module Level Description PIM, PIM6 3 Previously the SPTbit on a PIM device was not set under the following conditions: Y -Y Y Y -- - - - CR00011598 ■ when a PIM neighbor was the RP (Rendezvous Point), and ■ when the PIM neighbor was not the RPF (Reverse Path Forwarding) neighbor to the Source; that is, it did not have a direct connection to the Source traffic stream. In this situation, the SPTbit remained unset. This resulted in the non-RP PIM device continually sendi
