DocWiki - User contributions [en]

Troubleshooting Configuration Update

2011-06-13T06:48:16Z

Hsivakum: /* Config job fails for commands like "show run", "tclsh" etc */

To troubleshoot a configuration update, see the following sections:

==Config update failed==
'''Symptom: '''

The Device configuration update fails.

'''Solution: '''

To resolve this problem, follow these steps:

Step 1 Check the following on the Cisco Configuration Engine:

a. Make sure that the Event ID and Config ID match with what is defined on the device.

b. Make sure that the object status for the device in Cisco Configuration Engine is green. Green indicates that the Cisco Configuration Engine and the device are connected.

To verify that TibGate is up and running, enter the following command:

/etc/rc.d/init.d/EvtGateway status

/etc/rc.d/init.d/EvtGatewayCrypto status

Note If encryption is enabled, the TibGate ports begin with even numbers that begin from 11014. If encryption is not enabled, the TibGate ports begin with odd numbers that begin from 11013. Each TibGate port can support a maximum of 500 devices. You specify the number of the TibGates during the Cisco Configuration Engine Setup program. Make sure that the number of devices on each TibGate port does not exceed the maximum. For details, see the "Scalability Among Event Gateway Ports" chapter in the Cisco Configuration Engine Installation and Configuration Guide, 3.5.

d. If the authentication feature is enabled in the Cisco Configuration Engine, make sure that the device password (cns password <password string>) that is defined in the Cisco Configuration Engine user interface, matches with what is defined on the device. Otherwise, use the resync device command to reset the CNS password.

To use the resync command from the Cisco Configuration Engine user interface, do the following:

a. Go to Devices > Resync Device. The Resync Device page appears with a Groups list.

b. From the Groups list, choose the group that contains the device you want to resynchronize. Then click the icon for the device.

c. In the confirmation window, click Ok.

e. Make sure that the downloading configuration semantics and syntax for the device are correct.

If the device in the Cisco Configuration Engine was initially set as None, then deleted, and then re-created as an agent-enabled device, you must rename the Config ID and Event ID on both the device and the Cisco Configuration Engine user interface.

g. If during the Cisco Configuration Engine setup, a port other than the default port 80 is configured for HTTP, make sure that the same port number is also configured on the device.

Step 2

Check the following on the device:

a. Make sure that the following Event ID string is defined:cns id string <id string> cns id string <id string> event
The default value of the <id string> is the hostname of the device. This ID must be the same as the Config ID defined in the Cisco Configuration Engine host.

b. To verify that the Cisco Configuration Engine hostname or IP address is specified to receive events, enter the following command:cns event <configengine hostname> 11011 keepalive 30 10

Note Make sure that the TibGate port of this device is correct. The TibGate port must match the port that is defined in the Cisco Configuration Engine.

c. If the authentication feature is enabled in the Cisco Configuration Engine, make sure that the device password (cns password <password string>) matches what is defined in the Cisco Configuration Engine user interface.

Note You cannot see the password setting after you configure it on the router, nor can you edit the password in Cisco Configuration Engine. Therefore, you must reset the password. To reset the password, use the Resync Device feature in the Cisco Configuration Engine.

d. During the Cisco Configuration Engine setup, if a port other than the default port 80 is configured for HTTP, make sure that the same port number is also configured on the device. To configure the http port on the device, enter the following command:cns config partial <CE hostname> <http port>

Step 3 If you have tried all the preceding steps and the device configuration update still fails, enable the debugging tools.

• In the Cisco Configuration Engine host, do the following:

– To start event listener, enter the following commands:cd $CISCO_CE_INSTALL_ROOT/CSCOcnsie/tools./cns-listen "cisco.>"

– Check the cfgsrv log file. This file is located at: /var/log/CNSCE/cfgsrv/cfgsrv.log.

• In the device, use the debug cns config all command to enable debugging. Analyze the output to verify that the device is set up correctly with proper connectivity.

Step 4 Rerun the scenario, check the event traffic and the information from the device, capture the data, and then contact the Cisco TAC for assistance.

==Config job stuck or The configuration update is stuck in queue after data migration.==

'''Symptom : '''

The configuration update is stuck in queue after data migration.
'''
Solution : '''

After data migration from release 2.0 to 3.5, the OpenLDAP schema is transferred to a new host. To reuse the existing OpenLDAP schema for the new host, make sure that the country code and the company code information on the new host matches what is defined on the old host.

Note The country code and the company code in the OpenLDAP schema are case sensitive.

Step 1 To reinitialize the system, enter the following command:/opt/ConfigEngine/CSCOcnsie/reinitialize

Step 2 To run data migration again, enter the following command:/opt/ConfigEngine/CSCOcnsie/bin/datamigrate

Step 3 To run the Setup program again, enter the following command:/opt/ConfigEngine/CSCOcnsie/setup

Note Make sure that you run the Setup program in bash shell. If the shell is not in bash, press ctrl-c to exit. Configure your shell in bash, and then rerun the Setup program.

Step 4 When entering the Setup parameters, make sure that the country code and the company code information for the new host matches what is defined on the old host.

For detailed information about the parameters in the Setup program, see the Cisco Configuration Engine Administration Guide.

==The configuration update is stuck in the queue after data backup and restore.==
'''Problem : '''

The configuration update is stuck in the queue after data backup and restore.
'''
Solution :  '''

When you back up data and restore it, the OpenLDAP schema is transferred to a new host. To reuse the existing OpenLDAP schema for the new host, make sure that the country code and the company code information on the new host matches what is defined on the old host.

Note The country code and the company code in the OpenLDAP schema are case sensitive.

Step 1 To reinitialize the system, enter the following command:/opt/ConfigEngine/CSCOcnsie/reinitialize

Step 2 To run data restore again, enter the following command:/opt/ConfigEngine/CSCOcnsie/bin/datarestore

Step 3 To run the Setup program again, enter the following command:/opt/ConfigEngine/CSCOcnsie/setup

Note Make sure that you run the Setup program in bash shell. If the shell is not in bash, press ctrl-c to exit. Configure your shell in bash, and then rerun the Setup program.

Step 4 When entering the Setup parameters, make sure that the country code and the company code information for the new host matches what is defined on the old host.

For detailed information about the parameters in the Setup program, see the Cisco Configuration Engine Administration Guide.

==CNS-Enabled Device Unable to Connect with CCE==

'''Problem''': A device is created in the Cisco Configuration Engine user interface but the device indicator displays a red status.

'''Possible Cause''': The red status indicates that the device is unable to connect with Cisco Configuration Engine or it is still trying to connect. A connection delay might occur due to the device setting of the backoff timer. After the time has expired, the indicator does not turn to green, follow the steps given below.

'''Solution''': To resolve this problem, follow these steps:

1. Make sure that the Event ID and Config ID match with what is defined on the device.

Do the following from the Cisco Configuration Engine user interface:

a. Choose '''Devices''' > '''Edit Device'''. The Edit Device page appears with a Groups list.

b. From the Groups list, choose the group that contains the device, then click the icon for the device.

c. From the left pane, choose Edit Information. The Enter Device Information page appears.

d. Click Next. The Select Group Membership page appears.

e. Click Next. The Device IDs page appears.

f. Verify that the Event ID and Config IP match with what is defined on the router.

2. Make sure that the device type is Agent Enabled Device. From the Cisco Configuration Engine user interface, do the following:

a. Choose '''Devices'''>'''Edit Device'''. The Edit Device page appears with a Groups list.

b. From the Groups list, choose the group that contains the device. Then click the icon for the device.

c. From the left pane, choose Edit Information. The Enter Device Information page appears.

d .Verify that the device type is Agent Enabled Device.

3. Ping or telnet to the device to verify that the device is reachable from Cisco Configuration Engine.

4. From the Cisco Configuration Engine server, make sure that TibGate, httpd, and the Java process are up.

* To verify that all TibGates are up, enter the following command:

'''/etc/rc.d/init.d/EvtGateway status'''
'''/etc/rc.d/init.d/EvtGateway status'''

'''Note''': For information about TibGate event gateway ports, see the “Scalability Among Event Gateway Ports” chapter in the Cisco Configuration Engine Installation and Configuration Guide, 3.5.

* To verify that httpd is up, enter the following command:

''''httpd status'''

* To verify that the Java process is up, enter the following command:

'''ps –ef | grep –i java | grep ConfigEngine''''

5. Check the following on the device:

a. Make sure that the following Event ID string is defined:

cns id string <id string>
cns id string <id string> event

The default value of the <id string> is the hostname of the device. This ID must be the same as the Config ID defined in the Cisco Configuration Engine host.

b. To verify that the Cisco Configuration Engine hostname or IP address is specified to receive the events, enter the following command:

''''cns event <configengine hostname or ip address> keepalive 30 10'''

c. To verify that the Cisco Configuration Engine hostname or IP address is reachable from the device, enter the following command:

'''ping <configengine hostname or ip address>'''

d. If you are unable to reach the device through the ping command, use the '''ip host''' command to configure the device:

'''ip host <hostname> <ip address>'''
'''ip host <hostname.domainame> <ip address>'''

e.(Optional) To resolve hostnames, set up the DNS on the device by entering the following command:

'''ip name-server <ip address of DNS>'''

6. If the device status changes from green to red after Cisco Configuration Engine set up, follow the steps in “Device Status” section.

==CNS-Enabled Device Configuration Update Failed==

'''Problem''': The Device configuration update fails.

'''Possible Cause''': This problem can occur for one of the following reasons:

* Invalid commands in the configuration template
* Device is not online (RED)

'''Solution''': To resolve this problem, follow these steps:

If the device appears RED (offline), go to Step 2 and 3 to make the device GREEN (online) before proceeding with step 1.

a. In the Cisco Configuration Engine host, start the event listener and enter the following commands:

'''cd $CISCO_CE_INSTALL_ROOT/CSCOcnsie/tools'''
'''./cns-listen ?cisco.>?'''

