Enabling biosdevname on PE T610

Jeff Boyce jboyce at meridianenv.com
Mon Jan 23 16:39:11 CST 2012


Greetings -

I have a new PE T610 that I am configuring for my office, and before I put 
it into production I wanted to make sure that it was using the new network 
device naming scheme implemented by biosdevname.  This box will be used as a 
KVM host with 3 virtual machines, all using CentOS.  I initially installed 
Centos 6.0 in the host OS and for two VM's.  I have updated the host system 
to CentOS 6.2.

[jeffb at earth ~]$ uname -a
Linux earth.mei.lan 2.6.32-220.2.1.el6.x86_64 #1 SMP Fri Dec 23 02:21:33 CST 
2011 x86_64 x86_64 x86_64 GNU/Linux

I have reviewed the Dell Whitepaper regarding the use of biosdevname, and 
appear to have the required prerequisites installed.
http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf

[root at earth jeffb]# dmidecode -t 41
# dmidecode 2.11
SMBIOS 2.6 present.

Handle 0x2900, DMI type 41, 11 bytes
Onboard Device
        Reference Designation: Embedded NIC 1
        Type: Ethernet
        Status: Enabled
        Type Instance: 1
        Bus Address: 0000:01:00.0

Handle 0x2901, DMI type 41, 11 bytes
Onboard Device
        Reference Designation: Embedded NIC 2
        Type: Ethernet
        Status: Enabled
        Type Instance: 2
        Bus Address: 0000:01:00.1


[root at earth jeffb]# dmidecode -t 9
# dmidecode 2.11
SMBIOS 2.6 present.

Handle 0x0900, DMI type 9, 17 bytes
System Slot Information
        Designation: PCI1
        Type: x4 PCI Express 2 x8
        Current Usage: Available
        Length: Long
        ID: 1
        Characteristics:
                3.3 V is provided
                PME signal is supported
<<< clipped additional output >>>

I have rebooted the box since the system update and still see that it is 
using the old naming convention.

[jeffb at earth ~]$ ifconfig
br0       Link encap:Ethernet  HWaddr 78:2B:CB:5C:82:D1
          inet addr:192.168.112.5  Bcast:192.168.112.255  Mask:255.255.255.0
          inet6 addr: fe80::7a2b:cbff:fe5c:82d1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6881 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3329 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5952925 (5.6 MiB)  TX bytes:311159 (303.8 KiB)

eth0      Link encap:Ethernet  HWaddr 78:2B:CB:5C:82:D1
          inet6 addr: fe80::7a2b:cbff:fe5c:82d1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:7026 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3379 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6109523 (5.8 MiB)  TX bytes:330681 (322.9 KiB)
          Interrupt:36 Memory:da000000-da012800

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:84 errors:0 dropped:0 overruns:0 frame:0
          TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6033 (5.8 KiB)  TX bytes:6033 (5.8 KiB)

virbr0    Link encap:Ethernet  HWaddr 52:54:00:D4:F7:05
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:4583 (4.4 KiB)


Am I not seeing the new naming scheme because I had already made the initial 
system installation using CentOS 6.0, which did not include/support 
biosdevname?  Do I need to manually make some configuration changes in order 
to use the new naming scheme; such as to:

/etc/sysconfig/network-scripts/ifcfg-br0
/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/sysconfig/network-scripts/ifcfg-eth1
/etc/sysconfig/network-scripts/ifcfg-eth2, and possibly
/etc/udev/rules.d/70-persistent-net.rules

Would there be any SELinux implications that would need to be addressed 
also?

Sorry for the long post for such a short question, but I assume that someone 
would request that I provide most of this information anyway in order to 
fully address my question.  Thanks for any help anyone can provide.


Jeff Boyce
Meridian Environmental
www.meridianenv.com



More information about the Linux-PowerEdge mailing list