Red hat subscription manager tools

From the Subscriptions tab on your system profile, click Download Certificates to download the entitlement certificate s for attached subscriptions. The downloaded file will be in zip format. Virtually all of the additional configuration options — both system-level configuration like setting a service level and infrastructure-level configuration like using a different subscription or content service — are not applicable to a disconnected system as long as it is disconnected.

Most parameters, such as autoattaching, configure operations that occur automatically over the network. One thing to plan is what configuration should be used if the system is ever brought online. For example, if the rest of the infrastructure is using Satellite 6 rather than Customer Portal Subscription Management hosted services, the disconnected system should probably also be registered to the Satellite 6 services rather than Red Hat Subscription Management.

For security rules, that system may never be brought online, so that configuration may always be irrelevant. Backup systems could come online at any time, which would make proper configuration important. Red Hat Subscription Management 1. Customer Content Services.

Abstract Red Hat's Subscription Management tools and applications provide different ways to view system-level and organization-level notifications and statuses. There are multiple workflows to cater to an individual customer environment, and understanding what each does is the best way to learn to select which workflow to use. Understanding your workflow for subscribing with Red Hat products. A system is registered to the inventory for the subscription service.

This means that the subscription service can manage the server and attach subscriptions to it A subscription is attached to a system The system downloads software packages and updates from the content delivery network for as long as the subscription is active. An identity certificate for the system. This is used by the system to authenticate to the subscription service periodically to check for updates.

This is created when the system is registered. A product certificate for each product installed on the system. Each product in Red Hat has an identifying certificate but this is not unique to the system. This is installed on the system as part of installing the product. A subscription certificate for each subscription attached to the system. This includes information about the subscription from the inventory.

This is installed on the system when a subscription is attached to the system. Introduction to Red Hat Subscription Management. Tools and applications available for Red Hat Subscription Management. Red Hat Subscription Manager client tools to manage local systems Red Hat Subscription Management in the Customer Portal to manage systems and subscription application organizations for a single account globally through the Customer Portal Red Hat Satellite as an on-premise solution for systems that may not regularly check in.

Launching Red Hat Subscription Manager. Table 1. Understanding autoattaching subscriptions on the Customer Portal. Environments for autoattaching subscriptions on the Customer Portal.

Fewer than 20 Linux servers Limited IT resources for system maintenance No business need to create custom subscription or content utilities. Automatically attaching subscriptions on the Customer portal. Options and details for autoattaching subscriptions on the Customer portal. Attaching additional subscriptions, which is especially useful if the system is autoattached during firstboot, when subscriptions are only attached for the operating system. Overriding system facts, which is used by the autoattach and healing processes to determine what the system architecture and hardware is for finding compatible subscriptions.

Setting a service level preference this can also be done during registration, so it is used as one of the priorities when selecting subscriptions. Setting a release preference, so that the system only updates for software targeted to that release version and ignores any upgrades to a later operating system version.

Enabling or disabling associated yum repos. Understanding the manual registration and subscription on the Customer Portal. Environments for manually attaching subscriptions on the Customer Portal. Manually attaching subscriptions on the Customer Portal. Procedure Open Subscription Manager on the system you need to register. Select the Available Subscriptions tab. Select the subscriptions to attach to the system.

Options and details for manually attaching subscriptions to the Customer portal. Understanding registration using firstboot. Understanding registering subscriptions using Kickstart. Environments for using Kickstart to attach Subscriptions. Attaching subscriptions using Kickstart. Options and details for attaching subscriptions using kickstart. Set a service level preference using the '--servicelevel' option. To attach subscriptions manually, leave off the '--auto-attach' option and run a second script with the attach command or add the subscriptions later.

To use an on-premise service like Subscription Asset Manager, first run the subscription-manager config command and reset the Red Hat Subscription Manager configuration, and then register the system using the new configuration. To register a system and attach subscriptions using an activation key, first configure Red Hat Subscription Manager to use the appropriate subscription service and then register with the activation key.

Understanding attaching subscriptions for hypervisors and guests. Your local network has the routes and SSL proxy rules it needs to connect. If all of the settings are accurate, you may need to reinstall the root certificate: Download python-rhsm from the Customer Portal. Chapter 5. Configuring options in Red Hat Subscription Manager.

