Allied Telesis AR44xS Instruction Manual

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:
Caution: Using a maintenance version on the wrong model may cause unpredictable results, including disruption to the network.
This maintenance release note should be read in conjunction with the following documents:
■Release Note for Software Version 2.7.6 for AT-8800, Rapier i, AT-8700XL, AT-8600, AT-9900, AT-8900 and AT-9800 Series Switches and AR400 and AR700
Series Routers (document number C613-10462-00 Rev A)
■your router or switch’s Document Set for Software Release 2.7.5. This document set is available on the CD-ROM that shipped with your router or switch,
or from www.alliedtelesis.co.nz/documentation/documentation.html
Caution: Information in this release note is subject to change without notice and does not represent a commitment on the part of Allied Telesis Inc. While every
effort has been made to ensure that the information contained within this document and the features and changes described are accurate, Allied Telesis Inc. can
not accept any type of liability for errors in, or omissions arising from the use of this information.
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, Rapier 48i, Rapier 16fi Rapier i 86276-05.rez 8 September 2006 4312896 dr24ie27.rsc, dr48ie27.rsc, dr16ie27.rsc
AT-8824, AT-8848 AT-8800 86276-05.rez 8 September 2006 4312896 d8824e27.rsc, d8848e27.rsc

Enabling and Installing this Release 2
Version 276-05
C613-10474-00 REV D
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 AR440S router, use the commands:
enable rel=54276-05.rez num=2.7.6
set install=pref rel=54276-05.rez
Levels
The issues addressed in this Maintenance Version include a level number. This number reflects the importance of the issue that has been resolved. The levels
are:
Level 1 This issue will cause significant interruption to network services, and there is no work-around.
Level 2 This issue will cause interruption to network service, however there is a work-around.
Level 3 This issue will seldom appear, and will cause minor inconvenience.
Level 4 This issue represents a cosmetic change and does not affect network operation.

Features in 276-05 3
Version 276-05
C613-10474-00 REV D
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 was not released on that product series.
Level 1
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800
CR00013147 ATM 1 Excessive CPU usage was occurring when an SHDSL link was up. This resulted in
low throughput and dropped packets.
This issue has been resolved.
Y - --------
CR00013288 ADSL 1 For AR440S and AR441S ADSL routers, the Annex A and Annex B firmware has
been upgraded. On AR440S routers, this resolves an issue which meant that the
ADSL link could be unreliable at 3km when connected to a specific type of
DSLAM.
Y---------

Features in 276-05 4
Version 276-05
C613-10474-00 REV D
Level 2
Level 3
Level 4
No level 4 issues
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800
CR00012606 STP 2 Processing of an invalid STP packet could result in an STP timeout value being
incorrectly set to 0.
This issue has been resolved, so the timeout can never be set to 0.
---YY-----
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800
CR00013672 ATM 3 An SNMP Walk of the ATM MIB would fail to complete properly, as it would not
advance through the channel list.
This issue has been resolved.
Y - --------

