Configuring the Maximum Number of Renegotiation Attempts from a PPP Client

You can optionally configure the maximum number of renegotiation attempts from LCP, IPCP, and IPv6CP before terminating a session. Configuring the maximum number of renegotiation attempts helps prevent massive renegotiation loops between the router and a noncompliant PPP client. Such renegotiation loops can cause excessive CPU utilization and can prevent the PPP client from coming up properly.

When a PPP client exceeds the configured maximum number of renegotiation attempts, the router sends a termination request to end the PPP session. When the PPP session is terminated and LCP goes into a stopped (closed) state, static PPP or MLPPP interfaces go into passive mode and wait for the other side of the connection to start the LCP negotiation process.

When both IPv4 interface columns and IPv6 interface columns are configured over a PPP link-layer interface, the router terminates the PPP session only when the PPP client exceeds the configured maximum number of renegotiation attempts for both the IPv4 interface and the IPv6 interface.

You can configure the maximum number of renegotiation attempts from the Interface Configuration Mode, the Subinterface Configuration mode, and the Profile Configuration mode.

Note: If you do not specify the optional lcp, ipcp, or ipv6cp keyword, the ppp max-negotiations command sets the maximum number of renegotiation attempts for each of LCP, IPCP, and IPv6CP to the value you specify, or to the default value (30) if you omit the optional value for maximum renegotiation attempts.

To configure the maximum number of renegotiation attempts for LCP, IPCP, and IPv6CP:

• (Optional) From the Interface Configuration mode, specify the following command:
  host1(config-if)#ppp max-negotiations 15

  Use the no version to restore the default value, 30 renegotiation attempts for LCP, IPCP, and IPv6CP.

Related Documentation

• ppp max-negotiations