Overview
Robustel device deployments may require enabling ping detection through a configuration XML file when the same connectivity-monitoring settings must be deployed consistently or remotely. The steps below show how to start from an exported configuration, add the ping-detection block and import it through a supported method. In practice, the XML must preserve the required schema and use reachable targets to avoid false link recovery actions.
This guide explains how to configure ping detection using a config.xml file, which can be deployed via:
- RCMS platform
- Web UI
- USB drive
Complete Ping Detection Configuration Block
<ping>
<enable>true</enable>
<primary_server>8.8.8.8</primary_server>
<secondary_server>114.114.114.114</secondary_server>
<ipv6_primary_server>2001:4860:4860::8888</ipv6_primary_server>
<ipv6_secondary_server>2400:3200::1</ipv6_secondary_server>
<interval>300</interval>
<retry_interval>5</retry_interval>
<timeout>3</timeout>
<timeout_unit>second</timeout_unit>
<tries>3</tries>
</ping>
Parameter Explanation
- enable: Activates ping detection feature
- primary_server: Main IPv4 server to ping
- secondary_server: Backup IPv4 server to ping
- ipv6_primary_server: Main IPv6 server to ping
- ipv6_secondary_server: Backup IPv6 server to ping
- interval: Time between ping checks (300 seconds = 5 minutes)
- retry_interval: Time between retry attempts (5 seconds)
- timeout: How long to wait for response (3 seconds)
- tries: Number of attempts before marking as failed (3 tries)
Deployment Methods
- Access RCMS platform
- Navigate to device/group
- Upload configuration file
- Apply configuration
2. Via Web UI
- Access device web interface
- Go to System > Profile
- Upload config.xml
- Import
3. Via USB
- Place config.xml in "router" folder on USB
- Insert USB and power cycle device
- Wait for completion
Important Notes
- Modify server addresses according to your network
- Keep reasonable intervals to avoid excessive network traffic
- Consider timeout values based on network conditions
- Backup original configuration before changes
Conclusion
The workflow for enabling ping detection through a configuration XML file on Robustel device should be considered complete only when the imported profile is accepted and ping detection becomes active with the intended interface and targets. This enables repeatable link monitoring without configuring every field manually.