To add entries to a IP Route Table, you need to Display the Table. If the table has insufficient rows, you will need to Specify the Table Size.
You need to add a route entry for each non-local IP address to which a SCADAPack E outstation is to transfer data. There is no need to include entries for IP addresses that are on the same local subnet as the outstation, as data packets will be automatically forwarded to those addresses.
For greatest efficiency, order the entries in a IP Route Table so that routes that are used the most often appear at the top of the table, in priority order (Host, Network, Gateway, and then Default-Gateway). This allows the outstation’s TCP/IP stack to quickly locate the routes that it is to use to transfer most incoming IP data packets.
The entries that you specify in an IP Route Table are persistent (that is, they are retained when the outstation restarts). Any routes that are added using the diagnostic ROUTE command or ISaGRAF function blocks are non-persistent (that is, they will be discarded when the outstation restarts). See the outstation documentation for details on the ROUTE command and ISaGRAF function blocks.
Downloading an IP Route Table to a SCADAPack E outstation will cause a Cold Reset and therefore the loss of any dynamic entries in a table.
Geo SCADA Expert automatically allocates a unique Index number to each entry in an IP Route table. For each entry in the table, you need to specify:
- Destination IP Address—The IP address of the host that matches the destination address of the TCP/IP packets sent by the outstation. The address is used in conjunction with the Subnet Mask to identify a range of target host IP addresses. Leave this field blank (defaults to 0.0.0.0 when saved) for Default Route entries.
Example:
192.186.1.0
- Destination Subnet Mask—The Subnet Mask is used in conjunction with the Destination IP Address to identify either a single host address, or a range of host addresses (a subnet). Leave this field blank (defaults to 0.0.0.0 when saved) for Default Route entries.
Example:
255.255.255.0
- Destination Port—The outstation Port via which the IP packet is to be sent. Use the combo box to select the required port.
If you select a serial port, ensure that the Port Function for that port is set to PPP/TCPIP (see Configure the Properties of the Individual Ports).
- Gateway IP—The IP address of the host that provides the ‘gateway’ to the target host. Leave this field blank (defaults to 0.0.0.0 when saved) for non-gateway routes.
Example:
192.168.0.1
The Gateway IP address has to be on the same subnet as the outstation’s interface for the corresponding route. For example, if the Ethernet 1 interface is configured with an IP address of 192.168.0.1 and a subnet mask of 255.255.255.0, the gateway address could be 192.168.0.2, but cannot be 192.169.0.1
- Metric—Use to determine the route priority when multiple paths exist for interconnecting IP Hosts. The higher the number, the lower the priority. Set the entry to zero to apply the default metric value for a particular type of route (for example, PPP interfaces tend to have a higher metric and therefore a lower priority than Ethernet interfaces).
For an example that illustrates how the different route types (Host, Network, Gateway, and Default-Gateway) might be configured, see Types of IP Route.
Use the IP Route Table field on the DNP3 SCADAPack E Outstation Form’s SCADAPack TCP/IP tab to associate the table with a particular outstation (see Specify IP Route and BOOTP Tables).