If, during the installation process, K-TAP fails to load properly, possibly caused by
hardware or software incompatibility, P-CAP is installed as the default collection mechanism. To
switch to K-TAP, after compatibility issues are resolved, follow these steps.
Procedure
-
Resolve any issues with the K-TAP, such as submitting a module request to IBM or installing
kernel development packages.
Note: If you installed a GIM S-TAP bundle, set
export
GIM_CONTEXT=
Y. For
example:
export GIM_CONTEXT=Y
-
Run the script guard_ktap_loader retry from the ktap
directory:
- shell/RPM installation:guardium/guard_stap/ktap/current
- GIM installation: modules/KTAP/current
If K-TAP loads successfully, the guard_tap.ini parameter
ktap_installed
is automatically set to 1 (yes).