https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_Hardware_Certification/1/html-single/Program_Policy_Guide/index.html
Program Policy Guide
The Policies and Procedures of Hardware Certification
Edition 7.0-3
Legal Notice
Abstract
-
1. Introduction
- 2. The Certification Process
- 3. Hardware Certification Policies
-
-
3.1. Program Policies
-
-
3.1.1. Policy Changes
3.1.2. Red Hat Enterprise Linux
3.1.3. Red Hat Enterprise Linux OpenStack Compute (optional)
3.1.4. Red Hat Enterprise MRG for Realtime (RHEL6) and Red Hat Enterprise Linux for Real Time (RHEL7)
3.1.5. Red Hat Gluster Storage for On-Premise
3.1.6. Certification Life-cycle
3.1.7. Submission Window
3.1.8. Original Certifications
3.1.9. Unpublished Certifications
3.1.10. Component Leveraging
3.1.11. Component Leverage Pools
3.1.12. System Pass-Through Certifications
3.1.13. Component Pass-Through Certifications
3.1.14. Re-Certification
3.1.15. Known Issues
3.2. Software Policies
-
-
3.2.1. Test Suite Versions
3.2.2. Red Hat Enterprise Linux Versions
3.2.3. Red Hat Enterprise MRG Realtime and Red Hat Enterprise Linux for Real Time Versions
3.2.4. Unmodified Red Hat Enterprise Linux
3.2.5. Kernel Boot Parameters
3.2.6. Drivers
3.2.7. SELinux (Red Hat Enterprise Linux 6 and 7)
3.2.8. Red Hat Enterprise Linux as a Host
3.2.9. Red Hat Enterprise Linux as a Guest (Special Partnerships only)
3.3. BIOS/Firmware Policies
- 3.4. Hardware Policies
4. Creating the Test Plan
-
Chapter 1. Introduction
1.1. Audience
1.2. Program Overview
1.3. Certification Prerequisites
-
Red Hat certifies hardware models and not specific configurations of a model. All optional hardware configurations designated as part of the same model must be tested.
-
Testing must be performed with a standard installation of Red Hat Enterprise Linux without special configuration or additional software, including drivers which are not provided by Red Hat.
-
Certifications are currently available for:
-
Red Hat Enterprise Linux 6 and 7.
Also, optionally for:-
Red Hat Enterprise Linux OpenStack Compute 8 and 9
-
Red Hat Enterprise MRG Realtime 2
-
Red Hat Enterprise Linux for Real Time 7
-
Chapter 2. The Certification Process
2.1. Process Overview
-
Create an account with the Red Hat Customer Portal, Red Hat Bugzilla, and the Red Hat Hardware Program.The latest release(s) of the certification test suite (2.6-x and above) provide partners who certify hardware, the ability to use their Red Hat Customer Portal single sign-on (SSO) credentials to log in to the Red Hat Certification site and the Red Hat Certification test suite. The earlier versions of the certification test suite (2.5-x and below) support only the Bugzilla-based login. The Bugzilla-based login method will not be supported after September 2016. We recommend partners who are certifying for the first time to create and use the Red Hat Customer Portal SSO credentials throughout the certification process.Existing partners who have commenced the certification process using Bugzilla credentials are recommended to use the same to complete the certifications which are in progress.
-
Create a new certification in the Hardware Catalog.
-
Review the test plan created for your hardware.
-
Test your hardware until all criteria in the test plan are complete.
-
Ship representative hardware to a Red Hat office.
-
Attain support approval from Red Hat Global Support Services (GSS).
2.2. The Certification Process
2.2.1. Creating Accounts
Note
Procedure 2.1. Creating Accounts
-
Create an account with the Red Hat Hardware Program.
-
Email your sales contact and ask to purchase membership in the program. If you do not have a sales contact at Red Hat, email your technical account manager, partner manager or use the address hwcert@redhat.com for assistance with purchasing program membership.
-
Click the Register button and follow the steps to create a new account with the Red Hat Hardware Program.The account created during this step may also be on the Red Hat Customer Portal and also to log in to the Red Hat Certification site and the Red Hat Certification test suite if you are using the latest release(s) of the certification test suite (2.6-x and above).
-
-
Create a Red Hat Bugzilla accountWe recommend partners who are certifying for the first time to use the Red Hat Customer Portal SSO credentials throughout the certification process. Existing partners who have commenced the certification process using Bugzilla credentials are recommended to use the same to complete the certifications which are in progress.The account created with the Red Hat Hardware Program may be used on the Red Hat Customer Portal, the Red Hat Certification site and the Red Hat Certification test suite if you are using the latest release(s) of the certification test suite (2.6-x and above).
-
Navigate to https://bugzilla.redhat.com/.
-
Select New Account in the menu and follow the instructions.The Red Hat Bugzilla account is also used on the Hardware Catalog.
-
-
Obtain Red Hat Hardware Catalog permissions.
-
File a support request (see Section 2.3, “Giving Feedback and Getting Help”) for create permissions; include your Red Hat Hardware Program (may also be used on the Customer Portal) and Bugzilla login names. A Bugzilla login name is only required if you choose to complete the certification process using Bugzilla credentials supported in certification test suite version(s) 2.5-x and below.After this request has been approved, the Create button appears in the Hardware Catalog menu; this allows you to create a new certification request (see Figure 2.1, “The Hardware Catalog Menu”).
-
2.2.2. Creating a Certification
Procedure 2.2. Create a Certification using the Hardware Catalog.
-
To begin, you must log in to the catalog website located at https://hardware.redhat.com using Red Hat Bugzilla or Red Hat Customer Portal SSO credentials (whichever is applicable).To log in the catalog website using Bugzilla credentials, navigate to https://hardware.redhat.com/, click on the "Hardware Vendor Login" link, then log in to your Hardware Catalog account using your Red Hat Bugzilla login credentials.To log in to the catalog website using Red Hat Customer Portal SSO account credentials, navigate to https://hardware.redhat.com/, click the Account button at the top right of the catalog website and log in using the credentials used on Red Hat Hardware Program. You may also create and use an independent Red Hat Customer Portal SSO account. However it must be an organization account and not a personal account.
-
Click the Create create link from the Hardware Catalog menu.
-
Complete the certification form.Be certain to provide the product specification in the the Product Page URL field. The specifications provided to Red Hat are expected to be the same as would be provided to any customer. The preferred method to provide specifications is via the Specification URL field as shown in Figure 2.2, “The Certification Form - Certification Information” or by attaching the specification document using the Upload Specification section.
Important
Red Hat does not create test plans for certifications without product specifications.To upload a result package containing your hardware product data, select the Acquire from Package radio button in the Product Data Source field shown below. Alternatively, select the Provide Manually radio button. -
Depending on the radio button selected, complete either the Hardware Product Data or Upload Certification Package section.Upload and provide a brief description of the test result package.
-
Click Continue to submit the request.
-
Record the Hardware Certification number displayed on the following screen.
2.2.3. Reviewing the Test Plan
Procedure 2.3. Review the Test Plan
-
Navigate to https://hardware.redhat.com/ and log on to your Hardware Catalog account.
-
Find your system in the Hardware Catalog using either the search functionality located at the top of the page, or by scrolling through the catalog.
-
Click on the Review link in the Sections list at the top of the page and scroll down to the Test Plan Progress subsection.
-
Read through the test plan and ensure you understand how the requirements specified in Section 4.7, “Hardware Class Requirements” apply to your hardware.
2.2.3.1. The Test Plan State
-
Melted
-
The melted state indicates that the test plan is inaccurate or incomplete and is under review by the reviewer assigned to your certification. During this period the reviewer can alter the test plan, therefore, no test results are reviewed when a test plan is in a melted state.
Important
Red Hat does not perform package reviews on certifications with melted test plans.Should you find any inaccuracies with the test plan, you must melt the plan. This process is described in Procedure 2.4, “Changing the State of the Test Plan”.
Frozen
-
The frozen state indicates that the current test plan is valid and complete for the hardware listed in the specification. Test results submitted against a valid test plan are reviewed and recorded in the Test Plan Progress section.
Procedure 2.4. Changing the State of the Test Plan
-
Log on to your Hardware Catalog account and navigate to your certification.
-
In the Test Plan State section, select the Change Test Plan to radio button and select Melted in the drop down box.
-
Click the Save Changes button to submit.
-
Add a comment to the certification that describes why you have melted the plan. This process is described in the procedure Procedure 2.5, “Adding a Comment to the Certification” below.
Procedure 2.5. Adding a Comment to the Certification
-
Log on to your account in the Hardware Catalog and navigate to the Dialog tab.
-
In the Add Additional Comment section, enter the message in the text box.
-
Select either the No response requested or the Request Information From radio button. The latter allows you to choose the intended message recipient.
-
Click the Save Changes button to send the message.
2.2.4. Testing the Hardware
Procedure 2.6. Testing Hardware
-
Execute the
hwcert
utility on the hardware described in the test plan. -
Upload test result packages via your certification request.
-
Navigate to your certification request and click on the Review section as is described in the procedure, Procedure 2.3, “Review the Test Plan”.
-
Scroll down to the section, Upload Results Package or Other Document and complete the form. Please provide a comment describing what tests are expected to be covered by the attached result in the comment box to expedite review.
-
Click on the Attach File button to submit your package.
The reviewer team will analyze the package and record the result in the Test Plan Progress table (see Figure 2.7, “The Test Plan Section”.Note
Product Specification document must be submitted while filling the hardware details during certification creation. -
-
Provide test plan leverage data (Optional)
-
To submit leverage data, choose one of the leverage options from the drop-down. Enter the hardware certification test identification number from which the leveraged data has come from.The Red Hat Hardware Certification team reviews the leveraged data and records the results in the certification. Credited items are marked complete in the Test Plan Progress section. Refer to the Section 3.1.10, “Component Leveraging” section for more information.
Important
Comments and attachments identifying leveraged data are not reviewed. The procedure described above must be used.
-
-
Repeat this procedure until all test plan items in the Test Plan Progress are marked as Confirmed.
2.2.5. Sample Hardware
2.2.6. GSS Support Approval
2.3. Giving Feedback and Getting Help
-
search or browse through technical support articles and solutions about Red Hat products.
-
submit a support case to Red Hat Global Support Services (GSS).
-
access product documentation.
Note
Important
Warning
Chapter 3. Hardware Certification Policies
-
3.1. Program Policies
-
-
3.1.1. Policy Changes
3.1.2. Red Hat Enterprise Linux
3.1.3. Red Hat Enterprise Linux OpenStack Compute (optional)
3.1.4. Red Hat Enterprise MRG for Realtime (RHEL6) and Red Hat Enterprise Linux for Real Time (RHEL7)
3.1.5. Red Hat Gluster Storage for On-Premise
3.1.6. Certification Life-cycle
3.1.7. Submission Window
3.1.8. Original Certifications
3.1.9. Unpublished Certifications
3.1.10. Component Leveraging
3.1.11. Component Leverage Pools
3.1.12. System Pass-Through Certifications
3.1.13. Component Pass-Through Certifications
3.1.14. Re-Certification
3.1.15. Known Issues
3.2. Software Policies
-
-
3.2.1. Test Suite Versions
3.2.2. Red Hat Enterprise Linux Versions
3.2.3. Red Hat Enterprise MRG Realtime and Red Hat Enterprise Linux for Real Time Versions
3.2.4. Unmodified Red Hat Enterprise Linux
3.2.5. Kernel Boot Parameters
3.2.6. Drivers
3.2.7. SELinux (Red Hat Enterprise Linux 6 and 7)
3.2.8. Red Hat Enterprise Linux as a Host
3.2.9. Red Hat Enterprise Linux as a Guest (Special Partnerships only)
3.3. BIOS/Firmware Policies
- 3.4. Hardware Policies
3.1. Program Policies
3.1.1. Policy Changes
Note
3.1.2. Red Hat Enterprise Linux
Important
3.1.3. Red Hat Enterprise Linux OpenStack Compute (optional)
Important
3.1.4. Red Hat Enterprise MRG for Realtime (RHEL6) and Red Hat Enterprise Linux for Real Time (RHEL7)
Important
3.1.5. Red Hat Gluster Storage for On-Premise
3.1.6. Certification Life-cycle
3.1.7. Submission Window
Note
3.1.8. Original Certifications
3.1.9. Unpublished Certifications
Important
Note
3.1.10. Component Leveraging
3.1.11. Component Leverage Pools
3.1.12. System Pass-Through Certifications
3.1.13. Component Pass-Through Certifications
3.1.14. Re-Certification
3.1.15. Known Issues
3.2. Software Policies
3.2.1. Test Suite Versions
Important
3.2.2. Red Hat Enterprise Linux Versions
Note
3.2.3. Red Hat Enterprise MRG Realtime and Red Hat Enterprise Linux for Real Time Versions
3.2.4. Unmodified Red Hat Enterprise Linux
3.2.5. Kernel Boot Parameters
noacpi
is required to boot a system which does not install without that parameter, this would likely be acceptable. If, however, the system would install but corrupts data over time when
noacpi
is not specified, the certification would be suspended until the the situation is resolved. Additional kernel parameters utilized during certification are documented in
Red Hat Knowledge Base Solution associated with the certification listing.
3.2.6. Drivers
/sbin/lsmod
command will also mark technology preview modules with the letter "T" similar to the "U" for unsigned modules.
-
when the driver is included in an official Red Hat Errata and is not required for boot or installation testing (see Table 4.1, “Requirements by Class”) OR
-
when the driver is included in an official Red Hat Enterprise Linux Driver Update Disk OR
-
when the driver is for use with optional hardware (see Chapter 3, Hardware Certification Policies) that is not required to be tested to complete the certification.
Note
Important
Important
Warning
Note
3.2.7. SELinux (Red Hat Enterprise Linux 6 and 7)
3.2.8. Red Hat Enterprise Linux as a Host
3.2.9. Red Hat Enterprise Linux as a Guest (Special Partnerships only)
3.3. BIOS/Firmware Policies
3.3.1. Production Level
3.3.2. Changes
3.3.3. Settings
3.3.4. OS Loaded
3.4. Hardware Policies
3.4.1. Stand-Alone
3.4.2. Components and Peripherals
3.4.3. Production Level
3.4.4. Changes
3.4.5. Configuration Limits
Note
3.4.6. Performance Minimums
Chapter 4. Creating the Test Plan
4.1. Test Plan Overview
-
Define the model by its specification ( Section 4.2, “Models”)
-
Determine the options ( Section 4.3, “Options”)
-
Remove unsupported operating system features and unintentional hardware ( Section 4.4, “Non-OS Features and Unintentional Features”)
-
Apply the minimum test set criteria ( Section 4.5, “Minimum Test Set”)
-
Add the install, boot, and kdump requirements ( Section 4.6, “Installation, Boot, and Kdump Requirements”)
-
Add additional policy requirements ( Chapter 3, Hardware Certification Policies)
Note
4.2. Models
Note
Important
4.3. Options
Important
Important
4.4. Non-OS Features and Unintentional Features
4.5. Minimum Test Set
Warning
4.6. Installation, Boot, and Kdump Requirements
Note
4.7. Hardware Class Requirements
Table 4.1. Requirements by Class
Device Class | Required Tests | Minimum Requirements | Install, Boot, Kdump [a] [b] | General Notes | Leverage Notes |
---|---|---|---|---|---|
All
|
INFO
|
Info is required for all test runs.
|
Test runs without INFO are invalid and will be automatically discarded by the Hardware Catalog.
|
N/A
| |
Battery
|
BATTERY and SUSPEND
|
Required for all models capable of running from battery power.
|
None
| ||
Bluetooth
|
BLUETOOTH
|
A minimum of two machines with Bluetooth capability in proximity to each other.
|
Identical integrated chipsets and removable adapters.
| ||
CD-ROM, DVD, Blu-ray
|
CDROM or DVD or BLURAY
|
I,B
|
The hardware partner is required to support all drives that are part of the model regardless of the specific drive or number of drives used during testing. Equivalent production cycle drive changes are required to be tested internally by the hardware partner. Production cycle drive change test results are not required to be submitted to Red Hat.
|
Drives with identical or lesser media support on the storage controller following the storage controller leveraging policies.
| |
Display Adapter
|
VIDEO
|
The lower of VRAM/VBIOS limits, panel capabilities, or 1024x768 at 24 or 32 BPP.
|
I,B
|
VIDEO test runs may utilize the vesa driver. 3D is not currently tested. GPGPUs are not currently tested.
|
Identical removable cards or integrated chips without shared memory. Decreases in video memory.
|
Ethernet Adapters
|
Each interface @ maximum connection speed.
|
I,B,K
[f]
|
Nominal network connection speed is considered a feature.
|
Identical integrated chipsets and removable adapters.
| |
Express Card Sockets
|
EXPRESSCARD
|
All accessible sockets
|
Devices and inaccessible ports require additional class testing as applicable
Both USB and PCI-E portions are required.
|
None
| |
Fibre Channel
|
NETWORK and/or STORAGE
|
Each interface @ maximum connection speed.
|
I,B,K
[f]
|
Nominal connection speed is considered a feature. Remote attached storage devices may require additional testing. (see
Section 4.8.1, “External Storage and Multipath HBAs”)
|
Identical integrated chipsets, removable adapters, drives and arrays.
|
Fiber Channel over Ethernet (FCoE)
|
STORAGE
|
Identical integrated chipsets and removable adapters.
| |||
IDE/SCSI/SATA/SAS Drives, Arrays, and HBAs
|
STORAGE
|
Maximum storage capacity of local attach arrays if greater than OS limit.
|
I,B,K
[f]
|
Drive capacity are not tracked in context of a system. SATA Controllers require testing in a SATA mode. SAS Controllers require testing with SAS drives.
|
Identical integrated chipsets, removable adapters, drives and arrays.
|
Infiniband
|
INFINIBAND and NETWORK and/or STORAGE
|
Each interface @ maximum connection in FDR(highest), QDR, DDR, SDR(lowest) order.
|
I,B,K
[f]
|
Nominal connection speed is considered a feature. Remote attached storage devices may require additional testing. (see
Section 4.8.1, “External Storage and Multipath HBAs”)
|
Identical integrated chipsets, removable adapters, drives and arrays.
|
I/O Chassis, Port Expanders
|
Applicable testing for integrated additional CTO hardware.
|
I,B
|
Identical integrated chipsets, removable adapters, drives and arrays.
| ||
Integrated Graphics Display
|
VIDEO [LID]
|
Backlight must respond to lid switch if present
|
Identical display + graphics controller + BIOS'
| ||
iSCSI Adapters
|
NETWORK and STORAGE
|
Each interface @ maximum connection speed.
|
I,B,K
[f]
|
Nominal network connection speed is considered a feature.
[g]
|
Identical integrated chipsets and removable adapters.
|
STORAGE
|
Each interface. Maximum storage capacity and format feature set.
|
I,B
|
Multi-Readers follow the Multi-Port Adapter criteria.
|
Identical integrated chipsets, removable adapters. Identical, smaller capacity or feature cards and sticks.
| |
Motherboard / Mainboard
|
System Processor + Memory requirements + all integrated feature classes.
|
Follows the combined class leverage requirements.
| |||
Multi-Function Adapters
|
Applicable test for each function.
|
Follows the combined functional leverage requirements.
| |||
Multi-Port Adapters
|
Functional test(s) on all ports -or- single port where identical chips are replicated for each port -or- maximum number of ports per controller where heads are capped to create a port reduced variation.
|
Follows functional leverage requirements.
| |||
Network Interface Adapters
|
NETWORK
|
I,B,K
[f]
|
Nominal network connection speed is considered a feature.
|
Identical integrated chipsets and removable adapters.
| |
PC Card Sockets
|
PCCARD
|
All accessible sockets
|
Devices and inaccessible ports require additional class testing as applicable
|
None
| |
PCIE, SAS, and SATA SSD Storage Cards and Drives
|
STORAGE
|
Maximum storage capacity and feature set. Capacity is not tracked for SATA and SAS attached SSDs in context of a system certification and should follow the standard SAS and SATA policies instead.
|
I,B,K
[f]
|
Identical integrated chipsets, removable adapters and drives. Models with the same host interface, hardware and firmware designs including reduced features and capacity.
| |
RAID Controllers
|
STORAGE
|
Each OS code path (e.g. where multiple drivers are used) for each interface. Maximum storage capacity of arrays if greater than OS limit.
|
I,B,K
[f]
|
Host RAID/Driver RAID/Fake RAID/etc. use the applicable regular controller policy. Remote attached storage devices may require additional testing. (see
Section 4.8.1, “External Storage and Multipath HBAs”)
|
Identical integrated chipsets, removable adapters, drives and arrays following type criteria. Reduced RAID levels, changes in memory amounts or battery presence.
|
Sound Cards
|
AUDIO
|
Stereo record and playback as applicable.
|
Identical integrated chipsets + codec and removable adapters.
| ||
System Buses
|
I,B
|
Buses without possible active devices do not require testing.
|
Identical integrated chipsets, removable adapters
| ||
System Virtualization
|
Core clock speed, FSB speed, cache size, cache depth and manufacturing size are not considered for feature set review.
[t]
A fully virtualized guest environment using KVM.
REALTIME, RTEVAL and HWLATDETECT require the realtime kernel.
| ||||
System Memory
|
MEMORY
|
The vendor must support the maximum amount of RAM listed in the specification irrespective of the test results submitted. Memory clock speed is not considered for feature review.
|
Equal or lesser quantities where RAM type and memory controller match.
| ||
System Virtualization
|
INFO and CORE and MEMORY in the guest
|
A fully virtualized guest environment (Xen on Red Hat Enterprise Linux 5, KVM on Red Hat Enterprise Linux 6)
|
32-bit and 64-bit Intel and AMD systems with pae and vmx on Red Hat Enterprise Linux 5; 64-bit Intel and AMD systems only on Red Hat Enterprise Linux 6.
| ||
Tape Drives and Changers
|
TAPE
|
Each drive
|
Changers require manual testing with test description and results report.
|
Identical drives and changers. Internal and external versions of the same drives. Models with the same host interface, hardware and firmware designs including reduced features, capacity, media size and/or total slots and drive count in changers/libraries.
| |
USB ports
|
USB, USB2 or USB3, USB 3.1
|
inaccessible ports may substitute attached device class testing.
|
None
| ||
USB devices
|
Each function class at the stated connection version.
|
Class testing as applicable
|
Identical devices.
| ||
Virtual Hardware
|
Each virtualized hardware class.
|
class testing as applicable
|
None
| ||
Wireless Network Interface Adapters
|
Each interface @ maximum connection in N(highest), G, B, A(lowest) order.
|
I,B
|
Nominal network connection speed is considered a feature.
|
Identical integrated chipsets and removable adapters.
| |
[a] Red Hat Enterprise Linux 6 only.
[b] Not required on s390x.
[c] "+" and "-" are considered equal for feature review.
[d] For systems with 50 and 100Gb/s Ethernet options, testing is not required until September 9th 2016. A knowledgebase entry will be added to certifications without passing test results.
[e] For systems with 50 and 100Gb/s Ethernet options, testing is not required until September 9th 2016. A knowledgebase entry will be added to certifications without passing test results.
[f] Required only for integrated hardware.
[g] An alternate valid driver (see
Section 3.2.6, “Drivers”) may be utilized during testing when required; for example use of the software initatior or target instead of the hardware offload engine. A knowledge base entry may be added to the certification to clarify which drivers should be used to end users.
[h] Compensation/Stretching does not qualify as native testing.
[i] A horizontal resolution of 1360 may be used on 1366 native panels.
[j] Optional graphics controllers excluded by other policies are not required to be tested. At least one display + controller combination is required for each display.
[k] Display and graphics controller combinations may be clarified in a Red Hat Knowledge Base Article entry to avoid confusion.
[l] Native resolutions not required during install
[m] Including variants for each (eg. mini, micro, etc.).
[n] Network devices that support NIC partitioning are required to demonstrate both the complete bandwidth and a single partition in one or more test runs.
[o] A knowledge base entry may be added to the certification to clarify when passing results are not provided before the requirement date.
[p] For example, testing a PCI NIC with the NETWORK test tests the PCI bus.
[q] The minimum installed memory is required to match the System Memory testing requirement.
[r] System or OS maximum, whichever is lower.
[s] Integrated non-usable GPUs are ignored during feature set comparison.
[t] Additional testing may be required where maximum system core count is greater than the currently listed OS Certified maximum.
[v] Processor upgrades are defined as field installable physical packages and may require field installable BIOS/firmware upgrades (
Section 3.3, “BIOS/Firmware Policies” apply).
[w] Additional testing may be required where maximum system memory is greater than the currently listed OS Certified maximum.
[x] System Virtualization is leverageable in CPU upgrade leveraging where the existing certification already includes System Virtualization testing.
[y] RHEL 7.3 supports testing of USB 3.1 ports. These ports may be tested using a USB 3.1 device. RHEL 7.3 is required in all RHEL 7.x certifications. In RHEL 6.8, all ports will be tested as USB 3.0 ports.
[z] Red Hat Enterprise Linux 7 only supports 802.11ac devices at 802.11n speeds. Results will be accepted from the WirelessN test on 802.11ac devices until an erratum that provides full 802.11ac connection speeds to Red Hat Enterprise Linux 7 is available.
|
4.8. Additional Manual Testing
4.8.1. External Storage and Multipath HBAs
-
multi-controllers/single host
-
multi-host/single controller
-
multi-controller/multi-host
-
with/without multi-path
-
with/without LUN masking (i.e., dedicating LUNs to specific hosts)
-
a short cable pull (remove cable and restore prior to failure detection)
-
any special features listed as supported on Red Hat Enterprise Linux