Skip to main content

Network Settings

The following tables list the configurable Haivision Media Platform Network settings.


Please contact your Network Administrator if you are unsure what to put in any of these fields or if you are unsure whether the setting is required on your network.


HostnameThe hostname to be assigned to HMP. This is a FQDN (Fully Qualified Domain Name); for example,
Default Interface

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


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.

DNS Servers(Optional) The IPv4 addresses of the Domain Name Servers.
Search Domains(Optional) The search strings to use when attempting to resolve domain names.
NTP Server(Optional) If IP address or FQDN of the Network Time Protocol (NTP) server.
Proxy URL(Optional) If your network routes web traffic through a proxy server, enter the proxy server address or port. If required, you may also enter a username and password in the URL as well. For example: user:password@proxyserver:proxyport

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.


There are no HMP-specific MIBs.

Read-Only Community(SNMP must be enabled) Enter the SNMP community string associated with the SNMP Trap Server. This is the string to use when sending a trap to an SNMP Trap server. For example: "Haivision Media Platform".
SNMP Trap Servers

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


If multiple network interfaces are available on your HMP, the settings for each interface are organized within their own tab.

Bond InterfaceBonding enables an administrator to use more than one physical network port as a single connection. This can be used to increase performance or redundancy of a server. See the Bonding Mode entry in this table.
AddressingChoose whether the interface uses a static or dynamic IP address:
IP Address

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


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

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


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


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.


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

MTU(Maximum Transmission Unit) Specifies the maximum allowed size of IP packets for the outgoing data stream. 228..1500
MAC Address(Read-only) The Media Access Control address assigned to the interface. This is the physical address of the network interface and cannot be changed.
LinkSelect the link negotiation settings for the interface, either Auto or Manual. If you select Manual, you can select the Speed (10, 100, or 1000) and Duplex setting (Full or Half).
Bonding Mode

(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.
Slave Interfaces(Bond Interface only) Check this checkbox to select the slave interface(s) to allow the bond interface be the master.

Static Routes



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


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

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.