Allied Telesis Patch 89262-08 Instruction Manual

Simply connecting the world
Patch Release Note
Patch 89262-08
For AT-8900 Series Switches
Introduction
This patch release note lists the issues addressed and enhancements made in
patch 89262-08 for Software Release 2.6.2 on existing models of AT-8900 Series
switches. Patch file details are listed in Table 1.
This release note should be read in conjunction with the following documents:
■Release Note: Software Release 2.6.2 for AT-8900 Series switches
(Document Number C613-10399-00 REV A) available from
www.alliedtelesyn.co.nz/documentation/documentation.html.
■AT-8900 Series Switch Documentation Set for Software Release 2.6.2
available on the Documentation and Tools CD-ROM packaged with your
switch, or from www.alliedtelesyn.co.nz/documentation/documentation.html.
WARNING: Using a patch for a different model or software release may cause
unpredictable results, including disruption to the network. Information in this
release note is subject to change without notice and does not represent a
commitment on the part of Allied Telesyn International. While every effort has
been made to ensure that the information contained within this document and
the features and changes described are accurate, Allied Telesyn International
can not accept any type of liability for errors in, or omissions arising from the
use of this information.
Table 1: Patch file details for Patch 89262-08.
Base Software Release File 89-262.rez
Patch Release Date 15-Oct-2004
Compressed Patch File Name 89262-08.paz
Compressed Patch File Size 324452 bytes

2Patch Release Note
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
Some of the issues addressed in this Release Note include a level number. This
number reflects the importance of the issue that has been resolved. The levels
are:
From Patch 89262-07 onwards, issues for each patch are listed in severity order as per
the levels above. Enhancement PCRs are listed after Level 4 issues.
Features in 89262-08
Patch 89262-08 includes all issues resolved and enhancements released in
previous patches for Software Release 2.6.2, and the following enhancements:
Level 1
No issues.
Level 2
IPv6 multicast packets were not being forwarded when coming from a
6-over-4 tunnel. This issue has been resolved.
If the log module was configured to store a very large number of messages
(for example, more than 3000 messages), a watchdog timeout could occur
when the show debug command was executed. This issue has been
resolved.
Please note that this problem would not occur when the show log command
was executed. A temporary work-around would be to disable the log
module before executing the show debug command.
In a multicast setup, there was a possibility that all multicast and broadcast
packets were not being forwarded as expected. This caused symptoms such
as RIPv1 or RIPv2 losing routes, PIM neighbourhoods being lost, and other
protocols using broadcast or multicast packets would fail to register any
peers/neighbours. Also, multicast packets are not switched. This issue has
been resolved.
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.
PCR: 40570 Module: IP6 Level: 2
PCR: 40573 Module: LOG Level: 2
PCR: 40591 Module: SWMX Level: 2

Patch 89262-08 For AT-8900 Series Switches 3
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
When STP is enabled, when frames with a multicast destination MAC
address were sent, a loop was observed within the network. This issue has
been resolved.
In network configurations with multiple paths to neighbours on an
interface, if the interface changed state from up to down, then up again, the
interface route may have been erroneously deleted by a route update. This
issue has been resolved.
The valid and preferred parameters were incorrectly added to the dynamic
set ipv6 prefix configuration. The default onlink and autonomous
parameters were also being included. This issue has been resolved.
Level 3
The counter parameter did not exist in the show igmpsnooping command.
This issue has been resolved.
An error message is now shown if the user tries to assign more than the
allowable number of traffic class (or default traffic class) entries to active
QOS policies.
When a Core port was added to a nested VLAN, its Ingress Filtering
attribute was set to be On and Acceptable Frame Type was set to be Admit
Only VLAN tagged Frames. If the port was deleted from that VLAN, its
Ingress Filtering attribute must be set to Off and Acceptable Frame Type
must be set to Admit All Frames, however, the attributes were not changed
when the port was deleted from the nested VLAN. This issue has been
resolved.
The manager prompt did not appear when using a telnet session until the
[Enter] key was pressed several times. This issue has been resolved.
An FTP server located on a private interface of a firewall with NAT enabled
may have had its ftp-data (tcp/20) source port translated to another port.
This could lead to a firewall rejecting the data packets, as they do not strictly
conform to RFC 959. This issue has been resolved, ensuring that ftp-data
packets are sent from port 20 on the firewall, even when NAT is enabled.
PCR: 40596 Module: SWMX Level: 2
PCR: 40601 Module: SWMX Level: 2
PCR: 40619 Module: IPG Level: 2
PCR: 40589 Module: IPG Level: 3
PCR: 40603 Module: SWI, SWMX Level: 3
PCR: 40606 Module: VLAN Level: 3
PCR: 40617 Module: TTY Level: 3
PCR: 40618 Module: SWI Level: 3

