CHAPTER 15
L2TP Disconnect Cause Codes
L2TP Disconnect Cause Codes
Copyright © 2010, Juniper Networks, Inc.
L2TP Disconnect Cause Codes on page 413
Table 79 on page 413 describes the Point-to-Point Protocol (PPP) disconnect cause codes
that are displayed by the show l2tp received-disconnect-cause-summary command,
sorted by code number. For additional information, see RFC 3145.
Table 79: PPP Disconnect Cause Codes
Code
Name
0
no info
Description
Code 0 includes disconnect causes that are not specifically identified
by other codes. This code is generated in the following circumstances:
Internal resource constraints (for example, excessive load or
reduced resource availability) have prevented the generation of
a more specific disconnect code.
RFC 3145 does not define a disconnect code that corresponds to
the cause of the disconnection.
The following list shows current disconnection causes on an E Series
LNS that do not have a specific disconnect cause codes:
The peer initiated termination of LCP after the completion of LCP
negotiations, but prior to proceeding to authentication of NCP
negotiation. No conditions occurred that enabled the LNS to infer
a more informative disconnect code.
The peer initiated renegotiation of LCP.
Invalid local MRU (for example, MRU negotiation has been
disabled, but the lower MRU is less than the default MRU of 1500).
Unexpected local MLPPP MRRU for existing bundle (RFC 3145
code 10 covers peer MRRU mismatches, but not local
mismatches).
Authentication failures not covered by any of the
authentication-related codes (codes 13-16), such as:
Authentication denial of the local LCP by the peer
Local authentication failure due to no resources
Local authentication failure due to no authenticator
413