Configuring physical interfaces
Steps
1. Select Hardware > Ethernet > Interfaces.
2. Select an interface to configure.
3. Click Configure.
4. In the Configure Interface dialog box, determine how the interface IP address is to be set:
NOTE: On an HA system, the Configure Interface dialog box has a field for whether or not to designate the Floating
IP (Yes/No). Selecting Yes the Manually Configure IP Address radio button is auto-selected; Floating IP
interfaces can only be manually configured.
● Use DHCP to assign the IP address—in the IP Settings area, select Obtain IP Address using DHCP and select either
DHCPv4 for IPv4 access or DHCPv6 for IPv6 access.
Setting a physical interface to use DHCP automatically enables the interface.
NOTE: If you choose to obtain the network settings through DHCP, you can manually configure the hostname at
Hardware > Ethernet > Settings or with the net set hostname command. You must manually configure the
host name when using DHCP over IPv6.
● Specify IP Settings manually—in the IP Settings area, select Manually configure IP Address.
The IP Address and Netmask fields become active.
5. If you chose to manually enter the IP address, enter an IPv4 or IPv6 address. If you entered an IPv4 address, enter a
netmask address.
NOTE: You can assign just one IP address to an interface with this procedure. If you assign another IP address, the new
address replaces the old address. To attach an additional IP address to an interface, create an IP alias.
6. Specify Speed/Duplex settings.
NOTE: Speed and duplex cannot be set on DD3300, DD6400, DD6900, DD9400, and DD9900 systems.
The combination of speed and duplex settings define the rate of data transfer through the interface. Select one of these
options:
● Auto negotiate Speed/Duplex — Select this option to allow the network interface card to auto negotiate the line speed
and duplex setting for an interface. Auto negotiation is not supported on the following DD4200, D4500, DD6300, DD6800,
DD7200, DD9300, DD9500, and DD9800 I/O modules:
○ Dual port 10GbE SR Optical with LC connectors (using SFPs)
○ Dual port 10GbE Direct Attach Copper (SFP+ cables)
○ Quad port 2 port 1GbE Copper (RJ45) /2 port 1GbE SR Optical
○ Auto negotiate Speed/Duplex is required for all I/O modules on the DD3300, DD6400, DD6900, DD9400, and
DD9900 systems:
￭ Quad port 10GbE Base-T
￭ Quad port 10GbE SFP+
￭ Dual port 10/25GbE SFP28
￭ Dual port 100GbE QSFP28
● Manually configure Speed/Duplex — Select this option to manually set an interface data transfer rate. Select the
speed and duplex from the menus.
NOTE: This option is not available on DD3300, DD6400, DD6900, DD9400, and DD9900 systems.
○ Duplex options are half-duplex, full-duplex, and unknown.
○ Speed options listed are limited to the capabilities of the hardware device. Options are 10 Mb, 100 Mb, 1000 Mb (1
Gb), 10 Gb, and unknown. The 10G Base-T hardware supports only the 100 Mb, 1000 Mb and 10 Gb settings.
○ Half-duplex is only available for 10 Mb and 100 Mb speeds.
○ 1 Gb and 10 Gb line speeds require full-duplex.
○ On DD4200, DD4500, and DD7200 10 GbE I/O modules, copper interfaces support only the 10 Gb speed setting.
○ The default setting for 10G Base-T interfaces is Auto negotiate Speed/Duplex. If you manually set the speed to 1000
Mb or 10 Gb, you must set the Duplex setting to Full.
7. Specify the MTU (Maximum Transfer Unit) size for the physical (Ethernet) interface.
Do the following:
● Click the Default button to return the setting to the default value.
● Ensure that all of your network components support the size set with this option.
8. Optionally, select Dynamic DNS Registration.
Dynamic DNS (DDNS) is a protocol that registers local IP addresses on a Domain Name System (DNS) server. In this release,
DD System Manager supports Windows mode DDNS. To use UNIX mode DDNS, use the net ddns CLI command.
The DDNS must be registered to enable this option.
NOTE: This option disables DHCP for this interface.
9. Click Next.
The Configure Interface Settings summary page appears. The values listed reflect the new system and interface state, which
are applied after you click Finish.
10. Click Finish and OK.
MTU size values
The MTU size must be set properly to optimize the performance of a network connection. An incorrect MTU size can negatively
affect interface performance.
Supported values for setting the maximum Transfer Unit (MTU) size for the physical (Ethernet) interface range from 600 to
9000 for IPv4, and 1280 to 9000 for IPv6. For 100 Base-T and gigabit networks, 1500 is the standard default.
NOTE: The minimum MTU for IPv6 interfaces is 1280. The interface fails if you try to set the MTU lower than 1280.
Moving a static IP address
A specific static IP address must be assigned to only one interface on a system. A static IP address must be properly removed
from one interface before it is configured on another interface.
Steps
1. If the interface that hosts the static IP address is part of a DD Boost interface group, remove the IP address from that
group.
NOTE: Add the new IP address back to the DD Boost interface group after this task is complete.
2. Select Hardware > Ethernet > Interfaces.
3. Remove the static IP address that you want to move.
a. Select the interface that is currently using the IP address you want to move.
b. In the Enabled column, select No to disable the interface.
c. Click Configure.
d. Set the IP Address to 0.
NOTE: Set the IP address to 0 when there is no other IP address to assign to the interface. The same IP address
must not be assigned to multiple interfaces.
e. Click Next, and click Finish.
4. Add the removed static IP address to another interface.
a. Select the interface to which you want to move the IP address.
b. In the Enabled column, select No to disable the interface.
c. Click Configure.
d. Set the IP Address to the match the static IP address you removed.
e. Click Next, and click Finish.
f. In the Enabled column, select Yes to enable the updated interface.
Bonded interface creation
Create a bonded interface to support link aggregation or failover. The bonded interface serves as a container for the links to be
aggregated or associated for failover.
Creating a bonded interface for link aggregation
Create a bonded interface for link aggregation to serve as a container to associate the links that participate in aggregation.
About this task
A link aggregation interface must specify a link bonding mode and may require a hash selection. For example, you might enable
link aggregation on bonded interface veth1 to physical interfaces eth2b and eth5c in mode LACP (Link Aggregation Control
Protocol) and hash XOR-L2L3.
Steps
1. Select Hardware > Ethernet > Interfaces.
2. In the Interfaces table, disable the physical interface where the bonded interface is to be added by clicking No in the
Enabled column.
3. From the Create menu, select Virtual Interface.
4. In the Create Virtual Interface dialog box, specify a bonded interface name in the veth box. Enter a bonded interface name in the form vethx, where x is a unique ID (typically one or two digits). A typical full bonded interface name with VLAN and IP Alias is veth 56.3999:199. The maximum length of the full name is 15 characters. Special characters are not allowed. Numbers must be between 0 and 4094, inclusively. 5. In the Bonding Type list, select Aggregate. NOTE: Registry settings can be different from the bonding configuration. When interfaces are added to the bonded interface, the information is not sent to the bonding module until the bonded interface is brought up. Until that time the registry and the bonding driver configuration are different. 6. In the Mode list, select a bonding mode. Specify the mode that is compatible with the requirements of the system to which the interfaces are directly attached. ● Round-robin Transmit packets in sequential order from the first available link through the last in the aggregated group. ● Balanced Data is sent over interfaces as determined by the hash method selected. This requires the associated interfaces on the switch to be grouped into an Etherchannel (trunk) and given a hash via the Load Balance parameter. ● LACP Link Aggregation Control Protocol is similar to Balanced, except that it uses a control protocol that communicates to the other end and coordinates which links within the bond are available for use. LACP provides a kind of heartbeat failover and must be configured at both ends of the link. 7. If you selected Balanced or LACP mode, specify a bonding hash type in the Hash list. Options are: XOR-L2, XOR-L2L3, or XOR-L3L4. XOR-L2 transmits through a bonded interface with an XOR hash of Layer 2 (inbound and outbound MAC addresses). XOR-L2L3 transmits through a bonded interface with an XOR hash of Layer 2 (inbound and outbound MAC addresses) and Layer 3 (inbound and outbound IP addresses). XOR-L3L4 transmits through a bonded interface with an XOR hash of Layer 3 (inbound and outbound IP addresses) and Layer 4 (inbound and outbound ports). 8. To select an interface to add to the aggregate configuration, select the checkbox that corresponds to the interface, and then click Next. The Create bonded interface veth_name dialog box appears. 9. Enter an IP address, or enter 0 to specify no IP address. 10. Enter a netmask address or prefix. 11. Skip the Speed/Duplex options as they are ignored for bonding. 12. Specify the MTU setting. ● To select the default value (1500), click Default. ● To select a different setting, enter the setting in the MTU box. Ensure that all of your network components support the size set with this option. 13. Optionally, select Dynamic DNS Registration option. Dynamic DNS (DDNS) is a protocol that registers local IP addresses on a Domain Name System (DNS) server. In this release, DD System Manager supports Windows mode DDNS. To use UNIX mode DDNS, use the net ddns CLI command. The DDNS must be registered to enable this option. 14. Click Next. The Configure Interface Settings summary page appears. The values listed reflect the new system and interface state. 15. Click Finish and OK.
Creating a bonded interface for link failover
Create a bonded interface for link failover to serve as a container to associate the links that will participate in failover. About this task The failover-enabled bonded interface represents a group of secondary interfaces, one of which can be specified as the primary. The system makes the primary interface the active interface whenever the primary interface is operational. A configurable Down Delay failover option allows you to configure a failover delay in 900 millisecond intervals. The failover delay guards against multiple failovers when a network is unstable. NOTE: Modifying up and down delay is not supported in DD3300. Only one default setting of 100ms is supported. Steps 1. Select Hardware > Ethernet > Interfaces. 2. In the interfaces table, disable the physical interface to which the bonded interface is to be added by clicking No in the Enabled column. 3. From the Create menu, select Virtual Interface. 4. In the Create Virtual Interface dialog box, specify a bonded interface name in the veth box. Enter a bonded interface name in the form vethx, where x is a unique ID (typically one or two digits). A typical full bonded interface name with VLAN and IP Alias is veth56.3999:199. The maximum length of the full name is 15 characters. Special characters are not allowed. Numbers must be between 0 and 4094, inclusively. 5. In the Bonding Type list, select Failover. 6. Select an interface to add to the failover configuration, and click Next. Virtual aggregate interfaces can be used for failover. The Create Virtual interface veth_name dialog box appears. 7. Enter an IP address, or enter 0 to specify no IP address. 8. Enter a netmask or prefix if an IP address was specified. 9. Skip the Speed/Duplex options as they are ignored for bonding. 10. Specify MTU setting. ● To select the default value (1500), click Default. ● To select a different setting, enter the setting in the MTU box. Ensure that all of your network path components support the size set with this option. 11. Optionally, select Dynamic DNS Registration option. Dynamic DNS (DDNS) is a protocol that registers local IP addresses on a Domain Name System (DNS) server. In this release, DD System Manager supports Windows mode DDNS. To use UNIX mode DDNS, use the net ddns CLI command. The DDNS must be registered to enable this option. NOTE: This option disables DHCP for this interface. 12. Click Next. The Configure Interface Settings summary page appears. The values listed reflect the new system and interface state. 13. Complete the Interface, click Finish and OK
Modifying a bonded interface
After you create a bonded interface, you can update the settings to respond to network changes or resolve issues.
Steps
1. Select Hardware > Ethernet > Interfaces.
2. In the Interfaces column, select the interface and disable the bonded interface by clicking No in the Enabled column. Click
OK in the warning dialog box.
3. In the Interfaces column, select the interface and click Configure.
4. In the Configure Virtual Interface dialog box, change the settings.
5. Click Next and Finish.
Bonded interface configuration guidelines
Bonded interface configuration guidelines apply to failover and aggregate bonded interfaces. There are additional guidelines that
apply to either failover or aggregate interfaces but not both.
● The virtual-name must be in the form vethx where x is a number. The recommended maximum number is 99 because of
name size limitations.
● You can create as many bonded interfaces as there are physical interfaces.
● Each interface used in a bonded interface must first be disabled. An interface that is part of a bonded interface is seen as
disabled for other network configuration options.
● After a bonded interface is destroyed, the physical interfaces associated with it remain disabled. You must manually reenable the physical interfaces.
● The number and type of cards installed determines the number of Ethernet ports available.
● Each physical interface can belong to one bonded interface.
● A system can support multiple mixed failover and aggregation bonded interfaces, subject to the restrictions above.
● Bonded interfaces must be created from identical physical interfaces. For example, all copper, all optical, all 1 Gb, or all 10 Gb.
However, 1 Gb interfaces support bonding a mix of copper and optical interfaces. This applies to bonded interfaces across
different cards with identical physical interfaces.
● Failover links improve network resiliency.
● Aggregate links improve network performance and resiliency by using two or more network interfaces in parallel, thus
increasing the link speed for aggregated links and reliability over that of a single interface.
● Remove functionality is available using the Configure button. Click a bonded interface in the list of interfaces on the
Interfaces tab and click Configure. From the list of interfaces in the dialog box, clear the checkbox for the interface to
remove it from bonding (failover or aggregate), and click Next.
● For a bonded interface, the bonded interface is created with remaining secondary interfaces if the hardware for a secondary
interface interface fails. If all the secondary interface fail, the bonded interface can no longer send and receive network
traffic. This secondary interface hardware failure will generate managed alerts, one per failed secondary interface.
NOTE: The alert for a failed secondary interface disappears after the failed secondary interface is removed from the
system. If new hardware is installed, the alerts disappear and the bonded interface uses the new secondary interface
after the reboot.
● On DD3300, DD4200, DD4500, and DD7200 systems, the ethMa interface does not support failover or link aggregation.
Guidelines for configuring a bonded interface for link aggregation
Link aggregation provides improved network performance and resiliency by using one or more network interfaces in parallel, thus
increasing the link speed and reliability over that of a single interface. These guidelines are provided to help you optimize your
use of link aggregation.
● It is recommended that you make interface changes only during scheduled maintenance downtime even though routing rules
and gateways are reapplied after interface changes. Verify the routing configuration is still correct after making interface
changes
● Enable aggregation on an existing bonded interface by specifying the physical interfaces and mode.
● Bring up the bonded interface and make sure an IP address is on the interface or an associated interface. The bonded
interface may have VLANs and or aliases on it, each with an IP address, and therefore does not need an IP address directly
on it to be fully functional.
● 1 GbE and 10 GbE interfaces cannot be aggregated together.
● 1 GbE copper and optical interfaces can be aggregated together.
● 10 GbE copper and optical interfaces cannot be aggregated together.
Guidelines for configuring a bonded interface for failover
Link failover provides improved network stability by identifying backup interfaces that can support network traffic when the
primary interface is not operating. These guidelines are provided to help you optimize your use of link failover.
● A primary interface can be specified as part of the failover. If a primary interface removal is attempted from a failover, an
error message appears.
● When the main secondary interface is used in a failover configuration, it must be explicitly specified and must also be a
bonded interface to the bonded interface. If the primary interface goes down and multiple interfaces are still available, the
next interface is randomly selected.
● All interfaces in a bonded interface must be on the same physical network. Network switches used by a bonded interface
must be on the same physical network.
● The recommended number of physical interfaces for failover is greater than one. You can, however, configure one primary
interface and one or more failover interfaces.
https://www.dell.com/support/kbdoc/en-us/000206148 Configuring a VLAN and IP Alias with Graphical User Interface (GUI)