Appendix A: Configuration
Netcool/Proviso Cisco IP Telephony Technology Pack User’s Guide, Version 4.3-W 451
kill -9 <amgrw_pid>
kill -9 <cmgrw_pid>
14-f. Use the following commands to restart each DataChannel visual process:
cnsw
logw
amgrw
cmgrw
14-g.Use the dccmd command to start all DataChannel applications:
dccmd -action start all
14-h.Use the dccmd command to verify that all of the DataChannel applications started properly:
dccmd -action status all
More specifically, make sure that the UBA application associated with the DataChannel you configured
for the Cisco IP Telephony Technology Pack is running.
14-i. Watch the output of the status switch to verify that all the necessary processes are running. If these
processes are running, run the tail utility on the log file for the UBA by issuing a command similar
to the following:
tail -f DATA_CHANNEL_HOME/log/proviso.log | grep UBA.<channel>.<collector>- | more
where:
The following table identifies some events to watch for during the syntax check:
Variable Meaning
DATA_CHANNEL_HOME Is /opt/datachannel, by default.
<channel> Specifies the channel number (for example, 1) you
specified when configuring this DataChannel.
<collector> Specifies the collector number (for example, 100) you
specified when configuring this UBA Bulk Collector.
The trailing dash (–) after <collector> Removes extraneo us log messages from your view. That is,
the trailing dash guarantees that the command displays
only those messages generated by your application. The
first set of messages relate to syntax checks.
Event Meaning
The UBA application starts successfully, but then stops
executing. Typically, this event occurs because of a licensing issue.
The Bulk Adaptor Design File might be corrupt. This event causes a syntax error before the UBA
application connects to the database.