Allied Telesis AT-9800 Series Instruction Manual

Software Maintenance Release Note
Release sb273-01
For SwitchBlade 4000 Series Switches and
AT-9800 Series Switches
Introduction
This software maintenance release note lists the issues addressed, and
enhancements made, in patch SB273-01 for Software Release 2.7.3 on existing
models of the SwitchBlade and AT-9800 series switches. Release file details are
listed in Table 1.
This release note should be read in conjunction with the following documents:
■SwitchBlade document Set for Software Release 2.7.3 (Document Number
C613-03100-00 REV A).
■AT-9800 Series Switches Documentation Set for Software Release 2.7.3
(Document Number C613-03101-00 REV A).
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: Release file details for release SB273-01.
Base Software Release File SB-273.rez
Maintenance Release Date April 22 2005
Compressed Release File Name SB262-01.rez
Compressed Release File Size 91,532 bytes

2 Enabling and installing this Release Software Maintenance Release Note
Release sb273-01
C613-10436-00 Rev A
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:
Enabling and installing this Release
To use this maintenance release you must have a base release license for
Software Release 2.7.3. Contact your distributor or reseller for more
information.
To enable this release and install it as the preferred release, use the commands:
enable rel=sb273-01.rez num=2.7.3
set install=pref rel=sb273-01.rez
Features in sb273-01
sb273-01.rez includes the following issues resolved and enhancements
released:
Level 1
A heavy processor load could lead to queuing RSTP BPDUs, which in turn
could lead to even more processor load, resulting in more queued BPDUs.
This issue has been resolved by improving the efficiency in the interaction
between RSTP TCN BPDUs and the hardware tables.
This issue has been resolved. (PCR number: 40672)
When failover occurred between a redundant pair of Load Balancing
devices, host ARP caches were not updated with the new Master's MAC
address, thus causing the hosts to lose connectivity until their ARP caches
timed out the stale entry. This issue has been resolved. (No PCR number.)
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.
CR00005227 Module: SWI, RSTP, SWMX,
SWCX, SW56
Level: 1
CR00006609 Module: LB Level: 1

Release sb273-01 3
Release sb273-01
C613-10436-00 Rev A
A reboot could occur while ageing out Firewall sessions when the device
was under heavy load and had many active Firewall sessions.
This issue has been resolved. (No PCR number.)
When either the Firewall was enabled or multiple L2TP tunnels were
configured, and a default route existed over an L2TP tunnel, it was possible
for an infinite internal packet loop to be created when a packet was sent
over the L2TP tunnel after the underlying interface route to the remote IP
had gone down. This caused a reboot to occur.
This issue has been resolved. (No PCR number.)
Level 2
Previously, the forwarding database was flushed instead of being aged out
when an STP topology change notification was received.
This issue has been resolved. (PCR number: 40185)
Previously, when a port or ports was moved from one VLAN to another, the
switch would reset both STP/RSTP instances that control the VLANs. This
behaviour is now changed to only reset the STP process on the STP instance
that the port(s) is joining. The switch will now also retain the port(s) edge-
port setting during the moving process.
This issue has been resolved.
When routers and switches were using CIDR addressing, with a unicast
address coinciding with a network broadcast address of class A, B, or C,
then they could incorrectly forward traffic as directed broadcasts, even
though the traffic was unicast (only).
This issue has been resolved. (PCR number: 50069)
When Cisco encapsulation was used on a frame relay interface, the router
was not recognising bridged packets. This issue has been resolved.
Also, specifying a logical frame relay interface when adding a bridge port
has been explicitly disallowed. (No PCR number.)
CR00007034 Module: Firewall Level: 1
CR00007695 Module: PPP Level: 1
CR00002290 Module: STP, SWI Level: 2
CR00002662 Module: STP Level: 2
CR00007341 Module: IPG Level: 2
CR00007358 Module: BRG, FR Level: 2

4 Features in sb273-01 Software Maintenance Release Note
Release sb273-01
C613-10436-00 Rev A
Previously, when the packet overhead limits were exceeded, some packets
were being silently dropped by SQoS.
This issue has been resolved.
Additionally, extra checking has been added to the ATM process so that it
will explicitly drop, and count, any packets that still exceed the overhead
limit. This will aid in the diagnosing of any other cases where packets are
being dropped. (No PCR number.)
The AR026 4-port Ethernet PIC was not capable of receiving 1519-1522 byte
VLAN-tagged packets. Instead, these packets were dropped because they
were considered too long.
Also, some early revisions of the AR720 and AR740 were not capable of
receiving 1519-1522 byte VLAN-tagged packets.
These issues have been resolved. (PCR number: 50065)
When the router was acting as an L2TP Access Concentrator (LAC) it would
fail to negotiate a Virtual tunnel to another vendor’s LNS. This was due to
invalid Proxy LCP AVPs being used within the ICCN message.
This issue has been resolved. (No PCR number.)
On 9800 series switches with GBICs installed, if a GBIC with an active link
was physically removed the interface would not go DOWN.
This issue has been resolved. (No PCR number.)
When hot-swapping a Switch Blade line card, the trunking information on
other line cards could get over-written and cause the switch to stop
forwarding traffic.
This issue has been resolved. (No PCR number.)
Level 3
IP interfaces over X25 were not operating correctly. This issue has been
resolved. (No PCR number.)
The DNS relay has been changed to allow the relay of resource record types
between 0x1d and 0xff. Previously packets with these types of resource
records were dropped.
This issue has been resolved (No PCR number.)
CR00007417 Module: ATM,ENCO Level: 2
CR00007428 Module: ETH Level: 2
CR00007436 Module: L2TP Level: 2
CR00007770 Module: SWI Level: 2
CR00008127 Module: SWI Level: 2
CR00006086 Module: x25t Level: 3
CR00007476 Module: IPG Level: 3

Release sb273-01 5
Release sb273-01
C613-10436-00 Rev A
DVMRP packets were being dropped due to packet length inconsistencies
from other vendor devices.
This issue has been resolved. (No PCR number.)
If ATM is receiving a OAM loopback cell (normal from an ISP) at regular
intervals then it may cause a reboot. This fix stops this behaviour and will
also stop some other random packet corruption.
This issue has been resolved. (PCR number: 50064)
Previously, when changing the password on a log output/receive definition
to a shorter string, the log message exchange could fail.
This issue has been resolved. (PCR number: 50070)
When changing VLAN configuration on the Switchblade, MAC addresses
on the ports that move to a new VLAN need to be deleted. This address
deletion process has been made significantly more efficient, minimising the
impact on general switch operation.
This issue has been resolved. (No PCR number.)
Level 4
There was not enough information displayed to the user when the
ACTIVATE FLASH COMPACTION command was entered at the same time
as Flash was compacting.
This issue has been resolved. (No PCR number.)
Enhancements
Previously ISAKMP NAT-T was enabled by default on every ISAKMP
policy created. NAT-T is now disabled by default on every ISAKMP policy.
(No PCR number.)
The ability to configure Van Jacobson Header Compression over dynamic
PPP interfaces has been added. To this end, the command parameter
'VJC={ON|OFF}' has been added to the CREATE and SET PPP TEMPLATE
commands. (No PCR number.)
CR00007521 Module: IPG Level: 3
CR00007686 Module: ATM Level: 3
CR00007716 Module: LOG Level: 3
CR00007760 Module: SWCX, SWITCH Level: 3
CR00006093 Module: FFS Level: 4
CR00006652 Module: IKMP, IPSEC
CR00006953 Module: PPP