Installation and Setup Guide for Resource Manager Essentials 3.5 on Solaris (With LMS 2.2/RWAN 1.3)
Troubleshooting the Installation
Downloads: This chapterpdf (PDF - 311.0KB) The complete bookPDF (PDF - 1.54MB) | Feedback

Troubleshooting the Installation

Table Of Contents

Troubleshooting the Installation

Logging In After Upgrading

Microsoft Internet Explorer

Netscape Navigator

Understanding Installation Messages

Installing Syslog Analysis

Failure to Delete a Package During Uninstallation

Accessing the CiscoWorks Server

Verify the Server Is Running

Proxy Server Problems

Daemon Manager Not Running

Viewing Process Status

Browser Problems

Improving Server Performance

Frequently Asked Questions


Troubleshooting the Installation


This appendix provides troubleshooting information for Resource Manager Essentials (Essentials) installation and setup. It contains these sections:

Logging In After Upgrading

Understanding Installation Messages

Installing Syslog Analysis

Failure to Delete a Package During Uninstallation

Accessing the CiscoWorks Server

Viewing Process Status

Browser Problems

Improving Server Performance

Frequently Asked Questions

Logging In After Upgrading

If the Login Manager dialog box on the CiscoWorks desktop does not appear correctly when you try to log in for the first time after upgrading, clear your browser cache as follows, then reenter the server URL in your browser.

Wait for a few seconds after the server starts before logging in. If you have trouble logging in, use the Reload button on your browser.

Microsoft Internet Explorer


Step 1 Select Tools > Internet Options.

The Internet Options dialog box appears.

Step 2 Select the General tab.

Step 3 Click Delete Files, then click OK in the Delete Files dialog box.


Netscape Navigator


Step 1 Select Edit > Preferences.

The Preferences dialog box appears.

Step 2 Select Advanced > Cache.

Step 3 Click Clear Memory Cache, then click OK in the Memory Cache dialog box.

Step 4 Click Clear Disk Cache, then click OK in the Disk Cache dialog box.


Understanding Installation Messages

The messages that might appear during installation are:

Information messages, which give you important details

Warning messages, which tell you that something might be wrong with a particular process, but the process will complete

Error messages, which tell you that a particular process could not complete

All messages that appear during installation are logged in the /var/tmp/ciscoinstall.log file.

Table B-1 shows messages that might occur during installation and describes their reasons.

Table B-1 Installation Messages 

Message
Reason for Message
User Action

Base package did not install. Exiting.

Installation program cannot install a required package.

Contact your technical support representative.

Cannot backup /etc/services, no change will be made.

Installation program cannot make a copy of /etc/services before modifying it.

Make sure there is enough space in /tmp.

Cannot change ownership of library. Exiting.

Installation program cannot write to product root directory.

Check the permissions on the directory you specified.

Cannot create directory.

Installation program cannot write to the directory you specified.

Check the permissions on the directory you specified.

Cannot create symlink: ln -s root /opt/CSCOpx.

Installation program cannot create a link from /opt/CSCOpx to the product root directory you specified.

Contact your technical support representative.

Cannot determine the Essentials version.

Installation disk is corrupted.

Contact your technical support representative.

Cannot determine the version of product.

Installation program cannot determine product version.

Contact your technical support representative.

Cannot make list of packages for installation.

Installation suffered a major failure.

Contact your technical support representative.

Cannot upgrade.

Upgrade failed.

Contact your technical support representative.

Copy setupdir to nmsroot failed.

Installation program could not write to product root directory.

Check the permissions on the root.

Installation in progress

You are already running an installation on this machine.

Run only one installation program at a time.

For more information, see Frequently Asked Questions.

Missing file file.

Installation program cannot find a file.

Contact your technical support representative.

No Syslog facility is available.

No available Syslog facilities.

Make one of the facilities available.

Not enough disk space: root.

File system has insufficient space to load Essentials.

Make at least 4 GB of disk space available on the partition on which you install Essentials.

Package verification failed: pkg aborting.

While loading packages, one loaded incorrectly.

Contact your technical support representative.

Syslog is not running.

Installation program cannot start syslogd on this machine.

Restart syslogd.

The components have dependency errors.

Installation program suffered a major failure.

Contact your technical support representative.

User must be root.

You must be root to install.

Log in as root and enter the correct password.

User casuser appears in /usr/lib/cron/at.deny. Software Image Manager requires casuser to be able to run at. Contact your local technical support representative to edit the file /usr/lib/cron/at.deny and remove the entry for casuser.

User casuser appears in /usr/lib/cron/cron.deny. Software Image Manager requires casuser to be able to run crontab. Contact your local technical support representative to edit the file /usr/lib/cron/cron.deny and remove the entry for casuser.

Software Management requires that the user casuser be allowed to use at and cron.

Edit the relevant files to allow the user casuser to use at and cron. For details, see "Allowing the User casuser to Use at and cron" section.

Wrong OS.

Operating system is not Solaris or not a supported version of Solaris.

Make sure you are running Solaris 2.7 or 2.8.


Installing Syslog Analysis

If the Essentials installation fails during Syslog Analysis installation, make sure you do not have the Cisco DNS/DHCP Manager (CDDM) installed on the same machine as Essentials. CDDM, which can be downloaded from CCO, provides syslog and TFTP daemons as part of its product.

You cannot run CDDM Syslog or TFTP on the same machine as Essentials because they are not compatible. Make sure the server on which you install Essentials is not running CDDM Syslog or TFTP.


Caution The tftp directory ` /tftpboot' appears to be NFS mounted. Using NFS directories often increases the software transfer time and may cause a failure during distribution of the software to the device. Contact your local technical support representative to make ` /tftpboot' a local directory.

Failure to Delete a Package During Uninstallation

If you try to remove Essentials but the uninstallation program fails to delete a package, try running the uninstall program again. Several circumstances can cause a package to remain after uninstallation. Usually, running the uninstall program again, removes the package.

Accessing the CiscoWorks Server

The CiscoWorks Server uses port 1741 by default. This port is normally used by web servers. If you receive an error message that an existing web server is already configured to run on port 1741, and the alternative port is used instead, verify that you entered the correct URL for the server:

http://server_name:port_number

where server_name is the name of the machine where CiscoWorks was installed, and port_number is the alternative port on which CiscoWorks is installed if port 1741 is in use.

If SSL is enabled, enter:

https://server_name:1742 

where server_name is the name of the machine where CiscoWorks was installed.

Verify the Server Is Running

To make sure your server is running, enter:

ping server_name

Proxy Server Problems

If you get a message that the server is "alive," and get a proxy error when you try to connect to the server, make sure the proxy is set up correctly.

You will get proxy errors if both these conditions are true:

Your server is configured to use a proxy server outside the firewall.

You configured the proxy to ignore requests to a certain machine, set of machines, or domain.

You should specify a proxy server in Netscape Navigator under Edit > Preferences > Advanced > Proxies and in Internet Explorer under Tools > Internet Options > Connections > LAN Settings.

Your proxy is set up incorrectly if:

You receive an error message that you are using a proxy outside the firewall.

The proxy server recognizes www-int as an internal server, so it does not proxy requests to that server.

You set up a new internal server, www-nms, but when you make a request to the proxy server, it does not recognize www-nms as an internal server and proxies the request.

The proxy server outside the firewall tries to request data from a server inside the firewall, and the request is blocked.

You get a Connection Refused error from the proxy server.

Daemon Manager Not Running

You can use the following command to verify whether the daemon manager is running:

# /opt/CSCOpx/bin/pdshow

If the daemon manager is not running, following error message is displayed:

connect to dmgtd process on "127.0.0.1" on port 42340 failed: 

If the Daemon Manager is not running, CiscoWorks cannot run. When you install or uninstall CiscoWorks, the Daemon Manager is temporarily stopped and then restarted. If the install or uninstall process is interrupted, the Daemon Manager might remain in the stopped state.


Note Wait a few seconds after the server starts before logging in. If you have trouble logging in, use the "Reload" button on your browser.


To start or stop the Daemon Manager:


Step 1 Log in as root.

Step 2 Open a shell window.

Step 3 Start the server by entering:

# /etc/init.d/dmgtd start

Step 4 Stop the server by entering:

# /etc/init.d/dmgtd stop


Viewing Process Status

You can check back-end server process failures by selecting Server Configuration > Administration > Process Management > Process Status. Only users with administrator privileges can start and stop processes. For details, refer to User Guide for CiscoWorks Server.

Browser Problems

If the desktop buttons do not work, Java and JavaScript are not enabled. Make sure you enable Java and JavaScript.

Make sure the browser cache is not set to zero.

Do not resize the browser window while the desktop main page is loading. This can cause a Java error.

For more information about setting up browsers, refer to Installation and Setup Guide for Common Services on Solaris.

Improving Server Performance

To improve system performance for Essentials:

Reduce the number of managed devices polled by Availability.

Increase the interval used by Availability to poll managed devices.

Reduce the number of syslog messages saved to the CiscoWorks database.

Increase the interval used by Configuration Management to collect information about managed devices.

While using CMF Syslog Service, you can turn off DNS lookup to improve performance of Syslog Analyzer.

To turn off, set the registry key HKEY_LOCAL_MACHINE > System > CurrentControlSet > Services > crmlog > Parameters > CrmDnsResolution to 0.

Frequently Asked Questions

What are the various installation switches supported?

I modified the date and time on the CiscoWorks Server, but Essentials does not reflect the change. What should I do?

How do I re-initialize the Essentials database on a Solaris system, if the Essentials database is corrupted and the database restore operation has failed?

Can I use Essentials within a network containing firewalls? If so, what are special configurations I need to take care of?

Can I change the Essentials Database password? If so, how?

How do I back up a converted database

When I perform a backup of the Essentials database, what data is backed up?

When I export the Essentials database, what data is exported?

I performed a fresh installation of Essentials 3.5 on a machine. I also reinstalled Essentials 3.5 on another machine. Why did the installation prompt me for new a password in the latter scenario?

What is an IDU?

Why should I install the latest IDU?

Where can I download an IDU?

How do I know which version of IDU I have installed?

I have upgraded to Essentials 3.5. But, I have lost support for some devices. Why?

How do I cleanup my system after an aborted installation of Essentials?

Q. What are the various installation switches supported?

A. The following options are supported during installation:

Command
What it does

setup.sh -d

Running installation in the debug mode.

setup.sh -q ""

Quiet mode.


Q. I modified the date and time on the CiscoWorks Server, but Essentials does not reflect the change. What should I do?

A. You will need to stop and restart the CiscoWorks Daemon Manager for Essentials to reflect the changes in date, time or timezone.

For more information on stopping and starting the Daemon Manager, see "Daemon Manager Not Running" section.

Q. How do I re-initialize the Essentials database on a Solaris system, if the Essentials database is corrupted and the database restore operation has failed?

A. You can use the dbRestoreOrig.pl utility to re-initialize the Essentials database. To reinitialize the database, follow this procedure:


Step 1 Stop the daemon manager by entering:

/etc/init.d/dmgtd stop

Step 2 At the prompt, run the PERL script dbRestoreOrig.pl:

/opt/CSCOpx/bin/perl /opt/CSCOpx/bin/dbRestoreOrig.pl

The usage details for dbRestoreOrig.pl appear.

Enter the required variable parameters and the corresponding values based on your application (see "Variable Parameters" table).


Caution All the user configurable variable parameters are case-sensitive. Ensure that you enter the exact value as mentioned in the table—if not, the database will get corrupted.

We recommend that you reinitialize the database for both the applications—Common Services and Essentials. Else, the database may become inconsistent. You can follow any order for reintialization.

.

Table B-2 Variable Parameters 

Variable Parameter
For Common Services enter
For Essentials enter
dsn

cmf

rme

dmprefix

Cmf

Essentials

npwd

Note It is optional to enter a new password for this variable. Enter a new password only if you want to change your database password.

Your new password

Your new password


You will see a message that the initialization is complete.

Step 3 Restart the daemon manager by entering:

/etc/init.d/dmgtd start


Q. Can I use Essentials within a network containing firewalls? If so, what are special configurations I need to take care of?

A. Yes, you can use Essentials in a network containing firewalls.

Let us consider a few scenarios here:

Your server is behind a firewalled network, while your clients are outside the firewall.

In this scenario, you have to open ports on the firewall for your clients. If all you are interested in is Essentials, then you have to open TCP 1741 (or whichever port cscoweb is set to) as well as all established TCP connections.

If you require client support for Campus Manager, ACLM, or IPM, you have to take into account CORBA which requires you to open all TCP ports above 1023 on your firewall. In such a case, a better solution would be to create VPN tunnels for your clients.

You want to manage devices outside a firewall.

In this scenario, you need to open a few ports. For maximum manageability, ensure that the ports listed in Table B-3 are open.

