Network Settings

The default Ethernet interface: Select an available interface, such as eth0, eth1, em1, or em2.

Note

Network Interface names for Ethernet interfaces may vary, such as eth0/eth1/… or em1/em2/…. "None" or Blank indicates that the default interface is not set.

Select either IPv4 or IPv6 to specify the priority for DNS resolution.

On systems with both IPv6 and IPv4 enabled, if users use hostnames instead of specifying IP addresses when creating connections, the default behavior is to resolve to IPv6 first if it is available.

To enable SNMP (Simple Network Management Protocol) alerts for out-of-band monitoring, toggle this button to On.

This starts the SNMP server to query for OS information, such as CPU usage. SNMP alerts are typically used by IT administrators to monitor system health. See Using SNMP with HMP for more details.

Tip

There are no HMP-specific MIBs.

(SNMP must be enabled) Enter the IP address or FQDN of the SNMP server to send SNMP Traps to.

By default ICMP redirect messages are disabled to protect from malicious attacks. You may enable them by checking this box.

The IP Address for the interface. This is a unique IPv4 address that identifies the unit in the IP network.

Note

• If DHCP is disabled, you may enter an IP address in dotted-decimal format.
• If your network uses addresses within the 172.16.0.0/12 range, please contact Haivision Support for additional configuration steps.

This is a 32-bit mask used to divide an IP address into subnets and specify the network’s available hosts.

Note

If DHCP is disabled, you may enter a Network Mask in dotted-decimal format (e.g., 255.255.0.0).

The IPv4 default route to be assigned to the interface. This is the gateway that is used when no other route matches. This address must be reachable on your local subnet.

Note

If DHCP is disabled, you may enter a gateway address in dotted-decimal format.

(Maximum Transmission Unit) Specifies the maximum allowed size of IP packets for the outgoing data stream. 228..1500

Note

If IPv6 is enabled, the MTU value must be at least 1280 octets.

(Bond Interface only) Modes for the Linux bonding driver determine the way in which traffic sent out of the bonded interface is actually dispersed over the real interfaces. Modes 0, 1, and 2 are by far the most commonly used among them.

• Round Robin Sequential: Transmits packets in first available network interface (NIC) slave through the last. This mode provides load balancing and fault tolerance.
• Active Backup: Only one NIC slave in the bond is active at a time. A different slave becomes active only when the active slave fails. This mode provides fault tolerance
• XOR Sequential: Transmits based on XOR formula. (Source MAC address is XOR’d with destination MAC address). This mode selects the same NIC slave for each destination MAC address and provides load balancing and fault tolerance.
• Broadcast – Fault Tolerance: Transmits network packets on all slave interfaces. This mode is least used (only for specific purpose) and provides only fault tolerance.
• IEEE 802.3ad Dynamic Link Aggregation: Creates aggregation groups that share the same speed and duplex settings. Utilizes all slave network interfaces in the active aggregator group according to the 802.3ad specification. This mode is similar to the XOR mode above and supports the same balancing policies. The link is set up dynamically between two LACP-supporting peers.
• (Adaptive) Transmit Load Balancing (TLB): The outgoing traffic is distributed according to the current load and queue on each slave interface. Incoming traffic is received by one currently designated slave network interface. If this receiving slave fails, another slave takes over the MAC address of the failed receiving slave.
• (Adaptive) Active Load Balancing (ALB): This includes balance-tlb + receive load balancing (rlb) for IPV4 traffic. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the server on their way out and overwrites the source hardware address with the unique hardware address of one of the slaves in the bond such that different clients use different hardware addresses for the server.

Select one of the following options to obtain an IPv6 address for the unit:

• Automatic: Uses SLAAC (Stateless Address Autoconfiguration) to obtain IP addresses automatically without the need for a DHCP server
• Automatic (DHCP): Enables the Dynamic Host Configuration Protocol to get an IP address from a DHCP server on the network
• Static: Use to manually configure the device’s IP and gateway addresses.

If Automatic addressing is used, displays the IPv6 Address (with a /128 suffix). This is a unique address that identifies the unit in the IP network.

If Static addressing is used, enter an IPv6 address in hexadecimal notation.

(Automatic addressing only) If SLAAC privacy extensions are enabled, this field displays the temporary IPv6 address. The temporary address changes in accordance with network changes.

(Automatic addressing only) Displays the address assigned by SLAAC for management of the unit using the Subnet Prefix and the interface's MAC address. This is a unique address that identifies the interface/device in the IP network.

If Automatic addressing is used, displays the gateway address of the network (typically the address of the network router).

Note

HMP does not accept automatic configuration via Router Advertisements and the DHCP system must set the gateway via stateful DHCP.

If Static addressing is used, enter a gateway address in hexadecimal notation.

(Automatic addressing only) Check this checkbox to enable SLAAC Privacy Extensions. As documented in RFC 4941 "Privacy Extensions for Stateless Address Autoconfiguration in IPv6", this entails using randomly generated, temporary, global scope IPv6 addresses that are regularly discarded and replaced with different addresses.

Check this checkbox to automatically detect if your IPv6 addresses are duplicates of ones already in use. If so, the IPv6 addresses change to unique addresses. See RFC 4862 "IPv6 Stateless Address Autoconfiguration" for more details.

(Read-only) A link-local address is an Internet Protocol (IP) unicast address intended to be used only to connect to the hosts on the same network. A link-local address starts with fe80: and is always automatically assigned.

Click and fill in the values to add one or more static routes.

Note

A static route cannot be created with a Subnet Mask of either 0.0.0.0 or 255.255.255.255.