Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

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:

Table 1: Dynamic PPPoE Subscriber Interface Creation Based on PPPoE Client Request Values

PPPoE

Client

Service

Name

ACI Value

ARI Value

Receiving Underlying Interface

Results

Client 1

Premium

broadway-ge-1/0/1.1

london

ge-2/0/0.1

Matches ACI/ARI pair configured for any service. Router creates dynamic PPPoE subscriber interface over ge-2/0/0.1 using LondonProfile dynamic profile and LondonRI routing instance assigned to any service.

Client 2

Premium

dunstable-ge-1/0/1.0

toronto

ge-2/0/0.1

Matches base Premium service. Router creates dynamic PPPoE subscriber interface over ge-2/0/0.1 using PremiumProfile dynamic profile and routing instance associated with ge-2/0/0.1 underlying interface.

Client 3

empty

dunstable-ge-1/0/0.1

kanata

ge-2/0/0.1

Matches ACI/ARI pair configured for empty service and Standard service. Router creates dynamic PPPoE subscriber interface over ge-2/0/0/.1 after a delay of 10 seconds. Router uses BasicPPPoEProfile dynamic profile and routing instance associated with ge-2/0/0.1 underlying interface.

Client 4

empty

slinger-ge-1/0/0.1

chicago

ge-2/0/0.2

Because receiving underlying interface ge-2/0/0.2 is not associated with a dynamic profile, router does not create a dynamic PPPoE subscriber interface, and drops any PADI or PADR control packets received from this client.

Client 5

Standard

slinger-ge-1/0/0.1

chicago

ge-2/0/0.1

Matches base Standard service. Router creates dynamic PPPoE subscriber interface over ge-2/0/0.1 using StandardProfile dynamic profile and routing instance associated with ge-2/0/0.1 underlying interface.