Troubleshooting
Problem
Version 9
Unix S-TAP reads only the first 16 port_range definitions in Inspection Engine settings. That is, you can define 16 inspection engines in each of which there is a unique port_range defined. It's a limitation of K-TAP. When K-TAP is used for both local and TCP connections by ktap_local_tcp=0 in guard_tap.ini, K-TAP intercepts TCP connections but it reads only the first 16 port_range definitions and it won't read the 17th or later definitions if it's defined.
Version 10
Unix S-TAP reads only the first 20 port_range definitions in Inspection Engine settings.
[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"8.2;9.0;9.1","Edition":"","Line of Business":{"code":"LOB76","label":"Data Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
05 December 2018
UID
swg21676268