Initialization problems

When IKE successfully initializes, message EZD1046I is issued. If the IKE daemon fails to initialize, message EZD1045I or EZD1049I is issued. Common initialization problems include:

The IKE daemon load module is not APF-authorized. The IKE daemon load module must be APF-authorized. The symptom for this problem is the following message: EZD0986I IKE is not APF authorized.
To correct this problem, ensure that the IKE daemon load module is in an APF-authorized library, and then restart the IKE daemon.
IKE cannot create the /var/ike or /var/sock directories. The IKE daemon attempts to create the /var/ike and /var/sock directories at initialization. If IKE cannot create either of these directories, then initialization fails. If this problem occurs, one of the following messages is issued:
```
EZD1045I IKE initialization error : mkdir /var/ike failed
EZD1045I IKE initialization error : mkdir /var/sock failed
```
To correct this problem, ensure that the /var directory is mounted as read/write. Additionally ensure that either the IKE daemon has permission to create these directories or that these directories are already created and that the IKE daemon has access to them. If the problem still occurs, contact IBM® for additional assistance.
If the IKE daemon is configured in FIPS 140 mode, ICSF must be active when the IKE daemon is started. If ICSF is not active, message EZD2017I is issued. To correct this problem, start ICSF and then start the IKE daemon. ICSF must be configured in one of several FIPS operational modes when started.