Disable loop protection in RNRP ver. 4.8
RNRP detect a loop in the network in one server.
How to do for disable loop protection in RNRP ver. 4.8, 800xA 5.1 ver. D?
Starting with version 5.1 RNRP became a mandatory function that need to exist between servers and clients.
If you disable RNRP, you will not be able to start a workplace and connect to the aspect server.
With RSS disabled, we have, as far as I can tell had no false loop detections.
If this only affect one server out of many, and you have not been able to find any looped packets (its not that easy...) in Wireshark recordings I suggest replacing the NIC card and/or update the NIC driver.
Please note that information about a loop is relayed to all adjacent nodes (and areas). A loop *indicated* in RNRP Monitor of 172.16.4.71 may have been sensed by another node on the network and relayed to this node.
A *locally* sensed & blocked loop is indicated in the RNRP Monitor in the following way:
|====== Network Area 1 ==== Distance 0 ==== Ethernet =========|
primary network (path0)= 172.16.4.0 ownNode=71
!! The Interface has been BLOCKED after loop detection !!
The C:\ProgramData\RnrpEvent.log also logs blocking. Notice that there are two kinds:
- Short block
29/5 *08:01:14.920 ConfError: Suspected network loop, short interface block made on area=1 path=0
29/5 *08:01:52.027 ConfError: Interface unblocked on area=1 path=0,
- Long block
29/5 *08:01:52.074 ConfError: Interface blocked after detected network loop on area=1 path=0!!
29/5 *09:01:46.165 ConfError: Interface unblocked on area=1 path=0,
The RNRP Fault Tracer has functions to view RNRP status and errors remotely:
1 - Search own networks for nodes with configuration or network errors
2 - Get configuration parameters and error logs from one node
However, you need to familiarize yourself with how these look *during* and *after* loop protection.
If this does not suffice, I suggest asking your regional ABB support center for assistance.