![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Yeah you’re obviously beyond reason and we’re speaking across different levels of intellect here. Bringing up NOCs shows you’re entry level, despite how many years of experience you have. Find my phone is a network because the phone which has cellular capabilities reports that to Apple/Google.
It wasn’t my intention to start a dick measuring contest here but since it’s on the table, im a six figure(deep into six figures) engineer at a fortune 10 company. Your 25+ years of CompTIA A+ experience mean nothing to me. You’re talking to a CCIE.
No one with any amount of intellect would call something communicating at layer two a “network”, though anything that transfers data between two devices can technically be called a network, “networking” is being able to communicate with OTHER networks.
As a data center engineer of 10+ years, I struggled to understand this at first. In my world, the hardware does a POST before the OS boots and has an inventory of what hardware components are available, so it shouldn’t matter in what order they are discovered, since the interface names should make a correlation between the interface and the pcie slot that NIC exists in.
Where the water gets muddled is in virtualized servers. The NICs no longer have a correlation to a specific hardware component, and you may need to configure different interfaces in the virtualized OS for different networks. I think in trying to create a methodology that is agnostic to bare metal/virtualized OSs, it was decided that the naming convention should be uniform.
Probably seems like bloat to the average admin who is unconcerned with whether these NICs are physical or virtual, they just want to configure their server.