# Configuring PPPoE Dynamic Interfaces over PPPoE Static Interfaces

E Series routers support dynamic PPPoE subinterfaces over static PPPoE major interfaces. The PPPoE major interfaces can be created over:

- ATM
- Ethernet
- Ethernet with VLANs
- Ethernet with S-VLANs

The following sections describe how to create each of these configurations on the router. In addition, Configuring Encapsulation Type Lockout for PPPoE Clients describes how to configure dynamic encapsulation type lockout for PPPoE clients associated with dynamic PPPoE subinterface columns.

## Configuring Dynamic PPPoE over Static PPPoE with ATM Interface Columns

Figure 49 shows dynamic PPPoE subinterface columns and illustrates an alternative method for PPPoE to support multiple IP sessions over each ATM 1483 circuit.

Figure 49: Dynamic PPPoE over Static PPPoE with ATM Interface Columns

To configure an ATM 1483 subinterface to support a dynamic PPPoE subinterface:

1. Configure a physical interface.
   host1(config)#interface atm 5/0
2. Configure an ATM 1483 subinterface.
   host1(config-if)#interface atm 5/0.1
3. Configure a PVC by specifying the virtual circuit descriptor (VCD), the virtual path identifier (VPI), the virtual channel identifier (VCI), and the encapsulation type.

   If you want the router to autodetect the encapsulation type, use the aal5autoconfig option.

   host1(config-subif)#atm pvc 10 100 22 aal5snap host1(config-subif)#atm pvc 10 100 22 aal5autoconfig
4. Set the encapsulation type to PPPoE to create the PPPoE major interface.
   host1(config-subif)#encapsulation pppoe
5. Assign a profile.
   host1(config-subif)#pppoe profile pppoeProfile1
6. Configure the interface to detect and accept dynamic PPPoE subinterfaces.
   host1(config-subif)#pppoe auto-configure

   When you configure dynamic encapsulation type lockout for PPPoE sessions that contain the IWF-Session DSL Forum VSA (26-254) in the PPPoE active discovery request (PADR) packets, even if PPPoE sessions associated with a particular MAC address are locked out, other PPPoE sessions that originated with the same MAC address are not terminated (continue to remain logged in) if they are IWF sessions from different access loops (PPPoE clients) and this information is available to the B-RAS application.

7. (Optional) Verify your configuration.
   host1#show atm subinterface atm 5/0.1 host1#show pppoe interface atm 5/0.1

## Configuring Dynamic PPPoE over Static PPPoE with Ethernet Interface Columns

Figure 50 shows dynamic PPPoE subinterface columns configured over an Ethernet interface without VLANs.

Figure 50: Dynamic PPPoE over Static PPPoE with Non-VLAN Interface Columns

To configure an Ethernet interface without VLANs to support a dynamic PPPoE subinterface:

1. Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet interface.
   host1(config)#interface fastEthernet 4/1
2. Assign an IP address and mask.
   host1(config-if)#ip address 192.6.129.5 255.255.255.0
3. Specify PPPoE as the encapsulation method on the interface.
   host1(config-subif)#encapsulation pppoe

   This command creates the static PPPoE major interface.

4. Assign a profile to the PPPoE major interface.
   host1(config-subif)#pppoe profile pppoeProfile3
5. Configure the interface to detect and accept dynamic PPPoE subinterfaces.
   host1(config-subif)#pppoe auto-configure

## Configuring Dynamic PPPoE over Static PPPoE with Ethernet and VLAN Interface Columns

Figure 51 shows dynamic PPPoE subinterface columns and illustrates an alternative method for PPPoE to support multiple IP sessions over each VLAN.

Figure 51: Dynamic PPPoE over Static PPPoE with VLAN Interface Columns

To configure a VLAN subinterface to support a dynamic PPPoE subinterface:

1. Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet interface.
   host1(config)#interface fastEthernet 4/1
