Creating and managing manifests for a disconnected Satellite Server


Subscription Central 1-latest

Red Hat Customer Content Services

Abstract

This guide describes how to create, export, delete, and modify a manifest for a Red Hat Satellite Server on a disconnected network. Manifests enable you to find, access, synchronize, and download content from the correct repositories for use in the Satellite organizations that are managed by a Satellite Server.

Chapter 1. Using manifests for a disconnected Satellite Server

Only users on a disconnected Satellite Server create and manage subscription manifests from the Customer Portal.

Users on a connected Satellite Server create and manage their subscription manifests in the Manifests section of the Red Hat Hybrid Cloud Console. For information about creating and managing subscription manifests for a connected Satellite Server, see Creating and managing a manifest for a connected Satellite Server.

Chapter 2. Creating a subscription allocation for a disconnected Satellite Server

Users on a connected Satellite Server create subscription manifests in the Manifests section of the Red Hat Hybrid Cloud Console. For information about how to create a manifest for a connected Satellite Server, see Creating a manifest for a connected Satellite Server.

Users using a disconnected Satellite Server can still create a new subscription allocation to set aside subscriptions and entitlements for a system that is offline or air-gapped. This is necessary before you can download its manifest and upload it to a system.

Procedure

To create a manifest for a disconnected or air-gapped Satellite Server, complete the following steps:

  1. From the Subscription Allocations page, click Create Manifest.
  2. Click New Subscription Allocation
  3. Enter a Name for the allocation so that you can find it later.
  4. Select the Type of subscription management application you plan to use on the system.
  5. Click Create.

Chapter 3. Adding subscriptions to a subscription allocation for a disconnected Satellite Server

Only users on a disconnected Satellite Server need to add subscriptions to a subscription allocation. If you are a disconnected user, you must complete this step before you can download the manifest and add it to the host system.

Users on a connected Satellite Server skip this step. For information about managing a subscription manifest for a connected Satellite Server, see Creating and managing a manifest for a connected Satellite Server.

Procedure

To add subscriptions to a subscription allocation for a disconnected Satellite Server, complete the following steps:

  1. From the Subscription Allocations page, click the allocation to which you are adding subscriptions.
  2. Click the Subscriptions tab.
  3. Click Add Subscriptions.
  4. Enter the number of entitlements for each subscription you plan to add. Ensure that you are adding the correct number of entitlements for the system you are using.
  5. Click Submit.
Note
  • You can include future-dated subscriptions, or subscriptions that have a start date in the future, to an allocation.

Chapter 4. Downloading a manifest for a disconnected Satellite Server

Only users on a disconnected Satellite Server download a subscription manifest from the Customer Portal.

Users on a connected Satellite Server download subscription manifests in the Manifests section of the Red Hat Hybrid Cloud Console. For information about how to export and download a manifest for a connected Satellite Server, see Exporting and downloading a manifest for connected Satellite servers.

Procedure

To download a subscription manifest for a disconnected Satellite Server, complete the following steps:

  1. From the Subscription Allocations page, click the allocation that you want to add subscriptions to.
  2. Click the Subscriptions tab.
  3. Click Export Manifest.
Note

The file saves to your default downloads folder.

After you download the manifest, you can import it into your Satellite Server. You can then use the Satellite web UI to update the manifest and refresh it to reflect the changes. Alternatively, you can import an updated manifest that contains the changes. For more information, see Importing a Subscription Manifest into Satellite Server in the Red Hat Satellite Content Management Guide.

Chapter 5. Uploading a manifest to a host system

A system needs a manifest to connect to Red Hat Subscription Management. If you used a subscription allocation to create the manifest, you need to download the manifest first and then upload it to the host system. This situation is useful for systems that are offline or air-gapped.

Procedure

  1. On the local system, copy the manifest:

    Copy to Clipboard Toggle word wrap
    # scp ~/<manifest_file>.zip satellite.example.com:
  2. Import the manifest to your system:

    Copy to Clipboard Toggle word wrap
    # hammer subscription upload \
    --file ~/<manifest_file>.zip \
    --organization "ACME"

Providing feedback on Red Hat documentation

We appreciate your feedback on our documentation. To provide feedback, open a Jira issue that describes your concerns. Provide as much detail as possible so that your request can be addressed quickly.

Prerequisites

  • You have a Red Hat Customer Portal account. This account enables you to log in to the Red Hat Jira Software instance. If you do not have an account, you will be prompted to create one.

Procedure

To provide your feedback, perform the following steps:

  1. Click the following link: Create Issue.
  2. In the Summary text box, enter a brief description of the issue.
  3. In the Description text box, provide more details about the issue. Include the URL where you found the issue.
  4. Provide information for any other required fields. Allow all fields that contain default information to remain at the defaults.
  5. Click Create to create the Jira issue for the documentation team.

A documentation issue will be created and routed to the appropriate documentation team. Thank you for taking the time to provide feedback.

Legal Notice

Copyright © 2025 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
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, Inc.