Dynamic PPPoE Interfaces over PPPoE Static Interfaces

Configuring Dynamic PPPoE over Static PPPoE with ATM Interface Columns

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

Figure 1: 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, the virtual path identifier, the virtual channel identifier, and the encapsulation type. For more information, see Creating a PVC on an ATM 1483 Subinterface.
   host1(config-subif)#atm pvc 10 10 22 aal5snap

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

   host1(config-subif)#atm pvc 10 10 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

   The default encapsulation type, any, applies to any autoconfigured encapsulation that does not have a specific profile assignment.

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. For more information, see Monitoring Status or Summary Information for ATM Subinterfaces.

   host1#show atm subinterface atm 5/0.1

                                  Circuit                           Interface
   Interface ATM-Prot VCD VPI VCI  Type   Encap MTU      Status       Type
   --------- -------- --- --- --- ------- ----- ---- -------------- ---------
   ATM 5/0.1 RFC-1483  10  10  22 PVC     SNAP  9180 lowerLayerDown Static
   
   Auto configure status         : static
   Auto configure interface(s)   : none
   Detected 1483 encapsulation   : none
   Detected dynamic interface    : none
   Interface types in lockout    : none
   
   Assigned profile (IP)         : none assigned
   Assigned profile (BridgedEnet): none assigned
   Assigned profile (PPP)        : none assigned
   Assigned profile (PPPoE)      : none assigned
   Assigned profile (any)        : none assigned
   
   SNMP trap link-status: disabled
   Assigned VC Class: none assigned
   
   InPackets:                0
   InBytes:                  0
   OutPackets:               0
   OutBytes:                 0
   InErrors:                 0
   OutErrors:                0
   InPacketDiscards:         0
   InPacketsUnknownProtocol: 0
   OutDiscards:              0
   InPolicedPackets:         0
   OutPolicedPackets:        0
   1 interface(s) found

   host1#show pppoe interface atm 5/0.1

   PPPoE interface ATM 5/0.1 is operStatusLowerLayerDown
       PPPoE interface ATM 5/0.1 has max sessions = 8000
       PPPoE interface ATM 5/0.1 MTU 1494
       PPPoE interface ATM 5/0.1 has no acName set
       PPPoE interface ATM 5/0.1 autoconfigured subinterfaces
       PPPoE interface ATM 5/0.1 has 0 active connections,
           out of 0 configured subinterfaces
   Assigned profile (any)        : pppoeProfile1
   
   PPPoE Statistics
     Counters:
       PADI received       0
       PADI transmitted    0
       PADO received       0
       PADO transmitted    0
       PADR received       0
       PADR transmitted    0
       PADS received       0
       PADS transmitted    0
       PADT received       0
       PADT transmitted    0
       PADM received       0
       PADM transmitted    0
       PADN received       0
       PADN transmitted    0
     PAD packets received        0
     PAD packets transmitted     0
   
     Invalid PAD Packets:
       Invalid Version           0
       Invalid PAD Code          0
       Invalid PAD Tags          0
       Invalid PAD Tag length    0
       Invalid PAD Type          0
       Invalid PADI Session      0
       Invalid PADR Session      0
       Invalid PAD packet length 0
       Invalid PAD packets       0
      Total Invalid PAD packets  0
      Ingress Policed Packets 0
      Egress Policed Packets 0
   
     Insufficient Resources 0

Configuring Dynamic PPPoE over Static PPPoE with Ethernet Interface Columns

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

Figure 2: 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

   The default encapsulation type, any, applies to any autoconfigured encapsulation that does not have a specific profile assignment.

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 3 shows dynamic PPPoE subinterface columns and illustrates an alternative method for PPPoE to support multiple IP sessions over each VLAN.

Figure 3: 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

   The default encapsulation type, any, applies to any autoconfigured encapsulation that does not have a specific profile assignment.

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

Configuring IPv4 and IPv6 Interface Columns over Static and Dynamic PPPoE

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

Figure 4: 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 1host1(config-if)#ipv6 address 2000::1/64host1(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 ipv4Ipv6Profilehost1(config-profile)#ip virtual-router ppphost1(config-profile)#ip unnumbered loopback 1host1(config-profile)#ipv6 virtual-router ppphost1(config-profile)#ipv6 unnumbered loopback 1host1(config-profile)#ipv6 nd other-config-flaghost1(config-profile)#ipv6 nd ra-interval 10host1(config-profile)#ppp authentication chaphost1(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

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

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

Figure 5: 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

   The default encapsulation type, any, applies to any autoconfigured encapsulation that does not have a specific profile assignment.

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

S-VLAN Oversubscription for Dynamic PPPoE Interfaces over Static PPPoE Overview

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 input/output adapter (IOA) with PPPoE major interfaces stacked over them is greater than the maximum number of dynamic PPPoE subinterfaces. The maximum number of Point-to-Point Protocol (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.

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.

Encapsulation Type Lockout for PPPoE Clients Overview

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 interworking function (IWF)-Session digital subscriber line (DSL) Forum vendor-specific attribute (VSA) (26-254) in the PPPoE active discovery request (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 the figures provided in Configuring Dynamic PPPoE over Static PPPoE with ATM Interface Columns, Configuring Dynamic PPPoE over Static PPPoE with Ethernet Interface Columns, Configuring Dynamic PPPoE over Static PPPoE with Ethernet and VLAN Interface Columns, and Configuring Dynamic PPPoE over Static PPPoE with Ethernet and S-VLAN Interface Columns.

Differences from Lockout Configuration for PPPoE over Static ATM

Table 1 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.

For more information about the benefits and operation of dynamic encapsulation type lockout, see Dynamic 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.

Configuring Encapsulation Type Lockout for PPPoE Clients

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 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. For more information about the atm pvc command, see Creating a PVC on an ATM 1483 Subinterface

   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

   The default encapsulation type, any, applies to any autoconfigured encapsulation that does not have a specific profile assignment.

   For information about creating and using profiles, see Dynamic Interface Configuration Using a Profile and Configuring Profile Characteristics .

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 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 Monitoring Summary Information about the Encapsulation Type Lockout for PPPoE Clients and Monitoring Detailed Information about the Current Encapsulation Type Lockout Condition for PPPoE Clients.

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 Monitoring Detailed Information about the Current Encapsulation Type Lockout Condition for PPPoE Clients and Monitoring the Source MAC Address of a PPPoE Client.

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.)