RNRP No data from Node and check diagnostic counters
I am getting following error but i don't have any issue with system performance , what is impact of these error
The "Check diagnostic counters" warning will be lit when twelve or more (12+) RNRP telegrams have been lost in transit during the last hour.
--> unless you have made interactions in the network that may explain the losses, consider the warnings true and take action to investigate your network.
The principle of RNRP is easy: each RNRP node sends a routing message every second on every network path. These small routing messages are multicasted = sent once but delivered to all nodes on the Layer 2 network, called area by RNRP. In parallel, RNRP expects to hear these messages from all the adjacent RNRP nodes on the same area. If these messages are interrupted, a "Path Down" (single path down) or "Node Down" (all paths down) is sensed after a short timeout.
Path/Node Down is triggered after three consecutive lost routing messages (defined by the Max No Of Lost Messages setting).
If only one or two messages are lost (but resumed before number three is lost) counts as a "lost message". Lost messages are hence a precursor to "Path/Node Down".
However, even if the "Path/Node Down" state is never reached, RNRP takes immediate action and reroute traffic to secondary path.
As the diagnostic counters counts every message, they can be used to sense a "bad network".
Examples of healthy counters:
For natural reasons, there will always be a small number of lost messages accumulated over time). Controllers running on half duplex connection (except for PM891 capable of full duplex) may show slightly more loss than regular computers because of naturally occurring collisions. As a rule of thumb; when on half duplex, up to a handful of percent of total traffic volume is OK to loose due to collision and half duplex related errors. However, links between computers and in between switches shall be made on full duplex where no losses are acceptable.
Suggestions: make sure your network hardware is healthy, check port counters for all nodes and network up/downlinks, check switch firmware, check that the computer network drivers are up-to-date (and of supported model when using VMware). You may be at a recent version of Windows or VMware, but the network drivers below may be old and/or flawed. Please check BIOS and driver versions and lookup the vendor for updates.
VMware has a guide for driver updates: https://www.vmware.com/resources/comp...
You need to lookup the VID and DID numbers (usually by logging in to ESXi via SSH and use CLI commands - use Google...).
After corrective measures, reset the diagnostic counters (there is a button for reset in the RNRP Network Status tool) and take a new same some hours later.