Avaya Configuring RADIUS Manual de usuario Pagina 27

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 116
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 26
RADIUS Overview
308640-15.1 Rev 00
1-11
For non-Nortel 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 Nortel 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, see 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.
An accounting session is the time during which the remote user communicates
with the client. The session begins when the client passes an accounting request
from the remote user to the server, with an accounting status byte set to start. The
session ends when the client sends a second request with the accounting status
byte set to stop. Multiple accounting sessions can occur simultaneously if there
are multiple dial-up connections.
The client sends accounting requests only to the server configured for accounting,
enabling you to use different servers for accounting and authentication.
If the client cannot reach the primary server after several attempts, and you
configured an alternate server, the client sends the accounting request to the
alternate server. If an accounting session starts with the primary server, and this
server goes down, the session is continued with the alternate server. Unless the
primary server recovers, the request to end the session is then sent to the alternate
server. To accurately determine billing charges, the network administrator collects
information from all accounting servers.
Vista de pagina 26
1 2 ... 22 23 24 25 26 27 28 29 30 31 32 ... 115 116

Comentarios a estos manuales

Sin comentarios