BMC Network Management
Introduction
BMC Network Management (BMC Network Manager) is a network status viewing and configuration feature that aBMC provides for the management controller. It consists of the following three modules.
- Net Manage: view physical network port status, and configure IPv4 address, default gateway, gateway priority, and DNS via DHCP or manually.
- Bond Manage: combine multiple available network ports into a Bond aggregation device, and configure the aggregation mode and IPv4 network parameters.
- VLAN Manage: create VLAN sub-interfaces on a specified network port, and configure the VLAN ID, associated port, and IPv4 network parameters.
Version Requirement
aBMC version >= v1.4.0
Development Vision
- Provide a unified, visualized entry point for BMC network status and configuration, making it easy to quickly check the management network, aggregation network, and VLAN network status.
- Reduce the risk of losing BMC connectivity due to mistakenly modifying critical network ports, through NIC type restrictions, parameter validation, and configuration result confirmation.
Feature Usage
Viewing and Configuring BMC Network Ports
Open the BMC network management page
- Select System in the left main navigation bar.
- Select Network in the secondary navigation bar.
- Select Net Manage at the top of the page.
- In the network port tabs, select the target NIC, for example Net Port or Net Port.
- To modify the configuration, click Setting.
View network port information
Before modifying the configuration, identify the target NIC by port name and MAC address, and record the original network configuration.
| Page field | Description |
|---|---|
| Net Port | BMC NIC name, for example MGMT, nic0, or nic1. The loopback interface lo is not displayed. |
| NIC Type | The management type of the NIC. Hover the pointer over Setting to view the purpose and configuration restrictions of the current type. |
| MAC Address | The MAC address of the NIC, used to identify the physical interface. |
| Connection Status | The current connection status of the port, for example In Use, Not In Use, or Exception. |
| IPv4 Address | The current IPv4 address and prefix length. Multiple addresses may be displayed for the same NIC. |
| Default Gateway | The current IPv4 default gateway. |
| Gateway Priority | The routing priority of the current default gateway, that is, the metric in the routing table; a smaller value means higher priority. |
| DNS | The current DNS servers. |
Determine whether a NIC allows configuration
- Setting available: the current NIC allows the user to modify its configuration.
- Setting disabled: the current NIC may be a private NIC used for communication between the BMC and sub-boards, a Bond device, or a Bond member, and cannot be configured directly by the user.
NIC type restrictions
Do not attempt to bypass page restrictions through the CLI or API. Before configuring, confirm that Oem.Firefly.SettingEnabled in the NIC resource is true.
Configure IPv4
- Confirm that the current mode is IPv4 Configuration. IPv6 Configuration and VLAN Configuration are currently unavailable.
- In IPv4 Mode, select Auto (DHCP) or Manual.
- When using Manual, enter the Address and Subnet Mask. After a complete address is entered, the page automatically adds a blank row; if a default route is needed, enter the Gateway and Gateway Priority as a pair in the first row. A smaller priority value means higher priority.
- Enter DNS servers in DNS; separate multiple addresses with commas.
- To discard the changes, click Cancel.
- After verifying the parameters, click Confirm.
Configuration rules
| Item | Rule |
|---|---|
| Auto (DHCP) | The IPv4 address is assigned by the DHCP service. |
| Address | In Manual mode, at least one valid IPv4 address must be entered; multiple addresses on the same NIC are supported. |
| Subnet Mask | In Manual mode, each static address must be accompanied by a valid subnet mask. |
| Gateway | Optional; must be a valid IPv4 address and must be entered together with Gateway Priority. In multi-address scenarios, enter it only in the first row. |
| Gateway Priority | Routing metric of the gateway; must be a positive integer, and a smaller value means higher priority. The same gateway and priority combination must not duplicate another NIC or VLAN. |
| DNS | Optional; must be valid IP addresses, separated by commas. |
Gateway and gateway priority
Gateway and Gateway Priority must be entered as a pair; entering only one of them fails to submit. The priority is the metric of the route in the routing table, and a smaller value means higher priority. When multiple default routes exist, the one with the smallest metric takes effect first, and the others remain in the routing table as backups.
Confirm the configuration result
- Close the settings window and wait for the page to fetch the NIC information again.
- Select the target Net Port again.
- Confirm that IPv4 Address, Default Gateway, Gateway Priority, and DNS have been updated.
- From the corresponding subnet, verify the BMC address connectivity, default route, and domain name resolution.
BMC network change risks
Modifying the management address, subnet mask, or default gateway currently in use may immediately interrupt WEB, CLI, and API connections. Record the original configuration before operating, and prepare a serial port or another independent recovery channel. The addresses in the screenshots are for illustrating page locations only.
View BMC NIC information
When no configuration parameters are specified, bmc ethernet returns BMC NIC information.
bmc ethernet --protocol https --ip <BMC_IP> --port <BMC_PORT> --user <USERNAME> --password <PASSWORD> --core bmcUse --interface to view a specific NIC.
bmc ethernet --protocol https --ip <BMC_IP> --port <BMC_PORT> --user <USERNAME> --password <PASSWORD> --core bmc --interface <INTERFACE>Use DHCP
bmc ethernet --protocol https --ip <BMC_IP> --port <BMC_PORT> --user <USERNAME> --password <PASSWORD> --core bmc --interface <INTERFACE> --interface-dhcp4=trueConfigure static IPv4
The following addresses belong to documentation example subnets and must be replaced with on-site planned values before execution.
bmc ethernet --protocol https --ip <BMC_IP> --port <BMC_PORT> --user <USERNAME> --password <PASSWORD> --core bmc --interface <INTERFACE> --interface-dhcp4=false --interface-ip 192.0.2.10 --interface-ip-cidr 24 --interface-gateway 192.0.2.1 --interface-gateway-metric 100 --interface-dns 192.0.2.53The CLI can submit only one static address and one DNS server at a time. To configure multiple addresses or multiple DNS servers for the same NIC, use the WEB or API.
Parameter description
| Parameter | Required | Description |
|---|---|---|
--protocol | Yes | Request protocol, for example https. |
--ip | Yes | BMC management address. |
--port | Yes | Redfish service port. |
--user | Yes | HTTP Basic authentication username. |
--password | Yes | HTTP Basic authentication password. |
--core | Yes | BMC network management always uses bmc. |
--interface | Required when viewing a single interface or configuring | Target NIC name, for example MGMT or nic1. |
--interface-dhcp4 | Required when configuring | true for DHCP, false for static configuration. |
--interface-ip | Used for static configuration | IPv4 address. |
--interface-ip-cidr | No | IPv4 prefix length; when an IP is specified but this parameter is not, the CLI uses 24 by default. |
--interface-gateway | No | IPv4 default gateway. |
--interface-gateway-metric | No | Gateway routing priority (metric); must be an integer, and a smaller value means higher priority. Must be used together with --interface-gateway. |
--interface-dns | No | DNS server. The current CLI accepts one DNS address at a time. |
--output-format | No | Specifies the client output format. |
Credential and network security
Passwords on the command line may be retained in shell history or process lists. Before executing a configuration command, confirm that the target NIC allows configuration, and prepare an independent recovery channel.
| Operation | Method | URI |
|---|---|---|
| View the BMC NIC collection | GET | /redfish/v1/Systems/bmc/EthernetInterfaces |
| View a specific BMC NIC | GET | /redfish/v1/Systems/bmc/EthernetInterfaces/{EthernetInterfaceId} |
| Query configuration action parameters | GET | /redfish/v1/Systems/bmc/EthernetInterfaces/{EthernetInterfaceId}/Actions/Oem/Firefly/ConfigureActionInfo |
| Configure a specific BMC NIC | POST | /redfish/v1/Systems/bmc/EthernetInterfaces/{EthernetInterfaceId}/Actions/Oem/Firefly/EthernetInterface.Configure |
Note
For detailed information about interface authentication, request parameters, response fields, and error codes, refer to the Redfish API documentation.
Configuring BMC Network Bonding
Open Bond Manage
- Select System in the left main navigation bar.
- Select Network in the secondary navigation bar.
- Select Bond Manage at the top of the page.
- If there are multiple Bond devices, select the target Device.
- Click Add to add a Bond device.
- Click Setting to modify the current Bond device.
- Click remove to delete the current Bond device.
View Bond status
| Page field | Description |
|---|---|
| Device | Bond device name, for example bond0. |
| MTU | Maximum transmission unit of the Bond device. |
| MAC Address | MAC address of the Bond device. |
| Mode | Current network aggregation mode. |
| IPv4 Address | Current IPv4 address of the Bond device. |
| Default Gateway | Current IPv4 default gateway. |
| Gateway Priority | Routing priority of the default gateway, that is, the metric in the routing table; a smaller value means higher priority. |
| Net Port | Member ports of the current Bond. |
| DNS | Current DNS servers. |
Add a Bond device
- Enter the Bond device name in Device.
- In Net card, select at least two available ports. Grayed-out ports cannot join a new Bond at this time.
- Select the aggregation mode in Mode.
- In IPv4 Mode, select Auto (DHCP) or Manual.
- When using Manual, enter the address, subnet mask, gateway, and gateway priority.
- Fill in DNS as needed; separate multiple addresses with commas.
- To discard the changes, click Cancel.
- After checking the configuration, click Add.
Modify or delete a Bond device
When modifying a Bond, the device name cannot be changed; member ports, aggregation mode, and IPv4 parameters can be adjusted. Modify can be submitted only after at least two available member ports are selected.
When deleting a Bond, click remove, check the device name in the confirmation window, and then confirm the deletion. Before deleting, confirm that the Bond does not carry the current management connection or business traffic.
Bond configuration rules
| Item | Rule |
|---|---|
| Device | Required; 3–15 characters long, must start with bond, and can contain only letters and digits. After creation, it cannot be renamed in the modify window. |
| Net card | Select at least two non-loopback ports. Private ports, configuration-restricted ports, and ports already belonging to another Bond are not selectable. |
| Mode | Valid values are 802.3ad, active-backup, balance-alb, balance-rr, balance-tlb, balance-xor, broadcast. |
| Auto (DHCP) | The IPv4 address of the Bond device is assigned by the DHCP service. |
| Manual | Supports configuring one or more IPv4 addresses, subnet masks, default gateway, gateway priority, and DNS. |
| Setting | Available only when Oem.Firefly.SettingEnabled of the Bond resource is true. |
Member port impact
After a port joins a Bond, it can no longer be configured directly as an independent port. Changing Bond members or mode may cause a brief link interruption; when using modes such as 802.3ad, also make sure the peer switch configuration matches the server.
| Operation | Method | URI |
|---|---|---|
| View the Bond collection | GET | /redfish/v1/Systems/bmc/NetworkBondings |
| View a specific Bond | GET | /redfish/v1/Systems/bmc/NetworkBondings/{NetworkBondingId} |
| Query add action parameters | GET | /redfish/v1/Systems/bmc/NetworkBondings/Actions/Oem/Firefly/AddConfigureActionInfo |
| Query modify action parameters | GET | /redfish/v1/Systems/bmc/NetworkBondings/{NetworkBondingId}/Actions/Oem/Firefly/ConfigureActionInfo |
| Query delete action parameters | GET | /redfish/v1/Systems/bmc/NetworkBondings/Actions/Oem/Firefly/DelConfigureActionInfo |
| Add a Bond | POST | /redfish/v1/Systems/bmc/NetworkBondings/Actions/Oem/Firefly/NetworkBondingAdd.Configure |
| Modify a Bond | POST | /redfish/v1/Systems/bmc/NetworkBondings/{NetworkBondingId}/Actions/Oem/Firefly/NetworkBonding.Configure |
| Delete a Bond | POST | /redfish/v1/Systems/bmc/NetworkBondings/Actions/Oem/Firefly/NetworkBondingDel.Configure |
An add request mainly contains Device, Mode, Interfaces, and IPv4Addresses; when modifying, the Bond device is specified in the URI and Device is not submitted; a delete request submits the target Device.
Note
For detailed information about interface authentication, request parameters, response fields, and error codes, refer to the Redfish API documentation.
Managing BMC VLANs
Open VLAN Manage
- Select System in the left main navigation bar.
- Select Network in the secondary navigation bar.
- Select VLAN Manage at the top of the page.
- If there are multiple VLAN devices, select the target Net Port.
- Click Add to add a VLAN device.
- When Setting is available, you can modify the IPv4 configuration of the current VLAN.
- When remove is available, you can delete the current VLAN.
View VLAN status
| Page field | Description |
|---|---|
| Net Port | VLAN device name, for example vlan4000. |
| NIC Type | Management type of the VLAN device. |
| MAC Address | MAC address of the VLAN device. |
| Connection Status | Current connection status of the VLAN device. |
| IPv4 Address | Current IPv4 address and prefix length of the VLAN device. |
| Default Gateway | Current IPv4 default gateway. |
| Gateway Priority | Routing priority of the default gateway, that is, the metric in the routing table; a smaller value means higher priority. |
| DNS | Current DNS servers. |
| VLAN ID | VLAN identifier. |
| VLAN Link | Underlying network port associated with the VLAN sub-interface. |
Add a VLAN device
- Enter the VLAN identifier in VLAN ID.
- Confirm the VLAN device name in Device. After a valid VLAN ID is entered and the input box loses focus, the page automatically generates
vlan<VLAN_ID>if the field is empty. - Select the underlying port in VLAN Link.
- In IPv4 Mode, select Auto (DHCP) or Manual.
- When using Manual, enter the address, subnet mask, gateway, and gateway priority.
- Fill in DNS as needed; separate multiple addresses with commas.
- To discard the changes, click Cancel.
- After checking the configuration, click Add.
Modify or delete a VLAN
- When Setting is available, you can modify the IPv4 mode, address, subnet mask, gateway, gateway priority, and DNS. The VLAN ID, device name, and VLAN Link of an existing VLAN cannot be changed in the modify window.
- When remove is available, click the button and confirm the deletion in the confirmation window.
- When both Setting and remove are disabled, the current VLAN's
Oem.Firefly.SettingEnabledisfalse—for example, an independent private VLAN used for internal system communication. Such VLANs cannot be modified or deleted through the current page.
VLAN configuration rules
| Item | Rule |
|---|---|
| VLAN ID | Required; must be an integer in the range 1–4094. |
| Device | Required when adding. Generated by default as vlan<VLAN_ID>; after creation, it cannot be renamed in the modify window. |
| VLAN Link | Required when adding; select the underlying port that carries the VLAN. The loopback interface lo is not available. |
| Auto (DHCP) | The IPv4 address of the VLAN device is assigned by the DHCP service. |
| Manual | Supports configuring one or more IPv4 addresses, subnet masks, default gateway, gateway priority, and DNS. |
| Gateway Priority | Routing metric of the gateway; a smaller value means higher priority. The same gateway and priority combination must not duplicate another NIC or VLAN. |
| SettingEnabled | When false, both the modify and delete buttons in the WEB are unavailable. Do not bypass the restriction to operate on system-internal VLANs. |
VLAN connectivity requirements
Before creating a VLAN, confirm that the peer switch port permits the corresponding VLAN ID and that the VLAN Link is selected correctly. An incorrect VLAN ID, underlying port, or gateway configuration may make the VLAN address unreachable.
| Operation | Method | URI |
|---|---|---|
| View the VLAN collection | GET | /redfish/v1/Systems/bmc/NetworkVLANs |
| View a specific VLAN | GET | /redfish/v1/Systems/bmc/NetworkVLANs/{NetworkVLANId} |
| Query add action parameters | GET | /redfish/v1/Systems/bmc/NetworkVLANs/Actions/Oem/Firefly/AddConfigureActionInfo |
| Query modify action parameters | GET | /redfish/v1/Systems/bmc/NetworkVLANs/{NetworkVLANId}/Actions/Oem/Firefly/ConfigureActionInfo |
| Query delete action parameters | GET | /redfish/v1/Systems/bmc/NetworkVLANs/Actions/Oem/Firefly/DelConfigureActionInfo |
| Add a VLAN | POST | /redfish/v1/Systems/bmc/NetworkVLANs/Actions/Oem/Firefly/NetworkVlANAdd.Configure |
| Modify a VLAN | POST | /redfish/v1/Systems/bmc/NetworkVLANs/{NetworkVLANId}/Actions/Oem/Firefly/NetworkVLAN.Configure |
| Delete a VLAN | POST | /redfish/v1/Systems/bmc/NetworkVLANs/Actions/Oem/Firefly/NetworkVLANDel.Configure |
An add request mainly contains Device, Id, Link, and IPv4Addresses; when modifying, the VLAN device is specified in the URI, and Id, Link, and IPv4Addresses are submitted; a delete request submits the target Device.
Note
For detailed information about interface authentication, request parameters, response fields, and error codes, refer to the Redfish API documentation.
FAQ
Setting is unavailable
The current NIC, Bond, or VLAN may be a system-internal communication interface, a configuration-restricted private interface, or a Bond member. Query the corresponding resource and check Oem.Firefly.SettingEnabled; when the value is false, it cannot be modified.
Cannot access the BMC after modification
If the modified object is the current communication port, Bond, or VLAN, the original address may become invalid immediately. Reconnect using the new address; if the connection fails, restore the original configuration through the serial port or another independent channel.
Why some ports cannot join a Bond
The loopback interface, private ports, ports with SettingEnabled set to false, and ports that already belong to another Bond cannot join a new Bond. A Bond requires at least two available member ports.
How to choose a Bond mode
For typical active/standby scenarios, use active-backup; when the Link Aggregation Control Protocol is required, use 802.3ad and configure the switch accordingly; choose other load-balancing modes based on the network topology and peer capabilities.
Why both Setting and remove of a VLAN are disabled
The current VLAN's SettingEnabled is false, which usually means the VLAN is used for system-internal or private communication. Do not bypass the restriction through the API to modify or delete it.
How to configure multiple IPv4 addresses
In the WEB Manual mode, after completing a row of Address and Subnet Mask, the page automatically adds a blank row. The CLI can submit only one address for a physical NIC at a time; for multiple addresses, use the WEB or API.
What is gateway priority, and how do I handle a conflict warning?
Gateway Priority is the metric of the default gateway route in the routing table. It must be entered together with Gateway: entering only a gateway without a priority, or only a priority without a gateway, cannot be submitted.
A smaller value means higher priority. When multiple default routes exist, the one with the smallest metric takes effect first, and the others remain in the routing table as backups, for example:
default via 192.168.20.1 dev vlan20 metric 100
default via 192.168.30.1 dev vlan30 metric 200With the configuration above, outbound traffic uses vlan20 first and switches to vlan30, whose metric is larger, only when the vlan20 link becomes unavailable.
A conflict warning means the same gateway and priority combination is already used by another NIC, Bond, or VLAN. Adjust Gateway or Gateway Priority so that the combination differs from the existing ones.