Check the cfgsrv log file. This file is located at: /var/log/CNSCE/cfgsrv/cfgsrv.log.
In the device, use the '''debug cns all''' command to enable debugging. If debug messages displays the CNS_INVALID_CLI_CMD as shown below, the config template might contain invalid commands. Apply those commands one by one on the router to find which command failed and remove or fix them from the template.
<pre>
85E1E440: 7572653E 3C696465 6E746966 6965723E ure><identifier>
85E1E450: 31323635 38333937 32393339 32313C2F 12658397293921</
85E1E460: 6964656E 74696669 65723E3C 636F6E66 identifier><conf
85E1E470: 69672D69 643E4643 48313333 39543032 ig-id>myDevice
85E1E480: 383C2F63 6F6E6669 672D6964 3E3C6572 </config-id><er
85E1E490: 726F722D 696E666F 3E3C6C69 6E652D6E ror-info><line-n
85E1E4A0: 756D6265 723E3930 3C2F6C69 6E652D6E umber>90</line-n
85E1E4B0: 756D6265 723E3C65 72726F72 2D6D6573 umber><error-mes
85E1E4C0: 73616765 3E434E53 5F494E56 414C4944 sage>CNS_INVALID
85E1E4D0: 5F434C49 5F434D44 3C2F6572 726F722D _CLI_CMD</error-
85E1E4E0: 6D657373 6167653E 3C2F6572 726F722D message></error-
85E1E4F0: 696E666F 3E3C2F63 6F6E6669 672D6661 info></config-fa
85E1E500: 696C7572 653E ilure>
</pre>

2. Check the following on the Cisco Configuration Engine:

a. Make sure that the Event ID and Config ID match with what is defined on the device.

b. Make sure that the object status for the device in Cisco Configuration Engine is green. Green indicates that the Cisco Configuration Engine and the device are connected.

c. To verify that TibGate is up and running, enter the following command:

'''/etc/rc.d/init.d/EvtGateway status'''
'''/etc/rc.d/init.d/EvtGateway status'''

'''Note''': If encryption is enabled, the TibGate ports begin with even numbers that begin from 11012. If encryption is not enabled, the TibGate ports begin with odd numbers that begin from 11011. Each TibGate port can support a maximum of 500 devices. You specify the number of the TibGates during the Cisco Configuration Engine set up program. Make sure that the number of devices on each TibGate port does not exceed the maximum.

For details, see the “Scalability Among Event Gateway Ports” chapter in the Cisco Configuration Engine Installation and Configuration Guide, 3.5.

d. If the authentication feature is enabled in the Cisco Configuration Engine, make sure that the device password (cns password <password string>) that is defined in the Cisco Configuration Engine user interface, matches with what is defined on the device. Otherwise, use the resync device command to reset the CNS password.

To use the resync command from the Cisco Configuration Engine user interface, do the following:

a. Go to Devices > Resync Device. The Resync Device page appears with a Groups list.

b. From the Groups list, choose the group that contains the device you want to resynchronize. Then click the icon for the device.

c. In the confirmation window, click '''Ok'''.

e. Make sure that the downloading configuration semantics and syntax for the device are correct.

f. If the device in the Cisco Configuration Engine was initially set as '''None''', then deleted, and then re-created as an agent-enabled device, you must rename the Config ID and Event ID on both the device and the Cisco Configuration Engine user interface.

g. During the Cisco Configuration Engine set up, if a port other than the default port 80 is configured for HTTP, make sure that the same port number is also configured on the device.

3. Check the following on the device:

a. Make sure that the following Event ID string is defined:

cns id string <id string>
cns id string <id string> event

The default value of the <id string> is the hostname of the device. This ID must be the same as the Config ID defined in the Cisco Configuration Engine host.

b. To verify that the Cisco Configuration Engine hostname or IP address is specified to receive events, enter the following command:

'''cns event <configengine hostname or ip address> keepalive 30 10'''

'''Note''': Make sure that the TibGate port of this device is correct. The TibGate port must match the port that is defined in the Cisco Configuration Engine.

c. If the authentication feature is enabled in the Cisco Configuration Engine, make sure that the device password (cns password <password string>) matches what is defined in the Cisco Configuration Engine user interface.

'''Note''': You cannot see the password setting after you configure it on the router, nor can you edit the password in Cisco Configuration Engine. Therefore, you must reset the password. To reset the password, use the Resync Device feature in the Cisco Configuration Engine.

d. During the Cisco Configuration Engine set up, if a port other than the default port 80 is configured for HTTP, make sure that the same port number is also configured on the device. To configure the http port on the device, enter the following command:

'''cns config partial <CE hostname> <http port>'''

4. If you have tried all the preceding steps and the device configuration update still fails, enable the debugging tools.

* In the Cisco Configuration Engine host, start the event listener by enter the following commands:

'''cd $CISCO_CE_INSTALL_ROOT/CSCOcnsie/tools'''
'''./cns-listen “cisco.>”'''

* Check the cfgsrv log file. This file is located at: /var/log/CNSCE/cfgsrv/cfgsrv.log.

* In the device, use the debug '''cns config all''' command to enable debugging. Analyze the output to verify that the device is set up correctly with proper connectivity.

5. Re-run the scenario, check the event traffic and the information from the device, capture the data, and then contact the Cisco TAC for assistance.

==Configuration Update Stuck in Queue After Data Migration==

'''Problem''': The configuration update is stuck in queue after data migration.

'''Possible Cause''': This problem can occur if you did not enter the correct country code and company code information during the set up program.

'''Solution''': After data migration from release 3.0 to 3.5, the OpenLDAP schema is transferred to a new host. To reuse the existing OpenLDAP schema for the new host, make sure that the country code and the company code information on the new host matches with what is defined on the old host. Follow these steps:

1. To reinitialize the system, enter the following command:

'''/opt/ConfigEngine/CSCOcnsie/reinitialize'''

2. To run data migration again, enter the following command:

'''/opt/ConfigEngine/CSCOcnsie/bin/datamigrate'''

3. To run the set up program again, enter the following command:

'''opt/ConfigEngine/CSCOcnsie/setup'''

'''Note''': Make sure that you run the set up program in bash shell. If the shell is not in bash, press ctrl-c to exit. Configure your shell in bash, and then re-run the set up program.

4. When entering the set up parameters, make sure that the country code and the company code information for the new host matches with what is defined on the old host.

'''Note''': The country code and the company code in the OpenLDAP schema are case sensitive.

For detailed information about the parameters in the set up program, see the Cisco Configuration Engine Administration Guide.

<pre>
Example:

Choose operational mode of system. 0=internal directory mode,
1=external directory mode. [0]
Enter country code: us
Enter company code: cisco
</pre>

==Configuration Update Stuck in Queue After Data Backup and Restore==

'''Problem''': The configuration update is stuck in the queue after data backup and restore.

'''Possible Cause''': This problem can occur if you did not enter the correct country code and company code information during the set up program.

''''Solution''': When you back up data and restore it, the OpenLDAP schema is transferred to a new host. To re-use the existing OpenLDAP schema for the new host, make sure that the country code and the company code information on the new host matches with what is defined on the old host. Follow these steps:

1. To reinitialize the system, enter the following command:

'''/opt/ConfigEngine/CSCOcnsie/reinitialize'''

2. To run data restore again, enter the following command:

'''/opt/ConfigEngine/CSCOcnsie/bin/datarestore'''

3. To run the set up program again, enter the following command:

'''/opt/ConfigEngine/CSCOcnsie/setup'''

'''Note''': Make sure that you run the set up program in bash shell. If the shell is not in bash, press ctrl-c to exit. Configure your shell in bash, and then re-run the set up program.

4. When entering the set up parameters, make sure that the country code and the company code information for the new host matches with what is defined on the old host.

'''Note''': The country code and the company code in the OpenLDAP schema are case sensitive.

For detailed information about the parameters in the set up program, see the Cisco Configuration Engine Administration Guide.
<pre>
Example

Choose operational mode of system. 0=internal directory mode,
1=external directory mode. [0]
Enter country code: us
Enter company code: cisco
</pre>

[[Category:Configuration Engine Troubleshooting]]
[[Category:Configuration Engine]]

==Config job failed with parser error==
'''Problem :  '''

The configuration update job failed with “%CNS-3-XML_SEMANTIC: CNS_FW_XML_PARSE_ERROR”

'''Solution :  '''
To resolve this problem, follow these steps:

Step 1 Identify which CLI in the configuration job template caused the error

Step 2 Type that CLI directly on the device config terminal and see whether the CLI is support.

Step 3 If the CLI results an error, it means the CLI is not supported or has problem in the IOS version that the customer is using, report the problem to cns-ios-sw mailer. If the CLI has no problem in executing on the device, report to cs-ce mailer for further debug.

==Config job fails for commands like "show run", "tclsh" etc==
'''Problem : '''

The configuration update job fails for execution commands like "show run", "tclsh" etc and respond back with error messages like "CNS_FW_XML_PARSE_ERROR”, "AUTHORIZATION_FAILURE" etc. The debug of CNS will show errors like "Received malformed or errant xml".

'''Solution : '''
To commands like "show run", "tclsh" are execution commands in the device and are not configurations. These commands cannot be directly executed on the configuration terminal and so should not be pushed as part of configuration update which acts only on configuration. Verify the execution of commands used in configuration update on the configuration terminal of the device.

Troubleshooting Configuration Update

2011-06-13T05:28:31Z

Hsivakum:

To troubleshoot a configuration update, see the following sections:

==Config update failed==
'''Symptom: '''

The Device configuration update fails.

'''Solution: '''

To resolve this problem, follow these steps:

Step 1 Check the following on the Cisco Configuration Engine:

a. Make sure that the Event ID and Config ID match with what is defined on the device.

b. Make sure that the object status for the device in Cisco Configuration Engine is green. Green indicates that the Cisco Configuration Engine and the device are connected.

To verify that TibGate is up and running, enter the following command:

/etc/rc.d/init.d/EvtGateway status

/etc/rc.d/init.d/EvtGatewayCrypto status

Note If encryption is enabled, the TibGate ports begin with even numbers that begin from 11014. If encryption is not enabled, the TibGate ports begin with odd numbers that begin from 11013. Each TibGate port can support a maximum of 500 devices. You specify the number of the TibGates during the Cisco Configuration Engine Setup program. Make sure that the number of devices on each TibGate port does not exceed the maximum. For details, see the "Scalability Among Event Gateway Ports" chapter in the Cisco Configuration Engine Installation and Configuration Guide, 3.5.

d. If the authentication feature is enabled in the Cisco Configuration Engine, make sure that the device password (cns password <password string>) that is defined in the Cisco Configuration Engine user interface, matches with what is defined on the device. Otherwise, use the resync device command to reset the CNS password.

To use the resync command from the Cisco Configuration Engine user interface, do the following:

a. Go to Devices > Resync Device. The Resync Device page appears with a Groups list.

b. From the Groups list, choose the group that contains the device you want to resynchronize. Then click the icon for the device.

c. In the confirmation window, click Ok.

e. Make sure that the downloading configuration semantics and syntax for the device are correct.

If the device in the Cisco Configuration Engine was initially set as None, then deleted, and then re-created as an agent-enabled device, you must rename the Config ID and Event ID on both the device and the Cisco Configuration Engine user interface.

