[sles-beta] SLES12 network interface names

[urs.frey at post.ch]

Hi Olaf

>So, will vmware leave at least the MAC address intact?
Yes unless the type of driver changes in the VM client config, e.g.from Intel to vmxnet3, the MAC keeps being the same. But this is a different story.

See, my concern is, that I usually have to install a server remotely without having seen the HW before.
The only thing I have, is the MAC I can get either by API from the HP Proliant ILO remote console, or by API from the VMware Vspere client configuration.

In both cases I then need to "translate" the MAC of the first interface in the list to some name to generate my autoinst.xml
In my case the first interface in the list is cabled and has an open Firewall as setup interface for network setup.

Best regards

Urs Frey                                              
Post CH AG
Informationstechnologie
IT Betrieb 
Webergutstrasse 12 
3030 Bern (Zollikofen) 
Telefon : ++41 (0)58 338 58 70 
FAX     : ++41 (0)58 667 30 07 
E-Mail:   urs.frey at post.ch


-----Ursprüngliche Nachricht-----
Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Olaf Kirch
Gesendet: Monday, March 24, 2014 3:37 PM
An: sles-beta at lists.suse.com
Betreff: Re: [sles-beta] SLES12 network interface names


Hi Urs,

On Monday 24 March 2014 10:38:57 urs.frey at post.ch wrote:
> Hi
> 
> I had a look at the wiki you provided.
> http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfac
> eNames/
> 
> My concern is, that I have to know the proper network interface name before
>  I create the autoyast autoinst.xml profile. This could be accomplished
>  perfectly when having the eth names.
> 
> Now with the new naming rules I run into problems as I do not know the pci
>  bus number before powering the server. I sometimes do not even know the
>  kind of network interface HW built in in my ProLiant servers. Sometimes
>  Broadcom, sometimes, Intel sometimes Emulex NIC, who knows.
> 
> Even when having installed on VMWare and changing the HW emulation level,
>  the NIC name changes. This is really not a way to go, as with every ESXi
>  update the HW emulation level may change. I would like to have my VMware
>  installation living over years with no manual interaction necessary

Just for my education - when we're talking about name persistence, there
needs to be *something* that is permanent, otherwise there won't be a way
to tie a configuration to any piece of hardware. And if devices keep changing
all the time, then we're kinda out of luck if we need to tell them apart.

So, will vmware leave at least the MAC address intact? Or are we really
just talking about a configuration like "I really don't care how the NIC
identifies itself - I just want to make it come up with DHCP"?

Regards
Olaf
-- 
Neo didn't bring down the Matrix. SOA did. (soafacts.com)
--------------------------------------------
Olaf Kirch - Director SUSE Linux Enterprise; R&D (okir at suse.com)
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) 
_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta