Cisco Cisco Configuration Engine 3.5.3 Guía Para Resolver Problemas

Descargar
Página de 30
Troubleshooting Guide for Cisco Configuration Engine 3.5.3
Troubleshooting the Cisco CE Services
9
Troubleshooting Guide for Cisco Configuration Engine 3.5.3
OL-17767-03
Troubleshooting the Cisco CE Services
To troubleshoot Cisco Configuration Engine services, see the following sections:
Cisco CE Not Working Properly
Problem
The Cisco Configuration Engine is not working properly.
Possible Cause
This can occur if any of the processes fails.
Solution
Use the Cisco CE monitor feature to check the status of the processes. The CE monitor checks 
the status of a set of processes at a configured time interval and reports the status in the 
/var/log/CNSCE/ce_monitor/ce_monitor.log
 file. The CE monitor exits if any of the processes fails. 
To check the status of the processes, follow these steps:
Step 1
Check the status of CE monitor to determine whether the service is up or down:
For Linux, enter: 
/etc/rc.d/init.d/MonitorCE status
For Solaris, enter: 
/etc/init.d/MonitorCE
 
status
Step 2
Check the /var/log/CNSCE/ce_monitor/ce_monitor.log file to identify which process is down.
Step 3
If a particular process is down, check the process to determine the problem. 
No Response Received for the XML Request 
Problem
An XML request was sent, but you did not get a response.
Solution
To resolve this problem, do the following in any order:
To monitor events on the bus, use the cns-listen utility.
For Intelligent Modular Gateway (IMGW) devices, do the following:
Set the IMGW logging level to verbose.
Check the following log files under the /var/log/CNSCE/imgw directory:
IMGW-LOG-<hostname> (log file for the IMGW runtime)
IMGW-DEVMOD-LOG (log file for debugging the IMGW script)
For agent-enabled devices, configure cns debug on the router.