Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - BROADBAND ACCESS CONFIGURATION GUIDE 2010-10-12 Configuration Manual page 461

Software for e series broadband services routers broadband access configuration guide
Hide thumbs Also See for JUNOSE SOFTWARE FOR E SERIES 11.3.X - BROADBAND ACCESS CONFIGURATION GUIDE 2010-10-12:
Table of Contents

Advertisement

Copyright © 2010, Juniper Networks, Inc.
Table 79: PPP Disconnect Cause Codes (continued)
Code
Name
10
lcp mlppp mrru
not valid
11
lcp mlppp peer
ssn invalid
12
lcp callback
refused
13
authenticate
timed out
14
authenticate
mlppp name
mismatch
15
authenticate
protocol refused
16
authenticate
failure
Chapter 15: L2TP Disconnect Cause Codes
Description
The link attempted to join an existing MLPPP bundle whose peer
maximum received reconstructed unit (MRRU) did not match the
peer MRRU negotiated by the link.
Code 11 is not used; the short sequence number (SSN) option is not
supported.
Code 12 with direction 2 is generated when the following conditions
are met:
The peer initiates LCP termination without having proceeded to
NCP negotiation, and
Prior to the termination, the local LCP has responded with a
negative acknowledgement (NAK) to a callback option (LCP
option 13) from the peer.
The E Series LNS never generates code 12 with direction 1 because
the LNS never requests callback.
Authentication failed because the authentication protocol timed
out; either the CHAP Authenticate Response or the PAP Authenticate
Request was not received.
Code 14 is not used. Dynamic MLPPP bundling, which is the only kind
of MLPPP bundling supported for MLPPP/L2TP, uses the
authenticated name as part of the key for bundle selection. Therefore,
there will never be an unexpected authenticated name for an existing
MLPPP bundle.
No acceptable authentication protocol was negotiated by LCP.
Code 15 with direction 1 is generated if the peer rejected all of the
authentication protocols requested by the local LCP.
Code 15 with direction 2 is generated if the following conditions
are met:
The peer initiates LCP termination without having proceeded
beyond completion of NCP negotiation, and
During LCP negotiation, the local LCP responded with a NAK to
the final authentication protocol requested by the peer.
Code 16 with direction 1 is generated if the local authentication of
the peer fails (that is, the authenticator sent a PAP NAK or CHAP
Failure packet)
Code 16 with direction 2 is generated if the peer authentication of
the local LCP fails (that is, the authenticator received a PAP NAK
or CHAP Failure packet).
Note that there are a variety of causes for authentication failures,
including bad credentials (bad name, password or secret) and
resource problems.
423

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the JUNOSE SOFTWARE FOR E SERIES 11.3.X - BROADBAND ACCESS CONFIGURATION GUIDE 2010-10-12 and is the answer not in the manual?

This manual is also suitable for:

Junose 11.3

Table of Contents