
Implementation Notes for All Dial Services
117353-B Rev. 00
5-9
RADIUS Accounting Services
As networks grow to accommodate more remote dial-in users, network security,
network use, and billing become more difficult to manage. Remote Authentication
Dial-In User Service (RADIUS) centralizes security and accounting information,
improving security and providing a solution that adapts to the changing needs of
the remote user and service providers.
RADIUS operates between a client and a server. The router is the RADIUS client.
RADIUS accounting requires that you configure one of the three dial services.
The dial service enables the router to activate a dial-up connection for RADIUS
calls. Dial-up calls are active for a limited time period; therefore, the RADIUS
server can measure the duration of the call and count the number of packets
transmitted to determine billing charges. To learn more about RADIUS, see
Configuring RADIUS.
For accounting services, you can configure either a dial service or RADIUS first.
The following Bay Networks platforms can operate as a RADIUS client:
• Backbone Link Node (BLN)
• Backbone Concentrator Node
(BCN)
• Access Stack Node (ASN)
ISDN Services
A router with built-in ISDN capability is a TE1 device, which is an
ISDN-compatible device. This means that the router provides the S/T interface,
which defines the boundary between the user and the network. (The ARN also
provides the U interface, which includes an integral NT1 interface.) The NT1
interface defines the point at which the service provider’s wires terminate at your
site.
For BRI service, the S/T interface follows the standards outlined in ITU-T
recommendation I.430, the physical layer protocol that defines the S/T interface.
For PRI service, the interface follows ITU-T recommendation I.431.
Note:
The BLN, BCN, and ASN also support RADIUS authentication, but
only with dial-on-demand service. For more information, see “RADIUS
Authentication Services for Demand Circuit Groups” on page 6-14.
Kommentare zu diesen Handbüchern