Allied Telesis 4000 Series User Manual

Size:
222.03 Kb
Download

Software Maintenance Release Note

Software Version sb275a05

For SwitchBlade 4000 Series Switches

Introduction

This software maintenance release note lists the issues addressed and enhancements made in maintenance version sb275a05 for Software Release 2.7.5A on existing models of SwitchBlade series switches. Release file details are listed in Table 1.

Table 1: Release file details for release sb275a05

Maintenance Release Date

7 February 2007

 

 

Compressed Release File Name

sb275a05.rez

 

 

Compressed Release File Size

3764560

 

 

GUI Resource File Name

d_sb8e29.rsc (8-slotchassis)

 

d_sb4e29.rsc (4-slotchassis)

 

 

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

the documentation you received with Software Release 2.7.5A

the SwitchBlade Document Set for Software Release 2.7.3 (Document Number C613-03100-00REV A), available from:www.alliedtelesis.co.nz/documentation/documentation.html

Caution: Using a software maintenance version for the wrong model 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 Telesis Inc. While every effort has been made to ensure that the information contained within this document and the features and changes described are accurate, Allied Telesis Inc. can not accept any type of liability for errors in, or omissions arising from the use of this information.

2

Enabling and installing this Release

Software Maintenance Release Note

Some of the issues addressed in this Maintenance 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 nowork-around.

Level 2 This issue will cause interruption to network service, however there is awork-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.

Enabling and installing this Release

To use this maintenance release you must have a base release license for Software Release 2.7.5A. Contact your distributor or reseller for more information.

To enable this release and install it as the preferred release, use the commands:

enable rel=sb275a05.rez num=2.7.5

set install=pref rel=sb275a05.rez

Version sb275a05

C613-10464-00Rev H

Software Version sb275a05

3

Features in sb275a05

Software maintenance version sb275a05 includes all resolved issues and enhancements in earlier 2.7.5A versions, and the resolved issues and enhancements in the following tables.

Level 1

No level one issues

Level 2

CR

Module

Level

Description

 

 

 

 

CR00009347

GUI

2

It was not possible to use the GUI to add untagged ports to the default

 

 

 

VLAN.

 

 

 

This issue has been resolved.

 

 

 

 

CR00010874

IP Gateway

2

Previously, the switch discarded multicast OSPF packets that it received on

 

OSPF

 

unnumbered PPP interfaces. This prevented OSPF from working across

 

 

 

unnumbered PPP interfaces.

 

 

 

This issue has been resolved.

 

 

 

 

CR00013466

Switch

2

Previously, if a JDSU XFP was used in the AT-SB454110G line card, the

 

 

 

switch rebooted when executing the command show switch port.

 

 

 

This issue has been resolved.

 

 

 

Also, the XFP LED on the 10G line card used to flash amber when many

 

 

 

types of XFPs were installed without a link.

 

 

 

This issue has also been resolved. When an XFP is installed, enabled, and

 

 

 

without a link, the XFP LED is now solid green.

 

 

 

 

CR00013678

GUI

2

It was not always possible to save the switch configuration by using the

 

File System

 

Save button on the GUI. Sometimes the GUI reported the following error

 

 

 

instead of saving the configuration:

 

 

 

"Save failed: SYSR busy, try create config file when transfer complete"

 

 

 

This issue has been resolved.

 

 

 

 

CR00013823

Switch

2

In very rare circumstances, a port could stop transmitting traffic if its speed

 

 

 

was modified or it was reset while under heavy traffic load.

 

 

 

This issue has been resolved.

 

 

 

 

CR00013862

IP Gateway

2

If a network loop lasted for a day or longer, the switch ran out of memory

 

 

 

and rebooted.

 

 

 

This issue has been resolved. The switch now conserves memory in these

 

 

 

extreme circumstances.

 

 

 

 

CR00014124

Switch

2

When the master switch controller was in slot B and a slave controller was

 

 

 

in slot A, the Layer 2 multicast table for AT-SB454110G line cards could

 

 

 

become incorrect. This caused loss of connectivity.

 

 

 

This issue has been resolved. The Layer 2 multicast table now reflects the

 

 

 

correct configuration when the master controller is in slot A or slot B.

 

 

 

 

