Allied Telesis 86253-07 Instruction Manual

Simply connecting the world
Patch Release Note
Patch 86253-07
For Rapier Series Switches
Introduction
This patch release note lists the issues addressed and enhancements made in
patch 86253-07 for Software Release 2.5.3 on existing models of Rapier 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.5.3 for Rapier Switches and AR400 and
AR700 Series Routers (Document Number C613-10362-00 Rev A) available
from www.alliedtelesyn.co.nz/documentation/documentation.html.
■Rapier Switch Documentation Set for Software Release 2.5.1 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 86253-07.
Base Software Release File 86s-253.rez
Patch Release Date 18-Feb-2004
Compressed Patch File Name 86253-07.paz
Compressed Patch File Size 333756 bytes

2Patch Release Note
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
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:
Features in 86253-07
Patch 86253-06 was not released.
Patch 86253-07 includes all issues resolved and enhancements released in
previous patches for Software Release 2.5.3, and the following enhancements:
TCP Keepalive packets for FTP sessions were passing through the firewall
during the TCP setup stage with TCP Setup Proxy enabled. Keepalive
packets include sequence numbers that have already been acknowledged.
Such packets now fail stateful inspections and are dropped by the FTP
application-level gateway.
The PIM-DM prune expiry time was not reset when a State Refresh message
was received. This issue has been resolved.
When policy-based routing was active, IP packets not matching any policy-
specific routes were forwarded, even if there was no default policy route.
This issue has been resolved. Now, a route whose policy exactly matches the
policy of the packet is selected. If an exact match does not exist, a route with
the default policy will be used to route the packet. If no route is found, the
packet is discarded. The TOS field in incoming IP packets is ignored, so
packets with the TOS value set are forwarded using a route with the default
policy.
When a ping was sent to the device’s link-local address, the device flooded
the ICMP Reply packet over the VLAN. This issue has been resolved.
Occasionally when a device rebooted its OSPF routes were missing from the
route table. 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: 03941 Module: FIREWALL Level: 2
PCR: 03961 Module: PIM, PIM6 Level: 2
PCR: 03997 Module: IPG Level: 3
PCR: 31080 Module: IPv6 Level: 2
PCR: 31104 Module: OSPF Level: 2

Patch 86253-07 For Rapier Series Switches 3
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
A memory leak occurred if DNS relay was configured, and the device kept
receiving DNS Query packets. This issue has been resolved.
PIM6 could not send unicast bootstrap messages to a new neighbour. This
issue has been resolved.
If the SMTP Proxy detected a third party relay attack, the “SMTP third
party relay attack” trigger message was not displayed. This issue has
been resolved.
The forwarding database table sometimes did not update correctly when
multiple packets with the same MAC source address were sent to the switch
via different ports. This issue has been resolved.
The HWQUEUE parameter in the SET QOS HWQUEUE command
incorrectly accepted values from 0 to 9999. The upper limit for this
parameter is 3. This issue has been resolved. The correct limit is now
enforced.
Two VRRP log messages were displayed when they should not have been.
The log messages were:
Vrrp 1: Vlan vlan2 10 Port Failed decrementing priority by 20
Vrrp 1: Vlan vlan2 1 Port up incrementing priority by 2
This issue has been resolved. These messages are now displayed at the
correct time.
OSPF neighbours did not establish the Full state when IP route filters were
applied. This issue has been resolved.
The neighbour discovery timeout has been set to 3 seconds in ICMPv6 to
speed up Destination Unreachable detection.
The badQuery and badRouterMsg counters in the SHOW IGMP and SHOW
IGMPSNOOPING commands were not incrementing correctly. This issue
has been resolved.
When an Inter-area route went down and the only other route to the
destination was an AS-External route, the AS-External route was not
selected. This issue has been resolved.
PCR: 31160 Module: IPG Level: 2
PCR: 31176 Module: PIM6 Level: 2
PCR: 31178 Module: FIREWALL Level: 4
PCR: 31200 Module: SWI Level: 2
PCR: 31202 Module: QOS Level: 3
PCR: 31205 Module: VRRP Level: 3
PCR: 31220 Module: OSPF Level: 2
PCR: 31223 Module: IPV6 Level: 3
PCR: 31224 Module: IPG Level: 3
PCR: 31230 Module: OSPF Level: 3