2. Specify VLAN as the encapsulation method.
   host1(config-if)#encapsulation vlan

   This command adds the VLAN major interface.

3. Create a VLAN subinterface by adding a subinterface number to the interface identifier.
   host1(config-if)#interface fastEthernet 4/1.1
4. Assign a VLAN ID for the subinterface.
   host1(config-if)#vlan id 400
5. Set the encapsulation type to PPPoE.
   host1(config-subif)#encapsulation pppoe
6. Assign a profile.
   host1(config-subif)#pppoe profile pppoeProfile2
7. Configure the interface to detect and accept dynamic PPPoE subinterfaces.
   host1(config-subif)#pppoe auto-configure

## Configuring IPv4 and IPv6 over Static and Dynamic PPPoE

You can configure IPv4 and IPv6 interface columns over static and dynamic PPPoE, as shown in Figure 52.

Figure 52: IPv4 and IPv6 Interface Columns over Static and Dynamic PPPoE

To configure IPv4 and IPv6 interface columns over dynamic PPPoE:

1. Specify the loopback mode for an interface and assign both IPv6 and IPv4 addresses to the interface.
   host1(config)#interface loopback 1 host1(config-if)#ipv6 address 2000::1/64 host1(config-if)#ip address 2.2.2.1/24
2. Create a profile that defines attributes for the dynamic interface. You can use this profile to configure IPv4 or IPv6, or both IPv4 and IPv6 PPP interfaces.
   host1(config)#profile ipv4Ipv6Profile host1(config-profile)#ip virtual-router ppp host1(config-profile)#ip unnumbered loopback 1 host1(config-profile)#ipv6 virtual-router ppp host1(config-profile)#ipv6 unnumbered loopback 1 host1(config-profile)#ipv6 nd other-config-flag host1(config-profile)#ipv6 nd ra-interval 10 host1(config-profile)#ppp authentication chap host1(config-profile)#exit
3. Specify the interface.
   host1(config-if)#interface gigabitEthernet 4/0/6
4. Set the encapsulation type to PPPoE.
   host1(config-subif)#pppoe
5. Configure the interface to detect and accept dynamic PPPoE subinterfaces.
   host1(config-subif)#pppoe auto-configure
6. Assign the profile to any autoconfigured encapsulation.
   host1(config-if)#pppoe profile any ipv4Ipv6Profile

interface loopback

- Use to access and configure the loopback interface.
- Provides a stable address to minimize impact of a physical interface going down.
- Example
  host1(config)#interface loopback 20 host1(config-if)#ip address 10.10.20.5 255.255.255.254
- Use the no version to delete the loopback interface.
- See interface loopback.

ip address

- Use to assign an IP address and subnet mask to a subinterface.
- Example
  host1(config-if)#ip address 10.10.20.5 255.255.255.254
- Use the no version to remove an IP address or to disable IP processing.
- See ip address.

ip unnumbered

- Use to specify the numbered interface with which dynamic unnumbered interfaces created with the profile are associated.
- You can specify an unnumbered interface using RADIUS instead of using the ip unnumbered command in a profile. For more information about how to specify an unnumbered interface using RADIUS, see Configuring RADIUS Attributes in the JunosE Broadband Access Configuration Guide.
- Example
  host1(config-profile)#ip unnumbered fastEthernet 0/0
- Use the no version to remove the assignment from the profile.
- See ip unnumbered

ip virtual-router

- Use to assign a virtual router to a profile.
- You can configure a virtual router using RADIUS instead of adding one to the profile by using the ip virtual-router command. For more information about how to configure a virtual router using RADIUS, see Configuring RADIUS Attributes in the JunosE Broadband Access Configuration Guide.
- Example
  host1(config-profile)#ip virtual-router VR1
- Use the no version to remove the virtual router assignment.
- See ip virtual-router

ipv6 address

- Use to add an IPv6 address to an interface or a subinterface.
- Example
  host1(config)#interface gigabitEthernet 1/0.25 host1(config-if)#ipv6 address 1::1/64
