
Configuring and Troubleshooting Bay Dial VPN Services
C-26 302272-A Rev. 00
Mar 16 15:26:32 bay_lac ppp[1321]: ppp:asy23:l2tp tunnel call established,
forwarding traffic to remote node
Mar 16 15:26:32 bay_lac ppp[1321]: ppp:asy23:PPP Forward PAP
Mar 16 15:26:34 bay_lac radlog[1376]: Sent RADIUS Accounting-Request to
132.245.54.20
Mar 16 15:26:34 bay_lac radlog[1376]: Received RADIUS Accounting-Response
from 132.245.54.20
Once the tunnel has been established, an entry is placed in the RAC’s Tunnel
Table, as the following example illustrates.
annex: net -T
Layer 3 BayDVS
Dev Proto State When Home Address HA Address Type WAN
Addr
Layer 2 L2TP
Remote Ids Local Ids
Dev State When End Pnt Address Serial Num Tunnel Call Tunnel
Call
asy23 EST 3:26pm 132.245.56.6 0x6c070000 24708 1 32951
32790
If the dial-in user is having problems establishing a connection, try to isolate the
problem by determining the point at which the protocol is failing. The sequence of
events from the LAC’s perspective appears in the following table.
Troubleshooting the LNS
Before the tunnel and session is established the LNS should be in the up state. You
should see the following message.
[2:1]$ log -eL2TP -fftwi
Event What to check
LAC accepts call syslog, callhist and actcall commands on
RAS
Queries BSAC/TMS Database and
receives successful response
syslog, BSAC Statistics screen, BSAC
Activity logs
LAC contacts LNS to establish a tunnel if
one doesn’t already exist.
syslog
LAC forwards PPP datagrams to LNS to
establish session for dial-in user.
Syslog, shows PPP activity
Comentarios a estos manuales