Data Expedition, Inc.

Move Data Faster


Tech Notes
Configuring Firewalls
Vista Firewall
License Binding
Anon. Win32 servedat
Windows 7 Firewall
Amazon Web Services
NAS Authentication
Diagnostic Logging
Load Balancing

Amazon Web Services

Tech Note History
Aug012016Linux UUID Access
Nov242015Linux VMID/UUID
Jun222015Azure VMID/UUID
Sep082014Clarify Private IP
Oct302013EC2 Update
Nov302012Irix Correction
Mar232011AWS EC2
Jan112011Virtual Machines
Nov302009Clarified IP binding
Sep082009Clarified migration process
Oct272008Add AIX Host ID
Jul252008Clarified private addresses policy
May212007First Post

MTP/IP License Binding

Most MTP/IP applications are licensed on a per-server basis.  You must provide host identification for each server you are licensing using one of the types below.

Host bound licenses will not function without a host identifier.
DEI is not responsible for delays caused by your failure to provide correct binding information.

Fixed IP Address (IP)

You may choose almost any static, unicast IP address.  The bound MTP/IP license will work with the host which has that address assigned to its primary network interface card (NIC).  This allows you to completely change the host hardware, without disruption to your MTP/IP license.

The IP address you provide for binding must be assigned to an active network interface of the system that is actually running the MTP/IP software.  Do not use the address of a router, virtual host, or other device.  Under Windows, you can see a list of available addresses by running the console command "ipconfig /all".  On all other systems, type the shell command "ifconfig -a" from an administrative or root account.

If the system is behind an NAT gateway or firewall, you must use the static, private address of the host itself.  If a static IP address cannot be used, then you may need to use a machine identifier instead.

Addresses which are reserved for uses other than unicast routing are not permitted.  Private addresses matching the following patterns are not permitted: 10.0.*.0, 10.0.*.1, 10.0.*.2, 192.168.*.0, 192.168.*.1, 192.168.*.2, 172.16.*.0, 172.16.*.1, 172.16.*.2, 127.0.0.*, 0.0.0.*.

Machine Identifier (MAC)

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 migrate the license as described below.  Machine identifiers must be unique.

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

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

Amazon Web Services Elastic IP (EIP)

Licenses which are deployed on AWS EC2 instances may be bound to an Elastic IP address assigned to that instance.  The software license may be moved to a new instance by reassigning the Elastic IP address to that instance.  See Tech Note 0025 for more about using MTP/IP software with Amazon Web Services.

Amazon Web Services Instance ID (IID)

Licenses which are deployed on AWS EC2 instances may be bound to the Instance ID number of that instance.  The Instance ID remains constant across stops and starts, but if you terminate the instance you will need to migrate the license to a new host as described below.  See Tech Note 0025 for more about using MTP/IP software with Amazon Web Services.


Windows and Linux systems can be bound to the host hardware UUID on platforms which support it.  This allows binding to a Microsoft Azure VMID as well as the UUID of other virtual machines and hardware.  VMIDs are persistent across starts and shutdowns of a virtual machine, but if you delete a VM you will need to migrate the license to a new host as described below.  On most Linux systems, the UUID can only be accessed by processes running as root.

To Be Determined (TBD)

If the host binding for a license is not known at the time of purchase, mark that license as "TBD".  You can complete the binding process at a later time, but remember that the server software will not run until you do so.  If you expect there to be a long delay between your purchase and when the binding is available, notify your sales representative so that your support term can be adjusted.  This can be useful if you wish to pre-purchase licenses for rapid deployment at a later time.


During the term of an active support contract for a given host license, you may make occasional changes to the software host binding.  This may be done a reasonable number of times to facilitate changes in your network infrastructure.  It is not permitted as a substitute for acquiring multiple host licenses where needed.

Updating the license binding will require that you download new software executables from your customer website, and that you certify removal of the software from the old host.  You must have a current technical support contract to update your license bindings.  Contact your customer service representative to obtain a Host Migration request form.