4Patch Release Note
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
Fixing speed on a fibre SPF to 1000mfull in a configuration script showed
up incorrectly as 10mfull actual speed after reboot. This issue has been
resolved.
Level 4
No issues.
Enhancements
No issues.
Features in 89262-07
Patch file details are listed in Table 1.
Patch 89262-07 includes all issues resolved and enhancements released in
previous patches for Software Release 2.6.2, and the following enhancements:
Level 1
No issues.
Level 2
The switch learned an ARP entry for an IP address that was already
configured on one of its interfaces. This issue has been resolved, and the
receipt of spoofed ARP packets will now generate a log message.
1) A switch reboot could be observed if an IP interface was deleted while
BGP was learning routes.
2) A switch reboot could be observed if a BGP peer was disconnected while
the other peer was learning routes.
3) Excessive log messages were generated when the switch was low on
memory.
PCR: 40618 Module: SWI Level: 3
Table 2: Patch file details for Patch 89262-07.
Base Software Release File 89-262.rez
Patch Release Date 29-Sept-2004
Compressed Patch File Name 89262-07.paz
Compressed Patch File Size 316588 bytes
PCR: 40272 Module: IPG Level: 2
PCR: 40356 Module: BGP Level: 2

Patch 89262-08 For AT-8900 Series Switches 5
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
4) Not all routes were removed from the BGP route table when a peer was
disabled.
These issues have all been resolved.
If OSPF was configured using the command set ospf dyninterface=stub, to
advertise dynamic interfaces such as PPPoE interfaces as stub links, the
links were not being advertised as expected. This issue has been resolved.
In some circumstances, when a BGP peer became physically disconnected,
subsequent deletion of routes could cause a switch reboot to occur.
If OSPF was configured using the command set ospf dyninterface=stub, to
advertise dynamic interfaces such as PPPoE interfaces as stub links, the
links were not being advertised as expected. This issue has been resolved.
In some circumstances, when a BGP peer became physically disconnected,
subsequent deletion of routes could cause a switch reboot to occur.
If an STP disabled port was moved from one VLAN to another, it caused
STP to reconverge. This issue has been resolved.
Incorrect behaviour would occur if the switch was configured with a
hardware filter that used a classifier matching on a VLAN, plus some
additional IP Layer 3 or Layer 4 information (e.g. UDPDPort); and another
filter using a classifier matching on just a VLAN. The result would be that
only non-IP packets would be matched by this second hardware filter. IP
packets not matching the first filter would not match the second, and
therefore would not be classified by the switch. This symptom could also
occur for classifiers using MACSA and MACDA. This issue has been
resolved.
The switch could reboot when a user changed the Rendezvous Point
Candidate (RPC) priority in the PIM6 module. This issue has been resolved.
When BGP redistributed routes, locally imported routes were selected
rather than peer learnt routes. This issue has been resolved.
PCR: 40419 Module: OSPF, IPG Level: 2
PCR: 40420 Module: BGP, IGP Level: 2
PCR: 40419 Module: OSPF, IPG Level: 2
PCR: 40420 Module: BGP, IGP Level: 2
PCR: 40457 Module: STP Level: 2
PCR: 40460 Module: SWMX Level: 2
PCR: 40465 Module: PIM6, PIM4 Level: 2
PCR: 40470 Module: BGP Level: 2

6Patch Release Note
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
When IP filters are configured on IP interfaces of the switch, all IP routing
must occur in software. To achieve this, the IP forwarding table in the ASIC
must be emptied. There was an issue whereby Interim IP route entries (IP
routes for which there is not yet an ARP entry for the nexthop address) were
not removed from the hardware IP forwarding table when an IP filter was
added to an IP interface. This issue has been resolved.
If the switch received many packets to Layer 3 route, but did not have ARP
entries for the destination address, the switch memory would deplete,
leading to a switch reboot. This issue has been resolved.
For OSPF-originated routes, it was possible for a route to be deleted from
the IP routing table, but still be referenced by OSPF. This could cause a
switch reboot when later generating a summary LSA that contained the old
route. This occurred using the reset ip command. This issue has been
resolved.
If the configuration script on the switch contained several commands for
creating static arp entries, the switch could reboot on startup. This issue has
been resolved.
A memory leak could occur when the accessing of the environmental
monitoring chip failed. This issue has been resolved.
When a BGP peer was physically disconnected, the best routes for all
prefixes learned were written to the silicon. The memory that was used to
contain these routes was sometimes not freed, resulting in a memory leak.
This issue has been resolved.
When DHCP is enabled, it reclaims IP addresses at switch startup to
determine if the addresses are in use or not. If, during this process, DHCP
was disabled then re-enabled, the switch would not attempt to reclaim the
remaining IP address ranges. This would lead to the rejection of DHCP
requests for IP addresses that were still being reclaimed. This issue has been
resolved.
When doing AS-Path regular expression matching in the show bgp route
command, the router could reboot if there were withdrawn routes in the
BGP table. This issue has been resolved.
PCR: 40473 Module: IPG Level: 2
PCR: 40478 Module: IPG Level: 2
PCR: 40479 Module: OSPF Level: 2
PCR: 40481 Module: IPG Level: 2
PCR: 40487 Module: CORE Level: 2
PCR: 40488 Module: IPG Level: 2
PCR: 40496 Module: DHCP Level: 2
PCR: 40500 Module: BGP Level: 2

