|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||Red Hat Enterprise Linux Administration||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 RHN registration on proxy protected network||RHEL6 RHN registration on proxy protected network||Oracle Linux Registration||RHEL pricing||How to change IP address in RHEL||Humor||Etc|
Red Hat Enterprise Linux and other Red Hat products are sold through annual subscriptions called licenses. There are multiple types of licenses depending on the level of support you get, as well as number of socket of your server. Also virtual servers have additional issues.
Licensing system in RHEL is a very complex beast, that requires study. Many hours of sysadmin time are wasted on mastering its complexities, while in reality this overhead that allows Red Hat to charge money. So the fact that they are supporting it well tell us about the level of deterioration of the company. Red Hat support of this subsystem is usually dismal, unless you are lucky and get knowledgeable guy (I once did). In most case they search database and quite something from it, without even understanding what problem you are experiencing. Sometimes this quote helps, but often it is completely detached from reality.
All-in-all Red Hat successful created almost un-penetrable mess of obsolete and semi obsolete notes, poorly written and incomplete documentation, dismal diagnostic and poor troubleshooting tools. And the level of frustration sometimes sometimes reaches such a level that people just abandon RHEL. I did for several non-critical system. If CentOS or Academic Linux works there is no reason to suffer from Red Hat licensing issues. Also that makes Oracle, surprisingly, more attractive option too :-). Oracle Linux is also cheaper. But usually you are bound by corporate policy here.
"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.
Especially if you are behind restrictive firewall troubleshooting with Red Hat support is a real issue. They simply do not understand this (pretty common) large corporate environment.
Red Hat Subscriptions are built based on the following hierarchy.
Subscription management clarifies the relationships between local systems and available software
resources because it gives a view into where software subscriptions are assigned, apart from
installing the packages. Red Hat Subscription Manager works with
yum to unit content delivery
with subscription management. The Subscription Manager handles only the subscription-system associations.
yum or other package management tools handle the actual content delivery.
Chapter 5, Yum describes how to use
Generally, this is called software license management; with Red Hat's subscription model, this is subscription management.
There are two licensing system used by Red Hat
In its current stage classic licensing system is simply not functional enough for a large enterprise that has complex mix of systems (HPC clusters, servers that require premium support, regular support (most of the servers), self-help system (only patching), etc). You can slightly improve things by using you own patch distribution server (, but the licensing system remain complex and sysadmin unfriendly. Using multiple accounts (one for each type of license) might help but I never tries that. Usually each organization has a single account in Red Hat.
"New" subscription system (RHSM) is slightly better. It allows to assign specific license to specific box and list the current status of licensing. See RHEL System Registration Guide (https://access.redhat.com/articles/737393) for details.
The RHEL System Registration Guide (https://access.redhat.com/articles/737393) outlines all the options available for registering a system via Red Hat Subscription Management (recommended) or Red Hat Network (RHN) Classic (legacy), including How to register and subscribe a system to the Red Hat Customer Portal using Red Hat Subscription-Manager (https://access.redhat.com/solutions/253273), answers to some common questions:
There is also an online tool to assist you in selecting the most appropriate registration technology for your system - Red Hat Labs Registration Assistant (https://access.redhat.com/labs/registrationassistant/). If you would prefer to use this tool, please visit https://access.redhat.com/labs/registrationassistant"
If you are behind proxy With RHNSM you do need to put proper
/etc/rhsm/rhsm.conf . Like RHN, RHNSM does not take values for
proxy from environment as any well written program should. See
How to access Red Hat Subscription Manager (RHSM)
through a firewall or proxy
Subscriptions are managed though the Certificate-Based Red Hat Network service, which ties into the Subscription and Content Delivery Network (CDN).
The repository where the product software is located is organized according to the product. Each product group within the repository may contain the primary software packages and then any required dependencies or associated packages. Altogether, the product and its associated packages are called a content set. (A content set for a product even includes other versions of the product.) When a subscription grants access to a product, it includes access to all of the associated packages in that content set.A single subscription can have multiple products, and each system can have multiple different subscriptions, depending on how many entitlement certificates are loaded on the machine.
Any number of products, for any number of different architectures, can be contained in a single subscription. The subscription options that are visible to a consumer are filtered, by default, according to whether the architecture for the product matches the architecture of the system. This is compatibility. Depending on compatible subscriptions makes sure that subscriptions are allocated efficiently, only to systems which can actually use the products.Some subscriptions define some element count on the consumer, like the number of sockets on the machine, the number of virtual guests on a host, or the number of clients in a domain. Multiple subscriptions can be combined together to cover the counts on the consumer. For example, if there is a four socket server, two subscriptions for "RHEL Server for Two Sockets" can be consumed by the system to cover the socket count. Combining multiple subscriptions to cover the system count is called stacking.
The subscription tools can display even incompatible entitlements. Alternatively, the architecture definition for the system can be overridden by defining custom system facts for the subscription tools to use.It is important to distinguish between subscribing to a product and installing a product. A subscription is essentially a statement of whatever products an organization has purchased. The act of subscribing to a subscription means that a system is allowed to install the product with a valid certificate, but subscribing does not actually perform any installation or updates. In the reverse, a product can also be installed apart from any entitlements for the system; the system just does not have a valid product certificate. Certificate-Based Red Hat Network and the Content Delivery Network harmonize with content delivery and installation by using
yumplug-ins that come with the Subscription Manager tools.
The Subscription Manager tracks and displays what entitlements are available to the local system and what entitlements have been consumed by the local system. The Subscription Manager works can display important for large organizations information such as specific license quantities, how much of it was consumed, or subscription expiration dates.
rootbecause of the nature of the changes to the system. However, Red Hat Subscription Manager connects to the subscription service as a user account for the Customer Service Portal.
The Subscription Manager handles both registration and subscriptions for a system. The Subscription
Manager is part of the
firstboot process for configuring content and updates, but the system
can be registered at any time iether via the Red Hat Subscription Manager GUI or CLI. New subscriptions,
new products, and updates can be viewed and applied to a system through the Red Hat Subscription Manager
Subscription management helps to clarify and to define the relationships between local server infrastructure and the content delivery systems. Subscription management and content delivery are tightly associated. Entitlements (assigned subscriptions) identify what a system is allowed to install and update. In other words, entitlements define access to content. The content delivery system actually provides the software packages.There are three parties that are involved in subscriptions and content:
The subscription service handles the system registration (verifying that the system is allowed to access the content). It also supplies the system with information on what products are available and handles a central list of entitlements and remaining quantities for the entire organization.The content delivery network is responsible for delivering the content to the system when requested. The content server is configured in the Red Hat Subscription Manager configuration and then tied into the system's
yumservice through the Red Hat Subscription Manager yum plug-in.
Both the entitlement server and the content server used by a system's Red Hat Subscription Manager tools can be customized. The default settings use the public subscription service and Content Delivery Network, but either one can be changed to use organization-specific services.The operating infrastructure can be divided into completely separate organizations, which can be further divided into environments. The organization divisions allow a single parent to be able to partition content services and subscriptions to groups, and these groups are opaque to each other. This structure is very useful for ISPs, colocation facilities, or other service providers which may be customer groups that need to be independent of each other but still under the administrative control of the service provider itself. The multi-tenant structures are described in Section 4.3, "Managing Special Deployment Scenarios".
Google matched content
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: March 12, 2019