7 Replies Latest reply on Oct 16, 2020 12:21 PM by Stephane Guedon

    Experience TrueSight Upgrade from 11.3.03 to 11.3.04

    Markus Siegenthaler
      Share This:

      Hi all,

       

      I would like to tell you about my experience from upgrading from TrueSight Version 11.3.03 to 11.3.04. Maybe you will see some things that you were not aware of and can help you.

      And if BMC is reading this, they can maybe fix one or the other issue :-)

       

      On our site TSPS is based on Windows, all TSIM's on Linux.

       

      TSPS

      Database Issue:

      On the Test Server the database was corrupted after an additional reboot. This could be fixed with https://docs.bmc.com/docs/TSOperations/11304/truesight-presentation-server-does-not-start-due-to-postgresql-db-unavailability-954648736.html

      No problem on second TSPS

       

      Certificates:

      Also there was an error in the installation log because of the certificates. BMC found out that this is related because the certificate name has been renamed during the time.

      But it works correctly.

       

      TSIM

      Cell migration:

      Earlier the .load Files have been changed during the migration. Customized entries have been removed and also the order of the entries have changed.

      In the meantime this works fine, except for the data .load. BMC did not fix it, even there was a Defect created since 11.3.03

      Our customized entries have been removed. Funny (really?) thing is: the version number in the header has been changed to 11.3.04

       

      If you should have any git related Files/Directories (like for example directory .git or File .gitignore) within the copied cell directory, delete it or you will have an issue. To be honest, we had this problem within version 11.3.03, I did not test this now with 11.3.04

       

      Certificates:

      Same issues like on TSPS because of renamed certificate

       

      That's bad: our certificates Files .cer and .key have been deleted and the corresponding entries in the File /app/sim/tsim/pw/apache/conf/extra/httpd-ssl.conf have been changed to server.crt and server.key. Should not be.

       

      /app/sim/tsim/pw/tomcat/webapps/pronto/WEB-INF/classes/rsso-agent.properties:

      Within this File our settings have been changed during the upgrade from false to true

      # MSP-related flags

      # Flag to show realm-entry-page for the MSP deployments

      msp-deployment=true

      msp-always-show-domain-entry-page=true

       

      /app/sim/tsim/pw/server/etc/statbld.conf:

      Our own settings have been removed during upgrade

       

      app/sim/tsim/pw/tomcat/conf/server.xml:

      Our settings <Connector port="8088" protocol="HTTP/1.1" have been changed to Port 8080

       

      CMDB related:

      Within the File /app/sim/tsim/pw/server/bin/pserver our customized settings for the CMDB Extensions 11.3.03 have been removed (entries for the jar Files that have been deleted below) and the value "ARGS="-Xms256M -Xmx800M $PS_JVM_ARGS -DHomeLocation=$IM_HOME -cp $PS_CP" has replaced our own Memory settings

      And the Files /app/sim/tsim/pw/cmdb/lib/arapi91_build007.jar and arpluginsvr91_build007.jar have been deleted

       

      HealthCheckTool:

      The new HealthCheckTool proposes several new settings that were so far not in the configuration files. From my point of view it would make sense to set those values directly during the upgrade

      BSR:

      That was really good. We had in the past long support cases related to ticketing problems. That works now perfectly, except one small thing (as example for a 3 Cluster Service Modell, if 2 CI's are again ok, all upper CI's UAR's should be closed also. That we could fix with a small change in the outage.mrl

       

      Crontab:

      The cronjob entries like hourlyjobs, dailyjobs and so on have been added again, so the entries are twice there. This problem is already since some versions

       

      Hope it gives you some hints.

      And we will see soon what's missing if there is no more a Operator Console for TSIM

      Take care

      Cheers

      Markus

        • 1. Re: Experience TrueSight Upgrade from 11.3.03 to 11.3.04
          Patrick Mischler

          Hi Markus

           

          Thanks for your insights.

          I only did fresh installations of TrueSight 11.3.04 yet.

          There were some issues but in general the installation was smooth.

           

          One of the more serious issues was an installation issue regarding using Oracle DB 19c for the TSIM database. The company has a policy to set the property sqlnet.crypto_checksum_server in sqlnet.ora on the Oracle server to REQUIRED. The installation faild because the connection to the database was not working. BMC Support suggested to add SHA1 to the property sqlnet.crypto_checksum_types_server in sqlnet.ora. With this setting, we were able to install. But we wanted to get rid of the SHA1 entry in sqlnet.ora. We achieved this by replacing pw/apps3rdparty/jdbc/ojdbc7_patched.jar with pw/apps3rdparty/jdbc/oracle_repo/ojdbc8.jar. After we did this, the TSIM was running fine without SHA1.

           

          Regards,

          Patrick

          1 of 1 people found this helpful
          • 2. Re: Experience TrueSight Upgrade from 11.3.03 to 11.3.04
            avensis david

            Hi, thanks for sharing this information I find it very useful

            • 3. Re: Experience TrueSight Upgrade from 11.3.03 to 11.3.04
              Carsten Lempert

              Hey,

              we made also an upgrade from 11.3.03 to 11.3.04 on windows platform. Everything was fine. We had no problems.

              1 of 1 people found this helpful
              • 4. Re: Experience TrueSight Upgrade from 11.3.03 to 11.3.04
                Stephane Guedon

                Hi

                 

                Done many upgrade on Linux with no issues but:

                1) Take care nslookup is installed

                2) Be sure product is not installed on mount point ( if installed in /opt/tsim/pw you filesystem must be mounted on /opt. If mounted on /opt/tsim, you'll get issues)

                 

                Regards

                2 of 2 people found this helpful
                • 5. Re: Experience TrueSight Upgrade from 11.3.03 to 11.3.04
                  Markus Siegenthaler

                  Hi Stephane,

                   

                  thanks for your information.

                   

                  Also no double entries within the cronjobs for those settings below, I mean on our side it looked like that (this has happend during the last 2 or 3 updates):

                  # the following entry is added for BMC TrueSight

                  ## Changed on Tue Feb  6 10:56:34 CET 2018

                  #

                  #

                  15  * * * * /usr/pw/pronto/bin/hourlyjobs > /usr/pw/pronto/tmp/hrjob.log 2>&1

                  30 3 * * 1-6 /usr/pw/pronto/bin/dailyjobs hosts > /usr/pw/pronto/tmp/dajob$$.log 2>&1

                  30 4 * * 0 /usr/pw/pronto/bin/weeklyjobs hosts > /usr/pw/pronto/tmp/wkjob$$.log 2>&1

                  30 5 * * 0 /usr/pw/pronto/bin/dbarchive > /usr/pw/pronto/tmp/dbarchive7381.log 2>&1

                  0,15,30,45 * * * * /usr/pw/pronto/bin/check_pronetprocs > /usr/pw/pronto/tmp/check_pronetprocs.log 2>&1

                  30 5 * * 0 /usr/pw/pronto/bin/imDataBackup > /usr/pw/pronto/tmp/imDbBackup.log 2>&1

                  30 3 * * 1-6 /usr/pw/pronto/bin/imDataBackupDaily > /usr/pw/pronto/tmp/imDbBackupDaily.log 2>&1

                  0 * * * * /usr/pw/pronto/bin/imStatusChk > /usr/pw/pronto/tmp/imStatusCheck.log 2>&1

                  ## end_pronto -- DO NOT DELETE THIS LINE !

                   

                  # add empty line by TrueSight

                  # the following entry is added for BMC TrueSight

                  ## Changed on Tue Feb  6 10:56:34 CET 2018

                  #

                  #

                  15  * * * * /usr/pw/pronto/bin/hourlyjobs > /usr/pw/pronto/tmp/hrjob.log 2>&1

                  30 3 * * 1-6 /usr/pw/pronto/bin/dailyjobs hosts > /usr/pw/pronto/tmp/dajob$$.log 2>&1

                  30 4 * * 0 /usr/pw/pronto/bin/weeklyjobs hosts > /usr/pw/pronto/tmp/wkjob$$.log 2>&1

                  30 5 * * 0 /usr/pw/pronto/bin/dbarchive > /usr/pw/pronto/tmp/dbarchive7381.log 2>&1

                  0,15,30,45 * * * * /usr/pw/pronto/bin/check_pronetprocs > /usr/pw/pronto/tmp/check_pronetprocs.log 2>&1

                  30 5 * * 0 /usr/pw/pronto/bin/imDataBackup > /usr/pw/pronto/tmp/imDbBackup.log 2>&1

                  30 3 * * 1-6 /usr/pw/pronto/bin/imDataBackupDaily > /usr/pw/pronto/tmp/imDbBackupDaily.log 2>&1

                  0 * * * * /usr/pw/pronto/bin/imStatusChk > /usr/pw/pronto/tmp/imStatusCheck.log 2>&1

                  ## end_pronto -- DO NOT DELETE THIS LINE !

                  # add empty line by TrueSight

                   

                  also no replacement of the certificates?

                   

                  Cheers

                  Markus

                  • 6. Re: Experience TrueSight Upgrade from 11.3.03 to 11.3.04
                    Greg Michael

                    SHA1 should not be available anymore. It is considered vulnerable and has been replaced with SHA256 or higher. If BMC still allows its use, I cannot understand why other than the fact that have been extremely slow to update their encryption and hash algorithms to be something released within the last decade.

                    • 7. Re: Experience TrueSight Upgrade from 11.3.03 to 11.3.04
                      Stephane Guedon

                      Hi

                       

                      Just take care is using URL in events ...

                      See: https://communities.bmc.com/message/889634?et=watches.email.thread#889634

                       

                      No issues with certs on different env as far as cert is managed by F5 device

                       

                      HTH