Subscription Asset Manager (SAM) Quick Start Guide

Solution Verified - Updated -


  • Red Hat Enterprise Linux 7.0 and later releases
  • Red Hat Enterprise Linux 6.1 and later releases
  • Red Hat Enterprise Linux 5.7 and later releases
  • Subscription Asset Manager (SAM) 1.4 installed on Red Hat Enterprise Linux 6.6 Server, 64-bit architecture (x86_64)


  • How do I get started with Subscription Asset Manager (SAM)?


WARNING: Subscription Asset Manage reached it's End of Life on October 31st, 2018.

Installing SAM at this point still receives support until that date, but it is highly recommended to use an alternative method to manage your system subscriptions.

Planning: Network topology
  • LAN or vLAN connection is recommended between SAM and managed RHEL systems
  • Access to secure http ports 443 and 8088  is required
  • See details on above and other prerequisites (such as disk space) in official documentation - Installing Subscription Asset Manager

Alt text

Planning: Enhanced Reporting
Install SAM
  • Install Red Hat Enterprise Linux 6.6, 64-bit architecture (x86_64).

    • Although SAM can manage subscriptions on RHEL 5, RHEL 6, and RHEL 7 clients, the application itself requires RHEL 6.6 to run
  • Subscribe using either Red Hat Subscription Management or Red Hat Network (RHN) Classic. Red Hat Subscription Management is recommended.

  • If installing from ISO, see Installing Through an ISO Image

  • If using Red Hat Network (RHN) Classic, add "SAM for RHEL Server (v. 6 64-bit x86_64) " channel sam-rhel-x86_64-server-6.

  • If using Red Hat Subscription Management, start subscription-manager, see Installing Using yum

    • Register the SAM host system with --autoattach option (wait a few minutes for it to complete adding content repositories)

      subscription-manager register --auto-attach
    • Run the following command to enable the rhel-6-server-sam-rpms repository and disable Enhanced Updates (EUS) repository

      subscription-manager repos --enable rhel-6-server-sam-rpms --disable rhel-server-rhscl-6-eus-rpms
    • Then, install Subscription Asset Manager using

      yum install -y katello-headpin-all
    • Then, configure Subscription Asset Manager (see Additional Examples of the Configuration Script for options to override default values or populate from answer file) with following command (the --org option is not required but helpful to set to the name of the initial organization name for your deployment, otherwise it defaults to "ACME_Corporation")

      katello-configure --deployment=sam --org=Name_of_Your_Org --user-pass=Your_Admin_Password

alt text

Subscription Manifest
  • Log into Customer Portal:
    Select Subscriptions->Overview
    Click on Subscription Management
    Click on Register under Subscription Management Applications
    Choose Subscription Asset Manager Organizations in dropdown and enter the name of the Organization from above SAM install
    Attach subscriptions
    Download manifest

alt text

Subscription-manager on managed RHEL systems
  • Verify that subscription-manager is installed and updated to the newest version

    • RHEL 5.7, 5.8, 5.9, 5.10, 6.1, 6.2, 6.3, 6.4, and 7.0 are supported
  • Required Upgrades

    • A new model of pricing and counting subscriptions were coincident with the Subscription Asset Manager 1.3 release. In addition, SAM 1.4 contains pricing changed in RHEL 7 release. SAM 1.4 (and updated Red Hat Subscription Manager) can properly parse and apply these updated subscriptions as well as the former subscription structure. Older versions of Subscription Asset Manager cannot.

    • See SAM release notes - SAM 1.4 Release Notes

  • Review Systems and Subscriptions concepts

  • Install the configuration RPM and register system to the SAM server - see Registering a System.

  • Refer to Managing Systems and Subscriptions for instructions to use System Groups, view installed Products for a System, attach and remove Subscriptions, configure and run auto-attach.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.


Page 5 of the Red Hat document I have entitled "Red_Hat_Subscription_Asset_Manager-1.1-Installation_Guide-en-US" clearly states that the self-hosted SAM system must be a physical server. Is this still the case? This one limitation is preventing us from standing up a SAM server. Unfortunately, the requirement that the SAM server be a physical server is a non-starter for our organization.

Thank you for your interest in Subscription Asset Manager. We'll investigate if we can waive a requirement for a physical server.

You can run SAM on a virtual machine. I have entered to track this issue.

We can officially run SAM on a VM, and will be supported if it breaks? I assume it will work fine on a VM, but I need to know it's supported.

Again, from version 1.1 of the SAM Guide:

Chapter 2. Installation

2.1. Installing from the Repository
2.2. Installing in a Virtual Environment

Installation of Subscription Asset Manager is done on a physical networked host. Subscription Asset Manager is included with a Red Hat subscription at no additional cost. You need to have a valid Red Hat Network (RHN) subscription, and be registered to RHSM to begin your installation of Subscription Asset Manager. You can use Subscription Asset Manager to manage subscriptions on both physical systems and virtual machines.

Thanks for the update.

Above I quoted text from SAM 1.1 doc

SAM 1.0 doc lacks the physical requirement text, and the SAM 1.2 Beta doc says:

Chapter 2. Installation

2.1. Installing from the Repository
2.2. Installing from ISO

Installation of Subscription Asset Manager can be done on a physical or virtual networked host.

Do we know if installing and running SAM will allow us access to a RHEL YUM repository? We have a large VM Farm that we need to plug into a YUM repo for package management. We want our config management systems (chef/puppet) to be able to programmatically install packages.

Hello, this will be part of Red Hat Satellite 6, which also provides content and system management whereas SAM only provides subscription management.

Red Hat Satellite 6 is not yet generally available but you may be interested in taking a preview with the Managed Design Program - to learn more and/or sign up please visit


I am having issues with my manifest upload, how can I stop it and restart the upload? It is running for 2 days now.

Kind regards,

Jan Gerrit Kootstra

The TCP session initiation directions (i.e. for the 443 and 8088) need to be declared here so fw rules can be set.

Could you please clarify what needs to be opened in the firewall for TCP port 443 and 8088! What is source and what is destination?
Should the SAM server be able to talk to Red Hat over the Internet? Which addresses in that case? The SAM server can´t do that communication through the local Satellite server?

Do you plan to launch the new version? The last which I have got is sam-1.4-20140512-rhel-6-x86_64.iso. And mabye version for RHEL7.