z/OS Communications Server: IP Programmer's Guide and Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Local IPSec NMI: Connecting to the server

z/OS Communications Server: IP Programmer's Guide and Reference
SC27-3659-02

For an application to use this interface, it must connect to the AF_UNIX stream socket provided by the IKE daemon for this interface. The socket path name is /var/sock/ipsecmgmt. You can use the Language Environment® C/C++ API or the UNIX System Services BPX Callable Assembler services to create AF_UNIX sockets and connect to this service.

When an application connects to the socket, the IKE daemon sends an initialization message to the client application. When the IKE daemon closes a client connection (reasons for doing so include severe errors in the format of data requests sent by the application to the IKE daemon, or IKE daemon termination), the IKE daemon attempts to send a termination message to the client before closing the connection. Both the initialization and termination messages conform to the general response message structure used by the IKE daemon to send data to the application (see IPSec NMI request/response format).

The initialization message contains only a message header (see IPSec NMI initialization and termination messages). The version number reported in the message header indicates the maximum version of the interface supported by the IKE daemon. After the initialization message has been received by the client, the client can send requests for IPSec management data to the server.

Result: The IKE daemon does not send an INIT message to the client application until it has successfully connected to the Policy Agent.

The termination message also contains only a message header (see IPSec NMI initialization and termination messages). The message header contains a return code and a reason code that indicates the reason for terminating the connection.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014