Patch 89262-08 For AT-8900 Series Switches 7
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
A configuration generated with the create config or show config dynamic
commands could under some circumstances, include a
disable vrrp = <vrrpid> command even if VRRP was enabled. This issue
has been resolved.
While initialising a range, the switch acting as a DHCP server may release
a dynamic entry incorrectly. This issue has been resolved.
When the STP mode was changed, all the static arps on the ports belonging
to the STP were deleted. This issue has been resolved.
Multicast data could not flow from PIM to DVMRP on a PIM/DVMRP
border switch. This issue has been resolved.
If a create classifier command contained the ethformat parameter, the
resulting entry in a script created using the create config, or show config
dynamic commands could sometimes be incorrect. This issue has been
resolved.
When both Load Balancer and Firewall were configured, the very first TCP
session was established after rebooting. Subsequent TCP session startup
packets may have been routed out to an incorrect interface causing sessions
to not be established. This issue has been resolved.
A customer port in one nested VLAN could be set to be a core port in
another nested VLAN. This issue has been resolved.
When a particular model of SFP is fitted, and a switch reboot occurs, the
switch could get locked in a reboot cycle, and never manage to finish
booting. This issue has been resolved.
When the status of an interface changed, the BGP revaluation of IP routes
for redistribution (via the add bgp import or add bgp network commands)
was incorrect. This gave inconsistent BGP route tables depending on the
order of events. This issue has been resolved.
Multicast data failed to be forwarded by PIM-SM if an MLD report was
received on the switch before the corresponding multicast stream had
arrived. This issue has been resolved.
PCR: 40510 Module: VRRP Level: 2
PCR: 40516 Module: DHCP Level: 2
PCR: 40519 Module: SWI Level: 2
PCR: 40520 Module: DVMRP Level: 2
PCR: 40522 Module: CLASSIFIER Level: 2
PCR: 40530 Module: IPG Level: 2
PCR: 40531 Module: VLAN Level: 2
PCR: 40535 Module: SWMX Level: 2
PCR: 40537 Module: BGP Level: 2
PCR: 40538 Module: IP6, SWI Level: 2

8Patch Release Note
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
Problems could occur if hardware filters or QOS policies were created using
a classifier matching on: a Layer 2 attribute other than MAC Destination
(e.g. MACSA or VLAN ID), and one or more other parameters that match
on IPv4 frames (e.g. IP address, UDP/TCP parameters), and another
classifier matching on Layer 2 attributes only.
The possible problems were; a generic Layer 2 match only succeeding if the
frame was not of IP type, or false-positive matches when a frames had the
same MAC Destination as a classifier designed to match on MAC Source
address. This issue has been resolved.
If a classifier was created that used the ethformat and protocol parameters,
the resulting entry in a script created using the create config command or
show config dynamic commands was not always correct. This issue has
been resolved.
When a Novell IPX packet was received by a port in a a protocol-based
VLAN, it was being flooded out all ports on the default VLAN. This issue
has been resolved.
1.) A port was remaining in the default VLAN after having been added to
a nested VLAN.
2.) A port was being returned to the default VLAN when deleted from one
nested VLAN even if it was still a member of another nested VLAN.
3.) A port associated with a protocol or subnet rule was not being returned
to the default VLAN when deleted from a nested VLAN.
These issues have all been resolved.
The receipt of two IP packets whose destination IP addresses were subnet
addresses caused the switch to reboot. This issue has been resolved.
Wrong bits were being set in the ASIC rule table for classifiers that matched
on IPX source socket. As the result, the classifiers would match on incorrect
values of IPX source socket. This issue has been resolved.
Some MIB values for the AT-QOS MIB, have been changed so that the
output of the switch is now compatible with the latest version of the MIB.
After the disable switch learn command had been executed successfully,
automatic MAC learning was still operating. This issue has been resolved.
PCR: 40540 Module: SWI Level: 2
PCR: 40541 Module: CLASSIFIER Level: 2
PCR: 40543 Module: SWMX Level: 2
PCR: 40544 Module: VLAN Level: 2
PCR: 40549 Module: SWI Level: 2
PCR: 40550 Module: SWMX Level: 2
PCR: 40554 Module: QoS Level: 2
PCR: 40561 Module: SWMX Level: 2

Patch 89262-08 For AT-8900 Series Switches 9
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
If the command enable switch accelerator function=icmpredirect had been
executed, there was no resulting entry in a script subsequently created by
the create config or show config dynamic commands. This issue has been
resolved.
If two protocol VLAN association rules were added to two different
VLANs, the second protocol association rule would not work. This issue has
been resolved.
When PIM or DVMRP was enabled, if IP multicast packets were received on
the non-RPF (Reverse-Path-Forwarding) interface, i.e. the wrong ingress
interface, the CPU could become highly utilised, and the packets were not
correctly Layer 2 switched. This issue has been resolved.
Adding, or deleting, port=42 to, or from, a VLAN could cause the entire
Layer 2 Multicast Table to be cleared. This would subsequently cause high
CPU utilisation under heavy multicast traffic. This issue has been resolved.
If VRRP had been enabled on the switch, then the routing of any packets
that entered the switch via a an interface on which VRRP was operating
would be performed in software, rather than using the L3 switching process
in the ASIC. This issue has been resolved.
If a timed-out ARP entry was renewed by BOOTP, the new entry be created
with no port association. This issue has been resolved.
Level 3
When an accelerator card is installed, and ports had been configured for
mirroring, the enable switch mirror caused an unnecessary warning
message to be displayed. This issue has been resolved.
When an accelerator card is installed, the set switch mirror command
caused the switch to display an incorrect message saying that the maximum
port number is 54. This issue has been resolved.
In certain scenarios when acting as a DHCP server, the switch would send
a DHCP ACK to an invalid MAC address. This issue has been resolved.
PCR: 40562 Module: SWNP Level: 2
PCR: 40565 Module: SWMX Level: 2
PCR: 40571 Module: SWMX Level: 2
PCR: 40574 Module: SWMX Level: 2
PCR: 40586 Module: SWMX Level: 2
PCR: 40592 Module: BOOTP Level: 2
PCR: 40471 Module: SWI Level: 3
PCR: 40474 Module: IPG Level: 3
PCR: 40493 Module: DHCP Level: 3

10 Patch Release Note
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
When a virtual link end point is no longer reachable, the virtual interface is
not brought down, and the virtual neighbour is not removed. This issue has
been resolved.
Setting switch enhanced mode to “none” in order to disable QoS counters
did not disable the QoS counters properly. A debug error message was
shown when attempting to view the traffic class counters. This debug error
message has now been removed and an appropriate error message is now
displayed.
When MIB counters relating to packet flows reached their maximum
possible value (0xFFFFFFFF), they should have returned to 0, and counted
up from 0 again. However, they were remaining stuck at 0xFFFFFFFF.
This issue has been resolved, so that the counters will correctly roll over
from 0xFFFFFFFF to 0 and start counting up again.
Level 4
No issues.
Enhancements
The RSTP module has been enhanced to detect simple loop scenarios
downstream of an RSTP enabled edge port. If a loop is detected, the port is
placed into a Backup/Discarding/LoopbackDisabled state. In this state, all
packets are discarded. The port transitions to a Designated/Discarding
state after 3 x helloPeriod. If the loop still exists, the Backup/Discarding/
LoopbackDisabled state is repeated.
The new command show tacplus has been added. This command shows the
module status, number of servers, and number of logged in users.
PCR: 40498 Module: OSPF Level: 3
PCR: 40515 Module: QoS Level: 3
PCR: 40525 Module: SWI, SWX Level: 3
PCR: 40511 Module: RSTP
PCR: 40521 Module: TACACS+