4Patch Release Note
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
A filter entry was lost when the SET SWITCH L3FILTER ENTRY command
did not succeed. This issue has been resolved.
Link-local addresses can only be unicast addresses. If a link-local address
was added as an anycast address, no error message was returned. This issue
has been resolved. Now, an error message is returned stating that a link-
local address must be a unicast address.
The Maximum Transmission Unit (MTU) was not always set to the MTU
value in the ICMP Packet Too Big Message sent from the device. This issue
has been resolved.
After IGMP snooping was disabled, multicast data was not flooded to
VLANs. This was because the multicast route forwarding port map was
cleared. This issue has been resolved.
The forwarding database table sometimes did not update correctly when
multiple packets with the same MAC source address were sent to the switch
via different ports. This issue has been resolved.
If DHCP clients do not respond to echo requests, the DHCP server can not
detect an addressing conflict, so may offer inuse addresses to clients. This
issue has been resolved.
This PCR introduces a new parameter, PROBE, to the CREATE DHCP
RANGE and SET DHCP RANGE commands. This parameter allows for
address probing using ARP requests and replies instead of the normal ping
mechanism. This feature is limited to clients on the same subnet (broadcast
domain) as the DHCP server, and therefore can not be used with the
GATEWAY parameter.
The new syntax is:
CREATE DHCP RANGE=name [PROBE={ARP|ICMP}]
[other-parameters]
SET DHPC RANGE [PROBE={ARP|ICMP}] [other-parameters]
When the DHCP server rejected a DHCPRequest message, the requested IP
address was not logged correctly. This issue has been resolved.
PCR 31128 introduced an issue that occasionally caused a fatal error with IP
flows. This issue has been resolved.
PCR: 31233 Module: L3F Level: 2
PCR: 31236 Module: IPV6 Level: 3
PCR: 31239 Module: IPV6 Level: 3
PCR: 31247 Module: VLAN, IPG Level: 2
PCR: 31253 Module: SWI, SW56 Level: 2
PCR: 31258 Module: IPG, DHCP
PCR: 31259 Module: DHCP Level: 2
PCR: 31268 Module: IPG Level: 2

Patch 86253-07 For Rapier Series Switches 5
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
Entering “?” after a command at the CLI gives context-sensitive Help about
parameters valid for the command. Occasionally, commands (for example,
ENABLE IP MULTICASTING) were executed when “?” was entered at the
end of the command. This issue has been resolved.
Executing the SHOW DEBUG command caused a fatal error if the
temporary log had been destroyed with the DESTROY LOG
OUTPUT=TEMPORARY command. This issue has been resolved.
When an interface-based enhanced NAT was defined in a firewall policy,
and a reverse NAT rule was defined to redirect traffic to a proxy server, the
reverse NAT did not work correctly. The proxy server did not receive any
traffic from the device. This issue has been resolved.
When the device operated in NTP Client mode, the SHOW TIME command
sometimes displayed the incorrect time. This issue has been resolved.
The device sometimes rebooted when OSPF on demand was enabled for
PPP. This issue has been resolved.
When a port’s ingress limit was set to less than 1000 with the
INGRESSLIMIT parameter in the SET SWITCH PORT command, sending
packets to a tagged port caused FCS errors on transmission. This issue has
been resolved.
The timeout interval for IGMP group membership now conforms to RFC
2236 for IGMPv2.
After a Summary LSA for the default route in a stub area had been refreshed
by an Area Border Router, and the Area Border Router was restarted, the
Summary LSA was not advertised into the stub area again. This issue has
been resolved.
PCR: 31270 Module: CURE, IPG, ATK,
DVMRP, IPX2, LB, LOG, SNMP,
UTILITY
Level: 3
PCR: 40006 Module: LOG Level: 2
PCR: 40007 Module: FIREWALL Level: 2
PCR: 40008 Module: NTP Level: 3
PCR: 40012 Module: IPG, OSPF Level: 2
PCR: 40020 Module: SW56 Level: 3
PCR: 40023 Module: IPG Level: 2
PCR: 40038 Module: OSPF Level: 2

6Patch Release Note
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
Features in 86253-05
Patch file details are listed in Table 2:
Patch 86253-05 includes all issues resolved and enhancements released in
previous patches for Software Release 2.5.3, and the following enhancements:
A buffer leak occurred when rapid STP was specified with the SET STP
MODE=RAPID command, but STP had not been enabled with the ENABLE
STP command. This issue has been resolved.
When a connector was plugged into one physical interface, the RIPng
request packet was erroneously transmitted from all interfaces on the
switch. This issue has been resolved.
The STATIC and INTERFACE options have been removed from the
PROTOCOL parameter in the ADD IP ROUTE FILTER and SET IP ROUTE
FILTER commands. These parameters were redundant because received
static and interface routes are always added to the route table.
A fatal error occurred in the text editor while selecting blocks and scrolling
up. This issue has been resolved.
When RIP demand mode was enabled, and one interface changed to a
reachable state, the triggered Request packet was not sent from that
interface, and triggered Response packets were not sent from all other RIP
interfaces. This resulted in slow convergence of routing tables across the
network. This issue has been resolved.
Repeated Assert messages were sent after the prune limit expired. This issue
has been resolved. The default dense mode prune hold time has been
changed from 60 seconds to 210 seconds.
The following two issues have been resolved:
• Large CRL files were not decoded correctly.
• The certificate database was not validated immediately after the CRL
file was updated.
Table 2: Patch file details for Patch 86253-05.
Base Software Release File 86s-253.rez
Patch Release Date 26-November-2003
Compressed Patch File Name 86253-05.paz
Compressed Patch File Size 700793 bytes
PCR: 03781 Module: STP Level: 2
PCR: 03861 Module: IPV6 Level: 2
PCR: 03873 Module: IPG Level: 4
PCR: 03905 Module: TTY Level: 3
PCR: 03910 Module: IPG Level: 3
PCR: 03926 Module: PIM Level: 2
PCR: 03940 Module: PKI Level: 1