- Use the no version to remove an IPv6 address.
- See ipv6 address

ipv6 nd

- Use to enable the IPv6 Neighbor Discovery process on an interface.
- You can include the following commands in IPv6 profiles to configure Neighbor Discovery route advertisement characteristics.

  Command | Description
  --- | ---
  ipv6 nd | Enables Neighbor Discovery on an interface
  ipv6 nd other-config-flag | Sets the “other stateful configuration” flag in IPv6 router advertisements
  ipv6 nd ra-interval | Configures the interval between IPv6 router advertisements

- Example
  host1(config)#profile ProfileIpv6South22 host1(config-profile)#ipv6 nd
- Use the no version to disable the Neighbor Discovery process for the profile.
- See ipv6 nd

ipv6 unnumbered

- Use to set up an unnumbered interface.
- An unnumbered interface does not have an IPv6 address assigned to it. Unnumbered interfaces are often used in point-to-point connections where an IPv6 address is not required.
- This command enables IPv6 processing on an interface without your having to assign an explicit IPv6 address to the interface.
- You supply an interface location that is the type and number of another interface on which the router has an assigned IPv6 address. This interface cannot be another unnumbered interface.
- Example
  host1(config-if)#ipv6 unnumbered loopback 0
- Use the no version to disable IPv6 processing on an interface.
- See ipv6 unnumbered

ipv6 virtual-router

- Use to assign a virtual router to a profile.
- You can configure a virtual router using RADIUS instead of adding one to the profile by using the ipv6 virtual-router command. For more information about how to configure a virtual router using RADIUS, see Configuring RADIUS Attributes in the JunosE Broadband Access Configuration Guide.
- Example
  host1(config-profile)#ipv6 virtual-router VR6
- Use the no version to remove the virtual router assignment.
- See ipv6 virtual-router

ppp authentication

- Use to request authentication from a PPP peer and set the authentication method.
- The router supports the MD5 authentication algorithm for CHAP authentication.
- Example 1—Specifies the order of preference for the primary authentication protocol
  host1(config-if)#ppp authentication pap chap eap

  The router requests the use of PAP as the authentication protocol (because it appears first in the command line). If the peer refuses to use PAP, the router requests the CHAP protocol. If the peer refuses to use CHAP, the router requests the EAP protocol. If the peer refuses to negotiate authentication, the router terminates the PPP session.

- Example 2—Configures EAP or CHAP or PAP on a dynamic PPP interface
  host1(config)#profile ppptest host1(config-profile)#ppp authentication eap chap pap

  In this example, the router first attempts EAP negotiation. If PPP receives a NAK from the peer in response to the EAP request, then the router attempts CHAP negotiation. If PPP receives a NAK from the peer in response to the CHAP request, then the router attempts PAP negotiation. If PAP is also rejected, then PPP terminates the session.

- Use the no version to specify that the router does not require authentication.
- See ppp authentication.

pppoe

- Use to specify PPPoE as the encapsulation method for the interface.
- This command creates a PPPoE major interface.
- Example
  host1(config-if)#pppoe
- Use the no version to remove the PPPoE major interface.
- See pppoe.

profile

- Use from Global Configuration mode to create a profile. You can specify a profile name of up to 80 characters.
- Use from Interface Configuration mode or Subinterface Configuration mode to assign a profile to a PPP interface. The profile configuration is used to dynamically create an upper IP interface.
- Example 1–Creates a profile named foo.
  host1(config)#profile foo
- Example 2–Assigns a profile named action to a PPP interface.
  host1(config-if)#interface gigabitEthernet 2/1 host1(config-if)#encapsulation ppp host1(config-if)#profile action
- Use the no version from Global Configuration mode to remove a profile.
- Use the no version from Interface Configuration mode or Subinterface Configuration mode to remove a profile assignment from an interface.
- See profile

## Configuring Dynamic PPPoE over Static PPPoE with Ethernet and S-VLAN Interface Columns

