Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 2. Managing Red Hat subscriptions

Red Hat Satellite can import content from the Red Hat Content Delivery Network (CDN). Satellite requires a Red Hat subscription manifest to find, access, and download content from the corresponding repositories. You must have a Red Hat subscription manifest containing a subscription allocation for each organization on Satellite Server. All subscription information is available on the Red Hat Hybrid Cloud Console.

Use this chapter to import a Red Hat subscription manifest and manage the manifest within the Satellite web UI.

Subscription allocations and organizations
You can manage more than one organization if you have more than one subscription allocation. Satellite requires a single allocation for each organization configured in Satellite Server. The advantage of this is that each organization maintains separate subscriptions so that you can support multiple organizations, each with their own Red Hat accounts.
Future-dated subscriptions
You can use future-dated subscriptions in a subscription manifest. When you add future-dated subscriptions to your manifest before the expiry date of the existing subscriptions, you can have uninterrupted access to repositories.
Subscriptions service
The Subscriptions service on the Red Hat Hybrid Cloud Console helps you track and manage Red Hat subscription usage across connected and disconnected systems. It collects usage data, displays trends in a centralized dashboard, and supports historical analysis for planning and compliance. For more information, see Section 2.1, “Tracking subscription usage by using the Subscriptions service”.

Additional resources

You can configure your Satellite Server to report usage data to the Red Hat Hybrid Cloud Console by using the foreman_rh_cloud plugin.

Connected Satellite

In the Satellite web UI, navigate to Red Hat Lightspeed > Inventory Upload to configure the foreman_rh_cloud plugin and share inventory information with the Red Hat Hybrid Cloud Console. Ensure that the Automatic Inventory Upload setting is enabled. The plugin enables the subscriptions service to track usage information across connected systems.

You can configure the plugin to omit data that is not needed for subscription tracking, such as host names and IP addresses.

Disconnected Satellite

Export usage data in one of the following ways:

  • Use the foreman_rh_cloud plugin to generate a report locally. You can download the report from the Satellite web UI. The report is in JSON format and is easily integrated for automated scripts or machine processing. You can generate this report by using CLI: 

    # foreman-rake rh_cloud_inventory:report:generate
    Copy to Clipboard Toggle word wrap

  • View product usage by running the Host - Installed Products report.

    Navigate to Monitor > Reports > Report Templates. You can select the format that you want for the report. YAML, JSON, HTML, and CSV formats are supported.

Import a Red Hat subscription manifest into Satellite Server so that you can enable and synchronize Red Hat repositories.

Note

Simple Content Access (SCA) is set on the organization, not the manifest. Importing a manifest does not change your organization’s Simple Content Access status.

Simple Content Access simplifies the subscription experience for administrators. For more information, see the Subscription Management Administration Guide for Red Hat Enterprise Linux on the Red Hat Customer Portal.

Prerequisites

You can import a Red Hat subscription manifest into Satellite Server by using Satellite web UI.

Prerequisites

Procedure

  1. In the Satellite web UI, ensure the context is set to the organization you want to use.
  2. In the Satellite web UI, navigate to Content > Subscriptions.
  3. Click Manage Manifest.
  4. In the Manage Manifest window, click Choose File.
  5. Navigate to the location that contains the Red Hat subscription manifest file, then click Open.

Next steps

  • You can now enable and synchronize Red Hat repositories. For more information, see Importing content in Managing content.

You can import a Red Hat subscription manifest into Satellite Server by using Hammer CLI.

Prerequisites

Procedure

  1. Copy the Red Hat subscription manifest file from your local machine to Satellite Server: 

    $ scp ~/manifest_file.zip root@satellite.example.com:~/.
    Copy to Clipboard Toggle word wrap
  2. Log in to Satellite Server over SSH as the root user.

  3. Import the Red Hat subscription manifest file: 

    $ hammer subscription upload \
--file ~/manifest_file.zip \
--organization "My_Organization"
    Copy to Clipboard Toggle word wrap

Next steps

  • You can now enable and synchronize Red Hat repositories. For more information, see Importing content in Managing content.

