21.03.2013 Views

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Junos ®<br />

<strong>OS</strong> 12.3 <strong>Ethernet</strong> <strong>Interfaces</strong> <strong>Configuration</strong> Guide<br />

• <strong>Junos®</strong> <strong>OS</strong> <strong>Ethernet</strong> <strong>Interfaces</strong><br />

Configuring the Action Taken When the Client Request Includes an Empty Service<br />

Name Tag<br />

414<br />

Related<br />

Documentation<br />

You can configure the action taken by the PPPoE underlying interface when it receives<br />

a PADI packet that includes a zero-length (empty) service name tag. The empty service<br />

is present by default in every PPPoE service name table.<br />

To indicate that it can service the client request, the interface returns a PADO packet in<br />

response to the PADI packet. By default, the interface immediately responds to the<br />

request; this is the terminate action. Alternatively, you can configure the drop action to<br />

ignore (drop) the PADI packet, or the delay action to set a delay between receipt of the<br />

PADI packet and transmission of the PADO packet.<br />

(Optional) To configure the action taken for the empty service in response to a PADI<br />

packet from a PPPoE client:<br />

• Specify the action.<br />

[edit protocols pppoe service-name-tables table1]<br />

user@host# set service empty drop<br />

You can also accomplish the following optional tasks when you configure the empty<br />

service:<br />

• Specify the agent circuit identifier (ACI) and agent remote identifier (ARI) information<br />

to determines the action taken by the PPPoE underlying interface when it receives a<br />

PADI packet with matching ACI/ARI information.<br />

• Specify a dynamic profile and routing instance with which the router instantiates a<br />

dynamic PPPoE subscriber interface.<br />

• Limit the number of active PPPoE sessions that the router can establish with the empty<br />

•<br />

service.<br />

Understanding PPPoE Service Name Tables on page 398<br />

• Configuring PPPoE Service Name Tables on page 412<br />

• Assigning an ACI/ARI Pair to a Service Name and Configuring the Action Taken When<br />

the Client Request Includes ACI/ARI Information on page 417<br />

• Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair<br />

for Dynamic PPPoE Interface Creation<br />

• Limiting the Number of Active PPPoE Sessions Established with a Specified Service<br />

Name on page 418<br />

• PPPoE Overview on page 394<br />

• <strong>Junos®</strong> <strong>OS</strong> <strong>Ethernet</strong> <strong>Interfaces</strong><br />

Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!