Figure 53 shows dynamic PPPoE subinterface columns over PPPoE major interfaces using S-VLANs over Ethernet.

Figure 53: Dynamic PPPoE over Static PPPoE with S-VLAN Interface Columns

To configure an S-VLAN subinterface to support a dynamic PPPoE subinterface:

1. Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet interface.
   host1(config)#interface fastEthernet 4/1
2. Specify VLAN as the encapsulation method.
   host1(config-if)#encapsulation vlan

   This command creates the VLAN major interface.

3. Create a VLAN subinterface by adding a subinterface number to the interface identifier.
   host1(config-if)#interface fastEthernet 3/1.1
4. Assign an S-VLAN ID and a VLAN ID for the subinterface.
   host1(config-if)#svlan id 3 300
5. Assign an S-VLAN Ethertype.
   host1(config-if)#svlan ethertype 9200
6. Specify PPPoE as the encapsulation method on the interface.
   host1(config-subif)#encapsulation pppoe

   This command creates the PPPoE major interface.

7. Assign a profile.
   host1(config-subif)#pppoe profile pppoeProfile3
8. Configure the interface to detect and accept dynamic PPPoE subinterfaces.
   host1(config-subif)#pppoe auto-configure

### S-VLAN Oversubscription

When you configure S-VLAN subinterfaces over Ethernet interfaces to support dynamic PPPoE subinterfaces, you can take advantage of S-VLAN oversubscription.

The maximum number of S-VLANs that you can create per I/O module or IOA with PPPoE major interfaces stacked over them is greater than the maximum number of dynamic PPPoE subinterfaces. The maximum number of PPP interfaces supported per line module is directly proportional to the maximum number of PPPoE subinterfaces.

As a result, you can oversubscribe S-VLANs by configuring up to the maximum number of S-VLANs supported on the I/O module or IOA, knowing that no more than the maximum number of supported PPP sessions can be connected to the router at any one time.

For information about the module combinations that support S-VLAN oversubscription, see S-VLAN Oversubscription in Configuring VLAN and S-VLAN Subinterfaces .

For specific information about the maximum number of S-VLANs supported per I/O module or IOA and the maximum number of PPP interfaces and PPPoE subinterfaces supported per line module, see JunosE Release Notes, Appendix A, System Maximums.

| Note: S-VLAN oversubscription is not currently supported for S-VLANs configured over bridged Ethernet interfaces. The E120 and E320 routers can support up to two IOAs per line module. This maximum number of S-VLANs per line module does not change whether one or two IOAs are installed. For more information about configuration options for the ES2-S1 GE-4 IOA, see Configuring Ethernet Interfaces in JunosE Physical Layer Configuration Guide.

atm pvc

- Use to configure a PVC on an ATM interface. Specify one of the following encapsulation types:
  - aal5autoconfig—Enables autodetection of the 1483 encapsulation (LLC/SNAP or VC multiplexed).
  - aal5snap—Specifies a logical link control (LLC) encapsulated circuit; the LLC/Subnetwork Access Protocol (LLC/SNAP) header precedes the protocol datagram.
  - aal5mux ip—Specifies a VC multiplexed circuit. This option is used for IP only.
- Example
  host1(config-subif)#atm pvc 6 0 11 aal5autoconfig
- Use the no version to remove the specified PVC.
- See atm pvc.

encapsulation pppoe

- Use to configure PPPoE as the encapsulation method for the interface.
- Example
  host1(config-if)#encapsulation pppoe
- Use the no version to remove PPPoE encapsulation from the interface.
- See encapsulation pppoe.

encapsulation vlan

- Use to configure VLAN as the encapsulation method for the interface.
- Example
  host1(config-if)#encapsulation vlan
- Use the no version to remove VLAN encapsulation from the interface.
- See encapsulation vlan.

interface atm

