Allied Telesis SB251-13 Instruction Manual

Simply connecting the world

Patch Release Note

Patch SB251-13

For SwitchBlade 4000 Series Switches and

AT-9800 Series Switches

Introduction

This patch release note lists the issues addressed and enhancements made in

patch SB251-13 for Software Release 2.5.1 on existing models of SwitchBlade

4000 Series Switches and AT-9800 Series Switches. Patch file details are listed in

Table 1.

This release note should be read in conjunction with the following documents:

■SwitchBlade Documentation Set for Software Release 2.5.1 (Document

Number C613-03057-00 Rev A).

■AT-9800 Series Switches Documentation Set for Software Release 2.5.1

(Document Number C613-03056-00 Rev A)

■Release Note for Software Release 2.5.1 for SwitchBlade 4000 Switches and

AT-9800 Series Switches (Document Number C613-10354-00 Rev D)

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 SB251-13.

Base Software Release File sb-251.rez

Patch Release Date 08-Oct-03

Compressed Patch File Name sb251-13.paz

Compressed Patch File Size 525044

2Patch Release Note

Patch SB251-13 for Software Release 2.5.1

C613-10361-00 REV M

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 SB251-13

Patch SB251-13 includes all issues resolved and enhancements released in

previous patches for Software Release 2.5.1, and the following

enhancements:

MLD snooping is now supported on AT-9800 Series Switches. It is not

available on the SwitchBlade. Refer to the section, Multicast Listener

Discovery (MLD) Snooping For SwitchBlade and AT-9800 Series Switches shown

at the end of the SB251-13 features.

Sometimes IP flows were not deleted correctly when both directions of the

flow were in use. This issue has been resolved.

OSPF was disabling RIP unless RIP was activated using the SET OSPF RIP

command. This issue has been resolved.

Running the PURGE IP command with a multicast address and multiple

sources was causing a fatal error. This issue has been resolved.

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.

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.

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: 02414 Module: IPV6, SWI, IPG, VLAN Level: 2

PCR: 03040 Module: IPG Level: 3

PCR: 03524 Module: OSPF, IPG Level: 2

PCR: 03530 Module: IPG Level: 2

PCR: 03542 Module: HTTP Level: 3

PCR: 03598 Module: ETH, IPG, IPv6, IPX,

PORT, PPP.

Level: 3

Patch SB251-13 For SwitchBlade 4000 Series Switches and AT-9800 Series Switches 3

Patch SB251-13 for Software Release 2.5.1

C613-10361-00 REV M

Ports on the SwitchBlade and AT-9800 are now initialised to advertise

pausing as disabled.

BGP and UPNP were not informed when an ETH interface went up or

down. This issue has been resolved.

The IP route filter did not always work correctly for OSPF. This issue has

been resolved.

HTTP proxy did not discard cookies nor allow/deny access to URLs when

a second pass on the URL was performed. This issue has been resolved.

In a network with a large number of L1 intermediate systems (L1-ISs) a fatal

error occurred after approximately 10 minutes. This issue has been

resolved.

Directed IPv6 PING messages were being transmitted from other interfaces

if the specified interface was down. This issue has been resolved.

When CAM segments were full, the CAM entries were not being moved

correctly, and occasionally corrupting on compaction. This issue has been

resolved.

The SHOW SYS SYSR SLAVE command did not return a list of valid

features. This issue has been resolved.

Entering the SHOW IPX CACHE command on the SwitchBlade or AT-9800

Series switches, was displaying a message stating that IPX route caching is

not supported.

This PCR, when introduced in Patch 12, resulted in the Master and Slave

controller cards restarting whenever the bootscript contained more than

2000 VLANs. This issue has been resolved.

The VLAN table was corrupting during a hot swap if a protocol or subnet

VLAN had previously been created.

PCR: 03603 Module: SWCX, SWI. Level: 3

PCR: 03606 Module: IPG Level: 2

PCR: 03609 Module: OSPF, IPG Level: 1

PCR: 03617 Module: FIREWALL Level: 2

PCR: 03643 Module: CLNS/OSI Level: 3

PCR: 03645 Module: OSPF, IPG Level: 2

PCR: 03663 Module: SWCX Level: 2

PCR: 03668 Module: SYSR Level: 2

PCR: 03686 Module: IPX Level: 3

PCR: 03688 Module: SYSR Level: 3

PCR: 03714 Module: VLAN Level: 2

4Patch Release Note

Patch SB251-13 for Software Release 2.5.1

C613-10361-00 REV M

The SET VLAN BCLIMIT command did not work when executed from

start-up in a configuration script. This issue has been resolved.

New static routes cannot be added to the forwarding database until ARP

has resolved the routes' next hop MAC address. In the meantime, selecting

the best alternative route was sometimes causing incorrect forwarding and

