DOCSLIB.ORG

Broadband Access Aggregation and DSL Configuration Guide, Cisco IOS Release 15MT

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Broadband Access Aggregation and DSL Configuration Guide, Cisco IOS Release 15MT Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. © 2012 Cisco Systems, Inc. All rights reserved. C O N T E N T S Preparing for Broadband Access Aggregation 1 Finding Feature Information 1 Prerequisites for Preparing for Broadband Access Aggregation 2 Restrictions for Preparing for Broadband Access Aggregation 2 Information About Preparing for Broadband Access Aggregation 2 Virtual-Access Interfaces 2 Autosense for ATM PVCs 3 Virtual Access Interface Precloning 3 Configuration Enhancements for Broadband Scalability 3 Virtual Access Subinterfaces 3 Virtual Template Compatibility with Subinterfaces 4 Benefits of Using Broadband Scalability Features 4 How to Prepare for Broadband Access Aggregation 4 Configuring PVCs 5 Benefits of Configuring a PVC Range 5 Configuring an ATM PVC or PVC Range 5 Configuring an Individual PVC Within a PVC Range 7 Configuring a Virtual Template 9 Precloning Virtual-Access Interfaces 10 Configuring Enhancements for Broadband Scalability 11 Verifying Virtual-Template Compatibility with Virtual-Access Subinterfaces 11 Disabling Virtual-Access Subinterfaces 12 Configuration Examples for Preparing for Broadband Access Aggregation 13 ATM PVC Range on a Point-to-Point Subinterface Example 13 ATM PVC Range on a Multipoint Subinterface Example 14 Individual PVC Within a PVC Range Configuration Example 14 Virtual-Access Subinterfaces Configuration Examples 14 Virtual-Access Subinterface Configuration Example 14 Testing a Virtual Template for Compatibility with Subinterfaces Example 15 Broadband Access Aggregation and DSL Configuration Guide, Cisco IOS Release 15MT iii Contents Where to Go Next 16 Additional References 17 Feature Information for Preparing for Broadband Access Aggregation 18 Understanding Broadband Access Aggregation 21 Finding Feature Information 21 Information About Broadband Access Aggregation 21 Encapsulation Protocols 22 Layer 2 Tunneling Protocol 22 ATM Services 23 PPPoE 23 PPPoEoE PPPoEo802.1q 23 PPPoA 23 Routed Bridge Encapsulation 24 Cisco Subscriber Service Switch 24 RADIUS Support in Cisco IOS 25 Additional References 25 Glossary 26 Providing Protocol Support for Broadband Access Aggregation of PPP over ATM Sessions 29 Finding Feature Information 29 Prerequisites for Providing Protocol Support for Broadband Access Aggregation of PPP over ATM Sessions 29 Restrictions for Providing Protocol Support for Broadband Access Aggregation of PPP over ATM Sessions 30 Information About Providing Protocol Support for Broadband Access Aggregation of PPP over ATM Sessions 30 PPP over ATM Configuration Scenario 30 Virtual Access Interface 31 Autosense for ATM PVCs 31 Benefits of Autosense for ATM PVCs 31 How to Provide Protocol Support for Broadband Access Aggregation of PPP over ATM Sessions 32 Configuring IETF-Compliant MUX Encapsulated PPP over ATM 32 Configuring IETF-Compliant LLC Encapsulated PPP over ATM 35 Configuring Cisco-Proprietary PPP over ATM PVCs 39 Configuring SVCs for NAPs and NSPs 43 Configuring PPPoA Autosense for a Single PVC 47 Broadband Access Aggregation and DSL Configuration Guide, Cisco IOS Release 15MT iv Contents Configuring PPPoA Autosense for a VC Class 49 Verifying PPPoA Autosense for ATM PVCs 51 Configuration Examples for Configuring PPP over ATM 53 IETF-Compliant MUX Encapsulated PPP over ATM Configuration Examples 53 IETF-Compliant PPP over ATM with Different Traffic-Shaping Parameters Example 53 ADSL Termination Example 54 Two Routers with Back-to-Back PVCs Example 55 Multiplexed Encapsulation Using VC Class Example 56 IETF-Compliant LLC Encapsulated PPP over ATM Configuration Examples 56 Configuring IETF-Compliant PPP over ATM LLC Encapsulation Example 56 Overriding a Virtual Template for IETF-Compliant PPP over ATM Example 57 Disabling IETF-Compliant PPP over ATM LLC Encapsulation on a Specific VC Example 57 Cisco Proprietary-PPP-over-ATM Example 58 PPP over an ATM SVC Configuration Example 58 PPPoA PPPoE Autosense on an ATM PVC Example 58 PPPoA PPPoE Autosense on a VC Class Example 59 PPPoA PPPoE Autosense on Multiple VC Classes and Virtual Templates Example 60 Where to Go Next 61 Additional References 61 Feature Information for Providing Protocol Support for Broadband Access Aggregation of PPP over ATM Sessions 62 Upstream PPPoX Connection Speed Transfer at LAC 65 Finding Feature Information 65 Prerequisites for Upstream PPPoX Connection Speed Transfer at LAC 65 Restrictions for Upstream PPPoX Connection Speed Transfer at LAC 66 Information About Upstream PPPoX Connection Speed Transfer at LAC 66 Upstream PPPoX Connection Speed Transfer at LAC 66 Benefits of Upstream PPPoX Connection Speed Transfer at LAC 66 How to Configure Upstream Connection Speed Transfer at LAC 67 Configuring Upstream PPPoX Connection Speed Transfer at the LAC 67 Configuring Upstream PPPoX Connection Speed Transfer at LAC on a PVC 67 Configuring Upstream PPPoX Connection Speed Transfer at LAC on VC 68 Configuration Examples for Upstream PPPoX Connection Speed Transfer at LAC 70 Configuring Upstream PPPoX Connection Speed Transfer at LAC Example 70 Additional References 70 Broadband Access Aggregation and DSL Configuration Guide, Cisco IOS Release 15MT v Contents Feature Information for Upstream PPPoX Connection Speed Transfer at LAC 72 Providing Session Limit Support 75 Finding Feature Information 75 Information About Providing Session Limit Support 75 Benefits of Providing Session Limit Support 75 How to Provide Session Limit Support 75 Specifying the Maximum Number of PPPoE Sessions on the Router 76 Specifying the Maximum Number of PPPoE Sessions on a Gigabit Ethernet Interface 77 Configuration Examples for Providing Session Limit Support 79 Specifying the Maximum Number of PPPoE Sessions on a Router Example 79 Specifying the Maximum Number of PPPoE Sessions on a Gigabit Ethernet Interface Example 79 Additional References 79 Feature Information for Providing Session Limit Support 81 Monitoring PPPoE Sessions with SNMP 83 Finding Feature Information 83 Prerequisites for Monitoring PPPoE Sessions with SNMP 83 Restrictions for Monitoring PPPoE Sessions with SNMP 84 Information About Monitoring PPPoE Sessions with SNMP 84 Network Management Protocol 84 PPPoE Session Count MIB 84 Benefits of Monitoring PPPoE Sessions with SNMP 85 How to Configure SNMP Monitoring of PPPoE Sessions 85 Enabling PPPoE Session Count SNMP Traps 86 Configuring the PPPoE Session-Count Threshold for the Router Using VPDN Groups 87 Configuring the PPPoE Session-Count Threshold for the Router Using BBA Groups 88 Configuring the PPPoE Session-Count Threshold for a PVC 89 Configuring the PPPoE Session-Count Threshold for a VC Class 91 Configuring the PPPoE Session-Count Threshold for an ATM PVC Range 92 Configuring the PPPoE Session-Count Threshold for an Individual PVC Within a Range 93 Verifying PPPoE Session-Count Thresholds 95 Monitoring and Maintaining PPPoE Session Counts and SNMP Notifications 96 Configuration Examples
Recommended publications
  • Point-To-Point Protocol Over Ethernet (Pppoe) Management

    Point-To-Point Protocol Over Ethernet (Pppoe) Management

    Point-to-Point Protocol over Ethernet (PPPoE) Management In This Chapter This chapter provides information about using PPPoE, including theory, supported features and configuration process overview. Topics in this chapter include: • PPPoE on page 596 → PPPoE Authentication and Authorization on page 599 → General Flow on page 599 − RADIUS on page 600 − Local User Database Directly Assigned to PPPoE Node on page 601 − Local DHCP Server with Local User Database on page 605 → Multiple Sessions Per MAC Address on page 607 → Private Retail Subnets on page 608 • MLPPPoE, MLPPP(oE)oA with LFI on LNS on page 614 7750 SR Triple Play Service Delivery Architecture Page 595 PPPoE PPPoE A Broadband Remote Access Server (BRAS) is a device that terminates PPPoE sessions. PPPoE sessions are supported on Alcatel-Lucent Broadband Services Router (BSR) on IOM2. The Point- to-Point Protocol (PPP) is used for communications between a client and a server. Point-to-Point Protocol over Ethernet (PPPoE) is a network protocol used to encapsulate PPP frames inside Ethernet frames. Ethernet networks are packet-based, unaware of connections or circuits. Using PPPoE, Alcatel- Lucent users can dial from one router to another over an Ethernet network, then establish a point- to-point connection and transport data packets over the connection. In this application subscriber hosts can connect to the router using a PPPoE tunnel. There are two command available under PPPoE to limit the number of PPPoE hosts, one to set a limit that is applied on each SAP of the group-interface and one to set the limit per group-interface.
  • DSL Network Architectures

    DSL Network Architectures

    CHAPTER 2 DSL Network Architectures This chapter provides a brief overview of available asymmetric DSL (ADSL) architecture options. A typical ADSL service architecture is illustrated in Figure 2-1. In the architecture illustrated, the network consists of Customer Premise Equipment (CPE), the Network Access Provider (NAP) and the Network Service Provider (NSP). CPE refers to an end-user workstations (such as a PC) together with an ADSL modem or ADSL terminating unit router (ATU-R). The NAP provides ADSL line termination by using DSL access multiplexers (DSLAMs). The DSLAM forwards traffic to the local access concentrator, which is used for Point-to-Point Protocol (PPP) tunneling and Layer 3 termination. From the Layer 2 Tunneling Protocol Access Concentrator (LAC), services extend over the ATM core to the NSP. Figure 2-1 Overview of a DSL network deployment including CPE, NAP and NSP components ISP Internet Internet Enterprise DSLAM 6400 ATU-R Termination ATMCore service selection Content Video Aggregation Voice service selection 49326 CPE NAP NSP 2-1 Chapter 2 DSL Network Architectures Technology Overview Technology Overview In this section some of the major DSL architectures are briefly addressed. The order of the architectures presented is from the most simplistic (bridging based) to the most robust and scalable (PPP based). Five general design scheme are described: • Integrated Routing and Bridging (IRB)/RFC 1483 Bridging • Routed Bridge Encapsulation (RBE) • Point-to-Point Protocol over ATM (PPPoA) • Point-to-Point Protocol over Ethernet (PPPoE) • Service Selection Gateway (SSG) Integrated Routing and Bridging (IRB)/RFC 1483 Bridging The RFC 1483 bridging architecture is very simple to understand and implement.
  • Cisco IOS Broadband and DSL Configuration Guide Release 12.4

    Cisco IOS Broadband and DSL Configuration Guide Release 12.4

    Cisco IOS Broadband and DSL Configuration Guide Release 12.4 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 526-4100 Customer Order Number: DOC-7817496= Text Part Number: 78-17496-01 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
  • Understanding Broadband Access Aggregation

    Understanding Broadband Access Aggregation

    Understanding Broadband Access Aggregation First Published: May 2, 2005 Last Updated: May 2, 2005 Broadband access aggregation is the means by which connections are made among multiple technologies. These technologies include ISDN, DSL, cable, Ethernet, and wireless devices that are connected to corporate virtual private networks (VPNs), third-party applications, and the Internet. Subscriber demand for high-speed services, including multi-player gaming, video-on-demand, home security, digital audio, streaming video, and many other applications, require the delivery of IP services, regardless of the access medium. Because so many different technologies are involved in broadband access aggregation, it is important that the service provider understand their network both in terms of the hardware that makes up the installation, which determines what type of sessions need to be established, but also in terms of what kinds of services their subscribers expect to receive. The demands placed on large service provider installations can often result in the need to contend with millions of sessions and provide flexible and reliable configurations for widely diverse consumer needs. This module contains conceptual information about broadband access aggregation. Contents • Information About Broadband Access Aggregation, page 1 • Additional References, page 6 • Glossary, page 7 Information About Broadband Access Aggregation To perform the necessary tasks in providing broadband access aggregation, you should understand the following concepts: • Encapsulation
  • Point-To-Point Protocol Over Ethernet (Pppoe) Management

    Point-To-Point Protocol Over Ethernet (Pppoe) Management

    Point-to-Point Protocol over Ethernet (PPPoE) Management In This Chapter This chapter provides information about using PPPoE, including theory, supported features and configuration process overview. Topics in this chapter include: • PPPoE on page 512 → PPPoE Authentication and Authorization on page 515 → General Flow on page 515 − RADIUS on page 516 − Local User Database Directly Assigned to PPPoE Node on page 517 − Local DHCP Server with Local User Database on page 518 → Multiple Sessions Per MAC Address on page 520 → Private Retail Subnets on page 521 • MLPPPoE, MLPPP(oE)oA with LFI on LNS on page 529 7750 SR OS Triple Play Guide Page 511 PPPoE PPPoE A Broadband Remote Access Server (BRAS) is a device that terminates PPPoE sessions. PPPoE sessions are supported on Alcatel-Lucent Broadband Services Router (BSR) on IOM2. The Point- to-Point Protocol (PPP) is used for communications between a client and a server. Point-to-Point Protocol over Ethernet (PPPoE) is a network protocol used to encapsulate PPP frames inside Ethernet frames. Ethernet networks are packet-based, unaware of connections or circuits. Using PPPoE, Alcatel- Lucent users can dial from one router to another over an Ethernet network, then establish a point- to-point connection and transport data packets over the connection. In this application subscriber hosts can connect to the router using a PPPoE tunnel. There are two command available under PPPoE to limit the number of PPPoE hosts, one to set a limit that is applied on each SAP of the group-interface and one to set the limit per group-interface.
  • Must-Have Reference for IP and Next Generation Networking

    Must-Have Reference for IP and Next Generation Networking

    The Must-Have Reference for IP and Next Generation Networking This reference provides the information you need to (Application-Specific Integrated Circuits) allow real-time understand the terminology associated with IP and next switching and forwarding with wirespeed performance, generation network switching, routing, and testing and at lower cost than traditional software-based products. It enables you to make informed decisions routers built around general-purpose CPUs. about the products. Three factors combined over the last two years to fuel Understanding the Layers the evolution of multilayer switching: • Users need to get beyond the performance Internetworking devices such as bridges, routers, and bottleneck of collapsed backbone routers and avoid switches have traditionally been categorized by the OSI the high cost of expanding them. layer they operate at and the role they play in the • IP traffic from intranet and Internet applications has topology of a network: increased dramatically. • Bridges and switches operate at Layer 2: they • ASIC densities increased enough to allow economic extend network capabilities by forwarding traffic implementation of complex routing functions directly among LANs and LAN segments with high in high-speed hardware instead of using the slow throughput. software techniques of traditional routers. • Routers operate at Layer 3: they perform route calculations based on Layer 3 addresses and Multilayer Switch Names provide multi-protocol support and WAN access, but typically at the cost of higher latency and much Vendors, analysts, and editors don’t agree about the more complex administration requirements. specific meaning of terms such as multilayer switch, Layer 3 switch, IP switch, routing switch, switching Layer 2 refers to the layer in the communications router, and wirespeed router.
  • Traffic Policing of In-Contract Traffic in a L2tp Based L2f

    Traffic Policing of In-Contract Traffic in a L2tp Based L2f

    International Journal of Scientific & Engineering Research, Volume 5, Issue 2, February-2014 1126 ISSN 2229-5518 TRAFFIC POLICING OF IN-CONTRACT TRAFFIC IN A L2TP BASED L2F Pushpa yadav Abstract: L2TP (Layer 2 Tunneling Protocol) allows multiprotocol traffic to be encrypted and then sent over any medium that supports point-to-point datagram delivery, such as IP or asynchronous transfer mode. This paper represents the best features of PPTP and L2F. In this paper, we are mainly focusing on topic that how can shape the traffic for a smooth Traffic Management purpose so that we can easily confirm the amount of traffic travelled through the setup. This also ensures that the amount of traffic passed is same or varying to the amount of traffic we want to pass .At time of Congestion, this feature provides an additional benefit and helps in fighting congestion at the real time applications. Also this adds to the existing PPP authentication process and ensures a level of check from our side. Keywords: Authentication, VFN, Tunnelling, VPN, l2F, LAC, PPP ________________________ __________________________ IJSER IJSER © 2014 http://www.ijser.org International Journal of Scientific & Engineering Research, Volume 5, Issue 2, February-2014 1127 ISSN 2229-5518 1 Introduction Tunneling, also known as "port forwarding," is the transmission of data intended for use only within a private, usually corporate network through a public network in such a way that the routing nodes in the public network are unaware that the transmission is part of a private network.L2TP requires two levels of authentication: Computer level Authentication and User level Authentication.