Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 4. Manage system operations and configuration settings

To ensure that your RHEL systems are maintaining connectivity and reporting accurate data to Red Hat Lightspeed, perform routine maintenance by using both rhc and insights-client. With rhc and insights-client, you can edit global settings, adjust connection settings, and change features after registering systems to Red Hat Lightspeed.

4.1. Use remote host configuration manager
Link kopieren

You can use the rhc client using remote host configuration manager to control the global remote host configuration (rhc) settings for Red Hat Enterprise Linux systems connecting to Red Hat Lightspeed. You can enable or disable the execution of remediations playbooks, which affects the execution of the remediation plan. To access the remote host configuration manager, log in to the Red Hat Hybrid Cloud Console as a user with RHC user privileges. The remote host configuration manager is located at Red Hat Hybrid Cloud Console > Red Hat Lightspeed > Inventory > System Configuration > Remote Host Configuration (RHC).

4.1.1. Edit global rhc manager settings for connected systems
Link kopieren

You can use the remote host configuration manager to edit remote host configuration connection settings to enable and disable permissions to run remediation playbooks on rhc-connected systems.

Prerequisites

  • You must be logged into the Red Hat Hybrid Cloud Console.
  • You must have RHC administrator privileges.

Procedure

Maintain a strong connection between the remote host configuration (rhc) and Red Hat Hybrid Cloud Console, by optionally setting the recommended option for a 10-second reconnect delay. This involves adding the line, mqtt-reconnect-delay = "10s" to the /etc/rhc/config.toml file and restarting the rhcd.service to ensure uninterrupted remote management and monitoring.

Prerequisites

  • You have root-level access to the system or sudo permissions.
  • You have an rhc version that is between 0.2.4 and version 0.3.

Procedure

  1. Open the following file: /etc/rhc/config.toml
  2. Add this option to the file mqtt-reconnect-delay = "10s"
  3. Save your changes.

  4. Type the following command in the terminal: 

    # systemctl restart rhcd.service
    Copy to Clipboard Toggle word wrap

Verification

  • Type the following command in the terminal: 

    # systemctl status rhcd.service
    Copy to Clipboard Toggle word wrap

  • If the command completed successfully, you should see the following statement returned: 

    # `Active: active (running)`
    Copy to Clipboard Toggle word wrap

    The statement also includes a timestamp.

4.2. Manage system connectivity and networking
Link kopieren

To successfully connect your RHEL systems to Red Hat Lightspeed for registration and data transfer, make sure your network configuration and firewall allow necessary outbound traffic. If your network uses a proxy, configure your RHEL systems to use the proxy for outbound connections. Review the required prerequisites and configurations to configure your network correctly and ensure your firewall is open. This helps ensure your RHEL clients can register and send data to Red Hat Lightspeed using the client tools.

Additionally, to use remote management capabilities, verify that connections to required Red Hat systems on standard ports and the MQTT port are open.

4.2.1. The subscription-manager destinations and ports
Link kopieren

For subscription-manager, the system must be able to reach the following destination and TCP ports:

  • subscription.rhn.redhat.com:443 (https)
  • subscription.rhsm.redhat.com:443 (https)
  • cdn.redhat.com:443 (https)
  • *.akamaiedge.net:443 (https)
  • *.akamaitechnologies.com:443 (https)

Additional resources

4.2.2. The insights-client destinations and ports
Link kopieren

For Red Hat Lightspeed to collect data, the system must be able to reach the following destination and TCP ports:

  • api.access.redhat.com:443 (https)
  • cert-api.access.redhat.com:443 (https)

Additional resources

4.2.3. The rhc client daemon communication with MQTT
Link kopieren

For the rhc daemon (rhcd) to communicate with the MQTT message broker, the system must be able to reach reach connect.cloud.redhat.com:443 (https).

  • connect.cloud.redhat.com:443 (https)

4.2.4. Add a proxy for rhc
Link kopieren

When you run rhc on your RHEL systems, the system attempts to establish connections to several Red Hat endpoints. If these are blocked, the registration will fail, so you will need to add a proxy for rhc to connect to Red Hat.

Prerequisites

  • You have root-level access to your system