g. If during the Cisco Configuration Engine setup, a port other than the default port 80 is configured for HTTP, make sure that the same port number is also configured on the device.

Step 2

Check the following on the device:

a. Make sure that the following Event ID string is defined:cns id string <id string> cns id string <id string> event
The default value of the <id string> is the hostname of the device. This ID must be the same as the Config ID defined in the Cisco Configuration Engine host.

b. To verify that the Cisco Configuration Engine hostname or IP address is specified to receive events, enter the following command:cns event <configengine hostname> 11011 keepalive 30 10

Note Make sure that the TibGate port of this device is correct. The TibGate port must match the port that is defined in the Cisco Configuration Engine.

c. If the authentication feature is enabled in the Cisco Configuration Engine, make sure that the device password (cns password <password string>) matches what is defined in the Cisco Configuration Engine user interface.

Note You cannot see the password setting after you configure it on the router, nor can you edit the password in Cisco Configuration Engine. Therefore, you must reset the password. To reset the password, use the Resync Device feature in the Cisco Configuration Engine.

d. During the Cisco Configuration Engine setup, if a port other than the default port 80 is configured for HTTP, make sure that the same port number is also configured on the device. To configure the http port on the device, enter the following command:cns config partial <CE hostname> <http port>

Step 3 If you have tried all the preceding steps and the device configuration update still fails, enable the debugging tools.

• In the Cisco Configuration Engine host, do the following:

– To start event listener, enter the following commands:cd $CISCO_CE_INSTALL_ROOT/CSCOcnsie/tools./cns-listen "cisco.>"

– Check the cfgsrv log file. This file is located at: /var/log/CNSCE/cfgsrv/cfgsrv.log.

• In the device, use the debug cns config all command to enable debugging. Analyze the output to verify that the device is set up correctly with proper connectivity.

Step 4 Rerun the scenario, check the event traffic and the information from the device, capture the data, and then contact the Cisco TAC for assistance.

==Config job stuck or The configuration update is stuck in queue after data migration.==

'''Symptom : '''

The configuration update is stuck in queue after data migration.
'''
Solution : '''

After data migration from release 2.0 to 3.5, the OpenLDAP schema is transferred to a new host. To reuse the existing OpenLDAP schema for the new host, make sure that the country code and the company code information on the new host matches what is defined on the old host.

Note The country code and the company code in the OpenLDAP schema are case sensitive.

Step 1 To reinitialize the system, enter the following command:/opt/ConfigEngine/CSCOcnsie/reinitialize

Step 2 To run data migration again, enter the following command:/opt/ConfigEngine/CSCOcnsie/bin/datamigrate

Step 3 To run the Setup program again, enter the following command:/opt/ConfigEngine/CSCOcnsie/setup

Note Make sure that you run the Setup program in bash shell. If the shell is not in bash, press ctrl-c to exit. Configure your shell in bash, and then rerun the Setup program.

Step 4 When entering the Setup parameters, make sure that the country code and the company code information for the new host matches what is defined on the old host.

For detailed information about the parameters in the Setup program, see the Cisco Configuration Engine Administration Guide.

==The configuration update is stuck in the queue after data backup and restore.==
'''Problem : '''

The configuration update is stuck in the queue after data backup and restore.
'''
Solution :  '''

When you back up data and restore it, the OpenLDAP schema is transferred to a new host. To reuse the existing OpenLDAP schema for the new host, make sure that the country code and the company code information on the new host matches what is defined on the old host.

Note The country code and the company code in the OpenLDAP schema are case sensitive.

Step 1 To reinitialize the system, enter the following command:/opt/ConfigEngine/CSCOcnsie/reinitialize

Step 2 To run data restore again, enter the following command:/opt/ConfigEngine/CSCOcnsie/bin/datarestore

Step 3 To run the Setup program again, enter the following command:/opt/ConfigEngine/CSCOcnsie/setup

Note Make sure that you run the Setup program in bash shell. If the shell is not in bash, press ctrl-c to exit. Configure your shell in bash, and then rerun the Setup program.

Step 4 When entering the Setup parameters, make sure that the country code and the company code information for the new host matches what is defined on the old host.

For detailed information about the parameters in the Setup program, see the Cisco Configuration Engine Administration Guide.

==CNS-Enabled Device Unable to Connect with CCE==

'''Problem''': A device is created in the Cisco Configuration Engine user interface but the device indicator displays a red status.

'''Possible Cause''': The red status indicates that the device is unable to connect with Cisco Configuration Engine or it is still trying to connect. A connection delay might occur due to the device setting of the backoff timer. After the time has expired, the indicator does not turn to green, follow the steps given below.

'''Solution''': To resolve this problem, follow these steps:

1. Make sure that the Event ID and Config ID match with what is defined on the device.

Do the following from the Cisco Configuration Engine user interface:

a. Choose '''Devices''' > '''Edit Device'''. The Edit Device page appears with a Groups list.

b. From the Groups list, choose the group that contains the device, then click the icon for the device.

c. From the left pane, choose Edit Information. The Enter Device Information page appears.

d. Click Next. The Select Group Membership page appears.

e. Click Next. The Device IDs page appears.

f. Verify that the Event ID and Config IP match with what is defined on the router.

2. Make sure that the device type is Agent Enabled Device. From the Cisco Configuration Engine user interface, do the following:

a. Choose '''Devices'''>'''Edit Device'''. The Edit Device page appears with a Groups list.

b. From the Groups list, choose the group that contains the device. Then click the icon for the device.

c. From the left pane, choose Edit Information. The Enter Device Information page appears.

d .Verify that the device type is Agent Enabled Device.

3. Ping or telnet to the device to verify that the device is reachable from Cisco Configuration Engine.

4. From the Cisco Configuration Engine server, make sure that TibGate, httpd, and the Java process are up.

* To verify that all TibGates are up, enter the following command:

'''/etc/rc.d/init.d/EvtGateway status'''
'''/etc/rc.d/init.d/EvtGateway status'''

'''Note''': For information about TibGate event gateway ports, see the “Scalability Among Event Gateway Ports” chapter in the Cisco Configuration Engine Installation and Configuration Guide, 3.5.

* To verify that httpd is up, enter the following command:

''''httpd status'''

* To verify that the Java process is up, enter the following command:

'''ps –ef | grep –i java | grep ConfigEngine''''

5. Check the following on the device:

a. Make sure that the following Event ID string is defined:

cns id string <id string>
cns id string <id string> event

The default value of the <id string> is the hostname of the device. This ID must be the same as the Config ID defined in the Cisco Configuration Engine host.

b. To verify that the Cisco Configuration Engine hostname or IP address is specified to receive the events, enter the following command:

''''cns event <configengine hostname or ip address> keepalive 30 10'''

c. To verify that the Cisco Configuration Engine hostname or IP address is reachable from the device, enter the following command:

'''ping <configengine hostname or ip address>'''

d. If you are unable to reach the device through the ping command, use the '''ip host''' command to configure the device:

'''ip host <hostname> <ip address>'''
'''ip host <hostname.domainame> <ip address>'''

e.(Optional) To resolve hostnames, set up the DNS on the device by entering the following command:

'''ip name-server <ip address of DNS>'''

6. If the device status changes from green to red after Cisco Configuration Engine set up, follow the steps in “Device Status” section.

==CNS-Enabled Device Configuration Update Failed==

'''Problem''': The Device configuration update fails.

'''Possible Cause''': This problem can occur for one of the following reasons:

* Invalid commands in the configuration template
* Device is not online (RED)

'''Solution''': To resolve this problem, follow these steps:

If the device appears RED (offline), go to Step 2 and 3 to make the device GREEN (online) before proceeding with step 1.

a. In the Cisco Configuration Engine host, start the event listener and enter the following commands:

'''cd $CISCO_CE_INSTALL_ROOT/CSCOcnsie/tools'''
'''./cns-listen ?cisco.>?'''

Check the cfgsrv log file. This file is located at: /var/log/CNSCE/cfgsrv/cfgsrv.log.
In the device, use the '''debug cns all''' command to enable debugging. If debug messages displays the CNS_INVALID_CLI_CMD as shown below, the config template might contain invalid commands. Apply those commands one by one on the router to find which command failed and remove or fix them from the template.
<pre>
85E1E440: 7572653E 3C696465 6E746966 6965723E ure><identifier>
85E1E450: 31323635 38333937 32393339 32313C2F 12658397293921</
85E1E460: 6964656E 74696669 65723E3C 636F6E66 identifier><conf
85E1E470: 69672D69 643E4643 48313333 39543032 ig-id>myDevice
85E1E480: 383C2F63 6F6E6669 672D6964 3E3C6572 </config-id><er
85E1E490: 726F722D 696E666F 3E3C6C69 6E652D6E ror-info><line-n
85E1E4A0: 756D6265 723E3930 3C2F6C69 6E652D6E umber>90</line-n
85E1E4B0: 756D6265 723E3C65 72726F72 2D6D6573 umber><error-mes
85E1E4C0: 73616765 3E434E53 5F494E56 414C4944 sage>CNS_INVALID
85E1E4D0: 5F434C49 5F434D44 3C2F6572 726F722D _CLI_CMD</error-
85E1E4E0: 6D657373 6167653E 3C2F6572 726F722D message></error-
85E1E4F0: 696E666F 3E3C2F63 6F6E6669 672D6661 info></config-fa
85E1E500: 696C7572 653E ilure>
</pre>

2. Check the following on the Cisco Configuration Engine:

a. Make sure that the Event ID and Config ID match with what is defined on the device.

b. Make sure that the object status for the device in Cisco Configuration Engine is green. Green indicates that the Cisco Configuration Engine and the device are connected.

c. To verify that TibGate is up and running, enter the following command:

'''/etc/rc.d/init.d/EvtGateway status'''
'''/etc/rc.d/init.d/EvtGateway status'''

'''Note''': If encryption is enabled, the TibGate ports begin with even numbers that begin from 11012. If encryption is not enabled, the TibGate ports begin with odd numbers that begin from 11011. Each TibGate port can support a maximum of 500 devices. You specify the number of the TibGates during the Cisco Configuration Engine set up program. Make sure that the number of devices on each TibGate port does not exceed the maximum.

For details, see the “Scalability Among Event Gateway Ports” chapter in the Cisco Configuration Engine Installation and Configuration Guide, 3.5.

d. If the authentication feature is enabled in the Cisco Configuration Engine, make sure that the device password (cns password <password string>) that is defined in the Cisco Configuration Engine user interface, matches with what is defined on the device. Otherwise, use the resync device command to reset the CNS password.