Patch 86253-07 For Rapier Series Switches 7
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
On AT-8800 series switches, strict QoS scheduling is now enforced for ports
where egress rate limiting is applied. On Rapier i series switches, the same
QoS setup is now applied to all of the appropriate ports when setting up
egress rate limiting.
If an IPv6 filter that blocked traffic on a VLAN interface was removed, the
traffic was still blocked. This issue has been resolved.
The SMTP proxy did not correctly filter sessions where messages were
fragmented. This had the potential to prevent the detection of third-party
relay attacks. This issue has been resolved.
The AUTHENTICATION parameter has been removed from the “?” CLI
help for firewall commands. This was not a valid parameter.
Occasionally some firewall timers stopped early, resulting in sessions being
removed prematurely. Because of this, TCP Reset packets could be sent by
the firewall before TCP sessions were finished. This issue has been resolved.
When policy-based routing was active, IP packets not matching any policy-
specific routes were forwarded, even if there was no default policy route.
This issue has been resolved. Now, a route whose policy exactly matches the
policy of the packet is selected. If an exact match does not exist, a route with
the default policy will be used to route the packet. If no route is found, the
packet is discarded. The TOS field in incoming IP packets is ignored, so
packets with the TOS value set are forwarded using a route with the default
policy.
Sometimes the device rebooted when a severe multicast storm occurred due
to a loop in the network. This issue has been resolved.
If a SHOW command that displayed a lot of information, such as SHOW
DEBUG, was executed when the device’s free buffer level was very low, the
device sometimes became unresponsive. This could also occur if many
SHOW commands were executed through a script. This issue has been
resolved.
The server string was not copied correctly into an HTTP file request when
loading information from the configuration script. This issue has been
resolved.
PCR: 03953 Module: SW56 Level: 3
PCR: 03970 Module: IPV6 Level: 3
PCR: 03982 Module: FIREWALL Level: 3
PCR: 03993 Module: FIREWALL Level: 4
PCR: 03996 Module: FIREWALL Level: 2
PCR: 03997 Module: IPG Level: 3
PCR: 31002 Module: UTILITY Level: 2
PCR: 31004 Module: TTY Level: 2
PCR: 31009 Module: HTTP Level: 3

8Patch Release Note
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
When two devices are BSR candidates, and have the same preference set
with the SET PIM BSRCANDIDATE PREFERENCE command, the device
with the higher IP address was not elected as the candidate. This issue has
been resolved.
A Prune message sent to an old RP neighbour was ignored when a new
unicast route was learned. This issue has been resolved.
On Rapier series switches, an Assert message was not sent after the prune
limit expired. This issue has been resolved.
The log message “IGMP Snooping is active, L3FILT is activated”
has been changed to “IGMP packet trapping is active, L3FILT is
activated”. The revised message is clearer when IGMP is enabled and
IGMP snooping is disabled.
The following changes have been made to the ADD FIREWALL POLICY
RULE and SET FIREWALL POLICY RULE commands:
• An IP address range for the IP parameter is now only accepted when
enhanced NAT is configured.
• An IP address range for GBLREMOTE parameter is now only accepted
when reverse or reverse-enhanced NAT is configured.
• The GBLIP parameter is not accepted for a public interface when
enhanced NAT is configured.
When the interval between the NTP server and client exceeded 34 years 9
days and 10 hours, the time set on the client was incorrect. This issue has
been resolved.
MVR was not operating if IGMP had not been enabled. This issue has been
resolved.
A fatal error occurred when the PURGE STP command was executed when
STP instances were defined with VLAN members. This issue has been
resolved.
PCR: 31040 Module: PIM Level: 2
PCR: 31041 Module: PIM Level: 3
PCR: 31042 Module: PIM Level: 3
PCR: 31044 Module: SWI Level: 4
PCR: 31052 Module: FIREWALL Level: 3
PCR: 31058 Module: NTP Level: 3
PCR: 31063 Module: IPG Level: 2
PCR: 31068 Module: STP Level: 2

