Running SIMP on VMware (ESXi) - NIC Naming

38 views
Skip to first unread message

Mark Kraft

unread,
Feb 9, 2017, 2:41:27 PM2/9/17
to SIMP Q&A Forum

I'm trying to ensure that the systems being kickstarted on our ESXi server get standard network interface names.

To override the new naming conventions in Centos7 I need to ensure that "net.ifnames=0 biosdevname=0" gets appended to the GRUB_CMDLINE_LINUX.

Is there an augeasprovider for grub where I can globally add that to all new systems?  Or is there some way to ensure that kickstarted systems on VMware hosts get an eth0 network interface name?

Right now when I kickstart the interface is named:  eno167<5 numbers>
And SIMP configures the ifcfg to this interface.

Can I set it up so that the interface is eth0 and SIMP will configure to that name?

Thanks in advance,
Mark

Nick Miller

unread,
Feb 9, 2017, 2:46:20 PM2/9/17
to Mark Kraft, SIMP Q&A Forum
If you're using our tftpboot module and example code, you can add those kernel parameters to the 'extra' parameter of the `tftpboot::linux_model` resource you're using.

That should set them to what you want.

--
You received this message because you are subscribed to the Google Groups "SIMP Q&A Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/simp/3ccc3f0a-f72c-40af-94f4-be2a2ea2e10f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

OnyxPoint-logo-symbol-primary.png

Nicholas Miller
Consultant | Onyx Point, Inc.

7050 Hi Tech Drive, Suite 102

Hanover, MD. 21076
e: nick....@onyxpoint.com
w: 443-655-3675

copmany.pngcareers.pngproduct.pngmeetups.pngblog.png

Mark Kraft

unread,
Feb 9, 2017, 2:49:29 PM2/9/17
to SIMP Q&A Forum, kra...@gmail.com
Easy enough... I'll give it a shot.

Thanks for the quick response,
Mark


On Thursday, February 9, 2017 at 1:46:20 PM UTC-6, Nick Miller wrote:
If you're using our tftpboot module and example code, you can add those kernel parameters to the 'extra' parameter of the `tftpboot::linux_model` resource you're using.

That should set them to what you want.
On Thu, Feb 9, 2017 at 2:41 PM, Mark Kraft <kra...@gmail.com> wrote:

I'm trying to ensure that the systems being kickstarted on our ESXi server get standard network interface names.

To override the new naming conventions in Centos7 I need to ensure that "net.ifnames=0 biosdevname=0" gets appended to the GRUB_CMDLINE_LINUX.

Is there an augeasprovider for grub where I can globally add that to all new systems?  Or is there some way to ensure that kickstarted systems on VMware hosts get an eth0 network interface name?

Right now when I kickstart the interface is named:  eno167<5 numbers>
And SIMP configures the ifcfg to this interface.

Can I set it up so that the interface is eth0 and SIMP will configure to that name?

Thanks in advance,
Mark

--
You received this message because you are subscribed to the Google Groups "SIMP Q&A Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simp+uns...@googlegroups.com.

Trevor Vaughan

unread,
Feb 9, 2017, 3:58:11 PM2/9/17
to Mark Kraft, SIMP Q&A Forum
If that doesn't do what you need, you can indeed use augeasproviders_grub to do what you need. It supports both GRUB and GRUB2 now.

Thanks,

Trevor

To unsubscribe from this group and stop receiving emails from it, send an email to simp+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/simp/cd4e7051-fa26-436e-9ea3-e3990af4f8f1%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Trevor Vaughan
Vice President, Onyx Point, Inc

-- This account not approved for unencrypted proprietary information --
Reply all
Reply to author
Forward
0 new messages