Protocol-Specific Considerations
The following sections are the protocol-specific considerations for Oracle Utilities Live Energy Connect (LEC) v8.0.
ICCP
The ICCP protocol (IEC 60870-6/TASE.2) is based on MMS (ISO 9506) and allows for client and server roles. ICCP and MMS allow for TCP/IP connections to be inbound, outbound, or both, irrespective of the client/server role. The default MMS IP port is 102.
By default, the LEC Server listens on localhost:102. To override this when it is required to allow an inbound connection, the following command line modification must be added (through the Extra params field in the LCM Server tab): /listen=<interface>. For example, /listen=192.168.1.1. You can specify 0.0.0.0 to listen on all local interfaces. See the Oracle Utilities Live Energy Connect Configuration Manager User Guide for more information.
MMS TCP/IP port 102 connections and traffic must be allowed between the LEC system and any configured ICCP peers, based on the connection inbound/outbound configurations.
DNP3
DNP3 (IEEE 1815) is a protocol that uses TCP/IP or UDP/IP as a transport layer. LEC Server can be configured to accept inbound connections, make outbound connections, listen for inbound UDP messages, and send outbound UDP messages.
DNP3 is an unsecured protocol that offers no encryption nor authentication, and therefore must only be enabled for use on a secure operating network. DNP3 also uses configurable IP ports. TCP/IP connections and traffic must be allowed between the Server machine and any configured DNP3 master/outstation (client/server) peers based on connection inbound/outbound configurations.
2030.5
2030.5 is a REST-based networking protocol for transmitting control messages to and status messages from aggregators and other systems important to renewable power generation. The Oracle Utilities Live Energy Connect v8.0 cluster supports a containerized implementation of a 2030.5 server. For secure operation, a NGINX web server is installed on the Oracle Utilities Live Energy Connect v8.0 host machine and configured as a HTTPS reverse proxy to the 2030.5 server running inside the Oracle Utilities Live Energy Connect v8.0 cluster. Current standards for HTTPS security, certificate key length, and other relevant standards should be followed.