DNS Server 1: 172.33.0.59
DNS Server 2: 172.33.0.60
Factory Floor Airlink:
Device IP: 10.125.216.99 (port 9191)
IP Netmask: 255.255.255.0
Ethernet Port Configuration: Port 1 → WAN
From the server I can ping the airlink. I can remote into the airlink using 10.125.216.99:9191 and the login.
However, when I send a message from the server (using software Ignition over port 17141/17142) the message never arrives.
I know this isn’t because of the airlink as I can connect directly to the airlink and send messages from a copy of Ignition running on my laptop.
The traceroute from the server to the airlink has 4 hops:
169.254.0.5
192.168.255.2
10.120.0.1
10.125.216.99 ← this is the airlink
Can anyone explain what I am doing wrong or what settings I have setup incorrectly in the airlink? I am guessing this is related to host port routing settings but I don’t know what I need to set them to.
How do you use Ignition software to send SMS? Please provide more details.
→ I understand that the issue happens when you uses the Ignition software to send SMS, so, if you use a phone or any other device with a SIM card as usual to send SMS to the router, does the issue occur or not?
The Ignition User Manual describes how the Ignition server is setup and the second link describes how Ignition recommends the airlink RV50 be setup (RV55 is similar). However, not many of the settings in this guide are being used currently since they didn’t allow network traffic.
External devices can successfully send messages to the RV55.
RV55 is connected to local plant wi-fi and also plugged in through port 1. Last night we modified some settings on the LAN tab.
Ethernet:
Device IP: 10.125.216.99
IP Netmask: 255.255.255.0
DHCP Mode: Auto
DHCP Starting IP: 10.125.216.99
DHCP Ending IP: 10.125.216.100
Port 1 Port Mode: LAN
The weird thing is these new settings worked in allowing traffic from serverA to the airlink RV55. However, traffic cannot get from the airlink RV55 to the serverA.
What I don’t understand is why DHCP mode being in Auto would matter? I am happy to assign a static IP address.
The other weird setting is the Proxy ARP being enabled.
And finally disabling any of the routing settings makes the test fail again and no traffic is allowed.
“Auto - When the router is powered on or reboots, it attempts to determine if a DHCP server is present on the Ethernet network. If a DHCP server is found, the router obtains an IP address from the DHCP server. If no DHCP server is found, the port acts as a bridged LAN connection.”
I am confident a DHCP server does exist however since I assigned an IP address why would I need to obtain an IP address from the DHCP server?
In the Host Port Routing section of the manual
“When enabled, the AirLink router responds to Address Resolution Protocol (ARP) requests to resolve WAN addresses for devices on the connected LANs. In doing so, the router becomes the primary gateway for connected LANs.”
I have this enabled now. However the manual then states:
“Ethernet - Select this option if the network uses a router that acts as an ARP proxy for addresses on subnets connected to it. Note: If proxy ARP is not enabled on the router, the transmission fails (destination unreachable).”
Again, not sure if airlink is responding to ARP from somewhere to resolve the IP address I set the airlink to.
If other devices can send SMS to the RV50 successfully, it might be an issue with the server or software.
Therefore, I suggest it’s best to recheck on the software forum or seek assistance from the server side.
Hello, did you get the solution?
I’m having the same kind of problem here, I followed the Ignition manual and didn’t work.
I only can send SMS using PuTTY from the laptop connected to the Airling, I can’t ping from the network.
I’m attempting to use the Sierra Wireless RV55 router to send SMS messages through Ignition SCADA (by Inductive Automation). In Ignition, I’ve set up an alarm notification pipeline that contains the SMS message content and the recipient’s phone number. The RV55 is connected to our server via Ethernet, and the idea is that when an alarm is triggered in Ignition, it sends the SMS message to the RV55, which then relays it to the intended phone number.
However, the problem is that while Ignition appears to be sending the message, the RV55 does not seem to receive it. Eventually, the message attempt times out within Ignition. This suggests that communication between Ignition and the RV55 is failing.
After RV55 boots up, please:
a. Start IP Logging on RV55 device by using the option ‘tcpdump -vvnnXi any’ in IPlogger_sample.cmd in the attachment. Please refer to the attached user guide for detailed information. How to set up IP Logging.zip (151.1 KB)
b. Send SMSs from Ignition to RV55.
c. Stop IP Logging and Click the Download IP Logging File.
d. Then share the log file, template file and IP logging file with me.
*The configuration template file is in ACEmanager → Template, provide any name you desire for the Template Name, and then press Download to retrieve the template file.
*Go Admin → View log → Download Logs
The topology diagram would be almost similar to the one I attached above.
RV55 IP address: 10.0.110.250
Subnet Mask: 255.255.255.0
Ignition Gateway IP: 10.0.20.117
Also, the Cisco switch to which RV55 is connected to the company server is on gateway: 10.0.110.1
Ignition ports to send and receive message 17341 and 17342 respectively.
No, I cannot ping the RV55 through my ignition gateway or through CMD until I am physically connected to the RV55 using a USB cable (or ethernet but I use USB because the ethernet cable is connected to the Cisco Switch).
SMS Mode: Control and Gateway
I am not able to attach the files in this chat for some reason so I will provide you with the link and you can download it from there.
Thank you Jerdung, please let me know if you need any more information
After checking your log that you sent me, I found that the gateway did not receive any UDP packet from SMS server. It appears that there is a network issue. Please check your network again.
