Skip to main content

Find Ethernet Card by slot Linux


I was somewhat frustrated when network interface enumeration suddenly changed (around 6.3) in a seemingly random manner.  I noticed the madness now had a pattern... and regardless of my attempts to manually manage my interfaces using UDEV (as I had in the past) it would just screw everything up.
So - I conceded and allowed the system to manage itself how it wanted and I discovered that was the best option.

In the past, you may end up with eth0 being on a PCI card, while the onboard would be eth3.  Since the release of the new standard, the onboard are identified as em (for "embedded" I believe) and the other network interfaces are identified by slot number and interface (i.e. p2p1 - slot 2, eth 1).

A person who posts on the Red Hat Customer Portal had an amazing find and submitted the following:

....Dell (who wrote biosdevname and released it under GPL) have two white papers on the subject at the project page: http://linux.dell.com/biosdevname/
From the Consistent Network Device Naming in Linux paper:
  • Firmware information that "biosdevname" utilizes to suggest new names
    The system BIOS indicates the order of Onboard Network Devices to the OS via SMBIOS type 41 records.
    The system BIOS provides "system slot information" to the OS via type 9 records.
    The biosdevname makes use of SMBIOS type 41 to suggest names to the onboard network devices and type 9 records to suggest new names for PCI add-in adapters.
    The biosdevname falls back on PCI IRQ Routing Table in the absence of the above mentioned information.
You should be able to see this SMBIOS information with dmidecode -t 41 and dmidecode -t 9 ...
-- Jamie Bainbridge

I'll miss the foo of using lspci and /etc/udev/rules.d/70-persistent-network.rules :-(  Not really!

Comments

Popular posts from this blog

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un...