Establishing an SSH Connection
Although a remote network administrator can manage Alteon configuration through Telnet, this method does not provide a secure connection. The SSH (Secure Shell) protocol enables you to securely log into another computer over a network to execute commands remotely. As a secure alternative to using Telnet to manage Alteon configuration, SSH ensures that all data sent over the network is encrypted and secure.
Note: Alteon can perform only one session of key/cipher generation at a time. As a result, an SSH/SCP client cannot log in if Alteon is performing key generation at that time, or if another client has just logged in before this client. Similarly, the system fails to perform the key generation if an SSH/SCP client is logging in at that time.
The Alteon implementation of SSH supports both versions 1.5 and 2.0, and supports SSH clients version 1.5 to 2.x.
The supported SSH encryption and authentication methods are:
Server Host Authentication — Client RSA-authenticates Alteon at the beginning of every connection
Key Exchange — RSA
Encryption — 3DES-CBC, DES
User Authentication — Local password authentication, RADIUS
The following SSH clients have been tested:

PuTTY 0.64

SecureCRT 7.3

MobaXterm tool (Personal Edition v6.6)

Linux OS - centOS 5.5 (openSSH_4.3p2), centos 7 (openSSH_6.6.1p1), fedora 21 (openSSH_6.7p1)
Note: There can be a maximum number of four simultaneous Telnet, SSH, SCP connections at one time.