Configuring PPP and PPPoE SYSTEM ADMINISTRATOR GUIDE 64/1543-CRA 119 1170/1 Uen K
Copyright © Ericsson AB 2009–2012. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner. Disclaimer The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document. Trademark List SmartEdge is a registered trademark of Telefonaktiebolaget LM Ericsson.
Contents Contents 1 Overview 1 1.1 PPP-Encapsulated Circuits and Binding 1 1.2 PPP Oversubscription 3 1.3 Single-Stack and Dual-Stack Support 3 1.4 PPP Keepalive Checks 4 1.5 PPPoE Features 6 1.6 Using IPCP Option 144 to Reserve IP Addresses and Install Subnet Routes 6 2 Multilink PPP 9 3 Configuration Tasks 11 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.
Configuring PPP and PPPoE 5.1.2 PPP Configuration with Restricted Dynamic Binding 25 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.
Overview 1 Overview This document describes how to configure, monitor, and troubleshoot Point-to-Point Protocol (PPP) or PPP over Ethernet (PPPoE) on ports, channels, and PPP or PPPoE encapsulated circuits. Note: 1.1 Unless otherwise noted, the SmartEdge® 100 router supports all commands described in this document.
Configuring PPP and PPPoE bind a PPP-encapsulated ATM PVC to an interface on the basis of authentication. If you use the bind subscriber command (in ATM PVC configuration mode), the PPP-encapsulated PVC is brought up unauthenticated, meaning that no authentication data is received from the PPP remote peer. The subscriber name and password are then supplied through the command-line interface (CLI), similar to a PVC with RFC 1483 bridged- or routed-encapsulation.
Overview If the remote PPP device is a router (or the remote segment of any other encapsulation type contains a router), it might be necessary to configure one or more static routes whenever the link is brought up. This is accomplished by one or more Routing Information Protocol (RIP) configuration commands in the subscriber record. 1.
Configuring PPP and PPPoE 1.4 PPP Keepalive Checks Keepalive checks are LCP echo messages sent over PPP sessions in the context to determine if sessions are still active (alive). Normally, when a PPP session is ending, the peer sends the SmartEdge OS an LCP termination request (TERMREQ) message to indicate that it is ending. Keepalive checks detect abnormal disconnects that the SmartEdge OS would not otherwise know about.
Overview Table 1 Time Elapsed Before an Abnormally Terminated Session Is Torn Down PPP Keepalives Without Data Check Enabled Seconds Elapsed Since Previous Step Cumu lative Seconds Elapsed Packets sent by the session 5 5 Abnormal termination 2 Check interval timer expires; LCP echo request sent PPP Keepalives with Data Check Enabled Seconds Elapsed Since Previous Step Cumu lative Seconds Elapsed Packets sent by the session 5 5 7 Abnormal termination 2 7 53 60 Check interval timer 53 ex
Configuring PPP and PPPoE 1.5 PPPoE Features The SmartEdge OS implementation of PPPoE supports the following features: • PPPoE encapsulation on Ethernet ports and ATM and 802.1Q PVCs. • Both IP over Ethernet (IPoE) and PPPoE encapsulation on the same ATM or 802.1Q PVC. You must specify multiprotocol encapsulation (the multi keyword) for these circuits when creating the PVC. • Policing and rate-limiting on a per-PPP-session basis.
Overview Transfer Mode (PPPoA) subscribers are supported for IPv4 or in dual-stack environments. You can configure three possible variations for a subscriber that has a valid /32 netmask configured: • Reserve one IP address for the subscriber and install only the host /32 route. The system rejects IPCP netmask option requests received from the Customer Premise Equipment (CPE) client. This is the default configuration; no additional configuration is required.
Configuring PPP and PPPoE 8 64/1543-CRA 119 1170/1 Uen K | 2012-12-04
Multilink PPP 2 Multilink PPP Multilink PPP (MLPPP) is an extension to PPP that allows a peer to use more than one physical link for communication. When using more than one physical link to connect two peers, you need a mechanism to load balance the connection across the two (or more) links in the bundle. MLPPP is used to fragment the datagrams and send them across the multiple links in the bundle in a way that achieves optimum use of the media.
Configuring PPP and PPPoE subscriber name to determine whether to create a new MLPPP bundle or add the session to a current MLPPP bundle. You can use MLPPP using PPPoE with the following types of Ethernet encapsulation: 0 0 0 Ethernet with untagged traffic 802.1Q PVCs 802.1Q tunnels The system does not allow MLPPP using PPPoE over ATM (PPPoEoA).
Configuration Tasks 3 Configuration Tasks To configure PPP or PPPoE perform the tasks in the following sections. For information about troubleshooting PPP, see the BRAS Troubleshooting Guide. 3.1 Configuring PPP This section describes how to configure PPP global attributes, a PPP-encapsulated port, channel, or ATM PVC, to configure MLPPP on ATM PVCs or for L2TP subscribers, and to configure a subscriber record for PPP. 3.1.
Configuring PPP and PPPoE 3.1.2 Configure a PPP-Encapsulated Port To configure a PPP-encapsulated port, perform the tasks described in Table 3. Table 3 Configure a PPP-Encapsulated Port Step Task Root Command Notes 1. Specify PPP encapsulation for POS port. encapsulation (POS) Create a static binding to an interface. bind interface 2. 3.1.3 Enter this command in port configuration mode. Specify the encapsulation type as ppp.
Configuration Tasks 3.1.4 Configure a Subscriber Record for PPP To configure a circuit for PPP in the subscriber record, perform the tasks described in Table 5. Enter all commands in subscriber configuration mode. Table 5 Configure a Subscriber Record for PPP Step Task Root Command 1. Set the MTU used by PPP for the subscriber circuit. ppp mtu 2. For subscriber sessions on port-limit PPP multilink bundles, limit the number of sessions a subscriber can access simultaneously.
Configuring PPP and PPPoE Table 7 Configure MLPPP on ATM PVCs Step Task Root Command 1. Enable PPP multilink. ppp multilink 2. Specify the endpoint discriminator. ppp our-options mult ilink 3. Optional. Specify priority and fragmentation threshold value for subscriber sessions. ppp multilink lfi 4. Configure one or more PPP-encapsulated ATM PVCs. 3.1.7 Notes For the commands to configure a PPP-encapsulated ATM PVC, see Table 4.
Configuration Tasks Table 8 Configure MLPPP for L2TP Subscribers Step Task Root Command 2. Optional. Specify the endpoint discriminator. ppp our-options mult ilink 3. Optional. Specify priority and fragmentation threshold value for subscriber sessions. ppp multilink lfi 4. Configure one or more L2TP tunnels. 3.1.
Configuring PPP and PPPoE For information about troubleshooting PPPoE, see the BRAS Troubleshooting Guide. Table 9 Configure PPPoE Global and 802.1Q Profile Attributes Task Root Command Notes Configure an option inside PPPoE daemon that terminates the PPPoE session after a PPP session is terminated. pppoe always-send-pad t Enable acceptance and advertisement of any service name tag that is included in a PADI or PADR message.
Configuration Tasks Table 10 Configure an PPPoE-Encapsulated Ethernet Port Step Task Root Command 1. Encapsulate the Ethernet encapsulation port. (POS) 2. Bind the port with one of the following tasks: Notes Specify the encapsulation type as pppoe. Create an unrestricted dynamic binding. bind authenticati on You must specify the context to create a restricted dynamic binding. Create a restricted dynamic binding.
Configuring PPP and PPPoE Table 12 Configure a PPPoE-Encapsulated 802.1Q PVC Root Comman d Step Task 1. Create a PPPoE-enca psulated 802.1Q PVC and access dot1q PVC configuration mode. 2. dot1q pvc Notes Enter this command in port configuration mode. Specify the encapsulation type as pppoe. Bind the 802.1Q PVC with one of the following tasks: Create an unrestricted dynamic binding. bind authenticati on Create a restricted dynamic binding.
Configuration Tasks 3.2.6 Configure a PPPoE-Encapsulated Child Circuit on an 802.1Q PVC To configure a child circuit on an 802.1Q PVC for PPPoE, perform the tasks described in Table 14. Table 14 Configure a PPPoE-Encapsulated Child Circuit on an 802.1Q PVC Step Task Root Command 1. Create the parent 802.1Q dot1q pvc PVC and access dot1q PVC configuration mode. Enter this command in port configuration mode. 2.
Configuring PPP and PPPoE Table 15 Step Configure a Subscriber Record for PPPoE Task Root Command Create a PPPoE MOTM and enable the sending of it to subscribers. pppoe motm Point a subscriber’s PPPoE client browser to a specified URL. pppoe url Notes For descriptions of the basic tasks needed to configure a subscriber record, see the document, Configuring Subscribers. 3.2.
Configuration Tasks Table 16 Configure MLPPP over PPPoE Step Task 3. Optional. Specify priority and ppp multilink lfi fragmentation threshold value for subscriber sessions. 4. Configure one or more PPPoE For the commands encapsulated Ethernet ports. to configure a PPPo E-encapsulated Ethernet port, see Table 10. 3.2.10 Root Command Notes Example: MLPPP Configuration on PPPoE The following example shows how to configure MLPPP on PPPoE with two PPPoE sessions for the subscriber.
Configuring PPP and PPPoE 22 64/1543-CRA 119 1170/1 Uen K | 2012-12-04
Operations Tasks 4 Operations Tasks To enable the generation of debug messages for Point-to-Point Protocol (PPP) events and display PPP information, perform the appropriate task listed in Table 17. Enter the clear and debug commands in exec mode; enter the show commands in any mode. Table 17 PPP Operations Tasks Root Comman d Task Clear traffic counters for PPP-encapsulated ports and channels.
Configuring PPP and PPPoE 24 64/1543-CRA 119 1170/1 Uen K | 2012-12-04
Configuration Examples 5 Configuration Examples This section provides examples of PPP and PPPoE configurations. For information about troubleshooting PPP or PPPoE, see the BRAS Troubleshooting Guide. 5.1 PPP Examples This section provides examples of configuring PPP with dynamic and restricted dynamic binding and configuring MLPPP on ATM PVCs and for L2TP subscribers. 5.1.1 PPP Configuration with Dynamic Binding In Figure 1, the host on the left is configured to run PPP over ATM.
Configuring PPP and PPPoE 5.2 PPPoE Examples This section provides examples of configuring PPPoE. 5.2.1 Advertise a List of Services (Domains) The following example shows how to configure a SmartEdge OS to advertise all of its domains (isp1, isp2, and isp3) during the PPPoE discovery protocol: [local]Redback(config)#context isp1.net [local]Redback(config-ctx)#domain isp1 [local]Redback(config-ctx)#exit [local]Redback(config)#context isp2.
Configuration Examples 5.2.3 Set a PADO Delay The following example shows how to set the 802.1Q foo profile to have a PADO delay time of 3 seconds: [local]Redback(config)#dot1q profile foo [local]Redback(config-dot1q-profile)#pppoe pado delay 3 The following example shows how to remove the existing PADO delay: [local]Redback(config-dot1q-profile)#no pppoe pado delay 5.2.4 Point a Subscriber’s Browser to a URL The following example causes a PADM with the URL, http://www.loe.
Configuring PPP and PPPoE [local]Redback(config)#ppp ipcp negotiate netmask [local]Redback(config)#context PPP [local]Redback(config-ctx)#interface ppp multibind [local]Redback(config-if)#ip address 10.10.10.1/24 [local]Redback(config-if)#exit [local]Redback(config-ctx)#interface to_rad [local]Redback(config-if)#ip address 1.1.1.
Configuration Examples The following show command output indicates that a single IP address is reserved and the host route is installed: [local]Redback#show subscriber active all user1@local Session state Up Circuit 5/4 pppoe 17 Internal Circuit 5/4:1023:63/1/1/20 Interface bound ppp Current port-limit unlimited Protocol Stack Dual ip address 21.22.23.
Configuring PPP and PPPoE 30 64/1543-CRA 119 1170/1 Uen K | 2012-12-04
Reference List Reference List Related Documents [1] BRAS Troubleshooting Guide [2] Configuring Circuits [3] Configuring ATM, Ethernet, and POS Ports [4] Configuring Cross-Connections 64/1543-CRA 119 1170/1 Uen K | 2012-12-04 31
