4 Replies Latest reply on Jan 20, 2008 10:38 PM by lholling

    Insight manager 7.8.0 upgrade to 7.9.1 after ESX 3.5 upgrade

    fostereprints Novice

      I am running into a small issue on 2 of my older ESX hosts. They were running ESX 3.0.2 and HP insight manager 7.8.0 I upgraded to ESX 3.5 with no issues and insight manager is still working fine. However, insight manager 7.9.1 is now available and I wanted to install it. When I attempted to install it, I get a message stating that I need to remove 7.8.0 first. When I try to run the uninstall script I am presented with an error stating that this version of insight manager is not compatible with this version of ESX. So now I am stuck, I don't have to upgrade, but for compatibility and uniformity I would really like to. Is there any manual removal process for insight manager 7.8.0 which would allow me to bypass the script? Any help on this would be appreciated. Thanks!

        • 1. Re: Insight manager 7.8.0 upgrade to 7.9.1 after ESX 3.5 upgrade
          fostereprints Novice

           

          I found this on HP's website. It is for manually removing insight manager from a linux system. Does anyone know if this will work on ESX? Thanks!

           

          1. Stop the HP Systems Insight Manager daemons:

          2. /opt/mx/bin/mxstop

          3. Verify that the daemons are no longer running:
             
             
                 ps -ef | grep mx 
             
             
                 If any of the HP Systems Insight Manager daemons are running, record the PID and kill the process:
             
             
                 kill -9 pid 
             
             
                 where pid is the PID of the daemon. For example,
             
             
                 kill -9 3456

          4. Remove the HP Systems Insight Manager software:
             
             
                 rpm -qa | grep hpsim | xargs rpm -e

          5. (Optional) If other applications are not using PostgreSQL, you can remove it:

            1. Verify that the daemons are no longer running:

          6. ps -ef | grep post 
             
             
                 If any of the Postmaster/Postgres daemons are running, record the PID and kill all the process: 
             
             
                 kill -9 pid 
             
             
                 where pid is the PID of the daemon. For example,
             
             
                 kill -9 3456

          7. Now remove the PostgreSQL database: 
             
             
                 rpm -qa | grep postgresql | xargs rpm -e 
             
             
                 To remove the HP SIM and PostgreSQL folder:
             
             
                 rm -rf /var/opt/mx /etc/opt/mx /opt/mx /var/lib/pgsql /usr/lib/pgsql /etc/sysconfig/postgresql

          8. Restart the system.

           

          • 2. Re: Insight manager 7.8.0 upgrade to 7.9.1 after ESX 3.5 upgrade
            jhanekom Master

            That looks like a script for removing Insight Manager, not the Insight Management Agents.

             

            It may be an option to look at the "installvm780.sh" installation script for the agents and try to trick it into supporting 3.5.x.  If you open the script and go to line 20, it reads as follows:

            SUPPORTED_VERSIONS="3.0.0 3.0.1 3.0.2"

             

            I'd suggest trying to append 3.5.0 at the end of that string and seeing if that allows you to run it with the "--uninstall" option.

            • 3. Re: Insight manager 7.8.0 upgrade to 7.9.1 after ESX 3.5 upgrade
              fostereprints Novice

              That did the trick. It uninstalled successfully and then 7.9.1 installed successfully. Thanks for the help, I would have never thought it was something so simple as the supported version being text in the script file. Thanks again!

              • 4. Re: Insight manager 7.8.0 upgrade to 7.9.1 after ESX 3.5 upgrade
                lholling Expert

                You could have used the 7.91 script with the --uninstall option and that would have worked fine as well.

                 

                Leonard...

                 

                -


                 

                Don't forget if the answers help, award points