Serial IP transport using the Local Host Entity Manager

Overview

Serial transport over raw sockets can be either between two 7705 SAR NEs (one at an RTU and one at the controlling unit), or between a 7705 SAR NE and another NE such as a 7750 SR. These types of local-hosts do not require a 7705 SAR NE or any IP transport services to be configured. These would typically be 3rd party devices such as FEPs, SCADA controlling units, other terminal servers, or other devices not managed by the NFM-P.

For IP transport, the remote-host can be one of the following:

1. For a 7705 SAR NE, the remote-host can be another local-host IP that belongs to a different site in the same service.

2. For a non-7705 SAR NE, the remote-host can be another IP address that is globally reachable to the NE (via routing), but does not belong to the same service.

To facilitate adding remote-hosts to an IP transport, the Local Host Entity Manager is used. The Local Host Entity Manager lists the following:

• All local-hosts from all services/sites managed by the NFM-P, called discovered entries.

• A list of user-created global host entries called global entries.

When an NE is managed by the NFM-P, it checks the NE for all configured IP transports. The local-host details (IP Address and Port Number parameters) from all of the IP transports are populated in the Local Host Entity Manager. The remote-host details are not populated.

When the local-host entries are populated in the Local Host Entity Manager, you can click the Add Remote Hosts button on the IP Transport Remote Host Properties form which will list all possible entries from the Local Host Entity Manager that are valid remote-hosts for a particular local-host.