Specifications

67 / 80
 Test 8: Test the SCADA server’s connection to eth1 interface of M2M GW.
16.2.7. End-to-end connectivity
Last, test the SCADA server’s ability to connect to the Ethernet (or serial) device in Arctic’s LAN.
There are two options, a) Ethernet end device or b) Serial end device. Test the one that matches
your setup.
Ethernet device
• Ping the Ethernet device (10.10.10.2) from SCADA server.
• Test the SCADA control software’s ability to connect to the device (RTU, remote
terminal unit) that is controlled. In this example the RTU is referred as the “Ethernet
device”.
 Test 9 a: Test the SCADA server’s connection to end device, connected to Arctic via Ethernet.
Serial device
If the RTU is serial connected, you will need to use the Arctic’s VPN peer address (172.16.0.2 in
this example) and the port where the Arctic’s serial GW listens to the connections coming from
SCADA server.
Configure the Arctic’s serial GW to match the TCP/UDP port that is used by SCADA rather than
changing the SCADA port that is used for connecting the RTU. Refer to the SCADA documentation
for finding a proper TCP/UDP port.
 Test 9b: Test the SCADA server’s connection to end device, connected to Arctic via serial line.
The tests above will help you to verify the communication path segment by segment. If some
segment fails the test, it is easier to focus the troubleshooting efforts to the particular segment.
16.2.8. Log files
This step is not belonging to the actual testing phase but will rather give additional information on
how the VPN connections are seen in log files.
In M2M GW, the information related to VPN tunnels can be seen in the following log files, you can
list them in M2M GW’s GUI Æ Others Æ Command shell.
• SSH-VPN tunnels
Log file: /var/log/secure
command: tail -100 /var/log/secure
• L2TP tunnels
Log file: /var/log/tunnel
command: tail -100 /var/log/tunnel
The “-100” in “tail” command will define that last 100 lines of the file is shown. To see the whole file,
use the command “cat”, e.g. cat /var/log/tunnel.
The log files will indicate the login attempts of the Arctics, therefore, the log markings are a good
indication whether the Arctics are able to at least try the login and VPN tunnel establishment.
Examples:
The incoming SSH-VPN connection attempt from Arctic will show in /var/log/secure as
follows:
Mar 26 09:12:24 m2mgw sshd[<PID>]: Connection from <GPRS IP address> port <port>
The established SSH-VPN connection will show in /var/log/secure as follows:
Mar 24 03:34:17 m2mgw sshd[<PID>]: Accepted rsa for vvpn from <GPRS IP address> port <port>