Controller one Port Faulty
In one of our projects, in the RNRP status display we are getting "Socket error=67, Send Failed to 172.16.80.2".
RNRP Fault tracer Screen shot is also attached for suggestion and help, if any.
RNRP fault tracer does not tell date & time of errors found.
Save the output and reset all logs on area by using "Change settings", use 239.239.239.area number and then give clear command. Can't remember if its 188.8.131.52 or 184.108.40.206 for area 20, try until RNRP monitor show command being executed (=log cleared). Verify logs to be empty by searching once more.
Repeat fault tracer reading some time later. Only new errors should be listed now.
If errors continue:
1. Check Total CPU load (<90% for PA controller, <80% for HI)
2. Check Cyclic Load (<70%, <65% is even better to maintain some reserve capacity)
3. Check number of MMS/s (use Control Builder M->Remote System->Show MMS...)
4. Check switch port statistics; at half duplex (all but PM891) allow one or two percent errors (CRC, collisions, etc) of total volume. E.g. divide number of collisions with total sent telegrams to get % collision, etc) but not more. At full duplex (PM891 only) accept no or only handful of errors. Save & Reset statistics. Check again some time later to see if problem was old or is ongoing. If some port has higher errors than others, consider moving controller to other port to rule out switch port being defective. Even cables can become necessary to replace. Avoid long cables since it increases risk for disturbances and voltage potential travelling in shield of STP/FTP cable (cut shield in one end to avoid ground current, but basically it is recommended to have controller and switch very close to avoid potential differences)
5. Extract controller logs. Save them.
6. Check that proper task tuning is made (no fat tasks with >100 ms execution time) and that ~20 ms Task Offset or more is given between tasks to allow communication in between program execution (which has higher precedence than attending to network interfaces)
File support case with regional ABB in case you can't figure out what is causing the network disturbances.