Avaya Configuring RADIUS Bedienungsanleitung PDF herunterladen (Seite 23)

RADIUS Overview

117385-B Rev 00

1-9

Using RADIUS with IP Utilities

To use RADIUS authentication with an IP utility, you must configure the

RADIUS server so that it can recognize vendor-specific RADIUS clients.

• For Bay Networks servers, copy the bayrs.dct, vendor.ini, and dictiona.dcm

files from the distribution CD to the directory you define at installation time

(usually C:\RADIUS\Services). For more information, refer to Appendix D,

“Vendor-Specific Attributes” and the BaySecure Access Control

Administration Guide for your platform (UNIX, NetWare, or NT).

• For non-Bay servers, use the bayrs.dct file shown in Appendix D to modify

your existing RADIUS dictionary. Because the bayrs.dct file is in the format

of some popular RADIUS servers, you may be able to use it as a direct

replacement for the existing RADIUS dictionary. For more information, refer

to the vendor-specific server documentation.

The Bay Networks vendor ID is 1584, as allocated by the Internet Assigned

Numbers Authority. Use this ID in the VSA header.

For information on IP utilities, refer to Configuring IP Utilities.

RADIUS Accounting

You configure RADIUS accounting on a slot-by-slot basis. Therefore, a call

designated for a RADIUS-configured slot performs RADIUS accounting.

The RADIUS accounting server calculates billing charges for a communication

session between the remote user and the client. The RADIUS client sends

information to the server, such as the status of each call and the number of packets

transmitted during the session. Using this data, the server determines billing

charges, which the network administrator can use to manage network costs.

Note:

To use RADIUS with IP utilities such as FTP, NTP, HTTP, and Telnet,

your RADIUS server must support VSAs.

1 2 ... 18 19 20 21 22 23 24 25 26 27 28 ... 98 99

Keine Kommentare

Avaya Configuring RADIUS Bedienungsanleitung Seite 23