Technical data

Cisco 1604 Configuration 3-15
Step 6—Testing Connections to the Cisco AS5300
Figure 3-2 shows the actual test lab environment used in this test case.
Figure 3-2 Test Lab Environment
Step 1
Turn on the appropriate debugging. Examining the background processes is essential for
effective troubleshooting.
robo-austin# undebug all
All possible debugging has been turned off
robo-austin# terminal monitor
robo-austin# debug dialer
Dial on demand events debugging is on
robo-austin# debug isdn q931
ISDN Q931 packets debugging is on
robo-austin# debug ppp negotiation
PPP protocol negotiation debugging is on
robo-austin# debug ppp authentication
PPP authentication debugging is on
robo-austin# debug ip peer
IP peer address activity debugging is on
Step 2 Verify that your routing table points to the hq-sanjose network access server (NAS):
robo-austin# show ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route, o - ODR
Gateway of last resort is 10.1.254.1 to network 0.0.0.0
10.0.0.0/24 is subnetted, 2 subnets
C 10.1.4.0 is directly connected, Ethernet0
C 10.1.254.0 is directly connected, BRI0
S* 0.0.0.0/0 [1/0] via 10.1.254.1
PSTN/ISDN
15988
Cisco AS5300
(hq-sanjose)
DNS server
10.2.2.3
BRI
BRI
Ethernet
Cisco 1604
(robo-austin)
RS-232
console
Administrator's PC
(configuration and logging)
Test PC
10.1.4.2
10.1.254.4
10.1.254.1