Enabling The Service Name Table For Use; Using The Pppoe Remote Circuit Id To Identify Subscribers; Application - Juniper JUNOSE SOFTWARE 11.2.X - LINK LAYER CONFIGURATION GUIDE 7-7-2010 Configuration Manual

Using the PPPoE Remote Circuit ID to Identify Subscribers

Copyright © 2010, Juniper Networks, Inc.
Table 19: Sample PPPoE Service Name Table (continued)
Service Name Action
" " Drop
(empty-service-name)
unknown-service-name Drop
NOTE: You can associate the drop action with a maximum of eight service tags in a
PPPoE service name table.

Enabling the Service Name Table for Use

After you create a PPPoE service name table and populate it with entries, you must
enable it for use with a static or dynamic PPPoE interface. To enable a PPPoE service
name table for use with a static interface, you assign the table to the PPPoE major
interface. To enable a PPPoE service name table for use with a dynamic interface, you
add the table to a profile that is dynamically assigned to a PPPoE interface column. For
details about configuring and using PPPoE service name tables, see "Configuring PPPoE
Service Name Tables" on page 405.
You can enable the router to capture and format a vendor-specific tag containing a
PPPoE remote circuit ID transmitted from a digital subscriber line access multiplexer
(DSLAM) device. The router can then send this value to a Remote Authentication Dial-In
User Service (RADIUS) server or to a Layer 2 Tunneling Protocol (L2TP) network server
(LNS) to uniquely identify subscriber locations.
This feature is supported on all modules on which you can configure PPPoE interfaces.
The feature is particularly useful in Ethernet-based Broadband Remote Access Server
(B-RAS) configurations as a means of uniquely identifying subscribers connected to the
router on a single Ethernet link.
For detailed configuration instructions, see "Configuring PPPoE Remote Circuit ID Capture"
on page 413.

Application

When a connection between an E Series router and a DSLAM is on an ATM interface,
subscribers are typically assigned an ATM PVC to communicate with the router. Each
ATM PVC is created on a different ATM 1483 subinterface. When a RADIUS server in this
configuration sends messages to the router containing the NAS-Port-Id [87] RADIUS
attribute, each ATM 1483 subinterface produces a unique NAS-Port-Id that can
differentiate subscribers on the ATM link.
By contrast, when the connection between the router and the DSLAM is on an Ethernet
interface that does not use either virtual LANs (VLANs) or stacked VLANs (S-VLANs),
the NAS-Port-Id value is the same for all subscribers on the Ethernet link. Enabling the
router to capture the remote circuit ID sent from the DSLAM and use it as a RADIUS or
Chapter 12: Configuring Point-to-Point Protocol over Ethernet
375