The protocol description file contains descriptions of protocols for each connection.
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. Protocol – code of the application-level protocol. The following protocol codes are used: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):
|
Connection with the Mitsubishi System Q controller (one IP address, two ports):
|
Connection with the redundant Siemens S7-400 controller, two controllers (two IP addresses, one set of tags):
|
The connection with the Siemens S7-400 uses two protocols: S7Comm over the TCP/IP stack, and S7Comm over the Industrial Ethernet network (one set of tags):
|
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:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|