- Use to select an ATM interface or ATM 1483 subinterface.
- For information about specifying the ATM interface or subinterface, see interface atm.
- Examples
  host1(config)#interface atm 5/0.1 host1(config)#interface atm 4/0/2.1
- Use the no version to remove the interface or subinterface.
- See interface atm.

interface fastEthernet

- Use to select a Fast Ethernet interface.
- Example
  host1(config)#interface fastEthernet 4/1
- Use the no version to remove IP from an interface or a subinterface. You must issue the no version from the highest level down; you cannot remove an interface or a subinterface if the one above it still exists.
- See interface fastEthernet.

interface gigabitEthernet

interface tenGigabitEthernet

- Use to select a Gigabit Ethernet interface or a 10-Gigabit Ethernet interface.
- To specify a Gigabit Ethernet interface for ERX7xx models, ERX14xx models, and ERX310 router, use the slot/port[.subinterface ] format.
- To specify a Gigabit Ethernet interface or a 10-Gigabit Ethernet interface for E120 and E320 routers, use the slot/adapter/port[.subinterface ] format.
- For more information, see Configuring Ethernet Interfaces in JunosE Physical Layer Configuration Guide.
- Examples
  host1(config)#interface gigabitEthernet 1/0 host1(config)#interface gigabitEthernet 4/0/1 host1(config)#interface tenGigabitEthernet 4/0/1
- Use the no version to remove IP from an interface. You must issue the no version from the highest level down; you cannot remove an interface or subinterface if the one above it still exists.
- See interface gigabitEthernet.
- See interface tenGigabitEthernet.

ip address

- Use to assign an IP address and subnet mask to an interface or a subinterface.
- Example
  host1(config-if)#ip address 192.1.1.1 255.255.255.0
- Use the no version to remove an IP address or disable IP processing.
- See ip address.

pppoe auto-configure

- Use to set up the router to dynamically create PPPoE subinterfaces on the PPPoE major interfaces.
- Example
  host1(config-subif)#pppoe auto-configure
- Use the no version to remove this configuration.
- See pppoe auto-configure.

pppoe profile

- Use to assign a profile to a static PPPoE major interface. The profile configuration is used to dynamically configure an upper bridged Ethernet, IP, PPP, or PPPoE interface.
- Specify a profile name with up to 80 alphanumeric characters.
- The default encapsulation type, any, applies to any autoconfigured encapsulation that does not have a specific profile assignment.
- Examples
  host1(config-subif)#pppoe profile pppoeProfile4 host1(config-if)#pppoe profile any anyProfile
- Use the no version to remove the profile assignment from the interface.
- See pppoe profile.

svlan ethertype

- Use to assign an Ethertype value for the S-VLAN subinterface.
- Choose one of the following Ethertype values:
  - 8100—Specifies Ethertype value 0x8100, as defined in IEEE Standard 802.1q
  - 9100—Specifies Ethertype value 0x9100, which is the default
  - 9200—Specifies Ethertype value 0x9200
- Use an Ethertype value that matches the Ethertype value set on the customer premises equipment (CPE) to which your router connects.
- Example
  host1(config-if)#svlan ethertype 8100
- Use the no version to restore the default value, 9100.
- See svlan ethertype.

svlan id

- Use to assign S-VLAN IDs and VLAN IDs to VLAN subinterfaces.
- Use S-VLAN ID and VLAN ID numbers that are in the range 0–4095 and that are unique within the Ethernet interface.
- Issue the svlan id command before any upper bindings are made, such as IP or PPPoE.
- Example
  host1(config-if)#svlan id 4 255
- There is no no version.
- See svlan id.

vlan id

- Use to specify the VLAN ID.
- Use a VLAN ID that is in the range 0–4095 and is unique within the Ethernet interface.
- Issue the vlan id command before any upper bindings are made, such as IP or PPPoE.
- Use the optional keyword untagged to specify that frames be sent untagged. The keyword is valid only for VLAN ID 0, which can receive tagged frames but sends out untagged frames.
- Example
  host1(config-if)#vlan id 400
