Software Delivery Repository
Software Delivery Repository | Getting Started | FAQSFS: System Foundation Software (formerly SGI® Foundation Software) - HPE Update Server Setup
Oct.2019 Update: Foundation patches are moving to a more secure system, update1.linux.hpe.com, which requires both an email and a token for access. As new products are released, patches for those products will be released to the new server; patches for older releases will be available at the new location as well as at the current locations at download.linux.hpe.com.
SFS is used on HPE MC990X and legacy SGI UV systems. It should not be used on any other systems. The System Foundation Software (SFS) product consists of drivers and technical support tools and utilities designed for the HPE MC990X and SGI UV platforms using specific SUSE(R) Linux Enterprise Server 12, SUSE Linux Enterprise Server 15, Red Hat Enterprise Linux 7, and Red Hat Enterprise Linux 8 releases run more reliably and easier to administer. It provides base functionality required by some other HPE software products, support tools to assist in system maintenance and drivers not yet provided by the base operating systems, as well as packages that help tune systems for improved performance. By consolidating our support tools, utilities and drivers, System Foundation Software (SFS) improves product interoperability and simplifies product dependency management. It also provides packages specifically designed to ensure the smooth operation of SAP software on qualified SGI and HPE in-memory SAP HANA appliances.
An active warranty or support contract is required to access SFS Foundation
product updates. The email associated with the HPE Passport account must be supplied
as the username, and a user-generated token must be supplied as the http password
to access this repository. If you have a valid warranty
or support contract, login with your HPE Passport credentials and
generate your token here. Once you have a valid token, you may access the SGI/HPE Foundation repository with
your web browser (or yum, or zypper) using the following http URL syntax:
Documentation and Support Information
|
Generate_Token
then
Browse token as password |
Subscribe your system to the SGI/HPE Foundation repository
Red Hat Enterprise Linux
Cut-n-paste the following section (substituting ditribution, architecture and project version) into/etc/yum.repos.d/foundation.repo
on your RedHat system:
[foundation]
name=Foundation
baseurl=https://EMAIL:TOKEN@update1.linux.hpe.com/repo/foundation/rhel/dist_ver/arch/project_ver/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/GPG-KEY-HPE-SDR
Where:
EMAIL Email for HPE Passport account; must be URL encoded (e.g., SysAdmin%40some-company.com) (see note below) TOKEN Generated here dist_ver 8.9 - 8.0, 7.9, 7.8, 7.7 arch x86_64 project_ver current, 2.27, 2.26, 2.25, 2.24, 2.23
SUSE Linux Enterprise Server
Cut-n-paste the following section (substituting ditribution, architecture and project version) into/etc/zypp/repos.d/foundation.repo
on your SUSE system:
[foundation]
name=Foundation
baseurl=https://EMAIL:TOKEN@update1.linux.hpe.com/repo/foundation/sles/dist_ver/arch/project_ver/
enabled=1
autorefresh=1
type=rpm-md
keeppackages=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/GPG-KEY-HPE-SDR
Where:
EMAIL Email for HPE Passport account; must be URL encoded (e.g., SysAdmin%40some-company.com) (see note below) TOKEN Generated here dist_ver 15sp5, 15sp4, 15sp3, 15sp2, 12sp5, 12sp4, 12sp3 arch x86_64 project_ver current, 2.27, 2.26, 2.25, 2.24, 2.23
Import the GPG Key
Copy the GPG-KEY-HPE-SDR key to /etc/pki/rpm-gpg/
and then import the key with the following command:
rpm --import /etc/pki/rpm-gpg/GPG-KEY-HPE-SDR
Installing SGI/HPE Foundation packages
List available packages
# yum --disablerepo="*" --enablerepo="foundation" list available
# zypper search --repo foundation
Show available updates
# yum --disablerepo="*" --enablerepo="foundation" check-update
# zypper list-updates --repo foundation
Install a specific package
# yum install packagename
# zypper install packagename
URL Encoded Emails
In order for the yum and zypper to pass the correct email address to the authentication protocols on the Software Delivery Repository, email addresses in the *.repo files must be URL encoded. For most email addresses, changing the "@" to "%40" is sufficient. For instance, "john.smith@company.com" would be entered as "john.smith%40company.com" in the *.repo file. You may use the URL encoded values from the list below or use an online tool like URL Decode and Encode to help encode your email address.
@ = %40 & = %26 / = %2F ` = %60 space = %20 ! = %21 ' = %27 = = %3D { = %7B , = %2C # = %23 * = %2A ? = %3F | = %7C . = . $ = %24 + = %2B ^ = %5E } = %7D % = %25 - = - _ = _ ~ = ~