SSH/5/SSH_USER_LOGIN_FAIL

Message

SSH/5/SSH_USER_LOGIN_FAIL: The SSH user failed to login. (ServiceType=[ServiceType], FailedReason=[FailedReason], UserName=[UserName], UserAddress=[UserAddress], LocalAddress=[LocalAddress], VPNInstanceName=[VPNInstanceName])

In VS mode, this log is supported only by the admin VS.

Description

SSH user login failed.

Parameters

Parameter Name	Parameter Meaning
ServiceType	Service type
FailedReason	Cause of the login failure
UserName	SSH user name
UserAddress	IP address of the client
LocalAddress	IP address of the server
VPNInstanceName	Index of the VPN instance name

Possible Causes

Cause 1: The SSH user does not exist.

Cause 2: The RSA, DSA, or ECC does not exist.

Cause 3: The user name or password is incorrect.

Cause 4: The SSH service is disabled.

Cause 5: The ACL rule matches the IP address of the user and the action is deny.

Cause 6: The number of users connected to the SSH server reached the maximum value.

Cause 7: The user access permission is not enabled for the default path.

Procedure

1. The handling procedures for different causes are as follows:

Cause 1: An SSH user was created using the ssh user command.

Cause 2:

Run the display rsa local-key-pair public command to check the public key in the local RSA key pair. If no RSA key pair is configured, run the rsa local-key-pair create command to generate a local RSA key pair.
Run the display ecc local-key-pair public command to check the public key in the local ECC key pair. If no ECC key pair is configured, run the ecc local-key-pair create command to generate a local ECC key pair.
Run the display dsa local-key-pair public command to check the public key in the local DSA key pair. If no DSA key pair is configured, run the dsa local-key-pair create command to generate a local DSA key pair.

Cause 3: Ensure that the user name and password are correct.

Cause 4: Ensure that the SSH service is enabled.

Cause 5: Run the acl and rule commands in sequence to change the action of the corresponding rule to permit.

Cause 6: Ensure that the number of users connected to the SSH server does not reach the maximum value.

Possible cause 7: The user access permission for the default path is enabled.

2. Collect log and configuration information, and contact technical support personnel.