User guide

Security Administration NMS RADIUS Client Support
113
AlliedView NMS Administration Guide
1. Use CSUtil.exe -addUDV <slot> c:\ACS_Data\allied-telesis.ini to import the VSA file.
2. Use the Web interface to configure the AAA client (the NMS) and Users with the VSA:
3. Use “Interface Configuration” to enable RADIUS (Allied-Telesis) for Users.
4. Use “Network Configuration” to set authentication for the AAA client using RADIUS (Allied-Telesis)
3. Add users and permission groups.
1. Use “User Configuration” to create the users, assign their passwords, and, at the bottom, enable and assign the VSA
(ATI-avnms-group) to the user's permission group(s). Separate multiple group names with commas but do not
enclose the string with quotation marks.
2. Select any other relevant options and data fill as necessary.
3. Be sure all changes are submitted and applied where necessary.
4. Configure the NMS to use this RADIUS server, either by itself or within a list of RADIUS servers. Using the
AT_ConfigureRadius tool, assuming the server location is 10.52.18.110, the auth and acct ports are 1645 and 1646
respectively (Cisco defaults), add the selected line to the NMS configuration, as shown in the following figure.
FIGURE 4-2 Configuring NMS as Cisco Secure ACS Client
4.8.4 Feature Interactions (RADIUS Server De-activated or Unavailable)
As shown throughout this section, including in the examples, Admin and Users are the default groups defined on the NMS
server, and custom groups may be added using the NMS Security Management feature. The administrator can then choose to
include these groups when defining accounts on the RADIUS server.
In most cases, once the administrator has defined these accounts, the RADIUS server is activated, and users log in to the
NMS transparently using these defined accounts. The administrator could
1. Change passwords for existing user IDs
2. Change which users belonged to which permission groups.
3. Assign new user IDs and passwords, and associate them with a group or groups