Allied Telesis SwitchBlade 4000 Series Release Note - Page 3

Browse online or download pdf Release Note for Network Router Allied Telesis SwitchBlade 4000 Series. Allied Telesis SwitchBlade 4000 Series 5 pages. Software maintenance release note sb273-01

Print Page

Allied Telesis SwitchBlade 4000 Series Release Note

Release sb273-01

C613-10436-00 Rev A

CR00007034

Module: Firewall

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

CR00007695

Module: PPP

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

CR00002290

Module: STP, SWI

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)

CR00002662

Module: STP

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.

CR00007341

Module: IPG

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)

CR00007358

Module: BRG, FR

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

Level: 1

Level: 2