Patch 86253-07 For Rapier Series Switches 9
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
The warning given when a QoS policy is active on a port operating at
reduced speed has been changed to reflect the problem more accurately. The
old message was:
Warning (2087343): Port <Port num> is currently used in QoS
policy <QoS policy num>, this policy may become incorrect
due to the port bandwidth.
The new message is:
Warning (2087350): Port <Port num> is operating at less than
its maximum speed: this may affect QoS policy <QoS policy
num>.
If the DISABLE SWITCH PORT command appeared in the configuration
script, an interface could come up even though ifAdminStatus was set to
‘down’. This issue has been resolved.
The root bridge did not transmit BPDU messages with changed hellotime,
forwarddelay and maxage values. This issue has been resolved.
LDAP could not receive large messages spanning multiple packets. This
issue has been resolved.
Files with lines over 132 characters in length could not be transferred using
TFTP. This limit has now been raised to 1000 characters to match the
maximum command line length.
The SHOW FILE command caused an error when the displayed file had a
duplicate entry due to file size mismatch. This issue has been resolved. An
error message is now logged when the SHOW FILE command detects a
duplicate file. The first FFS file will be deleted when a duplicate exists.
Static DHCP address ranges were not reclaimed if the Reclaim operation was
interrupted by the interface going down. This issue has been resolved.
In the output of SHOW FIREWALL EVENT command, the DIRECTION of
denied multicast packets was shown as “out”, not “in”. This issue has been
resolved.
A small amount of memory was consumed by each ISAKMP exchange if an
ISAKMP policy's REMOTEID was set as an X.500 distinguished name with
the CREATE ISAKMP POLICY command. This issue has been resolved.
PCR: 31071 Module: SWI Level: 4
PCR: 31072 Module: SWI Level: 3
PCR: 31082 Module: STP Level: 2
PCR: 31085 Module: LDAP Level: 3
PCR: 31094 Module: FILE Level: 3
PCR: 31096 Module: FFS Level: 3
PCR: 31098 Module: DHCP Level: 3
PCR: 31099 Module: FIREWALL Level: 4
PCR: 31105 Module: ISAKMP Level: 3

10 Patch Release Note
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
When the device received a version 1 Query packet, it become a non-querier
on that interface, even if it should have remained as the querier. This issue
has been resolved.
When the TYPE parameter was specified for the ADD SWITCH L3FILTER
command, the type was sometimes a different value in the device’s
hardware table. This issue has been resolved.
The maximum value that the MESSAGES parameter accepted for the
CREATE LOG OUTPUT command was different from the value that could
be set with the SET LOG OUTPUT command. The DESTROY LOG
OUTPUT command did not release the NVS memory that was reserved for
the output. These issues have been resolved.
The etherHistoryIntervalStart node in the etherHistoryTable showed incorrect
values for the first and last 30 second interval periods. This issue has been
resolved.
If a rule based NAT was added to the firewall’s public interface, the firewall
forwarded ICMP Request packets even if ICMP forwarding was disabled.
This issue has been resolved.
When a large number of directed broadcast packets were received, CPU
usage increased up to 100%. This occurred because a log message was
generated each time a directed broadcast packet was deleted. This issue has
been resolved. Log messages are now rate-limited to a maximum of one log
message every 10 seconds for a directed broadcast flow. After the first
deletion is logged, subsequent log messages include a counter showing the
number of directed broadcast packets in the same flow that were deleted
since the last log message.
A fatal error occurred if IPX was disabled and then re-enabled when there
was a high rate of incoming IPX traffic on the device. This issue has been
resolved.
The DHCP server did not take any action when it received a DHCP decline
packet. This was because the device only checked the ciaddr field in the
packet, and not the RequestedIPAddress option. This issue has been resolved.
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.
Use the following commands to configure this feature.
PCR: 31106 Module: MLD Level: 2
PCR: 31118 Module: SWI Level: 2
PCR: 31119 Module: LOG Level: 2
PCR: 31122 Module: RMON Level: 3
PCR: 31127 Module: FIREWALL Level: 2
PCR: 31128 Module: IPG Level: 2
PCR: 31129 Module: IPX2 Level: 2
PCR: 31132 Module: DHCP Level: 2
PCR: 31133 Module: IPG

Patch 86253-07 For Rapier Series Switches DELETE IGMPSNOOPING ROUTERADDRESS 11
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
ADD IGMPSNOOPING ROUTERADDRESS
Syntax ADD IGMPSNOOPING ROUTERADDRESS=ipaddr[,...]
Description where:
•ipaddr is a reserved IP multicast address in dotted decimal notation.
This command adds reserved IP multicast addresses to the list of router
multicast addresses. The IP address specified must be within the range
224.0.0.1 to 224.0.0.255. This command is only valid if the IGMP snooping
router mode is set to IP with the SET IGMPSNOOPING ROUTERMODE
command.
SET IGMPSNOOPING ROUTERMODE
Syntax SET IGMPSNOOPING ROUTERMODE=
{ALL|DEFAULT|IP|MULTICASTROUTER|NONE}
Description This command sets the mode of operation for IGMP Snooping.
If ALL is specified, all reserved multicast addresses (i.e. 2240.0.1 to
224.0.0.255) are treated as router multicast addresses.
If DEFAULT is specified, the following addresses are treated as router
multicast addresses:
• IGMP Query: 224.0.0.1
• All routers on this subnet: 224.0.0.2
• DVMRP Routers: 224.0.0.4
• OSPFIGP all routers: 224.0.0.5
• OSPFIGP designated routers: 224.0.0.6
• RIP2 routers: 224.0.0.9
• All PIM routers: 224.0.0.13
• All CBT routers: 224.0.0.15
If IP is specified, addresses that are treated as router multicast addresses are
specified with the ADD/DELETE IGMPSNOOPING ROUTERADDRESS
command. In this mode, the switch will retain previous addresses that have
already been specified.
If MULTICAST is specified, the following addresses are treated as router
multicast addresses:
• DVMRP Routers: 224.0.0.4
• All PIM routers: 224.0.0.13
If NONE is specified, no router ports are created.
DELETE IGMPSNOOPING ROUTERADDRESS
Syntax DELETE IGMPSNOOPING ROUTERADDRESS=ipaddr[,...]
where
•ipaddr is a reserved IP multicast address in dotted decimal notation.

