/en-gb/
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Alan
Altmark
Sent: den 18 november 2011 18:34
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hardcoded mac addresses in an autogenerated environment
On Friday, 11/18/2011 at 11:44 EST, Agblad
Hi there.
We have autogenerated mac addresses for our zLinux servers (ip-only traffic)
I have tested and verified that the mac-address for the network adapter changes
between z/VM logoff-logon ( shutdown + start ).
Well, that's no surprise, that's what we wanted :-)
BUT:
The license for for a
Phone: (845) 433-7567
e-mail: thang.p...@us.ibm.com
From: Agblad Tore tore.agb...@volvo.com
To: LINUX-390@vm.marist.edu,
Date: 11/18/2011 11:45 AM
Subject:Hardcoded mac addresses in an autogenerated environment
Sent by:Linux on 390 Port LINUX-390@vm.marist.edu
Hi
On Friday, 11/18/2011 at 11:44 EST, Agblad Tore tore.agb...@volvo.com
wrote:
Hi there.
We have autogenerated mac addresses for our zLinux servers (ip-only
traffic)
I have tested and verified that the mac-address for the network adapter
changes
between z/VM logoff-logon ( shutdown + start ).
On 11/18/2011 at 12:33 PM, Alan Altmark alan_altm...@us.ibm.com wrote:
I recommend against coding LLADDR in your Linux config.
The problem isn't the system administrators doing it, but the tools they use.
I'm hopeful that will get fixed for at least SLES11 SP2.
Mark Post
On 11/18/2011 at 12:00 PM, Thang Pham thang.p...@us.ibm.com wrote:
You can hard-code the MAC address into /etc/sysconfig/network/ifcfg-eth0
You can, but that can cause serious problems at the z/VM level. There have
been cases where a hard coded MAC address in a Linux guest has caused another
