Software Delivery Repository
Software Delivery Repository | Getting Started | FAQHPE Data Management Framework (DMF) Suite - HPE Update Server Setup
Oct.2019 Update: DMF Suite 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.
The HPE Data Management Framework (DMF) Suite combines the following software into a single distribution:
The single distribution improves product interoperability and reduces the administration of product dependencies.
An active warranty or support contract is required to access DMF Suite
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, log in with your HPE Passport credentials and
generate your token
here. After you have a valid token, you may access the DMF Suite repository via your web browser, yum, or zypper using the following http URL syntax:
|
Generate_Token
then
Browse token as password |
Subscribe your system to the HPE DMF Suite repository
Red Hat Enterprise Linux
Copy the following section (substituting token, distribution, architecture and project version) into/etc/yum.repos.d/hpe-dmfsuite-updates.repo
on your RHEL system:
[hpe-dmfsuite-updates]
name=HPE DMF Suite Updates
baseurl=https://EMAIL:TOKEN@update1.linux.hpe.com/repo/dmfsuite/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 7.5, 7.6 ARCH x86_64 PROJECT_VER 4.1, 4.1.1
The updates for DMF 7 components are maintained in a separate repo. To update the DMF 7 specific components copy the following section (substituting token, distribution, architecture and project version) into
/etc/yum.repos.d/hpe-dmf7-updates.repo
on your RHEL system:
[hpe-dmf7-updates]
name=HPE DMF 7 Updates
baseurl=https://EMAIL:TOKEN@update1.linux.hpe.com/repo/dmfsuite/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 7.5, 7.6 ARCH x86_64 PROJECT_VER dmf7.1, dmf7.1.1
SUSE Linux Enterprise Server
Copy the following section (substituting token, distribution, architecture and project version) into/etc/zypp/repos.d/hpe-dmfsuite-updates.repo
on your SLES system:
[hpe-dmfsuite-updates]
name=HPE DMF Suite Updates
baseurl=https://EMAIL:TOKEN@update1.linux.hpe.com/repo/dmfsuite/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 12sp3, 12sp4 ARCH x86_64 PROJECT_VER 4.1, 4.1.1
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
Install DMF Suite packages
List available packages
# yum --disablerepo="*" --enablerepo="hpe-dmfsuite-updates" list available
# yum --disablerepo="*" --enablerepo="hpe-dmf7-updates" list available
# zypper search --repo hpe-dmfsuite-updates
Show available updates
# yum --disablerepo="*" --enablerepo="hpe-dmfsuite-updates" check-update
# yum --disablerepo="*" --enablerepo="hpe-dmf7-updates" check-update
# zypper list-updates --repo hpe-dmfsuite-updates
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 - = - _ = _ ~ = ~