To use TCP/IP, make sure you have the following components:
- Microsoft Windows installation disks or CD-ROM and documentation.
- Network adapter, drivers, and cabling.
For detailed information, refer to the online Help that came with your Microsoft Windows operating system.
In addition to the components you need to get started, you need do the following:
- Map the names of each SCADA server IP addresses.
- Verify the communication ports that FIX will use.
- Configure TCP/IP.
- Enable the TCP/IP protocol in the SCU.
The following sections provide guidelines for completing these tasks. Refer to your TCP/IP manuals for additional configuration information.
Mapping IP Addresses
To use a TCP/IP network with iFIX, each SCADA server must be mapped to unique IP addresses. This process is called name resolution, and TCP/IP vendors handle this in many different ways. You need to decide which method of name resolution is appropriate for your site. This section provides guidelines to help you reach that decision.
TCP/IP software can handle name resolution using the following:
- A local HOSTS file.
- DNS (Domain Name System).
- DHCP/WINS (Dynamic Host Configuration Protocol and Windows Internet Naming Service).
It is recommended that you use a local HOSTS file since this method has provided the highest reliability during our testing. More information on using a local HOSTS file is included in the section Using a Local HOSTS File.
If your company currently uses DNS servers, this option can be implemented since DNS servers are based on HOSTS files.
Using a Local HOSTS File
The HOSTS file provides mapping between node names and IP addresses. This text file is stored locally on each node. The contents of the HOSTS file should be identical on each node in your TCP/IP network. All FIX SCADA servers must be in the HOSTS file.
NOTE: You cannot save the HOSTS file unless you are an Administrator (in the built-in Administrator user group).
The syntax of the HOSTS file is as follows:
address HOSTNAME
Address — defines the IP address of the node.
Hostname — defines the iFIX node name, as specified in the SCU. The node name must be in uppercase and is limited to eight characters.
An example of an entry in the HOSTS file is as follows:
198.212.170.4 SCADA01
You can also provide an alias name for the host name as an optional third parameter.
TIP: A common mistake made when creating the Hosts files is leaving an extension at the end on the file name. For example: HOSTS.txt or HOSTS.doc. Do not include a file extension. The name of the file used by the operating system is: HOSTS.
Using DNS Servers
A DNS server is a HOSTS file stored on a server. This configuration is easier to administer than local HOSTS files since any changes to the HOSTS file need to be made only once. However, a single DNS server can be a single point of failure should it fail to respond. If avoiding a single point of failure is important to you, consider doing one of the following:
- Reverting back to local HOSTS files.
- Implementing redundant DNS servers.
Using DHCP/WINS
When using iFIX with DHCP, you also need to use WINS. The local host name must be the same as the iFIX node name. Refer to your Microsoft documentation for more information on setting up DHCP and WINS.
Verifying Port Assignments
By default, iFIX uses the following port:
FIX2010/tcp
You should not have to change this setting. If the number is used by another application on your node, you must edit or create a SERVICES file. The SERVICES file defines the port used by each TCP/IP application.
To define unique port numbers for iFIX, refer to your TCP/IP manuals for instructions on locating and editing the SERVICES file. Make sure, when you edit the file, you enter a unique port number for iFIX or change the port number of the conflicting application.
NOTE: The port used for iFIX Database Synchronization is port 53014.
