Chapter 3 Monitoring
3.1 Monitoring Communications with the Teldat-3Ge device
The L2TP tunnel monitoring commands can be accessed from the corresponding section in the monitoring process
(process 3), as shown below:
*process 3
+protocol l2tp
L2TP+
As already mentioned in chapter2 “Configuration” section 6) L2TP Tunnel, the tunnel-info all monitoring command
summarizes the L2TP general operations.
L2TP+tunnel-info all
Number of L2TP Tunnels: 1
Number of L2TP Sessions: 2
RemoteIP:172.24.78.28
LocalIP:0.0.0.0
Port:1701
RemoteName:ramfs-antennaeth
State:established
LocalID:52623
RemoteID:13425
Sessions:3
group 3
Pseudowire:ETH-ANT-MON
Interface:rcellular1
Sequencing:off
LAC
LocalID:20774
RemoteID:43001
State:
established
LastChange:4m35s
Events:Show
encaps:20
decaps:32
missed:0
dropped:0
Pseudowire:ETH-ANT-PPP
Interface:rcellular2
Sequencing:off
LAC
LocalID:52943
RemoteID:58150
State:
established
LastChange:4m35s
Events:Show
encaps:1
decaps:1
missed:0
dropped:0
Pseudowire:ETH-ANT-UPG
Interface:rcellular3
Sequencing:off
LAC
LocalID:14495
RemoteID:49170
State:
established
LastChange:4m35s
Events:Show
encaps:0
decaps:0
missed:0
dropped:0
L2TP+
In cases where the tunnel is not established (unlike the above capture, where the state is shown as correct according
to the State:established field) the router won’t have access to the Teldat-3Ge . The reasons for this abnormal beha-
vior can be one of two things:
• There is an element in the local network blocking the L2TP traffic.
• The DHCP negotiation between both devices has not completed correctly.
More detailed information on the DHCP negotiation can be obtained with the leases command (under the DHCP
server monitoring section):
L2TP+exit
+protocol dhcp
DHCP Protocol monitor
DHCP+server
DHCP-leases
========================================
..:: Currently assigned DHCP Leases ::..
========================================
172.24.78.28
hardware ethernet 00:a0:26:fe:98:89
start Thu Sep 06 2007 11:25:55
end Thu Sep 06 2007 23:25:55
uid 'teldat'
The Teldat-3Ge responds to the
ping
application. Therefore, you need to be able to obtain the responses to the
ping
command by sending this from the router to address 172.24.78.28, as in the example:
+ping 172.24.78.28
PING 172.24.78.28: 56 data bytes
64 bytes from 172.24.78.28: icmp_seq=0. time<1. ms
64 bytes from 172.24.78.28: icmp_seq=1. time<1. ms
3 Monitoring
Teldat S.A.
20
Teldat-3Ge Quick Guide