Welcome to Firefly
Switch language
Firefly Docsss
Last Updated: 2026-07-30 15:08:26

Sub Network Manager

Introduction

Sub Network Manager is a centralized network configuration function provided by aBMC for array servers. This function consists of two modules: network information management and configuration file operation.

  1. Network information management: Centrally view the IPv4 address, gateway, gateway priority, MAC address and DNS of the array sub-node network card, and supports DHCP or manual configuration.
  2. Configuration file operation: Provides network data export, template export and configuration import entrances. The import function only supports Linux devices.

Development Vision

  1. Provide array servers with a unified and visual network entrance to manage array sub-nodes, reducing the workload of logging in to devices one by one to configure the network.
  2. Reduce the risk of sub-board loss due to incorrect network configuration through clear configuration scope, private network card restrictions and result verification.

Feature Usage

View and configure network cards

Enter the network management page

  1. Select Devices in the main navigation bar on the left.
  2. Select Network in the secondary navigation bar.
  3. If you need to find the specified device, enter the device name in Enter device name; if you need to re-obtain the data, click Refresh.
  4. Confirm the target interface based on Device Name and Net Card in the network card list. The list displays both the BMC and the subboard network card, and does not display the loopback interface lo.

Enter the Network page: 1 select Devices, 2 select Network, 3 search or refresh, 4 view network list

View network card information

The same device may contain multiple network cards. Before configuration, the device name and network card name should be checked at the same time, and the original address, gateway, and DNS should be recorded to facilitate recovery in case of abnormalities.

FieldDescription
Device NameNode name, such as bmc or sub01.
Net CardThe name of the network card, such as MGMT, eth0, or eth1.
IPv4 AddressCurrent IPv4 address and prefix length. When there are multiple addresses for an interface, click the address to expand and view them.
GatewayThe current IPv4 default gateway.
Gateway PriorityThe routing priority of the current gateway.
MAC AddressNetwork card MAC address, used to identify the physical interface.
DNSCurrent DNS server list.
ActionsConfigure allows configuration when available; when the button is disabled, move the mouse over the button to see the reason for the restriction.

Determine whether the network card is allowed to be configured

  • Configure available: allows modification of this interface.
  • Configure Disabled: This interface is usually a private network card used by the BMC to communicate with the sub-board, or is restricted by the current topology policy and is not allowed to be configured.

Private network card restriction

Do not attempt to bypass page limits via the CLI or API. The backend will check the network card policy and return an error similar to card eth1 can not setting when Oem.Firefly.SettingEnabled is false.

Use DHCP to obtain the address

  1. Click Configure in the Actions column of the target interface.
  2. Select Auto (DHCP) in IPv4 Mode.
  3. If you need to specify DNS, enter the DNS server in DNS. Use commas to separate multiple addresses.
  4. Click Confirm.
  5. Return to the list and click Refresh to confirm that the interface has obtained the expected address.

Manually configure IPv4

First click Configure in the Actions column of the target interface to open the Configuration window, and then operate as shown below:

  1. Select Manual in IPv4 Mode.
  2. Enter the static IPv4 address in Address.
  3. Enter the corresponding subnet mask in Subnet Mask. After filling in a line of addresses, a blank line will automatically be added to the page, and you can continue to add other addresses.
  4. If you need to configure the default route, enter the gateway address in Gateway.
  5. When filling in the gateway, enter a positive integer priority in Gateway Priority.
  6. If you need to configure DNS, enter the DNS server in DNS; separate multiple addresses with commas.
  7. After checking that the parameters are correct, click Confirm to save the configuration.
  8. If you do not want to save this modification, click Cancel.

Configure a single network card: 1 IPv4 mode, 2 address, 3 subnet mask, 4 gateway, 5 gateway priority, 6 DNS, 7 OK, 8 Cancel

Modify DNS

First open the Configuration window of the target interface and keep the current IPv4 mode, address and gateway parameters unchanged, and then operate as shown below:

  1. Modify the server address in DNS. Use commas to separate multiple addresses, such as 192.0.2.53,192.0.2.54.
  2. Click Confirm to save changes.
  3. If you do not want to save this modification, click Cancel.

Configure the DNS field of the currently selected network card: 1 DNS, 2 Confirm, 3 Cancel

Configuration rules

Configuration itemsRules
Auto (DHCP)IPv4 addresses are assigned by a DHCP service. The static address and gateway should no longer be filled in when submitting.
AddressManual mode fills in at least one valid IPv4 address; supports configuring multiple addresses for the same interface.
Subnet MaskEach static address must be filled with a valid subnet mask.
GatewayOptional; Gateway Priority must be filled in when filling in the gateway.
Gateway PriorityMust be a positive integer. The same gateway and priority combination cannot be repeated with other network cards or VLANs.
DNSOptional; must be a valid IP address, multiple addresses separated by commas.

