Cisco Cisco Prime Network Registrar 8.2 發佈版本通知

Cisco Prime Network Registrar 8.2.1 now supports logging to a Syslog server (on Linux and Solaris). 
The Syslog support is not enabled by default. To configure which messages need to be logged, based on 
logging levels, the cnr.conf file must be updated.

In addition, on Windows, event logging for Warnings and Errors is enabled by default (for Windows 
Event log). In this release, you can log more (or less) to the event log by changing the log settings.

In Cisco Prime Network Registrar 8.2.1, the following cnr.conf configuration parameters are now 
supported: 

cnr.syslog.enable—Specifies whether logging to Syslog server or Windows Event log is enabled for 
Prime Network Registrar servers. 

To disable all logging, the value can be 0, off, or disabled. 

To enable all logging, the value can be 1, on, or enabled. 

By default, this parameter is disabled for Linux or Solaris and enabled for Windows.

cnr.syslog.levels—Specifies the severity levels to be logged to Syslog or Windows Event log. If 
Syslog is enabled, this defaults to warning and error. The value can be a case-blind, comma 
separated, list of the following keywords: error, warning, info, activity, and debug. This parameter 
is ignored if Syslog is disabled.

While it is possible to enable all of the severity levels and thus all messages written to the 
server log files are also logged to Syslog, this is not recommended unless the server log 
settings are reviewed and minimized. The performance impact on Syslog and the servers 
may vary greatly depending on how logging is configured. Syslog may rate limit the 
messages, so useful messages may also be lost.

cnr.syslog.facility—Specifies the facility under which Syslog logs (Linux or Solaris OS). This 
parameter is ignored for Windows. The valid facility keywords are daemon (the default), local0, 
local1, local2, local3, local4, local5, local6, local7.

These parameters apply to all Cisco Prime Network Registrar servers (cnrservagt, ccm, cdns, 
cnrsnmp, dns, dhcp, and tftp). 

To apply any change to the cnr.conf parameters, Cisco Prime Network Registrar must be restarted.

The following cnr.conf configuration parameters allow server-specific overrides of the above 
parameters. server is one of cnrservagt, ccm, cdns, cnrsnmp, dns, dhcp, and tftp.

cnr.syslog.server.enable—Specifies whether Syslog or Windows Event logging is enabled for the 
specified server (cnr.syslog.enable is ignored for that server).

cnr.syslog.server.levels—Specifies the severity levels for the specified server (cnr.syslog.levels is 
ignored for that server).

cnr.syslog.server.facility—Specifies the Syslog facility for the specified server (cnr.syslog.facility 
is ignored for that server).

The server specific configuration value is used, if specified. Otherwise, all parameters of the server are 
used. For example, to enable Syslog only for DHCP, add the following to the cnr.conf file:

cnr.syslog.dhcp.enable=1