To use the resync command from the Cisco Configuration Engine user interface, do the following:

a. Go to Devices > Resync Device. The Resync Device page appears with a Groups list.

b. From the Groups list, choose the group that contains the device you want to resynchronize. Then click the icon for the device.

c. In the confirmation window, click '''Ok'''.

e. Make sure that the downloading configuration semantics and syntax for the device are correct.

f. If the device in the Cisco Configuration Engine was initially set as '''None''', then deleted, and then re-created as an agent-enabled device, you must rename the Config ID and Event ID on both the device and the Cisco Configuration Engine user interface.

g. During the Cisco Configuration Engine set up, if a port other than the default port 80 is configured for HTTP, make sure that the same port number is also configured on the device.

3. Check the following on the device:

a. Make sure that the following Event ID string is defined:

cns id string <id string>
cns id string <id string> event

The default value of the <id string> is the hostname of the device. This ID must be the same as the Config ID defined in the Cisco Configuration Engine host.

b. To verify that the Cisco Configuration Engine hostname or IP address is specified to receive events, enter the following command:

'''cns event <configengine hostname or ip address> keepalive 30 10'''

'''Note''': Make sure that the TibGate port of this device is correct. The TibGate port must match the port that is defined in the Cisco Configuration Engine.

c. If the authentication feature is enabled in the Cisco Configuration Engine, make sure that the device password (cns password <password string>) matches what is defined in the Cisco Configuration Engine user interface.

'''Note''': You cannot see the password setting after you configure it on the router, nor can you edit the password in Cisco Configuration Engine. Therefore, you must reset the password. To reset the password, use the Resync Device feature in the Cisco Configuration Engine.

d. During the Cisco Configuration Engine set up, if a port other than the default port 80 is configured for HTTP, make sure that the same port number is also configured on the device. To configure the http port on the device, enter the following command:

'''cns config partial <CE hostname> <http port>'''

4. If you have tried all the preceding steps and the device configuration update still fails, enable the debugging tools.

* In the Cisco Configuration Engine host, start the event listener by enter the following commands:

'''cd $CISCO_CE_INSTALL_ROOT/CSCOcnsie/tools'''
'''./cns-listen “cisco.>”'''

* Check the cfgsrv log file. This file is located at: /var/log/CNSCE/cfgsrv/cfgsrv.log.

* In the device, use the debug '''cns config all''' command to enable debugging. Analyze the output to verify that the device is set up correctly with proper connectivity.

5. Re-run the scenario, check the event traffic and the information from the device, capture the data, and then contact the Cisco TAC for assistance.

==Configuration Update Stuck in Queue After Data Migration==

'''Problem''': The configuration update is stuck in queue after data migration.

'''Possible Cause''': This problem can occur if you did not enter the correct country code and company code information during the set up program.

'''Solution''': After data migration from release 3.0 to 3.5, the OpenLDAP schema is transferred to a new host. To reuse the existing OpenLDAP schema for the new host, make sure that the country code and the company code information on the new host matches with what is defined on the old host. Follow these steps:

1. To reinitialize the system, enter the following command:

'''/opt/ConfigEngine/CSCOcnsie/reinitialize'''

2. To run data migration again, enter the following command:

'''/opt/ConfigEngine/CSCOcnsie/bin/datamigrate'''

3. To run the set up program again, enter the following command:

'''opt/ConfigEngine/CSCOcnsie/setup'''

'''Note''': Make sure that you run the set up program in bash shell. If the shell is not in bash, press ctrl-c to exit. Configure your shell in bash, and then re-run the set up program.

4. When entering the set up parameters, make sure that the country code and the company code information for the new host matches with what is defined on the old host.

'''Note''': The country code and the company code in the OpenLDAP schema are case sensitive.

For detailed information about the parameters in the set up program, see the Cisco Configuration Engine Administration Guide.

<pre>
Example:

Choose operational mode of system. 0=internal directory mode,
1=external directory mode. [0]
Enter country code: us
Enter company code: cisco
</pre>

==Configuration Update Stuck in Queue After Data Backup and Restore==

'''Problem''': The configuration update is stuck in the queue after data backup and restore.

'''Possible Cause''': This problem can occur if you did not enter the correct country code and company code information during the set up program.

''''Solution''': When you back up data and restore it, the OpenLDAP schema is transferred to a new host. To re-use the existing OpenLDAP schema for the new host, make sure that the country code and the company code information on the new host matches with what is defined on the old host. Follow these steps:

1. To reinitialize the system, enter the following command:

'''/opt/ConfigEngine/CSCOcnsie/reinitialize'''

2. To run data restore again, enter the following command:

'''/opt/ConfigEngine/CSCOcnsie/bin/datarestore'''

3. To run the set up program again, enter the following command:

'''/opt/ConfigEngine/CSCOcnsie/setup'''

'''Note''': Make sure that you run the set up program in bash shell. If the shell is not in bash, press ctrl-c to exit. Configure your shell in bash, and then re-run the set up program.

4. When entering the set up parameters, make sure that the country code and the company code information for the new host matches with what is defined on the old host.

'''Note''': The country code and the company code in the OpenLDAP schema are case sensitive.

For detailed information about the parameters in the set up program, see the Cisco Configuration Engine Administration Guide.
<pre>
Example

Choose operational mode of system. 0=internal directory mode,
1=external directory mode. [0]
Enter country code: us
Enter company code: cisco
</pre>

[[Category:Configuration Engine Troubleshooting]]
[[Category:Configuration Engine]]

==Config job failed with parser error==
'''Problem :  '''

The configuration update job failed with “%CNS-3-XML_SEMANTIC: CNS_FW_XML_PARSE_ERROR”

'''Solution :  '''
To resolve this problem, follow these steps:

Step 1 Identify which CLI in the configuration job template caused the error

Step 2 Type that CLI directly on the device config terminal and see whether the CLI is support.

Step 3 If the CLI results an error, it means the CLI is not supported or has problem in the IOS version that the customer is using, report the problem to cns-ios-sw mailer. If the CLI has no problem in executing on the device, report to cs-ce mailer for further debug.

==Config job fails for commands like "show run", "tclsh" etc==
'''Problem : '''

The configuration update job fails for execution commands like "show run", "tclsh" etc and respond back with error messages like "CNS_FW_XML_PARSE_ERROR”, "AUTHORIZATION_FAILURE" etc.

'''Solution : '''
To commands like "show run", "tclsh" are execution commands in the device and are not configurations. These commands cannot be directly executed on the configuration terminal and so should not be pushed as part of configuration update which acts only on configuration. Verify the execution of commands used in configuration update on the configuration terminal of the device.

Cisco Configuration Engine -- Troubleshooting

2011-05-31T05:02:36Z

Hsivakum: /* Contents */

__TOC__

==Introduction==

The Cisco Configuration Engine is a network management software that acts as a configuration service for automating the deployment, management, and upgrading of network devices and services. Each Configuration Engine manages a group of Cisco devices (switches and routers) and the services that they deliver, storing their configurations and delivering them as needed. The Cisco Configuration Engine automates initial configurations and configuration updates by generating device-specific configuration changes, sending them to the device, executing the configuration change, and logging the results.

==Contents==

This document contains troubleshooting information for the Cisco Configuration Engine. It contains the following sections:
* [[Cisco Configuration Engine -- Troubleshooting Installation Checks]]
* [[Troubleshooting Cisco Configuration Engine Installation]]
* [[Troubleshooting_Logging_and_Connection_Issues|Troubleshooting Logging and Connection Issues]]
*[[Troubleshooting_the_Open_Lightweight_Directory_Access_Protocol_and_the_Berkeley_Data_Base|Troubleshooting the Open Lightweight Directory Access Protocol and the Berkeley Data Base]]
* [[Troubleshooting_the_Cisco_Configuration_Engine_Services|Troubleshooting the Cisco Configuration Engine Services]]
* [[Troubleshooting_the_General|Troubleshooting the Cisco Configuration Engine Services for General issues]]
* [[Troubleshooting_the_Web_Services|Troubleshooting the Web Services]]
* [[Troubleshooting_the_Initial_Configuration|Troubleshooting the Initial Configuration]]
* [[Troubleshooting_Configuration_Update|Troubleshooting Configuration Update]]
* [[Troubleshooting_an_Image_Update|Troubleshooting an Image Update]]
* [[Troubleshooting_IMGW|Troubleshooting IMGW]]
* [[Troubleshooting_the_Router|Troubleshooting the Router]]
* [[ASA_Configuration_Troubleshooting|ASA Configuration/Image/ASDM image upgrade Troubleshooting]]
* [[General_Troubleshooting|General Troubleshooting]]

'''Note:''' This is not an administration manual. For comprehensive information about administering the Cisco Configuration Engine, see the Cisco Configuration Engine Administration Guide at ''http://www.cisco.com/en/US/docs/net_mgmt/configuration_engine/3.5/administration/guide/CE_ag.html''.

==Checking the Version Number==

To check the version number of the Cisco Configuration Engine software, do one of the following:
*Start the Cisco Configuration Engine application, and look for the version number in the displayed login screen.
*Use the version command. This command is located in the '''cd $CISCO_CE_INSTALL_ROOT/CSCOcnsie/bin''' directory.

[[Category:Configuration Engine Troubleshooting]]
[[Category:Configuration Engine]]

Cisco Configuration Engine -- Troubleshooting Installation Checks

2011-05-31T04:48:34Z

Hsivakum: /* Root User Check */

==Troubleshooting Installation Checks==

This section describes the installation checks performed by ce_install.sh and ce_check.sh scripts. To troubleshoot by using the installation checks script, see the following sections:

==Root User and System Check==

If the user trying to install or run the check install script is not a root user, the following error message is displayed:

Reading XML file ./installRule.linux5.xml
check Root user..........
Error!!! Only user "root" can run check script!
The root user option should be used to install the Cisco CE.
Check for OS, CPU, RAM, and Disk space

The install and check install script validates the OS, CPU speed, RAM, and disk space usage to ensure that the configuration requirements are sufficient to install the Cisco Configuration Engine. The example below shows that the minimum RAM requirement is not meet within Cisco Configuration Engine.

System Requirement Check :
check OS.......... ok
check CPU.......... ok
check Ram.......... Error the machine has only 515536 Kbytes memory.
Minimum requirement: 2000000 Kbytes.
check Disk Space '/var/tmp'.......... ok
Check the system requirements and provide the proper
configuration to install the Cisco Configuration Engine.

==Checks for dependent and CE Packages==

The install and check install scripts will check if any of the Cisco Configuration Engine packages are already installed and displays the warning message as shown below:

