IP information in SMT

A PI trust can specify IP information about the computer running the PI interface or client application for which you are defining the trust. To collect this information, you can run pidiag -host on the computer where the interface or client application runs. This returns the connection credentials as retrieved from the local operating system.

Note: Using pidiag -host is helpful, but it is not a guarantee of getting the right information, depending on many factors, including the type of interface, the version of the SDK (if SDK-based), and whether there are firewalls / NAT devices in between the interface computer and the Data Archive computer. If you have difficulty configuring the trust, visit the Customer Portal.

• Network Path. The fully-qualified domain name. For PI API, this should match what the Data Archive server thinks based on a reverse-name lookup using the interface's IP address. For PI SDK (1.3.6.x and later), this should match what the client thinks, based on the Windows configuration (you can use pidiag –host on the client to see this information). For example, my_laptop.my_company.com.

• IP Address.

• Netmask. If you specify an IP address, you must also explicitly provide a netmask value. Failure to do so will generate an error. If you require an exact match on an IP address, specify the netmask as 255.255.255.255. If you specify a class C subnet, specify the netmask as 255.255.255.0 and the fourth field of the IP address as 0.

  Note: When applications run on machines with multiple network cards, you cannot predict which credentials the application will send to the Data Archive server for the trust authorization. We thus recommend that you either avoid such configurations, or create a PI trust for every IP address on the machine where the application runs.