6-65
Configuring the Data Link Layer Protocol for E1, T1, and Serial Interfaces
Troubleshooting Logical Interfaces
When a peer successfully authenticates itself, the authenticator returns an
Authen-Ack:
2005.07.08 09:05:08 PPP.AUTHENTICATION PPPtx[t1 1/1] PAP: Authen-Ack ID=1
Len=10 Message(Hello)
Note Usernames and passwords are case-sensitive.
Troubleshooting CHAP. If you are using CHAP authentication, look for
messages such as those shown in Figure 6-26.
Figure 6-26. CHAP Authentication Messages
The Challenge message indicates which router requires the other to authenti-
cate itself. In this example, the router with the hostname Local authenticates
Remote. (The PPPtx also indicates that the local router transmits the chal-
lenge.) The Failure message indicates that Remote could not correctly identify
itself.
View the running config for the interface (show run int ppp <interface
number>) and look for miskeyed passwords.
If the local router cannot authenticate itself, check the ppp chap hostname
and ppp chap password. If they seem correct, contact the remote site or ISP
and explain your problem.
If the remote router cannot authenticate itself, check the ppp username and
password in the running config, which may have been miskeyed. If they are
correct, contact the remote site and inform the network administrator that the
router is sending the wrong authentication information.
Note Usernames and passwords are case sensitive.
ProCurve# debug ppp authentication
2005.07.08 08:59:02 PPP.AUTHENTICATION PPPtx[t1 1/1] CHAP: Challenge
ID=1 Len=28 ValLen=16 Name(Local)
2005.07.08 08:59:02 PPP.AUTHENTICATION PPPrx[t1 1/1] CHAP: Response
ID=1 Len=25 ValLen=16 Name(Remote)
2005.07.08 08:59:02 PPP.AUTHENTICATION PPPtx[t1 1/1] CHAP: Failure
ID=1 Len=4 Message()
Peer’s hostname
To Next Page
Loading...
Need help?
General
