Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
NICs are enumerated oddly in RHEL6. I'm using a Sun Ultra27 workstation to do my RHEL6 testing. When only the onboard NIC is present, it's assigned as eth0 and everything works fine. I installed a 4-port PCI NIC into the system to replicate a problem that Sun reported. When I brought the system back up, it detected the card's 4 ports as eth1-eth4 and behaved as expected. I then reinstalled the OS to check that behavior and now I have eth0 (onboard) and eth4-7 (PCI card). Where did 1-3 go?
Version-Release number of selected component (if applicable):
NetworkManager-0.7.1-4.git20090414.fc11.x86_64
More to come, including a sosreport, momentarily.
Comment 1RHEL Program Management
2009-07-28 15:49:21 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
How reproducible:
Each boot post-install keeps the same unusual NIC ordering
Steps to Reproduce:
1. Install RHEL6 on a system with a 4-port NIC and an onboard NIC
2. Reboot after install
3. Observe the strange NIC ordering
Actual results:
Holes in NIC naming sequence
Expected results:
NICs enumerated in order
Additional info:
What's the content of /etc/udev/rules.d/70-persistent-net.rules (and/or /etc/sysconfig/network-scripts/ifcf-g*) on the installed system
1) when anaconda finishes
2) after rebooting
?
Okay. It looks like the ifcfg-* files are correct post-boot. They're called eth0-eth4 and their contents name them as eth0-eth4. It's the persistent net rules file and the output of NetworkManager that's wacky. I'm attaching a tarball with all the files.
Let me know how it goes; some devices may not have MAC addresses until they are given one. In this case, it's best to write udev rules to assign a MAC to the device based on other hardware attributes (like pci bus location, USB serial number, etc), if it doesn't have the capability to store its MAC address in NVRAM. Thus the MAC address is available to NetworkManager and ifup/ifdown.