Procedure

  1. On a command line, run the following commands to add a proxy for rhc to use to connect to Red Hat.

  2. Use the following commands to add a proxy for rhc to use to connect to Red Hat. 

    # mkdir -p /etc/systemd/system/rhcd.service.d
    Copy to Clipboard Toggle word wrap 
    # cat /etc/systemd/system/rhcd.service.d/proxy.conf
    Copy to Clipboard Toggle word wrap 
    [Service]
Environment=HTTPS_PROXY=http://proxy.corp.com:8888
    Copy to Clipboard Toggle word wrap 
    # systemctl daemon-reload
    Copy to Clipboard Toggle word wrap 
    # systemctl restart rhcd
    Copy to Clipboard Toggle word wrap

4.3. Manage system display and status
Link kopieren

To maintain an accurate inventory and ensure reliable management of your Red Hat Enterprise Linux (RHEL) systems, you can manage system identity and connection status. Performing management tasks such as, renaming a host, checking the client version, and unregistering or re-registering systems helps prevent duplicate entries in your inventory, which can lead to confusion, inaccurate reporting, and potential configuration errors.

4.3.1. Change the host display name
Link kopieren

You can change the host display name as it appears in the graphical user interface (GUI) to help streamline identifying your inventory, meet organizational naming conventions, or other reasons. Make this change either when you register the system with Red Hat Lightspeed, or after registration. If you do not assign a display name when you register the system, Red Hat Lightspeed uses the value in /etc/hostname. Changing the display name is optional, so you need to decide if you want to use a display name in addition to the default hostname.

Note

Using the insights-client command to set the display name takes effect immediately, but does not run the client.

Note

If you obfuscate the hostname, the hostname configured in /etc/hostname is obfuscated. Assign a display name so that you can identify a host even when its hostname is obfuscated.

Prerequisites

  • Root-level access to the system.

Procedure

  • Enter the insights-client command with the --display-name option and specify a display name. 

    [root@rhlightspeed]# insights-client --display-name ITC-4
System display name changed from None to ITC-4
    Copy to Clipboard Toggle word wrap

  • To create a display name that contains spaces, use double quotes. 

    [root@rhlightspeed]# insights-client --display-name "ITC-4 B9 4th floor"
System display name changed from None to ITC-4 B9 4th floor
    Copy to Clipboard Toggle word wrap

Additional resources:

4.3.2. Display the client version
Link kopieren

You can display the insights-client version and client core version.

Prerequisites

  • Root-level access to your system.

Procedure

  • Enter the insights-client command with the --version option. 

    [root@rhlightspeed]# insights-client --version
Client: 3.0.6-0
Core: 3.0.121-1
    Copy to Clipboard Toggle word wrap

Additional resources

4.4. Manage schedule and rule updates for the insights-client
Link kopieren

By default, the insights-client runs every 24 hours. The timers in the default schedules are random so that all systems do not run the client at the same time. You can disable, enable, or modify the schedule to control when the system performs data collection, although changes from the default might affect performance. To ensure that host information remains up-to-date extending the timers beyond 24 hours is not recommended.

4.4.1. Disable the insights-client schedule
Link kopieren

You must disable the client schedule before you can change the default insights-client settings and create a new schedule. The procedure you use to disable the insights-client schedule depends on your Red Hat Enterprise Linux and client versions.

Prerequisites

  • Root-level access to your system

  • The insights-client version 3.x and later

    • NOTE: The --no-schedule option is deprecated in Client 3.x and later.

Procedure

  1. Enter the insights-client command with the --version option to verify that you have the required client version installed. 

    [root@rhlightspeed]# insights-client --version
Client: 3.0.6-0
Core: 3.0.121-1
    Copy to Clipboard Toggle word wrap

  2. Enter the insights-client command with the --disable-schedule option to disable the client schedule. 

    [root@rhlightspeed]# insights-client --disable-schedule
    Copy to Clipboard Toggle word wrap

4.4.2. Enable the insights-client schedule
Link kopieren

When you enable the client schedule, it runs using its default settings. If you change the schedule, those settings take precedence.

When you run insights-client from the command line, insights-client runs using the settings you specify for only that session. When the next scheduled run takes place, it uses the default settings.

