Appendix B: Log Messages
Negot not converging level 2
Negotiation of the LCP layer is unattainable due to misconfiguration or the Ex- press L768/L1.5 or PPP peer is requiring authentication and the other is refus- ing.
No IP addr for peer level 2
The Express L768/L1.5 cannot continue the connection because there was no IP address received from the PPP peer or it was not set in Configuration/Con- nection List/IP/Route/IP/Net parameter.
No Response from peer level 2
The Express L768/L1.5 has dialed or answered a call and no PPP negotiation packets were seen.
PAP authen failed level 3
The PPP peer has rejected the Express L768/L1.5’s username and/or pass- word used for authenticating. Check to make sure the Configuration/Con- nection List/Authentication parameters Tx Method, Tx Username, and Tx Password are correct.
Peer failed CHAP authen level 3
The PPP peer’s reported CHAP username and/or password does not match the Express L768/L1.5’s parameters. This is most likely caused by PPP peer sending an incorrect username and/or password. Make sure the Configura- tion/Connection List/Authentication parameters Rx Username and Rx Pass- word are correctly entered. Also, if using RADIUS, check that the server is configured and running properly.
Peer failed EAP authen level 3
The PPP peer’s reported EAP username and/or password does not match the Express L768/L1.5’s parameters. This is most likely caused by PPP peer send- ing incorrect username and/or password. Make sure the Configuration/Con- nection List/Authentication parameters Rx Username and Rx Password are correctly entered. Also, if using RADIUS, check that the server is configured and running properly.
Express L768/L1.5 User Manual | 93 |
