Cisco Cisco Prime Network 3.8 Troubleshooting Guide

Contributed by Tom Maneri, Cisco TAC Engineer.
May 28, 2015

This document describes the internal design and operational flow of the Prime Network monitoring graphs.

You can access the monitoring graphs from 

https://<ip>:1311/graphs

 where '<ip>' is the hostname

or IP address of your prime network gateway.  For example, 

https://10.1.1.2:1311/graphs

.

The login user is admin and the password is the root GUI password.

The update.pl script gathers the individual performance data for each Autonomous Virtual Machine (AVM)
into temporary hidden files in /tmp at 20−second intervals. These files are readable and provide the memory,
cpu, log lines, and so on for each of the AVMs. They are the values from the AVM at the time when the file
was created.

The script then copies these files to the gateway server. They place this data into the
~/.RemoteCommands/units/<IP>/graphs/<date/time>_graph_counters files on the gateway.

After the copy to the gateway, the unit deletes the files from /tmp.

The copy from the unit to the gateway is executed on the unit like this:
~/local/scripts/remote_copy.cmd $local_file $gateway_ip:$remote_file

The update.pl script processes the files that are generated by the gateway AVMs. The update_remote.pl script
processes the files generated by the unit servers. These scripts read the files under .RemoteCommands once
every minute. These files represent a single polling of unit data.

The script updates the *.rdd files in the ~/Main/scripts/monitoring/data directory. There is one file for each
AVM in the system (ip_avm#.rdd). This .rdd file is a sliding window that contains one month of data from the
.RemoteCommands files. It is compressed and not human−readable.

These two scripts also read all of the existing .rdd files in the data directory and create every possible