• WEM Server: Logging for the server component of the WEM is facilitated by the emslogger.xml file located in the /<ems_dir>/server/etc directory by default. This component consists of a number of categories (called loggers) as described in the following table.
• Bulk Statistics Parser: Logging for the Bulk Statistic Parser component of the WEM is facilitated by the bsparserlogger.xml file located in the /<ems_dir>/server/etc directory by default. This component is responsible for analyzing information collected by the Bulk Statistic Server.
• Bulk Statistics Server: Logging for the Bulk Statistic Server component of the WEM is facilitated by the bsserverlogger.xml file located in the /<ems_dir>/server/etc directory by default. This component is responsible for collecting bulk statistic information from the system.
• Script Server: Logging for the Script Server component of the WEM is facilitated by the scriptlogger.xml file located in the /<ems_dir>/server/etc directory by default. This component supports the ability to execute specific scripts upon the receipt of SNMP alarms.
• NorthBound Server: Logging for the NorthBound Server component of the WEM is facilitated by the nbserverlogger.xml file located in the /<ems_dir>/server/etc directory by default. This component is responsible for collecting NB server information from the system.Important: The NorthBound (NB) Server process is customer-specific and is not operational without the appropriate license. Please contact your local sales representative for additional information.
• Appender settings: Control log file parameters such as naming, output location, format, and sizing specifications.
• Logger settings: Control logging parameters for the specified category such as whether or not to use appender settings and the log level. As described previously, the WEM Server component consists of multiple loggers. There is a single logger for the other components.
• Root element: Contains references to other appenders that should be added to loggers contained in the XML configuration file. In addition, this element contains a parameter that dictates how often the system is to scan and incorporate changes made to the logger configuration. (Additional information on configuring the scan frequency is provided in the Configuring Support for Dynamic Logging Updates section of this chapter.)By default, each logging configuration file has a single Rolling File Appender configured called Main. Each logger within the file is configured to use this appender by default. (It is referenced in the root element in the configuration file.) Additional appenders can be added to the configuration file using a text editor (such as Vi Editor) if desired.<appender name="appender_name" class="AsyncAppender"><appender-ref ref="attached_appender"/>
<appender name="appender_name" class="ConsoleAppender"><param name="Target" value="output"/><layout class="layout_class"><param name="ConversionPattern" value="conv_pattern"/>
Specifies the format of the log file output. Refer to the Log File Output Formats section of this chapter for information on supported output formats. Specifies the conversion pattern used to format event related information. Refer to the Pattern Layout Supported Conversion Characters table for a list of supported conversion characters.<appender name="appender_name" class="FileAppender"><param name="File" value="file_name"/>
• true : Append the information; this is the default setting.
• false : Do not append the information. Specifies the format of the log file output. Refer to Log File Output Formats section of this chapter for information on supported output formats. Specifies the conversion pattern used to format event related information. Refer to the Pattern Layout Supported Conversion Characters table for a list of supported conversion characters.<appender name="appender_name" class="RollingFileAppender"><param name="File" value="file_name"/><param name="Append" value="append_option"/><param name="MaxBackupIndex" value="max_backups"/><layout class="layout_class"><param name="ConversionPattern" value="conv_pattern"/>
• true : Append the information; this is the default setting.
• false : Do not append the information. Specifies the format of the log file output. Refer to the Log File Output Formats section of this chapter for information on supported output formats. Specifies the conversion pattern used to format event related information. Refer to the Pattern Layout Supported Conversion Characters table for a list of supported conversion characters.<appender name="appender_name" class="DailyRollingFileAppender"><param name="File" value="file_name"/><param name="Append" value="append_option"/><param name="DatePattern" value="date_format"/>
• true : Append the information; this is the default setting.
• false : Do not append the information. Specifies the format of the log file output. Refer to the Log File Output Formats section of this chapter for information on supported output formats. Specifies the conversion pattern used to format event related information. Refer to the Pattern Layout Supported Conversion Characters table for a list of supported conversion characters.For example, if the File parameter is set to abc.log and the DatePattern parameter is set to .%Y-%m-%d, on 2001-02-16 at midnight, the logging file abc.log is copied to abc.log.2001-02-16 and logging for 2001-02-17 will continue in abc.log until it rolls over the next day.
• <appender name="appender_name" class="SocketAppender"><param name="Port" value="port_no"/>
<appender name="appender_name" class="TelnetAppender"><param name="Port" value="port_no"/>
<appender name="appender_name" class="SMTPAppender"><param name="BufferSize" value="size" /><param name="SMTPHost" value="smtp_host"/><param name="From" value="sender"/><param name="To" value="recipient"/><param name="Subject" value="subject"/><layout class="layout_class"><param name="ConversionPattern" value="conv_pattern"/>
Specifies the format of the log file output. Refer to the Log File Output Formats section of this chapter for information on supported output formats. Specifies the conversion pattern used to format event related information. Refer to the Pattern Layout Supported Conversion Characters table for a list of supported conversion characters.
• Time: Event time
• Thread: Event thread
• Level: Event severity Level
• Category (Module): The enhanced logging function category that generated the event
• Message: Event descriptionCaution: Do not use the same TTCC Layout instance from within different appenders. The TTCC Layout may not handle event threads properly when used in this way.
<param name="DatePattern" value="date_format"/>
<param name="ConversionPattern" value="pattern"/>pattern specifies the conversion characters used to format the output. The following table provides information on supported conversion characters.
• ABSOLUTE : AbsoluteTimeDateFormat
• DATE : DateTimeDateFormat
• ISO8601 : ISO8601DateFormat <level value="severity"/><appender-ref ref="appender_name"/>
• true : Use appender defined within root (default)
• false : Do not use appender defined within root
•
•
•
•
• <param name="LevelToMatch" value="severity" /><param name="AcceptOnMatch" value="accept_option"/>
•
•
•
•
•
•
• true : Logs matching the severity are accepted
• false : Logs matching the severity are not accepted<param name="LevelMax" value="max_sev"/><param name="LevelMin" value="min_sev"/><param name="AcceptOnMatch" value="accept_option"/>
•
•
•
•
•
•
•
•
•
•
•
•
• true : Logs matching the criteria are accepted
• false : Logs not matching the criteria are not accepted<param name="StringToMatch" value="string" /><param name="AcceptOnMatch" value="accept_option"/>
• true : Logs matching the criteria are accepted
• false : Logs not matching the criteria are not accepted
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |