Subscriptions/Manifests for Disconnected Satellites

Latest response

Hi all!
I have a quick question about how to properly manage the subscriptions and manifests for our Satellite Servers.

Here's the setup we want to use:

2x Satellite Servers (v6.3.2)
- 1x Connected
- 1x Disconnected
4x RHEL Servers (v7.5)
- 2x Connected
- 2x Disconnected

Subscriptions and registrations:

  • 1x Satellite Server (Connected)
    • Registered and attached using subscription-manager
    • Consumes 1x Satellite Subscription
    • Upload a Manifest with the following subscription entitlements
      • 1x Satellite Server (to be used for disconnected Satellite)
      • 2x RHEL Sever (to be used for connected RHEL Servers)
    • Create 1x Activation Key for Satellite Server
    • Create 2x Activation Key for RHEL Server
  • 2x RHEL Server (Connected)
    • Registered to the connected Satellite Server via Activation Key
    • Consumes 2x RHEL Server subscriptions
  • 1x Satellite Server (Disconnected)
    • Air-gapped secure network
    • Registered with Activation Key from connected Satellite Server
    • Consumes 1x Satellite subscription
    • Upload manifest with 2x RHEL Server subscription entitlements
    • Create 2x Activation Key for RHEL Server
  • 2x RHEL Server (Disconnected)
    • Air-gapped secure network (same as disconnected Satellite)
    • Registered via Activation Key from disconnected Satellite
    • Consumes 2x RHEL Server subscriptions

Do I have that correct? I.e. the disconnected Satellite doesn't need a manifest with a Satellite entitlement because it's not going to register any further downstream Satellites, thus it only needs a manifest with 2x RHEL entitlements?

In total we'd have 2x Satellite and 4x RHEL subscriptions.

Thanks!

Edit: It looks like I cannot use an activation key to register the disconnected Satellites. Still looking for a solution to keep those up to date.

Responses