HP X.25/9000 User's Guide HP-UX 11i v3 (5900-1523, August 2011)

[x25init] nc open of module x25tun0 failed
CAUSE : Command has returned a bad exiting value
ACTION : Contact your system administrator
[x25init] Starting the X.25 stack failed.
CAUSE : Command has returned a bad exiting value
ACTION : Contact your system administrator
[x25init] Configuration initialization failed
Cause:
The x25tun kernel module is set to “unused” state.
This can be verified by executing the kcmodule command as shown:
# kcmodule x25tun
An output similar to the following is displayed:
Module State Cause Notes
x25tun unused loadable, unloadable
Verify if the State column has the value listed as "unused".
Solution:
Set the x25tun module state to “loaded” as shown:
# kcmodule x25tun=loaded
An output similar to the following is displayed:
Module State Cause Notes
x25tun (before) unused loadable, unloadable
(now) loaded explicit
Now rerun the kcmodule command:
# kcmodule x25tun
The output displayed will be similar to the following:
Module State Cause Notes
x25tun loaded loadable, unloadable
The State column value is changed to "loaded".
Issue 2
Symptom:
After executing the x25init command to initialize the XOT interface, an X.25 application may
fail and the x25ifstate -d /dev/x25_xot0 command displays the following message:
x25ifstate: X.25 interface present, but not up (OFF)
Causes and Solutions:
Following are the possible causes and the corresponding steps to handle them:
1. Cause:
Arguments passed to the x25init command while initializing the XOT interface are missing
absolute pathnames.
Solution:
Check if the arguments passed to the x25init command have the absolute pathname.
An example for absolute pathname: /etc/x25/x25init_xot_def.
54 Configuration