SUSE Conversations


System YES Certification and your network adapter(s)

Drew

By: Drew

August 11, 2014 10:36 am

Reads:1,053

Comments:0

Score:5

Print/PDF

How important are those network adapters in your SUSE® Linux Enterprise servers and desktops?

Should you care if your server or desktop network adapters and drivers have been SUSE YES Certified in your system with the current version of the OS?

The correct answers are it’s critical (what’s the point without the network right!) and definitely YES!

Here’s why…well, actually you first get a story from ancient history (in our industry that means more than five but definitely less than ten years ago!). In the early days of YES Certification with SUSE Linux Enterprise, new systems would arrive, and often the network adapter would not be recognized during OS installation. The installation would report that “no network adapter was found” or some terminology like that. Then the OS installation could continue. While installation continued, with no networking, I would often think, “What’s the purpose of this install?” What good does this server or desktop do with no network? Well, that’s one reason why we were certifying the system. Usually the networking adapter hardware was newer than the drivers in the OS and/or the PCI ID did not match the integrated drivers. Through YES Certification we would solve this problem with an updated or add-on driver, then validate the complete configuration, with networking, for compatibility with SUSE Linux Enterprise. BTW, this still happens today, not as often, but it does still happen.

Certification validates the network adapter/driver connection to SUSE Linux Enterprise as well as the physical interface to the network. The last thing you want is for your network to have connectivity issues with your system. Whether you are using one network adapter or 16 high-end server adapters, the adapter/driver needs to be validated to function in your system configuration with SUSE Linux Enterprise. Sometimes the second or third adapter in a system has interrupt conflicts or resource collisions with another adapter; you don’t want to be the one finding these issues.

YES Certification tests for basic network functionality during installation, configuration and stress tests. This testing validates that the network operates correctly while the system and memory are being fully utilized; the disks and storage channel are being pounded with requests; and USB ports are being exercised. With servers it also validates that multiple network adapters will function concurrently. Whether you are using industry standard 1 Gigabit Ethernet adapters, 10 Gigabit adapters or new immerging 40 or 100 Gigabit technologies, certification provides confidence in the network interface. Whether you connect using cables that are copper-based or fiber-based or even a wireless connection, you need to certify the network adapter/driver in your system with the OS.

SUSE YES Certification is indispensable when making hardware decisions. You can fiyes_cert_SLEnd more information about SUSE YES Certification at https://www.suse.com/partners/ihv/yes/ or search for certified hardware at https://www.suse.com/yessearch/. How you can use certification to help you make more informed hardware decisions, justify your proposals to your management and, hopefully, enjoy your summer vacation without interruptions from the office. Stay tuned for more blog entries.

1 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 5 (1 votes, average: 5.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Tags: , , , , ,
Categories: Alliance Partners, Desktop, Enterprise Linux, Expert Views, Integrated Systems, Open Enterprise Server on SLES, Server, SUSE Linux Enterprise, SUSE Linux Enterprise Desktop, SUSE Linux Enterprise Point of Service, SUSE Linux Enterprise Server, SUSE Linux Enterprise Server for System z, SUSE Linux Enterprise Virtual Machine Driver Pack, Technical Solutions, Virtualization

Disclaimer: As with everything else at SUSE Conversations, this content is definitely not supported by SUSE (so don't even think of calling Support if you try something and it blows up).  It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.

Comment

RSS