Features in 276-05 5
Version 276-05
C613-10474-00 REV D
Enhancements
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800
CR00012881 IP Gateway - The IP implementation has been enhanced to accept IP interfaces with a /31
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.
Y--YY-----
CR00013444 IP Gateway - RIPv2 can now use authentication passwords that contain almost any printable
character, including characters such as $, % and &. The ? character is interpreted
as asking for parameter help, so this is not usable anywhere inside a password.
Also, a password cannot contain double quotes (") as the first character of the
string.
The RIP password length is now strictly enforced at 16 characters. The command
handler no longer accepts a password with more characters than this.
Y--YY-----

Features in 276-04 6
Version 276-05
C613-10474-00 REV D
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 was not released on that product series.
“-” in a grey column indicates that the issue did not apply to that product series.
“Y” in a grey column indicates that the issue applied to that product series. These issues are resolved in the next Version (276-05).
Level 1
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800
CR00007273 Switch 1 If a user created a configuration file that contained port trunk settings before
VLAN port settings, then a loop occurred when the switch rebooted with this
configuration.
This issue has been resolved.
-- - YYYY- - -
CR00011711 PIM v6 1 For IPv6, the router or switch could restart when PIM-SM detected that the
primary RPF interface to an (S,G) routing entry had changed because the RPF
interface had gone down. When the interface went down, PIM-SM recalculated
the RPF to the source for the (S,G) entry, and if PIM-SM only found a non-PIM
neighbour as the RPF to the source for the (S,G), the router or switch could
restart.
This issue has been resolved.
Y- YYY- - - - -

Features in 276-04 7
Version 276-05
C613-10474-00 REV D
CR00011994 IPsec 1 When both Software QoS and IPSec were configured on the router or switch, it
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 reached quickly.
This issue has been resolved.
Y-YY---- - -
CR00012196 IPv6 1 When RIPng deleted a route from the IPv6 route table, routing for associated IPv6
flows was not updated correctly. This caused data forwarding on those flows to
use invalid routes.
This issue has been resolved.
Y- YYY- - - - -
CR00012461 IPv6 1 Sometimes the router or switch rebooted when it received Neighbour
Advertisements that did not properly conform to RFC 2461.
This issue has been resolved. The router or switch no longer reboots if it receives
non-conformant ND packets. If debugging is enabled, the router or switch now
also displays useful information about the non-conformant packets.
Y- YYY- - - - -
CR00012571
CR00013183
IPv6 1 The router or switch sometimes rebooted when running a configuration script
that included RIPng (RIPv6).
This issue has been resolved.
Y- YYY- - - - -
CR00012614 Switch 1 When PIM6 was configured on the switch, and it received an IPv6 multicast
stream for which it had no downstream interface to forward the stream to, a
reboot could occur.
This issue was resolved in a previous software version (as CR00012097) but this
version includes an improved resolution.
Y- YYY- - - - -
CR00013025 DVMRP 1 Receiving a DVMRP Graft or Prune message occasionally caused the router or
switch to reboot.
This issue has been resolved.
Y- YYY- - - - -
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800

Features in 276-04 8
Version 276-05
C613-10474-00 REV D
CR00013413 IP Gateway,
Load Balancer
1If the router or switch was configured with a local interface IP address and the
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.
Y- YYYYY- - -
CR00013457 VLAN 1 When ports were added to a currently-disabled RSTP domain, the ports could
start to discard packets (because their STP state was set to Discarding).
This issue has been resolved. When ports are added to a disabled RSTP domain,
they remain in a Forwarding state.
-- - YYYY- - -
CR00013743 Switch 1 If a user created a configuration file that contained LACP settings and VLAN port
settings, then a loop occurred when the switch rebooted with this configuration.
This issue has been resolved.
-- - YYYY- - -
CR00013758 IPv6 1 If a user manually deleted a Neighbour Discovery cache entry (by using the
command delete ipv6 nd), the router or switch sometimes rebooted some time
later.
This issue has been resolved.
Y- YYY- - - - -
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800

Features in 276-04 9
Version 276-05
C613-10474-00 REV D
Level 2
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800
CR00009079 MLD
Snooping,
IPv6, Switch
2When MLD snooping creates an All Router group, it also (correctly) adds router
ports to other groups. However, when MLD Snooping detected that there were
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.
---YY-----
CR00009212 Bridge 2 The Bridge cannot be configured to bridge PPPoE packets from an Ethernet
interface that has also been configured as a PPPoE interface. Previously, such a
Bridge configuration would appear to succeed. However the Bridge would not
bridge PPPoE packets and the router would restart when the command reset
bridge was entered.
This issue has been resolved. Note: if you want to bridge PPPoE packets, do not
also configure the router as a PPPoE endpoint (by using the command create
ppp=number over=ethx-any).
Y-Y-------
CR00009213 MSTP 2 Because of an MSTP issue, the switch did not always send a BPDU with an
agreement flag to its designated bridge, even if the switch was synchronised with
the latest spanning tree information from the designated bridge. This prevented
the designated port on the designated bridge from making a fast transition to
the forwarding state. The result was that the network could take up to two times
the “forward delay” time to fully converge.
This issue has been resolved.
---YYYY---
CR00009826 IP Gateway 2 When a static ARP is deleted, the router or switch sends out an ARP request to
attempt to create a dynamic ARP for that IP address. Previously, the router or
switch did not process the ARP response correctly and therefore did not add the
ARP to its ARP table.
This issue has been resolved. When a static ARP is deleted, the router or switch
attempts to create a dynamic ARP for that IP address, and will successfully add it
to the ARP table if a device responds.
Y- YYYYY---

Features in 276-04 10
Version 276-05
C613-10474-00 REV D
CR00010177 Firewall 2 When a session had been initiated from the LAN side of the firewall and the SIP
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.
Y-YYY-----
CR00010513 BGP,
IP Gateway
2BGP did not update its route table when a blackhole route changed in IP.
This issue has been resolved.
Y-YYY-----
CR00010593 IPv6 2 The router sometimes forwarded packets to directly connected hosts whose
corresponding IPv6 ND cache entry was still in INCOMPLETE state. This caused it
to send the packets to incorrect MAC addresses and egress ports.
This issue has been resolved.
Y-YYY-----
CR00011120 VRRP 2 Packets transmitted from VRRP sometimes contained random VLAN tags or VLAN
Priority information.
This issue has been resolved.
Y-Y-------
CR00011175 IPv6 2 After a route’s metric and/or preference changed, the route’s position in the
Equal Cost Multi Path chain was not always updated properly. This sometimes
caused the forwarding process to select a sub-optimal route.
This issue has been resolved.
Y-YYY-----
CR00011434 File 2 The router or switch sometimes rebooted when copying a very large file (several
Mbytes). This issue has been resolved by improving the copy process so that it
uses fewer memory buffers.
Y- YYYYY---
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800

Features in 276-04 11
Version 276-05
C613-10474-00 REV D
CR00011490 MLD,
MLD Snooping
2The following issues occurred:
■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 Timeout—the timeout period for registration of the “All
Router” group—was not calculated by using the following formula from
RFC 3810:
robustness * qinterval + qrinterval/2
■When robustness, qinterval or qrinterval were set to non-default values,
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.
Y-YYY-----
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-YYY-----
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800

Features in 276-04 12
Version 276-05
C613-10474-00 REV D
CR00011907 IP Gateway 2 Previously, if the IP Helper attempted to redirect packets to an address that
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 broadcast packets. If directedbroadcast=no,
IP still redirects packets from IP Helper when necessary.
Y- YYYYY---
CR00012364 IPv6 2 For IPv6, if there were multiple equal cost multipath (ECMP) static routes to a
destination, and one or more links for the routes became inactive, the inactive
route was sometimes still chosen for forwarding. This caused brief data delivery
failure to the destination.
This issue has been resolved.
Y-YYY-----
CR00012407 STAR 2 When the STAR protocol was used for link-layer encryption, the channel setup
failed continuously on heavy traffic.
This issue has been resolved.
Y-YY------
CR00012476 IGMP 2 If IGMP snooping was enabled but IGMP was not enabled, the snooper behaved
as if IGMP snooping fast leave had been enabled even when it had not been. This
meant that as soon as the snooper received a Leave message, the port left the
group.
This issue has been resolved. Note that fast leave is disabled by default.
Y- YYYYY---
CR00012534 IP Gateway 2 If the router or switch received an IP packet that had been sent as an Ethernet
broadcast, the router or switch responded as if the packet had been sent to its IP
address, even when the packet was destined for a different IP address. In
particular, the router or switch processed and responded to ICMP and TCP
packets that were sent as Ethernet broadcasts to different IP addresses. These
caused the router or switch to send ICMP echo responses or TCP reset packets.
This issue has been resolved. Such Ethernet broadcast packets are generally not
valid packets, so the router or switch now discards them.
Y- YYYYY---
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800

Features in 276-04 13
Version 276-05
C613-10474-00 REV D
CR00012624 VRRP,
IP Gateway
2Under certain network conditions in which VRRP entities become temporarily
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.
This issue has been resolved. The router or switch no longer accepts gratuitous
ARPs from other VRRP entities while it is still the Master.
Y- YYYYY---
CR00012657 STP 2 When STP was operating with a large number of VLANs in the same STP region,
the switch sometimes rebooted while processing topology change notifications
(TCNs).
This issue has been resolved.
---YYYY---
CR00012674 IPv6 2 The router or switch sometimes rebooted when it was about to send an MLDv2
source specific query.
This issue has been resolved.
Y-YYY-----
CR00012679 IPv6, PIMv6 2 For IPv6, PIM sometimes failed to forward multicast packets when MLD snooping
was enabled and MLDv2 was used by multicast receivers/clients to report group
membership.
This issue has been resolved.
Y-YYY-----
CR00012681 IPv6, MLD 2 Valid MLDv2 listener reports that contained two or more source addresses were
sometimes rejected by the router or switch because it treated them as invalid
packets. This could cause multicast clients to unexpectedly stop receiving
multicasts.
This issue has been resolved.
Y-YYY-----
CR00012741 Core, File,
Stack
2The command create config=filename set did not copy the configuration file
to all switches in the stack, but only saved the file onto the current switch.
This issue has been resolved.
---YYYY---
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800

Features in 276-04 14
Version 276-05
C613-10474-00 REV D
CR00012743 IP Gateway 2 When a device that is connected to a router or switch interface leaves a multicast
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 or switch rebooted.
This issue has been resolved. If the interface is deleted, the router or switch no
longer attempts to send more Queries.
Y- YYYYY---
CR00012825
CR00013458
MLD
Snooping,
IPv6, Switch
2An issue occurred in IPv6 multicasting if multiple ports were registered to receive
data from the All Routers group. When one of the ports timed out, the entries
for all of the ports were purged, even if the other ports’ timers had not expired.
The router or switch also sometimes flooded IPv6 multicast traffic undesirably
when the MLD All Routers snooping group contained more than one port.
These issues have been resolved.
Y-YYY-----
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800

Features in 276-04 15
Version 276-05
C613-10474-00 REV D
CR00012846 ASYN, Log 2 The following issues occurred with sending log messages to an asynchronous
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 something else.
■It was possible for a user to change the log output destination to an
asynchronous port while the user was logged into the asynchronous port. This
resulted in the user losing access to the command line interface.
■It was possible to create a log output definition with an asynchronous port as
the destination even when another user was logged into that asynchronous
port. This resulted in the other user losing access to the command line
interface.
■If a user changed the log output destination to an asynchronous port and
specified invalid parameters in the command, an error message was displayed
but the new output destination was saved anyway.
■The set command allowed a user to specify an asynchronous port as the
destination without specifying the asynchronous port number. The number
defaulted to asyn0, which may not have been the desired port.
These issues have been resolved.
Y- YYYYY---
CR00012868 ENCO 2 Entering the command create enco key=number ip=? caused the router or
switch to reboot.
This issue has been resolved.
Y- YYYYY---
CR00012951 IPv6 2 RIPng (for IPv6) sometimes sent sub-optimal routes to its neighbours. When
RIPng was configured in a network with loop topology, this could cause unstable
routing table entries on the neighbours (the metric kept being updated, as a
result of updates from neighbours).
This issue has been resolved. RIPng no longer sends sub-optimal routes.
Y-YYY-----
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800

Features in 276-04 16
Version 276-05
C613-10474-00 REV D
CR00012952 Bridge 2 If a tagged packet was bridged out of a VLAN interface, the interface always
added a VLAN tag into the packet, even though the packet was already tagged.
This issue has been resolved.
Y-Y-------
CR00012991 ATM 2 The maximum allowed value of the vpi parameter in the commands add and set
atm channel has been increased from 8 to 15.
Y---------
CR00013023 OSPF 2 An issue occurred when OSPF was configured to create passive interfaces by
default (set ospf passiveinterfacedefault=on) but an OSPF interface was not
passive (set ospf interface=interface passive=off). This interface setting was
saved in the configuration file or output resulting from the commands create
config and show config dynamic, but any other changes to interface settings
were not saved (such as changes to authentication settings). If the router or
switch rebooted, these other interface changes were lost.
This issue has been resolved.
Y- YYYYY---
CR00013077 IPv6 2 When an IPv6 address was deleted on the router or switch, and that IPv6 address
had previously been learnt by a remote IPv6 node, then the router or switch
would reboot if it received an ICMPv6 Neighbour Solicitation message from the
remote node. This meant, for example, that if you successfully pinged an address
on the router or switch, then deleted that address, then attempted to ping the
old address again, the router or switch would reboot.
This issue has been resolved.
Y-YYY-----
CR00013081 Switch, STP 2 When STP was enabled on ports in a trunk group, the non-master ports did not
have the same state as the master port in the switch’s hardware STG table. This
could, on rare occasions, create a broadcast storm.
This issue has been resolved. All ports in a trunk group follow the master port in
the hardware STG table.
---YYYY---
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800

Features in 276-04 17
Version 276-05
C613-10474-00 REV D
CR00013083 TACACS+, User 2 After a very large number of successful logins via TACACS+ authentication, the
router or switch would reboot.
This issue has been resolved.
Y- YYYYY---
CR00013096
CR00013718
IPv6 2 When the router or switch learned a better IPv6 route to exactly the same
destination as an existing route, the router or switch did not always change
existing data flows so that they used the new route. This meant that existing
flows did not always follow the optimal path.
This issue has been resolved. When the router or switch learns a better IPv6 route,
both new and existing flows now use it.
Also, the commands create ipv6 interface and set ipv6 interface now include
a new parameter: metric. This allows you to set the RIP metric of link local
interfaces to a desired value. Note that the metric parameter is only valid on link
local interfaces.
Y-YYY-----
CR00013234 IP Gateway 2 If the router or switch attempted to email log output, and used a domain name
server that gave a non-standard response to the DNS query, the router or switch
sometimes rebooted.
This issue has been resolved.
Y- YYYYY---
CR00013276 UPnP 2 In UPnP, Msearch requests were stored indefinitely, which eventually exhausted
the router’s memory and caused it to reboot.
This issue has been resolved. Msearch requests are now deleted once the router
has finished with them.
Y-Y-------
CR00013309 L2TP 2 When an L2TP LAC Client (for example, a Microsoft Windows XP VPN Client)
activated an L2TP tunnel to a router or switch that was operating as an LNS, the
dynamic PPP interface on the LNS left out the PPP authentication phase.
This also prevented the interface from obtaining an IP address by remote IP
assignment from a User Database entry.
This issue has been resolved.
Y-YYY-----
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800

Features in 276-04 18
Version 276-05
C613-10474-00 REV D
CR00013437 SCC 2 If a PRI or BRI interface had severe transmission difficulties due to a faulty
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.
Y-YY------
CR00013529 PIMv6 2 When the router or switch used PIM for multicast routing, and an IPv6 multicast
client joined a group, then left it, then attempted to rejoin it, sometimes the
attempt to rejoin was not successful.
This issue has been resolved.
Y-YYY-----
CR00013785 IPv6, Utility 2 IPv6 sometimes chose a suboptimal route for routing when there were more than
two routes destined to the same network.
This issue has been resolved.
Y-YYY-----
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800

Features in 276-04 19
Version 276-05
C613-10474-00 REV D
Level 3
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800
CR00008192 Switch 3 The following issues occurred with the counters that are displayed by the show
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 of packets,
not octets. Therefore, this counter has been renamed to ifInErrors.
---YYYY---
CR00010345 Firewall 3 When the HTTP proxy URL filter had entries that allowed certain domains and
also had entries that denied certain keywords, the supposedly-allowed domains
were denied if they contained the denied keywords. The proxy allowed the page
/index.html from such domains, but no other pages.
This issue has been resolved. The proxy no longer checks allowed domains
against the keyword list.
Y-YYY-----
CR00010504 IP Gateway 3 When a VRRP master was configured with VRRP adoption enabled, pings from
the VRRP master to its own VR IP address failed.
This issue has been resolved.
Y- YYYYY---
CR00011444 Asyn 3 If information was sent to a console (asyn) port that had no cable plugged into
it, excessive CPU usage occurred.
This issue has been resolved.
Y- YYYYY---

Features in 276-04 20
Version 276-05
C613-10474-00 REV D
CR00011598 PIM, PIM6 3 Previously the SPTbit on a PIM device was not set under the following conditions:
■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 sending register messages awaiting a register STOP.
This issue has been resolved. Non-RP PIM devices no longer continually send
register messages.
Y-YYY-----
CR00011710 Core 3 When the router sent a RADIUS accounting STOP packet, the packet’s Acct-
Session-Time was always zero, no matter how long the session had been active
for.
This issue has been resolved.
Y-YYY-----
CR00012128 IP Gateway 3 When the router or switch recalculated the IP checksum after decrementing the
TTL value, it was possible for the checksum to be 0xFFFF. This conformed to
RFC 1141 but not to RFC 1624. For switches, note that this issue did not affect
IP hardware routing, only packets routed by the CPU.
This issue has been resolved. Checksums are now calculated in accordance with
RFC 1624.
Y- YYYYY---
CR00012194
CR00002547
IPv6 3 When a user changed the settings for IPv6 Neighbour Discovery advertisement of
the prefix of an existing IPv6 interface route, then the changes were not saved in
the configuration file or output resulting from the commands create config and
show config dynamic. If the router or switch rebooted, the changes were lost.
This issue only occurred if the existing interface route and the modified prefix had
the same prefixlength.
This issue has been resolved.
Y-YYY-----
CR Module Level Description
AR44xS/ AR450S AR7x5 AR750S Rapier i AT-8800 AT-8600 AT-8700XL AT-8948 AT-9900 AT-9800