Patch 89262-08 For AT-8900 Series Switches 11
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
Features in 89262-06
Patch file details are listed in Table 3.
Patch 89262-06 includes all issues resolved and enhancements released in
previous patches for Software Release 2.6.2, and the following enhancements:
While the switch was set with a CIDR interface address, when it received an
ECHO request with a network broadcast destination address for a class C
network, the switch sent the ECHO reply packet. Also, the switch
forwarded the ECHO request packet using a broadcast MAC address. These
issues have been resolved.
When the device operated in NTP Client mode, the SHOW TIME command
sometimes displayed the incorrect time. This issue has been resolved.
Total exception errors occurred when the OSPF DEFAULTROUTE was set
to from ON to OFF. This problem has been resolved.
OSPF did not refresh a network LSA when it received a LSA with errors
from another vendor’s device. This has now been fixed.
PIM counters were not totalling up correctly for erroneous packets if the
type of PIM packet was not known. This issue has been resolved.
Out of sequence IPSEC packets could cause a switch reboot. This issue has
been resolved.
When PIM-SM was configured and a very large number of IGMP v2 joins
were received, a switch reboot could occur. This issue has been resolved.
When expirykbytes was set to a low value in the IPsec policy, it was
possible that a memory leak could occur if heavy IPsec traffic was being
Table 3: Patch file details for Patch 89262-06.
Base Software Release File 89-262.rez
Patch Release Date 12-Aug-2004
Compressed Patch File Name 89262-06.paz
Compressed Patch File Size 274040 bytes
PCR: 31225 Module: IPG Level: 3
PCR: 40008 Module: NTP Level: 3
PCR: 40075 Module: OSPF Level: 2
PCR: 40123 Module: OSPF Level: 2
PCR: 40261 Module: PIM4 Level: 4
PCR: 40266 Module: IPSEC Level: 2
PCR: 40284 Module: PIM Level: 2
PCR: 40321 Module: ENCO, IPSEC Level: 2

12 Patch Release Note
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
transmitted while the IPsec SA renegotiation took place. This issue has been
resolved.
The IP Options fields were being processed multiple times if a Firewall or
NAT were enabled. This resulted in two Timestamps or Record_Route fields
being added at each hop, instead of one. This issue has been resolved.
All OSPF packets sent had an IP Precedence of 0 rather than 110. This issue
has been resolved.
A slow memory leak was observed in some circumstances when adding
and deleting routes in the routing table. This issue has been resolved.
If the remote PPPoE client was not responding to LCP Configure Requests,
the PPPoE access concentrator would continually send configure requests,
as the PPP template could not be configured to change this default setting.
This issue has been resolved.
The add ipv6 nd command did not work when the port parameter was
specified. This issue has been resolved.
When two devices (A and B) had an IPsec tunnel connecting them and the
default route of device A was to device B, device B had a fatal error. If A lost
a link, any packets for that link were delivered to B unencrypted. If these
packets were routed through device B to device A, then B recognised the
packets as needing to be decrypted and attempted it. This caused a fatal
error. This issue has been resolved.
Procedures for handling bgp update messages which contained an invalid
next_hop attribute specified in Section 6, RFC1711 were incorrect. This issue
has been resolved.
If the ENCO process used to encrypt an ISAKMP packet failed, a switch
reboot could occur. This issue has been resolved.
When a nested VLAN core port received a packet, it could trigger some
debug to the console port, and prevent further communication via that
console port. This issue has been resolved.
PCR: 40340 Module: IPG Level: 3
PCR: 40350 Module: OSPF Level: 2
PCR: 40372 Module: IPG Level: 2
PCR: 40378 Module: PPP Level: 2
PCR: 40399 Module: IPv6 Level: 3
PCR: 40402 Module: IPSEC Level: 2
PCR: 40403 Module: BGP Level: 2
PCR: 40405 Module: ENCO Level: 2
PCR: 40408 Module: SWMX,SWI Level: 2

Patch 89262-08 For AT-8900 Series Switches 13
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
In certain cases where static routes in a multi-path environment were used
and routes were changed on the switch, the IPv6 flow table of the switch
wasn't refreshed correctly, i.e. an entry in the flow table had no outgoing
interface and ND entry. This issue has been resolved.
The command reset qos accel was generating an unexpected error message.
This issue has been resolved.
When a master VRRP router was configured from a bootup script, the
transition to the MASTER state occurred before the Layer 2 interface had
been initialised, preventing the gratuitous ARP from being sent. This issue
has been resolved.
The output of the show qos trafficclass=x command was not correctly
indicating the state of the parameter "Ignore BandwidthClass". This issue
has been resolved.
When LS Acks (Link State Advert acks) were received, they were compared
against the transmitted LSA (Link State Advert). If it was the same, the LSA
was removed from the re-transmission list. The algorithm used in this check
has been changed to be compliant with the algorithm specified in section
13.1 of RFC2328, to determine if the LS Ack received is the instance as the
LSA.
When the IPv6 Accelerator card was enabled in loopback mode, and you
used an SNMP management station to display the forwarding database, a
random value was displayed for one CPU MAC entry. This issue has been
resolved.
A problem existed when setting non-default Firewall attack trigger levels
for SMTP attacks. The show firewall policy attack output and dynamically
generated configuration scripts were incorrect. This issue has been
resolved.
When a private VLAN had a tagged uplink, and at least one untagged
private port, a configuration generated using the create conf command
would contain incorrect information. This issue has been resolved.
PCR: 40411 Module: IP6 Level: 2
PCR: 40413 Module: QOS Level: 3
PCR: 40415 Module: VRRP Level: 2
PCR: 40416 Module: QOS Level: 3
PCR: 40417 Module: OSPF Level: 3
PCR: 40418 Module: SWMX Level: 3
PCR: 40422 Module: FIREWALL Level: 3
PCR: 40425 Module: VLAN Level: 2