2.3. Locating a Red Hat subscription
Copy link

When you import a Red Hat subscription manifest into Satellite Server, the subscriptions from your manifest are listed in the Subscriptions window. If you have a high volume of subscriptions, you can filter the results to find a specific subscription.

Prerequisites

Procedure

  1. In the Satellite web UI, ensure the context is set to the organization you want to use.
  2. In the Satellite web UI, navigate to Content > Subscriptions.
  3. In the Subscriptions window, click the Search field to view the list of search criteria for building your search query.
  4. Select search criteria to display further options.
  5. When you have built your search query, click the search icon.

Additional resources

Use the following procedure to add Red Hat subscriptions to a subscription manifest in the Satellite web UI.

Prerequisites

Procedure

  1. In the Satellite web UI, ensure the context is set to the organization you want to use.
  2. In the Satellite web UI, navigate to Content > Subscriptions.
  3. In the Subscriptions window, click Add Subscriptions.
  4. On the row of each subscription you want to add, enter the quantity in the Quantity to Allocate column.
  5. Click Submit

Use the following procedure to remove Red Hat subscriptions from a subscription manifest in the Satellite web UI.

Warning

Manifests must not be deleted. If you delete the manifest from the Red Hat Customer Portal or in the Satellite web UI, all of the entitlements for all of your content hosts will be removed.

Prerequisites

Procedure

  1. In the Satellite web UI, ensure the context is set to the organization you want to use.
  2. In the Satellite web UI, navigate to Content > Subscriptions.
  3. On the row of each subscription you want to remove, select the corresponding checkbox.
  4. Click Delete, and then confirm deletion.

Every time that you change a subscription allocation, you must refresh the manifest to reflect these changes. For example, you must refresh the manifest if you take any of the following actions:

  • Renewing a subscription
  • Adjusting subscription quantities
  • Purchasing additional subscriptions

You can refresh the manifest directly in the Satellite web UI. Alternatively, you can import an updated manifest that contains the changes.

The Satellite web UI provides a notification before the subscription manifest expires.

Procedure

  1. In the Satellite web UI, ensure the context is set to the organization you want to use.
  2. In the Satellite web UI, navigate to Content > Subscriptions.
  3. In the Subscriptions window, click Manage Manifest.
  4. In the Manage Manifest window, click Refresh.

Additional resources

2.7. Content Delivery Network structure
Copy link

Red Hat Content Delivery Network (CDN), located at cdn.redhat.com, is a geographically distributed series of static webservers which include content and errata designed to be used by systems. This content can be accessed directly through a system registered by using Subscription Manager or through the Satellite web UI. The accessible subset of the CDN is configured through content available to a system by using Red Hat Subscription Management or by using Satellite Server.

Red Hat Content Delivery network is protected by X.509 certificate authentication to ensure that only valid users can access it.

Example 2.1. Directory structure of the Red Hat CDN

$ tree -d -L 11
└── content
    ├── beta
    │   └── rhel
    │       └── server
    │           └── 7
    │               └── x86_64
    │                   └── sat-tools
    └── dist
        └── rhel
            └── server
                └── 7
                ├── 7.2
                │   └── x86_64
                │       └── kickstart
                └── 7Server
                    └── x86_64
                        └── os
Copy to Clipboard Toggle word wrap
  • content – Root directory for the content.
  • beta – Directory responsible for the lifecycle of the content. Common directories include beta (for Beta code), dist (for Production) and eus (For Extended Update Support) directories.
  • rhel – Directory responsible for the product name. Usually rhel for Red Hat Enterprise Linux.
  • server – Directory responsible for the type of the product. For Red Hat Enterprise Linux this might include server, workstation, and computenode directories.
  • 7 – Directory responsible for the release version, such as 7, 7.2 or 7Server.
  • x86_64 – Directory responsible for the base architecture, such as i386 or x86_64.
  • sat-tools – Directory responsible for the repository name, such as sat-tools, kickstart, rhscl.

Some components have additional subdirectories which might vary.

This directory structure is also used in Red Hat subscription manifests.

Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat