HP PROCURVE 2520, Management And Configuration Manual

Page: 390 / 544

File Transfers
Downloading Switch Software
Troubleshooting SSH, SFTP, and SCP Operations
You can verify secure file transfer operations by checking the switch’s event
log, or by viewing the error messages sent by the switch that most SCP and
SFTP clients will print out on their console.
N o t e
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 would occur on the switch. If this happens, the switch
will gracefully exit the session and produce 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
N o t e
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
will 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):
A-16