IBM Support

STAP verification fails when non-default eth port is configured using IBM Security Guardium

Troubleshooting


Problem

STAP verification fails with zero failed checks when non-default eth port is configured

Symptom

STAP verification fails with zero failed checks.

Cause

This may be caused by a non-default eth port being used to communicate with database servers. By default eth0 is used to communicate. If another port, such as eth3, is used to communicate verification may fail although there are zero failed checks.

Resolving The Problem

This is a known issue in version 9GPU 300 and GPU 500. The issue is resolved in GPU 500 in patch 530. If a fix is required for GPU 300 please contact support to obtain ad-hoc patch 348.

[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"}],"Version":"9.1;9.5","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg21969844