- There is no no version.
- See vlan id.

## Configuring Encapsulation Type Lockout for PPPoE Clients

In configurations with dynamic PPPoE subinterfaces over static PPPoE major interfaces, you can configure dynamic encapsulation type lockout for the PPPoE clients associated with a dynamic PPPoE subinterface column. Using this feature enables you to temporarily prevent the static PPPoE major interface from autodetecting, accepting, and creating dynamic PPPoE subinterface columns for a configurable time period.

By default, encapsulation type lockout is disabled for PPPoE clients. To configure a lockout time range for the PPPoE clients associated with the dynamic PPPoE subinterface columns on the PPPoE major interface, use the pppoe auto-configure command with the lockout-time keyword. You can also use the show pppoe interface lockout-time command to display detailed information about the current lockout condition for each PPPoE client, and the pppoe clear lockout interface command to clear (reset) the lockout condition for an individual PPPoE client.

For information about the working of the dynamic encapsulation type lockout feature for PPPoE sessions that contain the IWF-Session DSL Forum VSA (26-254) in PADR packets, see Encapsulation Type Lockout Based on DSL Forum VSAs for IWF PPPoE Sessions.

For illustrations of the interface stacking in dynamic PPPoE over static PPPoE configurations, see Figure 49, Figure 50, Figure 51, and Figure 53.

### Differences from Lockout Configuration for PPPoE over Static ATM

Table 29 lists the important differences between how encapsulation type lockout works for dynamic PPPoE over static PPPoE configurations and how lockout works for dynamic PPPoE over static ATM 1483 configurations.

Table 29: Differences in Lockout Operation for Dynamic PPPoE Configurations

Dynamic PPPoE over Static PPPoE | Dynamic PPPoE over Static ATM 1483
--- | ---
Encapsulation type lockout is disabled by default. | Encapsulation type lockout is enabled by default with a lockout time range of 1–300 seconds.
You must explicitly configure encapsulation type lockout for PPPoE clients with the pppoe auto-configure command. | PPPoE clients automatically inherit their lockout setting from the lockout parameters configured for the underlying static ATM 1483 subinterface with the auto-configure command. Currently, the dynamic PPPoE interface layer must be configured directly above the static ATM 1483 interface layer to support inheritance of lockout parameters. For an illustration of dynamic PPPoE over static ATM 1483 interface stacking, see Figure 48.

For more information about the benefits and operation of dynamic encapsulation type lockout, see Encapsulation Type Lockout. In particular, see Guidelines for Configuring Encapsulation Type Lockout for PPPoE sessions for information about the rules that apply when you configure the lockout time. These rules are common to both dynamic PPPoE over static PPPoE configurations and dynamic PPPoE over static ATM 1483 configurations.

### Configuration Tasks

Configuring dynamic encapsulation type lockout for PPPoE clients includes the following tasks:

- Configuring and verifying lockout for PPPoE clients
- Clearing the lockout condition for a specific PPPoE client

### Configuring and Verifying Lockout for PPPoE Clients

To configure and verify encapsulation type lockout for a PPPoE client:

1. Configure the underlying physical interface.

   For example, the following commands configure a static ATM 1483 subinterface and corresponding ATM PVC.

   host1(config)#interface atm 3/0 host1(config-if)#interface atm 3/0.101 host1(config-subif)#atm pvc 10 10 20 aal5snap
2. Create a static PPPoE major interface.
   host1(config-subif)#encapsulation pppoe
3. Configure the PPPoE major interface to detect and accept dynamic PPPoE subinterfaces. Use the lockout-time keyword to configure a nondefault lockout time range for the PPPoE clients associated with the dynamic PPPoE subinterface column.

   For example, the following command configures a lockout time in the range 5–60 seconds for the PPPoE clients associated with the dynamic PPPoE subinterface column on the PPPoE major interface.

   host1(config-subif)#pppoe auto-configure lockout-time 5 60
