Accessing the Avaya G250/G350 Media Gateway
Set a policy for locking out access to the gateway after successive failed login attempts. To
●
do this, use login authentication lockout time attempt count, where time
is the interval of time for which lockout is enforced and count is a number of failed
attempts after which lockout is enforced. Use no login authentication lockout to
return the lockout time and lockout attempt threshold to their default values (180 and 3).
For example, to lockout Avaya Services access to the device for 360 seconds following
five failed login attempts:
G350-001(super)# login authentication lockout 360 attempt 5
This lockout affects all users locally stored in the gateway, including locally defined user
accounts and Avaya Services logins defined in the ASG authentication file. Remote users
maintained centrally in a Radius server are not subject to the lockout sanction.
Switch between modem operation modes, including rasaccess and ppp modes, using ppp
●
authentication {pap|chap|none|ras}. ASG authentication is enabled when ras
is selected. For example:
G350-001(super)# ppp authentication ras
Displaying ASG authentication information
Display login authentication settings and information, using show login
●
authentication. For example:
G350-001(super)# show login authentication
Services logins: On
Local craft: On
Lockout time: 180 seconds
Lockout attempt threshold: 3
Authentication response time: 120 seconds
CLI logout timeout: Off
Display ASG authentication file information, using show auth-file info. For example:
●
G350-001(super)# show auth-file info
Authentication File (AF) information:
AF-ID :7000012345
Date/time : 15:02:27 27-SEP-2005
Major release : 4
58 Administration for the Avaya G250 and Avaya G350 Media Gateways