Connections description file: connections.csv
A connections description file contains the IDs of connections, codes of application-layer protocols, and full network addresses of devices.
The file should begin with header strings containing the data needed for file processing. An example of header strings of the connections.csv file is provided below.
Example:
|
The first three header strings are identical to the header strings in the devices.csv file.
The string Connection;Protocol;Address contains the names of columns with data:
Connection– connection ID for description files.Connection ID is used to link protocols to devices and tags.
Protocol– code of the application-level protocol. The following protocol codes are used:- 0 – MODBUS TCP
- 1 – SIEMENS S7COMM over TCP
- 2 – SIEMENS S7COMM over INDUSTRIAL ETHERNET
- 3 – MITSUBISHI MELSEC SYSTEM Q
- 4 – ALLEN-BRADLEY ETHERNET/IP
- 5 – IEC 61850 MMS
- 6 – IEC 61850 GOOSE
- 7 – IEC 60870-5-104
- 8 – GENERAL ELECTRIC SRTP
- 9 – IEC 61850 SAMPLED VALUES
- 10 – SIEMENS S7COMMPLUS over TCP
- 11 – EMERSON DELTAV
- 12 – OMRON FINS over UDP
- 13 – MMS for ABB AC 800M
- 14 – YOKOGAWA VNET/IP
- 15 – CODESYS V3 GATEWAY over TCP
- 16 – DNP3
- 17 – OMRON FINS over TCP
- 18 – OPC UA BINARY
- 19 – DMS for ABB AC 700F
- 20 – OPC DA
- 21 – OMRON FINS over ETHERNET/IP
- 22 – CODESYS V3 GATEWAY over UDP
- 23 – BECKHOFF ADS/AMS
- 24 – IEC 60870-5-101
- 25 – FOXBORO FCP280 / FCP270 INTERACTION
- 26 – BSAP
- 27 – HONEYWELL CONTROLEDGE 900 INTERACTION
- 28 – WMI INTERACTION
- 29 – HONEYWELL EXPERION INTERACTION
- 30 – MiCOM C264 INTERACTION
- 31 – SCHNEIDER ELECTRIC UMAS
- 32 – TASE.2
- 33 – PROFINET IO
- 34 – DIRECTLOGIC INTERACTION
- 35 – BACNET
- 36 – YARD
- 37 – COS
- 38 – IPU-FEU INTERACTION
- 39 – VALMET DNA INTERACTION
- 40 – CODESYS V2
- 41 – PNU20
- 42 – GENERAL ELECTRIC EGD
- 43 – KNXnet/IP
- 44 – DTS
Address– a string containing the full network address of the device, which is specific to the given protocol.Example:
Connection with the Schneider Momentum controller (one IP address):
"Barline1";0;"IP-Address=192.168.0.7;Port=502"Connection with the Mitsubishi System Q controller (one IP address, two ports):
"Station1";3;"IP-Address=192.168.0.8;Port=5001 Network=0;Station=0;PC=255""Station1";3;"IP-Address=192.168.0.8;Port=5002 Network=0;Station=0;PC=255"Connection with the redundant Siemens S7-400 controller, two controllers (two IP addresses, one set of tags):
"S7$Program";1;"IP-Address=192.168.0.21;Port=102;Rack=0;Slot=2""S7$Program";1;"IP-Address=192.168.0.22;Port=102;Rack=0;Slot=2"The connection with the Siemens S7-400 controller uses two protocols: S7Comm over the TCP/IP stack, and S7Comm over the Industrial Ethernet network (one set of tags):
"S7$Program";1;"IP-Address=192.168.0.21;Port=102;Rack=0;Slot=2""S7$Program";2;"MAC=00:01:02:03:04:05;Rack=0;Slot=2"
The header strings are followed by the file body containing the values of parameters (connection ID, application-level protocol code, full network address of the device). An example of the connections.csv file is provided below.
Example:
|
The format of the device network address in the file connections.csv depends on the type of protocol used.
Example: The following address formats can be used for protocols supported by Kaspersky Industrial CyberSecurity for Networks:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
