![](/images/backgrounds/133660/bg13.png)
Features in 281-01 19
Version 281-02
C613-10482-00 REV B
CR00012846 ASYN, Log 2 The following issues occurred with sending log messages to an asynchronous
port:
■The log messages output on an asynchronous port were corrupt.
■When log messages were output to an asynchronous port, that port was
(correctly) locked . However, the port remaine d locked after the as ynchronous
log output definition was destroyed, and after the log output's destination
was changed from asynchronous to something else.
■It was possible for a user to change the log output destination to an
asynchronous port while the user was logged into the asynchronous port. This
resulted in the user losing access to the command line interface.
■It was possible to create a log output definition with an asynchronous port as
the destination even when another user was logged into that asynchronous
port. This resulted in the other user losing access to the command line
interface.
■If a user changed the log output destination to an asynchronous port and
specified invalid parameters in th e command, an erro r message was d isplayed
but the new output destination was saved anyway.
■The set command allowed a user to specify an asynchronous port as the
destination without specifying the asynchronous port number. The number
defaulted to asyn0, which may not have been the desired port.
These issues have been resolved.
YYYYYYYYYY
CR00012855 Core 2 If the switch was rebooted at a time when there was a high level of packet traffic
between the switch ports and the switch CPU, then during the reboot process it
was possible fo r RAM test errors to occur.
This issue has been resolved.
-------YY-
CR Module Level Description
AR400
AR7x5
AR750S / AR770S
Rapier i
AT-880 0
AT-860 0
AT-8700XL
AT-8948 / x900-48
AT-990 0
AT-980 0