|
(incomplete) means that the system didn't get (or parse) the arp reply. (ie: arp request was created and sent, but nothing has come back yet, so that's it's way of saying "in limbo"). Edit: That's a weird expiry timer. Try deleting the arp entries in case they're corrupted entries?
|
#
¿
Nov 21, 2016 19:14
|
|
|
|
| # ¿ Apr 27, 2024 12:29 |
|
|
BangersInMyKnickers posted:I'm guessing its seeing the NetApps doing gratuitous arps and deciding its a malicious device on the network and blocking it. Either way I'm mucking back in to support hell. Or your switch is blocking broadcast packets from your servers, so the netapp never gets the arp request in the first place. Simple test of that is to ping from the netapp to your servers (reverses the arp process). Your servers should then automatically learn the mac address from the netapp. Other test would be to hardcode the arp on the server temporarily. If it works, you've got broadcast filtering in place.
|
|
#
¿
Nov 22, 2016 16:40
|
|
|
Out of my experience, Ovirt is fundamentally designed to be run on 2+ nodes (+1 if you don't do self hosted controller) with a NAS of some sort (preferably NFS). Out side of that config you rapidly start running into weird issues and corner cases that someone hasn't programmed for.
|
|
#
¿
Sep 26, 2017 19:40
|
|
|
I'm dating myself, but I was at the usenix NSDI conference in 2005 where they were showing the first prototypes of live vm migrations between computers playing doom live. In retrospect that conference was wild for all the cutting edge tech that was being displayed and developed at the time - lots of zigbee stuff shown there too. (https://www.usenix.org/legacy/events/nsdi05/tech/clark.html)
|
|
#
¿
Mar 9, 2024 02:39
|
|