Message Reference
ETCA—TCP/IP Connection Establish
When a connection to a service running on a node is permitted, this message is generated.
Table 29: ETCA—TCP/IP Connection Establish Fields
Code | Field | Description |
|
|
|
SEID | Service Identifier | The unique identifier of the service to which the connec- |
|
| tion was established. |
|
|
|
CNDR | Connection | Indicates whether the connection was opened by the grid |
| Direction | node or by a remote host: |
|
| |
|
| nected to the node |
|
| |
|
| connected to a remote host |
|
|
|
SVIP | Destination Service | The port the connection was established to. |
| Port |
|
|
|
|
DAIP | Destination IP | The IP address the connection was established to. |
| Address |
|
|
|
|
SAIP | Source IP Address | The IP address the connection was established from |
|
| (local IP address). |
|
|
|
CNID | Connection | The unique identifier of the connection. |
| Identifier |
|
|
|
|
RSLT | Result Code | Connection status: |
|
| |
|
|
|
This audit message means an incoming or outgoing TCP/IP connection was successfully established. This does not indicate the corresponding user was permitted to use the service - just that they were not rejected. Typically, each service implements additional authentication mecha- nisms specific to the service type (DICOM, HTTP etc.).
This message can be used to report on external hosts communicating with the system, and to correlate higher level protocol messages back to the IP address initiating the activity. The “Connection Identifier” field allows correlation of audit messages related to actions performed during a session.
37
HP Medical Archive