Table 19: Sample PPPoE Service Name Table
(continued)
Action
Service Name
Drop
“myQOSClass2”
Drop
“ ”
(empty-service-name)
Drop
unknown-service-name
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 404.
Using the PPPoE Remote Circuit ID to Identify Subscribers
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.
Overview
■
379
Chapter 12: Configuring Point-to-Point Protocol over Ethernet
Содержание JUNOSE 11.1.X - LINK LAYER CONFIGURATION 4-7-2010
Страница 6: ...vi...
Страница 8: ...viii JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 26: ...xxvi List of Figures JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 34: ...2 Chapters JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 200: ...168 Monitoring Upper Level Protocols over Ethernet JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 230: ...198 Monitoring VLAN and S VLAN Subinterfaces JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 258: ...226 Monitoring 802 3ad Link Aggregation JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 334: ...302 Troubleshooting JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 394: ...362 Monitoring Multiclass MLPPP JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 406: ...374 Monitoring POS JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 468: ...436 Troubleshooting JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 498: ...466 Monitoring Bridged Ethernet JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 546: ...514 Monitoring Cisco HDLC JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 747: ...Part 2 Index Index on page 717 Index 715...
Страница 748: ...716 Index JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 774: ...742 Index JUNOSe 11 1 x Link Layer Configuration Guide...