[Contents] [Prev] [Next] [Index] [Report an Error]

# Configuring PPPoE Service Name Tables

To configure PPPoE service name tables on the router:

1. Create the PPPoE service name table.
2. (Optional) Add entries to populate the PPPoE service name table.

   You can:

   - Configure specific service names to represent custom values.
   - Specify a nondefault action for the empty service name entry.
   - Specify a nondefault action for the unknown service name entry.
3. Enable the PPPoE service name table for use with a static or dynamic interface.

The following sections describe how to perform these tasks.

## Creating and Populating PPPoE Service Name Tables

To create and populate a PPPoE service name table on the router:

1. From Global Configuration mode, create a PPPoE service name table by assigning it a name.
   `
   host1(config)#pppoe-service-name-table myServiceTable1
   `

   This command accesses PPPoE Service Name Table Configuration mode and builds a default PPPoE service name table named myServiceTable1. The table contains two entries: an empty service name entry associated with the default action, terminate; and an unknown service name entry associated with the default action, drop as shown in Table 17. This table directs the router to respond to all PADI requests containing an empty service name tag; and denies requests that contain a service name tag that has not been configured in the service name table.

   Table 17: Default PPPoE Service Name Table

   Service Name | Action
   --- | ---
   “ ” | Terminate
   unknown-service-name | Drop

2. (Optional) From PPPoE Service Name Table Configuration mode, create entries to populate the PPPoE service name table.

   You can configure up to 16 specific service name entries per table, in addition to the empty and unknown service name tags.

   `
   host1(config-pppoe-service-name-table)#service myISPService action drop
   host1(config-pppoe-service-name-table)#service myQOSClass1 action terminate
   host1(config-pppoe-service-name-table)#service myQOSClass2 action drop
   host1(config-pppoe-service-name-table)#service myQOSClass3
   host1(config-pppoe-service-name-table)#service empty-service-name action drop
   host1(config-pppoe-service-name-table)#service unknown-service-name action terminate
   `

   These commands build the PPPoE service name table shown in Table 18. This table directs the router to send a PADO packet in response to all PADI requests containing the myQOSClass1, myQOSClass3, empty service name tags, and unknown service name tag. The router is directed to drop all PADI requests containing the myISPService or myQOSClass2 or the empty service name tags.

   Table 18: PPPoE Service Name Table with Entries

   Service Name | Action
   --- | ---
   myISPService | Drop
   myQOSClass1 | Terminate
   myQOSClass2 | Drop
   myQOSClass3 | Terminate
   “ ” | Drop
   unknown-service-name | Terminate

3. Exit PPPoE Service Name Table Configuration mode.
   `
   host1(config-pppoe-service-name-table)#exit
   `
4. (Optional) Use the appropriate show command to verify the creation of the PPPoE service name table and entries.
   `
   host1(config)#show pppoe-service-name-table name myServiceTable1
   `
5. (Optional) Repeat Steps 1 through 4 to configure additional PPPoE service name tables on the router.

pppoe-service-name-table

- Use from Global Configuration mode to create a PPPoE service name table.
- You can create a maximum of 16 PPPoE service name tables per E Series router.
- Specify a table name of up to 31 alphanumeric characters.
- This command accesses PPPoE Service Name Table Configuration mode, which enables you to configure entries for the PPPoE service name table.
- Example
  `
  host1(config)#pppoe-service-name-table myServiceTable1
  `
- Use the no version to remove the specified PPPoE service name table from the router.
- See pppoe-service-name-table.

service

- Use to add service name tags to the PPPoE service name table.
- Each PPPoE service name table includes one empty service name tag, one unknown service name tag, and can optionally include up to 16 additional custom service name tags. An empty service name tag is used to represent any service. An unknown service name tag is used to represent a service that has not been configured in the PPPoE service name table. A custom service name tag is used to represent a specific service.
- To modify the action associated with an empty service entry, use the empty-service-name keyword with the action keyword. This directs the router to drop PADI requests from the PPPoE client. The default action for an empty service name entry is terminate.
- To include a custom service entry, specify a serviceName of up to 31 alphanumeric characters. Use the optional action keyword with the service command for a custom service entry to specify that the router either drop or terminate PADI requests from the PPPoE client. The default action for a custom service entry is terminate.
- To modify the action associated with an unknown service entry, use the unknown-service-name keyword with the action keyword. This directs the router to terminate (allow) PADI requests from the PPPoE client. The default action for an unknown service name entry is drop.

  The default action for the unknown service name entry depends on the configuration of the service name table. If all the services in the service name table are configured to terminate, the default action of the unknown service name tag is drop. If all the services in the service name table are configured to drop, the default action for the unknown service name tag is terminate. If both terminate and drop are configured, the default action for the unknown service name tag is drop.

