100 | RMC-100| 2105552MNAE
Table 6-3: User-enabled services on the RMC
Security feature available
Service
Serves connection requests for
secure login shell and file
transfer. Supports connection
requests from third-party
Authentication based on private-public key
pairs, passphrase-protected keys
Software
Update
Enables or blocks the ability of
the device loader to update the
embedded software.
None specific to the service. Must use Bi-
level security passcode or Role-Based
Authentication (Role-Based Authentication,
6.2.2 Open Transmission Control Protocol (TCP) ports
The table below lists the open TCP ports on the RMC. These ports are used for all TCP/IP based
connections which are supported by the Ethernet ports.
Protocols over TCP can be standard like SSH, or proprietary like Totalflow (Remote or Local).
Table 6-4: Open TCP ports on the RMC
Assigned to connections used for device monitoring,
configuration and data collection or polling. PCCU,
WinCCU, TDS and third-party SCADA systems request
Loader/TCP
Assigned to the device loader connections for device
software update.
PCCU requests this type of connection.
Assigned to secure shell (SSH/SFTP) connections.
Third-party SSH/SFTP clients request these connections.
Assigned to connections between the RMC and external
Modbus devices for communication and data transfer
For connections with user-configurable ports, use the default value or assign
a different port number from the range of 1024 to 65534. Connections using non
-default TCP ports
are handled by additional Totalflow/TCP communication or Modbus TCP applications configured with
different TCP ports. For example, the figure below shows an additional Totalflow/TCP application
(named ControlGroup) with a different TCP port (10001).
Figure 6-1: Totalflow/TCP application instance with non-default TCP port
To Next Page
Loading...
Need help?
General
