Since we upgraded to ONTAP 8.1.4 7-mode we have these messages in console.
arp: writing to routing socket: File exists
They don't appear in the messages log file but only in console. Seems that it comes from the ACP upgrade Fwd.
As anyone had the same ?
ACP is working well:
Alternate Control Path: Enabled
Ethernet Interface: e4b
ACP Status: Active
ACP IP Address: 192.168.0.123
ACP Subnet: 192.168.0.0
ACP Netmask: 255.255.252.0
ACP Connectivity Status: Full Connectivity
Shelf Module Reset Cnt IP Address FW Version Module Type Status
----------------- ------------ --------------- ------------ ------------ -------
1a.00.A 000 192.168.2.219 01.41 IOM3 active
1a.00.B 000 192.168.2.229 01.41 IOM3 active
1a.01.A 000 192.168.3.231 01.41 IOM3 active
1a.01.B 000 192.168.0.216 01.41 IOM3 active
1a.02.A 000 192.168.1.61 01.41 IOM3 active
1a.02.B 000 192.168.2.33 01.41 IOM3 active
1a.03.A 000 192.168.0.82 01.41 IOM3 active
1a.03.B 000 192.168.0.115 01.41 IOM3 active
1a.04.A 000 192.168.0.168 01.41 IOM3 active
1a.04.B 000 192.168.0.231 01.41 IOM3 active
We get the same message on my FAS2040 console after upgrading to 126.96.36.199-mode on December 18, 2013.
Everything else seems fine.
Here is the answer of the support :
Unfortunately it seems that you have ran into a known issue reported in Internal Case 723742 and caused by Internal Case number 640594.
reported in Internal Case: http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=723742
caused by Internal Case: http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=640594
As usual nothing public in this Burt
This issue just have been solved with DOT 8.1.4P1:
We are using DOT 8.1.4P1 on FAS 3220 systems and this problem is still occurring. I can still see messages on the console arp: writing to routing socket: File exists.
Is there any workaround for this?
Today we have updated our FAS6210 to 8.1.4P1. Since the update the Message "arp: writing to routing socket: File exists" is gone..
Have you tried an options acp.enabled off , wait a min and acp.enabled on
It worked for me.
I just upgraded a FAS6210 to 8.1.4P2 and still received the message. However, I used the suggestion to cycle the ACP and it appears to have stopped the messages.
Also an issue in 8.1.4P4,
we just upgraded from 8.1.2 to 8.1.4P4 and got this messages.
Upgraded FAS2240-2 from 8.1.4 to 8.2.3 and got this message.
options acp.enabled off
made it go away