Amer Networks E5Web GUI - Manual (Page 46)

SSH (Secure Shell) CLI Access
The SSH (Secure Shell) protocol can be used to access the CLI over the network from a remote
host. SSH is a protocol primarily used for secure communication over insecure networks,
providing strong authentication and data integrity. SSH clients are freely available for almost all
hardware platforms.
cOS Core supports version 1, 1.5 and 2 of the SSH protocol. SSH access is regulated by the remote
management policy in cOS Core, and is disabled by default.
Example 2.3. Enabling SSH Remote Access
This example shows how to enable remote SSH access from the lan_net network through the lan
interface by adding a rule to the remote management policy.
Command-Line Interface
Device:/> add RemoteManagement RemoteMgmtSSH ssh
Network=lan_net
Interface=lan
LocalUserDatabase=AdminUsers
Web Interface
1. Go to: System > Device > Remote Management > Add > Secure Shell Management
2. Enter a Name for the SSH remote management policy, for example ssh_policy
3. Select the following:
• User Database: AdminUsers
• Interface: lan
• Network: lan_net
4. Click OK
Logging on to the CLI
When access to the CLI has been established to cOS Core through the serial console or an SSH
client, the administrator will need to logon to the system before being able to execute any CLI
command. This authentication step is needed to ensure that only trusted users can access the
system, as well as providing user information for auditing.
When accessing the CLI remotely through SSH, cOS Core will respond with a login prompt. Enter
the username and press the Enter key, followed by the password and then Enter again. After the
first startup, cOS Core will allow administrator login with the username admin and the password
admin. This default password should be changed as soon as possible.
After a successful logon, the CLI command prompt will appear:
Device:/>
If a welcome message has been set then it will be displayed directly after the logon. For security
reasons, it is advisable to either disable or anonymize the CLI welcome message.
Chapter 2: Management and Maintenance
46