Register a Red Hat Enterprise Linux system with the Red Hat Customer Portal, attach a subscription, and enable the software repositories needed for updates and support.
subscription-manager registersubscription-manager attachsubscription-manager listsubscription-manager reposinsights-clientA freshly installed RHEL system is unregistered by default — it can't download software updates, install packages from Red Hat's official repositories, or receive support. Registering the system links it to a Red Hat account and an active subscription.
Registration gives a system access to:
dnf update.
Red Hat subscriptions are tracked through a hierarchy of concepts. Understanding the terms makes troubleshooting registration issues far easier.
| Term | Meaning |
|---|---|
| Red Hat account | Your login on the Red Hat Customer Portal |
| Organization (org) | A group of accounts and subscriptions, identified by an org ID |
| Subscription | An entitlement purchased from Red Hat, covering a number of systems |
| Entitlement certificate | The certificate installed locally that proves a system is covered |
| Simple Content Access (SCA) | Modern model where an org-registered system gets repository access automatically, without manually attaching an individual subscription |
subscription-manager attach is often unnecessary — registering the system is enough to unlock repositories. Older or legacy accounts may still use entitlement-based attachment.
The subscription-manager tool handles registration, subscription attachment, and repository configuration from the command line.
# Register interactively — prompts for username and password subscription-manager register # Register non-interactively with credentials on the command line subscription-manager register --username=admin --password='********' # Register to a specific organization subscription-manager register --org=12345678 # Register using an activation key instead of a username/password subscription-manager register --org=12345678 --activationkey=rhel-key
--password directly on the command line can leave it visible in shell history and process listings. Prefer the interactive prompt, or an activation key, for anything beyond a quick lab exercise.
# Confirm whether the system is currently registered subscription-manager status # Show identity details for the registered system subscription-manager identity # Unregister the system entirely subscription-manager unregister
On accounts that still use entitlement-based subscriptions (rather than Simple Content Access), a system must have a subscription attached before repositories become available.
# List subscriptions available to this account, not yet attached subscription-manager list --available # Attach a specific subscription by its pool ID subscription-manager attach --pool=8a85f XXXXXXXXXXXXXXXX # Let subscription-manager pick a suitable subscription automatically subscription-manager attach --auto # List subscriptions currently attached to this system subscription-manager list --consumed
--auto is convenient for a single system, but in larger environments administrators typically use activation keys tied to the correct subscription pool so every new system attaches consistently.
Once registered (and, if required, attached), subscription-manager exposes the repositories the subscription entitles the system to use. Not every available repository is enabled by default.
# List every repository this system is entitled to see subscription-manager repos --list # Enable a specific repository subscription-manager repos --enable=rhel-9-for-x86_64-appstream-rpms # Disable a repository you no longer need subscription-manager repos --disable=rhel-9-for-x86_64-supplementary-rpms # Confirm which repositories dnf will actually use dnf repolist
*-baseos-rpms and *-appstream-rpms repositories enabled. If dnf install can't find a package you expect, check subscription-manager repos --list before assuming the package doesn't exist.
Red Hat Insights is a proactive analytics service included with a RHEL subscription. Once a system is connected, Insights compares its configuration against a continuously updated rule set and flags security risks, stability issues, and performance problems before they cause an outage.
# Register this system with Insights (registering with subscription-manager # often connects Insights automatically, depending on defaults) insights-client --register # Manually trigger a one-time data collection and upload insights-client # Check the client's connection status insights-client --status
dnf can pull fromsubscription-manager attach generally required? Why or why not?dnf install and a package can't be found, even though you know it should exist. What command would you check first, and why?