Cisco DCNM Installation and Licensing Guide, Release 5.x
Troubleshooting Cisco DCNM-LAN Server Installation
Downloads: This chapterpdf (PDF - 107.0KB) The complete bookPDF (PDF - 3.69MB) | Feedback

Troubleshooting the Cisco DCNM-LAN Server Installation

Table Of Contents

Troubleshooting the Cisco DCNM-LAN Server Installation

Postgres Database Installation Fails

Previous Installation Found When No Previous Installation Exists

Editing the Zero G Registry File

Path to the Perl Binary Directory Not Found

Cisco DCNM-LAN Installer Asks for Another Extraction Location


Troubleshooting the Cisco DCNM-LAN Server Installation


This chapter describes how to troubleshoot some common issues that you might experience while installing a Cisco Data Center Network Manager for LAN (DCNM-LAN) server with solutions for the issues.

This chapter includes the following sections:

Postgres Database Installation Fails

Previous Installation Found When No Previous Installation Exists

Path to the Perl Binary Directory Not Found

Cisco DCNM-LAN Installer Asks for Another Extraction Location

Postgres Database Installation Fails

Check Table 15-1 for symptoms related to an installation failure of the Postgres database. For each symptom that describes your trouble, determine which possible causes apply and follow the corresponding solutions.

Table 15-1 Postgres Database Installation Fails 

Symptom
Possible Cause
Solution

Postgres database installation fails.

The username specified to run the Postgres service already exists on the server.

Specify a different username or remove the existing username from the server.

Antivirus software or intrusion detection software, such as Cisco Security Agent, blocked the installation.

Temporarily disable any antivirus software and intrusion detection software, and then reinstall Cisco DCNM-LAN.

The PostgreSQL installer shows the following message:

Failed to run 
initdb: 128

(Microsoft Windows only) Remote Desktop Connection client not running in console mode.

If you are installing Cisco DCNM-LAN on a supported Microsoft Windows operating system and using Remote Desktop Connection (RDC) to access the Cisco DCNM-LAN server system, start RDC from a command prompt and use the /console option, as follows:

C:\>mstsc /console /v:server
 
        

where server is the DNS name or IP address of the Cisco DCNM-LAN server system.

If the /console option not supported in Microsoft Windows version that you are running, use the /admin option, as follows:

C:\>mstsc /admin /v:server

The PostgreSQL installer shows the following message:

PostgreSQL installation has failed.

Failed to run initdb: 128

(Macintosh only) Remote Desktop Connection client not running in console mode.

If you are using Remote Desktop Connection on a Macintosh computer to access the Cisco DCNM-LAN server system follow these steps:

1. Enter the IP Address of the windows server on which the DCNM is installed.

2. Hold down the Command key and click Connect. This will force RDC to use console mode.

3. Release the Command key when the authentication window appears.

The PostgreSQL installer shows the following message:

Failed to create 
process for initdb. 
The service cannot 
be started, either 
because it is 
disabled or because 
it has no enabled 
devices associated 
with it.

(Microsoft Windows only) The Secondary Logon service is not running.

Verify that the Secondary Logon service is running.

1. On the Cisco DCNM-LAN server system, open the Control Panel and go to Administrative Tools > Services.

2. In the list of services, find the Secondary Logon service.

3. If the status of the Secondary Logon service is not Started, right-click the service and choose Start.

4. Close the Services window.

5. Restart the Cisco DCNM-LAN server installation.


Previous Installation Found When No Previous Installation Exists

Table 15-2 lists issues found when no previous installation exists.

Table 15-2 Previous Installation Found when No Previous Installation Exists 

Symptom
Possible Cause
Solution

A message wrongly states that a previous installation exists.

The following file has incorrect entries regarding Cisco DCNM-LAN:

C:\Program Files\Zero G 
Registry\.com.zerog.registry.xml

1. Perform the steps in the "Editing the Zero G Registry File" section.

2. Install the Cisco DCNM-LAN server.


Editing the Zero G Registry File

You can edit the Zero G Registry file to remove incorrect entries, which might cause the installation of the Cisco DCNM-LAN server to fail.

DETAILED STEPS


Step 1 Make a backup of the .com.zerog.registry.xml file, which is found at the following location:

C:\Program Files\Zero G Registry\.com.zerog.registry.xml
 
   

Step 2 Open the file in a text editor.

Step 3 Within the <products> element, remove the following <product> element and all its descendant elements:

<product name="Cisco DCNM" id="9e458447-1ee6-11b2-85ed-d4ed684e9c05" version="4.0.0.0" 
copyright="2007". . .
 
   

Step 4 Within the <components> element, remove every instance of the following <component> element:

<component id="9e458484-1ee6-11b2-860c-d4ed684e9c05" version="1.0.0.0" 
name="InstallAnywhere VM Component" location="C:\Program Files\Cisco Systems\Cisco 
DCNM\jre" vendor="Cisco Systems Inc."/>
 
   

Step 5 Save and close the file.


Path to the Perl Binary Directory Not Found

Table 15-3 lists the symptoms related to the Perl binary directory. For each symptom that describes your trouble, determine which possible causes apply and follow the corresponding solutions.

Table 15-3 Path to the Perl Binary Directory Not Found 

Symptom
Possible Cause
Solution

An error message states that the path to the bin directory for Perl is not in the system PATH environment variable.

Perl is not installed on the server system.

1. Install a supported version of ActivePerl. For more information about ActivePerl, see the "Prerequisites for Installing a Cisco DCNM-LAN Server" section.

2. Ensure that the system PATH environment variable includes the path to the directory that contains the Perl executable. On Microsoft Windows, the default path to the ActivePerl bin directory is C:\Perl\bin.

3. Start the DCNM-LAN server installation again.

The server system PATH environment variable does not include the path to the directory that contains the Perl executable.

1. Verify that a supported version of ActivePerl is installed on the server system. If not, install a supported version of ActivePerl. For more information about ActivePerl, see the "Prerequisites for Installing a Cisco DCNM-LAN Server" section.

2. Ensure that the system PATH environment variable includes the path to the directory that contains the Perl executable. On Microsoft Windows, the default path to the ActivePerl bin directory is C:\Perl\bin.

3. Start the DCNM-LAN server installation again.


Cisco DCNM-LAN Installer Asks for Another Extraction Location

Table 15-4 lists issues found when a Cisco DCNM-LAN installer asked for another extraction location.

Table 15-4 Cisco DCNM-LAN Installer Asks for Another Extraction Location 

Symptom
Possible Cause
Solution

After running the Cisco DCNM-LAN server installer, you see a dialog box with the following message:

Please select another location to 
extract the installer to

The Cisco DCNM-LAN installer software is corrupted. This problem can occur if you use FTP or a similar transfer protocol in ASCII mode.

1. Delete the Cisco DCNM-LAN server installer.

2. Download the Cisco DCNM-LAN server software again. For more information, see the "Downloading the Cisco DCNM-LAN Server Software" section.

Note If you transfer the installer with FTP or a similar protocol, ensure that you use a binary mode to transfer the installer.