Below lists package(s) which should not exist before CE 3.5.3 install.
Please remove them before running CE 3.5.3 installation script.

...... package: SUNJava2-SDK, existing version: 1.6.0_05-0
...... package: mod_jk2, existing version: 2.0.4-4jpp_4rh
...... package: CSCOcnscfgs, existing version: 1.4-0
...... package: ACE, existing version: 5.6.0-0
...... package: CSCOadmincommon, existing version: 1.3-0
...... package: CSCOcnscommon, existing version: 1.4-0
...... package: CSCOcnses, existing version: 1.9-0
...... package: CSCOcnsnsm, existing version: 1.5-0
...... package: CSCOcnsimgs, existing version: 1.5-0
...... package: CSCOcnspki, existing version: 1.3-0
...... package: CSCOdat, existing version: 1.3-0
...... package: CSCOemail, existing version: 1.0-0
...... package: CSCOencryption, existing version: 1.4-1
...... package: CSCOGroupAdmin, existing version: 1.5-1
...... package: CSCOimgw, existing version: 1.4-0.0
...... package: CSCOImgwConfig, existing version: 1.4-0.0
...... package: CSCOImgwDeviceServer, existing version: 1.4-0.0
...... package: CSCOnsmAdmin, existing version: 1.0-0
...... package: CSCOsrvr, existing version: 1.5-0
...... package: CSCOTools, existing version: 1.2-0
...... package: CSCOudiAdmin, existing version: 1.0-0
...... package: xerces-c, existing version: 2.8-0

Uninstall the Cisco CE properly and then try to install or run the install check script.

==Check for Dependent OS Packages==

The Cisco Configuration Engine install and check install script will check for the OS dependent packages and display error messages if the required packages are not installed.

Below lists package(s) which should be shared between CE and other projects. It is now detected that these component(s) are not installed or of
different version from that required by Configuration Engine. Please remove the inappropriate packages and install required packages before re-running
Configuration Engine installation script.

...... package: httpd, existing version: not installed
...... expected version: 2.0.52
...... package: httpd-suexec, existing version: not installed
...... expected version: 2.0.52
...... package: mod_ssl, existing version: not installed
...... expected version: 2.0.52

Install the three missing package mentioned above from your Operating System distribution mentioned below.
Red Hat Enterprise Linux AS release 4 (Nahant Update 6)

The customer should install the required packages from the Red Hat Distribution Media or RPM Package Manager like 'yum'.

The check install script will check for the OS package being installed on the system.

Package 'httpd'is shared...
/bin/rpm -V httpd
S.5....T c /etc/rc.d/init.d/httpd
..?..... /usr/sbin/suexec
system failed: 256 exit_value = 1 signal_num = 0 dumped_core = 0
Following command failed: see ./checkError.log for details
/bin/rpm -V httpd
Warning package httpd is not properly installed
Run the command '/bin/rpm -V httpd' to see the issues

Verify the error to see if the configurations are changed and reinstall the packages accordingly.

==Check for OS Dependent Package Files Missing==

The check install script will check for any missing files from the OS package that is installed on the system.

Package 'mod_ssl'is shared...
/bin/rpm -V mod_ssl
S.5....T c /etc/httpd/conf.d/ssl.conf
system failed: 256 exit_value = 1 signal_num = 0 dumped_core = 0
Following command failed: see ./checkError.log for details
/bin/rpm -V mod_ssl
Warning package mod_ssl is not properly installed
Run the command '/bin/rpm -V mod_ssl' to see the issues
Error file or directory /usr/lib/httpd/modules/mod_ssl.so doesn't exist
Please re-install the mod_ssl from your Operating System distribution mentioned below.
Red Hat Enterprise Linux Server release 5.2 (Tikanga)
Reinstall the package properly from the OS distribution.

[[Category:Configuration Engine Troubleshooting]]
[[Category:Configuration Engine]]

Cisco Configuration Engine -- Troubleshooting Installation Checks

2011-05-31T04:48:01Z

Hsivakum: /* Checks for dependent and CE Packages */

==Troubleshooting Installation Checks==

This section describes the installation checks performed by ce_install.sh and ce_check.sh scripts. To troubleshoot by using the installation checks script, see the following sections:

==Root User Check==

If the user trying to install or run the check install script is not a root user, the following error message is displayed:

Reading XML file ./installRule.linux5.xml
check Root user..........
Error!!! Only user "root" can run check script!
The root user option should be used to install the Cisco CE.
Check for OS, CPU, RAM, and Disk space

The install and check install script validates the OS, CPU speed, RAM, and disk space usage to ensure that the configuration requirements are sufficient to install the Cisco Configuration Engine. The example below shows that the minimum RAM requirement is not meet within Cisco Configuration Engine.

System Requirement Check :
check OS.......... ok
check CPU.......... ok
check Ram.......... Error the machine has only 515536 Kbytes memory.
Minimum requirement: 2000000 Kbytes.
check Disk Space '/var/tmp'.......... ok
Check the system requirements and provide the proper
configuration to install the Cisco Configuration Engine.

==Checks for dependent and CE Packages==

The install and check install scripts will check if any of the Cisco Configuration Engine packages are already installed and displays the warning message as shown below:

Below lists package(s) which should not exist before CE 3.5.3 install.
Please remove them before running CE 3.5.3 installation script.

...... package: SUNJava2-SDK, existing version: 1.6.0_05-0
...... package: mod_jk2, existing version: 2.0.4-4jpp_4rh
...... package: CSCOcnscfgs, existing version: 1.4-0
...... package: ACE, existing version: 5.6.0-0
...... package: CSCOadmincommon, existing version: 1.3-0
...... package: CSCOcnscommon, existing version: 1.4-0
...... package: CSCOcnses, existing version: 1.9-0
...... package: CSCOcnsnsm, existing version: 1.5-0
...... package: CSCOcnsimgs, existing version: 1.5-0
...... package: CSCOcnspki, existing version: 1.3-0
...... package: CSCOdat, existing version: 1.3-0
...... package: CSCOemail, existing version: 1.0-0
...... package: CSCOencryption, existing version: 1.4-1
...... package: CSCOGroupAdmin, existing version: 1.5-1
...... package: CSCOimgw, existing version: 1.4-0.0
...... package: CSCOImgwConfig, existing version: 1.4-0.0
...... package: CSCOImgwDeviceServer, existing version: 1.4-0.0
...... package: CSCOnsmAdmin, existing version: 1.0-0
...... package: CSCOsrvr, existing version: 1.5-0
...... package: CSCOTools, existing version: 1.2-0
...... package: CSCOudiAdmin, existing version: 1.0-0
...... package: xerces-c, existing version: 2.8-0

Uninstall the Cisco CE properly and then try to install or run the install check script.

==Check for Dependent OS Packages==

The Cisco Configuration Engine install and check install script will check for the OS dependent packages and display error messages if the required packages are not installed.

Below lists package(s) which should be shared between CE and other projects. It is now detected that these component(s) are not installed or of
different version from that required by Configuration Engine. Please remove the inappropriate packages and install required packages before re-running
Configuration Engine installation script.

...... package: httpd, existing version: not installed
...... expected version: 2.0.52
...... package: httpd-suexec, existing version: not installed
...... expected version: 2.0.52
...... package: mod_ssl, existing version: not installed
...... expected version: 2.0.52

Install the three missing package mentioned above from your Operating System distribution mentioned below.
Red Hat Enterprise Linux AS release 4 (Nahant Update 6)

The customer should install the required packages from the Red Hat Distribution Media or RPM Package Manager like 'yum'.

The check install script will check for the OS package being installed on the system.

Package 'httpd'is shared...
/bin/rpm -V httpd
S.5....T c /etc/rc.d/init.d/httpd
..?..... /usr/sbin/suexec
system failed: 256 exit_value = 1 signal_num = 0 dumped_core = 0
Following command failed: see ./checkError.log for details
/bin/rpm -V httpd
Warning package httpd is not properly installed
Run the command '/bin/rpm -V httpd' to see the issues

Verify the error to see if the configurations are changed and reinstall the packages accordingly.

==Check for OS Dependent Package Files Missing==

The check install script will check for any missing files from the OS package that is installed on the system.

Package 'mod_ssl'is shared...
/bin/rpm -V mod_ssl
S.5....T c /etc/httpd/conf.d/ssl.conf
system failed: 256 exit_value = 1 signal_num = 0 dumped_core = 0
Following command failed: see ./checkError.log for details
/bin/rpm -V mod_ssl
Warning package mod_ssl is not properly installed
Run the command '/bin/rpm -V mod_ssl' to see the issues
Error file or directory /usr/lib/httpd/modules/mod_ssl.so doesn't exist
Please re-install the mod_ssl from your Operating System distribution mentioned below.
Red Hat Enterprise Linux Server release 5.2 (Tikanga)
Reinstall the package properly from the OS distribution.

[[Category:Configuration Engine Troubleshooting]]
[[Category:Configuration Engine]]

Cisco Configuration Engine -- Troubleshooting Installation Checks

2011-05-31T04:47:15Z

Hsivakum: /* Check for Dependent OS Packages */

==Troubleshooting Installation Checks==

This section describes the installation checks performed by ce_install.sh and ce_check.sh scripts. To troubleshoot by using the installation checks script, see the following sections:

==Root User Check==

If the user trying to install or run the check install script is not a root user, the following error message is displayed:

Reading XML file ./installRule.linux5.xml
check Root user..........
Error!!! Only user "root" can run check script!
The root user option should be used to install the Cisco CE.
Check for OS, CPU, RAM, and Disk space

The install and check install script validates the OS, CPU speed, RAM, and disk space usage to ensure that the configuration requirements are sufficient to install the Cisco Configuration Engine. The example below shows that the minimum RAM requirement is not meet within Cisco Configuration Engine.

System Requirement Check :
check OS.......... ok
check CPU.......... ok
check Ram.......... Error the machine has only 515536 Kbytes memory.
Minimum requirement: 2000000 Kbytes.
check Disk Space '/var/tmp'.......... ok
Check the system requirements and provide the proper
configuration to install the Cisco Configuration Engine.

==Checks for dependent and CE Packages==

The install and check install scripts will check if any of the Cisco Configuration Engine packages are already installed and displays the warning message as shown below:

Below lists package(s) which should not exist before CE 3.5.3 install.
Please remove them before running CE 3.5.3 installation script.

