The tunnel password was not configured in the L2TP group at the local end but peer device was configured.ĭisable tunnel authentication on the peer device.Ĭheck the public network interface status and public network route on the local device. The tunnel has been set up or was idle when the SCCCN packet was received. The tunnel has been set up when the SCCRP packet was received. The tunnel has been set up when the SCCRQ packet was received Obtain SCCCN messages to locate the fault.
The received SCCCN packet failed to pass the check. Obtain SCCRP messages to locate the fault. The received SCCRP packet failed to pass the check. Obtain SCCRQ messages to locate the fault. The received SCCRQ packet failed to pass the check. No user goes online in the L2TP client-initiated scenario and the tunnel ages out. Table 1-1 Possible causes of L2TP tunnel establishment failures and handling suggestions 00:13:03.050 Peer Addr: L2TP tunnel-down-reason: a StopCCN packet was received. 00:06:14.540 Peer Addr: L2TP tunnel-down-reason: the received SCCN packet failed to pass the check. You can also locate the fault according to the sections in this chapter. Then, perform troubleshooting according to Table 1 Possible causes of L2TP tunnel establishment failures and handling suggestions. If no tunnel information is displayed in the command output, run the display l2tp tunnel-down-reason command (in V200R010 and later versions) to locate the cause of the L2TP tunnel establishment failure.LocalTID RemoteTID RemoteAddress Port Sessions RemoteName The following shows a sample command output on the LNS: display l2tp tunnel Total tunnel : 1
In this case, you can run the display l2tp tunnel command on the faulty device to check information about L2TP tunnels established on it. In the client-initiated, L2TP client-initiated, or NAS-initiated connection scenario, an L2TP VPN has been configured between devices but PCs connected to the devices cannot communicate with each other.
0 kommentar(er)
