Guide to Identifying Non-Production Servers for IBM Licensing

Learn how to identify Non-Production Servers for IBM Licensing to cut costs, meet compliance requirements, and avoid audit risks in ILMT and BigFix.

Many clients ask us how to reduce their IBM licensing costs. One of the easiest wins is correctly identifying non-production servers and assigning the appropriate lower-cost licenses.

It’s a common blind spot — especially with products licensed by the number of cores on a server (e.g. PVU, RVU, VPC).

Non-Production Servers for IBM Licensing

Having worked on hundreds of IBM licensing projects, I’ve seen this oversight cost clients millions — and it’s almost always avoidable. The good news? It’s usually easy to fix, and in most cases, no technical changes are needed.

If you’re using ILMT and reporting sub-capacity usage, this guide will help you prepare a list of non-production servers. That list can unlock savings of hundreds of thousands (sometimes even millions) in IBM license costs.

Why It Matters

IBM’s Passport Advantage terms allow for reduced or even zero licensing for some non-production scenarios — but only if you’ve done it correctly.

To be compliant, you need to ensure:

Get it right and you can significantly reduce license requirements and costs. Get it wrong, and it will come back to bite you in a future audit.

What Counts as Non-Production?

Definitions vary slightly by product, but broadly, IBM accepts the following server roles as non-production:

*Note: DR servers used actively (e.g., for testing) may be deemed production. See our Guide to IBM Licensing for Hot, Warm, and Cold Standby Machines for details.

How to Find Non-Production Servers

If you’re working with a long list of servers, here’s how we usually approach it. Each non-production server you find and downgrade could save you thousands — it’s worth the effort.

Start with a master server list

Begin with a complete inventory from your CMDB or similar system. Compare this to ILMT’s list and fix any discrepancies.

Filter for IBM product deployments

Refine the list to only servers running IBM software. ILMT helps here, but check for servers with IBM deployments not covered by ILMT.

Use server naming conventions

Most organizations use naming patterns (e.g. “P” for prod, “T” for test). Confirm the scheme with DevOps or network admins and filter accordingly—Cross-check with CMDB status.

Filter by data center or IP range

Non-production servers are often hosted in dedicated data centers or within specific IP ranges. Use this as another filtering method and reconcile it with your existing shortlist.

Ask the DBAs

Database administrators maintain excellent records of which databases and servers are linked. They know which are backups, hot or cold standbys, etc. Tap into their knowledge.

Other useful sources

Verify Your Non-Production Server List

Verifying the list (and the reasons behind it) is essential. It justifies the license treatment and prepares you for any questions from IBM or an auditor.

Verify with service owners

Ask the business or service owners to confirm the server status. Let them know cost savings may be possible if a server can be confirmed as non-production.

Verify with system admins and DBAs

Explain what you’re doing and why. With a clear goal — reducing IBM license costs — admins are usually happy to help. They may even flag additional servers.

Verify against IBM’s definitions

Be careful:

Verify with an IBM licensing expert

An expert can review the list and ensure the classifications align with IBM’s rules. They may also identify additional opportunities to reduce license needs further.

Verify cloud and container environments

Non-prod classification becomes trickier with containers and hybrid cloud environments. Make sure to:

I Have a List of Non-Production Servers. Now What?

Update BigFix / ILMT

IBM tools don’t distinguish between prod and non-prod by default. If a product is found, it’s assumed to require a full license. It’s up to you to adjust reports to exclude eligible non-prod servers and reduce costs.

Update the ELP

An Effective License Position (ELP) matches software deployed to entitlements held.

IBM auditors or consultants typically begin by assuming that all deployments require full licenses.

Your list of non-production servers, along with the rationale, enables them to assign the appropriate lower-cost entitlements.

Need help?

If this hasn’t been done before, there’s a reason. You may not have the time or tools to tackle it alone.

At LicenseHawk, we can:

FAQs

Do non-production servers need licenses at all?

Yes — but not always full-price licenses. Some roles (like cold standby) may not require a license at all, depending on the product and IBM policy.

Can I rely solely on ILMT to identify non-production servers?

No. ILMT scans for deployments but doesn’t distinguish usage types. You must manually configure and justify non-production designations.

What happens if I misclassify a server as non-production?

In an audit, IBM may reclassify it and retroactively charge for full production use — often with backdated costs and penalties.

How often should I review my non-production server list?

At least quarterly. Frequent changes in infrastructure, especially in cloud or container environments, mean roles can shift without notice.

Is there a tool to automate this process?

Some organizations use scripts or CMDB integrations to help tag servers. But expert review is still needed to ensure compliance with IBM’s definitions

Further Reading

About author
Avatar photo
Piaras MacDonnell
IBM License Expert
Piaras is an internationally recognized expert in IBM licensing. He has delivered over 100 licensing projects, including audit defenses, enterprise license agreement renewals, compliance health checks, and license optimization, resulting in millions of dollars and euros in savings for his clients.

Read Next

Red Hat audit triggers blog cover from LicenseHawk, a cream envelope with a postage stamp of a red fedora hat

Red Hat Audit Triggers and What Causes a Review 

Red Hat may call it a Request to Review, but the mechanics are the same as an audit, and the commercial impact can be just as large. This guide walks through the most common triggers, from RHSM mismatches and RHEL growth to OpenShift sprawl and renewal timing, so IT and procurement know what's behind the request before they respond.

IBM audit cost featured graphic showing a mountain avalanche, titled What an IBM Audit Costs the Business

What an IBM Audit Costs the Business 

IBM audit cost rarely stops at the licenses finance expects. Back support, reinstatement, full-capacity recalculation when ILMT data is missing, and a weaker renewal position add to the total, and most of it falls to procurement, finance, and IT leadership rather than the analyst who got the letter. Knowing where the money goes before a review starts keeps a surprise from becoming a settlement.

Mistake 6: Not Upgrading the Operating Systems or Underlying Infrastructure

Top Ten IBM Licensing Mistakes #6 Not Upgrading the Operating Systems or Underlying Infrastructure