install-num-migrate-to-rhsm(8)

NAME
install-num-migrate-to-rhsm - Checks the installation number for a system and installs the required product certificates. This is used for migrating an offline system to Customer Portal Subscription Management.

SYNOPSIS
install-num-migrate-to-rhsm [--dryrun|--instnum=NUMBER|--help]

DESCRIPTION
install-num-migrate-to-rhsm migrates a system using legacy Red Hat Enterprise Linux installation numbers to the X.509 certificates used by Customer Portal Subscription Management.

While the install-num-migrate-to-rhsm script performs the migration operation, the data used to map the channels to the corresponding product certificates is defined in the subscription-manager-migration-data package. The subscription-manager-migration-data package must be installed before the install-num-migrate-to-rhsm script can be run successfully.

BACKGROUND
Access to support and updates for products is determined through subscriptions. Subscriptions are assigned or attached to a system, which means that the system has the right to install and update a product with full support. Even disconnected or offline systems still need a way to track the products installed on them and the subscriptions used by them. In the older Red Hat Network Classic model of subscription management, a system was associated with a channel. In Customer Portal Subscription Management, installed products and subscriptions are identified through X.509 certificates. Either way, a channel or a certificate provides a means of recognizing and tracking the products and subscriptions for a system, even an offline system.

When Red Hat software is purchased through a vendor, the purchased software is identified in a installation number or subscription number. Installation numbers are described more in the Knowledgebase article: <https://access.redhat.com/kb/docs/DOC-15408>

This number is located in the /etc/sysconfig/rhn/install-num file. The installation number is in essence a code which contains all of the information about the products and versions purchased for the system. For example, this installation number shows that it is valid for RHEL Client and RHEL Workstation channels.
[root@server ~]# python /usr/lib/python2.4/site-packages/instnum.py da3122afdb7edd23
Product: RHEL Client
Type: Installer Only
Options: Eval FullProd Workstation
Allowed CPU Sockets: Unlimited
Allowed Virtual Instances: Unlimited
Package Repositories: Client Workstation
key: 14299426 "da3122"
checksum: 175 "af"
options: 4416 "Eval FullProd Workstation"
socklimit: -1 "Unlimited"
virtlimit: -1 "Unlimited"
type: 2 "Installer Only"
product: 1 "client"
{"Workstation": "Workstation", "Base": "Client"}

For an offline system, one which is not connect to either Red Hat Network Classic (Hosted) or a Satellite system, the installation number can be used to move the subscription configuration from the older channel-based subscription model to certificate-based Customer Portal Subscription Management, managed by Subscription Manager.

install-num-migrate-to-rhsm identifies the channel that a disconnected system is subscribed to and then installs the appropriate product certificates.

OPTIONS

-h, --help
    Prints the specific help information for the given command.

-d, --dryrun
    Performs a dry run of the script. This indicates what product certificates will be installed into the /usr/share/rhsm/product directory, but does not actually install the product certificates in the directory.

-i NUMBER, --instnum=NUMBER
    Migrates the channels and product certificates based on the manually-entered installation number rather than the number in /etc/sysconfig/rhn/install-num. This is an advanced option; most migrations will use the standard installation number in the system configuration.

USAGE
To pull in the product certificates and migrate the system, simply run the command:
[root@server ~]# install-num-migrate-to-rhsm

The script installs the product certificates that correspond to the available channels from the installation number. This script does not register the system or attach new subscriptions to the system. For the procedure to register an offline system with Customer Portal Subscription Management and attach subscriptions, see the Customer Portal documentation: <https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Customer_Portal/1/html/Red_Hat_Network_Certificate-based_Subscription_Management/managing-consumers.html#web-consumer-register>

After migration, the system facts maintained by Subscription Manager display what script was used for migration.
[root@server ~]# subscription-manager facts --list | grep migr
migration.migrated_from: install_number

Because the install-num-migrate-to-rhsm command does not register the system with Customer Portal Subscription Management, the migration facts do not include a new system ID.

FILES

/etc/sysconfig/rhn/install-num
    The 16-character activation key issued by a vendor which contains all of the subscription and product information for the system. This is used during the installation process.

/etc/sysconfig/rhn/systemid
    The digital server ID for this machine if the system has been registered with Red Hat Network Classic. This file does not exist otherwise.

/etc/sysconfig/rhn/up2date
    The common configuration file used by RHN client programs.

/var/log/rhsm/rhsm.log
    The Subscription Manager log file. This contains any errors registering the system to Customer Portal Subscription Management or with attaching the system to subscriptions.

/etc/rhsm/facts/migration.facts
    The file which contains the migration information. This is displayed as one of the system facts by Subscription Manager.

subscription-manager-migration-data.rpm
    The package which contains the mappings for the migration script to migrate channels to the appropriate product certificates.

SEE ALSO
install-num-migrate-to-rhsm(8), subscription-manager(8).

AUTHORS

Alex Wood <awood@redhat.com>

BUGS

Report bugs to <http://bugzilla.redhat.com>.

COPYRIGHT

Copyright © 2011 Red Hat, Inc.

This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.