Allied Telesis 86253-07 Manuale di istruzioni

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

Indice

Altri manuali Allied Telesis Software

Allied Telesis

Allied Telesis SwitchBlade AT-AR440S Manuale utente

Allied Telesis

Allied Telesis AT-8000S Series Manuale utente

Allied Telesis

Allied Telesis SB251-08 Manuale di istruzioni

Allied Telesis

Allied Telesis AT-S82 Manuale utente

Allied Telesis

Allied Telesis 86222-10 Come usare

Allied Telesis

Allied Telesis AT-S79 Manuale utente

Allied Telesis

Allied Telesis AR44xS Manuale di istruzioni

Allied Telesis

Allied Telesis 86222-27 Manuale di istruzioni

Allied Telesis

Allied Telesis AT-8600 Series Manuale utente

Allied Telesis

Allied Telesis AT-8600 Series Manuale di istruzioni

Allied Telesis

Allied Telesis AT-S95 Manuale utente

Allied Telesis

Allied Telesis AR441S Come usare

Allied Telesis

Allied Telesis 86222-25 Manuale di istruzioni

Allied Telesis

Allied Telesis WebSmart AT-FS750/16 Come usare

Allied Telesis

Allied Telesis AT-S87 Manuale di istruzioni

Allied Telesis

Allied Telesis AR44xS Manuale di istruzioni

Allied Telesis

Allied Telesis AlliedWare Plus 5.2.1 Manuale utente

Allied Telesis

Allied Telesis 86222-21 Manuale di istruzioni

Allied Telesis

Allied Telesis SwitchBlade AT-AR440S Manuale utente

Allied Telesis

Allied Telesis AT-S95 Manuale utente

Allied Telesis

Allied Telesis AT-S39 Manuale utente

Allied Telesis

Allied Telesis AT-8000S Series Manuale utente

Allied Telesis

Allied Telesis 86251-05 Manuale di istruzioni

Allied Telesis

Allied Telesis AT-x900-12XT/S Istruzioni per il montaggio

Manuali Software popolari di altre marche

COMPRO

COMPRO COMPROFM Manuale utente

Muratec

Muratec OFFICEBRIDGE ONLINE Manuale utente

Oracle

Oracle Contact Center Anywhere 8.1 Manuale utente

Adobe

Adobe 65007312 - Photoshop Lightroom Manuale

Avaya

Avaya NULL One-X for RIM Blackberry Manuale utente

HP ProLiant BL420c Manuale utente

PS Audio

PS Audio PowerPlay Manuale del proprietario

Brady

Brady LOCKOUT PRO 3.0 Manuale di servizio

Avaya

Avaya Interaction Center Manuale utente

Texas Instruments

Texas Instruments TI-83 Plus Silver Edition Manuale

Novell

Novell GROUPWISE 8 - INTERNET AGENT Manuale utente

Oracle

Oracle Application 9i Manuale utente

Acer

Acer RDM Manuale utente

Canon

Canon Vixia HF21 Manuale utente

Canon

Canon ZR950 Manuale utente

Samsung

Samsung Auto Backup Manuale utente

Polycom

Polycom Vortex EF2201 Istruzioni per l'installazione e il funzionamento

Brocade Communications Systems

Brocade Communications Systems Brocade 8/12c Manuale utente