loops. To avoid this situation, packets destined for dead-end routes are now

forced to the CPU. The CPU then creates an ICMP_Redirect message to the

source of the unforwardable packet to remove the previous hop from its

routing table.

In order to force packets back to the CPU, the hardware MAC table contains

a special entry for each VLAN that maps the unused MAC address

55.55.55.55.55.55.55.55 to the Multicast Group ID 4096. When the switch

encounters an unknown next hop MAC address, it now sends the packet to

the L2MC Group 4096. Because this group does not exist, the packet is

forwarded to the CPU. Note that this process will increment the SHOW

SWITCH COUNTER command’s L2MCGroupSoesntExist counter.

When a user logged on twice, thus creating two sessions, the user log on

time for the second session was overwriting the value recorded for the first.

This issue has been resolved by displaying the log on times as two separate

sessions.

Previous STP ports were not being deleted correctly when line cards were

hot swapped. Also STP ports were not initialising correctly when STP was

not enabled. These issues have 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 copying of switch routes between internal components was causing

processing delays. This issue has been resolved.

Although the SwitchBlade hardware is capable of forwarding jumbo

frames, sending these to the CPU was causing a variety of issues. These

issues have been resolved.

Attempts to disable BGP debug were, depending on configuration,

resulting in either a system failure, or the debug messages continuing to

appear after debug had been disabled. This issue has been resolved.

PCR: 03524 Module: OSPF, IPG Level: 2

PCR: 03717 Module: IP, SWCX Level: 2

PCR: 03726 Module: TTY, USER Level: 3

PCR: 03727 Module: SWI, STP Level: 2

PCR: 03734 Module: IPG Level: 2

PCR: 03736 Module: IPG Level: 3

PCR: 03739 Module: SWI Level: 2

PCR: 03746 Module: BGP Level: 3

Patch SB251-13 For SwitchBlade 4000 Series Switches and AT-9800 Series Switches 5

Patch SB251-13 for Software Release 2.5.1

C613-10361-00 REV M

An unknown 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.

The MLD snooping entries registered on a port were not removed when the

port went down or was unplugged. This issue has been resolved.

The IP multicast counter did not increment when IGMP, DVMRP and PIM

packets were transmitted and received. This issue has been resolved.

An error occurred in the GUI if it had been in operation for more than 20

days. This issue has been resolved.

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.

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).

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.

Fragmentation of IPv6 packets now complies with RFC 2460’s requirement

to align packet sizes to 8 octets.

Disabled copper ports on AT-SB4411 8-Port (RJ-45) Gigabit Ethernet Line

Cards and AT-SB4441 8-GBIC Line Cards were not disabled on reboot. This

issue has been resolved.

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.

PCR: 03747 Module: VRRP Level: 3

PCR: 03751 Module: MLDS Level: 3

PCR: 03764 Module: IPG Level: 3

PCR: 03769 Module: SWI Level: 2

PCR: 03778 Module: FILE, INSTALL, SCR Level: 2

PCR: 03780 Module: INSTALL Level: 3

PCR: 03783 Module: IPG Level: 3

PCR: 03784 Module: IPV6 Level: 3

PCR: 03791 Module: SWCX Level: 2

PCR: 03793 Module: RSVP Level: 3

6Patch Release Note

Patch SB251-13 for Software Release 2.5.1

C613-10361-00 REV M

Browsing the dot1dTpFdbPort table with SNMPv2c sometimes gave

incorrect output. This issue has been resolved.

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.

If a DNS lookup failed when using the UPLOAD command to load a file

with a host name, the file was sometimes deleted from FLASH. 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.

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.

After the SHOW VRRP command was executed, incorrect trigger messages

were entered into the log. This issue has been resolved.

A fatal error sometimes occurred when using hardware filters if DMA

debug was enabled. This issue has been resolved.

Rate limiting sometimes prevented IGMP snooping and MLD snooping

from operating correctly. This issue has been resolved.

A fatal error occasionally occurred because of an error with internal

processing of the control blades. This issue has been resolved.

The SHOW SWITCH HOTSWAP command output displayed more than 4

blades on a 4 blade chassis. This issue has been resolved.

PCR: 03795 Module: SWI Level: 3

PCR: 03796 Module: STP Level: 2

PCR: 03800 Module: LOAD Level: 2

PCR: 03801 Module: MLDS Level: 2

PCR: 03802 Module: FIREWALL Level: 1

PCR: 03806 Module: VRRP Level: 4

PCR: 03811 Module: UTILITY Level: 2

PCR: 03813 Module: SWI Level: 2

PCR: 03814 Module: SWI Level: 1

PCR: 03815 Module: SWI Level: 3

Patch SB251-13 For SwitchBlade 4000 Series Switches and AT-9800 Series Switches 7

