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

Configuring a PPPoE Interface

To configure a PPPoE interface over the underlying Fast Ethernet or ATM interface, perform the following tasks:

Specify the logical Ethernet interface or the logical ATM interface as the underlying interface for the PPPoE session by including the underlying-interface statement:

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number pppoe-options]

[edit logical-routers logical-router-name unit logical-unit-number interfaces interface-name pppoe-options]

The underlying interface can be an ATM, Fast Ethernet, or Gigabit Ethernet logical interface—for example, at-0/0/1.0 (ATM VC), fe-1/0/1.0 (Fast Ethernet interface), or ge-2/0/0 (Gigabit Ethernet interface).

Identify the access concentrator by a unique name by including the access-concentrator statement:

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number pppoe-options]

[edit logical-routers logical-router-name interfaces interface-name unit logical-unit-number pppoe-options]

By default, after a PPPoE session is terminated, the session attempts to reconnect immediately. To specify how many seconds to wait before attempting to reconnect, include the auto-reconnect statement:





auto-reconnect seconds;

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number pppoe-options]

[edit logical-routers logical-router-name interfaces interface-name unit logical-unit-number pppoe-options]

You can configure the reconnection attempt to occur in 0 through 4,294,967,295 seconds after the session terminates.

Identify the type of service provided by the access concentrator—such as the name of the Internet service provider (ISP), class, or quality of service—by including the service-name statement:

You can include this statement at the following hierarchy levels:

[edit interfaces interface-name unit logical-unit-number pppoe-options]

[edit logical-routers logical-router-name interfaces interface-name unit logical-unit-number pppoe-options]
Configure the maximum transmission unit (MTU) of the protocol by including the mtu statement at the [edit interfaces pp0] hierarchy level:
Configure the PPPoE interface address in one of the following ways:

Assign source and destination addresses—for example, 192.168.1.1/32 and 192.168.1.2. To assign the source and destination address, include the address and destination statements:

You can include these statements at the following hierarchy levels:

[edit interfaces pp0.0 family inet]
- [edit logical-routers logical-router-name interfaces pp0.0 family inet]

Derive the source address from a specified interface—for example, the loopback interface, lo0.0—and assign a destination address—for example, 192.168.1.2. The specified interface must include a logical unit number and have a configured IP address. To derive the source address and assign the destination address, include the unnumbered-address and destination statements:

You can include these statements at the following hierarchy levels:

[edit interfaces pp0.0 family inet]
- [edit logical-routers logical-router-name interfaces pp0.0 family inet]

Obtain an IP address by negotiation with the remote end. This method might require the access concentrator to use a RADIUS authentication server. To obtain an IP address from the remote end, include the negotiate-address statement:

You can include this statement at the following hierarchy levels:

[edit interfaces pp0.0 family (inet | inet6 | mpls)]
- [edit logical-routers logical-router-name interfaces pp0.0 family (inet | inet6 | mpls)]
- Configure the maximum transmission unit (MTU) size for the family. Specify a range from 0 through 5012 bytes. To set the MTU, include the mtu statement:

You can include this statement at the following hierarchy levels:

[edit interfaces pp0.0 family (inet | inet6 | mpls)]

[edit logical-routers logical-router-name interfaces pp0.0 family (inet | inet6 | mpls)]
Disable the sending of keepalives on a logical interface by including the no-keepalives statement:

You can include this statement at the following hierarchy levels:

[edit interfaces pp0.0]

[edit logical-routers logical-router-name interfaces pp0 unit logical-unit-number]

Example: Configuring a PPPoE Interface

Configure a PPPoE over ATM-over-ADSL interface:




[edit interfaces]


at-2/0/0 {

encapsulation ethernet-over-atm;




atm-options {

vpi 0;

}







dsl-options {

operating-mode auto;

}







unit 0 {

encapsulation ppp-over-ether-over-atm-llc;

vci 0.120;

}




}



pp0 {

mtu 1492;




unit 0 {




ppp-options {




chap {

access-profile A-ppp-client;

local-name A-at-2/0/0.0;

}




}







pppoe-options {

underlying-interface at-2/0/0;

access-concentrator ispl.com;

service-name "video@ispl.com";

auto-reconnect 100;

}




no-keepalives;




family inet {

negotiate-address;

mtu 100;

}







family inet6 {

negotiate-address;

mtu 200;

}







family mpls {

negotiate-address;

mtu 300;

}




}




}

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