Configuration scope and known limitations

Last Updated : Oct 30, 2026 |
Prolog information
The following constraints are enforced to ensure system integrity and predictable behavior:

Scope

The configNetwork script supports:
  • Dual bridge configuration (bridge0 & bridge1).
  • Dual bond configuration when configuring 2 bridges:
    • bond0 > bridge0
    • bond1 > bridge1
  • VLAN Trunking support.
    • When Configuring VLAN trunking:
      • Script can now configure 1-5 VLANs when using 1 Gbps Ports.
      • Script can now configure 1-10 VLANs when using 10/25 Gbps Ports.
      • Script can configure a dedicated bridge for every required VLAN.
      • VLAN trunking can be configured on either bridge0 or bridge1.
  • 10/25GB NIC on ASP 130A3/A31
    • Introduce support of the BCM57414 2x10/25GB Network Interface Card exclusively on the Dell R660xs profiles A3 and A31.
    • Ports will be labeled as P7 (NIC 7) / ens1f0np0 (Hypervisor) & P8 (NIC 8) / ens1f1np1 (Hypervisor)
Note:
When bonding ports (active/backup or LACP), both must be at either 10GB or 25GB.
Figure: Rear view of Dell PowerEdge R660xs -A3/A31 Server

Limitations

  • Out-of-Band Management (OOBM) is restricted to a single VLAN and cannot participate in trunking.
  • Cockpit must not be used to modify:
    • bridge0, bridgeoob or bridge1 (if configured) when configured via the network script configNetwork.
  • VLAN tagging within the VM guest OS is unsupported
Caution:
Unsupported changes may lead to network failure or require a full host re-image to restore connectivity.