12 SHOW IGMPSNOOPING ROUTERADDRESS Patch Release Note
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
Description This command deletes reserved IP multicast addresses from the list of router
multicast addresses. The IP address specified must be within the range
224.0.0.1 to 224.0.0.255. This command is only valid if the IGMP snooping
router mode is set to IP with the SET IGMPSNOOPING ROUTERMODE
command.
SHOW IGMPSNOOPING ROUTERADDRESS
Syntax SHOW IGMPSNOOPING ROUTERADDRESS
Description This command displays information about the list of configured IP multicast
router addresses currently configured on the switch (Figure 1).
Figure 1: Example output for SHOW IGMPSNOOPING ROUTERADDRESS
Bridges transmitted BPDUs at the rate specified by the local helloTime value
when they were not the root bridge. This is the behaviour specified in
802.1w-2001. This behaviour can cause instability in the spanning tree when
bridges are configured with different helloTime values, especially when the
root bridge's helloTime is significantly less than other bridges in the tree. This
issue has been resolved. Non-root bridges now adopt the root bridge's
helloTime value propagated in BPDUs.
The ADD IPV6 HOST command accepted an invalid IPv6 address. This
issue has been resolved.
The firewall sent an erroneous IPSPOOF attack message when processing
large packets. This issue has been resolved.
IGMP Snooping Router Address
----------------------------------------------------------------------------
IGMP Snooping Router Mode ...... IP
Router Address List
--------------------------------
224.0.0.4
224.0.0.6
224.0.0.80
224.0.0.43
224.0.0.23
224.0.0.15
224.0.0.60
----------------------------------------------------------------------------
PCR: 31134 Module: RSTP Level: 2
PCR: 31135 Module: IPV6 Level: 3
PCR: 31140 Module: FIREWALL Level: 4

Patch 86253-07 For Rapier Series Switches SHOW IGMPSNOOPING ROUTERADDRESS 13
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
The port counters were not incremented:
• ifInDiscards
•ifinErrors
•ifOutDiscards
•ifOutErrors
This issue has been resolved.
The following SNMP MIB objects could not be set:
•Dot1dStpPriority
•Dot1dStpBridgeMaxAge
•Dot1dStpBridgeHelloTime
•Dot1dStpBridgeForwardDelay
This issue has been resolved.
DHCP was incorrectly using the directly connected network interface
source IP address as the source IP address of packets it generates. This issue
has been resolved. DHCP now uses the local IP address as the source
address for the packets it generates when a local IP interface address is set.
If a local IP interface address is not set, then it uses the IP address of the
interface where packets are sent from as the source address.
When the device rebooted with PIM or PIM6 enabled, it sometimes did not
send a Hello packet quickly enough. This issue has been resolved.
When a DHCP client was in the renewing state, and it sent a DHCP Request,
the device did not add the ARP entry to the ARP table. Instead, the device
generated an ARP Request in order to transmit the DHCP Ack. This caused
a broadcast storm in the network when the client kept sending DHCP
Requests. This issue occurred because the ciaddr field, not the giaddr field,
was checked in the Request packet when the device determined whether to
add the ARP entry. This issue has been resolved.
The current implementation of RSTP conforms to the IEEE standard
802.1w-2001. However, several minor deviations from the standard are
possible without having a functional impact on the behaviour of RSTP.
These changes are useful for debugging RSTP, and tidy up aspects of RSTP
that sometimes have no purpose. The following three variations have been
implemented:
•TheLearning and Forwarding flags are set in BPDUs to indicate the state
of the Port State Transition state machine.
•TheAgreement flag is set in BPDUs only when a Root Port is explicitly
agreeing to a proposal from a designated port. Do not set the Agreement
flag in BPDUs transmitted by Designated Ports.
PCR: 31145 Module: SWI Level: 3
PCR: 31146 Module: SWI Level: 3
PCR: 31147 Module: DHCP Level: 3
PCR: 31148 Module: PIM, PIM6 Level: 2
PCR: 31152 Module: DHCP Level: 2
PCR: 31154 Module: STP Level: 4

