Transition from RHN Classic to RHSM
Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and has used that experience to build more robust technologies like RHSM.
RHSM will provide solutions that are easier to navigate and scale, and tooling to manage your subscription assignments via the Red Hat Customer Portal. Systems registered as clients to Red Hat Network Classic Hosted either directly or indirectly with Red Hat Proxy need to migrate to RHSM interface tools.
If you are using legacy technologies, you need to shift to RHSM by July 2017.
RHN Hosted UI will sunset in:
Please migrate to RHSM prior to this date to continue receiving support for your subscriptions.
Red Hat Subscription Manager Info
Product Feature Highlights
RHSM manages your contracts, subscriptions, and utilization in a simplified user interface and helps you:
With RHSM, you can also expect regular feature updates including:
- Errata display: View a list of errata affecting a system.
- Labeling: Apply labels to organize systems and subscriptions, as well as take actions such as assigning permissions.
Get Started with Red Hat Subscription Manager
Register a System
To begin using the interface, you must first register your systems to RHSM. Once registered, systems can be managed through the Customer Portal to receive bug fixes, manage updates, view system information and track individual subscriptions and entitlements.
# subscription-manager register --username <username> --password <password> --auto-attach
- Open Terminal.
- Register the system:
# subscription-manager register
Attach a Subscription through Customer Portal
Once registered, systems can be managed through the Customer Portal to receive bug fixes and updates.
- Click Subscriptions from the menu in the top left of your screen.
- Under Manage, click Systems.
- Click on the name of the system you want to modify.
- Click Attach a Subscription.
- Select the desired subscriptions, and click Attach Selected.
Migrating to RHSM
RHSM will provide solutions that are easier to navigate and scale, and tooling to manage your subscription assignments via the Red Hat Customer Portal. Systems registered as clients to Red Hat Network Classic Hosted either directly or indirectly with Red Hat Proxy need to migrate to RHSM interface tools. See Red Hat Subscription Management Migration FAQ for more information.
The user interface for RHN is shutting down July, 2017 and will no longer be supported. Staying on RHN is not recommended. RHSM contains the functionality you need to continue managing your systems.
You will no longer receive updates if the system was not registered prior to the shut down or if there were problems with the system. Satellite systems will no longer be able to register, activate, or sync to RHN Hosted and will need to use RHSM to do so.
- Following the web shut down, you can no longer access the web UI , view system details , edit properties, or update from the Web UI.
- Following the API shut down, you can no longer Register to RHN or Utilize APIs for any system management functions. All other feature shutdowns apply.
- Following the datastore shut down, there will be no more updates, either.
However, as long as you have a registered system that is checking in, you can receive system updates from the command line or system GUI in RHEL as long as there are no problems with the system.
Choose one of the three options below:
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.
- Decide on a configuration that suits your environment.
- Review the virt-who daemon’s prerequisites and ensure that all have been met.
- Install an instance of Red Hat Enterprise Linux for the purpose of running virt-who.
- Install the virt-who daemon.
# yum install virt-who
- 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.
RHN Hosted to RHSM Hosted
Beginning with RHEL versions 5.8 and 6.2, you can run an automatic script that migrates systems registered to RHN Classic 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 Classic 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
# subscription-manager repos --enable rhel-6-server-optional-rpms
# yum install subscription-manager-migration subscription-manager-migration-data
# 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
# yum install subscription-manager-migration subscription-manager-migration-data # rhn-migrate-classic-to-rhsm
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 further action is needed.
If you are using Red Hat Satellite 5, special care needs to be taken with Satellite 5.6 and 5.7 to ensure systems will work properly. Red Hat recently 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. Additionally, reference the following article ‘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 the Red Hat Satellite Lifecycle Support page to help you plan, deploy, and support your systems management infrastructure.
Proxy Server Standalone
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 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 Classiv via Satellite Proxy to Satellite 6.
- Following the RNH UI shut down, you can run the Proxy server from the command line. We highly recommend you transition before this happens, however. It can be challenging to manage the Proxy Server and attach new clients from the command line.
Important: Proxy Server Stand-Alone shuts down on October 31, 2017. Please reference the Satellite and Proxy Server Lifecycle page for more information.