Version sb275a05

C613-10464-00Rev H

4

Features in sb275a05

 

Software Maintenance Release Note

 

 

 

 

 

 

CR

Module

Level

Description

 

 

 

 

 

 

CR00015071

IP Gateway

2

Routing over a PPP interface could fail if the switch had a default route out

 

 

 

 

an Ethernet port. The default route switched all packets, even those

 

 

 

 

destined for the PPP interface.

 

 

 

 

This issue has been resolved. The resolution involves adding routes over

 

 

 

 

the PPP interface to the switch hardware tables with an instruction to trap

 

 

 

 

these packets to the CPU. Therefore these routes now appear in the

 

 

 

 

hardware tables, and can be displayed by using the command show

 

 

 

 

switch table=ip.

 

 

 

 

 

 

CR00015132

Switch

2

If a trunk group did not have any ports associated with it, viewing the

 

 

GUI

 

Trunk page in the GUI caused the switch to reboot.

 

 

 

 

This issue has been resolved.

 

 

 

 

 

 

CR00015190

Switch

2

When multicast data was being forwarded at L2 through the switch

 

 

 

 

during startup and a slave switch controller was present, the switch

 

 

 

 

sometimes rebooted.

 

 

 

 

This issue has been resolved.

 

 

 

 

 

 

CR00015697

Switch

2

Mirroring the traffic on port 1 of any line card caused the switch to lose

 

 

 

 

packets.

 

 

 

 

 

Level 3

CR

Module

Level

Description

 

 

 

 

CR00011444

Asyn

3

If information was sent to a console (asyn) port that had no cable plugged

 

 

 

into it, excessive CPU usage occurred.

 

 

 

This issue has been resolved.

 

 

 

 

CR00012858

DHCP

3

Previously, it was not possible to have multiple static DHCP entries with the

 

 

 

same client ID (MAC address), even if the static entries were for different

 

 

 

DHCP ranges.

 

 

 

This issue has been resolved. You can now add static DHCP entries for a

 

 

 

given MAC address to multiple ranges. Note that you cannot have

 

 

 

multiple entries for a given MAC address on the same range.

 

 

 

 

Level 4

No level four issues

Version sb275a05

C613-10464-00Rev H

Software Version sb275a05

5

Enhancements

CR

Module

Level

Description

 

 

 

 

CR00013351

IGMP

-

A new feature has been added to IGMP snooping, to minimise loss of

 

snooping,

 

multicast data after a topology change on networks that use EPSR or

 

EPSR, RSTP

 

spanning tree (STP, RSTP, or MSTP) for loop protection and IGMP

 

 

 

snooping.

 

 

 

For more information, see “IGMP Snooping Query Solicitation

 

 

 

(CR00013351)” on page 19.

 

 

 

 

CR00014222

IGMP

-

IGMP snooping learns which ports have routers attached to them, so it

 

snooping,

 

can forward relevant IGMP messages out those ports. By default,

 

Switch,

 

snooping identifies router ports by looking for ports that receive specific

 

VLAN

 

multicast packets (such as IGMP queries, PIM messages, OSPF messages,

 

 

and RIP messages).

 

 

 

 

 

 

In some network configurations, this learning process cannot identify all

 

 

 

router ports. For such networks, this enhancement enables you to

 

 

 

statically configure particular ports as multicast router ports.

 

 

 

To specify the static router ports, use the new command:

 

 

 

add igmpsnooping vlan={vlan-name|1..4094}routerport=port-list

 

 

 

To stop ports from being static router ports, use the new command:

 

 

 

delete igmpsnooping vlan={vlan-name|1..4094}routerport=port-list

 

 

 

To list the static router ports, use the existing command:

 

 

 

show igmpsnooping

 

 

 

and check the new “Static Router Ports” field.

 

 

 

 

Version sb275a05

C613-10464-00Rev H

6 Features in sb275a04 Software Maintenance Release Note

Features in sb275a04

Software maintenance version sb275a04 includes all resolved issues and enhancements in earlier 2.7.5A versions, and the resolved issues and enhancements in the following tables.

Level 1

No level one issues

Level 2

CR

Module

Level

Description

 

 

 

 

CR00007522

IP Gateway

2

