Migrating from RHN Classic
to migrate from older Red Hat Network Classic (hosted) to updated subscription management
- Systems can be upgraded from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7. Both Red Hat Enterprise Linux 6 and 7 systems use the same type of subscription management services, but the available content repositories and product subscriptions are different between the platforms. This means that subscriptions must be managed appropriately as part of upgrading the underlying system.
- Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6 systems can migrate from channel-based subscription services to Red Hat Subscription Management. This is truly migrating subscriptions, since the subscriptions are moved from one type of service to another.
Since Red Hat Enterprise Linux 6 can use Red Hat Subscription Management and Red Hat Enterprise Linux 7 systems must use Red Hat Subscription Management, there is no need to migrate the subscription services: it is the same service. However, the system migration and installed product migrations may not happen at the same time, which means that the subscriptions required to cover the system at Red Hat Enterprise Linux 6 may be different than the ones required after it is upgraded. This requires administering the subscriptions for the system, by updating the registration, configuring repositories, and re-attaching the subscriptions.
Red Hat Subscription Management structure provides detailed, accurate, and clear representations of the relationships between subscriptions, systems, their parent organizations, and overall usage patterns. This is done by identifying the different elements involved in subscription management — the system, the installed products, and the assigned subscriptions — with unique certificates.
1. Managing Subscriptions When Upgrading to RHEL 7
redhat-upgrade-toolupgrades the underlying operating system, but any software or applications installed may not necessarily be upgraded by the script. Many products do not yet have Red Hat Enterprise Linux 7 content repositories available.
- Update the Red Hat Enterprise Linux 6 to install the required upgrade tools, and reboot the system.
- Run the preupgrade check.
- Unregister your system from the previous subscription service. This is done using the unregister command.
[root@server ~]# subscription-manager unregister
- Remove the Red Hat Enterprise Linux 6 product certificate to allow the system to be upgraded. If the product certificate is not removed, then later attempting to register the system creates a conflict, because it is incorrectly interpreted as a Red Hat Enterprise Linux 6 system.
[root@server ~]# rm -rf /etc/pki/product/69.pem
- Use the upgrade script to upgrade the system to Red Hat Enterprise Linux 7. In this example, the version is set to Red Hat Enterprise Linux 7.0 and the installation directory points to a public FTP repository.
[root@server ~]# redhat-upgrade-tool-cli --network 7.0 --instrepo ftp://ftp.redhat.com/pub/redhat/rhel/7.0/x86_64/os
NoteThis only upgrades the base operating system. Any additional products or applications need to be upgraded separately.
- Register your system again with the subscription service. This is done using the register command.
[root@server ~]# subscription-manager register --username firstname.lastname@example.org Password: The system has been registered with id: 7d133d55-876f-4f47-83eb-0ee931cb0a97
- Locate any available Red Hat Enterprise Linux 7 repositories for any required layered products, and configure
yumto use those repositories.
- Optional. Attach any required subscriptions. For example:
[root@server1 ~]# subscription-manager list --available +-------------------------------------------+ Available Subscriptions +-------------------------------------------+ ProductName: RHEL for Physical Servers ProductId: MKT-rhel-server PoolId: ff8080812bc382e3012bc3845ca000cb Quantity: 10 Expires: 2016-09-21 [root@server1 ~]# subscription-manager attach --pool=ff8080812bc382e3012bc3845ca000cb