Table B-3 Devices outside firewall

Path
Ports

From Essentials server to device.

UDP 161,

TCP 80,

TCP 23 (and/or 22 (SSH) and/or 514 (RCP))

From device to Essentials server.

UDP sourced from 161,

UDP 69 (TFTP),

UDP 514 (syslog),

All established TCP sessions


Your firewall is engaged in NAT (Network Address Translation).

In this scenario, if you need to manage devices outside the NAT boundary, you must modify $NMSROOT/www/classpath/com/cisco/nm/archive/
config.properties file, and set USE_NAT to yes and decide on which USER_FIELD you wish to store the public address of the server (the default is field 3). Edit the attributes of the devices which fall outside of the NAT boundary so that the public address of the server is in the user field configured above. Consequently, when you perform Software Image Management operations, and configuration TFTP operations, this IP address will be used as the TFTP server address. Note, you must still open all the ports listed in Table B-3.

Q. Can I change the Essentials Database password? If so, how?

A. Yes, you can change the Essentials Database password. To do so:


Step 1 On the CiscoWorks Server, using a CLI, enter:

# /etc/init.d/dmgtd stop

This stops the daemon manager.

Step 2 Enter:

# cd /opt/CSCOpx/bin
# ./dbpasswd.pl dsn=rme


Note For detailed usage information, you can enter the following:
# ./dbpasswd.pl


The following message appear:

Please enter the new password for database rme:

Step 3 Enter the new password. The following message appears:

Please enter the new password again for verification:

Step 4 Enter the password again for verification. The following message appears:

Do you want to encrypt the database username and password, YES[Y] or 
keep the encryption mode as it is [N]:

Step 5 Enter Y to encrypt.

Step 6 Start the daemon manager. Enter:

# /etc/init.d/dmgtd start


Q. How do I back up a converted database

A. After a successful installation of Essentials it is a good practise to back up your newly converted database. This creates a backup compatible with Essentials 3.5 in case you have a problem and need to restore your database. This also prevents overwriting your database by restoring a database backup from the previous version of Essentials.


Step 1 Access the CiscoWorks desktop and log in. For information, see the "Accessing the Server" section and the "Logging In" section.

Step 2 Select Server Configuration > Administration > Database Management > Back Up Data Now.

The Back Up Data Now dialog box appears.

Step 3 Enter the pathname of the target directory. It is recommended that you use a different directory from the directory where Essentials is located, for example, /rme/backups.

Step 4 To begin the backup, click Finish. This process could take some time to complete.


Q. When I perform a backup of the Essentials database, what data is backed up?

A. The following data files are backed up:

Properties file for performing Configuration Management.

Directory containing Device Configurations

Configuration Jobs and NetConfig Templates

Software Image Management image repository

Q. When I export the Essentials database, what data is exported?

A. The following data is exported:

Essentials Application
What gets Exported

Availability

Data collected during polling

Inventory

The Essentials and Syslog databases

Configuration Management

Properties file for performing configuration management

Device Configurations

Directory containing device configuration information

Configuration Jobs

NetConfig, NetShow and ConfigEditor jobs

NetConfig templates

Software Image Management

Software Image Management image repository


Q. I performed a fresh installation of Essentials 3.5 on a machine. I also reinstalled Essentials 3.5 on another machine. Why did the installation prompt me for new a password in the latter scenario?

A. When you perform an installation of Essentials 3.5 and choose the typical installation mode, the installation will generate a random password for the Essentials database. In the second scenario, you might have opted for a custom installation. For more information see the table below:

Installation Type
Typical Mode
Custom Mode
Quiet Mode
New installation

Installation generates a random password.

You are prompted to view the generated password after installation completes.

You are prompted to enter a new password.

Installation generates a random password.

You are prompted to view the generated password after installation completes.

Upgrade installation

Password from previous installation of Essentials is restored.

You are prompted to enter a new password.

Password from previous installation of Essentials is restored.

Reinstallation

Password from previous installation of Essentials is restored.

You are prompted to enter a new password.

Password from previous installation of Essentials is restored.


Q. What is an IDU?

A. IDU (Incremental Device Update) for a CiscoWorks application is a downloadable package containing a collection of updated files to provide you with support for new devices. In addition, the package also contains fixes to certain known problems, as well as fixes to newly discovered problems. IDUs are available for download for various versions of CiscoWorks applications.

