Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 32 views

    Configuring The Cpe As The Pppoe or Pppoa Client: Teleworker Connectivity

    Uploaded by

    rajkumarlodh
    This document provides instructions for configuring a Cisco router or customer premises equipment (CPE) as a Point-to-Point Protocol over Ethernet (PPPoE) or Point-to-Point Protocol over ATM (PPPoA) client for a teleworker connectivity. It discusses: 1. Configuring Ethernet or ATM interfaces, dialer interfaces, port address translation (PAT), DHCP server, and default routes for the CPE as a PPPoE or PPPoA client. 2. Examples of full PPPoE and PPPoA client configurations on the CPE with debugging outputs. 3. Verification steps like showing PPPoE sessions, NAT translations

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd

    Configuring The Cpe As The Pppoe or Pppoa Client: Teleworker Connectivity

    Uploaded by

    rajkumarlodh
    32 views44 pages
    This document provides instructions for configuring a Cisco router or customer premises equipment (CPE) as a Point-to-Point Protocol over Ethernet (PPPoE) or Point-to-Point Protocol over ATM (PPPoA) client for a teleworker connectivity. It discusses: 1. Configuring Ethernet or ATM interfaces, dialer interfaces, port address translation (PAT), DHCP server, and default routes for the CPE as a PPPoE or PPPoA client. 2. Examples of full PPPoE and PPPoA client configurations on the CPE with debugging outputs. 3. Verification steps like showing PPPoE sessions, NAT translations

    Original Title

    ISCW10S02L04

    Copyright

    © © All Rights Reserved

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides instructions for configuring a Cisco router or customer premises equipment (CPE) as a Point-to-Point Protocol over Ethernet (PPPoE) or Point-to-Point Protocol over ATM (PPPoA) client for a teleworker connectivity. It discusses: 1. Configuring Ethernet or ATM interfaces, dialer interfaces, port address translation (PAT), DHCP server, and default routes for the CPE as a PPPoE or PPPoA client. 2. Examples of full PPPoE and PPPoA client configurations on the CPE with debugging outputs. 3. Verification steps like showing PPPoE sessions, NAT translations

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    32 views44 pages

    Configuring The Cpe As The Pppoe or Pppoa Client: Teleworker Connectivity

    Uploaded by

    rajkumarlodh
    This document provides instructions for configuring a Cisco router or customer premises equipment (CPE) as a Point-to-Point Protocol over Ethernet (PPPoE) or Point-to-Point Protocol over ATM (PPPoA) client for a teleworker connectivity. It discusses: 1. Configuring Ethernet or ATM interfaces, dialer interfaces, port address translation (PAT), DHCP server, and default routes for the CPE as a PPPoE or PPPoA client. 2. Examples of full PPPoE and PPPoA client configurations on the CPE with debugging outputs. 3. Verification steps like showing PPPoE sessions, NAT translations

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    of 44

    Teleworker Connectivity

    Configuring the CPE as the PPPoE or PPPoA


    Client
    Configuration of a
    Cisco Router as the
    PPPoE Client
    Configuration Tasks: Configuring the CPE as the
    PPPoE Client over the Ethernet Interface

    1. Configure an Ethernet interface


    2. Configure a dialer interface
    3. Configure PAT
    4. Configure DHCP server
    5. Configure a static default route
    Example: CPE as the PPPoE Client
    over the Ethernet Interface
    Example: CPE as the PPPoE Client
    over the Ethernet Interface (Cont.)
    Configuration Tasks: Configuring the CPE as the
    PPPoE Client over the ATM Interface

    1. Configure an ATM interface


    2. Configure a dialer interface
    3. Configure PAT
    4. Configure DHCP server
    5. Configure a static default route
    Example: CPE as the PPPoE Client
    over the ATM Interface
    Example: CPE as the PPPoE Client
    over the ATM Interface (Cont.)
    Configuration of a
    PPPoE Client
    PPPoE Client Configuration

    router(config)#
    interface ethernet number

    • Configures the Ethernet interface

    router(config-if)#
    pppoe enable

    • Enables PPPoE on Ethernet interface

    router(config-if)#
    pppoe-client dial-pool-number number

    • Binds a dialer profile to the Ethernet interface


    Example: Configuring PPPoE Client
    Configuration of the
    PPPoE DSL Dialer
    Interface
    Configuring the PPPoE Dialer Interface

    router(config)#
    interface dialer number

    • Configures the dialer interface.

    router(config-if)#
    encapsulation ppp

    • Specifies PPP encapsulation for the dialer interface.

    router(config-if)#
    ip address negotiated

    • Sets IP address to be negotiated with the remote peer using


    IPCP.
    Configuring the PPPoE
    Dialer Interface (Cont.)

    router(config-if)#
    dialer pool pool_number

    • Binds dialer interface to the dialer pool

    router(config-if)#
    ip mtu mtu_size

    • Reduces the maximum Ethernet payload size because the


    PPPoE header requires 8 bytes
    router(config-if)#
    ppp authentication chap [callin]

    • (Optional) Configures PPP authentication CHAP


    Example: Configuring the
    PPPoE Dialer Interface
    Configuration of PAT
    Port Address Translation
    Configure PAT

    router(config)#
    access-list ACL_num {permit | deny} protocol source_network
    source_wildcard destination_network destination_wildcard

    • Specifies the addresses that may be translated

    router(config)#
    ip nat inside source list ACL_num interface interface number
    [overload]

    • Enables dynamic translation of addresses using the assigned IP


    address of the interface

    router(config-if)#
    ip nat {inside | outside}

    • Specifies the interface as inside or outside related to PAT


    Example: PAT Configuration
    Configuration of DHCP
    to Scale DSL
    Configure a DHCP Server

    router(config)#
    ip dhcp pool pool_name
    • Enables a DHCP pool for use by hosts and enters DHCP pool configuration mode.

    router(dhcp-config)#
    import all

    • Imports DNS and WINS information from IPCP.


    router(dhcp-config)#
    network network_address subnet_mask

    • Specifies the network and subnet mask of the pool.


    router(dhcp-config)#
    default-router address

    • Specifies the default router for the pool to use.


    Example: DHCP Server Configuration
    Configuration of a
    Static Default Route
    Configuring a Static Default Route

    router(config)#
    ip route 0.0.0.0 0.0.0.0 interface number

    • The CPE can use a static default route to reach all remote
    destinations.
    Example: Static Default Route
    Verifying a PPPoE
    Configuration
    Verifying a PPPoE Configuration

    router#
    debug pppoe events

    • Displays PPPoE protocol messages about events that are


    part of normal session establishment or shutdown
    router#
    debug ppp authentication

    • Displays authentication protocol messages, including CHAP


    and PAP packet exchanges
    router#
    show pppoe session

    • Displays basic information about currently active PPPoE


    sessions
    Verifying a PPPoE Configuration (Cont.)

    router#
    show ip dhcp binding

    • Displays address bindings on the Cisco IOS DHCP server

    router#
    show ip nat translations

    • Displays active NAT translations

    C:\Documents and Settings\User>


    ipconfig /all

    • Displays the complete IP configuration on Windows NT,


    2000, or XP system
    Debug VPDN PPPoE Events

    CPE#debug pppoe events


    15:13:41.991: Sending PADI: Interface = Ethernet1
    15:13:42.083: PPPoE 0: I PADO
    15:13:44.091: PPPOE: we've got our pado and the pado timer went off
    15:13:44.091: OUT PADR from PPPoE Session
    15:13:44.187: PPPoE 5989: I PADS
    15:13:44.187: IN PADS from PPPoE Session

    • Determine if the PPPoE connect phase is successful.

    CPE#show pppoe session


    Total PPPoE sessions 1

    PPPoE Session Information


    UID SID RemMAC Intf Intf Session
    LocMAC VASt state
    0 5989 0090.1a41.1a83 Et1 Vi2 N/A
    000b.46e2.eb36 UP

    • Get the status of the PPPoE session.


    Debug PPP Authentication

    CPE#debug ppp authentication


    CPE#configure terminal
    Enter configuration commands, one per line. End with CNTL/Z.
    CPE(config)#interface ATM 0/0
    CPE(config-if)#no shutdown
    00:19:05: %LINK-3-UPDOWN: Interface ATM 0/0, changed state to up
    00:19:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0/0,
    changed state to up
    00:19:29: %DIALER-6-BIND: Interface Vi2 bound to profile Di1
    00:19:29: Vi2 PPP: Using dialer call direction
    00:19:29: Vi2 PPP: Treating connection as a callout
    00:19:29: Vi2 PPP: Authorization required
    00:19:29: Vi2 PPP: No remote authentication for call-out
    00:19:29: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
    00:19:31: Vi2 CHAP: I CHALLENGE id 1 len 24 from "ISP"
    00:19:31: Vi2 CHAP: Using hostname from interface CHAP
    00:19:31: Vi2 CHAP: Using password from AAA
    00:19:31: Vi2 CHAP: O RESPONSE id 1 len 25 from "CPE"
    00:19:32: Vi2 CHAP: I SUCCESS id 1 len 4
    00:19:33: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-
    Access2, changed state to up

    • Enable debugging for PPP authentication to verify authentication


    success.
    Verify DHCP Clients

    C:\Documents and Settings\User>ipconfig /all

    Windows 2000 IP Configuration

    Ethernet adapter LAB:

    Connection-specific DNS Suffix . : lab.com


    Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Mobile
    Connection
    Physical Address. . . . . . . . . :
    00-11-25-AF-40-9B
    Dhcp Enabled. . . . . . . . . . . :
    Yes
    Autoconfiguration Enabled . . . . :
    Yes
    IP Address. . . . . . . . . . . . :
    10.0.0.2
    Subnet Mask . . . . . . . . . . . :
    255.0.0.0
    Default Gateway . . . . . . . . . :
    10.0.0.1
    DHCP Server . . . . . . . . . . . :
    10.0.0.1
    DNS Servers . . . . . . . . . . . :
    192.168.1.1
    192.168.1.2
    Primary WINS Server . . . . . . . : 192.168.1.3
    Lease Obtained. . . . . . . . . . : 6. April 2006 16:36:31
    Lease Expires . . . . . . . . . . : 7. April 2006 0:36:31

    • Verify how the IP address is assigned on the PC.


    Verify DHCP Server

    CPE#show ip dhcp binding


    IP address Client-ID/ Lease expiration Type
    Hardware address
    10.0.0.2 0100.5056.4000.59 Jan 21 2006 12:50 AM Automatic
    10.0.0.3 0100.5056.4000.60 Jan 21 2006 12:50 AM Automatic

    • Verify the existing DHCP bindings on the router (DHCP


    server).
    Verify PAT

    CPE#show ip nat translations


    Pro Inside global Inside local Outside local Outside global
    icmp 192.168.1.202:512 10.0.0.2:512 192.168.123.100:512 192.168.123.100:512

    • Verify how IP addresses are translated on the router.


    PPPoE Sample Configuration

    hostname CPE
    !
    ip dhcp pool MyPool
    network 10.0.0.0 255.0.0.0
    default-router 10.0.0.1
    !
    interface Ethernet0/1
    no ip address
    pppoe enable
    pppoe-client dial-pool-number 1
    !
    interface Ethernet0/0
    ip address 10.0.0.1 255.0.0.0
    ip nat inside
    !
    interface Dialer0
    ip address negotiated
    encapsulation ppp
    dialer pool 1
    ip mtu 1492
    ip nat outside
    ppp authentication chap callin
    ppp chap password mysecret
    !
    ip nat inside source list 101 interface Dialer0 overload
    access-list 101 permit ip 10.0.0.0 0.255.255.255 any
    !
    ip route 0.0.0.0 0.0.0.0 Dialer0
    Configuration of a
    PPPoA DSL
    Connection
    DSL Configuration Overview

    • The CPE device encapsulates the PPP session based on RFC 1483 for transport
    across the DSLAM.
    • The virtual access interface associates each PPP connection with an ATM VC.
    • The virtual access interface obtains its configuration from a virtual interface
    template when the VC is created.
    • The PPP subsystem starts and the router attempts to send a PPP configure
    request to the remote peer.
    • The virtual access interface remains associated with a VC as long as the VC is
    configured.
    • Three types of PPP over ATM connections are supported:
    – IETF-compliant MUX encapsulated PPPoA
    – IETF-compliant LLC encapsulated PPPoA
    – Cisco-proprietary PPPoA
    PPPoE vs. PPPoA

    • In the PPPoE configuration, you have to bind Ethernet interface to


    dialer interface and reduce the maximum Ethernet payload size from
    1500 to 1492.
    • In the PPPoA configuration, you have to configure proper
    encapsulation on the ATM interface and associate the interface with
    the dialer pool.

    PPPoE PPPoA
    interface Ethernet0/1 interface ATM0/0
    no ip address no ip address
    pppoe enable dsl operating-mode auto
    pppoe-client dial-pool-number 1 pvc 1/32
    ! encapsulation aal5mux ppp dialer
    interface Dialer0 dialer pool-member 1
    ip mtu 1492
    Configuration of the
    DSL ATM Interface
    Configuring the DSL ATM Interface

    Step 1: Configure modulation mode


    router(config)#
    interface atm number
    router(config-if)#
    dsl operating-mode auto

    • Permits the router to automatically determine the service provider


    DSL modulation; this is the default setting on the Cisco router.

    Step 2: Create PVC


    router(config-if)#
    pvc vpi/vci

    • Creates an ATM PVC for the router.


    • Note: The PVC VPI/VCI must match the provider VPI/VCI.
    Configuring the DSL ATM Interface (Cont.)

    Step 3: Define the encapsulation


    router(config-atm-vc)#
    encapsulation aal5mux ppp dialer

    • Identifies the Layer 2 encapsulation

    Step 4: Associate the interface with the pool


    router(config-atm-vc)#
    dialer pool-member number

    • Specifies a dialer pool member


    PPPoA Sample Configuration
    hostname CPE
    !
    ip dhcp pool MyPool
    network 10.0.0.0 255.0.0.0
    default-router 10.0.0.1
    !
    interface ATM0/0
    no ip address
    dsl operating-mode auto
    pvc 8/35
    encapsulation aal5mux ppp dialer
    dialer pool-member 1
    !
    interface Ethernet0/0
    ip address 10.0.0.1 255.0.0.0
    ip nat inside
    !
    interface Dialer0
    ip address negotiated
    encapsulation ppp
    dialer pool 1
    ip nat outside
    ppp authentication chap callin
    ppp chap password mysecret
    !
    ip nat inside source list 101 interface Dialer0 overload
    access-list 101 permit ip 10.0.0.0 0.255.255.255 any
    !
    ip route 0.0.0.0 0.0.0.0 Dialer0
    Summary

    • Configuring DSL requires global and interface configuration


    commands.
    • Enable PPPoE on Ethernet interface with the pppoe enable
    command and bind the Ethernet interface to a dialer interface.
    • Configure the dialer interface with MTU size of 1492 and,
    optionally, for PPP authentication.
    • PAT enables you to use one registered IP address for the
    interface to access the Internet from all devices in the network.
    • The Cisco IOS DHCP server was enhanced to allow
    configuration information to be updated automatically.
    Summary (Cont.)

    • Configure a static default route on the Cisco router to allow the router
    to reach all unknown destinations toward the dialer interface.
    • To verify proper PPPoE configuration, use debug ppp authentication,
    show pppoe session, show ip dhcp binding, show ip nat translations, and
    ipconfig /all commands.
    • Configuring a PPPoA connection requires configuration of ATM and
    dialer interfaces, PAT, DHCP, and static default route.
    • Use the dsl operating-mode auto interface configuration command to
    specify that the router will automatically detect the DSL modulation
    that the service provider is using, and will set the DSL modulation to
    match.
    • An ATM VCI/VPI pair must be configured to communicate with the
    service provider.

    You might also like