You can perform the following login configurations:
Block login access of Avaya Logins using EASGManage disableEASG. This deactivates all Avaya logins. To reactivate, use EASGManage enableEASG.
You can set the time duration the gateway waits for a user to respond to authentication requests before timing out a connection. Use login authentication response-time time, where time is the time span in seconds following which the gateway aborts the connection if no response is received.
The following example shows a connection being timed out if no response arrives within 180 seconds of an authentication request:
(super)# login authentication response-time 180
Use no login authentication response-time to restore the response time span to the factory default of 120 seconds. The time value you enter is used for both:
Set a policy for blocking access to Branch Gateway following successive failed login attempts. To do this, use the login authentication lockout time attempt count command. time is the time duration for which the lockout is enforced and count is the number of failed attempts following which lockout is enforced. Use no login authentication lockout to return the lockout time and lockout attempt threshold to their default values. The default time span for lockout time and lockout attempt is 180 seconds and 3 seconds respectively.
The following example shows blocking access of Avaya Services to the device for 360 seconds following five failed login attempts:
(super)# login authentication lockout 360 attempt 5
This lockout affects locally defined user accounts and Avaya Logins. Remote users maintained centrally in a Radius server are not subject to the lockout sanction.
