API Doc
Search Docs...
⌘ K
OverviewDeploymentManagementOperationReferenceGlossary
    ACOS 6.3.0
  • Arcfra Cloud Operating System>
  • CLI command>
  • Managing networks

Managing the pre-deployment management network configuration

Use the command line to manage the management network configuration before deployment.

If a node with a configured management network is rebooted before the cluster is fully deployed, its management network configuration will be lost. Refer to Cleaning the pre-deployment management network configuration to clean up residual configurations and then reconfigure.

Bonding multiple network ports into a single LACP bond

Bond multiple network ports used by the management network into a single port that supports the LACP protocol. After bonding, the port name defaults to pre_bond, and the system generates the port configuration file ifcfg-pre_bond.

Procedure

Run the following command in the network port configuration file path:

network-preconfig create-lacp --nics <nics>

--nics <nics> (required) specifies the names of multiple network ports used by the management network. Separate multiple network port names with spaces and enclose them in double quotes (" ") if any name contains spaces, e.g., "eth0 eth1".

Usage example

Bond two network ports, eth0 and eth1, used by the management network into a single network port that supports the LACP protocol.

network-preconfig create-lacp --nics "eth0 eth1"

Output example

If create lacp bond port success is displayed, it indicates that the pre_bond port has been successfully created and the management ports have been bonded successfully.

If the system reports an error or requires configuration changes, refer to Cleaning the pre-deployment management network configuration to clean up residual configurations and then reconfigure.

Creating a VLAN subinterface

Create a VLAN subinterface for the single network port or bonded port used by the management network. Configure a static IP address, subnet mask, gateway, and VLAN ID for the VLAN subinterface, and generate the corresponding subinterface configuration file.

Procedure

Run the following command in the network port configuration file path:

network-preconfig create-vlanif --iface <iface> --ipaddr <ipaddr> --netmask <netmask> --gateway <gateway> --vlanid <vlanid>

Parameter description

Parameter Description
--iface <iface> Required. The network port name of the VLAN subinterface to be created.
  • If the management network port is the pre_bond port, the value is pre_bond.
  • If the management network port is a single port, the value is the actual port name, e.g., eth0.
--ipaddr <ipaddr> Required. The planned static IP address of the VLAN subinterface.
--netmask <netmask> Required. The planned subnet mask of the VLAN subinterface.
--gateway <gateway> Required. The planned gateway of the VLAN subinterface.
--vlanid <vlanid> Required. The planned VLAN ID of the VLAN subinterface.

The created subinterface is named pre_vlan.vlanid, and the corresponding configuration file is generated as ifcfg-pre_vlan.vlanid.

Usage example

Create a VLAN subinterface for the bonded network port pre_bond with the static IP 192.168.52.251, subnet mask 255.255.240.0, gateway 192.168.16.1, and VLAN ID 1.

network-preconfig create-vlanif --iface pre_bond --ipaddr 192.168.52.251 --netmask 255.255.240.0 --gateway 192.168.16.1 --vlanid 1

Output example

If create vlan interface success is displayed, the VLAN subinterface has been successfully created. The name of the created subinterface is pre_vlan. 1.

If the system reports an error or requires configuration changes, refer to Cleaning the pre-deployment management network configuration to clean up residual configurations and then reconfigure.

Configuring a static IP address, subnet mask, and gateway for the bonded network port

Directly configure the IP address and gateway for the bonded network port pre_bond without creating VLAN subinterfaces. The deployment will use the bonded network port directly.

Procedure

Run either of the following commands in the network port configuration file path:

  • network-preconfig config-bond-address --ipaddr <ipaddr> --netmask <netmask> --gateway <gateway>

    To clean or change the configuration, refer to Cleaning the pre-deployment management network configuration to clean up residual configurations.

  • network-preconfig config-address --iface pre_bond --ipaddr <ipaddr> --netmask <netmask> --gateway <gateway>

    To clean or change the configuration, run the ip addr del command.

Parameter description

Parameter Description
--ipaddr <ipaddr> Required. The static IP address planned for the bonded network port.
--netmask <netmask> Required. The static subnet mask planned for the bonded network port.
--gateway <gateway> Required. The static gateway planned for the bonded network port.

Usage example

Configure the bonded network port pre_bond with the static IP 192.168.52.251, subnet mask 255.255.240.0, gateway 192.168.16.1.

  • network-preconfig config-bond-address --ipaddr 192.168.52.251 --netmask 255.255.240.0 --gateway 192.168.16.1

  • network-preconfig config-address --iface pre_bond --ipaddr 192.168.52.251 --netmask 255.255.240.0 --gateway 192.168.16.1

Output example

If config ip address for pre_bond interface success is displayed, the IP configuration for pre_bond is successful.

Configuring a specified physical network port

Configure the static IP address, subnet mask, and default gateway for the specified physical network port.

To clean or change the configuration, run the ip addr del command.

Procedure

Run the following command in the network port configuration file path:

network-preconfig config-address --iface <iface> --ipaddr <ipaddr> --netmask <netmask> --gateway <gateway>

Parameter description

Parameter Description
--iface <iface> Required. The name of the physical network port of the management network for which the address is to be configured, for example, eth0.
--ipaddr <ipaddr> Required. The static IP address planned for the network port.
--netmask <netmask> Required. The subnet mask planned for the network port.
--gateway <gateway> Required. The gateway planned for the network port.

Usage example

Configure the physical network port eth0 with the static IP 192.168.52.251, subnet mask 255.255.240.0, gateway 192.168.16.1.

network-preconfig config-address --iface eth0 --ipaddr 192.168.52.251 --netmask 255.255.240.0 --gateway 192.168.16.1

Output example

If config ip address for eth0 interface success is displayed, the IP address, subnet mask, and gateway are successfully configured for the physical network port eth0.

Cleaning the pre-deployment management network configuration

Clean all pre-deployment management network configuration, including the configuration for bonding multiple network ports into an LACP-supported network port and for creating VLAN subinterfaces.

Procedure

Run the following command in the network port configuration file path:

network-preconfig clear-config

Output example

  • If delete pre_bond configuration is displayed, the configuration of the network port pre_bond has been successfully cleaned.
  • If delete pre_vlan configuration is displayed, the configuration of the VLAN subinterface has been successfully cleaned.

Cleaning all network configurations for a node

Clean all network configurations on the node, including the OVS bridge, system network, and bond configuration.

Risk warning

This operation cleans all network configurations on the node and carries a high risk. Execute it with caution.

Procedure

Run the following command in the network port configuration file path:

  • If delete pre_bond configuration is displayed, the configuration of the network port pre_bond has been successfully cleaned.
  • If delete pre_vlan configuration is displayed, the configuration of the VLAN subinterface has been successfully cleaned.

Output example

If clean network configuration success! is displayed, the network configurations on the node have been cleaned successfully.