Show Table of Contents
5.4. Setting Preferences for Autoattaching Subscriptions
When the subscription process automatically updates and attaches subscriptions (as new products are installed or older subscriptions expire), the subscription service selects the best-fitting subscriptions based on the attributes of the system. Attributes include hardware characteristics — such as socket count and architecture — and operating system and product characteristics.
There are times when there are multiple available options for a particular attribute. In that case, administrators can define a preference for that attribute to help determine what subscription the autoattach process selects. For example, each subscription has a service-level preference defined in it. There can be multiple available subscriptions with different service levels. Setting the service level preference means that subscriptions are auto-selected with a preference for ones that match the desired service level.
5.4.1. Setting a Preferred Service Level
Part of a subscription is a defined service level for that product on a given system. Red Hat service levels are defined in the contract; a summary of production support levels is available at https://access.redhat.com/support/offerings/production/sla.html.
There are three basic support levels:
- Premium
- Standard
- None (self-supported)
An account can have multiple levels of support available, even for the same product, and, obviously, not every system within an IT environment demands the same response times and support as other systems. For example, a production system usually has a premium support level since it is a business critical system, while a development system may have standard support or be self-supported.
Note
By default, the highest available level of support is selected for the subscription and system.
When a system is configured, it can be assigned a preferred service level. When subscriptions are autoattached to the system and the preferred service level is available, then the subscription matching that preference is used. (Service-level preferences are not evaluated or enforced for manually selecting and attaching subscriptions.)
Note
Service-level preferences must first be set locally on the client when it is registered, by autoattaching, or when editing the configuration later. For example:
[root#server ~]# subscription-manager attach --auto --servicelevel Premium
After the service-level preference is set for the system, then that preference can be viewed and edited through the Portal.
The service-level preference is set in the system details page.
Figure 14. Service-Level Preference
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.