Dear all, Thank you for all the interest and support. I investigated the problem together with our network team. It turned out that there was a configuration mismatch in the VLAN definitions of the physical switch where the VSWITCH/OSA was connected to. Due to the fact that we run that DMZ only on our primary node (Node A) before we had z/VM 6.2, the VSWITCH on the backup site was never used before. It was patched but not really tested. The situation was quite strange since we never faced problems with a relocation of a guest in the internal LAN before. Since in that specific case there was now a firewall involved I suspected the firewall. Mea culpa.
However we managed the move of the production guest successfully the other node just in time. Kind regards, Florian On Fri, Sep 21, 2012 at 7:20 PM, Alan Altmark <[email protected]>wrote: > I wasn't paying close enough attention. APAR VM65104 is not for LGR. The > APAR is a roll-back of a subset of the LGR grat ARP logic. Florian, you > need to open a CP PMR. > > Regards, > Alan > > Senior Managing z/VM and Linux Consultant > IBM System Lab Services and Training > ibm.com/systems/services/labservices > office: 607.429.3323 > [email protected] > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