4. Assign a profile to the PPPoE major interface.
   host1(config-subif)#pppoe profile pppoeLockoutProfile

   For information about creating and using profiles, see Configuring a Dynamic Interface from a Profile .

5. (Optional) Verify the lockout configuration by using either of the following commands.
   - To display summary information about the lockout configuration, use the show pppoe interface command. (The following example shows only the portion of the command display relevant to the PPPoE lockout configuration.)

         host1#show pppoe interface atm 3/0.101
         PPPoE interface ATM 3/0.101 is operStatusUp (dynamic)
         . . .

         Lockout Configuration (seconds): Min 5, Max 60
          Total clients in active lockouts: 0
          Total clients in lockout grace period: 0

   - To display detailed information about the current lockout condition for each PPPoE client associated with a specific source media access control (MAC) address, use the show pppoe interface lockout-time command.

     This command displays multiple entries for the same MAC address if multiple IWF sessions contain the same MAC address. In the following example, more than one entry for the same PPPoE client MAC address, 0090.1a42.527c, is displayed under the Client Address column head. This method of display occurs because the MAC address in the Client Address field denotes the MAC address of the DSLAM device at which multiplexing functions are performed and not the address of the originating PPPoE client (access loop) for PPPoE sessions that contain the IWF-Session DSL Forum VSA (26-154).

         host1#show pppoe interface atm 12/1/1.1.1 lockout-time
         PPPoE interface atm 12/1/1.1
         Lockout Configuration (seconds): Min 90, Max 120
          Total clients in active lockout: 1
          Total clients in lockout grace period: 0
         Client Address Current Elapsed Next
         -------------- ------- ------- ----
         0090.1a42.527c     120      30  120
         0090.1a42.527c       0       0   90

     For a description of the fields in the command display, see show pppoe interface and show pppoe interface lockout-time.

pppoe auto-configure lockout-time

- Use to specify the lockout time range for the PPPoE clients associated with the dynamic PPPoE subinterface column on the static PPPoE major interface.
- Dynamic encapsulation type lockout is disabled for PPPoE clients by default.
- Configuring dynamic encapsulation type lockout temporarily prevents the static PPPoE major interface from detecting, accepting, and creating dynamic PPPoE subinterface columns until the lockout time expires.
- Use the lockout-time keyword to set the minimum lockout time and maximum lockout time, each of which can be in the range 1–86400 seconds (24 hours).
- Use the none keyword to disable lockout for the PPPoE clients associated with the dynamic PPPoE subinterface column on the static PPPoE major interface.
- For information about the rules that apply when you configure the lockout time for dynamic encapsulation type lockout, see Guidelines for Configuring Encapsulation Type Lockout for PPPoE sessions.
- Example 1—Enables dynamic creation of PPPoE subinterfaces on the static PPPoE major interface using a nondefault lockout time range, 10–120 seconds
  host1(config-subif)#pppoe auto-configure lockout-time 10 120
- Example 2—Disables dynamic encapsulation type lockout for any PPPoE clients associated with the dynamic PPPoE subinterface column on the static PPPoE major interface
  host1(config-subif)#pppoe auto-configure lockout-time none
- Example 3—Terminates dynamic creation of PPPoE subinterfaces on the static PPPoE major interface and, by extension, disables dynamic encapsulation type lockout for this interface
  host1(config-subif)#no pppoe auto-configure
- Use the no pppoe auto-configure command to terminate dynamic creation of PPPoE subinterfaces on the static PPPoE major interface.
- See pppoe auto-configure.

### Clearing the Lockout Condition for a PPPoE Client

You can use the pppoe clear lockout interface command to clear the lockout condition for an individual PPPoE client associated with a dynamic PPPoE subinterface column on a static PPPoE major interface. To identify the PPPoE client, you must specify its source MAC address.

For information about the working of the dynamic encapsulation type lockout feature for PPPoE sessions that contain the IWF-Session DSL Forum VSA (26-254) in PADR packets, see Encapsulation Type Lockout Based on DSL Forum VSAs for IWF PPPoE Sessions.

