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.

You can also associate a PPPoE dynamic profile, routing instance, and static PPPoE<br />

interface with an ACI/ARI pair.<br />

Dynamic Profiles and Routing Instances in PPPoE Service Name Tables<br />

You can associate a previously configured PPPoE dynamic profile with a named service,<br />

empty service, or any service in the PPPoE service name table, or with an ACI/ARI pair<br />

defined for these services. The router uses the attributes defined in the profile to<br />

instantiate a dynamic PPPoE subscriber interface based on the service name, ACI, and<br />

ARI information provided by the PPPoE client during PPPoE negotiation. The dynamic<br />

profile configured for a service entry or ACI/ARI pair in a PPPoE service name table<br />

overrides the dynamic profile assigned to the PPPoE underlying interface on which the<br />

dynamic PPPoE interface is created.<br />

To specify the routing instance in which to instantiate the dynamic PPPoE interface, you<br />

can associate a previously configured routing instance with a named service, empty<br />

service, or any service in the PPPoE service name table, or with an ACI/ARI pair defined<br />

for these services. Like dynamic profiles configured for service entries or ACI/ARI pairs,<br />

the routing instance configured for the PPPoE service name table overrides the routing<br />

instance assigned to the PPPoE underlying interface.<br />

For information about configuring the PPPoE service name table to create a dynamic<br />

PPPoE subscriber interface, see Assigning a Dynamic Profile and Routing Instance to a<br />

Service Name or ACI/ARI Pair for Dynamic PPPoE Interface Creation in the Junos <strong>OS</strong><br />

Subscriber Management, Release 12.3.<br />

Maximum Sessions Limit in PPPoE Service Name Tables<br />

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

To limit the number of PPPoE client sessions that can use a particular service entry in<br />

the PPPoE service name table, you can configure the maximum number of active PPPoE<br />

sessions using either dynamically-created or statically-created PPPoE interfaces that<br />

the router can establish with a particular named service, empty service, or any service.<br />

(You cannot configure the maximum sessions limit for an ACI/ARI pair.) The maximum<br />

sessions limit must be in the range 1 through the platform-specific maximum PPPoE<br />

sessions supported for your routing platform. The router maintains a count of active<br />

PPPoE sessions for each service entry to determine when the maximum sessions limit<br />

has been reached.<br />

The router uses the maximum sessions value for a service entry in the PPPoE service<br />

name table in conjunction with both of the following:<br />

• The maximum sessions (max-sessions) value configured for the PPPoE underlying<br />

interface<br />

• The maximum number of PPPoE sessions supported on your routing platform<br />

If your configuration exceeds either of these maximum session limits, the router cannot<br />

establish the PPPoE session.<br />

Chapter 30: Configuring Point-to-Point Protocol over <strong>Ethernet</strong><br />

401

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

Saved successfully!

Ooh no, something went wrong!