Cleaning up a failed or corrupt Network and Systems Management (NSM) r11.0 installation on Linux


Article ID: 49698


Updated On:


CA Unicenter NSM



If the installation of the Network and Systems Management (NSM) R11.x fails on a Linux system, the following steps may be required to completely remove the failed installation, as in some cases the failed installation leaves behind files and configurations that may conflict during reinstall.

In some cases install will fail, which may remain some of the files or uninstall will not remove NSM completely. In such cases you can run the below cleanup steps to completely remove the NSM from the box.


Network and Systems Management (NSM) r11.x cleanup steps on Linux:

Please note that these are only valid if the box only has NSM r11.0 installed. If any other CA product that utilizes CA Common Services (CCS) component is installed, then following these steps may damage or destroy that product's installation.

  1. Make sure there are no NSM r11.x processes running. If there are, please stop them:

    unicntrl status all (will list the status of all NSM components)
    unicntrl stop all (will stop all NSM components)

  2. Use lsm (or) ./setupNSM to uninstall NSM -

    If we are going to remove all of NSM r11, then it is easier to execute the following lsm command:
    lsm -e UnicenterNSM <-s>

    The <-s> switch is optional and means to perform the uninstall silently. We have to use setupNSM and select the uninstall option if you only want to remove specific NSM components that have been installed. Please note that this lsm command will not work if lsm was not fully installed or the UnicenterNSM package has not been installed. Both of these conditions only happened when there is a problem with the initial NSM r11 install.


    Run ./setupNSM, if the uninstall radio button is available please run this first, otherwise cancel.

  3. Remove all ca-cs-*, ca-unicenter*, ca-ingres*, and ca-lic* rpm packages. The following command identifies the installed CA specific rpm packages:
    rpm -qa | grep " ca-"

    and the following command should be used to remove each rpm package:
    rpm -e <package name> --noscripts --notriggers --nodeps

    for example:
    rpm -e ca-cs-utils --noscripts --notriggers -nodeps

  4. Cleanup the autostart files in the autostart subdirectories under /etc. The following commands will locate all of these files that need to be deleted:
    cd /etc
    find . -name "*CA-*" -a -print
    find . -name "*ingresEI*" -a -print

  5. Clean up the file system:
    rm -rf $CASHCOMP
    rm -rf $CANSM
    rm -rf $AGENTWORKS_DIR
    rm -rf /opt/CA <Or the location where NSM was installed>
    rm -f /.uniovpath
    rm -f /usr/bin/lsm
    rm -f /ca_lic
    rm -f /etc/catngcampath

  6. Remove NSM r11 users/groups if they exist:
    userdel ingres
    groupdel ingres
    userdel nsmadmin
    groupdel nsmadmin

  7. Restore /etc/syslog.conf removing CA specific additions.

    The /etc/syslog.conf might contain the following line which needs to be deleted:

    Once cleaned, recycle the syslogd daemon:
    kill -SIGHUP 'cat /var/run/'

    This kill command will only work on systems where the PID of the syslogd daemon is stored in the /var/run/ file. If this file does not exist, then we have to determine the PID of the syslogd daemon from the "ps -ef | grep syslogd" command and execute "kill -SIGHUP <syslogd PID>" instead.

  8. Clean up the system environment setup scripts, /etc/profile, /etc/csh.login /etc/cshrc, /etc/.login, /etc/login.csh, and .profile in root user's home directory.

    Remove the line(s) added by the NSM r11 install:
    test -r /etc/profile.CA && { CA_SECTION=all; export CA_SECTION; ./etc/profile.CA all; } # Added by Computer Associates\

    setenv CA_SECTION all; if ( -r /etc/csh_login.CA ) source /etc/csh_login.CA all # Added by Computer Associates

  9. Remove the CA specific environment setup scripts:
    rm -f /etc/profile.CA
    rm -f /etc/csh_login.CA

  10. Log out and log back in to make sure the environment is now cleared by running "env | sort" command and verify that none of the NSM environment variables are set (CASHCOMP, CANSM, CAIGLBL0000, AGENTWORKS_DIR, CA_DIA_HOME, etc..)


Release: TNGEXO05500-11.2-Management-for Microsoft Exchange