The switch’s hardware IP route table occasionally did not contain the most

CR00012896

 

 

optimal route to a destination. This meant packets were sometimes sent

 

 

via sub-optimalroutes. An additional effect was that when multiple equal-

 

 

 

cost routes existed a less than complete set of those routes would be

 

 

 

utilised.

 

 

 

This issue has been resolved, so that the switch forwards packets via the

 

 

 

best IP route(s) available.

 

 

 

 

CR00009026

IP Gateway,

2

The IP route cache (and therefore the Layer 3 IP routing table in hardware)

 

OSPF

 

was sometimes refreshed unnecessarily when OSPF SPF recalculation took

 

 

 

place as a result of OSPF receiving a router LSA update.

 

 

 

This issue has been resolved.

 

 

 

 

CR00009347

GUI

2

It was not possible to use the GUI to add untagged ports to the default

 

 

 

VLAN.

 

 

 

This issue has been resolved.

 

 

 

 

CR00009826

IP Gateway

2

When a static ARP is deleted, the switch sends out an ARP request to

 

 

 

attempt to create a dynamic ARP for that IP address. Previously, the switch

 

 

 

did not process the ARP response correctly and therefore did not add the

 

 

 

ARP to its ARP table.

 

 

 

This issue has been resolved. When a static ARP is deleted, the switch

 

 

 

attempts to create a dynamic ARP for that IP address, and will successfully

 

 

 

add it to the ARP table if a device responds.

 

 

 

 

CR00010170

OSPF

2

Route maps did not filter static routes of external type 2 when

 

 

 

redistributing them into OSPF.

 

 

 

This issue has been resolved.

 

 

 

 

CR00010598

OSPF

2

When filtering OSPF routes, IP route filters did not filter out intra-area

 

 

 

interface routes.

 

 

 

This issue has been resolved.

 

 

 

 

CR00010827

OSPF

2

Previously, OSPF would advertise LSU packets to the wrong area when a

 

 

 

stub area was altered.

 

 

 

This issue has been resolved.

 

 

 

 

CR00011219

IPv4

2

When the switch received an IP packet with invalid IP option length (a

 

 

 

corrupted packet), a reboot might occur.

 

 

 

This issue has been resolved.

 

 

 

 

Version sb275a05

C613-10464-00Rev H

Software Version sb275a05

 

7

 

 

 

 

CR

Module

Level

Description

 

 

 

 

CR00011585

OSPF

2

Adding the same OSPF stub or host twice caused OSPF to suspend its

 

 

 

operation, causing neighbour relationships to eventually fail.

 

 

 

This issue has been resolved.

 

 

 

 

CR00012067

OSPF

2

A summary LSA was not turned into a route if the destination and mask

 

 

 

fell inside one of the switch’s active ranges, unless it exactly matched the

 

 

 

active range’s address and mask.

 

 

 

This complied with RFC 1583 section 16.2. However, the recommended

 

 

 

behaviour has been modified in RFC 2328 section 16.2. To comply with

 

 

 

this, the LSA is now calculated if it falls inside one of the switch’s active

 

 

 

ranges.

 

 

 

 

CR00012606

STP

2

Processing of an invalid STP packet could result in an STP timeout value

 

 

 

being incorrectly set to 0.

 

 

 

This issue has been resolved, so the timeout can never be set to 0.

 

 

 

 

CR00012783

VLAN

2

When the mirror port was specified on the switch, untagged ports would

 

 

 

start to transmit tagged traffic.

 

 

 

This issue has been resolved.

 

 

 

 

CR00013178

Switch

2

In packet storm conditions, involving a high percentage of routing

 

 

 

protocol packets, the switch could become very low on resources, and

 

 

 

reboot.

 

 

 

This issue has been resolved.

 

 

 

 

CR00013275

Firewall

2

If a firewall policy had a list attached to it (by using the command add

 

 

 

firewall policy=policy-name list=list-name),destroying the policy

 

 

 

would cause the switch to reboot.

 

 

 

This issue has been resolved.

 

 

 

 

CR00013380

IP Gateway

2

In certain unusual network configurations, the switch would respond to

 

 

 

ICMP messages addressed to it with the wrong source IP address in the

 

 

 

reply.

 

 

 

