Lab 2.5.

3 Configuring an Asynchronous Dialup PPP

Objective
In this lab, the student will configure two Cisco routers to connect to each other asynchronously
using PPP. Two Cisco routers will also be configured to support in-band user sessions through
modems connected to the SanJose1 and Capetown serial interfaces. The student will configure the
asynchronous connections to support PPP encapsulation and Dial-on-demand routing (DDR).
Configure each router with their respective hostname and Fastethernet IP Addresses. Configure
each workstation with the correct IP address and default gateway.

Scenario
The International Travel Agency wants to allow Capetown to access to the company headquarters,
SanJose1. Capetown needs only occasional access to company email. As the network administrator,
configure a dial-up PPP connection between the two sites. When finished, Capetown must be able to
establish a DDR connection to SanJose1. Verify this configuration by pinging between the Capetown
Host B and the SanJose1 Host A.

Step 1
Before beginning this lab, it is recommended that each router be reloaded after erasing its 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 serial interfaces on either
router yet. Use the Adtran Atlas 550 or similar device to simulate the PSTN. If the Atlas 550 is used,
be sure the line cables from both modems are plugged into the octal FXS voice module ports of the
Atlas 550 as labeled in the diagram. Also, be sure to configure both workstations with the correct IP
address and default gateway, router Fa0/0 IP address.

1-5 CCNP 2: Remote Access v 3.0 - Lab 2.5.3 Copyright  2003, Cisco Systems, Inc.
Step 2
Configure the serial interface on Capetown for an asynchronous connection as follows:

Capetown(config)#interface serial 0/1

Capetown(config-if)#physical-layer async
Capetown(config-if)#ip address 192.168.8.3 255.255.255.0
Capetown(config-if)#encapsulation ppp
Capetown(config-if)#async mode dedicated

Notice that the serial interface uses PPP encapsulation.

1. What is the default encapsulation type for a serial interface when in physical-layer async mode?
__________________________________________________________________________
__________________________________________________________________________
The async mode dedicated command puts the interface in dedicated asynchronous network
mode. In this mode, the interface will only use the specified encapsulation, which is PPP in this case.
An EXEC prompt does not appear, and the router is not available for normal interactive use.
Since a low-bandwidth dialup connection is being configured, turn off CDP updates to reduce
bandwidth usage as follows:

Capetown(config-if)#no cdp enable

Enter additional commands, as follows, so that Capetown can dial SanJose1:

Capetown(config-if)#dialer in-band

The dialer in-band command specifies that the interface will support DDR.

Capetown(config-if)#dialer idle-timeout 300

The dialer idle-timeout command specifies the number of seconds the router will allow the
connection to remain idle before disconnecting. The default is 120 seconds.

Capetown(config-if)#dialer wait-for-carrier-time 60

The dialer wait-for-carrier-time command specifies the length of time the interface waits
for a carrier when trying to establish a connection. The default wait time is 30 seconds. The routers
in this lab will use a chat script to initialize the modem and cause it to dial.
Note: A chat script will be configured later in this step. On asynchronous interfaces, the dialer
wait-for-carrier-time command essentially sets the total time allowed for the chat script to
run.

Capetown(config-if)#dialer hold-queue 50

The dialer hold-queue command is used to allow outgoing packets to be queued until a modem
connection is established. If no hold queue is configured, packets are dropped during the time
required to establish a connection. The 50 in this command specifies 50 packets.

2-5 CCNP 2: Remote Access v 3.0 - Lab 2.5.3 Copyright  2003, Cisco Systems, Inc.
 Capetown(config-if)#dialer-group 1

The dialer-group command controls access by configuring an interface to belong to a specific

dialing group. In Step 3, the dialer-list command will be used to configure interesting traffic that will
trigger DDR for interfaces belonging to group 1.

Capetown(config-if)#dialer map ip 192.168.8.1 name SanJose1 modem-

script hayes56k broadcast 5556001

