RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1204105 - Intel physical function ends up called enp2s0f0
Summary: Intel physical function ends up called enp2s0f0
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-20 12:03 UTC by lejeczek
Modified: 2015-06-05 18:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-05 18:30:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description lejeczek 2015-03-20 12:03:36 UTC 
Description of problem:

enp2s0f0 is, from what I gathered a name for function. I still have enp2s16 and enp2s17 but they are apparently virtual functions.

# biosdevname -d
BIOS device: p13p1
Kernel name: enp2s0f0
Permanent MAC: 00:25:90:72:BB:E2
Assigned MAC : 00:25:90:72:BB:E2
ifIndex: 6
Driver: igb
Driver version: 5.0.5-k
Firmware version: 1.5.3
Bus Info: 0000:02:00.0
PCI name      : 0000:02:00.0
PCI Slot      : 13
Index in slot: 1
Virtual Functions:
0000:02:11.4
0000:02:11.2
0000:02:11.0
0000:02:10.6
0000:02:10.4
0000:02:10.2
0000:02:10.0

BIOS device: p13p2
Kernel name: enp2s0f1
Permanent MAC: 00:25:90:72:BB:E3
Assigned MAC : 00:25:90:72:BB:E3
ifIndex: 14
Driver: igb
Driver version: 5.0.5-k
Firmware version: 1.5.3
Bus Info: 0000:02:00.1
PCI name      : 0000:02:00.1
PCI Slot      : 13
Index in slot: 2
Virtual Functions:
0000:02:11.5
0000:02:11.3
0000:02:11.1
0000:02:10.7
0000:02:10.5
0000:02:10.3
0000:02:10.1

I have:
enp2s16 - what's this?
enp2s17 - what's this?
enp2s0f0 - physical
enp2s0f1 - psysical
enp2s16f1 - virtual
enp2s16f2 - virtual
...

how does one decipher these names???

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Michal Schmidt 2015-06-05 18:30:39 UTC 
enp2s0f0 is an interface name derived from PCI geographical information, i.e. it encodes the PCI address 02:00.0.

For information about the naming schemes see:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Consistent_Network_Device_Naming.html

or the upstream wiki page:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
Note You need to log in before you can comment on or make changes to this bug.