...... package: SUNJava2-SDK, existing version: 1.6.0_05-0
...... package: mod_jk2, existing version: 2.0.4-4jpp_4rh
...... package: CSCOcnscfgs, existing version: 1.4-0
...... package: ACE, existing version: 5.6.0-0
...... package: CSCOadmincommon, existing version: 1.3-0
...... package: CSCOcnscommon, existing version: 1.4-0
...... package: CSCOcnses, existing version: 1.9-0
...... package: CSCOcnsnsm, existing version: 1.5-0
...... package: CSCOcnsimgs, existing version: 1.5-0
...... package: CSCOcnspki, existing version: 1.3-0
...... package: CSCOdat, existing version: 1.3-0
...... package: CSCOemail, existing version: 1.0-0
...... package: CSCOencryption, existing version: 1.4-1
...... package: CSCOGroupAdmin, existing version: 1.5-1
...... package: CSCOimgw, existing version: 1.4-0.0
...... package: CSCOImgwConfig, existing version: 1.4-0.0
...... package: CSCOImgwDeviceServer, existing version: 1.4-0.0
...... package: CSCOnsmAdmin, existing version: 1.0-0
...... package: CSCOsrvr, existing version: 1.5-0
...... package: CSCOTools, existing version: 1.2-0
...... package: CSCOudiAdmin, existing version: 1.0-0
...... package: xerces-c, existing version: 2.8-0

Uninstall the Cisco CE properly and then try to install or run the install check script.

==Check for Dependent OS Packages==

The Cisco Configuration Engine install and check install script will check for the OS dependent packages and display error messages if the required packages are not installed.

Below lists package(s) which should be shared between CE and other projects. It is now detected that these component(s) are not installed or of
different version from that required by Configuration Engine. Please remove the inappropriate packages and install required packages before re-running
Configuration Engine installation script.

...... package: httpd, existing version: not installed
...... expected version: 2.0.52
...... package: httpd-suexec, existing version: not installed
...... expected version: 2.0.52
...... package: mod_ssl, existing version: not installed
...... expected version: 2.0.52

Install the three missing package mentioned above from your Operating System distribution mentioned below.
Red Hat Enterprise Linux AS release 4 (Nahant Update 6)

The customer should install the required packages from the Red Hat Distribution Media or RPM Package Manager like 'yum'.

The check install script will check for the OS package being installed on the system.

Package 'httpd'is shared...
/bin/rpm -V httpd
S.5....T c /etc/rc.d/init.d/httpd
..?..... /usr/sbin/suexec
system failed: 256 exit_value = 1 signal_num = 0 dumped_core = 0
Following command failed: see ./checkError.log for details
/bin/rpm -V httpd
Warning package httpd is not properly installed
Run the command '/bin/rpm -V httpd' to see the issues

Verify the error to see if the configurations are changed and reinstall the packages accordingly.

==Check for OS Dependent Package Files Missing==

The check install script will check for any missing files from the OS package that is installed on the system.

Package 'mod_ssl'is shared...
/bin/rpm -V mod_ssl
S.5....T c /etc/httpd/conf.d/ssl.conf
system failed: 256 exit_value = 1 signal_num = 0 dumped_core = 0
Following command failed: see ./checkError.log for details
/bin/rpm -V mod_ssl
Warning package mod_ssl is not properly installed
Run the command '/bin/rpm -V mod_ssl' to see the issues
Error file or directory /usr/lib/httpd/modules/mod_ssl.so doesn't exist
Please re-install the mod_ssl from your Operating System distribution mentioned below.
Red Hat Enterprise Linux Server release 5.2 (Tikanga)
Reinstall the package properly from the OS distribution.

[[Category:Configuration Engine Troubleshooting]]
[[Category:Configuration Engine]]

Cisco Configuration Engine -- Troubleshooting Installation Checks

2011-05-31T04:44:56Z

Hsivakum: /* Check for Dependent OS Packages */

==Troubleshooting Installation Checks==

This section describes the installation checks performed by ce_install.sh and ce_check.sh scripts. To troubleshoot by using the installation checks script, see the following sections:

==Root User Check==

If the user trying to install or run the check install script is not a root user, the following error message is displayed:

Reading XML file ./installRule.linux5.xml
check Root user..........
Error!!! Only user "root" can run check script!
The root user option should be used to install the Cisco CE.
Check for OS, CPU, RAM, and Disk space

The install and check install script validates the OS, CPU speed, RAM, and disk space usage to ensure that the configuration requirements are sufficient to install the Cisco Configuration Engine. The example below shows that the minimum RAM requirement is not meet within Cisco Configuration Engine.

System Requirement Check :
check OS.......... ok
check CPU.......... ok
check Ram.......... Error the machine has only 515536 Kbytes memory.
Minimum requirement: 2000000 Kbytes.
check Disk Space '/var/tmp'.......... ok
Check the system requirements and provide the proper
configuration to install the Cisco Configuration Engine.

==Checks for dependent and CE Packages==

The install and check install scripts will check if any of the Cisco Configuration Engine packages are already installed and displays the warning message as shown below:

Below lists package(s) which should not exist before CE 3.5.3 install.
Please remove them before running CE 3.5.3 installation script.

...... package: SUNJava2-SDK, existing version: 1.6.0_05-0
...... package: mod_jk2, existing version: 2.0.4-4jpp_4rh
...... package: CSCOcnscfgs, existing version: 1.4-0
...... package: ACE, existing version: 5.6.0-0
...... package: CSCOadmincommon, existing version: 1.3-0
...... package: CSCOcnscommon, existing version: 1.4-0
...... package: CSCOcnses, existing version: 1.9-0
...... package: CSCOcnsnsm, existing version: 1.5-0
...... package: CSCOcnsimgs, existing version: 1.5-0
...... package: CSCOcnspki, existing version: 1.3-0
...... package: CSCOdat, existing version: 1.3-0
...... package: CSCOemail, existing version: 1.0-0
...... package: CSCOencryption, existing version: 1.4-1
...... package: CSCOGroupAdmin, existing version: 1.5-1
...... package: CSCOimgw, existing version: 1.4-0.0
...... package: CSCOImgwConfig, existing version: 1.4-0.0
...... package: CSCOImgwDeviceServer, existing version: 1.4-0.0
...... package: CSCOnsmAdmin, existing version: 1.0-0
...... package: CSCOsrvr, existing version: 1.5-0
...... package: CSCOTools, existing version: 1.2-0
...... package: CSCOudiAdmin, existing version: 1.0-0
...... package: xerces-c, existing version: 2.8-0

Uninstall the Cisco CE properly and then try to install or run the install check script.

==Check for Dependent OS Packages==

The Cisco Configuration Engine install and check install script will check for the OS dependent packages and display error messages if the required packages are not installed.

Below lists package(s) which should be shared between CE and other projects. It is now detected that these component(s) are not installed or of
different version from that required by Configuration Engine. Please remove the inappropriate packages and install required packages before re-running
Configuration Engine installation script.

...... package: httpd, existing version: not installed
...... expected version: 2.0.52
...... package: httpd-suexec, existing version: not installed
...... expected version: 2.0.52
...... package: mod_ssl, existing version: not installed
...... expected version: 2.0.52

Install the three missing package mentioned above from your Operating System distribution mentioned below.
Red Hat Enterprise Linux AS release 4 (Nahant Update 6)

Install the required software from the distribution supported by the customer.

The check install script will check for the OS package being installed on the system.

Package 'httpd'is shared...
/bin/rpm -V httpd
S.5....T c /etc/rc.d/init.d/httpd
..?..... /usr/sbin/suexec
system failed: 256 exit_value = 1 signal_num = 0 dumped_core = 0
Following command failed: see ./checkError.log for details
/bin/rpm -V httpd
Warning package httpd is not properly installed
Run the command '/bin/rpm -V httpd' to see the issues

Verify the error to see if the configurations are changed and reinstall the packages accordingly.

==Check for OS Dependent Package Files Missing==

The check install script will check for any missing files from the OS package that is installed on the system.

Package 'mod_ssl'is shared...
/bin/rpm -V mod_ssl
S.5....T c /etc/httpd/conf.d/ssl.conf
system failed: 256 exit_value = 1 signal_num = 0 dumped_core = 0
Following command failed: see ./checkError.log for details
/bin/rpm -V mod_ssl
Warning package mod_ssl is not properly installed
Run the command '/bin/rpm -V mod_ssl' to see the issues
Error file or directory /usr/lib/httpd/modules/mod_ssl.so doesn't exist
Please re-install the mod_ssl from your Operating System distribution mentioned below.
Red Hat Enterprise Linux Server release 5.2 (Tikanga)
Reinstall the package properly from the OS distribution.

[[Category:Configuration Engine Troubleshooting]]
[[Category:Configuration Engine]]

Troubleshooting Cisco Configuration Engine Installation

2011-05-30T04:58:59Z

Hsivakum: /* Setup fails in start of httpd for wrong elfclass */

=='gethostbyaddr()' error==

'''Symptom:'''

Installation aborted with error message “Hostname value retrieval by system calls 'gethostbyaddr()' and command 'hostname' have different values returned. Please correct it also make sure 'ifconfig' is set in your PATH before installing Config Engine 3.5”

'''Solution: '''

To resolve this problem, follow these steps:

Step 1 Make sure the hostnames configured in /etc/hosts, /etc/sysconfig/network and/or DNS server are consistent with what’s returned by “hostname –s” command.

Step 2 Make sure the ifconfig command is in the $PATH environment variable

==Can’t reinstall CE==
'''Symptom:'''

If a install shell is accidentally closed, reinstall is not allowed.

'''Solution: '''

To resolve this problem, follow these steps:

Step 1 use ce_uninstall –force to uninstall any partially installed packages and rerun ce_install.sh again.

Note: If the user typed ^Z to suspend the install process in the background, they need to either resume the install process or kill the install process.

==Setup fails in start of httpd with library errors==
'''Symptom:'''

While setting up of Cisco Configuration Engine version 3.5.2 or lower on Red Hat Enterprise Linux Version 5,the setup fails with appliance-setup.log showing httpd start error as mentioned below.

Starting httpd: /usr/sbin/httpd: error while loading shared libraries: libpq.so.4: cannot open shared object file: No such file or directory

'''Solution: '''

The problem is due to missing Red Hat packages on the Red Hat Enterprise Linux.
To resolve this problem, follow these steps:

Step 1 Use ce_uninstall to uninstall all installed packages.

Step 2 Install the "postgresql-libs" and "mailcap" rpm for the Red Hat Enterprise Linux Distribution.

Step 3 Rerun the ce_install.sh again to install Cisco Configuration Engine.

Step 4 Launch a new root user Session and enter into a new bash shell.

Step 5 Execute the setup.sh command on the bash shell.