This issue has been resolved.

 

 

 

 

CR00013598

IP Gateway

2

If the switch had multiple default routes with the same nexthop (such as

 

 

 

one static default route and a default route learnt by RIP) and one of those

 

 

 

default routes was withdrawn, then the hardware entry for the default

 

 

 

route would be removed. This meant that traffic destined to that route

 

 

 

was forwarded to the CPU, which could result in a performance

 

 

 

degradation.

 

 

 

This issue has been resolved.

 

 

 

 

CR00014044

IGMP

2

When large numbers of multicast streams were passing through the

 

 

 

switch and there was no multicast routing protocol running (such as PIM

 

 

 

or DVMRP), the CPU would experience regular periods of extended high

 

 

 

utilisation. This could result in lost control packets and network instability.

 

 

 

This issue has been resolved.

 

 

 

 

Version sb275a05

C613-10464-00Rev H

8

Features in sb275a04

Software Maintenance Release Note

Level 3

CR

Module

Level

Description

 

 

 

 

CR00000133

Log

3

Messages in the permanent log were lost after changing the queue length

CR00008167

 

 

for the permanent log.

 

 

This issue has been resolved.

 

 

 

 

 

 

 

CR00002589

IPX

3

Previously, an IPX circuit sometimes incorrectly displayed its link status as

CR00011829

 

 

UP, when it was actually in a DOWN state.

 

 

This issue has been resolved.

 

 

 

 

 

 

 

CR00009817

Ping

3

The command purge ping totally did not purge all the information

 

 

 

about ping polling.

 

 

 

This issue has been resolved.

 

 

 

 

CR00010183

OSPF

3

If a route had already been learnt by OSPF, and then the inroutemap on

 

 

 

OSPF was configured in such a way that the properties of this route should

 

 

 

be altered as it is imported into the IP route table, the route would not be

 

 

 

altered even if the SPF calculation was repeated.

 

 

 

This issue has been resolved.

 

 

 

 

CR00010184

OSPF

3

If route map filtering altered the type of a AS-Externalroute, the metric

 

 

 

format was not also appropriately altered.

 

 

 

This issue has been resolved, so that the metric format will also be altered

 

 

 

to be appropriate for the route type.

 

 

 

 

CR00011652

GUI

3

It was not possible to use the GUI to edit a file (through the Management

 

 

 

> Configuration Files > Edit page) if the filename contained a hyphen

 

 

 

(such as test-1.cfg).The browser returned a “page not found” error.

 

 

 

This issue has been resolved. You can now edit such files.

 

 

 

 

CR00012130

IP Gateway

3

The command set ip route preference=value protocol=protocol did

 

 

 

not correctly update the preference of all routes learned by the specified

 

 

 

protocol.

 

 

 

This issue has been resolved.

 

 

 

 

CR00012427

Logging

3

If a user modified the permanent log by destroying it and creating a new

CR00002887

 

 

one, and then saved the configuration with the command create config,

 

 

the resulting configuration file included the command destroy log

 

 

 

output=permanent. Therefore when the switch restarted it destroyed

 

 

 

the log and all entries.

 

 

 

This issue has been resolved. The command create config now writes the

 

 

 

command set log output=permanent to the configuration file instead

 

 

 

of the destroy andcreate commands.

 

 

 

 

CR00012947

Log

3

When a user entered the command show log receive=ipadd

 

 

 

mask=mask, the switch displayed an error message that saidmask was

 

 

 

not a valid parameter.

 

 

 

This issue has been resolved. The mask parameter is now valid for this

 

 

 

command.

 

 

 

 

Version sb275a05

C613-10464-00Rev H

Software Version sb275a05

 

9

 

 

 

 

CR

Module

Level

Description

 

 

 

 

CR00013048

Firewall

3

When IP NAT or firewall NAT was used, the switch sometimes generated

 

 

 

ICMP messages that specified the wrong source IP address. This meant

 

 

 

that the response to traceroute could be incorrect.

 

 

 

This issue has been resolved.

 

 

 

 

CR00014021

Switch

3

In certain circumstances, if the switch was configured with IP filters and

 

 

 

STP, then some traffic would be incorrectly blocked.

 

 

 

This issue has been resolved.

 

 

 

 

Level 4

