The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The following topics provide procedures that you can use to test your report and resolve common issues and errors:
Step 1 Save your report and its associated.properties file in the / opt/CSCOppm-gw/etc/pollers/user directory.
Step 2 In the Prime Performance Manager GUI, select Reports and then click the Reports Status tab.
Step 3 Scroll down the list of reports and locate your report.
Step 4 Check the interval(s) for which you want to enable your report then click the Save icon.
The report should now be active.
Step 5 Navigate to the report category associated with your report, then click your report.
Step 6 Note any error messages that appear.
Step 7 If you have set up cross-launch of Cisco Prime Performance Management reports:
a. Log into Cisco Prime Network Vision.
c. Locate the device or network location where your cross-launch is set up.
d. Right click on the cross-launch point.
e. Verify that the NetworkVision Device Shortcut has a Performance select; for example, Performance > Device Reports.
f. Click Device Reports and verify that a Cisco Prime Performance Manager report comes up.
g. Verify that any reports you set up to cross-launch from Prime Network are available and work correctly.
This section lists common issues and error messages that can occur when running reports and provides information on how to resolve the problems.
Step 1 From the System menu, choose Messages.
Step 2 To view only error messages, click Error.
Step 3 To see a console log, under the System menu, choose Logs, then choose Console Log.
If your report uses an incorrect MIB variable, an error message will appear. The incorrect MIB variable will appear in the sgmConsoleLog.txt or messageLog.txt file. These log files can also be viewed from the System->Logs and System->Messages menus.
Check the MIB and check the XML code in your report to make sure that the variable is referenced correctly.