- Example 1– Includes a custom service entry in the PPPoE service name table. The associated action for this service tag is terminate. This is the default action when you add a custom service entry without using the optional action keyword.
  `
  host1(config-pppoe-service-name-table)#service myISPService
  `
- Example 2 – Includes a custom service entry in the PPPoE service name table. The associated action for this service tag is drop. Use the optional action keyword with the service command to associate an action with the custom service entry.
  `
  host1(config-pppoe-service-name-table)# service myQOSClass2 action drop
  `
- Example 3 – Includes an unknown service name entry in the PPPoE service name table. The associated action for this service tag is terminate. Use the action keyword with the service command to associate an action with the unknown service name entry.
  `
  host1(config-pppoe-service-name-table)# service unknown-service-name action terminate
  `
- Example 4 – Includes an empty service name entry in the PPPoE service name table. The associated action for this service tag is drop. Use the action keyword with the service command to associate an action with the empty service name entry.
  `
  host1(config-pppoe-service-name-table)#service empty-service-name action drop
  `
- Use the no version to remove the custom service name tags from the PPPoE service name table or restore the default action for the empty and unknown service name tags.
- See service.

## Enabling PPPoE Service Name Tables for Use with Static Interfaces

To enable a PPPoE service name table for use with a static interface, assign the service name table to the PPPoE major interface.

### PPPoE over ATM Configurations

To enable a PPPoE service name table for use with a static interface in PPPoE over ATM configurations:

1. Configure an ATM physical interface.
   `
   host1(config)#interface atm 3/0
   `
2. Configure an ATM 1483 subinterface.
   `
   host1(config-if)#interface atm 3/0.1
   `
3. Configure an ATM PVC by specifying the VCD, the VPI, the VCI, and the encapsulation type.
   `
   host1(config-subif)#atm pvc 10 100 22 aal5snap
   `
4. Select PPPoE as the encapsulation method on the interface. This command creates the PPPoE major interface.
   `
   host1(config-subif)#encapsulation pppoe
   `
5. Assign the PPPoE service name table to the PPPoE major interface.
   `
   host1(config-subif)#pppoe service-name-table myServiceTable1
   `

atm pvc

- Use to configure a PVC on an ATM interface.
- For details about specifying the mandatory VCD, VPI, VCI, and encapsulation type parameters, see atm pvc.
- Example
  `
  host1(config-if)#atm pvc 10 100 22 aal5snap
  `
- Use the no version to remove the specified PVC.
- See atm pvc.

encapsulation pppoe

- Use to specify PPPoE as the encapsulation method for the interface.
- This command creates a PPPoE major interface.
- Example
  `
  host1(config-subif)#encapsulation pppoe
  `
- Use the no version to disable PPPoE on an interface.
- See encapsulation pppoe.

interface atm

- Use to configure an ATM interface.
- For information about specifying the ATM interface or subinterface, see interface atm.
- Examples
  `
  host1(config)#interface atm 3/1.19
  host1(config)#interface atm 3/0/1.19
  `
- Use the no version to remove the interface or subinterface.
- See interface atm.

pppoe service-name-table

- Use from Subinterface Configuration mode to assign a PPPoE service name table to a PPPoE major interface for use by a static ATM 1483 subinterface.
- Specify the name of the PPPoE service name table configured with the pppoe-service-name-table command from Global Configuration mode.
- Example
  `
  host1(config-subif)#pppoe service-name-table myServiceTable1
  `
- Use the no version to remove the PPPoE service name table assignment.
- See pppoe service-name-table.

### PPPoE over Ethernet Configurations

To enable a PPPoE service name table for use with a static interface in PPPoE over Ethernet configurations:

1. Configure a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet physical interface.
   `
   host1(config)#interface fastEthernet 4/1
   `
2. Select PPPoE as the encapsulation method on the interface. This command creates the PPPoE major interface.
   `
   host1(config-if)#pppoe
   `
3. Assign the PPPoE service name table to the PPPoE major interface.
   `
   host1(config-if)#pppoe service-name-table myServiceTable1
   `

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 subinterface. 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 fastEthernet.