==Setup or Resetup of Cisco Configuration Engine fails ==
'''Symptom:'''

The setup/resetup fails with appliance-setup.log showing httpd failure and java not found errors as mentioned below.

/etc/rc.d/init.d/httpd start
Checking if the following ports have been cleared:8009 8005 Starting tomcat...Waiting for tomcat to initialize...
Starting httpd: FAILED
system failed: 256 exit_value = 1 signal_num = 0 dumped_core = 0

Deploying config web services ...
/opt/ConfigEngine/CSCOcnsie/bin/deploy.config.websvc [-wsdl]
./adminclient.sh: line 18: java: command not found

'''Solution: '''

The problem is due to non execution of a new bash shell to source the environment variables added by Cisco Configuration Engine.
To resolve this problem, follow these steps:

Step 1 Launch a new root user Session and enter into a new bash shell.

Step 2 Execute the setup.sh command on the new bash shell created.

==Setup fails in start of httpd for wrong ELF class==
'''Symptom:'''

While setting up of Cisco Configuration Engine on Red Hat Enterprise Linux the setup fails with appliance-setup.log showing httpd start error as mentioned below.

Starting httpd: httpd: Syntax error on line 1383 of /opt/ConfigEngine/CSCOcnsie/httpd/conf/httpd.conf:
Syntax error on line 10 of /opt/ConfigEngine/tomcat/conf/mod_jk-ce.conf: Cannot load /opt/ConfigEngine/CSCOcnsie/httpd/modules/mod_jk.so
into server: /opt/ConfigEngine/CSCOcnsie/httpd/modules/mod_jk.so: wrong ELF class: ELFCLASS32

'''Solution: '''

The problem is due to installation of Cisco Configuration Engine on 64 bit architecture(x86_64). Cisco Configuration Engine is supported only on 32 bit architecture(i386). Install the correct version of Red Hat Enterprise Linux before installing Configuration Engine.

Troubleshooting Cisco Configuration Engine Installation

2011-05-30T04:53:33Z

Hsivakum:

=='gethostbyaddr()' error==

'''Symptom:'''

Installation aborted with error message “Hostname value retrieval by system calls 'gethostbyaddr()' and command 'hostname' have different values returned. Please correct it also make sure 'ifconfig' is set in your PATH before installing Config Engine 3.5”

'''Solution: '''

To resolve this problem, follow these steps:

Step 1 Make sure the hostnames configured in /etc/hosts, /etc/sysconfig/network and/or DNS server are consistent with what’s returned by “hostname –s” command.

Step 2 Make sure the ifconfig command is in the $PATH environment variable

==Can’t reinstall CE==
'''Symptom:'''

If a install shell is accidentally closed, reinstall is not allowed.

'''Solution: '''

To resolve this problem, follow these steps:

Step 1 use ce_uninstall –force to uninstall any partially installed packages and rerun ce_install.sh again.

Note: If the user typed ^Z to suspend the install process in the background, they need to either resume the install process or kill the install process.

==Setup fails in start of httpd with library errors==
'''Symptom:'''

While setting up of Cisco Configuration Engine version 3.5.2 or lower on Red Hat Enterprise Linux Version 5,the setup fails with appliance-setup.log showing httpd start error as mentioned below.

Starting httpd: /usr/sbin/httpd: error while loading shared libraries: libpq.so.4: cannot open shared object file: No such file or directory

'''Solution: '''

The problem is due to missing Red Hat packages on the Red Hat Enterprise Linux.
To resolve this problem, follow these steps:

Step 1 Use ce_uninstall to uninstall all installed packages.

Step 2 Install the "postgresql-libs" and "mailcap" rpm for the Red Hat Enterprise Linux Distribution.

Step 3 Rerun the ce_install.sh again to install Cisco Configuration Engine.

Step 4 Launch a new root user Session and enter into a new bash shell.

Step 5 Execute the setup.sh command on the bash shell.

==Setup or Resetup of Cisco Configuration Engine fails ==
'''Symptom:'''

The setup/resetup fails with appliance-setup.log showing httpd failure and java not found errors as mentioned below.

/etc/rc.d/init.d/httpd start
Checking if the following ports have been cleared:8009 8005 Starting tomcat...Waiting for tomcat to initialize...
Starting httpd: FAILED
system failed: 256 exit_value = 1 signal_num = 0 dumped_core = 0

Deploying config web services ...
/opt/ConfigEngine/CSCOcnsie/bin/deploy.config.websvc [-wsdl]
./adminclient.sh: line 18: java: command not found

'''Solution: '''

The problem is due to non execution of a new bash shell to source the environment variables added by Cisco Configuration Engine.
To resolve this problem, follow these steps:

Step 1 Launch a new root user Session and enter into a new bash shell.

Step 2 Execute the setup.sh command on the new bash shell created.

==Setup fails in start of httpd for wrong elfclass==
'''Symptom:'''

While setting up of Cisco Configuration Engine on Red Hat Enterprise Linux the setup fails with appliance-setup.log showing httpd start error as mentioned below.

Starting httpd: httpd: Syntax error on line 1383 of /opt/ConfigEngine/CSCOcnsie/httpd/conf/httpd.conf:
Syntax error on line 10 of /opt/ConfigEngine/tomcat/conf/mod_jk-ce.conf: Cannot load /opt/ConfigEngine/CSCOcnsie/httpd/modules/mod_jk.so
into server: /opt/ConfigEngine/CSCOcnsie/httpd/modules/mod_jk.so: wrong ELF class: ELFCLASS32

'''Solution: '''

The problem is due to installation of Cisco Configuration Engine on 64 bit architecture(x86_64). Cisco Configuration Engine is supported only on 32 bit architecture(i386). Install the correct version of Red Hat Enterprise Linux before installing Configuration Engine.

Cisco Configuration Engine -- Troubleshooting

2011-05-25T06:48:21Z

Hsivakum: /* Contents */

__TOC__

==Introduction==

The Cisco Configuration Engine is a network management software that acts as a configuration service for automating the deployment, management, and upgrading of network devices and services. Each Configuration Engine manages a group of Cisco devices (switches and routers) and the services that they deliver, storing their configurations and delivering them as needed. The Cisco Configuration Engine automates initial configurations and configuration updates by generating device-specific configuration changes, sending them to the device, executing the configuration change, and logging the results.

==Contents==

This document contains troubleshooting information for the Cisco Configuration Engine. It contains the following sections:
* [[Troubleshooting Cisco Configuration Engine Installation]]
* [[Troubleshooting_Logging_and_Connection_Issues|Troubleshooting Logging and Connection Issues]]
* [[Cisco Configuration Engine -- Troubleshooting Installation Checks]]
*[[Troubleshooting_the_Open_Lightweight_Directory_Access_Protocol_and_the_Berkeley_Data_Base|Troubleshooting the Open Lightweight Directory Access Protocol and the Berkeley Data Base]]
* [[Troubleshooting_the_Cisco_Configuration_Engine_Services|Troubleshooting the Cisco Configuration Engine Services]]
* [[Troubleshooting_the_General|Troubleshooting the Cisco Configuration Engine Services for General issues]]
* [[Troubleshooting_the_Web_Services|Troubleshooting the Web Services]]
* [[Troubleshooting_the_Initial_Configuration|Troubleshooting the Initial Configuration]]
* [[Troubleshooting_Configuration_Update|Troubleshooting Configuration Update]]
* [[Troubleshooting_an_Image_Update|Troubleshooting an Image Update]]
* [[Troubleshooting_IMGW|Troubleshooting IMGW]]
* [[Troubleshooting_the_Router|Troubleshooting the Router]]
* [[ASA_Configuration_Troubleshooting|ASA Configuration/Image/ASDM image upgrade Troubleshooting]]
* [[General_Troubleshooting|General Troubleshooting]]

'''Note:''' This is not an administration manual. For comprehensive information about administering the Cisco Configuration Engine, see the Cisco Configuration Engine Administration Guide at ''http://www.cisco.com/en/US/docs/net_mgmt/configuration_engine/3.5/administration/guide/CE_ag.html''.

==Checking the Version Number==

To check the version number of the Cisco Configuration Engine software, do one of the following:
*Start the Cisco Configuration Engine application, and look for the version number in the displayed login screen.
*Use the version command. This command is located in the '''cd $CISCO_CE_INSTALL_ROOT/CSCOcnsie/bin''' directory.

[[Category:Configuration Engine Troubleshooting]]
[[Category:Configuration Engine]]

Troubleshooting the Open Lightweight Directory Access Protocol and the Berkeley Data Base

2011-05-19T11:03:54Z

Hsivakum:

To troubleshoot Open Lightweight Directory Access Protocol (OpenLDAP) and Berkeley Data Base (BDB), see the following sections:

==OpenLDAP Server Not Responding==

'''Problem''': The OpenLDAP server is not responding.

'''Possible Cause''': This problem could occur if, after a system crash, power outage, or manual shutdown, the OpenLDAP sever did not shut down gracefully, which caused data corruption.

'''Solution''': To resolve this problem, stop the OpenLDAP server, and then recover the data. Follow these steps:

1. To stop the OpenLDAP server, enter the following command:

'''/etc/init.d/NetAppOpenLDAP stop'''

2. To recover the data, enter the following command:

'''$CISCO_CE_INSTALL_ROOT/bdb/bin/db_recover -h'''
'''$CISCO_CE_INSTALL_ROOT/openldap/var/openldap-data'''

==BDB Using Excessive Disk Space==

'''Problem''': The BDB is using excessive disk space.

'''Possible Cause''': BDB creates transaction logs in the $CISCO_CE_INSTALL_ROOT/openldap/var/openldap-data file. If transaction logs are not purged, the BDB uses excessive disk space.
For information about disk space, see the “System Requirements” and “Understanding Disk Space Calculation” sections in the Cisco Configuration Engine Installation and Configuration Guide, 3.5.

'''Solution''': To resolve this problem, follow these steps:

1. To verify whether dbpurge.sh is running as a cron job, enter the following command:

'''crontab –l'''

2. If '''crontab –l''' is not in the list, run the Setup program to add it.

3. To manually purge BDB transaction logs, enter the following command:

'''$CISCO_CE_INSTALL_ROOT/CSCOcnsie/bin/dbpurge.sh'''

==OpenLDAP Server throws error during setup of Configuration Engine on Solaris==

'''Problem''': During Setup of Solaris server the appliance-setup.log reports "javax.naming.NamingException: [LDAP: error code" as mentioned below

javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3005)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2951)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2753)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2667)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:287)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:82)
at com.cisco.cns.dat.DATConfigurator.loadConfigAppSettings(DATConfigurator.java:204)
at com.cisco.cns.dat.DATConfigWrapper.main(DATConfigWrapper.java:60)

