Cisco Prime Provisioning Installation Guide, 7.2

Symptom 1

Out of disk space.

Recommended Action

The error looks something like the following:

If you see an error like this, it is likely due to the server running out of disk space.

To verify what space is available, run the command df –k < install directory >.

See “Installation Requirements,”for the disk space recommendations.

Symptom 2

The Installation utility GUI never displays.

Recommended Action

This problem should be accompanied with a Java stack dump.

Step 1 Run the following command to check for the $DISPLAY environment variable being set:

echo $DISPLAY.

If you use the secure shell (ssh), then this will be set up and managed for you.

If you manually change the $DISPLAY environment variable in an SSH environment, the easiest recovery method is to log off and reestablish the SSH connection.

Step 2 To set the DISPLAY environment variable, do the following:

a. For the K or Bourne shell:

b. For the C shell:

setenv DISPLAY= < machine name > :0.0

Symptom 3

Could not find temporary files.

Recommended Actions

If you receive an error that says the temporary file could not be created or found, it usually means the location used to write the temporary file is write-protected or out of disk space.

The two places that Prime Provisioning uses for temporary files are /tmp and /var/tmp.

• Make sure both locations have write permission by doing a long list on the directories (ls -la). The directory should have wide open permissions: drwxrwxrwx.
• There is another temporary file problem that can arise, especially in cases where there have been previous aborted installation attempts—existing temp files might be left by previous installations. If this is the case, it is best to clean out all the files in the temp directories after aborted installation attempts.

Symptom 4

Running./install.sh fails.

Recommended Action

Running./install.sh can fail due to the following reasons:

1. You are not root.

Although it is possible to install as non-root if you have appropriate permissions in the target directory, this will still have problems since only root can write to /etc/init.d where the startup scripts reside. Therefore, it is easier to install as root.

2. You do not have enough disk space in the target directory. To find out the available disk space, issue the following command:

df –k <target directory>

3. You do not have enough disk space in the /tmp directory. Issue the command df –k /tmp to determine the available disk space for /tmp.

4. You do not have enough disk space in the /var/tmp directory. Issue the command df –k /var/tmp to determine the available disk space for /var/tmp.

5. The PATH and LD_LIBRARY_PATH environment variables are incorrect.

Make sure your PATH and LD_LIBRARY_PATH environment variables are correct.

Example:

a. Alternatively, start a clean root shell with this command:

env – ksh

b. Then issue a command like the following:

./install.sh /opt/PrimeProvisioning iscadm

Symptom 5

Prime Provisioning does not start on reboot.

Recommended Action

Perform the following steps:

Step 1 Install Prime Provisioning as the root user.

If you install as root, init.d has a script to start the Watchdog.

If you do not install as root, you do not get the startup on reboot feature.

Step 2 To become root, enter the following command:

su root

Step 3 Get the prime.tmpl file from the installation media.

Step 4 Edit the following fields in prime.tmpl :

OWNER=_owner - replace _owner with the username whom owns prime

PRIMEF_HOME=_vpnsc_home - replace _vpnsc_home with the prime directory

Step 5 Rename prime.tmpl as prime and then enter the following commands:

mv prime /etc/init.d

chmod 744 /etc/init.d/prime

Step 6 Create the following symbolic links to prime :

a. cd /etc/rc1.d

ln -s /etc/init.d/prime K98ISC

b. cd to /etc/rc2.d

ln -s /etc/init.d/prime K98ISC

c. cd to /etc/rc3.d

ln -s /etc/init.d/prime S99ISC

Symptom 6

Note Cisco Networking Services (CNS) has been removed as of Prime Provisioning 6.7.

Unable to create or delete IOS devices in the Cisco CNS IE2100 appliance repository when using Cisco CNS Configuration Engine 1.4 software with Prime Provisioning.

Recommended Action

Log into the Cisco CNS IE2100 appliance as root and modify the web.xml file located at /opt/CSCOcnsie/WEB-INF as follows.

Step 1 Locate the following entry:

<servlet>

<servlet-name> ServletLoadComplete </servlet-name>

<servlet-class> com.cisco.cns.cfgsrv.ServletLoadComplete </servlet-class>

<load-on-startup> 105 </load-on-startup>

</servlet>

Step 2 Immediately after the entry found in Step 1, insert the following lines:

<servlet>

<servlet-name> ImportDevice </servlet-name>

<servlet-class> com.cisco.cns.cfgsrv.ImportDevice </servlet-class>

<load-on-startup> 100 </load-on-startup>

</servlet>

<servlet>

<servlet-name> ImportTemplate </servlet-name>

