m (Minor updates to how to test) |
(Use new infobox) |
||
Line 1: | Line 1: | ||
{| | {{Infobox_group | ||
| | | name = Fedora Test Days | ||
| | | image = [[File:Echo-testing-48px.png|link=QA/Fedora_15_test_days]] | ||
|- | | caption = [[Test_Day:2011-01-27_Network_Device_Naming_With_Biosdevname|Network Device Naming With Biosdevname]] | ||
| | | date = Thursday, January 27, 2011 | ||
| | | time = all day | ||
| website = [[QA/Fedora_15_test_days]] | |||
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc]) | |||
| fedora_mailing_list = test | |||
}} | |||
{{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}} | {{admon/note | Can't make the date? | If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at [http://bugzilla.redhat.com Bugzilla], and add your results to the results section. If this page is more than a month old when you arrive here, please check the [[QA/Test_Days|current schedule]] and see if a similar but more recent Test Day is planned or has already happened.}} | ||
Line 163: | Line 166: | ||
! User | ! User | ||
! Smolt Profile | ! Smolt Profile | ||
! [[QA: | ! [[QA:Testcase_Upgrade | persistent rules]] | ||
! [[QA: | ! [[QA:Testcase_Onboard_Network_Interface_Names | onboard devices]] | ||
! [[QA: | ! [[QA:Testcase_PCI_Add-In-Network-Interace_Names | add-in devices]] | ||
! [[QA: | ! [[QA:Testcase__SRIOV_Virtual_Function_Interface_Names| virtual iface]] | ||
! [[QA:Testcase_Interface_Configuration | device config]] | |||
! [[QA:Testcase_Install_Time_Network_Interface_Names | name durint install]] | |||
! References | ! References | ||
|- | |- | ||
Line 172: | Line 177: | ||
| [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW] | | [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW] | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|pass}} | |||
| {{result|inprogress}} | |||
| {{result|pass}} | | {{result|pass}} | ||
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref> | | {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref> |
Revision as of 20:42, 17 January 2011
Fedora Test Days | |
---|---|
Network Device Naming With Biosdevname | |
Date | Thursday, January 27, 2011 |
Time | all day |
Website | QA/Fedora_15_test_days |
IRC | #fedora-test-day (webirc) |
Mailing list | test |
What to test?
Today's installment of Fedora Test Day will focus on Network Interface Naming in Fedora Rawhide
Traditionally network interfaces in Linux are named ethN. With multiple network adapters, both onboard and add-in, single and multiport, in modern Server platforms, the naming of these interfaces is non-deterministic. In specific, 'eth0 does not always map to Gb1 or 'Embeddec NIC 1' as named on the server chassis. This makes the existing naming not very user friendly for administration.
Please refer to the following link for more details on the issue itself and various solutions we proposed upstream to address this issue -
- http://linux.dell.com/wiki/index.php/Oss/libnetdevname#Implementation
- http://linux.dell.com/wiki/index.php/Oss/libnetdevname#Presentations_at_various_forums
We address this issue by assigning names to network interfaces based on their physical location on the system board. Biosdevname which is a Dell developed utility, can suggest names to network interfaces, which are physical location based. http://linux.dell.com/biosdevname/
Naming convention followed is -
- Embedded devices: em<port>
- Add-in PCI cards: pci<slot>#<port>_<virtual function instance>
On a PowerEdge R710 server with 4 onboard network interfaces, 1 single port add-in network adapter on PCI slot 4, one dual port network adapter on PCI slot 3, the interfaces will be named as follows -
[root@fedora-14-r710 ~]# ls /sys/class/net/ em1 em2 em3 em4 lo pci3#1 pci3#1_0 pci3#1_1 pci3#2 pci3#2_0 pci3#2_1 pci4#1
- em1 - ethernet-on-motherboard 1
- em2 - ethernet-on-motherboard 2
- pci3#1 - ethernet interface physically located on PCI slot no 3, port 1
- pci3#2 - ethernet interface physically located on PCI slot no 3, port 2
- When pci3#2 has SRIOV capability and has enabled 2 virtual functions
- pci3#2_0 - ethernet interface physically located on PCI slot no 3, port 2, virtual function instance 0
- pci3#2_1 - ethernet interface physically located on PCI slot no 3, port 2, virtual function instance 1
Who's available
- Narendra K (irc_nick1) will be your host for the day.
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
Prerequisite for Test Day
- Hardware Requirements
- Computer system (Servers/Laptops/Desktops) with onboard(Lan-On-Motherboard) network adapters and/or add-in network adapters.
- Single and multiport add-in network adapters with SRIOV capability
- Single and multiport add-in network adapters with NPAR capability
- Computer system (Servers/Laptops/Desktops) with onboard(Lan-On-Motherboard) network adapters and/or add-in network adapters.
- Firmware/BIOS requirements
- System firmware/BIOS should implement SMBIOS version 2.6.
- System firmware/BIOS should implement SMBIOS type 41 record which defines a device type instance and string for onboard devices (network adapters included)
[root@fedora-14-r710 ~]# dmidecode -t 41 # dmidecode 2.10 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 Handle 0x2902, DMI type 41, 11 bytes Onboard Device Reference Designation: Embedded NIC 3 Type: Ethernet Status: Enabled Type Instance: 3 Bus Address: 0000:02:00.0 Handle 0x2903, DMI type 41, 11 bytes Onboard Device Reference Designation: Embedded NIC 4 Type: Ethernet Status: Enabled Type Instance: 4 Bus Address: 0000:02:00.1
- Software Requirements
- The system should be updated to Fedora Rawhide
- The SMBIOS type 41 device type instance and string should be available in sysfs.
[root@fedora-14-r710 ~]# lspci | grep -i ether 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 01:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) 02:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20) [root@fedora-14-r710 ~]# find /sys/ -name index /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/index /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.1/index /sys/devices/pci0000:00/0000:00:03.0/0000:02:00.0/index /sys/devices/pci0000:00/0000:00:03.0/0000:02:00.1/index [root@fedora-14-r710 ~]# find /sys/ -name label /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/label /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.1/label /sys/devices/pci0000:00/0000:00:03.0/0000:02:00.0/label /sys/devices/pci0000:00/0000:00:03.0/0000:02:00.1/label
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
- An updated Fedora XX pre-release, Rawhide (tips on installing Rawhide below), or a nightly live image
- Your hardware profile uploaded to Smolt according to these instructions
How to test?
At a high level, the testing will focus on
- Network interface names during install time
- Network interface names after installation is completed (after you login for first time)
- Required changes available in
ifcfg-ethN
config files - Upgrading from a previous update with a
/etc/udev/rules.d/70-persistent-net.rules
to Fedora Rawhide does not affect the naming scheme defined in/etc/udev/rules.d/70-persistent-net.rules
Update your machine
There are several ways to upgrade your test system.
- Upgrading from Fedora 14 to Fedora Rawhide -- see Rawhide for instructions
- Installing Fedora Rawhide using Fedora 14 ISO media -- see FIXME
- Boot a Fedora Rawhide Using a LIVE CD -- see FIXME
Test Cases
- Test upgrade from Fedora 14 to Rawhide
- Test that onboard interfaces are named as emN
- Test that PCI add-in interfaces are named as pci<slot>#<port>
- Test that Virtual Function Interfaces are named as pci<slot>#<port>_<virtual function instance>
- Test that onboard, Add-in, Add-in Virtual Function interfaces can be configured
- Test that Onboard and Add-in Interfaces are named as expected during Install Time
Test Results
Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
If you have problems with any of the tests, report a bug to Bugzilla usually for the component udisks, or gnome-disk-utility for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, if your system worked correctly, simply enter the word PASS. If you had trouble, enter the word FAIL, with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash.
User | Smolt Profile | persistent rules | onboard devices | add-in devices | virtual iface | device config | name durint install | References |
---|---|---|---|---|---|---|---|---|
Sample User | HW |