14 Patch Release Note
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
When the IPV6 accelerator card was present but disabled, the switch was
not transmitting CPU-initiated packets after receiving non-reserved
multicast packets. This issue has been resolved.
When the nested VLAN feature was disabled using the disable feature
command, the switch did not remove, from software and hardware, all of
the nested VLAN’s associated ports, protocols and subnets as well as the
nested vlans. This issue has been resolved.
For those classifiers that specified the IP protocol as a match criterion, the IP
protocol number was being stored and displayed in a configuration file as a
hexadecimal value rather than a decimal value. This issue has been
resolved.
If VRRP was enabled and a reset ip command was issued followed by a
disable vrrp command, then the device would still reply to pings, even
though the device was no longer the VRRP master. Duplicate echo replies
were seen on the device sending the pings. This issue has been resolved.
In certain situations, if a DHCP client used a DHCP relay agent to request
IP addresses from the switch acting as the DHCP server on a different
subnet, it was not be able to renew the IP address allocated to it. This issue
has been resolved.
Particular IP packets (unicast destination IP, but multicast destination
MAC) could result in a memory leak, which in some cases could cause the
device to stop responding to the command line. This issue has been
resolved.
The enable/disable switch accelerator commands could be executed even
though no IPv6 accelerator card was installed. This issue has been resolved.
The switch was accepting network RIP packets from foreign subnets. This
issue has been resolved.
PCR: 40431 Module: SWMX Level: 2
PCR: 40433 Module: VLAN Level: 2
PCR: 40440 Module: CLASSIFIER Level: 3
PCR: 40441 Module: IPG, VRRP Level: 4
PCR: 40446 Module: DHCP Level: 2
PCR: 40453 Module: IPG Level: 2
PCR: 40454 Module: SWNP Level: 3
PCR: 40458 Module: IPG Level: 2

Patch 89262-08 For AT-8900 Series Switches 15
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
Under the IPv6 multipath environment, e.g. when both a static route and a
RIPng route were available, if the static route was disconnected, the switch
used the CPU to transmit outgoing packets on the RIPng Route, i.e using
software routing. This issue has been resolved.
NetBios responses to NetBeui packets were not being classified by a
protocol based VLAN. This was because both are represented by 0xF0, but
in the packet NetBios is 0xF0F1 and NetBeui is 0xF0F0. Now, when adding
a VLAN classification rule for NetBeui (0xF0), two classification rules are
added to the hardware. One for NetBeui (0xF0F0), and one for
NetBios(0xF0F1).
Features in 89262-05
Patch file details are listed in Table 4.
Patch 89262-05 includes all issues resolved and enhancements released in
previous patches for Software Release 2.6.2, and the following enhancements:
Occasionally a fatal error might be observed when the switch was removing
IPv6 multicast downstream interfaces (for example, when downstream
clients left a multicast group). This issue has been resolved.
If the switch was configured with nested VLANs, and a command was
entered to disable the nested VLAN feature, then a fatal error was observed
as the switch removed the configured nested VLANs. This issue has been
resolved.
A fatal error was observed after entering the command restart reboot or
restart switch, when there were 1000 IPv6 interfaces configured on the
device with all links up. This issue has been resolved.
A Watchdog fatal error was observed when many (e.g. >1000) IPv6
interfaces configured on the device join a multicast group all at once. This
issue has been resolved.
PCR: 40463 Module: IPG Level: 2
PCR: 40509 Module: SWMX Level: 3
Table 4: Patch file details for Patch 89262-05.
Base Software Release File 89-262.rez
Patch Release Date 6-Jul-2004
Compressed Patch File Name 89262-05.paz
Compressed Patch File Size 222160 bytes
PCR: 40304 Module: IPv6 Level: 2
PCR: 40371 Module: VLAN Level: 2
PCR: 40397 Module: IPv6 Level: 2
PCR: 40409 Module: SWNP Level: 2