<servlet-class> com.cisco.cns.cfgsrv.ImportTemplate </servlet-class>

<load-on-startup> 100 </load-on-startup>

</servlet>

<servlet>
<servlet-name> RemoveDevice </servlet-name>
<servlet-class> com.cisco.cns.cfgsrv.RemoveDevice </servlet-class>
<load-on-startup> 100 </load-on-startup>
</servlet>

<servlet>
<servlet-name> RemoveTemplate </servlet-name>
<servlet-class> com.cisco.cns.cfgsrv.RemoveTemplate </servlet-class>
<load-on-startup> 100 </load-on-startup>
</servlet>

Step 3 Locate the following entry:

<servlet-mapping>

<servlet-name> ServletLoadComplete </servlet-name>

<url-pattern> /ServletLoadComplete </url-pattern>

</servlet-mapping>

Step 4 Immediately after the entry found in Step 3, insert the following lines:

<servlet-mapping>

<servlet-name> ImportDevice </servlet-name>

<url-pattern> /ImportDevice </url-pattern>

</servlet-mapping>

<servlet-mapping>

<servlet-name> ImportTemplate </servlet-name>

<url-pattern> /ImportTemplate </url-pattern>

</servlet-mapping>

<servlet-mapping>
<servlet-name> RemoveDevice </servlet-name>
<url-pattern> /RemoveDevice </url-pattern>
</servlet-mapping>

<servlet-mapping>
<servlet-name> RemoveTemplate </servlet-name>
<url-pattern> /RemoveTemplate </url-pattern>
</servlet-mapping>

Step 5 Reboot the Cisco CNS IE2100 appliance.

Symptom 7

Not able to connect to the database.

Recommended Action

Perform the following steps:

Step 1 Check that the following values are substituted correctly in the installation window:

• Oracle database server name
• Oracle port number
• SID

Step 2 If everything is correct, check that the server is reachable by entering:

ping < Oracle database server name >

Step 3 Issue the following to determine whether the database is running:

netstat -an | grep < oracle port number >

If no responses are found, your database is not running and you must restart, as explained in detail in the section, “Launching Oracle and Opening Your Database”.

Symptom 8

Unable to access Prime Provisioning with your web browser.

Recommended Action

Check the server status with the command ./prime.sh status.

If any server state is other than started, attempt to restart by entering the command,
./prime.sh wdclient restart < server name >. If this command does not succeed, enter the commands
./prime.sh stop and then ./prime.sh startwd.

Note The most common server not to start is the httpd server.

Symptom 9

The web browser does not display certain GUI elements such as the main bar and charts in Prime Provisioning GUI.

Recommended Action

Install Adobe Flash player (version 10.3.183.7) and its plug-in to support the web browser and to enable the main bar and charts in the Prime Provisioning GUI.

Symptom 10

Installation fails due to ANT related errors, such as:

Exception - BUILD FAILED

/opt/Prime Provisioning -6.8/install.xml:57: The signjar type doesn't support the "destdir" attribute

followed by

Error running: /opt/Prime Provisioning -6.8/thirdparty/ant/bin/ant -f /opt/Prime Provisioning -6.8/install.xml jarsigner

Exiting installation.

Cause

Prime Provisioning is unable to use the right version of ANT.

Recommended Action

Update the silent_install.sh file available in the untarred installation folder as follows:

• Locate the command
  ANT_HOME=${vpnsc_home}/thirdparty/ant
• Include the following text in the next line
  export ANT_HOME
• Re-intall Prime Provisioning.

Symptom 11

Prime Provisioning cannot unzip the upgrade tool during installation.

Error: Cannot create upgradeTool

Recommended Action

• For a new installation ( for new installations, the symptoms of this issue are minor and can be ignored):

– a) Copy the installation files from cd /cdrom/cdrom0 to a location to which you have Write permissions.

– b) Initiate the installation procedure:
/install.sh

• New installation using an existing DB, and the opting to upgrade the DB manually:

– a) Copy the installation files from the cd /cdrom/cdrom0 to a location to which you have Write permissions.

– b) Go to the location where you have copied the installation files:
cd <Hand-off location>

– c) Unzip the isc-upgrade.zip file:
unzip isc-upgrade.zip

– d) Initiate the installation procedure:
/install.sh

• Upgrade installation and choosing to perform an ‘upgrade in place’:

– a) Copy the installation files from the cd /cdrom/cdrom0 to a location to which you have Write permissions.

– b) Go to the location where you have copied the installation files:
cd <Hand-off location>

– c) Unzip the isc-upgrade.zip file:
unzip isc-upgrade.zip

– d) Initiate the installation procedure:
/install.sh