Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
6 replies Latest Post - ‏2013-03-28T10:05:27Z by SystemAdmin
Javier_Balles
Javier_Balles
25 Posts
ACCEPTED ANSWER

Pinned topic issue collecting data in Report

‏2013-03-26T01:34:15Z |
Hi All,

Has anyone experienced the following issue, I have Server IP Column 0.0.0.1 ?

Best Regards!

Thanks in advance!
Updated on 2013-03-28T10:05:27Z at 2013-03-28T10:05:27Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    483 Posts
    ACCEPTED ANSWER

    Re: issue collecting data in Report

    ‏2013-03-26T15:51:37Z  in response to Javier_Balles
    Is it only on a particular server? How about other server? May I know the OS type and version for the server? What is the DB type and version?

    How about the rest of the information such as DB username, Source Program, Client IP? Is it display correctly?

    What is your Guardium version?
    • Javier_Balles
      Javier_Balles
      25 Posts
      ACCEPTED ANSWER

      Re: issue collecting data in Report

      ‏2013-03-27T17:49:26Z  in response to SystemAdmin
      Hi,

      Well, in this case I just see the ServerIP Column 0.0.0.1 for DB2 and INFORMIX - Server Type.

      For example: I have the next columns:
      SevrIP ClintIP DBUserName SourceProg SrvcName
      0.0.0.1 164.4.121.207 without_data without_data INFORMIX
      0.0.0.1 164.4.121.207 INFORMIX /respaldo/.. DICTCP

      I know the ClientIP 164.4.121.207 is a Local Zone where the S-TAP Agent was installed, and this IP has a Global Zone is where the ServerIP Column reflects 0.0.0.1 and the details of the server are:
      Operating System Solaris - SunOS
      Host OS Version - 5.10
      DBMS - INFORMIX, DB2
      DBMS Version 11.50.FC5 for INFORMIX, v9.5.0.0 for DB2
      Guardium Version-8.2
      Latest patch number:p150

      I would like attached a file with the issue.

      Thank you in advance.

      Best Regards!

      Attachments

      • SystemAdmin
        SystemAdmin
        483 Posts
        ACCEPTED ANSWER

        Re: issue collecting data in Report

        ‏2013-03-28T10:05:27Z  in response to Javier_Balles
        Hi, when you install the STAP on Sun Solaris, are you install in Global zone or local zone? Because for Solaris, you must install the STAP in Global zone and not local zone.

        Do you enable any encryption such as SSL encryption?
  • SystemAdmin
    SystemAdmin
    483 Posts
    ACCEPTED ANSWER

    Re: issue collecting data in Report

    ‏2013-03-27T11:18:04Z  in response to Javier_Balles
    Hi Javier,

    I sometimes face with similar problem, and I add the "Server Host Name" field under Client/Server Entity and see the Server IP in the "Server Host Name", but I do not know the reason actually. If you solve the problem, I also want to know how.

    Best Regards,
    Adem
  • SystemAdmin
    SystemAdmin
    483 Posts
    ACCEPTED ANSWER

    Re: issue collecting data in Report

    ‏2013-03-27T11:18:04Z  in response to Javier_Balles
    Hi Javier,

    I sometimes face with similar problem, and I add the "Server Host Name" field under Client/Server Entity and see the Server IP in the "Server Host Name", but I do not know the reason actually. If you solve the problem, I also want to know how.

    Best Regards,
    Adem
    • Javier_Balles
      Javier_Balles
      25 Posts
      ACCEPTED ANSWER

      Re: issue collecting data in Report

      ‏2013-03-27T17:59:00Z  in response to SystemAdmin
      Hi,

      Well, a partner had similar problems but with Client IP, this is very interesting! For Client IP with 0.0.0.0 you can apply below procedure suggested by IBM support. For Server IP address problems it is a diferent case I do not if it applies.
      1. Amend the guard_tap.ini configuration file manually to include the following two parameters and values.
      KRB_MSSQL_DRIVER_INSTALLED=2

      KRB_MSSQL_DRIVER_NONBLOCKING=1

      (Also KRB_MSSQL_DRIVER_ONDEMAND=1).

      And make sure LHMON_FOR_NETWORK = 1

      2. Re-start the Windows GUARDIUM_STAP service.

      Along with the above please also ensure you have the INSTANCE_NAME

      defined in the inspection engine - please get this value from the

      following sql (run locally on the MSSQL server using Query Analyser) :

      "SELECT @@SERVICENAME" <== the resulting value should be cut and paste

      exactly as is into the inspection engine's "INSTANCE_NAME" field.

      This will solve this kind of issue quite frequently. The settings above may also help with the client IP of 0.0.0.0. This can often be caused by encryption. There is also a field called "Analysed Client IP" that you can try, which will often contain the correct IP address in these cases.

      I hope it helps for you.

      Best Regards!