Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
TOC
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

Contents

Table of Contents

Problem Description

When Charon emulators are run on a cloud instance, often one or more NICs must be configured manually for emulator use.

After configuring the network interface settings in a Linux cloud instance either manually (via nmcli or ip commands) or via the Charon-SSP Manager, the configuration is periodically reset to the default DHCP configuration.

Possible Causes of the Problem

All Clouds Supported by nm-cloud-setup

Problem Cause

In some operating systems like RHEL 8.4, NetworkManager includes two extra services called nm-cloud-setup.service and nm-cloud-setup.timer.

...

Such behavior can interfere with the manual configuration required for configuring a host interface dedicated to the emulator by resetting the manual configuration to the configuration retrieved from the instance metadata.

Solution

Test if the problem is caused by the nm-cloud-setup configuration:

...

# systemctl disable nm-cloud-setup
# systemctl stop nm-cloud-setup

Google Cloud Platform (GCP)

Problem Cause

By default, Google cloud tools installed on the Linux instance automatically start the attached network interfaces and configure them using DHCP. This resets any manual interface configuration periodically.

Should this be undesirable, for example, because a NIC is to be dedicated to the guest operating system running in the emulator, this automatic configuration can be suppressed by disabling the setup in the file /etc/default/instance_configs.cfg.

Problem Solution

Important information:

  • Older Charon-SSP marketplace images are based on CentOS 7, newer ones are based on Linux 8.x.
  • The NetworkManager is disabled by default in instances based on Charon marketplace images that use Linux 7.x.
  • If you disable the automatic interface setup by GCP on instances running Linux 7.x, you must make sure that the correct ifcfg-files for every interface exist in /etc/sysconfig/network-config. Failure to do so, can make your instance unreachable after the next network restart. On instances based on Charon marketplace images using Linux 8.x you can use the NetworkManager manually or via the Charon Manager to configure the IP setup for additional interfaces.
  • If you use a RHEL/CentOS 8 or later image as the base image for your Charon host, the interface must be controlled by the NetworkManager. You can set up the appropriate configuration by editing the interface configuration files, using nmcli commands, the nmtui utility or the Charon Manager.

...

Please note: if your instance normally would detect the network MTU automatically, this will not work if DHCP is disabled, and the correct MTU must be set manually.

Related

...

Articles

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@121d9
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel = "kb-troubleshooting-article" and type = "page" and space = "KBP"
labelskb-troubleshooting-article

Readers/approval