Overview
This guide explains setting up cellular ping detection on a Robustel device when a router must identify a stalled upstream connection even though the cellular interface still appears connected. It covers how to choose targets, detection intervals, failure thresholds and a recovery action. The key takeaway is that effective ping detection balances fast recovery against false triggers caused by a single unreachable server.
Why Ping Detection is Critical
Ping detection serves as an essential keep-alive mechanism for your RCMS (Remote Cloud Monitoring Solution) connectivity. This feature:
- Actively monitors real-time connectivity to the RCMS platform
- Identifies network disconnections immediately
- Initiates automatic reconnection procedures when communication fails
- Ensures accurate device status reporting
- Maintains system reliability and data integrity
Problems Prevented
Without proper ping detection, several critical issues can arise:
- "Ghost" devices appearing as connected in RCMS when actually offline
- Missed alerts and notifications
- Inaccurate device status reporting
- Delayed fault detection and response
- Unreliable monitoring data
Detailed Configuration Steps
1. Accessing the Configuration
- Login to your device's web interface
- Navigate through: Interface > Link Manager > WWAN1 settings
- Locate the Ping Detection Settings section
2. Basic Settings Configuration
- Enable/Disable: Set to "ON"
- Interval: 1800 seconds (maximum value). Defines how often the system should check connectivity
- Retry Interval: 5 seconds. Is wait time between retry attempts
- Timeout: 3 seconds. Period for a response before considering it failed
- Timeout Unit: Second(s)
- Max Ping Tries: 3. The maximum number of retry attempts
3. IPv4 Configuration
- Enable IPv4 Ping Detection
- Primary Server: Set to your RCMS Stack IP address
- Secondary Server (Optional): Configure with another reliable internal IP such as:
- Another RCMS server IP
- A stable SIM card IP from your private network
- Internal NTP server IP
- Any other reliable internal service IP
4. IPv6 Configuration
- Disable IPv6 under General Settings
- Leave IPv6 ping detection settings at their defaults
- Note: IPv6 settings will not affect operation when IPv6 is disabled
Best Practices
- Server Selection
- Always use servers within your private APN network
- Prioritize RCMS platform IPs as primary servers
- Select secondary servers that have confirmed 100% uptime
- Verify all IPs are part of your allowed endpoints
Configuration Maintenance
- Never disable ping detection once configured
- Regularly verify ping detection status
- Monitor system logs for any ping failures
- Keep backup server IPs updated
Troubleshooting Common Issues
If Ping Detection Fails
- Verify server IP addresses are correct and within your private APN
- Check if target servers are in your allowed endpoints list
- Confirm APN firewall rules allow ICMP traffic
- Review system logs for specific error messages
- Verify network coverage and signal strength
Network Considerations
- Ensure stable network connectivity
- Monitor data usage if relevant to your plan
- Check for any network restrictions or firewalls
- Verify APN settings are correct
Important Notes
- Keep ping detection enabled at all times
- Regular communication checks maintain accurate device status
- The system will automatically attempt reconnection after failed pings
- Monitor system logs periodically for any connection issues
- Update server IPs if your RCMS infrastructure changes
Support and Maintenance
- Document any changes made to the configuration
- Keep a record of working settings
- Maintain a list of reliable server IPs
- Regularly verify ping detection is functioning correctly
- Monitor system performance after any configuration changes
Remember: Proper ping detection configuration is crucial for maintaining reliable connectivity between your devices and the RCMS platform. It's not just a feature - it's a critical component of your monitoring infrastructure.
Conclusion
To complete setting up cellular ping detection on a Robustel device, verify that normal traffic produces stable successful checks and a simulated upstream failure causes the expected recovery behavior. This helps restore service automatically when the mobile data path stops passing traffic.