CR

Module

Level

Description

 

 

 

 

CR00002394

IP Gateway

4

RIP would try to send route update packets when the lower link layer was

 

 

 

down.

 

 

 

This issue has been resolved, so that RIP no longer tries to send packets

 

 

 

when the lower link layer is down.

 

 

 

 

CR00008006

OSPF

4

Previously, the maximum metric value for OSPF route redistribution was

 

 

 

16777215. This has been changed to 16777214.

 

 

 

 

CR00010399

IP Gateway

4

Previously, the ? help for some IP commands showed duplicate options.

 

 

 

This issue has been resolved.

 

 

 

 

CR00010540

TTY

4

Sometimes, output from the CLI ? help is long enough for the page

 

 

 

scrolling mechanism to take effect. This produces the prompt:

 

 

 

--More--(<space> = next page, <CR> = one line, C = continuous, Q = quit)

 

 

 

Previously, if a user entered q in response to this prompt, the command

 

 

 

was lost instead of regenerated.

 

 

 

Also, commands terminated with the ? or Tab characters were added to

 

 

 

the command history with the ? or Tab character present, which is not

 

 

 

desirable behaviour.

 

 

 

These issues have been resolved.

 

 

 

 

CR00010584

OSPF

4

The “operation successful” message was not produced after the

 

 

 

command reset ospf spf was successfully carried out.

 

 

 

This issue has been resolved.

 

 

 

 

CR00011743

Core, GUI

4

The GUI sometimes displayed a value above 100% for the peak utilisation

 

 

 

of a port.

 

 

 

This issue has been resolved.

 

 

 

 

CR00012192

Core, Utility

4

If the ? is entered at the end of an incomplete command (to obtain help),

 

 

 

but the partially-enteredcommand contains an error, then an error

 

 

 

message is displayed.

 

 

 

Previously, the incomplete command was not then re-presentedto the

 

 

 

user for editing.

 

 

 

This issue has been resolved, so that the incomplete command is now

 

 

 

presented to the user again after the error message.

 

 

 

 

Version sb275a05

C613-10464-00Rev H

10

Features in sb275a04

 

Software Maintenance Release Note

 

 

 

 

 

 

CR

Module

Level

Description

 

 

 

 

CR00012774

IP Gateway,

4

In an unusual network configuration where the IP subnet on one interface

 

 

TCP

 

was a subset of that on another interface, it was possible for the results

 

 

 

 

of a trace route to show erroneous information.

 

 

 

 

This issue has been resolved. A search for an interface using an address

 

 

 

 

within the interface's subnet now finds the most specific match for the

 

 

 

 

address.

 

 

 

 

CR00012946

Log

4

When a user entered the command show log receive=ipadd,

 

 

 

 

information about all IP addresses was displayed unless the user also

 

 

 

 

entered the mask parameter.

 

 

 

 

This issue has been resolved. Specifying an IP address without a mask now

 

 

 

 

limits the display to information about that IP address.

 

 

 

 

CR00013332

Core

4

When insufficient arguments were entered in the command set

 

 

 

 

interface, an error message was not produced.

 

 

 

 

This issue has been resolved, so that an error message is now correctly

 

 

 

 

output.

 

 

 

 

CR00013334

TCP

4

The delete tcp command did not output a success message after

 

 

 

 

successfully completing.

 

 

 

 

The enable tcp debug command produced messages with the wrong

 

 

 

 

module ID.

 

 

 

 

These issues have been resolved.

 

 

 

 

CR00013336

Core, NVS, TCP,

4

If parameters were incorrectly entered twice in some set orshow

 

 

TTY

 

commands, the resulting error message was corrupted and included

 

 

 

 

meaningless characters.

 

 

 

 

This issue has been resolved.

 

 

 

 

CR00013442

Switch

4

When the user attempted to enable CPU Tx health checking on an

 

 

 

 

instance in the SwitchBlade controller (by using the command enable

 

 

 

 

switch healthcheck=cputx), the switch correctly rejected this command.

 

 

 

 

However, the output of the show config dynamicor create config

 

 

 

 

commands included this rejected command.

 

 

 

 

This issue has been resolved.

 

 

 

 

 

Version sb275a05

C613-10464-00Rev H