Allied Telesis 4000 User Manual
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 Ta bl e 1 .
Table 1: Release file details for release sb275a05
Maintenance Release Date
Compressed Release File Name
Compressed Release File Size
GUI Resource File Name
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-00 REV 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.
7 February 2007
sb275a05.rez
3764560
d_sb8e29.rsc (8-slot chassis)
d_sb4e29.rsc (4-slot chassis)
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 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.
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-00 Rev 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
CR00010874
CR00013466
CR00013678
CR00013823
GUI 2 It was not possible to use the GUI to add untagged ports to the default
VLAN.
This issue has been resolved.
IP Gateway
OSPF
Switch 2 Previously, if a JDSU XFP was used in the AT-SB4541 10G line card, the
GUI
File System
Switch 2 In very rare circumstances, a port could stop transmitting traffic if its speed
2 Previously, the switch discarded multicast OSPF packets that it received on
unnumbered PPP interfaces. This prevented OSPF from working across
unnumbered PPP interfaces.
This issue has been resolved.
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.
2 It was not always possible to save the switch configuration by using the
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.
was modified or it was reset while under heavy traffic load.
This issue has been resolved.
CR00013862
CR00014124
Version sb275a05
C613-10464-00 Rev H
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.
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-SB4541 10G 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.
4 Features in sb275a05 Software Maintenance Release Note
CR Module Level Description
CR00015071
CR00015132
CR00015190
CR00015697
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.
Switch
GUI
Switch 2 When multicast data was being forwarded at L2 through the switch
Switch 2 Mirroring the traffic on port 1 of any line card caused the switch to lose
2 If a trunk group did not have any ports associated with it, viewing the
Trunk page in the GUI caused the switch to reboot.
This issue has been resolved.
during startup and a slave switch controller was present, the switch
sometimes rebooted.
This issue has been resolved.
packets.
Level 3
CR Module Level Description
CR00011444
CR00012858
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.
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-00 Rev H
Software Version sb275a05 5
Enhancements
CR Module Level Description
CR00013351
CR00014222
IGMP
snooping,
EPSR, RSTP
IGMP
snooping,
Switch,
VLAN
- A new feature has been added to IGMP snooping, to minimise loss of
multicast data after a topology change on networks that use EPSR or
spanning tree (STP, RSTP, or MSTP) for loop protection and IGMP
snooping.
For more information, see “IGMP Snooping Query Solicitation
(CR00013351)” on page 19.
- IGMP snooping learns which ports have routers attached to them, so it
can forward relevant IGMP messages out those ports. By default,
snooping identifies router ports by looking for ports that receive specific
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-00 Rev 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
CR00012896
CR00009026
CR00009347
CR00009826
IP Gateway 2 The switch’s hardware IP route table occasionally did not contain the most
optimal route to a destination. This meant packets were sometimes sent
via sub-optimal routes. An additional effect was that when multiple equalcost 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.
IP Gateway,
OSPF
GUI 2 It was not possible to use the GUI to add untagged ports to the default
IP Gateway 2 When a static ARP is deleted, the switch sends out an ARP request to
2 The IP route cache (and therefore the Layer 3 IP routing table in hardware)
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.
VLAN.
This issue has been resolved.
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
CR00010598
CR00010827
CR00011219
OSPF 2 Route maps did not filter static routes of external type 2 when
redistributing them into OSPF.
This issue has been resolved.
OSPF 2 When filtering OSPF routes, IP route filters did not filter out intra-area
interface routes.
This issue has been resolved.
OSPF 2 Previously, OSPF would advertise LSU packets to the wrong area when a
stub area was altered.
This issue has been resolved.
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-00 Rev H
Software Version sb275a05 7
CR Module Level Description
CR00011585
CR00012067
CR00012606
CR00012783
CR00013178
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.
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.
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.
VLAN 2 When the mirror port was specified on the switch, untagged ports would
start to transmit tagged traffic.
This issue has been resolved.
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
CR00013380
CR00013598
CR00014044
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.
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.
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.
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-00 Rev H
Loading...