Cisco Cisco Unified Provisioning Manager 8.5 Troubleshooting Guide

Page of 40
4
Troubleshooting Guide for Cisco Unified Provisioning Manager
OL-25681-01
Provisioning Manager Troubleshooting Tools
<
loglevel
> can be DETAIL, LOW, NORMAL, HIGH, or EMERGENCY.
Show Tech
ShowTech is a CLI tool that collects required troubleshooting information in a single compressed archive 
file. This tool is available in Provisioning Manager 2.0 and later versions, and is not backward 
compatible with Provisioning Manager 1.x versions. To execute ShowTech, you must specify a date 
range. Optionally, you can specify a target directory for the zip file output; otherwise, the default OS 
temp directory is used.
While collecting the troubleshooting data, and before writing to the output directory, the tool checks that 
a minimum of 100 MB of free disk space is available on the target drive. During data collection, if 100 
MB of free disk space is not available, the tool will abort (with an appropriate message) and clean up the 
drive thereby preventing the risk of consuming too much disk space. It is recommended that you refine 
the date range options to limit the data to be collected, and rerun the tool. 
You can categorize the troubleshooting data by component, you can explicitly collect any component by 
specifying a command line option. By default, all component data is collected.
You can collect following component data:
DEPLOYMENT—Collects deployment information.
Domain and Service Area configuration—Output is stored in Domain directory. 
AAA server configuration—Output is stored in AAA directory. 
Device Configuration—Output is stored in MediaServer and CiscoRouter directories.
Processor Configuration—Output is stored in CallProcessor, UMProcessor, and CUPProcessor 
directories.
All service actions and their network dialogs for the specified date range will be exported. 
Output is stored in ServiceAction directory.
LOGS—collects log files.
SEP and NICE logs—Output is stored in cupm-logs directory.
PostgreSQL logs—Output is stored in pgsql-logs directory.
JBoss logs—Output is stored in jboss-logs directory.
ORDER—Collects order information. 
Order XMLEntity export of all INITIAL|HOLD|RELEASED orders for the specified date range 
(located in Order directory).
For all collected orders, the corresponding ordering subscribers of the products, along with their 
customer records, are also exported as a XMLEntity. Output will be stored in the subscriber 
directory.
All service actions and their network details for the specified date range will be exported. 
Output will be stored in ServiceAction directory.
SA—Collects all Service Action data (both successful and failed). The ALL option collects failed 
Service Actions.
SYSTEM—Collects system information.
Provisioning Manager configuration—dfc.properties, ipt.properties, system runtime properties, 
and IM counts. Output will be stored in the cupm directory.