Previous page Next page

Login Order of Operations

When a user attempts to log into the Avaya switch, the switch will first check the local user accounts for the entered user name and password. If found, the user is logged in using the local settings for that account.

If no local account is found and RADIUS is enabled/configured, the switch will send an Access Request message to the primary RADIUS server in an attempt to authenticate the user remotely. If the user’s login is found and correct, then the RADIUS server responds with an Access Accept message that includes the user’s privileges. Provided the user account has the right Management Type (for example: Web Agent if you are trying to log in to the embedded Web Agent), the user is granted access.

If the user’s login is incorrect or does not exist, then a Access Reject message is sent to the switch and the user is denied access to the switch.

If the RADIUS server does not respond, the Avaya switch will attempt to use the Secondary server if it is configured, and if not, will continue to try the Primary. If the Secondary server is configured, the switch will alternate between the two servers on subsequent retries. It will wait the number of seconds specified in the retry interval and try as many times as specified in the retry time.


Previous page Next page