14 SHOW IGMPSNOOPING ROUTERADDRESS Patch Release Note
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
•TheProposal flag is not set in a BPDU sent by a designated port once the
port has reached the forwarding state.
Static ARP entries sometimes prevented the firewall from working
correctly. This is because when an VLAN interface is added to the firewall,
the CPU takes over the routing from the switch silicon in order to inspect
the packet. Hence all the Layer 3 route entries must be deleted. However,
static ARP Layer 3 entries were not being deleted from the silicon. This issue
has been resolved. When interface is added to the firewall, all hardware
layer 3 routing is now turned off to allow the firewall to inspect packets.
A STP topology change incorrectly deleted static ARP entries. This issue has
been resolved.
IP MVR member ports were not timing out. MVR member ports now
timeout in the same way as IP IGMP ports. The timeout values are
configured by IGMP. Also, IGMP interfaces were incorrectly being enabled
and disabled by MVR. This issue has been resolved.
If a device had IPSec and firewall enabled, it could not handle long ICMP
packets even when enhanced fragment handling was enabled on the
firewall. If a long packet is passed to the firewall for processing, the firewall
chains the fragmented packets. The firewall can process chained packets,
but IPSec could not process these packets, and dropped them. This was only
an issue for packets between 1723 and 1799 bytes long. This issue has been
resolved. The way IP processes fragmented packets has been changed so
that IPsec no longer drops chained packets.
On a Rapier 48, after an IP interface was added to a protected VLAN, the
switch's MAC address was registered as static in the switch forwarding
database, and had an incorrect port number. This information was shown in
the output of the SHOW SWITCH FDB command. This issue has been
resolved.
The following commands did not require security officer privilege when the
device was in security mode, but this privilege should have been required:
• ADD USER
• SET USER
• DELETE USER
•PURGEUSER
• ENABLE USER
• DISABLE USER
• RESET USER
This issue has been resolved. Security officer privilege is now required for
these commands when security mode is enabled with the ENABLE
SYSTEM SECURITY_MODE command.
PCR: 31159 Module: FW, VLAN Level: 2
PCR: 31162 Module: SWI Level: 2
PCR: 31167 Module: IPG Level: 2
PCR: 31174 Module: IPG Level: 2
PCR: 31177 Module: SWI Level: 2
PCR: 31180 Module: USER Level: 2

Patch 86253-07 For Rapier Series Switches SHOW IGMPSNOOPING ROUTERADDRESS 15
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
When static port security was enabled with the RELEARN parameter in the
SET SWITCH PORT command, and a switch port was reset or unplugged,
the MAC entries were removed (unlearned) from the forwarding database
table. The MAC entries should only be removed when dynamic port
security is in use. This issue has been resolved.
When executing the command:
ADD IP ROUTEMAP ENTRY SET ASPATH
followed by the command:
ADD IP ROUTEMAP ENTRY COMMUNITY ADD=YES
where the values for ROUTEMAP and ENTRY were the same in both
commands, the second command failed and returned a “ROUTEMAP clause
already exists” error message. This issue has been resolved.
Features in 86253-04
Patch file details are listed in Table 3:
Patch 86253-04 includes all issues resolved and enhancements released in
previous patches for Software Release 2.5.3, and the following enhancements:
MLD snooping is now supported on AT-9800 Series Switches and Rapier i
Series Switches. For details, see “MLD Snooping” on page 30.
The ability to log MAC addresses whenever the ARP cache changes has
been added. To enable this, use the command:
ENABLE IP ARP LOG
To disable it, use the command:
DISABLE IP ARP LOG
The logging of MAC addresses is disabled by default. Use the SHOW LOG
command to view the MAC addresses that have been logged when the ARP
cache changes.
The performance of IPv6 has been improved by introducing IPv6 flows.
PCR: 31190 Module: SWI, SW56 Level: 2
PCR: 31194 Module: BGP, IP Level: 3
Table 3: Patch file details for Patch 86253-04.
Base Software Release File 86s-253.rez
Patch Release Date 17-October-2003
Compressed Patch File Name 86253-03.paz
Compressed Patch File Size 585295 bytes
PCR: 02414 Module: IPV6, SWI, IPG, VLAN
PCR: 02577 Module: IPG, LOG Level: 4
PCR: 03162 Module: IPV6 Level: 3

16 SHOW IGMPSNOOPING ROUTERADDRESS Patch Release Note
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
When using MVR on a Rapier 48 or Rapier 48i, multicast packets were not
forwarded correctly between ports 1-24 and 25-48. This issue has been
resolved.
The switch filter was not operating correctly after a boot cycle. This issue
has been resolved.
OSPF disabled RIP unless RIP was activated using the SET OSPF RIP
command. This issue has been resolved.
A fatal error sometimes occurred when IPv6 multicast packets were
forwarded via an interface that went down and then came back up. This
issue has been resolved.
After about 250 days, commands such as SHOW BRIDGE COUNT were not
displaying the correct number of seconds for Uptime and Last Change At.
days. This issue has been resolved.
Three new commands have been added to enable and disable transmission
of the following ICMP messages: Network Unreachable, Host Unreachable, and
all Redirect messages.
The commands are:
DISABLE IP
ICMPREPLY[={ALL|NETUNREACH|HOSTUNREACH|REDIRECT}]
ENABLE IP
ICMPREPLY[={ALL|NETUNREACH|HOSTUNREACH|REDIRECT}]
SHOW IP ICMPREPLY
For details, see “Enable and Disable ICMP Messages” on page 28.
Interoperating with other vendors implementations of ISAKMP was
occasionally causing errors following key exchanges. This relates to
differing implementations of the RFC regarding the retention of leading
zeros. This issue has been resolved by modifying the software to retain
leading zeros. An additional command provides compatibility with routers
that still use previous software versions. The command details are:
SET ENCO DHPADDING={ON|OFF}
This command controls the padding process for Diffie Hellman generated
values. This may be required when interoperability is required with other
vendor’s equipment that uses the Diffie Hellman algorithm.
The DHPADDING parameter specifies whether the Diffie Hellman
generated values should be padded or not. If ON is specified, then leading
zeros will be inserted into the generated values. If OFF is specified, then the
generated values will not be padded. The default is ON.
PCR: 03268 Module: SWI Level: 1
PCR: 03409 Module: SWI Level: 2
PCR: 03524 Module: OSPF, IPG Level: 2
PCR: 03560 Module: IPV6 Level: 2
PCR: 03598 Module: ETH, IPG, IPv6, IPX,
PORT, PPP.
Level: 3
PCR: 03616 Module: IPG Level: 4
PCR: 03622 Module: ENCO Level: 2

