Brocade Mobility RFS Controller System Reference Guide (Supporting software release 5.5.0.0 and later) User Manual

Page 529

Advertising
background image

Brocade Mobility RFS Controller System Reference Guide

517

53-1003099-01

8

8. Refer to the Message Logging field to define how the profile logs system events. It’s important

to log individual events to discern an overall pattern that may be negatively impacting
performance using the configuration defined for this profile.

9. Refer to the System Event Messages section to define how system messages are logged and

forwarded on behalf of the profile.

10. Refer to the Events E-mail Notification section to define how system event notification emails

are sent.

Enable Message Logging

Select this option to enable the profile to log system events to a user defined log file or a syslog
server. Selecting this check box enables the rest of the parameters required to define the profile’s
logging configuration. This option is disabled by default.

Remote Logging Host

Use this table to define numerical (non DNS) IP addresses for up to three external resources where
logged system events can be sent on behalf of the profile. Select Clear as needed to remove an IP
address.

Facility to Send Log
Messages

Use the drop-down menu to specify the local server facility (if used) for the profile’s syslog event log
transfer.

Syslog Logging Level

Event severity coincides with the syslog logging level defined for the profile. Assign a numeric
identifier to log events based on criticality. Severity levels include 0 - Emergency, 1 - Alert, 2 -
Critical, 3 - Errors, 4 - Warning, 5 - Notice, 6 - Info and 7 - Debug. The default logging level is 4.

Console Logging Level

Event severity coincides with the syslog logging level defined for the profile. Assign a numeric
identifier to log events based on criticality. Severity levels include 0 - Emergency, 1 - Alert, 2 -
Critical, 3 - Errors, 4 - Warning, 5 - Notice, 6 - Info and 7 - Debug. The default logging level is 4.

Buffered Logging Level

Event severity coincides with the syslog logging level defined for the profile. Assign a numeric
identifier to log events based on criticality. Severity levels include 0 - Emergency, 1 - Alert, 2 -
Critical, 3 - Errors, 4 - Warning, 5 - Notice, 6 - Info and 7 - Debug. The default logging level is 4.

Time to Aggregate
Repeated Messages

Define the increment (or interval) system events are logged on behalf of this profile. The shorter the
interval, the sooner the event is logged. Either define an interval in Seconds
(0 - 60) or Minutes (0 -1). The default value is 0 seconds.

Forward Logs to Controller

Select the checkbox to define a log level for forwarding event logs. Log levels include Emergency,
Alert, Critical, Error, Warning, Notice, Info and Debug. The default logging level is Error.

Event System Policy

Select an Event System Policy from the drop-down menu. If an appropriate policy does not exist click
the Create button to make a new policy.

Enable System Events

Select this option to allow the profile to capture system events and append them to a log file. It’s
important to log individual events to discern an overall pattern that may be negatively impacting
system performance. This setting is enabled by default.

Enable System Event
Forwarding

Select the Enable System Event Forwarding box to enable the forwarding of system events to
another cluster member. This setting is enabled by default.

SMTP Server

Specify either the Hostname or IP Address of the outgoing SMTP server where notification emails
will be originated.

Port of SMTP

If a non-standard SMTP port is used on the outgoing SMTP server check this box and specify a port
between 1 and 65,535 for the outgoing SMTP server to use.

Advertising