RNRP, SystErrLog and ConfError
The commuincation with AS,CS,client and AC800M controllers are working good.
When checked the RNRP configuration and network errors for each controllers, many started showing and I was not able to get what these error numbers relates to.
Please check the attachment.
Voted best answer
The information returned by the RNRP Utility's "Search own networks for nodes with configuration or network errors" function does not contain any time stamps - hence the problem(s) reported may be old, perhaps due to some explainable network errors in the past that are healed now. The log is emptied at reboot/reset of controller/PC.
Since the "Socket send queue full to ..." problem seem so widespread I suspect a general problem with the physical network preventing nodes from sending telegrams on the network.
It is recommended to predefine link speed & duplex to highest possible speed & duplex on all network links where possible; e.g. links connecting a AC800 controller should be set for 10 Mbit/s Half Duplex (except for the PM891 processor which can sustain 100 Mbit/s Full Duplex) while most PC:s and switch-switch links shall have 100 or 1000 Mbit/s, Full Duplex.
Problems with auto-negotiate are very common so we recommend disabling it wherever possible.
To find out if problem is ongoing or not, use the RNRP Utility to clear the error logs in all nodes and perform a new check some time later. To easily reset all logs on e.g. RNRP area 20 in one operation; use this trick in the RNRP Utility on one of the PCs with physical connection to area 20:
Tools to help find problems in network configuration, ver 4.0, src_port=2424
----------------------------------------------------------------------------
0 - Quit
1 - Search own networks for nodes with configuration or network errors
2 - Get configuration parameters and error logs from one node
3 - Get network map from one node
4 - Change log conditions in one node (for experts)
5 - Test rnrp response time from one node
6 - Find nodes with rnrp on one network
7 - Unblock interface blocked in Windows after network loop detection
8 - Network to node throughput test. Caution, this may disturbe node !!!
Enter your choice : 4
Enter node IP-addr : 239.239.239.80
Select:
0 - Return
5 - Enable trace logs from area routing
6 - Disable trace logs from area routing
7 - Enable trace logs from network interface
8 - Disable trace logs from network interface
11 - Clear log buffers
Enter your choice : 11
"239.239.239.80" is the multicast address used by RNRP on network area 20 and will have all nodes to execute the clear log buffers command in parallel. The figure "80" is derived from RNRP Area number x 4.
I also suggest contacting your regional ABB support center if you are unable to resolve this problem yourself.
/Stefan
Answers
Hi
PLease check the 3BSE034463-510_en_System_800xA_5.1_Network_Configuration manual to make neccessary RNRP settings.
Also your attachment is missing.
Hi,
The possible reason could benecessary settings in Switches were not done/ethernet speed was not correctly set/spanning tree was enabled.
After doing the correct settings,please clear teh log buffers and then recheck.
If you still face the problem,please contact your regional supportline center for the assistance.
The information returned by RNRP Utility's "Search own networks for nodes with configuration or network errors" does not contain any time stamps - hence the problem(s) may be old, perhaps due to some errors in the past (from last reset of controller).
Since the "Socket send queue full to " problem seem so widespread I suspect a general problem with the physical network.
It is recommended to predefine link speed & duplex on all network links where possible; e.g. links connecting a controller should be set for 10 Mbit/s Half Duplex (except for the PM891 processor which can sustain 100 Mbit/s Full Duplex).
We have observed problems with using auto-negotiate so I recommend disabling it.
To find out if problem is ongoing or not, use RNRP Utility to clear the error logs in all nodes and perform a new check some time later.
To easily reset all logs on e.g. Area 20 in one operation; use this trick:
Tools to help find problems in network configuration, ver 4.0, src_port=2424
----------------------------------------------------------------------------
0 - Quit
1 - Search own networks for nodes with configuration or network errors
2 - Get configuration parameters and error logs from one node
3 - Get network map from one node
4 - Change log conditions in one node (for experts)
5 - Test rnrp response time from one node
6 - Find nodes with rnrp on one network
7 - Unblock interface blocked in Windows after network loop detection
8 - Network to node throughput test. Caution, this may disturbe node !!!
Enter your choice : 4
Enter node IP-addr : 239.239.239.80
Select:
0 - Return
5 - Enable trace logs from area routing
6 - Disable trace logs from area routing
7 - Enable trace logs from network interface
8 - Disable trace logs from network interface
11 - Clear log buffers
Enter your choice : 11
239.239.239.80 is the multicast address used by RNRP on network area 20 (4 x 20 = 80) and will have all nodes to execute the clear log buffers command in parallel.
I also suggest contacting your regional ABB support center if you are unable to resolve this problem yourself.
/Stefan
Add new comment