Migrating to Red Hat Subscription Management

Updated -

Red Hat shut down the RHN UI on July 31, 2017.

If you have not transitioned to RHSM yet, you need to do so to continue receiving support for your subscriptions. You can no longer receive updates if the system, either. Satellite systems can no longer be able to register, activate, or sync to RHN Hosted and will need to use RHSM to do so. If you need help determining the systems you use with RHN, try our new RHN System List Exporter lab app.

RHN end-of-life timeline

  • July 31, 2017: No access to the web user interface (UI) and no ability to view system details, edit properties, or update from the web UI for any systems still on RHN.

  • October 31, 2017: No longer able to register systems to RHN Hosted.

  • March 31, 2018: No longer able to update any systems still registered to RHN.

  • For more information, see the Red Hat Subscription Management Migration FAQ.

Virt-who pre-requistes

If you have a virt-limit=unlimited subscription (e.g., a data center), you need to set up virt-who before migrating to RHSM from RHN. If you don’t set up virt-who prior to the migration, repositories and/or subscriptions may fall off of any system that is using a virt-who required subscription.

  1. Decide on a configuration that suits your environment.
  2. Review the virt-who daemon’s prerequisites and ensure that all have been met.
  3. Install an instance of Red Hat Enterprise Linux for the purpose of running virt-who.
  4. Install the virt-who daemon:
# yum install virt-who
  1. Establish connections between the virt-who daemon and your hypervisors.

Note: virt-who setup needs to be completed within 24 hours after the process is initiated.

Migrating from RHN Hosted to RHSM Hosted

Beginning with RHEL versions 5.8 and 6.2, you can run an automatic command that migrates systems registered to RHN to RHSM. This is the supported method for migrating systems.

Note: Before you begin, the system you are migrating needs the subscription-manager-migration and subscription-manager-migration-data packages installed. These packages enable the RHN channels to the Customer Portal Subscription Management product certificates to be mapped during migration. If you do not have these packages installed beforehand, you need to install them manually:

Run the command:

# yum search subscription-manager-migration -v

If necessary, enable the supplementary repositories which contain the migration RPMS:

# subscription-manager repos --enable rhel-6-server-optional-rpms

Install the migration tool packages:

# yum install subscription-manager-migration subscription-manager-migration-data

Once the migration packages are installed, you can migrate from RHN to Subscription Management. The rhn-classic-to-rhsm command uses this syntax:


After the migration is completed, run the following command to confirm the details.

# subscription-manager facts --list | grep migr
migration.classic_system_id: 09876
migration.migrated_from: rhn_hosted_classic
migration.migration_date: 2012-09-14T14:55:29.280519

Install the migration tool packages:

# yum install subscription-manager-migration subscription-manager-migration-data

Run the migration command:

# rhn-migrate-classic-to-rhsm

Migrating from Satellite 5 to RHSM

If you are using Red Hat Satellite 6, changes planned for RHN subscription services in July, 2017 will not impact you, and no action is needed.

If you wish to continue using Red Hat Satellite 5, we highly recommend upgrading to the recently released Satellite 5.8 version as soon as possible. Satellite 5.8 has the ability to both register via Red Hat Subscription Manager (RHSM) and retrieve content from the Content Delivery Network (CDN). Additionally, Satellite 5.8 will offer Extended Lifecycle Support beginning in early 2019, if you wish to continue using Satellite 5 after that date. All other versions of Satellite 5 will end-of-life after January 31, 2019.

If you do wish to stay on Satellite 5.6 & 5.7 for a period of time, your servers will need to be migrated from Red Hat Network (RHN) to Red Hat Subscription Management (RHSM). Special care needs to be taken with Satellite 5.6 & 5.7 servers to ensure the systems will work properly. Red Hat has released an erratum on this topic with instructions for allowing a Satellite 5.6 or 5.7 system registered via RHSM to continue to sync via satellite-sync. You can also reference Prepare Satellite 5 systems for Red Hat Network’s End of Life, which walks you through the steps of migrating your systems.

As always, you can reference Red Hat Satellite Lifecycle Support to help you plan, deploy, and support your systems management infrastructure.

Migrating from Red Hat Satellite Proxy Server Stand-Alone to RHSM

Red Hat Satellite Proxy Server Stand-Alone is a component of Red Hat Satellite which uses the Proxy server as a stand-alone (Satellite-less) offering.

  • We recommend that you transition from Red Hat Proxy Server Stand-Alone to Satellite 6. Work with your Red Hat Account Manager to determine what Satellite subscriptions are best suited to your organization. Review the steps you need to take to migrate systems registered to RHN Classic via Satellite Proxy to Satellite 6.

  • You can currently run the Proxy server from the command line, but it can be challenging to manage the Proxy Server and attach new clients from the command line. Therefore, we highly recommend you transition before this happens.

Important: Proxy Server Stand-Alone shuts down on October 31, 2017. You can also reference Satellite and Proxy Server Lifecycle for more information.

Additional migration resources