Example: Configuring a PPPoE Service Name Table for Dynamic Subscriber Interface Creation

This example shows how to configure a PPPoE service name table to create a dynamic PPPoE subscriber interface based on the service name, agent circuit identifier (ACI), and agent remote identifier (ARI) information provided by PPPoE clients during PPPoE negotiation.

In this example, PPPoE service name table TableDynamicPPPoE includes an any service entry, empty service entry, and two named service entries: Premium and Standard. The PPPoE underlying interfaces configured for TableDynamicPPPoE are ge-2/0/0.1 and ge-2/0/0.2. Only ge-2/0/0.1 is configured for dynamic profile assignment and creation of dynamic PPPoE subscriber interfaces.

Following the configuration example, Table 1 explains how the router evaluates the entries in TableDynamicPPPoE to create a dynamic PPPoE subscriber interface in a specified routing instance for each of several sample clients.

To configure a PPPoE service name table to create dynamic PPPoE subscriber interfaces:

1. Configure the PPPoE service name table.

2. Configure the PPPoE underlying interface for the service name table.

Table 1 lists the service name, ACI value, and ARI value provided in several sample PPPoE client requests, and the name of the PPPoE underlying interface on which the router received each client request. The Results column describes the dynamic PPPoE subscriber interface created by the router based on both of the following:

• The values received from each PPPoE client during PPPoE negotiation

• The sequence in which the router evaluates the entries configured in the PPPoE service name table to find a match for the client’s service name and ACI/ARI information, as described in Evaluation Order for Matching Client Information in PPPoE Service Name Tables