This article explains how to configure Red Hat processor-based licenses in FlexNet Manager Suite (FNMS) to ensure accurate license consumption. Red Hat processor licenses can be modeled using one of three license types, depending on the specific licensing rights granted by the purchased subscription:

1. Microsoft Server Processor

   • For stackable licenses that can be consumed by either physical processor sockets or virtual machines.

2. Device (Processor-Limited)

   • For legacy processor-limited licenses that are restricted to servers with a specific socket count.

3. Processor Points

   • For Red Hat Virtual Datacenter licenses that provide unlimited VM entitlements after licensing host sockets.

Selecting the appropriate license type is critical to achieving accurate compliance calculations.

Red Hat has historically offered processor-based licensing models with different entitlement rules. Depending on the SKU and subscription terms, licenses may:

• Cover physical server sockets.
• Cover a specified number of virtual machines.
• Allow unlimited virtual machines once host processor requirements are met.
• Restrict deployment to servers with a specific socket count.

FlexNet Manager Suite supports these scenarios through different license metrics and configuration options.

Scenario 1: Red Hat Enterprise Linux Server License (Processor Not Limited)

Overview

This licensing model allows consumption based on:

• Physical deployment: One license covers two processor sockets.
• Virtual deployment: One license covers two virtual machines on a host.

You can stack additional licenses to cover more processors or virtual machines.

Example SKU

RH00004S

• Red Hat Enterprise Linux Server – Standard Subscription
• 2 sockets
• 1 physical server OR 2 virtual machines
• Stackable

Recommended License Type

Microsoft Server Processor

This is the only license type in FNMS capable of calculating consumption based on either:

• Processor sockets, or
• Number of virtual machines

depending on deployment method.

Configuration Steps

Step 1: Configure Processor Limits

On the license configuration:

• Set consumption to 1 license per 2 processors.
• Set minimum processor requirement to 1.

This configuration ensures:

Step 2: Configure VM Rights

Navigate to:

Use Rights & Rules → Rights on Virtual Machines and Hosts

Enable:

✅ One license covers multiple VMs per Host

This allows:

Unlimited VM Variant

If the license grants unlimited VMs after host licensing:

Enable:

✅ Always use full capacity license calculations

This ensures unlimited guest VM entitlements are recognized correctly.

Scenario 2: Red Hat Enterprise Linux Server License (Processor Limited)

Overview

Some older Red Hat subscriptions were sold with processor restrictions.

Under this model:

• A license purchased for a 2-socket server can only be deployed on a 2-socket server.
• Licenses cannot be stacked to cover larger servers.
• A different license SKU must be purchased for servers with higher socket counts.

Example

A 2-socket license cannot be combined with another 2-socket license to cover a 4-socket server.

Recommended License Type

Device (Processor-Limited)

This license type enforces maximum processor limits and prevents consumption on devices exceeding the allowed socket count.

Configuration Steps

Step 1: Set Processor Limit

Navigate to the Identification tab.

Set:

Processor Limit = 2

Result:

• Devices with 2 processors are licensed.
• Devices with more than 2 processors remain unlicensed.

Example

Step 2: Configure VM Rights

Navigate to:

Use Rights & Rules → Rights on Virtual Machines and Hosts

Enable:

✅ One license covers multiple VMs per Host

This allows the license to cover two VMs for each licensed two-socket entitlement.

Unlimited VM Variant

For processor-limited licenses that permit unlimited VMs:

Enable:

✅ Always use full capacity license calculations

This allows unlimited VM consumption once the host is licensed.

Scenario 3: Red Hat Enterprise Linux for Virtual Datacenters

Overview

Red Hat Virtual Datacenter licensing is designed for fully virtualized environments.

Consumption is based on:

• Two physical processor sockets per license.

Once host processors are licensed:

• Unlimited virtual machines may run on the licensed host.

These licenses:

✅ Can be stacked

✅ Allow unlimited guests

❌ Are not intended for licensing physical-node installations

Example SKU

RH00002S

• Red Hat Enterprise Linux for Virtual Datacenters
• Standard Subscription
• 2 sockets
• Unlimited virtual machines
• No physical node entitlement

Important Limitation

FlexNet Manager Suite currently does not generate an alert when this license is installed directly on a physical machine rather than in a virtualized environment.

Administrators should manually review deployment locations when using this license model.

Recommended License Type

Processor Points

This license metric provides the most accurate modeling for unlimited guest virtualization rights based on licensed host sockets.

Configuration Steps

Step 1: Configure Processor Points

Set:

Processor Points = 0.5

This results in:

Step 2: Configure Full Capacity Rights

Navigate to:

Use Rights & Rules → Rights on Virtual Machines and Hosts

Enable:

✅ Always use full capacity license calculations

This allows:

• Unlimited VMs on licensed hosts.
• Consumption based only on host processor capacity.

When Not to Use Processor Points

Do not use Processor Points if the subscription grants a limited number of VMs (for example, 2 VMs per license).

In these scenarios, use:

✅ Microsoft Server Processor

because Processor Points cannot correctly calculate VM-based consumption limits.

License Type Selection Matrix