This dialer map command creates mapping between an IP address and the phone number that
should be dialed to reach that address. It also tells the router to use the appropriate chat script. Chat
scripts are used in DDR to issue commands to dial a modem and log on to remote systems.
Return to the global configuration mode to define the chat script. The following command should be
used with Hayes 56K Accura modems:

Capetown(config)#chat-script hayes56k ABORT ERROR "" "AT Z" OK "ATDT \T"

TIMEOUT 30 CONNECT \c

Step 3
Once the serial interface and chat script have been configured for asynchronous PPP, configure the
following line parameters:

Capetown(config)#line 2
Capetown(config-line)#speed 115200
Capetown(config-line)#flowcontrol hardware
Capetown(config-line)#modem inout
Capetown(config-line)#transport input all
Capetown(config-line)#stopbits 1

1. What is the default number of stopbits on a line?

__________________________________________________________________________
__________________________________________________________________________

Step 4
On Capetown, define interesting to establish a dial-up connection for IP traffic as follows:

Capetown(config)#dialer-list 1 protocol ip permit

Since this dialer list is number 1, it is linked to dialer group 1. The dialer-list command specifies
the traffic that is to be permitted on interfaces that belong to the corresponding dialer group.
In order for Capetown to route traffic through the Serial 0/1 interface, configure this default route to
the central site as follows:

Capetown(config)#ip route 0.0.0.0 0.0.0.0 192.168.8.1

This completes the Capetown router configuration.

3-5 CCNP 2: Remote Access v 3.0 - Lab 2.5.3 Copyright  2003, Cisco Systems, Inc.
Step 5
Configure the company headquarters router, SanJose1. Enter the following commands:

SanJose1(config)#interface s0/1
SanJose1(config-if)#physical-layer async
SanJose1(config-if)#ip address 192.168.8.1 255.255.255.0
SanJose1(config-if)#encapsulation ppp
SanJose1(config-if)#async mode dedicated
SanJose1(config-if)#no cdp enable
SanJose1(config)#line 2
SanJose1(config-line)#speed 115200
SanJose1(config-line)#flowcontrol hardware
SanJose1(config-line)#modem inout
SanJose1(config-line)#transport input all
SanJose1(config-line)#stopbits 1
SanJose1(config-line)#modem autoconfigure discovery
SanJose1(config)#ip route 192.168.216.0 255.255.255.0 192.168.8.3

Step 6
Write the SanJose1 and Capetown configurations to NVRAM and reload the routers. Power cycle the
modem and the Adtran Atlas 550. This will help avoid potential problems due to residual
configurations.

Step 7
From the Capetown Host B, ping the SanJose1 Host A (192.168.0.2). The first set of pings will fail
because the modems must perform the handshaking sequence to establish a connection
(approximately 20 seconds). Once a connection is established, issue the ping command a second or
third time. Eventually the ping should be successful which means the Capetown Host B has dialed
the SanJose1 Host A and the configuration is working. Troubleshoot, as necessary.
Once successful pings have been verified, issue the show dialer command on Capetown. The
following is a sample output:

Capetown#show dialer

Serial0/1 - dialer type = IN-BAND ASYNC NO-PARITY

Idle timer (300 secs), Fast idle timer (20 secs)
Wait for carrier (60 secs), Re-enable (15 secs)
Dialer state is data link layer up
Dial reason: ip (s=192.168.216.2, d=192.168.0.2)
Time until disconnect 217 secs
Connected to 5556001
Dial String Successes Failures Last DNIS Last status
5556001 1 0 00:04:19 successful

1. What is the dialer type of S0/1?

__________________________________________________________________________
__________________________________________________________________________
2. What is the dialer state?
__________________________________________________________________________
__________________________________________________________________________

4-5 CCNP 2: Remote Access v 3.0 - Lab 2.5.3 Copyright  2003, Cisco Systems, Inc.
 3. What is the dial reason?
__________________________________________________________________________
__________________________________________________________________________
4. How much longer will this connection remain up if it is idle?
__________________________________________________________________________
__________________________________________________________________________

5-5 CCNP 2: Remote Access v 3.0 - Lab 2.5.3 Copyright  2003, Cisco Systems, Inc.