Show Table of Contents
2.3. Migrating from RHN Classic to Customer Portal Subscription Management
Note
If you have a virt-limit=unlimited subscription (e.g., a Virtual Data Center entitlement), 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.
A system which was registered against the hosted subscription service, RHN Classic, can be migrated to Customer Portal Subscription Management using the
rhn-migrate-classic-to-rhsm script.
The general action is that it unregisters the system from RHN Classic, registers it with Customer Portal Subscription Management, and opens Subscription Manager (either GUI or CLI) to attach subscriptions.
The
rhn-migrate-classic-to-rhsm script has this syntax:
rhn-migrate-classic-to-rhsm [--force|--gui|--help|--no-auto|--servicelevel=SERVICE_LEVEL]
After running migration, the system facts list what script was used for migration and what the previous system ID was.
[root@server ~]# 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
This makes it easy to track the migration process for systems within the infrastructure.
Comparison for migration:
Please refer to the following table for comparisons between RHN Classic and Red Hat Customer Portal Subscription Management capabilities. Note, this table may contain statements regarding future services not yet approved for implementation and does not indicate a commitment for delivery.
Additional information on migration options and deployment strategies for RHN Classic Hosted customers can be found at: "Transition of Red Hat Network Classic Hosted to Red Hat Subscription Management" and "RHN Classic Hosted/stand-alone Proxy Customer Options for Red Hat Enterprise Linux 7 (RHEL 7)"
|
Feature/Function
|
RHN Classic
|
Red Hat Portal (Red Hat Subscription Management)
|
|
Red Hat Product Support
| ||
|
Red Hat Enterprise Linux versions supported
|
All current products and versions in Red Hat Enterprise Linux 4 All current products and versions in Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6 All current products and versions in Red Hat including Enterprise Linux 7 are supported via Red Hat Satellite 5.7 But not via RHN Classic Hosted or stand-alone Proxy)
|
Red Hat Enterprise Linux 5 (5.7 and newer) Red Hat Enterprise Linux 6 (6.1 and newer) Red Hat Enterprise Linux 7 Intended for future versions of Red Hat Enterprise Linux
|
|
Red Hat Enterprise Virtualization versions supported
|
All current products and versions including RHEV 2.1, 2.2, 3.0
|
RHEV 3.0 and newer
|
|
Red Hat Enterprise Linux Migration to RHSM support?
|
N/A
|
YES, for Red Hat Enterprise Linux 5 (5.8 and newer) - via migration tooling as described in Red Hat Subscription Management
YES, for Red Hat Enterprise Linux 6 (6.3 and newer) - via migration tooling as described in Red Hat Subscription Management and How to migrate a Red Hat Enterprise Linux System from RHN Classic to RHSM
|
|
Red Hat Satellite 5
|
YES, all versions of 5.x
|
PARTIAL, Satellite 5 certificates can be issued from Customer Portal. Satellite 5.6 or 5.7 can be integrated with SAM 1.3+ to provide subscription status reporting
|
|
Red Hat Satellite 6
|
NO
|
YES
|
|
Support for all product SKUs
|
YES, but future product products may not be enabled for RHN Classic
|
YES, with a small number of exceptions and Why aren’t my subscriptions available in Red Hat Subscription Management?
|
|
Subscription Management Support
| ||
|
Default Client for installation method
|
Red Hat Enterprise Linux 5 (5.7 and older) Red Hat Enterprise Linux 6 (6.1 and older) All Red Hat Enterprise Linux 4
|
Red Hat Enterprise Linux 6 (6.3 and later) Red Hat Enterprise Linux 5 (5.9 and later) future versions of Red Hat Enterprise Linux
|
|
Content Basis for Client
|
RHN Classic
rhn-channel command and What is the command "rhn-channel" and how to use it?
|
Red Hat Subscription Manager
subscription-manager command to register and add subscriptions
|
|
Command line utilities for Client
| yum update (Red Hat Enterprise Linux 5 and later), up2date (Red Hat Enterprise Linux 4)
| yum update
|
|
System registration
| rhn_register, rhnreg_ks
| subscription-manager register and How to register and subscribe a system to the Red Hat Customer Portal using Red Hat Subscription-Manager
|
|
Activation keys
|
YES, with Smart Management subscriptions
|
YES, via Red Hat Subscription Asset Manager (SAM), Red Hat Satellite 6, and now also the Red Hat Customer Portal)
|
|
List subscriptions available to apply to installed system on Client
|
N/A
| subscription-manager list --available
|
|
Force list all subscriptions on Client
|
N/A
| subscription-manager list --available --all and Why can’t I see available subscriptions for my system in Red Hat Subscription Management?
|
|
Smart autosubscribe a subscription
|
N/A
| subscription-manager register --autosubscribe How do I subscribe to a channel in Red Hat Subscription Management?
|
|
Graphical user interface utilities for Client
|
System → Administration → RHN Registration
|
System → Administration → Red Hat Subscription Manager
|
|
Package update utility
| /usr/bin/yum System → Administration → Add/Remove Software
| /usr/bin/yum System → Administration → Add/Remove Software
|
|
Yum plugin support
| yum-rhn-plugin (provides rhnplugin.conf)
| subscription-manager (provides subscription-manager.conf and product-id.conf)
|
|
Web-based administration tool for customers
| ||
|
Support for updating content through Content Delivery Network
|
YES
|
YES
|
|
Email errata notifications
|
YES
|
YES
Satellite 6.1: Subscribing to Errata Notifications
|
|
Support for IP-Based Firewall Rules
| ||
|
Support for
sosreport diagnostics logging
|
YES
|
YES
|
|
Optional and Supplementary Channels available?
|
YES, but off by default Many devel packages are not available in Red Hat Enterprise Linux
| |
|
Support for subscription status
|
PARTIAL, Red Hat Satellite 5.6 or 5.7 can be integrated with Red Hat SAM 1.3+ for subscription status
|
YES
|
|
Support for subscription consumption reports
|
PARTIAL, Red Hat Satellite 5.6 or 5.7 can be integrated with Red Hat SAM 1.3 for subscription status
|
YES, via Red Hat Subscription Asset Manager FUTURE, via Red Hat Satellite 6
|
|
System Management Support
| ||
|
Support for Smart Management Red Hat Enterprise Linux Add-On
|
YES
|
YES, with Red Hat Satellite 6
|
|
Support for machine provisioning and monitoring
|
YES, with Smart Management subscriptions
|
YES, via Red Hat Satellite 6 provisioning feature
|
|
Content Management Support
| ||
|
Content Download GUI
|
YES
|
YES
|
|
Support for remote updating
|
YES, with Smart Management subscriptions
|
NO
|
|
Support for offline updating
|
YES, via Red Hat Satellite 5
|
FUTURE, via Red Hat Subscription Asset Manager YES, via Red Hat Satellite 6
|
|
Support for proxied updating
|
YES, via Red Hat Satellite Proxy 5
|
YES, via Red Hat Subscription Asset Manager (SAM) and Red Hat Satellite 6 Capsule Server
|
2.3.1. Basic RHN Classic to Customer Portal Subscription Management Migration
Simply running the
rhn-migrate-classic-to-rhsm tool migrates the system profile, registers the system with Customer Portal Subscription Management Subscription Management, and autoattaches the system to the best-matched subscriptions. Optionally, administrators can also set a service level preference for the system, which is used to help evaluate what subscriptions to select.
While administrators only have to run the command, the script itself runs through a series of steps to migrate the account.
[root@server ~]# rhn-migrate-classic-to-rhsm --servicelevel=premium RHN Username: jsmith@example.com Password:
The script prompts for the username and password to use to connect to Red Hat Network. It uses these credentials to authenticate to both Red Hat Network Classic and Red Hat Network Subscription Management, to verify the account settings.
Once the account is verified, the script creates a channel list for the system.
Retrieving existing RHN classic subscription information ... +----------------------------------+ System is currently subscribed to: +----------------------------------+ rhel-i386-client-5
Each discovered channel is then mapped to a corresponding product certificate (Section 2.4, “Looking at Channel and Certificate Mappings”). Not every product has a product certificate, so not every channel may have a map. Only the products with a channel have a corresponding certificate map.
The matching certificates are installed in the
/etc/pki/product directory.
List of channels for which certs are being copied rhel-i386-client-5 Product Certificates copied successfully to /etc/pki/product !!
Then, the script unregisters the system from RHN Classic.
Preparing to unregister system from RHN classic ... System successfully unregistered from RHN Classic.
Then, it registers the system with Customer Portal Subscription Management.
Attempting to register system to RHN ... The system has been registered with id: abcd1234 System server.example.com successfully registered to RHN.
The script then autoattaches matching subscriptions to the system and lists all selected subscriptions.
Attempting to auto-subscribe to appropriate subscriptions ... Installed Product Current Status: ProductName: Red Hat Enterprise Linux Desktop Status: Subscribed Successfully subscribed.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.