IBM Guardium

 View Only

  • 1.  Stap-No inspection Engine defined

    Posted Mon July 29, 2024 02:17 PM

    Hi Experts,

    I have integrated two Windows-based databases into a collector. However, after the integration in Stap Control, there is no inspection engine defined. What could be the reason for this? Could you please assist?

    Thanks,



    ------------------------------
    ALBERT A
    ------------------------------


  • 2.  RE: Stap-No inspection Engine defined

    Posted Wed July 31, 2024 03:28 AM

    Hi @ALBERT A,

    Do you mean that Win S-TAP was installed successfully and it's connected to the target collector, and you can see the S-TAP from GUI but you don't see any inspection engine? Please check if inspection engines are defined in Guard_Tap.ini. If you have one or more database instance(s) in the Windows server but nothing is defined in Guard_Tap.ini, check Stap.ctl to see if there is any error in auto discovery. 

    If you have any difficulty in reading the log file, please open a support ticket and send Win S-TAP Must Gather.

    Thanks,
    Satoshi



    ------------------------------
    SATOSHI KAWASE
    ------------------------------

    Original Message


  • 3.  RE: Stap-No inspection Engine defined

    Posted Mon August 05, 2024 01:49 AM

    Hi Albert,
    Greetngs for the day. Hope this finds you well. 

    Do you know if the Windows server has any active database instance(s) on it? 
    Can you please check with your MS-SQL DBA on this? 

    If there are no active databases, then it is correct not to have any I.E defined. In that case, check when the DBAs will be planning to have an instance on the server. 

    If there are active instances,
    A. Did you check if WINSTAP_AUTO_DISCOVERY was set to 0 or 1 during installation?
    B. Is it possible for you to set it to 1 and then push an update on WINSTAP?
    C. Also, from S-TAP Control page of Collector, can you try sending a Command to STAP? (Select Run Database Instance Discovery and please check replace inspection engines and click on Apply)

    Once you update WINSTAP, please refer to STAP.ctl to check if there are any errors. 

    If the above does not help, please raise a case with IBM Support and attach WinSTAP DIAG files. 

    Regards,
    GIRISH



    ------------------------------
    GIRISH RAMESH BABU
    ------------------------------

    Original Message


  • 4.  RE: Stap-No inspection Engine defined

    Posted Mon August 05, 2024 03:01 AM
    Edited by Akash Parmar Mon August 05, 2024 08:30 AM

    Hello all, Good Day! Hope all is well at your side.

    I have a similar Issue around Inspection Engine Configuration where MS SQL Server is in Cluster Environment where we have separate cluster IP/Hostname & port (other than the IP-Port of each Node) on which Database is communicating/listening. In this case, Guardium is able to Identify & discover IE on each node,

    But, For Cluster we need to Manually Configure IE using Cluster IP-Port. STAP Is not discovering & configuring automatically. 

    For this I have even raise case with Support but really not getting any suitable/proper response on this. So, what would you suggest on such case. 



    ------------------------------
    Akash Parmar
    ------------------------------

    Original Message


  • 5.  RE: Stap-No inspection Engine defined

    Posted Mon August 05, 2024 12:20 PM

    Hi Girish,

    Thanks for your Valuable information, as you suggested

    "A. Did you check if WINSTAP_AUTO_DISCOVERY was set to 0 or 1 during installation?"

    this works for me and now I can see the IE. 

    Regards,



    ------------------------------
    ALBERT A
    ------------------------------

    Original Message