How to Identify Inactive Systems and Manage Subscriptions in SUSE Customer Center
SUSE Linux Enterprise Server

How to Identify Inactive Systems and Manage Subscriptions in SUSE Customer Center

Publication Date: April 23, 2026

Tracking active versus decommissioned servers is critical for maintaining an accurate inventory and optimizing infrastructure costs. This guide explains how to use the SUSEConnect keep-alive timer to automatically identify inactive systems and manage your overall subscription consumption.

1 What is SUSEConnect keep-alive timer?

SUSEConnect is a tool to register SLE-based operating systems with SCC or RMT. Registered systems receive updates to installed packages, for example, to increase security of the operating system. With SUSEConnect, you can additionally register extensions and modules that extend the base system functionality.

Tip
Tip

This document does not cover general usage of SUSEConnect. To find more basic information about how to register your system, modules and extensions with SUSEConnect, refer to https://documentation.suse.com/sles/html/SLES-all/cha-register-sle.html.

To improve visibility into subscription consumption, SUSEConnect now features a daily ping. This ping automatically updates system information in the SUSE Customer Center or RMT, helping you to identify and filter out decommissioned or inactive systems regardless of where they are running or how they are managed; physical or virtual, on-premises or in the cloud, connected to SCC or RMT, or managed by SUSE Multi-Linux Manager. As a result, you can maintain an accurate inventory of active systems and optimize your subscription costs.

2 Requirements

To use the extended SUSEConnect functionality, you need to:

  • Run a supported and registered SLE-based host with all update patches applied.

  • Verify that the host system includes the SUSEConnect command version 0.3.33 or higher.

3 How enhanced system visibility works

We extended SUSEConnect with the new option --keepalive. The command SUSEConnect --keepalive updates the last time that a host contacted SCC or RMT and updates the host's hardware information.

The SUSEConnect package ships with two systemd units:

suseconnect-keepalive.service

A service which runs the command SUSEConnect --keepalive on demand.

suseconnect-keepalive.timer

A timer which runs the service suseconnect-keepalive.service once a day at random time to prevent SCC congestion.

These units are responsible for keeping the system information up to date with the SCC or RMT, and for providing accurate data about subscription usage.

Note
Note: The timer is enabled automatically

When the SUSEConnect package is installed or updated, and its version is equal to or greater than the one described above, the keep-alive timer is enabled automatically.

3.1 How do I disable the SUSEConnect keep-alive timer?

If you prefer to not have the SUSEConnect keep-alive timer running on your system, you can disable it with systemctl:

> sudo systemctl disable --now suse-connect-keepalive.timer

Once the timer is disabled, subsequent updates to the SUSEConnect package do not re-enable it.

Tip
Tip: Re-enabling the keep-alive timer

If you decide to re-enable the disabled keep-alive timer, run the following command:

> sudo systemctl enable --now suse-connect-keepalive.timer

4 Identifying inactive systems

When SUSEConnect reports details about active hosts daily, SCC or RMT collect this information and let you filter out registered inactive hosts. If your hosts are registered against RMT or SUSE Multi-Linux Manager, these registration servers forward the received information to SCC.

4.1 How to filter and deregister inactive systems in SCC?

In the SCC Web user interface, you can limit the list of systems to see only inactive hosts.

  1. Log in to SCC at https://scc.suse.com and select your organization in the left pane.

  2. Select Systems from the top menu to list all registered hosts by default.

  3. Select Inactive from the upper-left drop-down list.

    A screenshot showing a filter for inactive hosts
    Figure 1: Drop-down list with a filter for inactive hosts
  4. If you have sufficient privileges and your inactive host is registered directly with SCC, you can deregister it by clicking the three dots on its right and selecting De-register.

4.2 Identifying inactive systems with RMT

By using the rmt-cli systems purge command, you can view and remove hosts that have not contacted the RMT server since a given date in the past. For more details, refer to https://documentation.suse.com/sles/15-SP7/html/SLES-all/cha-rmt-tools.html#sec-rmt-tools-rmt-cli-systems

5 What hardware and system data does SCC collect?

When a system is registered directly via SCC, or its registration information is forwarded by RMT or SUSE Multi-Linux Manager, SCC collects the following information:

Table 1: System attributes collected by SCC
System AttributeTypeExample value
Host Namestringvirtual.domain.net
CPUsint1
Socketsint2
Total Memoryint4096 (in MiB)
Architecturestringx86_64
UUIDuuid6A5072A0-311B-430E-8EDE-A8770788B92D
HypervisorstringKVM or VMware etc.
Container runtimestringDocker
unamestringLinux lair 6.9.7-1-default #1 SMP PREEMPT_DYNAMIC Fri Jun 28 05:50:47 UTC 2024 (a5efffa) x86_64 x86_64 x86_64 GNU/Linux
VendorstringHardware manufacturer for the system. For virtual machines this is the hypervisor. A sample of the possible values would be Dell Inc., IBM, HP, QEMU, ...
Architecture specificsmapDepends on the architecture. It includes parameters such as device-tree information or virtualization type on PowerPC or System Z.
SAPlist

system_id (string) and instance_types (list of strings) for each SAP installation.

"sap": [
    {
      "system_id": "DEV",
      "instance_types": [
        "ASCS",
        "D"
      ]
    }
]
Cloud ProviderstringAmazon, Google, or Azure
Last Seen Datedate2021-05-05 (the last time that the system contacted SCC or RMT)
Productslist

Base product and activated extensions and modules, for example:

{
  "id": 2511,
  "identifier": "sle-module-live-patching",
  "version": "15.2",
  "arch": "x86_64"
}
SubscriptionslistThe subscription registration code used to activate each product
pci_dataList

PCI Device information

{
  "identifier":"37191ca7bc6a[...]e5e5e9533109e06fc",
  "data":[
    "00:00.0 Host bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMI2 (rev 02)",
    "00:01.0 PCI bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 1 (rev 02)",
    ...
  ]
}
mod_listList

Loaded kernel modules

{
  "identifier":"5eff37558df4[...]3f01244f6ee80fc73",
  "data":[
    "aesni_intel",
    "af_packet",
    "button",
    ...
  ]
}
Tip
Tip

SUSE Multi-Linux Manager sends additional data about the used hypervisor and virtualized systems. Find more details in https://documentation.suse.com/subscription/hypervisor-collector/html/SLE-scc-hypervisor-collector/index.html#scc-hypervisor-collector-data.

6 Why use the keep-alive timer for subscription management?

The new functionality of SUSEConnect brings the following benefits to the customer:

  • Ability to identify all types of deployments of systems, no matter if they are derived from a custom image or are clones of an already registered virtual machine.

  • By contacting SCC or RMT regularly, you can obtain the number of actually running registered systems. This provides a better insight into the consumption of SUSE subscriptions.

  • Updates to registration tools provide a clearer picture of your workloads. You can filter out the systems that are no longer running or decommissioned.

  • By collecting regular registration and hardware information, we can continue to improve our products to reflect your needs and let you manage system subscriptions more easily.