Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Evaluation Order for Matching Client Information in PPPoE Service Name Tables
Related
Documentation
When the router receives a service request from a PPPoE client, it evaluates the entries
configured in the PPPoE service name table to find a match for the client’s ACI/ARI
information so it can take the appropriate action.
The order of evaluation is as follows:
1. The router evaluates the ACI/ARI information configured for the any service entry, and
ignores the contents of the service name tag transmitted by the client.
2. If no match is found for the client information, the router evaluates the ACI/ARI
information for the empty service entry and the named service entries. If an ACI/ARI
pair is not configured for these service entries, the router evaluates the other attributes
configured for the empty service and named services.
3. If there is still no match for the client information, the router evaluates the other
•
attributes configured for the any service entry, and ignores both the ACI/ARI information
for the any service and the contents of the service name tag transmitted by the client.
If the any service is configured for the default action, drop, the router drops the PADR
packet. If the any service is configured for a nondefault action (terminate or delay),
the router evaluates the other attributes configured for the any service.
Understanding PPPoE Service Name Tables on page 398
• Benefits of Configuring PPPoE Service Name Tables on page 403
• Configuring PPPoE Service Name Tables on page 412
• Example: Configuring a PPPoE Service Name Table for Dynamic Subscriber Interface
Creation
• PPPoE Overview on page 394
• Junos® OS Ethernet Interfaces
Benefits of Configuring PPPoE Service Name Tables
Copyright © 2012, Juniper Networks, Inc.
This topic describes the benefits of configuring PPPoE service name tables.
Configuring PPPoE service name tables provides the following benefits:
• Enables support for multiple services requested by PPPoE clients, and configuration
of an action for the underlying PPPoE interface to take (delay, drop, or terminate) upon
receipt of a PPPoE Active Discovery Initiation (PADI) packet requesting that service.
• Provides tighter control over which PPPoE clients can log in to and receive services
from a particular PPPoE server.
• Provides load balancing across a set of remote access concentrators (ACs) in a mesh
topology by enabling you to configure agent circuit identifier/agent remote identifier
(ACI/ARI) pairs for named, empty, and any service entries to specify the appropriate
AC to receive and service a particular PPPoE client request.
Chapter 30: Configuring Point-to-Point Protocol over Ethernet
403