Q. Why should I install the latest IDU?

A. If you had installed IDU 2.0 on Essentials, and then upgraded to Essentials 3.5, you will not lose any device support. This is because IDU 2.0 has been merged into Essentials 3.5. But, if you had installed a version of IDU later than 2.0 on Essentials, and then upgraded to Essentials 3.5, you will lose support for new devices, and fixes to known problems.

Q. Where can I download an IDU?

A. To retain support for new devices, we recommend that you download and install the latest IDU for Essentials 3.5 from

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme.

Q. How do I know which version of IDU I have installed?

A. To check the version of IDU installed on your system, from the CiscoWorks desktop, select Server Configuration > About the Server > Applications and Versions.

The Patches Installed table displays the installed version of the applications in the following format:

If Patches Installed table displays
IDU version installed is...

RME3_3_IDU-2_0

IDU 2.0 on Essentials 3.3

RME3_3_IDU-3_0

IDU 3.0 on Essentials 3.3

RME3_4_IDU-2_0

IDU 2.0 on Essentials 3.4

RME3_4_IDU-3_0

IDU 3.0 on Essentials 3.4


Q. I have upgraded to Essentials 3.5. But, I have lost support for some devices. Why?

A. If you had installed IDU 2.0 on Essentials, and then upgraded to Essentials 3.5, you will not lose any device support. This is because IDU 2.0 has been rolled into Essentials 3.5. But, if you had installed a version of IDU later than 2.0 on Essentials, and then upgraded to Essentials 3.5, you will lose support for new devices.

To retain support for the new devices, we recommend that you download and install the latest IDU for Essentials 3.5 from

http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme.

Q. How do I cleanup my system after an aborted installation of Essentials?

A. To revert your system back to its pre-install state, you might have to cleanup your machine after:

An aborted installation of Essentials, as a result of pressing Ctrl-C.

Or

A corrupted installation of Essentials.

Use the procedure below only as a last resort after exhausting all other options, like reinstalling Essentials.


Caution The script will remove all the files installed by CiscoWorks applications.


Step 1 Copy the following lines into a text editor:

# BEGIN COPY

#!/usr/bin/sh

PromptResponse ()
{
 RESPONSE=""
 VALID_RES=""
 if [ -n "$2" ] ; then VALID_RES="$2" ; fi
 DEF_ARG=""
 if [ -n "$3" ] ; then DEF_ARG="$3" ; fi

 until [ "${RESPONSE}" != "" ];
 do
  if [ "${DEF_ARG}" = "" ] ; then
   echo "$1 \c"
  else
   echo  "$1 [${DEF_ARG}] \c"
  fi

  read RESPONSE

  if [ "$VALID_RES" = "1" ]; then
   case "${RESPONSE}" in
    "")
     RESPONSE="${DEF_ARG}"
     ;;
    [Yy]|[Yy][Ee][Ss])
     RESPONSE="y"
     ;;
    [Nn]|[Nn][Oo])
     RESPONSE="n"
     ;;
    *)
     RESPONSE=""
     ;;
   esac
  else
   case "${RESPONSE}" in
    "")
     RESPONSE="${DEF_ARG}"
     ;;
    1)
     RESPONSE="1"
     ;;
    2)
     RESPONSE="2"
     ;;
    3)
     RESPONSE="3"
     ;;
    *)
     RESPONSE=""
     ;;
   esac
  fi

 done

 unset DEF_ARG
 return 0
}

# Main

if [ "`uname`" != "SunOS" ]; then
 echo "This script can only run on Solaris."
 exit 0
fi

if [ `/bin/id | sed -e 's/(.*$//' -e 's/^.*=//'` != 0 ] ; then
 echo "ERROR: You must be logged in as root to run this script."
 exit 0
fi

echo "\nThis script will try to remove CiscoWorks from the system.\
 It is kind of risky to do it especially when you have bundles installed.\
 Please make sure you already tried any of these TWICE:"
echo "\n\t* /opt/CSCOpx/bin/uninstall.sh"
echo "\t* pkgrm CSCOxxx"
echo "\t  (CSCOxxx is one of CiscoWorks packages)"
echo "\nWARNING: Don't try this script unless the system"
echo "WARNING: contents file corrupted (bad or garble"
echo "WARNING: entry) which makes above commands failed.\n"

