Managing Bandwidth

MTP/IP License Binding

Most MTP/IP applications are licensed on a per-server basis.  The licensing terms generally require that each MTP/IP server license be bound to a specific network host.  The host may be specified using either a fixed IP address or a machine identifier.

Customers must choose which methods best suit their deployment needs and provide the necessary information for each server license at the time of purchase.

Fixed IP Address

You may choose any fixed IP address.  The bound MTP/IP license will work with any machine for which that address is the primary network interface.  This allows you to completely change the machine hardware, without disruption to your MTP/IP license.

Some private address ranges, such as the 192.168 block, may not be permitted.

Host Identifier

The MTP/IP license may be bound to the host identifier of a machine.  The IP address may change, but the software will only run on that specific hardware.  If you acquire new hardware, the software will not run unless you update it as described below.

For Windows, Linux, Mac OS X, NetBSD, and FreeBSD, the host identifier is the MAC/Ethernet address of the machine's primary network interface.  This interface must be available and active when the MTP/IP software is run.

For Solaris, Irix, and HP-UX, the host identifier is the value returned by the system "hostid" command.

Updates

You may make a reasonable number of changes to the IP address or machine identifier by contacting Technical Support.  Updating the license binding will require that you download new software executables from your customer website.  You must have a current technical support contract to update your license bindings.

Exceptions

Exceptions to these restrictions may apply.  Contact a DEI sales representative if you have unusual deployment needs that do not fit with the license binding described here.