Linux CSP and Errata Kernels

[Keith Howells]

Wanted to know if there is any documention that lays out what steps need to happen after applying an errata kernel to a system that had previously had the Linux PSP installed? I know some drivers come as source rpm's and need to be installed and new binary rpm's created; I'd like to know step by step what the process is and which pieces need to be built from source.

Any feedback is appreciated.
Thanks!

[Michael Garner_1]

Keith,
You should re-install the Linux CSP after installation of an errata kernel. The Linux CSP keeps track of what kernels were used during each installation. If you change the errata kernel, the Linux CSP will know which files need to be updated, even if their installed version is the same. In the Installed Version field, you will see "Re-install Required" instead of a version to note which drivers/utilities need to be re-installed/re-built.

If you want to do it manually, then you will need to re-build/re-install all of the NIC drivers based on the hardware you have installed in your server and possibly some of the storage drivers depending on whether the binary RPMs support the currently installed kernel. If you want to use the Linux CSP to see if a driver supports a given kernel, you can use the "./install???.sh --view RPMNAME" command to see the minimum and maximum errata kernels each RPM supports. If the maximum errata kernel is set to 2.4.99-99, then it means the RPM should be able to support any 2.4 kernel unless there are changes in the kernel that prevent it from working.

If you have more questions, please post them to this issue and I'll be happy to address them.

Regards,
Michael Garner
Linux PSP Developer

[Keith Howells]

I'll give that a try. Is there a way to see in the TUI install routine what drivers require a re-install? I'm trying to document the process to share with other engineers worldwide so they know what has to take place post errata install. It sounds like the best solution based on your feedback is to perform a reinstall which I can document. I've only ran the TUI mode install script install640.sh, never tried the X based deployment utility yet. Thanks again for your help.

[Michael Garner_1]

Keith,
The output of the --view command will give you the current status (including the Re-install Required) at the TUI.

Regardless of whether you use the GUI or the TUI, we only update the components that require re-installation based on the new errata kernel.

I'll also add the current status to the output you get from the TUI for the next release. This will allow you to see the current status and version that is installed in addition to the name and version of what is being installed during TUI.

Thanks,
Michael Garner

[Keith Howells]

Thank you. Sounds good. I will put together a quick document based on what HP has provided for the install process. Do you recommend using the 7.00 version of the PSP? I have not yet tested that version yet. We run RedHat Enterprise Linux 2.1 AS/ES and will be moving the 3.0 Update 1 as some of our tools become supported.

[Michael Garner_1]

I would definitely recommend using the latest version (ie 7.00) of the Linux PSP for RHEL/RHAS 2.1. HP updated and tested the drivers to work with the e.37 kernel. The 6.40 release was only tested up through the e.27 errata kernel.

On RHEL3, I would strongly recommend that you use Update 1 or later.

If you have more questions, let me know.