IOEP01710A DFSKERN fails initialization

Configuration error.
This error can be caused by many things. It is a configuration error.

Some things to check are

1- that you ran the dfs_cpfiles script, which populates the file system
with the various configuration and envar files

/opt/dfsglobal/scripts/dfs_cpfiles
This process is documented in the SMB Admin Manual in the section on post SMPE installation processing.

2-The reason code 1026 typically indicates an error with the
DFS/SMB socket service and communication between the daemons that
DFS/SMB uses.
There are a number of daemons that make up the DFS/SMB product. In each of the configuration files for these daemons, you need to verify that the value of the envar DCE_START_SOCKET_NAME in each process envar file is the same.
These files would be:
---
/opt/dfslocal/home/dfscntl/envar
/opt/dfslocal/home/dfskern/envar
/opt/dfslocal/home/dfsexport/envar
---
In each of these files, you want a statement that is EXACTLY like this:

DCE_START_SOCKET_NAME=/opt/dfslocal/home/dfscntl/ioepk.soc

The path in all 3 files needs to point to the same place.
These 3 daemons use this file to get the socket to communicate between themselves.
Can you check that this envar value is the same in all 3 files?

3- This could also be an issue with symbolic links (which we use) /opt/dfslocal MUST be a symlink to /etc/dfs

If somehow your symlinks became incorrect, you could also have problems like this.

You can check this one link with a ls -al command


DCESVPI:/opt/ > ls -al /opt/dfslocal
lrwxrwxrwx 1 STC1 SYS1 10 Sep 17 15:01 /opt/dfslocal ->
../etc/dfs

Then, you can confirm it by issuing cd /opt/dfslocal
This should put you into /etc/dfs
If it doesn't, that is wrong.

We ship a job that will non-destructively check and correct symlinks.
The job is IOEISMKD.


Of the above, #2 is the most common cause.