Command reference updates, Delete ssh session, Disable ssh debug – Allied Telesis RAPIER I User Manual
Page 147: Disable ssh server

Software Version 2.8.1
147
Software Version 2.8.1
C613-10477-00 REV B
Command Reference Updates
This section describes each new command and the changed portions of
modified commands and output screens. For modified commands and output,
it shows the new parameters, options, and fields in bold.
delete ssh session
syntax
DELete SSH SEssion={session-id|ALL}
Description
This new command deletes Secure Shell and Secure Copy sessions that are
currently active on the router or switch. This can include both server and client
sessions. The deleted sessions are closed.
The session-id is the number assigned to each connection. Use a
comma-separated list to specify more than one session-id. To see a list of current
SSH sessions with their session-id numbers, use the show ssh session
command. If a session-id number is specified, that session is closed. If all is
specified, all connections are closed, except the sessions that are listening on
the TCP port for new SSH connections.
Example
To stop the current manager sessions in the following example output, use the
command:
del ssh se=2,4,5
disable ssh debug
Syntax
DISable SSH DEBug={SSH|SCP|ALL}
Description
This new command disables the SSH server debugging facility. If ssh is
specified, debugging is turned off for Secure Shell. If scp is specified,
debugging is turned off for Secure Copy. If all is specified, debugging for both
SSH and SCP is turned off. Debugging is disabled by default.
Example
To disable debugging of SCP, use the command:
dis ssh deb=scp
disable ssh server
Syntax
DISable SSH SERver
Description
This command disables the Secure Shell server. When the Secure Shell server is
disabled, connections from Secure Shell and Secure Copy clients are not
accepted.
The Secure Shell server is disabled by default. Secure Shell and Secure Copy
sessions may be initiated from the router or switch to another host, but
inbound connections are not accepted.