Table 10: Dsa Authentication Access Level And File Name - Avaya VSP 4000 Technical Configuration Manual

Linux/Unix/Cygwin
FileZilla
After you install one of the SSHv2 clients you must generate a client and server key using the RSA or
DSA algorithms if you wish to use public key authentication. Please note that the VSP switch when acting
as an SSH server can only support one PKI key per access level, i.e. one key file per rwa, rw, ro, etc.
access level.
The VSP switch generates a DSA server and client keys stored in the following location respectively:
/intflash/.ssh/ssh_dsa.key
/intflash/.ssh/id_dsa_rwa (private key for DSA client)
/intflash/.ssh/id_dsa_rwa.pub (public key for DSA client)
If a DSA key pair does not exist, then the VSP modular switch automatically generates one when you
enable the SSHv2 server.
To authenticate an SSHv2 client using DSA, the administrator must copy the public part of the client DSA
key to /intflash/.ssh directory on the VSP switch that is acting as the SSHv2 server. That file that is copied
over to the SSHv2 server must be named according to Table 10 shown below.

Table 10: DSA authentication access level and file name

Client key format
Client key in IETF format (SSHv2)
Client key in non IETF format

Please note that for the VSP 9000 only, the client keys in IEFT format requires the key to end
with "ietf.
March 2015
 Authentication:
o RSA
o DSA
o Password
Avaya Inc. – External Distribution
and SFTP
 Includes SFTP support
File name
Access Level
VSP 9000 and VOSS 4.1 or
lower (VSP 4000/8000)
/intflash/.ssh/dsa_key_rwa_ietf
RWA
RW /intflash/.ssh/dsa_key_rw_ietf
RO /intflash/.ssh/dsa_key_ro_ietf
/intflash/.ssh/dsa_key_rwl3_ietf
L3
L2 /intflash/.ssh/dsa_key_rwl2_ietf
L1 /intflash/.ssh/dsa_key_rwl1_ietf
/intflash/.ssh/dsa_key_rwa
RWA
RW /intflash/.ssh/dsa_key_rw
RO /intflash/.ssh/dsa_key_ro
/intflash/.ssh/dsa_key_rwl3
L3
L2 /intflash/.ssh/dsa_key_rwl2
L1 /intflash/.ssh/dsa_key_rwl1
avaya.com
79