Patch 86253-07 For Rapier Series Switches SHOW IGMPSNOOPING ROUTERADDRESS 17
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
For example, to turn off the Diffie Hellman padding, use the command:
SET ENCO DHPADDING=OFF
Also, the output of the SHOW ENCO command now contains a new line
showing the setting for DHPADDING.
BGP was importing the best route from IP without checking whether the
route was reachable. BGP now selects the best reachable route. If there are no
reachable routes, BGP will select the best unreachable route.
The list of multicast groups for each Rendezvous Point occasionally became
corrupted, and this could cause a fatal error. This issue has been resolved.
BGP routes that were added after a summary aggregate route had been
formed were not suppressed. This issue has been resolved: all routes added
after summary aggregate route creation are also now suppressed.
The SHOW BGP ROUTE command displayed unselected routes as the
"best" route, until they had been processed. This issue has been resolved.
When a single route was deleted from an aggregate route, the aggregate
route was deleted, even if it contained other routes. This issue has been
resolved.
The time recorded when a user logged in was overwritten when the same
user logged in a second time while the original connection was still active.
This meant the SHOW USER command displayed the same time for both
connections. This issue has been resolved.
When an oversize packet (PMTU) was received, an error message was not
returned, even when IPv6 flow was enabled. This issue has been resolved.
With static multicasting enabled on two VLANs, only the first few multicast
packets of a stream were L3 forwarded. This issue has been resolved.
The MLD snooping entries registered on a port were not removed when the
port went down or was unplugged. This issue has been resolved.
Route flapping occurred with BGP when an interface went down. This issue
has been resolved.
When ingress rate limiting was used on Rapier switch ports, TCP sessions
sometimes obtained a throughput that was lower than the configured
ingress rate limit. This issue has been resolved.
PCR: 03704 Module: BGP Level: 2
PCR: 03710 Module: PIM, PIM6 Level: 2
PCR: 03723 Module: BGP Level: 2
PCR: 03726 Module: TTY, USER Level: 3
PCR: 03733 Module: IPV6 Level: 3
PCR: 03734 Module: IPG Level: 2
PCR: 03751 Module: MLDS Level: 3
PCR: 03757 Module: BGP Level: 2
PCR: 03771 Module: SWI Level: 2

18 SHOW IGMPSNOOPING ROUTERADDRESS Patch Release Note
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
If a configuration file had a long file name, the SHOW CONFIG command
displayed the file name using the shortened DOS 8.3 format (where file
names are 8 characters long, with extensions of 3 characters). This issue has
been resolved so that long configuration file names are now displayed using
the DOS 16.3 format (where file names are up to 16 characters long).
When a 4-port ETH PIC card was installed, the output of the SHOW IP
INTERFACE command showed the ETH port as Down, but the link LEDs
on the card were lit. This issue has been resolved. The SHOW command
now shows the correct link status. The link will go down after 90 seconds if
no inbound traffic is received. When inbound traffic is received the link will
come up.
When a tagged port was deleted from a VLAN that was in the default STP,
and the port was then added to the VLAN again, communications were
sometimes not resumed on that port. This issue has been resolved.
ISAKMP did not support the IPSec message option
ID_IPV6_ADDR_SUBNET (RFC 2407, 4.6.2.7). ISAKMP was using the
ID_IPV6_ADDR (RFC 2407, 4.6.2.6) option instead. This issue has been
resolved.
MLD and MLD Snooping accepted MLD Query packets with a hop limit
greater than 1. Duplicate packets were forwarded when the hop limit was
not 1 and the payload was 0::0. This issue has been resolved. MLD and MLD
Snooping now require the hop limit to be 1.
After the SHOW VRRP command was executed, incorrect trigger messages
were entered into the log. This issue has been resolved.
An additional check has been added for unknown GBIC models to
determine if they are copper or fibre.
A fatal error occurred when IPv6 fragmented a packet. Also, when a large
fragmented ICMP echo request packet was received, the reply may not have
been fragmented and so may have exceeded the MTU for the interface it
was sent on. These issues have been resolved.
When BGP imported routes from IP with the ADD BGP IMPORT command,
and there were multiple import choices, the best IP route was not always
imported. This issue has been resolved.
PCR: 03780 Module: INSTALL Level: 3
PCR: 03789 Module: ETH Level: 2
PCR: 03790 Module: SWI Level: 2
PCR: 03798 Module: IKMP Level: 3
PCR: 03801 Module: MLDS Level: 2
PCR: 03806 Module: VRRP Level: 4
PCR: 03809 Module: SWI Level: 2
PCR: 03817 Module: IPV6 Level: 2
PCR: 03826 Module: BGP Level: 2

