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

Page 232

Advertising
background image

220

Brocade Mobility RFS Controller System Reference Guide

53-1003099-01

5

Use the drop-down menu to select an existing management policy to apply to this profile. If no
management policies exist meeting the data access requirements of this profile, select the
Create icon to access screens used to define administration, access control and SNMP
configurations. Select an existing policy and select the Edit icon to modify the configuration of
an existing management policy. For more information, see

Viewing Management Access

Policies

.

6. 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 potentially impacting performance.

7. Refer to the System Event Messages section to define or override how controller or service

platform system messages are logged and forwarded on behalf of the profile.

Enable Message Logging

Select this option to enable the profile to log system events to a 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 (if used) for profile event log transfers.

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 the 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 check box 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,
select the Create button to make a new policy.

Enable System Events

Select the Enable System Events check box 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 controller or service platform performance. This setting is enabled by
default.

Enable System Event
Forwarding

Select the Enable System Event Forwarding radio button to forward system events to another
controller, service platform or cluster member. This setting is enabled by default.

Advertising