Allied Telesis SB251-10 Nota de lançamento - Página 7
Procurar online ou descarregar pdf Nota de lançamento para Software Allied Telesis SB251-10. Allied Telesis SB251-10 14 páginas. Patch for switchblade 4000 series switches and at-9800 series switches
Imprimir página
Patch SB251-10 For SwitchBlade 4000 Series Switches and AT-9800 Series Switches
Patch SB251-10 for Software Release 2.5.1
C613-10361-00 REV J
Patch SB251-05 includes all issues resolved and enhancements released in
previous patches for Software Release 2.5.1, and the following enhancements:
PCR: 03281
Module: SWI
Specifying the PORT and SPEED parameters with the CREATE SWITCH
TRUNK command did not set ports in a trunk group to advertise the correct
trunk group speed and duplex mode. This issue has been resolved.
PCR: 03313
Module: SWI
A power cycle on the switch could cause the console port to become frozen
if a port was in a link up state. If a port went into a link down state, then the
console port became unfrozen. If RESTART REBOOT or RESTART
SWITCH commands were used, then the console port functioned correctly.
This issue has been resolved.
Features in SB251-04
Patch file details are listed in Table 7.
Table 7: Patch file details for Patch SB251-04.
Base Software Release File
Patch Release Date
Compressed Patch File Name
Compressed Patch File Size
Patch SB251-04 includes all issues resolved and enhancements released in
previous patches for Software Release 2.5.1, and the following enhancements:
PCR: 03226
Module: SWI
An internal misconfiguration of memory occurred when an M3 control card
and an M5 control card were installed, and the M3 control card was acting
as the Master. This could cause unexpected restarts. This issue has been
resolved.
PCR: 03228
Module: SWI
On a 48 port line card, or a 32F card, if Port 1 went down, or was
disconnected, then traffic on Port 13 was also stopped, and vice versa. The
same issue affected other pairs of ports. This issue has been resolved.
PCR: 03230
Module: SWI
Port speeds on trunk ports sometimes had to be set using the SET SWITCH
PORT command instead of automatically adopting the trunk group speed.
If a port was added to a trunk group and the port status was 'up', (that is, it
was correctly connected to another port) then the trunk group speed should
have applied to all the ports in the trunk, but it did not. Similarly, if a port
was added to a trunk group, and the port status was 'down', but it was later
linked correctly, then the trunk group speed should have applied to the
ports in the trunk. This issue has been resolved.
sb-251.rez
24 -Mar-2003
sb251-04.paz
71112 bytes
7
Level: 2
Level: 1
Level: 2
Level: 1
Level: 2