Patch 86253-07 For Rapier Series Switches SHOW IGMPSNOOPING ROUTERADDRESS 19
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
The MTU value for IPv6 PPP interfaces was always set to 1280 bytes. This
MTU value is now correctly set to 1500 bytes, and 1492 bytes for PPP over
Ethernet (PPPoE).
OSPF sometimes chose routes with an infinite metric over routes with a
finite metric when selecting the best local route. This issue has been
resolved.
A fatal error sometimes occurred when an IPv6 ping packet length
exceeded 1453 bytes. This issue has been resolved.
When some DHCP entries were in Reclaim mode, and all interface links
related to the range of these entries went down, these DHCP entries were
stuck in Reclaim mode. This issue has been resolved.
Entering Ctrl-N caused some terminals to expect Shift Out ASCII
characters. This issue has been resolved.
Files were not displayed in the SHOW FFILE command output, after
entering “Q” at the CLI to quit from a previous prompt. This issue has been
resolved.
PIM SM did not establish a BSR candidate between two AR720 routers with
PPP over SYN. This issue has been resolved.
When INGRESSLIMIT parameter in the SET SWITCH PORT command was
set to 64kbps, the switch received packets intermittently rather than
continuously. This issue has been resolved.
Previously, an IP multicast stream destined for an IP multicast group was
forwarded out ports in the All Groups IGMP snooping entry even after this
entry had timed out. This issue has been resolved.
When a connector was plugged into one physical interface, the RIPng
request packet was erroneously transmitted from all interfaces on the
switch. This issue has been resolved.
BGP sent Update packets when the local host route table changed but did not
affect BGP. Also, BGP did not send Withdrawn packets when there was a
change in the best route. These issues have been resolved.
PCR: 03828 Module: IPV6 Level: 2
PCR: 03836 Module: OSPF Level: 2
PCR: 03839 Module: IPV6 Level: 2
PCR: 03843 Module: DHCP Level: 2
PCR: 03847 Module: TTY Level: 3
PCR: 03850 Module: FFS Level: 3
PCR: 03852 Module: IPG, IPV6 Level: 2
PCR: 03854 Module: SWI Level: 2
PCR: 03855 Module: IPG Level: 2
PCR: 03861 Module: IPV6 Level: 2
PCR: 03864 Module: BGP Level: 2

20 SHOW IGMPSNOOPING ROUTERADDRESS Patch Release Note
Patch 86253-07 for Software Release 2.5.3
C613-10382-00 REV E
BGP sometimes chose routes with an infinite metric over routes with a finite
metric when selecting the best local route. This issue has been resolved.
The ipForwDatagrams SNMP MIB object was incremented when it should
not have been. This issue has been resolved.
On Rapier 48iswitches, mirror port information was repeated in the output
of the SHOW VLAN command. This issue has been resolved.
The HTTP proxy sometimes allowed URL requests that should have been
denied. Also, the HTTP proxy denied all URLs that contained a deniable
keyword, even when some URLs with that word had explicitly been
allowed. These issues have been resolved.
For parameters that accept a list of IP addresses in a DHCP command (such
as LOGSERVER in the ADD DHCP POLICY command), the list is now
limited to a maximum of 32 IP addresses.
Sometimes OSPF routes were not entered in the IP route table. This issue has
been resolved.
A fatal error occurred if the TRACE command was executed when a trace
was already in progress. This issue has been resolved.
The layer 3 filter was matching a layer 3 packet incorrectly when the egress
port was specified by the filter. This issue has been resolved.
Some IP addresses were not displayed correctly in log messages. This issue
has been resolved.
The IGMP MVR membership timeout was not operating correctly.
Membership of a multicast group is now eliminated when it times out. Also,
Leave messages were not being processed correctly, which sometimes
delayed the membership timeout. These issues have been resolved.
When the device was configured as a DHCP server, a fatal error sometimes
occurred when a telnet session to the device was closed while DHCP was
reclaiming IP addresses. Also, a telnet error message displayed an incorrect
value when a telnet command line parameter was repeated (for example,
SHOW TELNET TELNET). These issues have been resolved.
PCR: 03867 Module: BGP Level: 2
PCR: 03868 Module: IPG Level: 3
PCR: 03870 Module: SWI, VLAN Level: 3
PCR: 03871 Module: FIREWALL Level: 2
PCR: 03874 Module: DHCP Level: 3
PCR: 03875 Module: IPG Level: 2
PCR: 03876 Module: PING Level: 2
PCR: 03878 Module: SWI Level: 2
PCR: 03883 Module: IPG Level: 3
PCR: 03884 Module: IPG Level: 2
PCR: 03888 Module: DHCP, TELNET Level: 2