15.2. Registering and Unregistering a System
15.2.1. Registering from the GUI
- Launch Subscription Manager. For example:
[root@server ~]# subscription-manager-gui
- If the system is not already registered, then there will be a My Installed Products tab.button at the top of the window in the top right corner of the
- To identify which subscription server to use for registration, enter the hostname of the service. The default service is Customer Portal Subscription Management, with the hostname subscription.rhn.redhat.com. To use a different subscription service, such as Subscription Asset Manager, enter the hostname of the local server.There are seveal different subscription services which use and recognize certificate-based subscriptions, and a system can be registered with any of them in firstboot:
- Customer Portal Subscription Management, hosted services from Red Hat (the default)
- Subscription Asset Manager, an on-premise subscription server which proxies content delivery back to the Customer Portal's services
- CloudForms System Engine, an on-premise service which handles both subscription services and content delivery
- Enter the user credentials for the given subscription service to log in.The user credentials to use depend on the subscription service. When registering with the Customer Portal, use the Red Hat Network credentials for the administrator or company account.However, for Subscription Asset Manager or CloudForms System engine, the user account to use is created within the on-premise service and probably is not the same as the Customer Portal user account.
- Optionally, select the Manually assign subscriptions after registration checkbox.By default, the registration process automatically attaches the best-matched subscription to the system. This can be turned off so that the subscriptions can be selected manually, as in Section 15.3, “Attaching and Removing Subscriptions”.
- When registration begins, Subscription Manager scans for organizations and environments (sub-domains within the organization) to which to register the system.IT environments that use Customer Portal Subscription Management have only a single organization, so no further configuration is necessary. IT infrastructures that use a local subscription service like Subscription Asset Manager might have multiple organizations configured, and those organizations may have multiple environments configured within them.If multiple organizations are detected, Subscription Manager prompts to select the one to join.
- With the default setting, subscriptions are automatically selected and attached to the system. Review and confirm the subscriptions to attach to the system.
- If prompted, select the service level to use for the discovered subscriptions.
- Subscription Manager lists the selected subscription. This subscription selection must be confirmed by clicking thebutton for the wizard to complete.
15.2.2. Registering from the Command Line
registercommand with the user account information required to authenticate to Customer Portal Subscription Management. When the system is successfully authenticated, it echoes back the newly-assigned system inventory ID and the user account name which registered it.
registeroptions are listed in Table 15.2, “register Options”.
Example 15.1. Registering a System to the Customer Portal
[root@server1 ~]# subscription-manager register --username admin-example --password secret The system has been registered with id: 7d133d55-876f-4f47-83eb-0ee931cb0a97
Example 15.2. Automatically Subscribing While Registering
registercommand has an option,
--autosubscribe, which allows the system to be registered to the subscription service and immediately attaches the subscription which best matches the system's architecture, in a single step.
[root@server1 ~]# subscription-manager register --username admin-example --password secret
Example 15.3. Registering a System with Subscription Asset Manager
--orgoption in addition to the username and password. The given user must also have the access permissions to add systems to that organization.
- The username and password for the user account withint the subscription service itself
--serverurlto give the hostname of the subscription service
--baseurlto give the hostname of the content delivery service (for CloudForms System Engine only)
--orgto give the name of the organization under which to register the system
--environmentto give the name of an environment (group) within the organization to which to add the system; this is optional, since a default environment is set for any organizationA system can only be added to an environment during registration.
[root@server1 ~]# subscription-manager register --username=admin-example --password=secret
--org="IT Department" --environment="dev" --serverurl=sam-server.example.comThe system has been registered with id: 7d133d55-876f-4f47-83eb-0ee931cb0a97
registercommand returns a Remote Server error.
Table 15.2. register Options
|--username=name||Gives the content server user account name.||Required|
|--password=password||Gives the password for the user account.||Required|
|--serverurl=hostname||Gives the hostname of the subscription service to use. The default is for Customer Portal Subcription Management, subscription.rhn.redhat.com. If this option is not used, the system is registered with Customer Portal Subscription Management.||Required for Subscription Asset Manager or CloudForms System Engine|
|--baseurl=URL||Gives the hostname of the content delivery server to use to receive updates. Both Customer Portal Subscription Management and Subscription Asset Manager use Red Hat's hosted content delivery services, with the URL https://cdn.redhat.com. Since CloudForms System Engine hosts its own content, the URL must be used for systems registered with System Engine.||Required for CloudForms System Engine|
|--org=name||Gives the organization to which to join the system.||Required, except for hosted environments|
|--environment=name||Registers the system to an environment within an organization.||Optional|
|--name=machine_name||Sets the name of the system to register. This defaults to be the same as the hostname.||Optional|
|--autosubscribe||Automatically ataches the best-matched compatible subscription. This is good for automated setup operations, since the system can be configured in a single step.||Optional|
|--activationkey=key||Attaches existing subscriptions as part of the registration process. The subscriptions are pre-assigned by a vendor or by a systems administrator using Subscription Asset Manager.||Optional|
|--servicelevel=None|Standard|Premium|| Sets the service level to use for subscriptions on that machine. This is only used with the ||Optional|
|--release=NUMBER|| Sets the operating system minor release to use for subscriptions for the system. Products and updates are limited to that specific minor release version. This is used only used with the ||Optional|
|--force||Registers the system even if it is already registered. Normally, any register operations will fail if the machine is already registered.||Optional|
unregistercommand. This removes the system's entry from the subscription service, removes any subscriptions, and, locally, deletes its identity and subscription certificates.
Example 15.4. Unregistering a System
[root@server1 ~]# subscription-manager unregister
- Open the Subscription Manager UI.
[root@server ~]# subscription-manager-gui
- Open the System menu, and select the item.
- Confirm that the system should be unregistered.