From Fedora Project Wiki

(Use new infobox)
(Corrected download links)
Line 144: Line 144:


There are several ways to upgrade your test system.
There are several ways to upgrade your test system.
# Upgrading from Fedora 14 to Fedora Rawhide -- see [[Releases/Rawhide|Rawhide]] for instructions
# Upgrade from Fedora 14 to Fedora Rawhide using {{command|yum}} -- for guidance, see [[Releases/Rawhide#Yum_update_from_previous_release|yum update from previous release]]
# Installing Fedora Rawhide using Fedora 14 ISO media -- see [[#FIXME|FIXME]]
# Install Fedora Rawhide using [http://fedoraproject.org/get-fedora Fedora 14 ISO media] -- for guidance, see [[Releases/Rawhide#Using_a_general_release_Fedora_ISO|Install rawhide using Fedora 14 ISO]]
# Boot a Fedora Rawhide Using a LIVE CD -- see [[#FIXME|FIXME]]
# Download and boot a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ Fedora Rawhide live image] -- for guidance, see [[How_to_create_and_use_Live_USB]]


== Test Cases ==
== Test Cases ==

Revision as of 21:21, 17 January 2011

Fedora Test Days
Echo-testing-48px.png
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


Note.png
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 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 current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's installment of Fedora Test Day will focus on Network Interface Naming in Fedora Rawhide

https://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming#Consistent_Network_Device_Naming

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 -

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
  • 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:

How to test?

At a high level, the testing will focus on

  1. Network interface names during install time
  2. Network interface names after installation is completed (after you login for first time)
  3. Required changes available in ifcfg-ethN config files
  4. 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.

  1. Upgrade from Fedora 14 to Fedora Rawhide using yum -- for guidance, see yum update from previous release
  2. Install Fedora Rawhide using Fedora 14 ISO media -- for guidance, see Install rawhide using Fedora 14 ISO
  3. Download and boot a Fedora Rawhide live image -- for guidance, see How_to_create_and_use_Live_USB

Test Cases

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
none
Pass pass
Inprogress inprogress
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345