Show Table of Contents
Chapter 8. Viewing System-Level Subscription Information
The ultimate goal of subscription management is to allow administrators to identify the relationship between their systems and the subscriptions used by those systems. This can be done from two different perspectives: from the perspective of the local system looking externally to potential subscriptions and from the perspective of the organization (top-level account), looking down at the total infrastructure of systems and all subscriptions.
Subscription Asset Manager has several different ways of conveying subscription and system information. This includes information about insufficient or expiring subscriptions, which is invaluable to administrators for maintaining current subscriptions.
8.1. Viewing the High-Level Information in the Dashboard
The Subscription Asset Manager dashboard shows a count of all systems registered with that organization and their overall subscription status.
Figure 8.1. The Subscription Asset Manager Dashboard
Subscription status refers to the status of all subscriptions for all products which are installed on a system. For example, if a system has Red Hat Enterprise Linux, OpenShift, and Directory Server all installed, then that system must have subscriptions for Red Hat Enterprise Linux, OpenShift, and Directory Server attached to it so that it is current.
There are three categories of subscription status:
- Current subscriptions mean that a system has a subscription for every install product, in the appropriate quantity.
- Invalid subscriptions mean that a system has installed products but at least one of those products has no corresponding subscription for it.
- Insufficient subscriptions is a slightly more complex state. It means that at least one installed product has some subscriptions for it, but not enough. Each subscription states some attribute that applies to it. For example, an operating system subscription may specify a certain number of cores or a certain amount of RAM. If a system has four cores and the subscription specifies that it covers two sockets, then the system requires two subscriptions. If only one subscription is attached, then the system is in an insufficient state.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.