Cisco Systems 1604 manual 3-17, Verify that the correct dialer map exists

Models: 1604

1 22
Download 22 pages 37.23 Kb
Page 17
Image 17
Step 3 Verify that the correct dialer map exists:

Chapter 3 Configuring the Cisco 1604 Router

Step 6—Testing the Cisco 1604 Connection to the Cisco AS5300

Step 3 Verify that the correct dialer map exists:

robo-austin#show dialer map

Static dialer map ip 10.1.254.1 name hq-sanjose (14085551234) on BRI0

Step 4 Ping the IP address assigned to the Cisco AS5300’s dialer interface. Note that the Cisco 1604 (robo-austin) quickly gets 4 of 5 pings back from the Cisco AS5300 (hq-sanjose). After the ping is sent, examine the background processes in the debug output that follows the ping example shown below:

robo-austin#ping 10.1.254.1 Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.1.254.1, timeout is 2 seconds:

.!!!!

Success rate is 80 percent (4/5), round-trip min/avg/max = 116/182/372ms robo-austin#

The following comments apply to the debug output example that follows:

a.See 08:03:55.

The source and destination IP addresses of the DDR dial cause display. (s=10.1.254.4, d=10.1.254.1)

b.See 08:03:55.

Hq-sanjose’s hunt group number is dialed. (Attempting to dial 14085551234)

c.See 08:03:55.

ISDN Setup is transmitted.

(TX -> SETUP pd = 8 callref = 0x2F)

d.See 08:03:55.

A synchronous data bearer capability displays. (Bearer Capability i = 0x8890)

e.See 08:03:55.

The outgoing LCP configuration request is made. (BR0:1 LCP: O CONFREQ [Closed] id 42 len 28)

f.See 08:03:55.

The incoming LCP configuration request wants to authenticate with CHAP. (AuthProto CHAP (0x0305C22305))

g.See 08:03:55.

The outgoing acknowledgment says this peer will do CHAP. (LCP: O CONFACK [REQsent])

h.See 08:03:55.

Both PPP peers have received LCP CONFACK. LCP is now open. (BR0:1 LCP: State is Open)

i.See 08:03:55.

Authentication phase is initiated by robo-austin.

(BR0:1 PPP: Phase is AUTHENTICATING, by the peer)

j.See 08:03:55.

Robo-austin accepts a CHAP challenge initiated by hq-sanjose. The device robo-austin is not authenticating hq-sanjose, which is the desired behavior for this scenario.

(BR0:1 CHAP: I CHALLENGE id 5 len 31 from "hq-sanjose")

(BR0:1 CHAP: O RESPONSE id 5 len 32 from "robo-austin")

Cisco IOS Dial Services Quick Configuration Guide

3-17

Page 17
Image 17
Cisco Systems 1604 manual 3-17, Verify that the correct dialer map exists