Updating rhel without subscription ang dating daan tanging awit
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.
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.
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.
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.
See How to access Red Hat Subscription Manager (RHSM) through a firewall or proxy The basis of everything is a , or number of servers, that the product can be installed on.
Subscriptions are managed though the Certificate-Based Red Hat Network service, which ties into the Subscription and Content Delivery Network (CDN). Each product group within the repository may contain the primary software packages and then any required dependencies or associated packages.