Scribd Logo
Upload

Welcome to Scribd!

  • 33 views

    Lab 4.9.3 Using PPP Multilink For ISDN B Channel Aggregation

    Uploaded by

    Kishore Reddy Kandi
    a

    Copyright:

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

    Lab 4.9.3 Using PPP Multilink For ISDN B Channel Aggregation

    Uploaded by

    Kishore Reddy Kandi
    33 views5 pages
    a

    Original Title

    lab_4_9_3

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    a

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    33 views5 pages

    Lab 4.9.3 Using PPP Multilink For ISDN B Channel Aggregation

    Uploaded by

    Kishore Reddy Kandi
    a

    Copyright:

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

    Lab 4.9.

    3 Using PPP Multilink for ISDN B Channel Aggregation

    Objective
    In this lab, the student will configure two Cisco routers for DDR using Multilink PPP (MLP) to use
    both B channels as a 128 kbps bundle.

    Scenario
    The International Travel Agency wants an ISDN DDR connection configured between a remote office
    in Capetown and its corporate office known as SanJose1. To maximize bandwidth, configure MLP to
    use both B channels for the data link.

    Step 1
    Before beginning this lab, it is recommended that the routers be reloaded after erasing their startup
    configuration. This will prevent problems that may be caused by residual configurations.
    Build and configure the network according to the diagram, but do not configure the BRI interfaces on
    either router yet. Use the Adtran Atlas 550 or similar device to simulate the ISDN cloud. If the Atlas
    550 is used, be sure to use straight-through cables. Connect both routers to the respective BRI
    module ports of the Atlas 550 as labeled in the diagram. Be sure to configure both workstations with
    the correct IP address and default gateway.

    Step 2
    Configure SanJose1 and Capetown for ISDN. Refer to the following commands to guide the
    configuration:
    SanJose1(config)#username Capetown password cisco
    SanJose1(config)#isdn switch-type basic-ni
    SanJose1(config)#interface bri0/0
    1-5

    CCNP 2: Remote Access v 3.0 - Lab 4.9.3

    Copyright 2003, Cisco Systems, Inc.

    SanJose1(config-if)#ip address 192.168.16.1 255.255.255.0


    SanJose1(config-if)#encapsulation ppp
    SanJose1(config-if)#ppp authentication chap
    SanJose1(config-if)#isdn spid1 51055510000001 5551000
    SanJose1(config-if)#isdn spid2 51055510010001 5551001
    SanJose1(config-if)#dialer idle-timeout 60
    SanJose1(config-if)#dialer-group 1
    SanJose1(config-if)#dialer map ip 192.168.16.3 name Capetown 5552000
    SanJose1(config-if)#no shutdown
    SanJose1(config)#dialer-list 1 protocol ip permit
    SanJose1(config)#ip route 192.168.216.0 255.255.255.0 192.168.16.3
    Capetown(config)#enable password cisco
    Capetown(config)#line vty 0 4
    Capetown(config-line)#password cisco
    Capetown(config-line)#exit
    Capetown(config)#username SanJose1 password cisco
    Capetown(config)#isdn switch-type basic-ni
    Capetown(config)#interface bri0/0
    Capetown(config-if)#ip address 192.168.16.3 255.255.255.0
    Capetown(config-if)#encapsulation ppp
    Capetown(config-if)#ppp authentication chap
    Capetown(config-if)#isdn spid1 51055520000001 5552000
    Capetown(config-if)#isdn spid2 51055520010001 5552001
    Capetown(config-if)#dialer idle-timeout 60
    Capetown(config-if)#dialer-group 1
    Capetown(config-if)#dialer map ip 192.168.16.1 name SanJose1 5551000
    Capetown(config-if)#no shutdown
    Capetown(config)#dialer-list 1 protocol ip permit
    Capetown(config)#ip route 0.0.0.0 0.0.0.0 192.168.16.1

    Use the show isdn status command to verify that the routers have established communication
    with the ISDN switch. If the routers have not established communication with the ISDN switch use
    the clear interface bri0/0 command multiple times if necessary, to enable a valid and
    established SPID status. The show running-config command can also be used on each router
    to verify that the configurations have been entered correctly.
    Verify that the routers have established communication with the ISDN switch with the show isdn
    status command. Use the clear interface bri0/0 command multiple times if necessary to
    enable a valid and established SPID status.
    Issue the debug dialer command on both SanJose1 and Capetown. Then test the DDR
    configuration by pinging Host A from Host B. Troubleshoot as necessary.

    Step 3
    Configure each router for multilink PPP. On both SanJose1 and Capetown, issue the following
    commands for PPP multilink:
    SanJose1(config)#interface bri0/0
    SanJose1(config-if)#ppp multilink
    SanJose1(config-if)#dialer load-threshold 1 either
    SanJose1(config-if)#dialer map ip 192.168.16.3 name Capetown 5552001
    SanJose1(config-if)#dialer redial interval 5 attempts 3
    Capetown(config)#interface bri0/0
    Capetown(config-if)#ppp multilink
    Capetown(config-if)#dialer load-threshold 1 either
    Capetown(config-if)#dialer map ip 192.168.16.1 name SanJose1 5551001
    Capetown(config-if)#dialer redial interval 5 attempts 3

    The ppp multilink command is used on ISDN interfaces to bundle both 64 kbps B channels.
    When bundled, they function together as a 128 kbps pipe.
    2-5

    CCNP 2: Remote Access v 3.0 - Lab 4.9.3

    Copyright 2003, Cisco Systems, Inc.

    The dialer load-threshold command specifies how much traffic on the first B channel will
    force the second channel to be brought up. This command takes a numerical argument from 1 to
    255. The number 1 is the minimum load and would enable the second channel automatically. The
    number 255 is a full load. Therefore, the value 128 would be approximately a fifty percent (50%)
    load.
    If the threshold is set to 255, the second B channel will not be brought up until the first channel is
    completely loaded. By default, only outbound traffic is monitored. To monitor incoming and outgoing
    traffic, the keyword either is used. The option of specifying inbound or outbound instead is also
    available.
    A second dialer map statement is entered to map the Layer 3 IP address to another Layer 2
    destination SPID. Essentially, it configures the second B channel.
    The dialer redial command was introduced in Cisco IOS Software Release 12.1(2).
    Therefore, this command will not be available, and not required, if an older IOS version is used. The
    command sets the redial interval between dial attempts to five seconds, for a maximum of three
    attempts. This interval allows for the old call to be torn down completely before the redial is
    attempted.

    Step 4
    Ping Host A from Host B. This ping should bring up the DDR connection. Troubleshoot as necessary.
    Once the connection is up, verify that both channels have been enabled. Use the show ip
    interface brief command on both routers. Notice that both B channels are up. If only channel 1
    is up, clear the interface and send more pings to Host A from Host B. The following are sample
    outputs:
    SanJose1#show ip interface brief
    Interface
    IP-Address
    FastEthernet0/0
    192.168.0.1
    Serial0/0
    unassigned
    BRI0/0
    192.168.16.1
    BRI0/0:1
    unassigned
    BRI0/0:2
    unassigned
    Serial0/1
    unassigned
    Virtual-Access1
    unassigned

    OK?
    YES
    YES
    YES
    YES
    YES
    YES
    YES

    Method
    NVRAM
    NVRAM
    NVRAM
    unset
    unset
    NVRAM
    TFTP

    Status
    Protocol
    up
    up
    administratively down down
    up
    up
    up
    up
    up
    up
    administratively down down
    up
    up

    Capetown#show ip interface brief


    Interface
    IP-Address
    FastEthernet0/0
    192.168.216.1
    Serial0/0
    unassigned
    BRI0/0
    192.168.16.3
    BRI0/0:1
    unassigned
    BRI0/0:2
    unassigned
    Serial0/1
    unassigned
    Virtual-Access1
    unassigned

    OK?
    YES
    YES
    YES
    YES
    YES
    YES
    YES

    Method
    NVRAM
    NVRAM
    NVRAM
    unset
    unset
    NVRAM
    TFTP

    Status
    Protocol
    up
    up
    administratively down down
    up
    up
    up
    up
    up
    up
    administratively down down
    up
    up

    Notice that both B channels show up and up.


    1. A new interface has appeared in the output from the show ip interface brief command.
    What is it called?

    __________________________________________________________________________
    __________________________________________________________________________
    With the ISDN connection still active, issue the show dialer command on both routers. The
    following are sample outputs:
    SanJose1#show dialer
    BRI0/0 - dialer type = ISDN
    3-5

    CCNP 2: Remote Access v 3.0 - Lab 4.9.3

    Copyright 2003, Cisco Systems, Inc.

    Dial String
    Successes
    Failures
    Last DNIS
    0 incoming call(s) have been screened.
    0 incoming call(s) rejected for callback.

    Last status

    BRI0/0:1 - dialer type = ISDN


    Idle timer (60 secs), Fast idle timer (20 secs)
    Wait for carrier (30 secs), Re-enable (15 secs)
    Dialer state is multilink member (Capetown)
    BRI0/0:2 - dialer type = ISDN
    Idle timer (60 secs), Fast idle timer (20 secs)
    Wait for carrier (30 secs), Re-enable (15 secs)
    Dialer state is multilink member
    Connected to <unknown phone number> (Capetown)
    Capetown#show dialer
    BRI0/0 - dialer type = ISDN
    Dial String
    Successes
    Failures
    Last DNIS
    5551001
    0
    0
    never
    5551000
    21
    0
    00:00:31
    0 incoming call(s) have been screened.
    0 incoming call(s) rejected for callback.

    Last status
    successful

    BRI0/0:1 - dialer type = ISDN


    Idle timer (60 secs), Fast idle timer (20 secs)
    Wait for carrier (30 secs), Re-enable (15 secs)
    Dialer state is multilink member
    Dial reason: ip (s=192.168.216.2, d=192.168.0.2)
    Connected to 5551000 (SanJose1)
    BRI0/0:2 - dialer type = ISDN
    Idle timer (60 secs), Fast idle timer (20 secs)
    Wait for carrier (30 secs), Re-enable (15 secs)
    Dialer state is multilink member
    Dial reason: Multilink bundle overloaded
    Connected to 5551000 (SanJose1)

    2. Which part of the show dialer command output indicated that PPP multilink is functioning?

    __________________________________________________________________________
    __________________________________________________________________________
    3. What was the dial reason for the first B channel? What was the dial reason for the second B
    channel?

    __________________________________________________________________________
    __________________________________________________________________________
    Issue the show ppp multilink command on SanJose1 and on Capetown. The following are
    sample outputs:
    SanJose1#show ppp multilink
    Virtual-Access1, bundle name is Capetown
    Dialer interface is BRI0/0
    0 lost fragments, 0 reordered, 0 unassigned, sequence 0x3/0x0 rcvd/sent
    0 discarded, 0 lost received, 1/255 load
    Member links: 2 (max not set, min not set)
    BRI0/0:1
    BRI0/0:2
    Capetown#show ppp multilink
    Virtual-Access1, bundle name is SanJose1
    Dialer interface is BRI0/0
    4-5

    CCNP 2: Remote Access v 3.0 - Lab 4.9.3

    Copyright 2003, Cisco Systems, Inc.

    0 lost fragments, 0 reordered, 0 unassigned, sequence 0x0/0x6 rcvd/sent


    0 discarded, 0 lost received, 1/255 load
    Member links: 2 (max not set, min not set)
    BRI0/0:1
    BRI0/0:2

    4. According to the output of this command, how many channels are participating in the bundle?

    __________________________________________________________________________
    __________________________________________________________________________

    5-5

    CCNP 2: Remote Access v 3.0 - Lab 4.9.3

    Copyright 2003, Cisco Systems, Inc.

    You might also like