| Note: Issuing the pppoe clear lockout interface command resets the current lockout condition for the specified PPPoE client, but does not disable dynamic encapsulation type lockout for that PPPoE client.

To clear the current lockout condition for a PPPoE client:

1. Display the source MAC address assigned to the PPPoE client by issuing one of the following show commands:
   - To display the source MAC address when there is no available PPPoE session in progress, use the show pppoe interface lockout-time command.

     This command displays multiple entries for the same MAC address if multiple IWF sessions contain the same MAC address. In the following example, more than one entry for the same PPPoE client MAC address, 0090.1a42.527c, is displayed under the Client Address column head. This method of display occurs because the MAC address in the Client Address field denotes the MAC address of the DSLAM device at which multiplexing functions are performed and not the address of the originating PPPoE client (access loop) for PPPoE sessions that contain the IWF-Session DSL Forum VSA (26-154).

         host1#show pppoe interface atm 12/1/1.1.1 lockout-time
         PPPoE interface atm 12/1/1.1
         Lockout Configuration (seconds): Min 90, Max 120
          Total clients in active lockout: 1
          Total clients in lockout grace period: 0
         Client Address Current Elapsed Next
         -------------- ------- ------- ----
         0090.1a42.527c     120      30  120
         0090.1a42.527c       0       0   90

   - To display the source MAC address when a subscriber is connected to the router through an available PPPoE session, use either the show pppoe interface lockout-time command or the show pppoe subinterface full command. (The following example shows only the portion of the command display relevant to the source MAC address.)

         host1#show pppoe subinterface full
         ...
             PPPoE subinterface ATM 3/0.101 has source MAC address 0090.1a10.165e
         ...

   For a description of the fields in the command display, see show pppoe interface lockout-time and show pppoe subinterface.

2. Clear the current lockout condition for the PPPoE client associated with the specified source MAC address on the static PPPoE major interface.
   host1#pppoe clear lockout interface atm 3/0.101 0090.1a10.165e

   If the specified PPPoE client is undergoing active lockout or is in a lockout grace period, issuing the pppoe clear lockout interface command causes the router to reset the current lockout condition and start the next lockout interval at the minimum configured lockout time.

   The lockout grace period occurs when the time between lockout events is greater than either 15 minutes or the maximum lockout time. When a PPPoE client is in a lockout grace period, the router resets the number of consecutive lockout events to 1. (For more information, see Guidelines for Configuring Encapsulation Type Lockout for PPPoE sessions.)

pppoe clear lockout interface

- Use to clear the lockout condition for the PPPoE client associated with the specified source MAC address.
- For PPPoE clients undergoing active lockout or in a lockout grace period, issuing the pppoe clear lockout interface command causes the router to reset the current lockout condition and start the next lockout interval at the minimum configured lockout time.
- For PPPoE sessions that contain the IWF-Session DSL Forum VSA (26-254) in the PPPoE active discovery request (PADR) packets, the encapsulation lockout condition is cleared for all IWF PPPoE sessions whose source MAC address matches the MAC address specified in the command. In lower-numbered releases, issuing this command cleared the lockout condition only for one PPPoE session associated with a specific MAC address.
- You must specify the following:
  - interfaceType—One of the following interface types listed in Interface Types and Specifiers in JunosE Command Reference Guide:
    - atm
    - fastEthernet
    - gigabitEthernet
    - lag
    - tenGigabitEthernet
  - interfaceSpecifier—Particular interface; format varies according to interface type; see Interface Types and Specifiers in JunosE Command Reference Guide for information
  - macAddress—Source MAC address of the PPPoE client, specified as a dotted triple of four-digit hexadecimal numbers
- Example
  host1#pppoe clear lockout interface gigabitEthernet 2/1.1 1011.22c2.333d
- There is no no version.
- See pppoe clear lockout interface.