ppp delay-lcp-negotiation

Function

The ppp delay-lcp-negotiation command delays the negotiation in the LCP phase.

The undo ppp delay-lcp-negotiation command cancels the delay for the negotiation in the LCP phase.

By default, the negotiation in the LCP phase is not delayed.

This command is supported only on the NetEngine 8000 F1A.

Format

ppp delay-lcp-negotiation [ force ]

undo ppp delay-lcp-negotiation

Parameters

Parameter	Description	Value
force	Sets the LCP delay negotiation type to force.	-

Parameter

Description

Value

force

Sets the LCP delay negotiation type to force.

Views

Virtual template view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
pppoebras	write

Usage Guidelines

Usage Scenario

If the Layer 2 network of the user is a ring network, packets transmitted across the network may be out of order, making users unable to go online normally. To ensure that the LCP negotiation packets sent by the arrive at the user later than the PPPoE packets, you need to delay the negotiation in the LCP phase. In this manner, packets exchanged between the and user are in correct order.

After you configure the ppp delay-lcp-negotiation command, the device sends the first LCP Request packet after the specified delay. If the force parameter is not specified, when the device receives an LCP Request packet from the user, the device will stop delay and instantly performs LCP negotiation. If the force parameter is specified, the device still delays LCP negotiation upon receipt of an LCP Request packet from the user.
If the does not receive the LCP Request packet from the peer within the specified time (3 seconds by default), the sends the first LCP Request packet after a delay of the specified time.
If the receives the LCP Request packet from the peer within the specified time (3 seconds by default), the responds to the request in real time and continues subsequent negotiation (in this situation, the ppp delay-lcp-negotiation command configuration is regarded as invalid).

Precautions

This command is supported only on the admin VS.

If the DSLAM sends the VBAS Response packet at a low speed, the required VBAS information cannot be encapsulated into the Request packet sent by the to the RADIUS server for authentication. To solve the problem, you can set the LCP delay negotiation type to force.

Example

# Delay the negotiation in the LCP phase on VT 9.

<HUAWEI> system-view
[~HUAWEI] interface virtual-template 10
[*HUAWEI-Virtual-Template10] ppp delay-lcp-negotiation