Management and Configuration Guide K/KA/KB.15.15

NOTE: Messages that are sent by the switch to the client depend on the client software in use to
display them on the user console.
Broken SSH connection
If an ssh connection is broken at the wrong moment (for instance, the link goes away or spanning
tree brings down the link), a fatal exception occurs on the switch. If this happens, the switch
gracefully exits the session and produces an Event Log message indicating the cause of failure.
The following three examples show the error messages that may appear in the log, depending on
the type of session that is running (SSH, SCP, or SFTP):
ssh: read error Bad file number, session aborted I 01/01/90
00:06:11 00636 ssh: sftp session from ::ffff:10.0.12.35 W
01/01/90 00:06:26 00641 ssh:
sftp read error Bad file number, session aborted I 01/01/90
00:09:54 00637 ssh: scp session from ::ffff:10.0.12.35 W 01/
01/90
ssh: scp read error Bad file number, session aborted
NOTE: The Bad file number is from the system error value and may differ depending on the
cause of the failure. In the third example, the device file to read was closed as the device read
was about to occur.
Attempt to start a session during a flash write
If you attempt to start an SCP (or SFTP) session while a flash write is in progress, the switch does
not allow the SCP or SFTP session to start. Depending on the client software in use, the following
error message may appear on the client console:
Received disconnect from 10.0.12.31: 2: Flash access in
progress
lost connection
Failure to exit from a previous session
This next example shows the error message that may appear on the client console if a new SCP
(or SFTP) session is started from a client before the previous client session has been closed (the
switch requires approximately ten seconds to timeout the previous session):
Received disconnect from 10.0.12.31: 2: Wait for previous
session to complete
lost connection
Attempt to start a second session
The switch supports only one SFTP session or one SCP session at a time. If a second session is
initiated (for example, an SFTP session is running and then an SCP session is attempted), the
following error message may appear on the client console:
Received disconnect from 10.0.12.31: 2: Other SCP/SFTP
session running
lost connection
Disabling TFTP and auto-TFTP for enhanced security 297