Jonathan Billings wrote: <snip>>> And *why* random NIC names? Quick, you've got servers from 5 >> manufacturers, of different ages... what's the NIC going to be called? >> Do names like enp5s0 offer any convenience to *anyone* not a hardware >> engineer? > > Unrelated to systemd. This actually started happening in RHEL6 with > the biosdevname feature. systemd can handle the NIC naming stuff, but > it started happening well before systemd appeared in RHEL. > > Having consistent device names is helpful when you've got more than > one NIC and you don't want to rely on the order in which the network > driver is loaded to define the interface name.In what universe are those "consistant" device names, as opposed to eth[0...]? And how could it help automated scripts that you can run on *any* system you're administering? mark
On 4/10/2017 1:57 PM, m.roth at 5-cent.us wrote:> In what universe are those "consistant" device names, as opposed to > eth[0...]? And how could it help automated scripts that you can run on > *any* system you're administering?if I have a Intel gigE interface and a Marvell 10g interfaces, which one is eth0 and why? Say its Intel on eth0 and Marvell on eth1, if I then add another intel, is the Marvell now eth2 ? -- john r pierce, recycling bits in santa cruz
On Mon, April 10, 2017 4:17 pm, John R Pierce wrote:> On 4/10/2017 1:57 PM, m.roth at 5-cent.us wrote: >> In what universe are those "consistant" device names, as opposed to >> eth[0...]? And how could it help automated scripts that you can run on >> *any* system you're administering? > > if I have a Intel gigE interface and a Marvell 10g interfaces, which one > is eth0 and why? > > Say its Intel on eth0 and Marvell on eth1, if I then add another intel, > is the Marvell now eth2 ? >Without intent to contradict... I really would prefer them numbered according to their bus address. Not in the order (or reverse order - as it was once) of them been discovered. And if you add hardware with bus address between those of eth0 and eth1, you will have newly added one become eth1, and former eth1 becomes eth2. I know, it stems from old idiotic habit to always look inside the boxes... call me an old UNIX outcast. (No, don't, that would be a complement I unlikely deserve ;-) Valeri> > -- > john r pierce, recycling bits in santa cruz > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++
John R Pierce wrote:> On 4/10/2017 1:57 PM, m.roth at 5-cent.us wrote: >> In what universe are those "consistant" device names, as opposed to >> eth[0...]? And how could it help automated scripts that you can run on >> *any* system you're administering? > > if I have a Intel gigE interface and a Marvell 10g interfaces, which one > is eth0 and why? > > Say its Intel on eth0 and Marvell on eth1, if I then add another intel, > is the Marvell now eth2 ? >And if I have a 5-yr-old Penguin (OEM-branded Supermicro), and a Dell PowerEdge R530 and an HP ProLiant dl580 and a hot-off-the-presses Penguin/Intel, what will their primary device be named? As opposed to you installing a new NIC in addition to one that's there... which, since you've just installed it, I suppose you could add the UUID to whatever you want to name it. mark
On 04/10/2017 05:17 PM, John R Pierce wrote:> On 4/10/2017 1:57 PM, m.roth at 5-cent.us wrote: >> In what universe are those "consistant" device names, as opposed to >> eth[0...]? And how could it help automated scripts that you can run on >> *any* system you're administering? > if I have a Intel gigE interface and a Marvell 10g interfaces, which one > is eth0 and why? > > Say its Intel on eth0 and Marvell on eth1, if I then add another intel, > is the Marvell now eth2 ? > >In my experience the new interface would be eth2, because the startup scripts create a mac binding to ethx name in the /etc/udev/rules.d/70-persistent-net.rules file, so even if the intel is probed before the marvel the scripts rename them to keep them in the original order. Steve