Two additional log files are used by the DPE when PacketCable is enabled on the DPE server: RegSvr.logxxx.log and SNMPService.logyyy.log. You use the show packetcable registration log and show packetcable snmp log DPE CLI commands to view these files, which are also located in the BPR_DATA/dpe/logs directory. See the "PacketCable (Voice Technology) Commands" section, for command usage.
The log file structure, is describe here and illustrated in Example A-1. The log file includes this information:
Domain Name—This is the name of the computer generating the log files.
Date and Time—This is the date on which a message is logged. This information also identifies the applicable time zone.
Facility—This identifies the system which, in this case is the BAC.
SubFacility—This identifies the BAC subsystem or component.
Severity Number—The logging system defines seven levels of severity (log levels) that are used to identify the urgency with which you might want to address log issues. The process of configuring log levels is described in the "Configuring Log Levels" section:
0—Emergency; System unstable.
1—Alert; Immediate action is needed.
2—Critical; A critical condition exists.
3—Error; Error conditions exist.
4—Warning; Warning condition exists.
5—Notification; A normal, but significant, condition exists.
6—Information; Informational messages only.
Note Another level known as DEBUG is used exclusively by Cisco for debugging purposes. Do
not use this level except at the direction of the Cisco TAC.
Message ID—This is a unique identifier for the message text.
Message—This is the actual log message.
Configuring Log Levels
You can configure logging levels for both the RDU and the DPE to suit your specific requirements. For example, the logging level for the RDU could be set to Warning and the level for the DPE could be set to Alert.
Log messages are written based on certain events taking place. Whenever an event takes place, the appropriate log message and level are assigned and, if that level is less than or equal to the configured level the message is written to the log. The message is not written to the log if the level is higher than the configured value.
For example, assume that the log level is set to 4-Warning. All events generating messages with a log level of 4 or less are written into the log file. If the log level is set to 6-Information, the log file will receive all messages. Consequently, configuring a higher log level results in a larger log file size.