Juniper JUNOS 10.1 - CONFIGURATION GUIDE 1-2010 Configuration Manual page 898

JUNOS 10.1 Network Interfaces Configuration Guide
3.
4.
Components of PPPoE Service Name Tables
The following information describes the components of a PPPoE service name table
and how you can use them in a subscriber network:
828
Understanding PPPoE Service Name Tables
The PPPoE client sends a unicast PPPoE Active Discovery Request (PADR) packet
to the AC to which it wants to connect, based on the responses received in the
PADO packets.
The selected AC sends a PPPoE Active Discovery Session (PADS) packet to
establish the PPPoE connection with the client.
Service name tag—Specifies the PPPoE client services that an AC can support.
For example, you might configure service name tags associated with different
subscribers who log in to the PPPoE server, such as user1-service or user2-service.
Each PPPoE service name table can include a maximum of 16 service name
tags. A service name tag is associated with the
Empty service name tag—A service tag of zero length that represents an
unspecified service. Each PPPoE service name table includes one empty service
name tag. The empty service name tag is associated with the
by default, and cannot be configured with agent circuit identifier/agent remote
identifier (ACI/ARI) pairs.
Action—Specifies the action taken by the underlying PPPoE interface assigned
to the PPPoE service name table upon receipt of a PADI packet from the client
containing a particular service request. You can configure one of the following
actions for the associated service name tag, empty service name tag, or ACI/ARI
pair in the PPPoE service name table on the router:
terminate —(Default) Directs the router to immediately respond to the PADI
packet by sending the client a PADO packet containing the name of the AC
that can service the request. Service name tags, empty service name tags,
and ACI/ARI pairs are associated with the
Configuring the terminate
tightly control which PPPoE clients can access and receive services from a
particular PPPoE server.
—Number of seconds that the PPPoE underlying interface waits after
delay
receiving a PADI packet from the client before sending a PADO packet in
response. In networks with mesh topologies, you might want to designate
a primary PPPoE server and a backup PPPoE server for handling a particular
service request. In such a scenario, you can configure a delay for the
associated service name tag on the backup PPPoE server to allow sufficient
time for the primary PPPoE server to respond to the client with a PADO
packet. If the primary server does not send the PADO packet within the
delay period configured on the backup server, then the backup server sends
the PADO packet after the delay period expires.
—Directs the router to drop (ignore) a PADI packet containing the
drop
specified service name tag when received from a PPPoE client, which
effectively denies the client s request to provide the associated service. To
prohibit the router from responding to PADI packets that contain empty
service name tags, you can configure the
name tag. You can also use the
terminate
terminate
action for a service name tag enables you to more
drop action for the empty service
action in combination with ACI/ARI
drop
action by default.
action
terminate
action by default.