This article explains the meaning and any impact caused by the below syslog message
SSHD_LOGIN_FAILED: Login failed for user '<host-name>' from host '10.100.200.61'
Logs
LogMay 16 04:43:35.673 : PAM_USER_LOCK_ACCOUNT_LOCKED: Account for user <user-name> is locked.
May 16 04:43:35.673: error: PAM: user account has expired for <user-name> from 10.100.200.61
May 16 04:43:35.674: SSHD_LOGIN_FAILED: Login failed for user <user-name> from host '10.100.200.61'
May 16 04:43:56.197: fatal: monitor_read: unpermitted request 104
May 16 04:43:56.199: /usr/sbin/sshd[97973]: exited, status 255
May 16 04:43:56.211: SNMPD_AUTH_RESTRICTED_ADDRESS: nsa_initial_callback: request from address 10.43.161.109 not allowed
May 16 04:43:58.540: SNMPD_AUTH_RESTRICTED_ADDRESS: nsa_initial_callback: request from address 10.43.161.110 not allowed
May 16 04:44:00.716: SNMPD_AUTH_RESTRICTED_ADDRESS: nsa_initial_callback: request from address 10.43.161.109 not allowed
May 16 04:44:38.034: fatal: monitor_read: unpermitted request 104
May 16 04:44:38.036: /usr/sbin/sshd[97978]: exited, status 255
May 16 04:44:40.070: SNMPD_AUTH_RESTRICTED_ADDRESS: nsa_initial_callback: request from address 10.43.161.109 not allowed
May 16 04:44:43.033 : LIBJNX_LOGIN_ACCOUNT_UNLOCKED: Account for user <user-name> has been unlocked for logins
May 16 04:44:43.046: Accepted keyboard-interactive/pam for <user-name> from 10.100.200.61 port 49944 ssh2
May 16 04:44:43.349 : UI_AUTH_EVENT: Authenticated user <user-name> assigned to class 'class-1'
May 16 04:44:43.349: User <user-name> login, class 'class-1' [97990], ssh-connection '10.100.200.61 49944 10.9.8.1 22', client-mode 'cli'
May 16 04:44:53.667: SNMPD_AUTH_RESTRICTED_ADDRESS: nsa_initial_callback: request from address 10.43.161.110 not allowed
Below logs indicate that there is SSH login failure for particular user, this can happen when cached user data is not updated because the domain the user is coming from is offline from some reasons.
We can try to logout and login again via SSH and check for SSHD logs or restart SSH connection, however these logs does not cause any production impact and hence can be safely ignored.