IBM License Metric Tool (ILMT)

IBM License Metric Tool (ILMT)

Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems.

 View Only

  • 1.  Clarification on ILMT silent install (disconnected with ansible, no BigFix).

    Posted Mon December 18, 2023 05:56 PM
    Edited by Demian Phillips Mon December 18, 2023 06:48 PM

    Doing my best to follow documentation on this.
    IBM documentation and IBM youtube seem to imply if doing a disconnected scanner with ansible setup we do not use BigFix.
    We are monitoring a virtual datapower on vmware which can not have BigFix installed on it.
    We are using a RHEL 8 headless server setup (no gui) so wish to perform a silent install, reading through the install_response.txt seems to imply I can skip BigFix, but I also have to set up a number of BigFix specific variables anyway.
    Assuming I am using defaults for everything but the account names and passwords, what items do I need to set for this scenario?

    I also have a question about the size of the DB2 install as it installs to /opt but non of the documentation tells me what minimum size I need for that filesystem.


    All I can find is a few simple tutorials for installing using the GUI and nothing on doing silent non-BigFix.

    I've been trying to resolve issues with running the installer but it seems to be bone headed/buggy.

    Firs it wants /tmp to be executable which we have to be CIS hardened and requires noexec on /tmp so I did what the installer said and exported IATEMPDIR=/var/tmp then re-ran the installer, it still dies with the error about /tmp even with the variable in root user running env (no sudo used for install).
    In the install logs made in /root homedir I see it calling out /tmp being noexec still as well.
    I also see where it wants if failing because we do not have I686 packages installed on ax86_64 system (this breaks things)
    "2023:12:18-18:36:48 - err - com.ibm.license.mgmt.install.ia.silent.PrereqCheckSilent.doInstall - CODIN0525E The following RPM packages are required for this installation:
       - libstdc++*i686
       - numactl*x86_64
       - binutils*x86_64
       - pam*i686"

    RPM output for each of the packages mentioned above
    libstdc++-8.5.0-20.el8.x86_64
    numactl-libs-2.0.16-1.el8.x86_64
    binutils-2.30-123.el8.x86_64
    pam-1.3.1-27.el8.x86_64

    ------------------------------
    Demian Phillips
    ------------------------------



  • 2.  RE: Clarification on ILMT silent install (disconnected with ansible, no BigFix).

    Posted Mon December 18, 2023 06:52 PM
    Edited by Demian Phillips Mon December 18, 2023 07:01 PM

    I see my mistake on numactl, only the libs were there.
    fixed that.
    I also installed all the i686 (previous versions of RHEL have gotten unhappy) but it looks like now this is how you get 32 bit packages.

    Guess we will have to break compliance and enable /tmp or hack the installer to not lose the alt-temp location.



    ------------------------------
    Demian Phillips
    ------------------------------

    Original Message


  • 3.  RE: Clarification on ILMT silent install (disconnected with ansible, no BigFix).

    Posted Mon December 18, 2023 07:36 PM

    Determined /opt needs at least 6.2GB free space for install.

    There is an gotchya where if you define one of the passwords that the install_settings.txt says you must define or it will abort. If you install without BigFix it errors that it must be commented out.The error message also gives you the wrong variable to comment out (the one in the error message does not exist) but a close enough one does and after I commented that one out it was able to continue past that error.



    ------------------------------
    Demian Phillips
    ------------------------------

    Original Message


  • 4.  RE: Clarification on ILMT silent install (disconnected with ansible, no BigFix).

    Posted Mon December 18, 2023 07:37 PM

    Finally
    CODIN0505I The installation finished successfully. To complete the remaining configuration steps, go to the following URL: https:XXXXXXXXXXXX

    I hope some of the fun I ran into and got around helps someone else in the future.



    ------------------------------
    Demian Phillips
    ------------------------------

    Original Message


Related Content