On Monday, 07/12/2010 at 09:47 EDT, Agblad Tore <[email protected]> wrote: > Hi again. > I'm in contact with a network person here and is trying to explain what's it > all about. > He is somewaht confused and he says the problem is in VIO.
Well, there is no VIO in z/VM as there is in, say, System p virtualization, so *that's* not it... > Is there anybody else having had this problem and succeeded in explain what to > do ? > We have a SLES10 maxhine with three network adapters and that works fine, but > that is not in the > same zone. The firewall hardwre and software is the same but obviously > something differ here. > > Can I add the MACID statement for the NICDEFs and try that ? > Do I need to fix that VMLAN MACPREFIX, or make sure it is set? > Hmm, I have to dig into some manuals here it seams.... The z/VM Connectivity book has the information you need. Simply code VMLAN MACPREFIX in SYSTEM CONFIG on each VM system, making sure that the prefix is different in each one, e.g. VMLAN MACPREFIX 020001. This will ensure that MAC addresses do not collide if the VM systems are connected to the same LAN segments. Note that this *may* not be the cause of your problems. The fact that multiple IP addresses have the same MAC address is not necessarily a bad thing and while it isn't common, it's not unheard of. If sessions aren't being established or are being broken, packet traces along the path (including tcpdump in the Linux guest) will identify where the data is going astray. Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- 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/