16 Patch Release Note
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
Features in 89262-04
Patch file details are listed in Table 5.
Patch 89262-04 includes all issues resolved and enhancements released in
previous patches for Software Release 2.6.2, and the following enhancements:
Occasionally the device suffered a fatal error if it received a large number of
directed broadcast packets. This issue has been resolved.
Adding the maximum number of allowed filters to an IPv6 Accelerator
hardware filter set (filling the hardware filters to capacity) would delete all
existing filters and fail. This issues has now been resolved. The device now
correctly accepts a full set of hardware filters.
When multiple RIPng routes existed, the correct route was not chosen by
the device. This issue has been resolved.
Attempts to ping a site-local address from a global unicast address would
fail. This issue has been resolved.
GVRP added tagged ports to dynamic VLANs as static entries. As a result,
these member ports were not timed out or deregistered properly when the
ports were disabled, the link went down, or GARP was disabled. This issue
has been resolved. In addition, GVRP no longer operates on private or
nested VLANs.
IPv6 Accelerator MIB counters could not be reset. This issue has been
resolved.
The terminal session would freeze when a large number of IPv6 Accelerator
hardware filters were added. This issue has been resolved.
Table 5: Patch file details for Patch 89262-04.
Base Software Release File 89-262.rez
Patch Release Date 25-Jun-2004
Compressed Patch File Name 89262-04.paz
Compressed Patch File Size 221932 bytes
PCR: 40279 Module: IPG Level: 2
PCR: 40313 Module: SWNP Level: 3
PCR: 40344 Module: IP6 Level: 2
PCR: 40349 Module: IPv6 Level: 3
PCR: 40351 Module: VLAN Level: 3
PCR: 40352 Module: SWNP Level: 3
PCR: 40363 Module: SWNP Level: 3

Patch 89262-08 For AT-8900 Series Switches 17
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
When a large number of IPv6 interfaces were configured:
• a boot script could take several minutes to process
• processing multicast updates could take several minutes
• high packet loss sometimes occurred when updating hardware for a
change in IPv6 multicast membership
These issues have been resolved.
Enhancements to tuning and buffer configuration settings have improved
reliability at extreme temperatures and performance.
The QoS MIB has been restructured to separate generic switching and
AT-8948 specific MIB variables. Traffic class counters were always returned
as 0. This PCR modifies PCR 40213 (see “Features in 89262-02” on page 21).
You should obtain the latest revision of the QoS MIB from your authorised
Allied Telesyn distributor, reseller or customer service representative.
The create config command generated duplicate entries for the protocol
parameter in IPv6 classifiers. This issue has been resolved.
The ifJackType MIB object (RFC 2239) always returned the value BNC,
regardless of the actual GBIC/SFP installed. The correct value for the
installed GBIC/SFP (e.g. Fiber, LC, BNC) is now returned.
The command:
set qos port defaultqueue=value forcedefqueue=yes
failed to enforce the use of the default queue. This issue has been resolved.
When the firewall was used on a NAT interface in conjunction with IP
policy filters, Telnet to this interface was not possible. This issue has been
resolved.
When VRRP was enabled and an IP interface on which VRRP was operating
went down, VRRP was not being disabled, preventing VRRP from
transitioning to the Initial state. This issue has been resolved.
When IGMP Snooping was disabled the DVMRP forwarding database was
not updated correctly. This issue has been resolved.
PCR: 40365 Module: EZDRV, IPv6, SWNP Level: 2
PCR: 40367 Module: SWMX Level: 3
PCR: 40376 Module: QOS Level: 3
PCR: 40380 Module: CLASSIFR Level: 3
PCR: 40391 Module: SWMX Level: 4
PCR: 40396 Module: SWMX Level: 3
PCR: 40116 Module: FIREWALL Level: 2
PCR: 40355 Module: VRRP Level: 3
PCR: 40364 Module: IPG Level: 3

18 Patch Release Note
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
The IPv6 Accelerator Card port (port 53) can only be associated with a QOS
policy containing classifiers that specify ethii-tagged as the Ethernet
encapsulation and IPv6 as the protocol:
create classifier=rule-id ethformat=ethii-tagged
protocol=ipv6 [other-parameters...]
The add qos port command now checks that all classifiers associated with
the QoS policy being assigned to the port specify ethformat=ethii-tagged
and protocol=ipv6.
Features in 89262-03
Patch file details are listed in Table 6:
Patch 89262-03 includes all issues resolved and enhancements released in
previous patches for Software Release 2.6.2, and the following enhancements:
It is now possible to prevent specified ports from acting as IGMP all-group
ports, and specify which ports are allowed to behave as all-group entry
ports. This is enabled with the ENABLE IP IGMP ALLGROUP command,
and disabled with the DISABLE IP IGMP ALLGROUP command.
For details, see “IGMP Snooping All-Group Entry” on page 23.
The switch was adding a router port for multicast packets to destinations
with an address in the range 224.0.0.x. Switch port entries are now only
created for special router multicast addresses.
This PCR introduces an enhancement that extends an issue that was
resolved in PCR 03890, in which switch port entries are only created for
special router multicast addresses. It is now possible to specify reserved
multicast addresses that will be treated as multicast packets from routers.
For details, see “IGMP Snooping” on page 25.
PIM Dense Mode Graft and GraftAck messages were not being sent. This
issue has been resolved.
PCR: 40382 Module: SWMX Level: 3
Table 6: Patch file details for Patch 89262-03.
Base Software Release File 89-262.rez
Patch Release Date 02-Jun-2004
Compressed Patch File Name 89262-03.paz
Compressed Patch File Size 181136 bytes
PCR: 03420 Module: IPG, SWI Level: 3
PCR: 03890 Module: IGMP, SWI Level: 2
PCR: 31133 Module: IPG
PCR: 40112 Module: PIM6 Level: 2

