Table 79: PPP Disconnect Cause Codes
(continued)
Description
Name
Code
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.
lcp mlppp mrru
not valid
10
Code 11 is not used; the short sequence number (SSN) option is not
supported.
lcp mlppp peer
ssn invalid
11
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.
lcp callback
refused
12
Authentication failed because the authentication protocol timed out;
either the CHAP Authenticate Response or the PAP Authenticate
Request was not received.
authenticate
timed out
13
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.
authenticate
mlppp name
mismatch
14
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.
authenticate
protocol refused
15
■
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.
authenticate
failure
16
L2TP Disconnect Cause Codes
■
419
Chapter 15: L2TP Disconnect Cause Codes
Summary of Contents for JUNOSE 11.0.X MULTICAST ROUTING
Page 6: ...vi...
Page 28: ...xxviii Table of Contents JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 36: ...xxxvi List of Tables JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 42: ...2 Managing Remote Access JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 204: ...164 Managing RADIUS and TACACS JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 292: ...252 Monitoring RADIUS Relay Server JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 336: ...296 RADIUS Client Terminate Reasons JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 368: ...328 Managing L2TP JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 444: ...404 PPP Accounting Statistics JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 494: ...454 Managing DHCP JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 510: ...470 DHCP Local Server Configuration Tasks JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 556: ...516 Configuring DHCP Relay Proxy JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 616: ...576 Managing the Subscriber Environment JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 674: ...634 Managing Subscriber Services JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 767: ...Part 7 Index Index on page 729 Index 727...
Page 768: ...728 Index JUNOSe 11 0 x Broadband Access Configuration Guide...