- Allied Telesis, Inc SwitchBlade Software Maintenance Release Note

Release sb273-01 3
Release sb273-01
C613-10436-00 Rev A
A reboot could occur while ageing out Firewall sessions when the device
was under heavy load and had many active Firewall sessions.
This issue has been resolved. (No PCR number.)
When either the Firewall was enabled or multiple L2TP tunnels were
configured, and a default route existed over an L2TP tunnel, it was possible
for an infinite internal packet loop to be created when a packet was sent
over the L2TP tunnel after the underlying interface route to the remote IP
had gone down. This caused a reboot to occur.
This issue has been resolved. (No PCR number.)
Level 2
Previously, the forwarding database was flushed instead of being aged out
when an STP topology change notification was received.
This issue has been resolved. (PCR number: 40185)
Previously, when a port or ports was moved from one VLAN to another, the
switch would reset both STP/RSTP instances that control the VLANs. This
behaviour is now changed to only reset the STP process on the STP instance
that the port(s) is joining. The switch will now also retain the port(s) edge-
port setting during the moving process.
This issue has been resolved.
When routers and switches were using CIDR addressing, with a unicast
address coinciding with a network broadcast address of class A, B, or C,
then they could incorrectly forward traffic as directed broadcasts, even
though the traffic was unicast (only).
This issue has been resolved. (PCR number: 50069)
When Cisco encapsulation was used on a frame relay interface, the router
was not recognising bridged packets. This issue has been resolved.
Also, specifying a logical frame relay interface when adding a bridge port
has been explicitly disallowed. (No PCR number.)
CR00007034 Module: Firewall Level: 1
CR00007695 Module: PPP Level: 1
CR00002290 Module: STP, SWI Level: 2
CR00002662 Module: STP Level: 2
CR00007341 Module: IPG Level: 2
CR00007358 Module: BRG, FR Level: 2