Patch 89262-08 For AT-8900 Series Switches 19
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
Fibre SFPs can now be set to a fixed speed. Copper SFPs still can not have
their speed parameters modified.
The maximum number of PIM6 interfaces has been increased from 255 to
2000. The number of MLD interfaces has also been increased to 2000 to
match the maximum number of PIM interfaces.
In SNMPv2c the histroyControlBucketsGranted value was outside the
acceptable range. This issue has been resolved.
BGP routes were not always readvertised to peers after a next-hop route
was lost and then reactivated. This issue has been resolved.
The device’s own MAC address was accepted as the next hop MAC address
when adding a static IP ARP entry with the add ip arp command, or an IPv6
neighbour with the add ipv6 nd command. This issue has been resolved.
An incorrect nexthop for a RIP route was advertised in RIP messages. This
issue has been resolved.
When the most recently added VLAN was deleted, the switch did not
respond correctly to subsequent DHCP Discover messages. This issue has
been resolved.
The value for the Device rule space limit in the output of the show switch
command was incorrect. This issue has been resolved.
Incorrect options were returned with “?” help for the show switch
accelerator command. This issue has been resolved.
A memory leak sometimes occurred when many HTTPS sessions (using
SSL) were load balanced. This issue has been resolved.
The incorrect parameter ipaddress was returned with “?” help for the
delete ipv6 host=name command. This issue has been resolved.
IPv6 packets travelling through a 6-to-4 tunnel were sent to an incorrect
IPv4 end address, although the first packet was sent correctly. This issue has
been resolved so that all packets are sent to the correct address.
PCR: 40249 Module: SWI, SWMX
PCR: 40270 Module: PIM6
PCR: 40274 Module: VLAN, RMON Level: 3
PCR: 40277 Module: IPG Level: 2
PCR: 40289 Module: IPG, IPV6 Level: 2
PCR: 40290 Module: IPG Level: 3
PCR: 40299 Module: IPG Level: 2
PCR: 40301 Module: SWMX Level: 3
PCR: 40302 Module: SWI, SWNP Level: 3
PCR: 40307 Module: SSL Level: 2
PCR: 40310 Module: IPV6 Level: 3
PCR: 40312 Module: IPV6 Level: 2

20 Patch Release Note
Patch 89262-08 for Software Release 2.6.2
C613-10402-00 REV H
The next hop of an IPv6 RIPng Response message was not assigned with a
link local address when an invalid next hop was specified in the prefix field
of the route table entry. This issue has been resolved.
An error message was not returned if an unavailable interface was specified
for the enable test interface command. This issue has been resolved.
A dynamic VLAN created by GVRP should contain a tagged port, but it did
not. This issue has been resolved.
When an untagged port was added to a non-default VLAN, and then set as
tagged, it could not be added back to the default VLAN as an untagged
port. This issue has been resolved.
Hardware filtering has been enhanced so that the traffic class can be
remapped using classifiers and hardware filtering. This can increase the
chance of packets that match the classifier reaching the CPU because they
are transmitted to the CPU on a different queue and DMA channel. To
configure this type of filtering, use the command add switch hwfilter
action=setl2qos.
It was not possible to set a QoS policy to a port if the corresponding
classifier with IPv6 parameters was changed. This issue has been resolved.
If there were more than one port connected on the same IPv6 interface,
traffic stopped if a cable was unplugged from the egress port of the switch
and then plugged into a different port. This issue has been resolved.
STP restarted when GVRP sent a Join message for a newly created dynamic
VLAN. This issue has been resolved.
PCR: 40318 Module: IPV6 Level: 2
PCR: 40322 Module: TM Level: 3
PCR: 40334 Module: VLAN Level: 2
PCR: 40338 Module: VLAN Level: 2
PCR: 40341 Module: SWMX, SWI
PCR: 40342 Module: SWI Level: 2
PCR: 40343 Module: IPV6, VLAN Level: 2
PCR: 40348 Module: VLAN Level: 2