Related Documentation
- J, M, MX, T Series
- PPPoE Overview
- M, MX Series
- Understanding PPPoE Service Name Tables
- Configuring PPPoE Service Name Tables
- Assigning an ACI/ARI Pair to a Service Name and Configuring the Action Taken When the Client Request Includes ACI/ARI Information
- Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair for Dynamic PPPoE Interface Creation
- Limiting the Number of Active PPPoE Sessions Established with a Specified Service Name
- Additional Information
- Ethernet Interfaces
Configuring the Action Taken for the Any Service
The any service acts as a default service for service name tags transmitted by the client that do not match any of the service entries configured in the PPPoE service name table on the router. By configuring an action for the any service, you specify the action taken by the PPPoE underlying interface when it receives a PADI control packet from a client that includes a non-empty service name tag that does not match any of the named service entries or empty service entry in the PPPoE service name table.
Each PPPoE service name table includes one any service entry associated by default with the drop action. The drop action ignores a PADI packet containing a nonmatching service name tag. Alternatively, you can configure the terminate action to immediately respond to the PADI packet with a PADO packet, or the delay action to specify a delay between receipt of the PADI packet and transmission of the PADO packet.
To configure the action taken for the any service in response to a PADI packet from a PPPoE client:
- Specify the action.
You can also accomplish the following optional tasks when you configure the any service:
- Specify the agent circuit identifier (ACI) and agent remote identifier (ARI) information to determine the action taken by the PPPoE underlying interface when it receives a PADI packet with matching ACI/ARI information.
- Specify a dynamic profile and routing instance with which the router instantiates a dynamic PPPoE subscriber interface.
- Limit the number of active PPPoE sessions that the router can establish with the any service.
Related Documentation
- J, M, MX, T Series
- PPPoE Overview
- M, MX Series
- Understanding PPPoE Service Name Tables
- Configuring PPPoE Service Name Tables
- Assigning an ACI/ARI Pair to a Service Name and Configuring the Action Taken When the Client Request Includes ACI/ARI Information
- Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair for Dynamic PPPoE Interface Creation
- Limiting the Number of Active PPPoE Sessions Established with a Specified Service Name
- Additional Information
- Ethernet Interfaces
Published: 2013-08-01
Related Documentation
- J, M, MX, T Series
- PPPoE Overview
- M, MX Series
- Understanding PPPoE Service Name Tables
- Configuring PPPoE Service Name Tables
- Assigning an ACI/ARI Pair to a Service Name and Configuring the Action Taken When the Client Request Includes ACI/ARI Information
- Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair for Dynamic PPPoE Interface Creation
- Limiting the Number of Active PPPoE Sessions Established with a Specified Service Name
- Additional Information
- Ethernet Interfaces
