Suspected Network Loops errors of controller
Voted best answer
I can't see any loops in the drawing.
I assume the switches are of some professional brand?
Only comment is that router nodes (i.e. the connectivity servers) should carry same node number on all interfaces/areas. CS1 (172.16.4.21) should use 21 on the control network as well, i.e. 172.16.80.21. However, this has nothing to do with the loop detection.
Did you really rule our Receive Side Scaling, RSS being enabled on the NICs (RSS is known to cause false loop detection by RNRP)?
Please check your network!
What is the network's physical configuration?
Are you making use of the less preferred Spanning Tree Protocol (STP) or Rapid Spanning Tree Protocol (RSTP) in combination with a physical network consisting of loops?
ABB does not promote using STP nor RSTP and rings / meshed networks since the time to detect and stabilize is too long. STP may take up to a minute to resolve a closure of a previously open path.
I need more details about the network to be able to tell more.
Do also involve your regional ABB support center.
Somtimes due to some network issues loop can occur. immediately it will not get reset. In order to to reset the network loop, Double click on the RNRP icon which will open the RNRP Utiltiy tool , Go with option 7 and give IP of the node where you noticed the loop. Clear the loop and restart the node once.. If there is no physical loop this action will clear all old error events from RNRP.
Else you have trace out from networking side from each node to switch where the error reported
In CS2, their is 4 eth port, CN1-172.16.80.32 RSS- Enabled; CN2- 172.17.80.32 RSS- Enabled; PN1- 172.16.4.32 RSS not showing in list; PN2- 172.17.4.32 RSS not showing in list;
CS1 is not in line due to hardware problem;
AS1 and AS2 having 2 eth port, Both port RSS- Enabled
check the attach file may it help you to understand better.