User guide

Appendix G: Troubleshooting
306
Problem
Solution
upgrade pack again.
Events Not Captured in Event Log
The eventlogfile command can fail to be captured in the SX event
log for three possible reasons:
 The log file size is set to greater than 10000000
 The log file size is set to less than 1024
 Saving the event to the event log file causes the log file size to
exceed 50% of the available flash memory on the SX. SX does not
allow this to occur.
To fix the problem, set the event log file to save at a smaller file size.
Note that each SX model has a different amount of flash memory
available. Use the log file sizes that can cause failures described here as
your guidelines when setting the event log file size.
Modem
Problem
Solution
Login Failure
The unit supports Web-browser access through the modem
at connection speeds of 28.8K bps or greater. If the baud
rate is insufficient, the user may be unable to log in to the
unit via the modem.
28.8K bps minimum connection speed is recommended for
browser-based modem authentications (login). For CLI-
based access, using SSH or Telnet, speed as low as
9600bps is adequate.
SSH Connection
Problem
Solution
SSH Access to SX from a
client running the Windows
Vista
®
operating system
failed to connect.
There may be a problem experienced by some users of Vista's
Enterprise (and Business) edition with SX where the SSH window
starts and fails to open. This is independent of the SX firmware
version and does not require an upgrade of SX firmware to
resolve.
This problem seems to stem from the Vista's implementation of