SSH Tectia

Upgrading SSH Tectia Manager (Sybase)

This section describes upgrading SSH Tectia Manager version 2.x to version 6.0.

To upgrade SSH Tectia Manager that is using the Sybase database, follow the instructions below:

  1. Stop the Management Server:

    # /etc/init.d/ssh-mgmt-server stop                         
    
  2. Upgrade the Management Server.

    1. On Linux: To upgrade from a previous version of the Management Server, run the following command as root:

      # rpm --upgrade ssh-mgmt-server-<v>-linux-x86.rpm
      

      In the command, <v> is the current release version of the Management Server (for example 6.0.12.123).

    2. On Solaris: To upgrade the Management Server, copy the package to the hard disk to a temporary directory of your choice, uncompress the package, and run the upgrade. Run the following commands as root:

      # cp /cdrom/install/solaris/ssh-mgmt-server-<v>-solaris-8-10-sparc.pkg.Z .
      # uncompress ssh-mgmt-server-<v>-solaris-8-10-sparc.pkg.Z
      # pkgrm SSHmgmtse
       ... answer "yes" to any questions displayed
      # pkgadd -d ssh-mgmt-server-<v>-solaris-8-10-sparc.pkg all
       ... answer "yes" to any questions displayed
      

      In the commands, <v> is the current release version of the Management Server (for example 6.0.12.123).

    The Management Server installation package includes the installation packages for the Management Agents for all supported platforms. There is no need to import them separately to the Management Server machine.

  3. Start the Management Server:

    # /etc/init.d/ssh-mgmt-server start
    

  4. Wait for the database update to finish and login to the Management Server.

    In case of problems, check the system syslog for possible error messages. An environment that is running correctly should always have the Management Database process and the Management Server processes (ssh-mgmt-server and ssh-mgmt-engine) running.

    [Note]Note

    Note specifically that all the modules should be started using the startup script provided, since running the binaries directly will cause the paths and environment to be set incorrectly.

    The process listing should have the following processes after a while:

    # ps -def | grep ssh-mgmt
    
    root     1503     1  0 09:42 ?  00:00:00 ssh-mgmt-server 
    sshmgmt  1504  1503  4 09:42 ?  00:00:10 ssh-mgmt-engine      
    sshmgmt  1530     1  0 09:42 ?  00:00:01 dbeng8 -ga -x none -n ssh-mgmt 
    

    Check that the following syslog messages appear:

    # tail -f /var/log/messages | grep ssh-mgmt-engine
    
    ssh-mgmt-engine[1504]: Database update finished.   
    ssh-mgmt-engine[1504]: SSH Tectia Manager restarted
    
  5. Upgrade the Management Agents to new versions remotely at Software → Management Agent.

  6. Check that all hosts are correctly upgraded to the new version at Reports → Standard reports → Tectia management system reports → Tectia Management Agent versions.