How to Troubleshoot Link Detection Configuration Errors

Applicable Versions

RG-WALL1600-Z series firewalls running NTOS1.0R8P1 or earlier.
Principle:
The link detection functionis implemented using Track and RNS, and pay attention to the following content:
The logic for using RNS and track together:
First, configure an MS object and choose to periodically send either ICMP Echo or DNS packets, based on the capabilities of the devices at both ends of the link.
Next, create a track object to monitor the status of the MS object. If the MS object receives a response to its packets, the track object’s status will be "Up";if not, it will be "Down".
Finally, associate the track object with actual functional modules, such as policy-based routing (PBR) or VRRP protocols. This allows you to detect if a monitored link fails, so that PBR can be disabled or switched to another path, and VRRP can perform a failover.
On the web interface, a link detection is a track object and the detection nodeassociated with it is an RNS object.

Configuration Errors

Due to the design, the following configuration errors may occur in link detection configuration:
Error1: The Enable switch is not toggledon for the RNS module during configuration.

Error 2: The relationship between track objects and RNS objects is not clearly understood.
For example, if a customer wants to route traffic over the Gi0/7 and Ten Gi0/0 interfaces and achieve automatic switching when either link becomes unstable, they might configure a single track object to be associated with both RNS objects.

The correct configuration is to create a separate track object for each interface and then associate each track object with its corresponding RNS object.

Error 3: The track object is not associated with an interface or route.
The track module receives link detection results from the RNS module and notifies the service module. The service module must be manually associated with thetrack module to receive these results.