|Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
May the source be with you, but remember the KISS principle ;-)
Skepticism and critical thinking is not panacea, but can help to understand the world better
|News||RHEL subscription management||Recommended Books||Recommended Links||Migrating systems from RHN to RHNSM||Registering a server using Red Hat Subscription Manager (RHSM)||Redhat Networking||Unix Administration|
|RHEL4 registration||RHEL5 registration on proxy protected network||RHEL6 registration on proxy protected network||Oracle Linux Registration||Xinetd||How to change IP address in RHEL||Humor||Etc|
"New" subscription system (RHSM) is slightly better then RHN for large organizations. It allows to assign specific license to specific box and list the current status of licensing. But like RHN it requires to use proxy setting in configuration file, it does not take them from the environment. If the company has several proxies and you have mismatch you can be royally screwed. In general you need already to check consistently of your environment with conf file settings. The level of understanding of proxies environment by RHEL tech support is basic of worse, so they are using the database of articles instead of actually troubleshooting based on sosreport data. Moreover each day there might a new person working on your ticket, so there no continuity. RHEL System Registration Guide (https://access.redhat.com/articles/737393) is weak and does not cover more complex cases and typical mishaps.
On RHEL 6 subscription-manager is preinstalled. If you run RHEL 6.2 or below you need to update the package before proceeding. It can be done form ISO.
There are two cases of migration: your subscription expired and you subscription is current. If your subscription expired you have twp options:
subscription-manager-migration subscription-manager-migration-dataRPMs manually and follow standard Red Hat Recommendation
For some reason migration to RHNSM is easier then the registration from scratch. The following steps are
# subscription-manager register # subscription-manager list --available --all
Above command will give you list of available subscriptions and pool ID. You will need to copy the pool id that you want to attach to the system
# subscription-manager attach --pool=
Once done you can check the subscription status by executing below command:
# subscription-manager list --consumedThis command allows you to check if system is registered, attached to it subscriptions and expiration date
# yum clean all
From the yum manual:
The following are the ways which you can invoke yum in clean mode.
yum clean packages
Eliminate any cached packages from the system. Note that packages are not automatically deleted after they are downloaded.
yum clean headers
Eliminate all of the files which yum uses to determine the remote availability of packages. Using this option will force yum to download all the headers the next time it is run.
yum clean all
Runs yum clean packages and yum clean headers as above."
The "yum clean all" command will not only remove cached packages, but also any headers. You need flush out everything in case there are obsolete headers
# yum repolist # (or if you want to see all avalable repositories yum repolist all )
Now you can see to what repositories you are subscribed and if you wish what repositories are available for subscription.
Once this is done, you can un-register the system from RHN Classic. To do this you need to do two things:
[root@localhost ~]# cd /etc/sysconfig/rhn [root@localhost ~]# mv systemid systemid.old
[root@localhost pluginconf.d]# vim rhnplugin.conf
enabled = 0
gpgcheck = 1
Now can also try to install or update one package on the system to see if it works
yum update vim
If this command failed you need to enable repositories
See How to add a new yum repository
Do not try this if your subscription si alreay expred. Those packages have a lot of dependencies that you will never be able to resove without much pain.
yumsearch to make sure that the packages are available. For example:
[root@server ~]# yum search subscription-manager-migration -v Not loading "rhnplugin" plugin, as it is disabled Loading "product-id" plugin Loading "refresh-packagekit" plugin Loading "security" plugin Loading "subscription-manager" plugin Updating certificate-based repositories. ================= N/S Matched: subscription-manager-migration ================== subscription-manager-migration.x86_64 : Migration scripts for moving to : certificate based subscriptions Repo : rhel-6-server-rpms subscription-manager-migration-data.noarch : RHN Classic to RHSM migration data Repo : rhel-6-server-rpmsIf necessary, enable the supplementary repositories which contain the migration RPMs.
[root@server ~]# subscription-manager repos --enable rhel-6-server-optional-rpms
[root@server ~]# yum install subscription
# yum install subscription-manager-migration subscription-manager-migration-data
More information on migrating systems from RHN Classic to Certificate-based RHN can be found in our official Subscription Management Guide.
For the migration process the system should only be subscribed to base channel. If it is subscribed to any child channels, remove the child channels before the migration process.
Check if you are still subscribed to RHN Classic:
[root@localhost ~]# yum check-update Loaded plugins: refresh-packagekit, rhnplugin
2. Install plugins needed for RHSM (not necessary for RHEL 6)
[root@localhost ~]# yum install subscription-manager
3. Change directory to edit plugins.
[root@localhost ~]# cd /etc/yum/pluginconf.d
4. List current plugins
[root@localhost pluginconf.d]# ls refresh-packagekit.conf rhnplugin.conf
5. Edit plugins on system, enable plugins needed for RHSM
[root@localhost pluginconf.d]# vim rhnplugin.conf [main] enabled = 0 gpgcheck = 1
6. Clean yum
[root@localhost pluginconf.d]# yum clean all Loaded plugins: refresh-packagekit, rhnplugin Cleaning up Everything
7. Remove (or rename) the systemid file
[root@localhost ~]# cd /etc/sysconfig/rhn [root@localhost ~]# mv systemid rhnclassic.systemid
8. Register system to RHSM via command-line
[root@localhost pluginconf.d]# subscription-manager register --autosubscribe
For both Red Hat Enterprise Linux 5 and 6, migrating a system's registration and subscriptions from RHN Classic Hosted to Customer Portal Subscription Management (hosted) uses the
Subscription Concepts and Workflows" outlines the importance of clear, detailed, and consistent subscription tracking. It is an increasingly critical part of IT maintenance. The older channel-based subscription management process in RHN Classic was great at providing access, but it was very difficult to get an accurate accounting of how subscriptions were applied, how many subscriptions were being used, where subscriptions were being used, and what any individual system was using.
The migration process involves moving the system's full registration information - including its subscriptions - from RHN Classic to Customer Portal Subscription Management. The system is identified by a unique number. This can either be aThe migration script takes the identifier and then uses it to extract and migrate the system entry.
systemidvalue (Red Hat Enterprise Linux 5 or 6) or an installation number (Red Hat Enterprise Linux 5).
rhn-migrate-classic-to-rhsmperforms the migration based on the system ID, in the
2.2. Installing the Migration ToolsThe migration tools are contained in the subscription-manager-migration package. An additional package, subscription-manager-migration-data, is required to map the RHN Classic channels to Customer Portal Subscription Management product certificates.
- The migration tools and data are usually in the main channels for Red Hat Enterprise Linux 5 or 6, but they may be located in optional or supplementary channels. Do a simple
yumsearch to make sure that the packages are available. For example:[root@server ~]# yum search subscription-manager-migration -v Not loading "rhnplugin" plugin, as it is disabled Loading "product-id" plugin Loading "refresh-packagekit" plugin Loading "security" plugin Loading "subscription-manager" plugin Updating certificate-based repositories. ================= N/S Matched: subscription-manager-migration ================== subscription-manager-migration.x86_64 : Migration scripts for moving to : certificate based subscriptions Repo : rhel-6-server-rpms subscription-manager-migration-data.noarch : RHN Classic to RHSM migration data Repo : rhel-6-server-rpmsIf necessary, enable the supplementary repositories which contain the migration RPMs.[root@server ~]# subscription-manager repos --enable rhel-6-server-optional-rpms
- Install the migration tool packages.[root@server ~]# yum install subscription
Google matched content
Migrating from RHN Classic
The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D
Copyright © 1996-2018 by Dr. Nikolai Bezroukov. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) in the author free time and without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info|
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Last modified: October, 18, 2019