Patch SB251-13 for Software Release 2.5.1

C613-10361-00 REV M

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.

Previously, Multicast Storm Protection limited broadcast packets when

Broadcast Storm Protection was not enabled. This has been changed so that

only multicast packets are limited when Multicast Storm Protection is

enabled, and only broadcast packets are limited when Broadcast Storm

Protection is enabled.

If a 10MB half-duplex link was connected to a port, the maximum

bandwidth shown in the SHOW SWITCH TABLE command output was not

updated. This issue has been resolved.

If the last port in a VLAN went down, that port was not automatically

deleted from IGMP groups. This issue has been resolved.

A multihomed interface sometimes sent duplicate multicast packets. This

issue has been resolved.

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.

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.

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).

The value of the ifInErrors counter in the SHOW INTERFACE=interface

command incorrectly showed the number of packets received with bytes in

the normal range. This issue has been resolved. The ifInErrors counter now

correctly shows the number of packets received that had errors.

PCR: 03817 Module: IPV6 Level: 2

PCR: 03819 Module: SWCX Level: 3

PCR: 03821 Module: SWCX Level: 3

PCR: 03823 Module: VLAN Level: 2

PCR: 03824 Module: IPG Level: 3

PCR: 03825 Module: IPG Level: 2

PCR: 03826 Module: BGP Level: 2

PCR: 03828 Module: IPV6 Level: 2

PCR: 03829 Module: SWCX Level: 3

8Patch Release Note

Patch SB251-13 for Software Release 2.5.1

C613-10361-00 REV M

Hardware filters using classifiers that specified IP addresses were not

accepted by the ADD SWITCH HWFILTER command when added in a

particular order. This issue has been resolved.

If either the MCLIMIT or BCLIMIT parameter in the SET VLAN MCLIMIT

BCLIMIT command was set to NONE, the other parameter was sometimes

incorrectly set to NONE as well. This issue has been resolved.

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.

When browsing the ifInNUcastPkt MIB counter, the value was not correctly

incremented because only broadcast packets were counted. This issue has

been resolved.

A fatal error sometimes occurred when an IPv6 ping packet length

exceeded 1453 bytes. This issue has been resolved.

A fatal error occurred when the PIM path was recovering. This issue has

been resolved.

MLD startup query packets were not being sent correctly due to IPv6 MLD

being unaware of the IPv6 interfaces it was running on. 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.

An STP blocking port did not discard SNAP encapsulated packets with

TYPE=00BB (ESRP packets). This caused a loop in the network. This issue

has been resolved.

The GUI install file was not copied to the slave controller card after

executing the SET INSTALL=GUI command. This issue has been resolved.

PCR: 03834 Module: SWCX Level: 2

PCR: 03835 Module: VLAN Level: 3

PCR: 03836 Module: OSPF Level: 2

PCR: 03837 Module: VLAN Level: 3

PCR: 03839 Module: IPV6 Level: 2

PCR: 03841 Module: IPG Level: 2

PCR: 03842 Module: IPG Level: 3

PCR: 03843 Module: DHCP Level: 2

PCR: 03846 Module: SWCX Level: 2

PCR: 03849 Module: SYSR Level: 2

PCR: 03850 Module: FFS Level: 3

Patch SB251-13 For SwitchBlade 4000 Series Switches and AT-9800 Series Switches 9

Patch SB251-13 for Software Release 2.5.1

C613-10361-00 REV M

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.

Multicast packets were not forwarded between switch instances on

SwitchBlade series switches. 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 GBIC port had its speed and duplex configured as part of a

configuration script, the settings were not applied to the hardware. This

issue has been resolved.

The speed on copper GBIC ports can no longer be manually set.

When linking up a single interface.

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.

When dual firewall policies were defined, public to private passive mode

FTP transfers sometimes failed. This issue has been resolved.

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.

CompactFlash™ cards formatted to FAT16 by Windows XP were not

recognised correctly. This was because Windows XP reserved a number of

sectors. This issue has been resolved.

PCR: 03853 Module: SWCX Level: 2

PCR: 03855 Module: IPG Level: 2

PCR: 03857 Module: SWCX Level: 1

PCR: 03859 Module: SWI Level: 2

PCR: 03861 Module: SWI Level: 2

PCR: 03861 Module: IPV6 Level: 2

PCR: 03864 Module: BGP Level: 2

PCR: 03865 Module: FIREWALL Level: 2

PCR: 03867 Module: BGP Level: 2

PCR: 03869 Module: CFLASH Level: 3

10 Patch Release Note

Patch SB251-13 for Software Release 2.5.1

C613-10361-00 REV M

When typing “?” at the command line after SET SWITCH PORT,

INGRESSLIMIT was incorrectly displayed as a valid option. This issue has

