Allied Telesis 86251-08 User Manual
Patch Release Note
Patch 86251-08
For Rapier Series Switches
Introduction
This patch release note lists the issues addressed and enhancements made in
patch 86251-08 for Software Release 2.5.1 on existing models of Rapier L3
managed switches. Patch file details are listed in Table 1.
Table 1: Patch file details for Patch 86251-08.
Base Software Release File
Patch Release Date
Compressed Patch File Name
Compressed Patch File Size
This release note should be read in conjunction with the following documents:
■ Release Note: Software Release 2.5.1 for Rapier Switches (Document
Number C613-10354-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.
86s-251.rez
9-Dec-2003
86251-08.paz
545820 bytes
.
Simply connecting the world
2 Patch Release Note
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:
Level 1 This issue will cause significant interruption to network services, and
there is no work-around.
Level 2 This issue will cause interruption to network service, however there
is a work-around.
Level 3 This issue will seldom appear, and will cause minor inconvenience.
Level 4 This issue represents a cosmetic change and does not affect network
operation.
Features in 86251-08
Patch 86251-08 includes all issues resolved and enhancements released in
previous patches for Software Release 2.5.1, and the following enhancements:
PCR: 03179 Module: IPG Level: 3
The device responded when it received a directed broadcast ICMP echo
request that was in its supernet, but not its subnet. This issue has been
resolved.
PCR: 03359 Module: CORE Level: 3
An incorrect object ID (OID) was being returned for Fan/PSU in SNMP v1
trap messages.This issue has been resolved.
PCR: 03527 Module: BGP Level: 4
Session-only counters have been added to the MIB entry for BGP peers.
PCR: 03622 Module: ENCO Level: 2
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.
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.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
Patch 86251-08 For Rapier Series Switches 3
PCR: 03684 Module: CORE Level: 4
A fanAndPsRedundantFanTrap message was sent from a Rapier when the
RPS (Redundant Power Supply) was turned on or off, even though Rapiers
do not monitor the redundant fan status. This issue has been resolved.
PCR: 03726 Module: TTY, USER Level: 3
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.
PCR: 03746 Module: BGP Level: 2
Occasionally a fatal error occurred if BGP debug was disabled. Also, BGP
debug messages were sometimes still displayed after BGP debug was
disabled. These issues have been resolved.
PCR: 03781 Module: STP Level: 2
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.
PCR: 03856 Module: FIRE, UTILITY Level: 2
When a file was copied, only blocks of 1024 bytes were copied successfully.
The remainder was discarded. This had two possible consequences. Either
a truncated file was created on the destination media, or the device restarted
with a fatal error. This issue has been resolved so that files copy correctly.
PCR: 03858 Module: IP
This PCR implements RFC 1256 “ICMP Router Discovery Messages”. This
enhancement allows the device to advertise its interface IP addresses to
local hosts. For details, see “ICMP Router Discovery Advertisements” on
page 47.
PCR: 03861 Module: IPV6 Level: 2
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.
PCR: 03873 Module: IPG Level: 4
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.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
PCR: 03893 Module: FW Level: 3
Reverse enhanced NAT was not working for ICMP packets. This issue has
been resolved.
PCR: 03926 Module: PIM Level: 2
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.
4 Patch Release Note
PCR: 03935 Module: ISAKMP Level: 3
ISAKMP debug messages now correctly output IPv6 addresses when using
IPv6, and IPv4 addresses when using IPv4.
PCR: 03937 Module: IPSEC Level: 2
The IP version of packets was not being checked, so an IPv4 packet could
match an IPv6 IPSec policy. This issue has been resolved.
PCR: 03953 Module: SW56 Level: 3
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.
PCR: 03958 Module: FIREWALL Level: 2
The ADD FIREWALL POLICY RULE and SET FIREWALL POLICY RULE
commands no longer accept the GBLREMOTEIP parameter with standard
NAT, or enhanced NAT for a private interface.
PCR: 03961 Module: PIM, PIM6 Level: 2
The PIM-DM prune expiry time was not reset when a State Refresh message
was received. This issue has been resolved.
PCR: 03965 Module: IPSEC Level: 3
IPv6 used the same SA soft expiry timer at both ends of a link, which used
memory unnecessarily. This issue has been resolved.
PCR: 03967 Module: IPG Level: 2
RIP did not send the correct next hop address if the route originated from a
different subnet to that of the egress interface. This issue has been resolved.
PCR: 03970 Module: IPV6 Level: 3
If an IPv6 filter that blocked traffic on a VLAN interface was removed, the
traffic was still blocked. This issue has been resolved.
PCR: 03973 Module: IPG Level: 3
When equal cost multipath routes were used, the IP option field for trace
route was not applied correctly. This issue has been resolved.
PCR: 03978 Module: OSPF Level: 3
Occasionally an error occurred with OSPF’s route table calculation, so all
routes in the network were not discovered. The error only happened with a
network topology that involved connections between routers via both a
Point to Point link and a transit network link. This issue has been resolved.
A new command has been added that forces a route table recalculation by
rerunning the Shortest Path First calculation. The command is:
RESET OSPF SPF [DEBUG]
If DEBUG is specified, debugging information for the route table calculation
is output to the port from which the command was executed. SPF
debugging can be turned on for every route table calculation using the
ENABLE OSPF DEBUG=SPF command, but this will be overridden if
DEBUG is specified with the RESET OSPF SPF command.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
Patch 86251-08 For Rapier Series Switches 5
PCR: 03982 Module: FIREWALL Level: 3
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.
PCR: 03985 Module: SWI Level: 2
Sometimes on Rapier series switches, a severe multicast or broadcast storm
depleted packet buffers, so the switch received packets intermittently. This
issue has been resolved.
PCR: 31000 Module: IGP Level: 3
In the output of the SHOW IP IGMP COUNTER command, the outQuery
and outTotal counters were always displaying “0”. This issue has been
resolved.
PCR: 31001 Module: DHCP Level: 2
When executing the SET DHCP POLICY, DELETE DHCP POLICY and
DESTROY DHCP POLICY commands, memory was not de-allocated
correctly. This issue has been resolved.
PCR: 31002 Module: UTILITY Level: 2
Sometimes the device rebooted when a severe multicast storm occurred due
to a loop in the network. This issue has been resolved.
PCR: 31009 Module: HTTP Level: 3
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: 31013 Module: SWI Level: 2
If ports were set to a speed of 100m when creating a switch trunk, the speed
could not subsequently be set to 1000m, even if the ports were capable of
that speed. This issue has been resolved.
PCR: 31015 Module: STP Level: 2
The PORT and PORTPRIORITY parameters of the STP PORT command
were not always updating switch instances on ports that are members of
multiple STP instances. This issue has been resolved.
PCR: 31017 Module: NTP Level: 3
The RootDispersion value in NTP packets was negative. RFC 1305 states that
only positive values greater than zero are valid. This issue has been
resolved.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
PCR: 31019 Module: PIM6 Level: 2
The checksum for the PIMv2 Register message for IPv6 was not being
calculated correctly. This issue has been resolved.
PCR: 031020 Module: PIM Level: 2
When the switch received a generation ID change message, it was not
responding by sending a PIM HELLO message. This issue has been
resolved.
6 Patch Release Note
PCR: 31028 Module: BGP Level: 2
BGP did not always send Withdrawn advertisements when a route went
down. This issue has been resolved.
PCR: 31040 Module: PIM Level: 2
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.
PCR: 31041 Module: PIM Level: 3
A Prune message sent to an old RP neighbour was ignored when a new
unicast route was learned. This issue has been resolved.
PCR: 31044 Module: SWI Level: 4
The log message “
has been changed to “
activated
”. The revised message is clearer when IGMP is enabled and
IGMP Snooping is active, L3FILT is activated”
IGMP packet trapping is active, L3FILT is
IGMP snooping is disabled.
PCR: 31052 Module: FIREWALL Level: 3
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.
PCR: 31058 Module: NTP Level: 3
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.
PCR: 31063 Module: IPG Level: 2
MVR was not operating if IGMP had not been enabled. This issue has been
resolved.
PCR: 31068 Module: STP Level: 2
A fatal error occurred when the PURGE STP command was executed when
STP instances were defined with VLAN members. This issue has been
resolved.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
Patch 86251-08 For Rapier Series Switches 7
PCR: 31071 Module: SWI Level: 4
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>.
PCR: 31072 Module: SWI Level: 3
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.
PCR: 31080 Module: IPV6 Level: 2
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.
PCR: 31081 Module: VRRP, IP, TCP, TELNET,
HTTP, SNMP, SSH
This patch adds an enhancement that allows a Virtual Router IP address to
be adopted by the current master Virtual Router. This means that regardless
of whether the device actually ‘owns’ the IP address, it will respond to
specific service requests made to that IP address. The service requests are
ICMP echo (ping), Telnet, SSH, SNMP, HTTP server (GUI), and SSL for the
GUI. For details, see “Adopting the VRRP IP Address” on page 56.
PCR: 31094 Module: FILE Level: 3
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.
PCR: 31096 Module: FFS Level: 3
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.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
PCR: 31098 Module: DHCP Level: 3
Static DHCP address ranges were not reclaimed if the Reclaim operation was
interrupted by the interface going down. This issue has been resolved.
PCR: 31102 Module: DHCP Level: 2
When a boot file for DHCP was specified with the ADD DHCP POLICY
FILE command, a blank space was added after the filename in the
configuration. This meant the file could not be found. This issue has been
resolved.
8 Patch Release Note
PCR: 31106 Module: MLD Level: 2
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.
PCR: 31118 Module: SWI Level: 2
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.
PCR: 31129 Module: IPX2 Level: 2
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.
PCR: 31162 Module: SWI Level: 2
A STP topology change incorrectly deleted static ARP entries. This issue has
been resolved.
PCR: 31167 Module: IPG Level: 2
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.
Features in 86251-07
Patch file details are listed in Table 2:
Table 2: Patch file details for Patch 86251-07.
Base Software Release File
Patch Release Date
Compressed Patch File Name
Compressed Patch File Size
Patch 86251-07 includes all issues resolved and enhancements released in
previous patches for Software Release 2.5.1, and the following enhancements:
86s-251.rez
18-Sep-2003
86251-07.paz
487620 bytes
PCR: 02414 Module: IPV6, SWI, IPG, VLAN
MLD snooping is now supported on AT-9800 Series Switches and Rapier i
Series Switches. For details, see “MLD Snooping” on page 57.
PCR: 03445 Module: IPG
Support has been added for the Ping Polling enhancement. For details, see
“Ping Polling of Device Reachability” on page 58
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
Patch 86251-08 For Rapier Series Switches 9
PCR: 03524 Module: OSPF, IPG Level: 2
OSPF disabled RIP unless RIP was activated using the SET OSPF RIP
command. This issue has been resolved.
PCR: 03530 Module: IPG Level: 2
Running the PURGE IP command with a multicast address and multiple
sources was causing a fatal error. This issue has been resolved.
PCR: 03542 Module: HTTP Level: 2
The value specified for the IP parameter in the ADD FIREWALL POLICY
PROXY command was not being used by the HTTP proxy. This issue has
been resolved.
PCR: 03570 Module: ISAKMP Level: 3
Previously, there was no limit to the number of concurrent ISAKMP
Security Associations (SAs), and occasionally new SAs were created until all
free memory was exhausted. This issue has been resolved. The number of
ISAKMP SAs is now limited to the maximum number of ENCO channels.
Also, if the ISAKMP policy’s REMOTEID was set as an X.500 distinguished
name (e.g. ocn=user), a small amount of memory was consumed by each
ISAKMP exchange. This issue has been resolved.
PCR: 03598 Module: ETH, IPG, IPv6, IPX,
Level: 3
PORT, PPP.
After about 250 days, commands such as SHOW BRIDGE COUNT w ere not
displaying the correct number of seconds for Uptime and Last Change At.
days. This issue has been resolved.
PCR: 03606 Module: IPG Level: 2
BGP and UPNP were not informed when an ETH interface went up or
down. This issue has been resolved.
PCR: 03645 Module: OSPF, IPG Level: 2
Directed IPv6 PING messages were being transmitted from other interfaces
if the specified interface was down. This issue has been resolved.
PCR: 03734 Module: IPG Level: 2
With static multicasting enabled on two VLANs, only the first few multicast
packets of a stream were L3 forwarded. This issue has been resolved.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
PCR: 03751 Module: MLDS Level: 3
The MLD snooping entries registered on a port were not removed when the
port went down or was unplugged. This issue has been resolved.
PCR: 03764 Module: IPG Level: 3
The IP multicast counter did not increment when IGMP, DVMRP and PIM
packets were transmitted and received. This issue has been resolved.
10 Patch Release Note
PCR: 03778 Module: FILE, INSTALL, SCR Level: 2
Files used during start up were backed up from NVS to FLASH even if they
were already present in FLASH. This used up FLASH memory
unnecessarily. This issue has been resolved so that files are only backed up
when a copy does not already exist in FLASH.
PCR: 03780 Module: INSTALL Level: 3
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).
PCR: 03783 Module: IPG Level: 3
The TIMEOUT and SIZE parameters are only valid for the SET IP DNS
CACHE command, but no error message was returned if either parameter
was specified for the SET IP DNS command. This issue has been resolved.
PCR: 03784 Module: IPV6 Level: 3
Fragmentation of IPv6 packets now complies with RFC 2460’s requirement
to align packet sizes to 8 octets.
PCR: 03789 Module: ETH Level: 2
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.
PCR: 03796 Module: STP Level: 2
Setting RSTPTYPE to NORMAL, when normal has already been set, sets all
ports to the “sending RSTP” state process. This is referred to in IEEE 802.1w
as mCheck.
When RSTPTYPE was changed from STPCOMPATIBLE to NORMAL with
the SET STP command, the STP instance continued to send STP BPDUs
until an mCheck was performed by entering the SET STP
RSTPTYPE=NORMAL command again. This issue has been resolved so
that when RSTPTYPE is set to NORMAL an mCheck is performed, causing
the STP to start sending RSTP BPDUs immediately.
PCR: 03801 Module: MLDS Level: 2
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.
PCR: 03802 Module: FIREWALL Level: 1
Packets with bad ACK numbers were sometimes generated by the firewall
as part of the proxy TCP setup process. These packets sometimes caused
TCP sessions from the public side of the firewall to fail. This issue has been
resolved.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
Patch 86251-08 For Rapier Series Switches 11
PCR: 03809 Module: SWI Level: 2
An additional check has been added for unknown GBIC models to
determine if they are copper or fibre.
PCR: 03817 Module: IPV6 Level: 2
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.
PCR: 03823 Module: VLAN Level: 2
If the last port in a VLAN went down, that port was not automatically
deleted from IGMP groups. This issue has been resolved.
PCR: 03825 Module: IPG Level: 2
The incorrect logical interface was selected for broadcast packets received
with a subnet mask that differed from the class mask. This issue has been
resolved.
PCR: 03826 Module: BGP Level: 2
When B GP imp orted routes f rom IP w ith th e ADD BGP IM PORT co mm and,
and there were multiple import choices, the best IP route was not always
imported. This issue has been resolved.
PCR: 03828 Module: IPV6 Level: 2
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).
PCR: 03836 Module: OSPF Level: 2
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.
PCR: 03839 Module: IPV6 Level: 2
A fatal error sometimes occurred when an IPv6 ping packet length
exceeded 1453 bytes. This issue has been resolved.
PCR: 03841 Module: IPG Level: 2
A fatal error occurred when the PIM path was recovering. This issue has
been resolved.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
PCR: 03843 Module: DHCP Level: 2
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.
PCR: 03850 Module: FFS Level: 3
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.
12 Patch Release Note
PCR: 03852 Module: IPG, IPV6 Level: 2
PIM SM did not establish a BSR candidate between two AR720 routers with
PPP over SYN. This issue has been resolved.
PCR: 03854 Module: SWI Level: 2
Wh en INGR ESSLI MIT p aramet er in the SE T SWIT CH PORT command w as
set to 64kbps, the switch received packets intermittently rather than
continuously. This issue has been resolved.
PCR: 03855 Module: IPG Level: 2
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.
PCR: 03861 Module: IPV6 Level: 2
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.
PCR: 03864 Module: BGP Level: 2
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: 03865 Module: FIREWALL Level: 2
When dual firewall policies were defined, public to private passive mode
FTP transfers sometimes failed. This issue has been resolved.
PCR: 03867 Module: BGP Level: 2
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.
PCR: 03870 Module: SWI, VLAN Level: 3
On Rapier 48i switches, mirror port information was repeated in the output
of the SHOW VLAN command. This issue has been resolved.
PCR: 03875 Module: IPG Level: 2
Sometimes OSPF routes were not entered in the IP route table. This issue has
been resolved.
PCR: 03888 Module: DHCP, TELNET Level: 2
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: 03896 Module: TTY Level: 3
A fatal error occurred when a long string of text was pasted over an existing
long string of text at the CLI. This issue has been resolved.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
Patch 86251-08 For Rapier Series Switches 13
PCR: 03898 Module: ETH Level: 3
An ETH interface was sometimes shown as Up in the output of the SHOW
INTERFACE command when it was actually Down. This issue has been
resolved.
PCR: 03902 Module: FIREWALL Level: 3
Under some circumstances traffic did not have NAT applied if a standard
subnet NAT rule was added to a public interface. Such rules did not
correctly match incoming traffic when the REMOTEIP parameter in the
ADD FIREWALL POLICY RULE command was not specified, and the
destination IP address was not the interface’s actual IP address. If this
situation occurred, traffic was redirected back out the public interface. This
issue has been resolved.
PCR: 03906 Module: SWITCH Level: 2
Software emulation of layer 3 hardware filtering was not operating
correctly. Packets that the switch had no routing information for were
filtered incorrectly. The first packet of a fl ow tha t shou ld ha ve be en dropped
was not dropped, and a flow that should have been allowed was being
dropped. This issue has been resolved.
PCR: 03921 Module: IP ARP Level: 3
ARP requests with invalid source MAC and IP addresses were being
processed, but should have been dropped. This issue has been resolved.
PCR: 03922 Module: PIM Level: 3
The SET PIM INTERFACE command did not succeed when the
HELLOTIMER parameter was specified. This issue has been resolved.
PCR: 03925 Module: IPV6 Level: 3
Incorrect debug information was returned when an ICMPv6 PacketTooBig
message was received. This issue has been resolved.
PCR: 03928 Module: IKMP Level: 2
ISAKMP in aggressive mode did not establish a connection when the peer
client sent 10 or more payloads. This issue has been resolved.
PCR: 03931 Module: IPSEC Level: 3
The IPSec configuration was not created correctly when the RADDRESS
and LNAME parameters in the CREATE IPSEC POLICY command were
used together. This issue has been resolved.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
PCR: 03934 Module: IPSEC Level: 2
The CREATE IPSEC POLICY command failed if the interface specified with
the INTERFACE parameter did not have a global IPv6 interface defined.
This PCR implements a workaround by using the interface’s link-local IPv6
address if no other IPv6 address can be found.
PCR: 03936 Module: IKMP Level: 3
When ISAKMP was used with IPv6, an incorrect IP address was displayed
in the output of the SHOW ISAKMP EXCHANGE command. This issue has
been resolved.
14 Patch Release Note
PCR: 03938 Module: IKMP Level: 3
DHEXPONENTLENGTH parameter in the CREATE ISAKMP POLICY
command was not accepted when creating ISAKMP policies that used IPv6.
This issue has been resolved.
PCR: 03939 Module: IPV6 Level: 2
When a NeighbourAdvert message containing an anycast target address was
received, the device incorrectly performed Duplicate Address Detection.
This issue has been resolved.
PCR: 03946 Module: IPSEC Level: 3
When IPSec was used with IPv6, an incorrect IP address was displayed in
the output of the SHOW IPSEC SA command. This issue has been resolved.
PCR: 03949 Module: IPSEC Level: 3
If a local IP address and remote IP address were not specified in the
CREATE IPSEC POLICY command for IPv6 IPSec, the SET IPSEC POLICY
configuration was shown unnecessarily in the output of the SHOW
CONFIG DYNAMIC=IPSEC command. This issue has been resolved.
PCR: 03952 Module: SWI Level: 3
MAC address are now deleted from the all the internal tables for ports
where the learn limit has been exceeded.
Features in 86251-06
Patch file details are listed in Table 3:
Table 3: Patch file details for Patch 86251-06.
Base Software Release File
Patch Release Date
Compressed Patch File Name
Compressed Patch File Size
Patch 86251-06 includes all issues resolved and enhancements released in
previous patches for Software Release 2.5.1, and the following enhancements:
86s-251.rez
30-July-2003
86251-06.paz
895445 bytes
PCR: 02216 Module: FIREWALL Network affecting: No
Support has been added to the Firewall module for RTSP, MMS, BROBA,
and MPEG2.
PCR: 02510 Module: SWI Level: 4
Support has been added for enabling flow control on half duplex links. The
ENABLE SWITCH PORT command configures the switch chip to send a
jamming signal over a half duplex link in response to congestion. The
following commands configure flow control:
DISABLE SWITCH PORT={port-list|ALL}
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
Patch 86251-08 For Rapier Series Switches 15
DISABLE SWITCH PORT=port-list FLOW=PAUSE
DISABLE SWITCH PORT=ALL FLOW={JAMMING|PAUSE}[,...]
ENABLE SWITCH PORT={port-list|ALL}
ENABLE SWITCH PORT=port-list FLOW=PAUSE
ENABLE SWITCH PORT=ALL FLOW={JAMMING|PAUSE}[,...]
SHOW SWITCH PORT[={port-list|ALL}]
PCR: 03011 Module: OSPF Network affecting: No
When the router priority was changed on a dynamic OSPF interface, the
new priority did not appear in the output of the SHOW OSPF NEIGHBOUR
command on neighbouring routers. The new priority only showed after the
RESET OSPF command was executed on the neighbouring routers. This
issue has been resolved.
PCR: 03070 Module: BGP Level: 2
When BGP imported other route types, it would advertise routes that had
nexthops of the BGP peers themselves. The BGP peers would reject these
routes and close the peering session, thus preventing the exchange of
routing information between BGP peers. This issue has been resolved.
PCR: 03072 Module: BGP Level: 4
The Import parameter of the ADD, SET, DELETE and SHOW BGP
commands now has an INTERFACE type. INTERFACE routes were
previously grouped with STATIC routes.
PCR: 03178 Module: IPSEC Level: 4
An unnecessary check has been removed from the CREATE ISAKMP
POLICY AUTHTYPE=RSASIG command.
PCR: 03264 Module: FIREWALL Level: 4
The event logs for the firewall did not show the correct detail for
DOSFLOOD, HOSTSCAN, SYNATTACK and HOSTSCAN. This issue has
been resolved.
PCR: 03287 Module: Firewall Level: 2
When the firewall was set to ACTION=NAT, it was allowing inbound
traffic, (for example FTP) even though a port was specified for a particular
application, (for example Telnet). This issue has been resolved.
PCR: 03310 Module: SWI Level: 3
When the VLAN mirror port was configured as a tagged port, the port did
not transmit tagged packets. This issue has been resolved.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
PCR: 03315 Module: L2TP Level: 2
The L2TP Framing Type attribute-value pair (19) for virtual tunnels was set
to 0 which caused an interoperability problem with a Linux L2TP
implementation. This issue has been resolved. The Framing Type attributevalue pair is now set to 1 (synchronous) for virtual tunnels.
16 Patch Release Note
PCR: 03355 Module: IPV6 Level: 2
IPv6 tunnelling over IPv4 failed if an IPv4 interface was not configured,
even though an IPv4 interface is not needed for IPv6 tunnelling. This issue
has been resolved.
PCR: 03374 Module: IPV6 Level: 1
Multilink Listener Discovery (MLD) packets received on the switch caused
fatal errors. This issue has been resolved.
PCR: 03425 Module: PRI Level: 3
On the AT-AR020 PRI E1/T1 Port Interface Card (PIC), E bits were not
transmitted in response to received CRC-4 errors. Also, after a period of
Alarm Indication Signal (AIS) reception, Remote Alarm Indication (RAI)
transmission was not terminated. These issues have been resolved.
PCR: 03437 Module: IPV6 Level: 2
RIPng received RIP routes from neighbours even when RIPng was disabled.
This issue has been resolved.
PCR: 03447 Module: PPP Level: 2
A remotely assigned IP address on a PPP interface was not always released
when the connection timed out. This issue has been resolved.
PCR: 03490 Module: IPSEC Level: 2
IPSec used with IPv4 sometimes caused a fatal error. This issue has been
resolved.
PCR: 03499 Module: IPG Level: 2
The SET TIME command caused an error on Refresh timers for IGMP
groups. This issue has been resolved.
PCR: 03511 Module: IPG Level: 3
The special group entry 01-00-5e-00-00-02 was being written to the layer 2
forwarding database to identify router ports for IGMP snooping. Router
ports are now identified from software, so this special group entry is no
longer written to the layer 2 forwarding database.
PCR: 03514 Module: IPSEC Level: 2
An incorrect IPSec Security Association (SA) was used to transmit packets
when the SA’s IP address was assigned dynamically on another VPN
gateway. This issue has been resolved.
PCR: 03515 Module: DHCP Level: 3
DHCP was offering network and broadcast addresses to clients. This issue
has been resolved.
PCR: 03522 Module: IKMP Level: 3
ISAKMP suffered an error when it encountered unknown cryptographic
algorithms. This issue has been resolved.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
Patch 86251-08 For Rapier Series Switches 17
PCR: 03524 Module: OSPF, IPG Level: 2
OSPF disabled RIP unless RIP was activated using the SET OSPF RIP
command. This issue has been resolved.
PCR: 03532 Module: FIREWALL Level: 3
Occasionally the TCP connection was terminated early during an IDENT
proxy TCP session. This issue has been resolved.
PCR: 03536 Module: BGP, TCP Level: 3
Outgoing BGP packets did not have the Internet Work control flags set in
the IP TOS bits. This issue has been resolved.
PCR: 03537 Module: BGP Level: 3
BGP was returning incorrect and/or incomplete bgp4AttrPath MIB entry
information. This issue has been resolved.
PCR: 03538 Module: BGP Level: 2
Configuration information was not exported to BGP peers when BGP was
disabled and then re-enabled. This issue has been resolved.
PCR: 03543 Module: IPG Level: 2
When acting as a DNS relay agent, the device restarted after approximately
three hours of heavy load. This issue has been resolved.
PCR: 03544 Module: HTTP, FIREWALL Level: 3
HTTP proxy was not denying an IP address if its corresponding domain
name was specified in a filter, or if a domain name was requested and its
corresponding IP address was in the filter. This issue has been resolved.
PCR: 03546 Module: FIREWALL Level: 2
In a dual policy configuration (a LAN policy and a DMZ policy with
common WAN interface) where both policies have enhanced NAT,
behaviour changed according to which policy was configured first. Traffic
received on the WAN interface, where a matching rule existed in the DMZ
policy to NAT the traffic through to the DMZ, was not permitted if the DMZ
policy was configured first. A deny event was recorded in the LAN policy.
The traffic was permitted if the LAN policy was configured first. Also, with
the same rule configured when traffic was sent from the LAN interface to
the WAN interface, IP traffic through to the DMZ policy did not have NAT
applied correctly when the DMZ policy was configured first. An inwards
deny event was recorded in the LAN policy. If the LAN policy was
configured first this did not occur. Both of these issues have been resolved.
In these situations, behaviour is now independent of the order of
configuration.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
PCR: 03547 Module: DHCP Level: 3
The range of values for the IPMTU parameter in the ADD DHCP POLICY
command was set incorrectly in PCR 03465. The correct range is 576-65535,
not 579-65535. This issue has been resolved.
18 Patch Release Note
PCR: 03551 Module: IPV6 Level: 2
The command ADD IPV6 6TO4 IP did not allow more than one tunnel. This
issue has been resolved. This command can now be used repeatedly to
create multiple tunnels.
PCR: 03554 Module: FIREWALL Level: 3
When a dynamic public firewall interface was UP it was not possible to
delete any (non-dynamic) public interface rules. Also, under the same
circumstances it was possible to create duplicates of public interface rules
(with the same rule ID number). These issues have been resolved.
PCR: 03555 Module: HTTP Level: 3
The RESET HTTP SERVER command was resetting the dynamic
configuration settings back to the default values. This command now resets
the HTTP server counters, and restarts the HTTP server using the dynamic
configuration settings.
PCR: 03558 Module: PIM, PIM6 Level: 2
Periodic PIM (*,*,RP) Join messages did not cease after a set Rendezvous
Point timed out. This issue has been resolved.
PCR: 03560 Module: IPV6 Level: 2
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.
PCR: 03562 Module: IPV6 Level: 3
Disabling and then enabling IPv6 made the CREATE IPV6
INTERFACE=VLAN command appear twice in the configuration script.
This issue has been resolved.
PCR: 03564 Module: IPV6 Level: 2
A fatal error sometimes occurred when an IPv6 flow used a virtual
interface, and the flow was displayed using the SHOW IPV6 FLOW
command. This issue has been resolved.
PCR: 03565 Module: BGP Level: 2
A fatal error occurred after executing the SET BGP PEER command when a
BGP session was established with more than 15 communities defined. This
issue has been resolved.
PCR: 03566 Module: OSPF Level: 2
An area border router did not send summary LSA messages via a PPP link
when the area changed. This issue has been resolved.
PCR: 03568 Module: IPV6 Level: 3
IPv6 filters were not handling ICMPv6 packets correctly. This issue has been
resolved.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
Patch 86251-08 For Rapier Series Switches 19
PCR: 03569 Module: FIREWALL Level: 3
A problem existed in a configuration with a single policy involving one
private interface and two On Demand PPP public interfaces with NAT
acting on traffic from the private to each of the public interfaces. Traffic
generated on the device (e.g. pings) that was routed out one of the public
interfaces sometimes caused both PPP interfaces to activate. This occurred
if the NAT relating to the correct PPP was configured first. This behaviour
was partially fixed in PCR 02250. This issue has been resolved so that only
one PPP interface is activated and NAT is used correctly.
PCR: 03571 Module: IPG Level: 3
The Proxy Arp default setting should be OFF for VLAN interfaces. This
issue has been resolved.
PCR: 03572 Module: STP Level: 4
The dot1dStpPortForwardTransitions value in the dot1dBridge MIB was not
correctly incremented when STP transitioned a port to the forwarding state.
This issue has been resolved.
PCR: 03573 Module: IPG Level: 2
It is now possible to configure an IP filter with the default route of 0.0.0.0.
This allows BGP to control the default route for route distribution.
PCR: 03574 Module: STP Level: 4
The dot1dStpInfoTopChanges value in the dot1dBridge MIB was not correctly
incremented when a topology change was detected by the bridge. This issue
has been resolved.
PCR: 03576 Module: IPG Level: 2
When the device received a route from two separate sources to the same
destination network, RIP only used the metric value when selecting the best
route. RIP now selects the route by lowest preference value, or if they are the
same, by the metric.
PCR: 03582 Module: FIREWALL, IPG Level: 4
Previously, when the ADD FIREWALL POLICY INTERFACE command
activated software routing, the static IP ARP entries were removed
automatically. Static IP ARP entries now remain and the following message
is displayed:
WARNING: Static ARPs associated with a particular VLAN are
recommended to be deleted when Firewall is enabled on the VLAN.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
PCR: 03584 Module: MLD Level: 3
MLD had no mechanism for dealing with an IPv6 interface changing its
local link address. This issue has been resolved.
PCR: 03594 Module: PING Level: 2
IPv6 ping or traceroute sometimes caused the device to restart. This issue
has been resolved.
20 Patch Release Note
PCR: 03609 Module: OSPF Level: 1
The IP route filter did not always work correctly for OSPF. This issue has
been resolved.
PCR: 03615 Module: LOAD Level: 3
Zmodem uploads to some terminal emulators did not succeed because the
16-bit checksum was incorrect. This issue has been resolved.
PCR: 03616 Module: IPG Level: 4
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 60.
PCR: 03618 Module: DHCP Level: 3
The SHOW DHCP CLIENT command output showed a ClientId value even
when the State for the client entry was Unused. This issue has been resolved.
PCR: 03619 Module: IPv6 Level: 4
When the SET IPv6 FILTER command specified a filter that did not exist, an
Operation successful message was displayed as well as an error
message. This issue has been resolved.
PCR: 03620 Module: IPV6 Level: 3
The 16-bit reserved field after the maximum response code field was not set
to zero, as specified by the Internet Draft “Multicast Listener Discovery
Version 2 (MLDv2) for IPv6”. This issue has been resolved.
PCR: 03623 Module: SWI Level: 3
If both the EPORT and IPORT parameters were specified with the ADD
SWITCH L3FILTER ENTRY command, a value of 63 or 64 for the EPORT
parameter was not accepted. This issue has been resolved.
PCR: 03624 Module: IPV6 Level: 3
The ADD IPV6 FILTER and SET IPV6 FILTER commands accepted a
SESSION parameter when the PROTOCOL parameter was not TCP. The
SESSION parameter specifies the type of TCP packet to match. This issue
has been resolved.
PCR: 03625 Module: STP, SWI Level: 4
The MIB object dot1dStpTimeSinceTopologyChange has been implemented to
record when a topology change is detected by the bridge.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
Patch 86251-08 For Rapier Series Switches 21
PCR: 03631 Module: SWI Level: 4
When a Finisar 8521 GBIC was used in an AT-A42/GBIC uplink module the
link LED did not correctly show the link status. This issue has been
resolved.
PCR: 03635 Module: IPV6 Level: 1
IPv6 was selecting routes on interfaces that were down. This issue has been
resolved.
PCR: 03637 Module: IPV6 Level: 1
IPv6 static tunnels remained in the Tentative state and did not change to the
Preferred state. This issue has been resolved.
PCR: 03640 Module: STP Level: 2
A fatal error sometimes occurred when the ENABLE STP PORT command
was executed. This issue has been resolved.
PCR: 03646 Module: IPv6 Level: 1
A fatal error occurred when the SHOW IPV6 MLD INTERFACE command
was executed after the interface had been destroyed. This issue has been
resolved.
PCR: 03647 Module: SNMP Level: 2
A fatal error occurred when a Set request with an incorrect object ID value
was received by SNMPv2c. This issue has been resolved.
PCR: 03650 Module: IPG Level: 3
IGMP Query messages were sent over an interface even if IGMP had been
disabled on that interface. This issue has been resolved.
PCR: 03652 Module: SWI Level: 2
Packet forwarding between switch chips on Rapier 48 switches sometimes
failed if ingress rate limiting was set below 1 Mb/s. This was caused by
packets receiving a bad hop count between switch chips via the CPU,
causing packets to be discarded. This issue has been resolved.
PCR: 03657 Module: SWI Level: 3
Executing the DISABLE SWITCH PORT command on a port that was the
source of a mirror port did not disable the mirror port. This issue has been
resolved.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
PCR: 03662 Module: IPG Level: 1
Equal Cost Multi-Path (ECMP) routing selected a route with an infinite
metric, so that forwarded packets using that route were discarded. This
issue has been resolved.
PCR: 03666 Module: BGP Level: 3
BGP advertised interface routes when the corresponding interface was
down. This issue has been resolved.
22 Patch Release Note
PCR: 03669 Module: FIREWALL Level: 3
If the firewall received a packet with an incorrect TCP checksum and ACK
number, the packet was sent to the client. Such packets are now rejected by
the firewall. This patch fixes the problem.
PCR: 03678 Module: IPG Level: 3
Packet throughput was reduced if an incoming packet did not match the
first entry of the IP filter table. This issue has been resolved.
PCR: 03679 Module: IPG Level: 3
When IP filters were deleted, the corresponding IP flow cache was not
invalidated. This issue has been resolved.
PCR: 03689 Module: PKI Level: 1
A fatal error occurred when a device received a PKI certificate that exceeded
the CERTSTORELIMIT parameter in the SET PKI command. This
parameter sets the maximum number of certificates that can be stored on
the device. This issue has been resolved.
PCR: 03691 Module: DVMRP Level: 2
A fatal error occurred if the number of DVMRP interfaces being added
exceeded the limit. This issue has been resolved.
PCR: 03692 Module: BGP Level: 2
Occasionally a fatal exception may have occurred when sending BGP
aggregate routes. This issue has been resolved.
PCR: 03696 Module: IPG Level: 2
IGMP snooping entries were not being deleted from the hardware table.
This issue has been resolved. Also, port timers are now updated when the
IGMP timeout is changed.
PCR: 03698 Module: DVMRP Level: 3
The output of the SHOW DVMRP FORWARDING command did not
display the forwarding ports. This issue has been resolved.
PCR: 03707 Module: STP Level: 2
When adding a port to a VLAN, any STP ports that had been disabled in the
default STP were re-enabled. This issue has been resolved.
PCR: 03708 Module: DHCP Level: 2
When the DELETE DHCP RANGE command was executed, DHCP
attempted to reclaim the addresses in that range. It also tried to reclaim
addresses in that range that were not allocated at that time, resulting in
duplicate addresses appearing on the free list for allocation. This has been
resolved by allowing DHCP to reclaim only those addresses that are
currently in use by one of its clients.
PCR: 03710 Module: PIM, PIM6 Level: 2
The list of multicast groups for each Rendezvous Point occasionally became
corrupted, and this could cause a fatal error. This issue has been resolved.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
Patch 86251-08 For Rapier Series Switches 23
PCR: 03720 Module: STP Level: 2
When changing from RSTP to STP mode, the STPCOMPATIBLE option for
the RSTPTYPE parameter incorrectly appeared in the dynamic
configuration. Also, when changing from RSTP to STP mode or vice versa,
disabled STP ports did not remain in the disabled state. These issues have
been resolved.
PCR: 03722 Module: PPP, VJC Level: 3
Previously, VJC supported 136 interfaces and PPPoE supported 256 PPP
interfaces, but the device software supported up to 512 PPP interfaces. This
discrepancy sometimes caused a fatal error and prevented PPPoE interfaces
with a PPP index greater than 255 from working correctly. This issue has
been resolved, so that VJC and PPPoE now fully support 512 PPP interfaces.
PCR: 03723 Module: BGP Level: 2
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.
PCR: 03728 Module: IPG Level: 4
A field has been added to the SHOW IP command output that displays
whether the IP ARP log is enabled or disabled.
PCR: 03733 Module: IPV6 Level: 3
When an oversize packet (PMTU) was received, an error message was not
returned, even when IPv6 flow was enabled. This issue has been resolved.
PCR: 03738 Module: IPG Level: 2
If a port went down, the port was deleted from the appropriate static IGMP
associations but was not added back again when it came back up. Similarly,
static IGMP associations were automatically deleted but not added back
when IP or IGMP was disabled. These issues have been resolved. You can
now create IGMP associations before enabling IGMP, and they will become
active when IGMP is enabled.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
PCR: 03741 Module: FIREWALL Level: 3
The maximum number of firewall sessions had decreased since software
release 86s-241. This issue has been resolved.
PCR: 03743 Module: IP Level: 3
If a ping was active and the IP configuration was reset, subsequent pings
were sent out the wrong interface. This issue has been resolved.
PCR: 03744 Module: PING Level: 3
Executing a ping to the IP address 0.0.0.0 did not return an
destination address
error message. Also, when the TRACE command
invalid
was executed for local addresses, it timed out after 90 seconds. These issues
have been resolved.
24 Patch Release Note
PCR: 03747 Module: VRRP Level: 3
An unkown interface log message was returned for VRRP if there was an
interface UP or interface DOWN event due to a mismatch between a
monitored interface index and the corresponding interface instance. This
issue has been resolved.
PCR: 03750 Module: IPv6 Level: 3
IPv6 loopback address was used as a source address in ping packets,
causing ping to fail. This issue has been resolved.
PCR: 03756 Module: IPV6 Level: 2
The following issues have been resolved:
• IPv4 addresses x.x.x.0 or x.x.x.255 were not accepted for the IP
parameter in the ADD IPV6 6TO4 command.
• IPv4 addresses x.x.x.0 or x.x.x.255 were not accepted for the LOCAL
parameter in the ADD IPV6 TUNNEL command.
• IPv6 addresses 2002:x:x::/48 were not accepted for the IPADDRESS
parameter in the ADD IPV6 INTERFACE command.
PCR: 03766 Module: FIREWALL Level: 2
The firewall denied streaming data using Windows Media Player 9. This
issue has been resolved.
PCR: 03771 Module: SWI Level: 2
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: 03790 Module: SWI Level: 2
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.
PCR: 03793 Module: RSVP Level: 3
The ENABLE RSVP INTERFACE command did not succeed if IP was
enabled after the RSVP interface had been created. Now, ENABLE RSVP
INTERFACE will succeed regardless of when IP is enabled as long as an IP
interface exists.
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
Loading...