Cisco Cisco Prime Network Registrar 8.1 Installation Guide
Cisco Prime Network Registrar IPAM 8.1.2 Logging Overview
•
9
log4j.appender.RollingFile.File=${INCX_HOME}/log/dnslistener.log
The logging level, INFO by default, can be modified via the following entry in this same
properties file:
properties file:
log4j.category.com.diamondip.ipcontrol.dnssyncmgr=INFO
log4j.category.com.diamondip.netcontrol=WARN
log4j.category.com.diamondip.ipcontrol=WARN
log4j.category.com.diamondip.netcontrol=WARN
log4j.category.com.diamondip.ipcontrol=WARN
File Manager – The File Manager does NOT use log4j, but is configured, including its logging
configuration via the $INCHOME/ftpd.conf file. The logging output destination is set by default
to $INCHOME/log/ftp.log. The logging output destination is specified via the
configuration via the $INCHOME/ftpd.conf file. The logging output destination is set by default
to $INCHOME/log/ftp.log. The logging output destination is specified via the
FtpServer.server.config.data=${INC_HOME} line
. This parameter is overloaded as it
also specifies other File Manager resource file locations; the File Manager will log output to an
ftp.log file within a log subdirectory of the specified path; hence the output to
$INCHOME/log/ftp.log.
ftp.log file within a log subdirectory of the specified path; hence the output to
$INCHOME/log/ftp.log.
The File Manager supports four logging levels, from coarsest to finest: Error (3), Warning (2),
Information (1), and Debug(0). The default setting is Information (1) but this can be changed by
editing the
Information (1), and Debug(0). The default setting is Information (1) but this can be changed by
editing the
FtpServer.server.config.log.level=0
line, shown set to Debug (=0).
Log Manager – The Log Manager was intended to provide a cross-service logging perspective
utilizing the log4j utility. The default logging output destination was
$INCHOME/log/logmanager.log as defined in the lm_log4jconfig.properites file, though
currently logging is disabled.
utilizing the log4j utility. The default logging output destination was
$INCHOME/log/logmanager.log as defined in the lm_log4jconfig.properites file, though
currently logging is disabled.
log4j.appender.RollingFile.File=${INCX_HOME}/log/logmanager.log
Agent and Messaging Services (Executive and Remote)
An agent runs on both the Executive as well as on each remote server. They communicate with
each other using Cisco Prime Network Registrar IPAM messaging services. For Cisco Prime
Network Registrar IPAM 2.2 installations, the Message Router service, utilizing swiftmq, is the
messaging service. For Cisco Prime Network Registrar IPAM 8.1.2 and for an Executive
communication with mixed 8.1.1 and 8.1.2 remotes, the ActiveMQ service provides messaging
services.
each other using Cisco Prime Network Registrar IPAM messaging services. For Cisco Prime
Network Registrar IPAM 2.2 installations, the Message Router service, utilizing swiftmq, is the
messaging service. For Cisco Prime Network Registrar IPAM 8.1.2 and for an Executive
communication with mixed 8.1.1 and 8.1.2 remotes, the ActiveMQ service provides messaging
services.
2.2 Agents – Configure version 2.2 agent logging in the $INCHOME/agent_log4j.properties
file, which defaults to $INCHOME/log/agent.log. The default logging output destination is
specified on the line:
file, which defaults to $INCHOME/log/agent.log. The default logging output destination is
specified on the line:
log4j.appender.RollingFile.File=${INCX_HOME}/log/agent.log
The categories of events and corresponding severities can be specified in this file:
log4j.category.com.diamondip.netcontrol=DEBUG
log4j.category.com.diamondip.ipcontrol=DEBUG
log4j.category.com.diamondip.netcontrol.task=DEBUG
log4j.category.com.diamondip.netcontrol.agent=DEBUG
log4j.category.com.diamondip.ipcontrol=DEBUG
log4j.category.com.diamondip.netcontrol.task=DEBUG
log4j.category.com.diamondip.netcontrol.agent=DEBUG