Network Storm blocked PM864 TCP ports,... PART 2
Thanks for your quick answer to my first question. I don't know how to use this forum yet and I don't know how to make another question related to a previus one. So I decided to make another question direct to you.
The problem I mentioned on my first question happend a month ago, I already asked to my ABB support Line but they have not sent me any answer yet.
We solved the phisical network loop, but the controller still has its two lower CPU TCP ports blocked.
The primary and secundary CPU are running OK, but the diagnostic shows NoCommunication with backup CPU for both ethernet port. Attached you'll find the controller logs.
Is it safe to use de RNRP tracer unblock command? Does it work for the lower CPU ports? Can you give an example how to use the command?
Network Interface 172.16.84.155 (255.255.252.0 ) : 00-00-23-0a-f4-02
Network Interface 172.17.84.155 (255.255.252.0 ) : 00-00-23-0a-f4-03
Backup Interface 172.16.86.155 (255.255.252.0 ) (default rule)
Backup Interface 172.17.86.155 (255.255.252.0 ) (default rule)
Toolport IP adress 192.168.255.254 (255.255.255.0 )
E 2013-11-16 15:00:14.722 RNRP Config error: Suspected network loop!! same msg received twice fr 172.16.84.158
Error=31, Param=0xac10549e LP=504
0x85eed0 (tNetTask): arpresolve: can't allocate llinfo0x85eed0 (tNetTask): arpresolve: can't allocate llinfo0x85eed0 (tNetTask): arpresolve: can't allocate llinfoI 2013-10-16 15:00:35.157: Ethernet port status(P-CN1 P-CN2 B-CN1 B-CN2)= ERROR OK WAR
I 2013-11-16 15:01:50.031: Ethernet port status(P-CN1 P-CN2 B-CN1 B-CN2)= OK OK WARNING OK
I 2013-11-16 15:01:51.032: Ethernet port status(P-CN1 P-CN2 B-CN1 B-CN2)= OK OK WARNING WARNING
E 2013-11-19 12:05:46.088 On Unit= 6.5.0 HWError C_246_CTRL_002 CON 0000 See HWTree Error 16#00000000 16#00000000
0x85eed0 (tNetTask): arpresolve: can't allocate llinfo0x85eed0 (tNetTask): arpresolve: can't allocate llinfo
Voted best answer
As mentioned previously, the by factory default active Network Loop (later called Storm) Protection was introduced first in version 5.1. It has been available since 5.0 SP2, but back then it had to be manually activated by manipulating the RNRP base address setting.
If this controller is 4.1 as stated before; it does NOT have loop/storm protection, only detection (i.e. it will report if it senses a loop, but it will not do anything to protect itself against the storm).
I suspect something else is wrong with the backup controller; you should probably try to stress your regional ABB support center for an answer. Send me an email (firstname.lastname@example.org) if you would like me to take a look into the support case (don't forget to specify the case number).
In 4.1 there exists no tool to unblock the ports since no ports will be blocked.
In 5.1, the following messages in the controller log signifies network storm detection and protection (the exact delays used and text reading depend on version and what ethernet capable module that detects the storm - not only the ethernet ports of the controller itself are monitored, e.g. the CI867 has storm protection as well):
I 2013-09-13 14:09:53.083 NSP: Blocking Ethernet port CN1 at limit 800 pkt/s
I 2013-09-13 14:09:59.083 NSP: Ethernet port CN1 is now unblocked
I 2013-07-19 09:26:08.910 (tNetTask)[SYS] NSP: High Ethernet load generated from addr 0:30:11:8:d1:ac
I 2013-07-19 09:26:09.574 (tNspTask)[SYS] NSP: Network Storm Protection is delaying tNetTask at limit 1000 packets/s
I 2013-07-19 09:26:15.574 (tNspTask)[SYS] NSP: tNetTask running without delay
Unblocking using RNRP Fault Tracer (aka RNRP Utility):