been resolved.

A memory leak was occurring with DHCP. This issue has been resolved.

Uplugging the remote receive port on the 32FX card (AT-SB4352) was

causing the switch to lock-up. This issue has been resolved.

When the speed and duplex settings of a port were configured with the SET

SWITCH PORT SPEED command, the port sometimes erroneously

advertised auto-negotiation capabilities, usually when ports were

configured with a startup script. This issue has been resolved so that switch

ports will not advertise any capabilities when configured with fixed speed

and duplex settings.

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.

Packets were not routed when an IPv6 flow was enabled. This issue has

been resolved.

The switch was adding a router port for multicast packets to destinations

with an address in the range 224.0.0.x. Switch port entries are now only

created for special router multicast addresses.

When the configurable temperature threshold had not been set, its value

should show as “Undefined” in the output of the SHOW SYSTEM

command, but it showed the same value as the fixed temperature threshold.

This issue has been resolved.

A fatal error sometimes occurred during persistent hotswapping of line

cards if the cards were inserted or removed before waiting for a message

like the following examples to appear:

Info (1034266): Board AT-SB4411 8-1000T(RJ45) hot-inserted

Info (1034268): Board AT-SB4411 8-1000T(RJ45) hot-swapped out

This issue has been resolved.

PCR: 03872 Module: SWI Level: 3

PCR: 03879 Module: DHCP Level: 2

PCR: 03880 Module: SWICX, SWI Level: 2

PCR: 03887 Module: SWCX Level: 2

PCR: 03888 Module: DHCP, TELNET Level: 2

PCR: 03889 Module: IPV6 Level: 2

PCR: 03890 Module: IGMP, SWI Level: 2

PCR: 03891 Module: CORE Level: 3

PCR: 03899 Module: CORE Level: 2

Table of contents

Other Allied Telesis Software manuals

Allied Telesis

Allied Telesis AT-9400 User manual

Allied Telesis

Allied Telesis AT-GS950/8 User manual

Allied Telesis

Allied Telesis AT-8000S Series User manual

Allied Telesis

Allied Telesis SNMP Rel. 2.0.0 User manual

Allied Telesis

Allied Telesis 86222-25 Instruction Manual

Allied Telesis

Allied Telesis AT-8600 Series User manual

Allied Telesis

Allied Telesis AR4155 Instruction Manual

Allied Telesis

Allied Telesis 86241-06 Instruction Manual

Allied Telesis

Allied Telesis AT-S82 User manual

Allied Telesis

Allied Telesis AlliedWare Plus 5.2.1 User manual

Allied Telesis

Allied Telesis AT-S63 Specification sheet

Allied Telesis

Allied Telesis 86253-07 Instruction Manual

Allied Telesis

Allied Telesis SwitchBlade AT-AR440S User manual

Allied Telesis

Allied Telesis AT-8600 Series Instruction Manual

Allied Telesis

Allied Telesis WebSmart AT-FS750/16 How to use

Allied Telesis

Allied Telesis 86222-27 Instruction Manual

Allied Telesis

Allied Telesis AT-8000S Series User manual

Allied Telesis

Allied Telesis Broadcom Advanced Control Suite 3 User manual

Allied Telesis

Allied Telesis SwitchBlade AT-AR440S User manual

Allied Telesis

Allied Telesis AR44xS Instruction Manual

Allied Telesis

Allied Telesis 86241-02 Instruction Manual

Allied Telesis

Allied Telesis AT-S87 Instruction Manual

Allied Telesis

Allied Telesis 86222-21 Instruction Manual

Allied Telesis

Allied Telesis 86241-01 Instruction Manual

Popular Software manuals by other brands

COMPRO

COMPRO COMPROFM manual

Muratec

Muratec OFFICEBRIDGE ONLINE user guide

Oracle

Oracle Contact Center Anywhere 8.1 installation guide

Adobe

Adobe 65007312 - Photoshop Lightroom Programmer's guide

Avaya

Avaya NULL One-X for RIM Blackberry user guide

HP ProLiant BL420c user guide

PS Audio

PS Audio PowerPlay Programming manual

Brady

Brady LOCKOUT PRO 3.0 Administrator's guide

Avaya

Avaya Interaction Center user guide

Texas Instruments

Texas Instruments TI-83 Plus Silver Edition Guide book

Novell

Novell GROUPWISE 8 - INTERNET AGENT manual

Oracle

Oracle Application 9i Configuration guide

Acer

Acer RDM user guide

Canon

Canon Vixia HF21 instruction manual

Canon

Canon ZR950 instruction manual

Samsung

Samsung Auto Backup user manual

Polycom

Polycom Vortex EF2201 Application note

Brocade Communications Systems

Brocade Communications Systems Brocade 8/12c user manual