ARP moved on nas4free server

danypd69

Renowned Member
Oct 8, 2010
28
0
66
Hello
I have a very simple setup with one proxmox host with 3 network interfaces and a nas4free server used as iscsi storage.

One of the interfaces is used to connect to internet and the other two are used for iscsi.
The iscsi interfaces are on a dedicated switch so there is no physical connection between iscsi and other network.

I keep getting these messages on the nas4free log files.

Code:
arp: 192.168.200.30 moved from 00:15:17:63:56:4e to 00:15:17:63:56:4f on em0
arp: 192.168.201.30 moved from 00:15:17:63:56:4f to 00:15:17:63:56:4e on em1
arp: 192.168.200.30 moved from 00:15:17:63:56:4f to 00:15:17:63:56:4e on em0
arp: 192.168.201.30 moved from 00:15:17:63:56:4e to 00:15:17:63:56:4f on em1
arp: 192.168.200.30 moved from 00:15:17:63:56:4e to 00:15:17:63:56:4f on em0
arp: 192.168.201.30 moved from 00:15:17:63:56:4f to 00:15:17:63:56:4e on em1

em0 and em1 are the iscsi nics on the nas4free server.

This is the network config of the proxmox host; eth0 is the internet nic and eth2/eth3 are the iscsi nics

Code:
eth0      Link encap:Ethernet  HWaddr 00:1e:4f:20:32:3b            inet6 addr: fe80::21e:4fff:fe20:323b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1032346 errors:0 dropped:0 overruns:0 frame:0
          TX packets:940185 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1025941053 (978.4 MiB)  TX bytes:96790027 (92.3 MiB)


eth2      Link encap:Ethernet  HWaddr 00:15:17:63:56:4e  
          inet addr:192.168.200.30  Bcast:192.168.200.255  Mask:255.255.255.0
          inet6 addr: fe80::215:17ff:fe63:564e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:84037148 errors:0 dropped:568 overruns:0 frame:0
          TX packets:55748736 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:88598257398 (82.5 GiB)  TX bytes:39459734170 (36.7 GiB)
          Interrupt:16 Memory:fc3e0000-fc400000 


eth3      Link encap:Ethernet  HWaddr 00:15:17:63:56:4f  
          inet addr:192.168.201.30  Bcast:192.168.201.255  Mask:255.255.255.0
          inet6 addr: fe80::215:17ff:fe63:564f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:89541611 errors:0 dropped:12933 overruns:0 frame:0
          TX packets:55686388 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:94854825994 (88.3 GiB)  TX bytes:39316043550 (36.6 GiB)
          Interrupt:17 Memory:fc3a0000-fc3c0000

Does anyone have idea of what can cause this problem?
 
Your two nics are connected to the same nas4free?

If yes, why not bond the two interfaces effectively making only one connection to nas4free?

In your current setup you will likely have iscsi connections active on both interfaces to the same LUN and data flowing interchangeably to/from nas4free on both nics. Your setup will likely cause data loss sometime in the near future.
 
Yes, two nics for multipathing. Each nic is on a different subnet so there should not be problems with mixed data.
 
I am already using it, the multipath is configured and working ok, the only problem is the message in the nas4free console; I don't know if it is a real problem that can cause errors in future.


Code:
root@px2950-01:/home/daniele# multipath -ll
3300000003f4b6f41 dm-3 FreeBSD,iSCSI DISK
size=3.6T features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=0 status=active
  |- 6:0:0:0  sdd 8:48  active ready  running
  |- 7:0:0:0  sde 8:64  active ready  running
  |- 8:0:0:0  sdf 8:80  active ready  running
  `- 9:0:0:0  sdh 8:112 active ready  running
330000000e20ec5f9 dm-4 FreeBSD,iSCSI DISK
size=931G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=0 status=active
  |- 10:0:0:0 sdg 8:96  active ready  running
  |- 13:0:0:0 sdi 8:128 active ready  running
  |- 11:0:0:0 sdj 8:144 active ready  running
  `- 12:0:0:0 sdk 8:160 active ready  running
 
Last edited:
It's not related to the iscsi service.
I have disabled iscsi on nas4free, rebooted the server and done a ping on each ip address from the proxmox host.
Result

Code:
arp: 192.168.200.30 moved from 00:15:17:63:56:4e to 00:15:17:63:56:4f on em0
arp: 192.168.201.30 moved from 00:15:17:63:56:4f to 00:15:17:63:56:4e on em1
arp: 192.168.200.30 moved from 00:15:17:63:56:4f to 00:15:17:63:56:4e on em0
 
I alredy found that link but the interfaces are not teamed nor bonded.
As I stated in a previous message the problem is present also when I simply enable the nics without activating iscsi.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!