PromptResponse "Do you want to continue (y/n)?" 1 n
if [ "$RESPONSE" != "y" ]; then
 exit 0
fi

Backup_c=0
Backup_s=0

echo "\nStop daemon manager ..."
if [ -x /etc/init.d/dmgtd ]; then
 /etc/init.d/dmgtd stop 2> /dev/null
 sleep 10
fi

echo "\nChecking CSCO packages installed ... \c"
csco_pkgs=`ls -d /var/sadm/pkg/CSCO* 2> /dev/null |sed -e 's#/var/sadm/pkg/##' -e 's#/##'`
if [ "$csco_pkgs" = "" ]; then
 csco_pkgs=`grep " CSCO" /var/sadm/install/contents |awk '{print $NF}' |grep CSCO |sort 
-u`
fi

if [ "$csco_pkgs" = "" ]; then
 echo "No"
else
 echo "Yes\n"

 for pkg in `echo $csco_pkgs`; do echo "\t$pkg"; done
 echo "\nAbove packages found in the system. Some of them might not belong\
 to CiscoWorks when you have other Cisco product installed. If you are\
 not sure about this, verify these packages with Cisco TAC before go ahead."
 echo "\n\t1. Clean them all in one step."
 echo "\t2. Clean them one by one. (later you can select to skip any of them)"
 echo "\t3. Quit.\n"

 PromptResponse "Please input your decision -->" 2
 if [ "$RESPONSE" != "1" -a "$RESPONSE" != "2" ]; then
  exit 0
 fi
 METHOD=$RESPONSE

 echo "\nBackup contents file in /var/sadm/install/contents.save.$$"
 cp /var/sadm/install/contents /var/sadm/install/contents.save.$$
 Backup_c=1
 echo "\nCleaning packages from system registry ..."
 cp /var/sadm/install/contents /tmp/contents
 for pkg in `echo $csco_pkgs`;
 do
  if [ "$METHOD" = 2 ]; then
   PromptResponse "Clean $pkg ?" 1
   if [ "$RESPONSE" != "y" ]; then continue; fi
  fi
  grep -v $pkg /tmp/contents > /tmp/contents.tmp
  mv /tmp/contents.tmp /tmp/contents
  rm -rf /var/sadm/pkg/$pkg
  echo "$pkg cleaned"
 done
 mv /tmp/contents /var/sadm/install/contents
fi

if [ "`grep CSCO /etc/services`" != "" ]; then
 echo "\nBackup system services file in /etc/services.save.$$"
 cp /etc/services /etc/services.save.$$
 Backup_s=1
 echo "Cleaning system services file ..."
 grep -v CSCO /etc/services > /tmp/remove.tmp
 mv /tmp/remove.tmp /etc/services
fi

echo "\nCleaning CiscoWorks runtime trees ..."

if [ -d /opt/CSCOpx -o -h /opt/CSCOpx ]; then
 PromptResponse "Remove /opt/CSCOpx ?" 1
 if [ "$RESPONSE" = "y" ]; then
  rm -rf /opt/CSCOpx/*
  rm -rf /opt/CSCOpx
 fi
fi

if [ -d /var/adm/CSCOpx ]; then
 PromptResponse "Remove log directory /var/adm/CSCOpx ?" 1
 if [ "$RESPONSE" = "y" ]; then
  rm -rf /var/adm/CSCOpx
 fi
fi

if [ -d /tmp/cscotmp -o -f /tmp/csco* ]; then
 PromptResponse "Remove temp files /tmp/csco* ?" 1
 if [ "$RESPONSE" = "y" ]; then
  rm -rf /tmp/csco*
 fi
fi

echo
if [ "$Backup_c" = "1" ]; then
 echo "INFO: Original contents file saved in /var/sadm/install/contents.save.$$"
fi
if [ "$Backup_s" = "1" ]; then
 echo "INFO: Original system services file saved in /etc/services.save.$$"
fi

echo "\nCleaning is done."

# END COPY

Step 2 Save the text in the text editor as a shell script, with a .sh extension.. For example, you can save the file as cleanup.sh.

Step 3 Using a CLI, modify the permissions on the file to allow script execution. For example if you saved the file as cleanup.sh, enter:

# chmod 750 cleanup.sh

Step 4 Navigate to the directory where you saved the file, and enter:

# ./cleanup.sh

The script removes files installed by all CiscoWorks applications.