javax.naming.NamingException: [LDAP: error code 80 - internal error]; remaining name 'ou=config,ou=CNSApplications,ou=configengine,o=ica,c=se'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3049)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2951)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2758)
at com.sun.jndi.ldap.LdapCtx.c_bind(LdapCtx.java:383)
at com.sun.jndi.ldap.LdapCtx.c_bind(LdapCtx.java:340)
at com.sun.jndi.toolkit.ctx.ComponentContext.p_bind(ComponentContext.java:596)
at com.sun.jndi.toolkit.ctx.PartialCompositeContext.bind(PartialCompositeContext.java:183)
at com.sun.jndi.toolkit.ctx.PartialCompositeContext.bind(PartialCompositeContext.java:173)
at javax.naming.InitialContext.bind(InitialContext.java:400)
at com.cisco.cns.dat.DATConfigurator.loadConfigAppSettings(DATConfigurator.java:226)
at com.cisco.cns.dat.DATConfigWrapper.main(DATConfigWrapper.java:60)

'''Possible Cause''': The Solaris Server on which Cisco Configuration Engine is being is containing zones(containers).

'''Solution''': Cisco Configuration Engine is certified on a Solaris Server with Zone. Please install Cisco Configuration Engine only on non zoned Solaris Server's.

[[Category:Configuration Engine Troubleshooting]]
[[Category:Configuration Engine]]

Troubleshooting Cisco Configuration Engine Installation

2011-05-19T10:47:08Z

Hsivakum:

=='gethostbyaddr()' error==

'''Symptom:'''

Installation aborted with error message “Hostname value retrieval by system calls 'gethostbyaddr()' and command 'hostname' have different values returned. Please correct it also make sure 'ifconfig' is set in your PATH before installing Config Engine 3.5”

'''Solution: '''

To resolve this problem, follow these steps:

Step 1 Make sure the hostnames configured in /etc/hosts, /etc/sysconfig/network and/or DNS server are consistent with what’s returned by “hostname –s” command.

Step 2 Make sure the ifconfig command is in the $PATH environment variable

==Can’t reinstall CE==
'''Symptom:'''

If a install shell is accidentally closed, reinstall is not allowed.

'''Solution: '''

To resolve this problem, follow these steps:

Step 1 use ce_uninstall –force to uninstall any partially installed packages and rerun ce_install.sh again.

Note: If the user typed ^Z to suspend the install process in the background, they need to either resume the install process or kill the install process.

==Setup fails in start of httpd==
'''Symptom:'''

While setting up of Cisco Configuration Engine version 3.5.2 or lower on Red Hat Enterprise Linux Version 5,the setup fails with appliance-setup.log showing httpd start error as mentioned below.

Starting httpd: /usr/sbin/httpd: error while loading shared libraries: libpq.so.4: cannot open shared object file: No such file or directory

'''Solution: '''

The problem is due to missing Red Hat packages on the Red Hat Enterprise Linux.
To resolve this problem, follow these steps:

Step 1 Use ce_uninstall to uninstall all installed packages.

Step 2 Install the "postgresql-libs" and "mailcap" rpm for the Red Hat Enterprise Linux Distribution.

Step 3 Rerun the ce_install.sh again to install Cisco Configuration Engine.

Step 4 Launch a new root user Session and enter into a new bash shell.

Step 5 Execute the setup.sh command on the bash shell.

==Setup or Resetup of Cisco Configuration Engine fails ==
'''Symptom:'''

The setup/resetup fails with appliance-setup.log showing httpd failure and java not found errors as mentioned below.

/etc/rc.d/init.d/httpd start
Checking if the following ports have been cleared:8009 8005 Starting tomcat...Waiting for tomcat to initialize...
Starting httpd: FAILED
system failed: 256 exit_value = 1 signal_num = 0 dumped_core = 0

Deploying config web services ...
/opt/ConfigEngine/CSCOcnsie/bin/deploy.config.websvc [-wsdl]
./adminclient.sh: line 18: java: command not found

'''Solution: '''

The problem is due to non execution of a new bash shell to source the environment variables added by Cisco Configuration Engine.
To resolve this problem, follow these steps:

Step 1 Launch a new root user Session and enter into a new bash shell.

Step 2 Execute the setup.sh command on the new bash shell created.

Troubleshooting Logging and Connection Issues

2011-05-18T09:50:00Z

Hsivakum: /* System Login Problem */

To troubleshoot logging and connection issues, see the following sections:
==System Login Problem==
'''Problem''': You cannot log in to the system.

'''Possible Cause''': This problem can occur for one of the following reasons:
* The Cisco Configuration Engine is installed on a Solaris Server containing zones.
* LDAP is corrupted
* You did not run the Setup program to create the initial system configuration
* You lost all of the user account passwords

'''Solution''': To resolve this problem, follow these steps:

# Cisco Configuration Engine is not supported on a Solaris Server containing zones, Please install Cisco Configuration Engine on a Solaris platform without zones.
# If you did not run the Setup program, run the Setup program as described in the Cisco Configuration Engine Solaris Installation and Configuration Guide 3.5.
# If you do not know the passwords for the system user accounts, reconfigure the system to create a new user account.
# For corrupted LDAP issue, if you receive the following error messages:
<pre>
Server encountered the following error:

javax.naming.CommunicationException: 127.0.0.1:389 [Root exception is \
java.net.ConnectException: Connection refused]
at com.sun.jndi.ldap.Connection.<init>(Connection.java:207)
at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:118)
at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2616)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:287)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)</pre>

Restart the database by providing the following commands:

'''$CISCO_CE_HOME/bin/ce_shutdown -all'''
'''export'''
'''LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$CISCO_CE_INSTALL_ROOT/bdb/lib:$CISCO_CE_INSTALL_RO OT/unixodbc/lib'''
'''$CISCO_CE_INSTALL_ROOT/bdb/bin/db_recover -h'''
'''$CISCO_CE_INSTALL_ROOT/openldap/var/openldap-data'''
'''$CISCO_CE_HOME/bin/ce_startup -all'''

If you still cannot log in to the system, contact the Cisco Technical Assistance Center (TAC) for assistance.

==System Cannot Connect to the Network==

'''Problem''': The system cannot connect to the network.

'''Possible Cause''': This problem can occur for the following reasons:

* The network cable is not connected to an Ethernet port
* The Ethernet interface is disabled or misconfigured
* The system is configured correctly, but the network is down or misconfigured
* The system is not configured correctly

'''Solution''': To resolve this problem, follow these steps:

1. Verify that the network cable is connected to an Ethernet port and the link light is on. If the network cable is not connected, connect it. If the network cable is connected but the Link light is not on, check for these probable causes:

* The network cable is faulty.
* The network cable is the wrong type (for example, a crossover
type is used, instead of the required straight-through type)
* The port on the default gateway to which the system
connects is down

2. If you still cannot connect to the network, use the ping command to perform the following tests:
* Try to connect to a well-known host on the network.
A Domain Name System (DNS)server is a good target host
* If the ping command can reach the well-known host,
the system is connected to the network. If it cannot connect
to the host, the problem is with the network configuration
or the host. Contact your network administrator for assistance
* If the ping command cannot reach the well-known host, try to
reach another host on the same subnet as the system
* If the ping command can reach a host on the same subnet,
but cannot reach a host on a different subnet, the
default gateway is probably down or misconfigured

3. If the ping command cannot reach any hosts, use the '''ifconfig''' command to determine whether the Ethernet interface is disabled or misconfigured. If the Ethernet interface is disabled, enable it. If it is misconfigured, configure it correctly.

4. If the interface is enabled and correctly configured but you still cannot connect to the network, ensure that all the network settings are configured correctly. Run the Set up program again by entering the set up command in the shell prompt.

'''Note:''' You cannot run the Set up program a second time by logging in as setup. For security reasons, the account is disabled after it is used once successfully.

5. Contact your network administrator to verify that there are no conditions on the network that prevent the system from connecting to the network.

6. If no conditions are preventing the system from connecting to the network, contact the Cisco TAC for assistance.

==Cannot Connect to the System Using a Web Browser==

'''Problem''': You cannot connect to the system by entering its IP address in a web browser.

'''Possible Cause''': This problem can occur for the following reasons:

* The system cannot connect to the network.
* Encryption is enabled (plain text is disabled).
* The HTTP service is not running.

'''Solution''': To resolve this problem, follow these steps:

1. Make sure that the system can connect to the network. If it cannot connect to the network, see the “[[System Cannot Connect to the Network]]” section for possible resolution.

2. Try to connect to the system by using a web browser.

If encryption is enabled:
* Use '''https://…''' to connect
* Verify that the certificate is correct

3. If you still cannot connect, stop and start the web server by entering the following commands:

'''$CISCO_CE_HOME/bin/ce_shutdown'''
'''$CISCO_CE_HOME/bin/ce_startup'''

If the LDAP directory contains thousands of devices, restart and wait for 20 minutes.

4. Repeat Step 2.

5. If you cannot connect, restart the system. If the LDAP directory contains thousands of devices, restart and wait for 20 minutes.

6. If you still cannot connect to the system, contact the Cisco TAC for assistance.

==Problems Connecting to the System with Secure Shell==

'''Problem''': When connecting to the system using Secure Shell (SSH), you can experience one of these problems:

* You cannot connect to the system
* The system is extremely slow, even though it is connected to the network
* The system cannot correctly process requests from management applications

'''Possible Cause''': The system cannot obtain the DNS services from the network.

'''Solution''': To resolve this problem, follow these steps. Connect to the console if you cannot connect by using SSH.

1. Do one of the following:

* Set up the name servers properly by editing the ''/etc/resolv.conf'' file
* Re-execute Setu.
2. Verify that the system can obtain the DNS services from the network by entering the following command:

'''host <dns-name>''' where <dns-name> is the DNS name of a host on the network that is registered in DNS. When you enter this command, it responds with the IP address of the host. If the system cannot resolve the DNS names to IP addresses, the DNS server is not working properly.

3. Resolve the network DNS problem.

4. If the system can resolve the DNS names to IP addresses but you still cannot connect to the system using SSH, contact the Cisco TAC for assistance.

==Cannot Connect to the System Using Telnet==

'''Problem''': You cannot connect to the system by using Telnet even though the system is connected to the network.

'''Possible Cause''': This problem could occur if the Telnet service is disabled on the system.

'''Solution''': To resolve this problem, use SSH to connect to the system.

[[Category:Configuration Engine Troubleshooting]]
[[Category:Configuration Engine]]