Juniper JUNOSE SOFTWARE 11.2.X - BROADBAND ACCESS CONFIGURATION GUIDE 7-20-2010 Configuration Manual page 452

JunosE 11.2.x Broadband Access Configuration Guide
414
Table 79: PPP Disconnect Cause Codes (continued)
Code Name
1 admin
disconnect
2 renegotiation
disabled
3 normal
disconnect
4 compulsory
encryption
refused
5 lcp failed to
converge
6 lcp peer silent
7 lcp magic
number error
8 lcp keepalive
error
9 lcp mlppp
endpoint
discriminator
mismatch
Description
The disconnection was a result of direct administrative action,
including:
The administrator shut down the network or link interface.
The administrator logged out the subscriber.
Code 2 is not used; the E Series LNS is always capable of
renegotiating LCP if proxy data is not available.
Indicates that one of the following events occurred:
user-initiated logout (direction 1)
session timeout (direction 2)
inactivity timeout (direction 2)
address lease expired (direction 2)
The E Series LNS determines by inference that a normal disconnect
has occurred for direction 1. The LNS does this when the peer initiates
LCP termination after proceeding beyond the successful negotiation
of LCP (that is, after starting authentication signaling or NCP
negotiation).
Code 4 with direction 2 is generated if the following conditions are
met:
The peer initiates LCP termination without having proceeded
beyond the completion of LCP negotiation, and
Prior to receiving the terminate request from the peer, the local
LCP has sent a Protocol Reject in response to any packet for
Encryption Control Protocol (ECP) protocols (protocol codes
0x8053, 0x8055) from the peer.
Code 4 with direction 1 is never generated, because the E Series LNS
never requests ECP.
An LCP configuration error prevented LCP from converging; the two
peers attempted to negotiate but did not agree on acceptable LCP
parameters.
LCP negotiation timed out; the LNS did not receive any LCP packets
from the LAC.
A magic number error was detected; this indicates a possible looped
back link.
The keepalive drop count was exceeded.
Code 9 is not used. Dynamic MLPPP bundling, which is the only kind
of MLPPP bundling supported for MLPPP/L2TP, uses the endpoint
discriminator as part of the key for bundle selection. Therefore, there
will never be an unexpected endpoint discriminator for an existing
MLPPP bundle.
Copyright © 2010, Juniper Networks, Inc.