Enabling supplementary and optional repositories. Content repositories are based on the product and on the content delivery network CDN that are defined in the rhsm. A subscription may include access to optional content repositories in addition to the default repositories that are automatically enabled on the system.

These optional repositories must be enabled before the packages in them can be installed even if the system has the appropriate subscriptions for the products in those repositories. The optional and supplementary channels are named rhelserver-optional-rpms and rhelserver-supplementary respectively. The repositories can be enabled using the --enable command:. Likewise, unwanted repositories can be disabled using the repos --disable command.

Disabling the Subscription Manager repository. Maintaining a redhat. It can create static in content management operations if that repository is not the one actually used for subscriptions. This is relevant for disconnected systems or systems using an on-premise content mirror. Using an HTTP proxy. Some network environments may only allow external Internet access or access to content servers by going through an HTTP proxy.

Subscription Manager can be configured to use an HTTP proxy for all of its connections to the subscription service. This is also an advanced configuration option at firstboot. To configure the proxy:. Checking logs in Subscription Manager. Frequency parameter in the rhsm. The rhsm. Each entry has this format:. The response in the log entry can be very complex, spanning multiple lines, or relatively simply, with just a status code. Because each log entry in rhsm.

Retrieving the system UUID. The system UUID is a unique identifier used in the inventory subscription service. This UUID can be used to re-register the system if there is some kind of corruption or for internal tracking. From the command-line, use the identity command to return the current UUID. Chapter 6. Working with yum repos. Red Hat Subscription Manager works with yum. Subscription Manager has its own yum plug-ins: product-id for subscription-related information for products and subscription-manager which is used for the content repositories.

Viewing available repositories. Subscription management application can define a number of different content repositories, based on environments, physical locations, and other factors.

Even when using the Red Hat Content Delivery Network, multiple repositories are available depending on the product. The repos command lists all of the repositories that are available to the configuration environments and organization for a system, and then shows whether those repositories are enabled for the system.

As product subscriptions are attached to systems, the associated content repositories identified in the subscription certificate are made available to the system. The content repositories are based on the product and on the content delivery network, defined in the baseurl parameter of the rhsm.

A subscription may include access to optional content repositories along with the default repositories. These optional repositories must be enabled before the packages in them can be installed even if the system has the appropriate subscriptions for the products in those repositories : List all available repos for the system, including disabled repos.

The repositories can be enabled using the --enable option with the repos command:. The optional and supplementary channels are named rhelserver-optional-rpmsand rhelserver-supplementary, respectively. Disabling the subscription manager repository. When a system is registered using Subscription Manager, the rhsmcertd process creates a special yum repository — redhat.

As the system adds subscriptions, the product channels are added to the redhat. It can create static in content management operations if that repository is not the one actually used for subscriptions, such as for a disconnected system or a system using an on-premise content mirror. This default redhat. Setting firewall access for content delivery.

For systems registered with Customer Portal Subscription Management or a local Subscription Asset Manager instance, all content is delivered from Red Hat-hosted repositories. The URL set by default in the rhsm. However, there is no single server for cdn. The download server is selected based on what is geographically closest to the requesting machine. This results in much faster download times and better availability for content — however, in some firewall configuration, the required IP addresses could be blocked.

If yum downloads are failing, the it may be necessary to open the firewall to allow access to the IP address of the available content delivery servers.

Appendix A. Revision History. Revision History Revision 2. Revision 1. Anni Bond. Added diagram to first chapter. BZ - The Customer Portal hasn't looked or behaved like those screenshots for at least one revision. Andrew Dahms. BZ - Updated a description of the --all option when checking available entitlements. Ella Deon Ballard.

Updating reference to CIDR list. Log in Your Red Hat account gives you access to your member profile and preferences, and the following services based on your customer status: Customer Portal Red Hat Connect for Business Partners.

User management Certification Central. Register now Not registered yet? Here are a few reasons why you should be: Browse Knowledgebase articles, manage support cases and subscriptions, download updates, and more from one place. View users in your organization, and edit their account information, preferences, and permissions.

Manage your Red Hat certifications, view exam history, and download certification-related logos and documents. Edit your profile and preferences Your Red Hat account gives you access to your member profile, preferences, and other services depending on your customer status. Log out.