JunosE 11.2.x Broadband Access Configuration Guide
Remote Access References
Before You Configure B-RAS
Remote Access Configuration Tasks
6
Bridged Ethernet
Layer 2 Tunneling Protocol (L2TP), both L2TP access concentrator (LAC) and L2TP
network server (LNS)
For more information about the topics covered in this chapter, see the following
documents:
RFC 2748—The COPS (Common Open Policy Service) Protocol (January 2000)
RFC 2865—Remote Authentication Dial In User Service (RADIUS) (June 2000)
RFC 3084—COPS Usage for Policy Provisioning (COPS-PR) (March 2001)
RFC 3159—Structure of Policy Provisioning Information (SPPI) (August 2001)
RFC 3198—Terminology for Policy-Based Management (November 2001)
RFC 3317—Differentiated Services Quality of Service Policy Information Base
(DIFFSERV-PIB)
RFC 3318—Framework Policy Information Base (March 2003)
JunosE Release Notes, Appendix A, System Maximums—Refer to the Release Notes
corresponding to your software release for information about the number of concurrent
RADIUS requests that the router supports for authentication and accounting servers.
Before you begin to configure B-RAS, you need to collect the following information for
the RADIUS authentication and accounting servers:
IP addresses
User Datagram Protocol (UDP) port numbers
Secret keys
Each configuration task is presented in a separate section in this chapter. Most of the
B-RAS configuration tasks are optional.
To configure B-RAS, perform the following tasks:
Configure a B-RAS license.
1.
(Optional) Map a user domain name to a virtual router. By default, all requests go
2.
through a default router.
(Optional) Set up domain name and realm name usage.
3.
(Optional) Specify a single name for users from a domain.
4.
Copyright © 2010, Juniper Networks, Inc.