interface gigabitEthernet

interface tenGigabitEthernet

- Use to select a Gigabit Ethernet interface or a 10-Gigabit Ethernet interface.
- For information about specifying the Gigabit Ethernet or 10-Gigabit Ethernet interface or subinterface, see interface gigabitEthernet and interface tenGigabitEthernet on interface tenGigabitEthernet.
- Examples
  `
  host1(config)#interface gigabitEthernet 1/0
  host1(config)#interface gigabitEthernet 4/0/1 6.0.0FRS
  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.

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.

pppoe service-name-table

- Use from Interface Configuration mode to assign a PPPoE service name table to a PPPoE major interface for use by a static Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet interface.
- Specify the name of the PPPoE service name table configured with the pppoe-service-name-table command from Global Configuration mode.
- Example
  `
  host1(config-if)#pppoe service-name-table myServiceTable1
  `
- Use the no version to remove the PPPoE service name table assignment.
- See pppoe service-name-table.

## Enabling PPPoE Service Name Tables for Use with Dynamic Interfaces

To enable a PPPoE service name table for use with a dynamic interface, add the service name table to a profile that is dynamically assigned to the interface.

For complete details, see Configuring a Dynamic Interface from a Profile in Configuring Dynamic Interfaces.

To enable a PPPoE service name table for use with a dynamic interface:

1. Create a profile by assigning it a name.
   `
   host1(config)#profile baseProfile
   `
2. Assign the PPPoE service name table to the profile as a PPPoE characteristic.
   `
   host1(config-profile)#pppoe service-name-table myServiceTable1
   `
3. Exit Profile Configuration mode.
   `
   host1(config-profile)#exit
   `
4. Configure a physical interface.

   On ERX7xx models, ERX14xx models, and the ERX310 router:

   `
   host1(config-if)#interface atm 3/0.1
   `
5. Configure an ATM PVC by specifying the VCD, the VPI, the VCI, and the encapsulation type.
   `
   host1(config-subif)#atm pvc 10 100 22 aal5snap
   `
6. Apply the profile to the interface.
   `
   host1(config-subif)#profile pppoe baseProfile
   `
7. Enable the PPPoE dynamic encapsulation type.
   `
   host1(config-subif)#auto-configure pppoe
   `

atm pvc

- Use to configure a PVC on an ATM interface.
- For details about specifying the mandatory VCD, VPI, VCI, and encapsulation type parameters, see atm pvc.
- Example
  `
  host1(config-if)#atm pvc 10 100 22 aal5snap
  `
- Use the no version to remove the specified PVC.
- See atm pvc.

auto-configure

- Use to configure an ATM 1483 subinterface to support a dynamic interface. Specifies the type(s) of dynamic encapsulation that will be accepted/detected by the ATM 1483 subinterface.
- This command causes the layers above ATM 1483 to become dynamic.
- Select pppoe as the dynamic next upper interface type.
- Example
  `
  host1(config-subif)#auto-configure pppoe
  `
- Use the no version to disable detection of the specified encapsulation.
- See auto-configure.

interface atm

- Use to configure an ATM interface.
- For information about specifying the ATM interface or subinterface, see interface atm.
- Examples
  `
  host1(config)#interface atm 3/0.1
  host1(config)#interface atm 3/0/0.1
  `
- Use the no version to remove the interface or subinterface.
- See interface atm.

pppoe service-name-table

- Use from Profile Configuration mode to assign a PPPoE service name table to a profile for use by the dynamic PPPoE interface column associated with the profile.
- Specify the name of the PPPoE service name table configured with the pppoe-service-name-table command from Global Configuration mode.
- Example
  `
  host1(config-profile)#pppoe service-name-table myServiceTable1
  `
- Use the no version to remove the PPPoE service name table assignment.
- See pppoe service-name-table.

profile

- Use from Global Configuration mode to create a profile name of up to 80 characters.
- Use from Subinterface Configuration mode to assign a profile to an interface. Specify pppoe as the encapsulation type to which the profile applies.
- Examples
  `
  host1(config)#profile myProfile
  host1(config-subif)#profile pppoe myProfile
  `
- Use the no version to remove a profile (from Global Configuration mode) or to remove the profile assignment (from Subinterface Configuration mode).
- See profile.

[Contents] [Prev] [Next] [Index] [Report an Error]