Current page capabilities

The current version only opens IPv4 Configuration. The IPv6 Configuration and VLAN Configuration tags are disabled.

Verify configuration results

  1. Return to the Network list and click Refresh.
  2. Find the device and network card you just configured.
  3. Confirm that the IPv4 Address, Gateway, Gateway Priority, and DNS are updated.
  4. Verify address connectivity, default route, and domain name resolution from the corresponding network segment.

Network Change Risk

Modifying the address, subnet mask, or default gateway in use may cause the device to immediately lose contact. Before operation, the original configuration should be recorded and a serial port or other independent recovery channel should be prepared. The address in the screenshot is only used to illustrate the page location.

Import and export network configuration

Open the batch operation entrance

You can use the following operations in the upper right corner of the Network page:

  1. Export Data: Export network information within the current query range.
  2. Export Template: Export the network configuration template of the Linux device.
  3. Import: Import the completed .xls or .xlsx file.
  4. Move the mouse pointer to Import to view the import restrictions: currently only Linux devices are supported, and Android sub-boards are not supported.

File operation and import restrictions: 1 Export Data, 2 Export Template, 3 Import, 4 Android sub-boards do not support import and only Linux devices are supported

Export current network data

  1. If you need to restrict exported devices, first enter the device name in Enter device name.
  2. Click Export Data.
  3. Open the exported Excel file and verify that it contains the device name, network card, IPv4 address, gateway, gateway priority, MAC address, and DNS.

Export Data Exports all data matching the current search conditions, regardless of page paging restrictions.

Export and fill in the configuration template

  1. If you need to limit the devices in the template, first search by device name.
  2. Click Export Template.
  3. Keep the header of the first row and the original column order, and fill in the configuration in the first worksheet of the template.
Template columnRequiredFilling instructions
Device NameYesThe target node name, for example, sub01. Must be consistent with the device name on the page.
Net CardYesThe target network card name, such as eth0; lo will not be imported.
IPv4 AddressManual mode is requiredUse the IPv4/prefix-length format, such as 192.0.2.10/24; separate multiple addresses with commas.
GatewayNoIPv4 default gateway.
Dhcp4It is recommended to fill inIt is recommended to fill in yes or no. yes, true or 1 represents DHCP; when left blank or filled in with other values, press Manual.
Gateway PriorityNoGateway routing priority, fill in the number.
DNSNoDNS server; separate multiple addresses with commas.

Number of template lines

When the file contains a header, a maximum of 100 rows are allowed, that is, a maximum of 99 pieces of configuration data are allowed. The page only reads the first worksheet.

Import network configuration

  1. Confirm that the device and network card in the template exist, and delete the lines that do not need to be modified.
  2. Click Import and select the completed Excel file.
  3. Wait for the success or failure prompt for each device/network card. The page can handle up to 5 configuration requests at the same time.
  4. After the import is completed, the page will re-obtain network information.

Import processing rules

RulesProcessing
The device name or network card name is emptyFile verification failed and the import will not start.
The network card is loFile verification failed.
The device or network card does not exist in the current listSkip this line.
The configuration content is emptySkip this line.
Configuration consistent with current valuesSkip this line.
Linux devicesSupport for import.
Android sub-boardThe current version does not support import.

Verify import results

  1. Click Refresh after the import is complete.
  2. Verify the IPv4 address, gateway, gateway priority, and DNS of the affected interface.
  3. Verify the target device’s network connectivity and domain name resolution.

Batch import risk

Batch import will directly modify the network configuration of multiple devices. You should use Export Data to back up current information before importing, and ensure that all target devices have independent recovery channels.

FAQ

Target device not found

Clear or modify the search conditions in Enter device name, click Refresh and search again.

2.Configure is not available

This interface may be a separate private network card used by the BMC to communicate with the sub-board. Check the page prompt; if it is confirmed to be a private network card, it cannot be modified by the user.

3.IPv6 Configuration or VLAN Configuration cannot be selected

These two configuration tags are not yet open in the current interface. Please use the currently available IPv4 Configuration and do not treat the disabled label as a supported feature.

How to fill in multiple DNS addresses

According to the page prompt Use commas to separate IP addresses, use English commas to separate multiple addresses. Do not use Chinese commas.

5.Import cannot import Android sub-board

This is a feature limitation of the current version. Import only supports Linux devices, and Android sub-boards do not support importing network configurations.

On this page