Prerequisites

  • Root-level access to your system.
  • The client schedule is disabled.
  • (Optional) You modified the default schedule.

Procedure

  1. Verify the client version on your system by entering the insights-client command with the --version option. 

    [root@rhlightspeed]# insights-client --version
Client: 3.0.6-0
Core: 3.0.121-1
    Copy to Clipboard Toggle word wrap

  2. Enter the insights-client command with the --enable-schedule option to enable the client schedule. 

    [root@rhlightspeed]# insights-client --enable-schedule
    Copy to Clipboard Toggle word wrap

4.4.3. Modify the insights-client schedule by using the systemd service
Link kopieren

You can change when the insights-client runs by modifying the schedule. The method that you use depends on the RHEL release and client version that your system is running. For Red Hat Enterprise Linux 7.5 and later, you can update the systemd settings and the insights-client.timer file.

Important

If you update the schedule using cron or the systemd.timer, those customized settings take precedence. However, if you change settings using the insights-client on the command line, the settings apply only to that session. When the next scheduled run takes place, the client uses your persistent customized settings.

Note

For Red Hat Enterprise Linux 7.4 and earlier, use cron to modify the system schedule. For more information about using cron, see the Red Hat Knowledgebase solution, What is cron and how is it used?.

Prerequisites

  • You have root-user access to your system.

Procedure

  1. To edit the settings in the insights-client.timer file, enter the systemctl edit command and the file name. 

    [root@rhlightspeed]# systemctl edit insights-client.timer
    Copy to Clipboard Toggle word wrap

    This action opens an empty file with the default system editor, on RHEL 6, 7, and 8. On RHEL 9 and later, running the command opens a file with a template that includes the original systemd service file as a reference.

  2. Enter different settings to modify the schedule. The values in this example are the default settings for systemd. 

    [Timer]
OnCalendar=daily
RandomizedDelaySec=14400
    Copy to Clipboard Toggle word wrap

  3. Enable the insights-client schedule. 

    [root@rhlightspeed]# insights-client --enable-schedule
    Copy to Clipboard Toggle word wrap
    • For more information, refer to the man pages for systemctl(1), systemd.timer(5), and systemd.time(7) to understand systemd

4.4.4. Enable automatic rule updates for Red Hat Lightspeed
Link kopieren

You can re-enable the automatic collection rule updates for Red Hat Lightspeed, if you previously disabled updates. By default, automatic rule update is enabled. Re-enable these updates to ensure that your system continues to benefit from the latest security and performance analysis provided by Red Hat Lightspeed.

Prerequisites

  • Root-level access to your system.
  • Automatic rule collection is disabled.

Procedure

  1. Open the /etc/insights-client/insights-client.conf file with an editor.

  2. Locate the line that contains the following: 

    auto_update=False
    Copy to Clipboard Toggle word wrap

  3. Change False to True. 

    auto_update=True
    Copy to Clipboard Toggle word wrap
  4. Save and close the /etc/insights-client/insights-client.conf file.

4.4.5. Disable automatic rule updates
Link kopieren

You can disable the automatic collection rule updates for Red Hat Lightspeed, but it is not a recommended action to take. Disabling the automatic rule updates puts your systems at risk of using outdated rule definition files and not getting the most recent validation or updates from Red Hat’s hosted services.

Prerequisites

  • Root-level access to your system.
  • Automatic rule updates are enabled.

Procedure

  1. Open the /etc/insights-client/insights-client.conf file with an editor.

  2. Locate the line that contains 

    #auto_update=True
    Copy to Clipboard Toggle word wrap

  3. Remove the # and change True to False. 

    auto_update=False
    Copy to Clipboard Toggle word wrap
  4. Save and close the /etc/insights-client/insights-client.conf file.

You can use the --build-packagecache option to provide accurate reporting for applicable updates on Satellite-managed systems. This option rebuilds the yum/dnf package caches for insights-client, and creates a refreshed list of applicable updates for the system.

You can run the command manually to rebuild the package caches immediately, or you can edit the client configuration file, /etc/insights-client/insights-client.conf, to rebuild the package caches automatically each time the system checks in to Red Hat Lightspeed.

Additional resources

Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2026 Red HatNach oben