CentOS - Mar 2018 - NIC naming conventions and vmware

I have a couple of CentOS 7 machines running in a vmware environment. On 
all the older ones I've deployed, the NIC is named ens160, but on all of 
the new ones, it is named ens192. I can't find any difference in the 
hardware that would account for this.

Any suggestions on what I can do to figure out why some are named ens160 
and some ens192?

Thanks.

Hi,

The older running Centos 7?

All machines are in the same vmware host?

It is not your case, but are interesting:
https://access.redhat.com/solutions/2592561

On Wed, Mar 7, 2018 at 2:31 PM, John Ratliff <john at bluemarble.net>
wrote:
> I have a couple of CentOS 7 machines running in a vmware environment. On
> all the older ones I've deployed, the NIC is named ens160, but on all
of
> the new ones, it is named ens192. I can't find any difference in the
> hardware that would account for this.
>
> Any suggestions on what I can do to figure out why some are named ens160
> and some ens192?
>
> Thanks.
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>


-- 
*Diego Chac?n Rojas*
** E-mail: diego at gridshield.net <diego at gridshield.net>*

On Thu, Mar 8, 2018 at 9:31 AM, John Ratliff <john at bluemarble.net>
wrote:
> I have a couple of CentOS 7 machines running in a vmware environment. On
> all the older ones I've deployed, the NIC is named ens160, but on all
of
> the new ones, it is named ens192. I can't find any difference in the
> hardware that would account for this.
>
> Any suggestions on what I can do to figure out why some are named ens160
> and some ens192?
>
>
Hi John,

This may not be helpful but I can confirm that you should be getting
consistent naming.
Normally I actually get something like eno16777984  But I have a couple
systems that get named in the way that you mention.  When this happens I
normally see ens160 as the first nic and 192 if a second is defined.
I haven't dug too deeply into this but I would suggest that you look at the
udev rules that are defined in /etc/udev/rules.d/ and see if this explains
what is happening.   You may also want to check that the VMware Hardware
version is what you expect.







> Thanks.
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

-----Original Message-----
From: CentOS <centos-bounces at centos.org> On Behalf Of John Ratliff
Sent: Wednesday, March 7, 2018 1:31 PM
To: CentOS <centos at centos.org>
Subject: [CentOS] NIC naming conventions and vmware
 
> I have a couple of CentOS 7 machines running in a vmware environment. On
> all the older ones I've deployed, the NIC is named ens160, but on all
of
> the new ones, it is named ens192. I can't find any difference in the
> hardware that would account for this.
> 
> Any suggestions on what I can do to figure out why some are named ens160
> and some ens192?
The difference comes from the virtual machine host operating
system definition and the virtual network adapter type selected
where the first choice constrains the available options for the second.