×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Marc - you hit the nail on the head. The subnet mask for our virtual IP was 255.255.255.240. No one even uses the virtual IP, so I just ended the interface. If within a month we don't experience any issues I will remove the interface entirely.
I believe the virtual interface was initially setup as some form of fault tolerance, but that was years ago. I would prefer to setup a LACP connection between the two iSeries NICs and our core rather than use a VIPA for fault tolerance.
Thanks for your help!
Taylor Hammerling
IT Manager | RateWatch
800.348.1831 x4302 | taylor.hammerling@xxxxxxxxxxxxxx | rate-watch.com
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Marc Rauzier
Sent: Wednesday, May 11, 2016 3:12 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: ARP issues with HMC and iSeries
Le 11/05/2016 à 21:30, Taylor Hammerling a écrit :
At this point I'm feeling like there has to be some IBM specific piece of software or configuration I'm missing.
Hello
I am not sure to understand what you mean but I have got the same kind of behaviour with a misconfigured network mask for a Virtual IP Address configuration (VIPA) on an IBM i partition. The mask of the VIPA was
*not* set to 255.255.255.255. The result was that the IBM i partition was responding to any arp request about an IP in the mask of the VIPA "yes, this IP is mine and here my MAC address".
So, if you have such a VIPA configuration, double check the masks.
Marc
midrange.com
