IBM Guardium

IBM Guardium

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

Exadata DB host is not visible in Guardium collector after installing the STAP 11.4

  • 1.  Exadata DB host is not visible in Guardium collector after installing the STAP 11.4

    Posted Thu September 05, 2024 03:20 AM

    Hi All,

    Exadata DB host is not visible in Guardium collector after installing the STAP 11.4. There is no error showing the GIM event list as well at the server end. KTAP showing installed. All the required processes are running properly. Exadata server running linux version 7. We installed the exact match of bundle as kernel version. what could be the reason. Please suggest asap on urgent basis. Thanks

    Raj

    Raj.Raj@ibm.com



    ------------------------------
    Raj Kumar Bhatia

    Raj.Raj@ibm.com
    ------------------------------


  • 2.  RE: Exadata DB host is not visible in Guardium collector after installing the STAP 11.4

    Posted Mon September 09, 2024 10:00 AM

    Hello Raj,

    This post might be a bit late if you needed urgent assistance. Wondering if you got it to work and what was the problem.

    In any case, here's a couple of items to check:

    • ·       Confirm that SQLGUARD_IP is pointing to the correct collector
    • ·       Verify that traffic is allowed from the DB Server to the collector: from the DB server, you may run telnet <collector> <16016 or 16018> (https://www.ibm.com/docs/en/gdp/11.4?topic=system-guardium-port-requirements)
    • ·       Check central_logger.log messages
    • ·       Check STAP.log messages
    • ·       Run STAP diag for clues on the problem (https://www.ibm.com/docs/en/gdp/11.4?topic=support-must-gather-unix-linux-s-tap)


    ------------------------------
    Marcio Bulek
    ------------------------------



  • 3.  RE: Exadata DB host is not visible in Guardium collector after installing the STAP 11.4

    Posted Fri September 27, 2024 08:53 AM

    Hi Raj,

    This issue may be related to network access or sniffer service. You should check some steps like below:
     
    - Check the guard_tap.ini file for the collector IP address. If the IP address is incorrect, fix it and restart the guard_gsvr service. service guard_gsvr restart
     
    -Check the netstat -an|grep 16016 and netstat -an|grep 16018 outputs. If the outputs show SYN_SENT, and then check the firewall rules, you must define the permit rules for the S-TAP to the collector connectivity
     
    -Check sniffer service on the collector, if sniffer service is not running on the collector the S-TAP cannot connect properly. Please connect with the CLI user via SSH, and run the restart inspection-core command.
    Kindly Regards.


    ------------------------------
    Veysel Gundogdu
    ------------------------------