Cisco Cisco Prime Network 3.8 Troubleshooting Guide

Page of 1
AVM 100 FAQ: How do you change the logging
level for the EventCollector (AVM 100) to debug?
Document ID: 117697
Contributed by Tom Maneri and Eyal Tuzon, Cisco TAC Engineers.
May 20, 2014
Contents
Introduction
How do you change the logging level for the EventCollector, or Application Visibility and Management
(AVM) 100, to debug?
Introduction
This document describes how to change the logging level for the EventCollector (AVM 100) in order to
debug.
How do you change the logging level for the EventCollector,
or Application Visibility and Management (AVM) 100, to
debug?
This prints out the text of every trap and syslog received by Prime Network into the AVM 100 log file.
From the Prime Network user, enter this command:
runRegTool.sh −gs 127.0.0.1 set 0.0.0.0
site/trap/services/logger/log4j.category.com.sheer.metrocentral.framework.instrumentation.trap DEBUG
To revert it back, enter this command:
runRegTool.sh −gs 127.0.0.1 unset 0.0.0.0
site/trap/services/logger/log4j.category.com.sheer.metrocentral.framework.instrumentation.trap
If the EventCollector (AVM 100) runs on a unit server, then the AVM needs to be restarted. No restart is
necessary if the EventCollector is active on the gateway server.
Updated: May 20, 2014
Document ID: 117697