Admin Guide

Table Of Contents
SSH public key encryption clients have to connect to the VSP server with the same access
level, such as rwa then the clients must connect to the server one-by-one as the VSP only
supports one public key per access level.
Encryption. The SSHv2 server uses encryption algorithms to scramble data and render it
unintelligible except to the receiver.
Supported encryption and ciphers are: 3DES, AES128-cbc, AES192-cbc, AES256-cbc,
AES128–ctr, AES192-ctr, AES256-ctr, rijndael128-cbc, rijndael 192-cbc, aeadAes-128Gcm,
aeadAes-256Gcm, blowfish-cbc, secure hash algorithm 1 (SHA-1) and SHA-2.
Integrity. This feature guarantees that the data transmits from the sender to the receiver
without alterations. If a third party captures and modifies the traffic, the SSHv2 server detects
this alteration.
SSHv2 considerations using EDM
You must use ACLI to initially configure SSHv2. You can use Enterprise Device Manager (EDM) to
change the SSHv2 configuration parameters. However, Avaya recommends that you use ACLI.
Avaya also recommends that you use the console port (10101) to configure the SSHv2 parameters.
Important:
Do not enable SSHv2 secure mode using Configuration and Orchestration Manager (COM). If
you enable SSHv2 secure mode, then the system disables Simple Network Management
Protocol (SNMP). This locks you out of a COM session. Enable SSH secure mode using ACLI
or EDM.
SSHv2 secure mode is different from enhanced secure mode and hsecure. SSHv2 secure
mode disables unsecure management protocols on the device such as FTP, rlogin, SNMP,
telnet, and TFTP. SSHv2 secure mode is enabled through the ssh secure command.
When you enable SSHv2 secure mode, the system disables FTP, rlogin, SNMPv1, SNMPv2,
SNMPv3, telnet and TFTP. After SSHv2 secure mode is enabled, you can choose to enable
individual non-secure protocols. However, after you save the configuration and restart the
system, the non-secure protocol is again disabled, even though it is shown as enabled in the
configuration file. After you enable SSHv2 secure mode, you cannot enable non-secure
protocols by disabling SSHv2 secure mode.
You can disable block-snmp after you enable SSHv2 secure mode, and you can connect again
using COM.
SSHv2 support for IPv6
On IPv6 networks, the VSP switch supports SSHv2 server only. The VSP switch does not support
outbound SSHv2 client over IPv6. On IPv4 networks, the VSP switch supports both SSHv2 server
and SSHv2 client.
Interoperability
The VSP SSHv2 client can operate with the following SSHv2 servers:
Another Avaya Virtual Services Platform 8000 Series
ERS 8600/8800
VSP 4000
Linux running Open SSH
VSP 7000
Secure Shell fundamentals
January 2017 Administering Avaya VSP 7200 Series and 8000 Series 149
Comments on this document? infodev@avaya.com