Configuring Settings for Faults, Events, and Logs
This chapter includes the following sections:
- Configuring the Syslog
- Fault Collection Policy
- Configuring the Fault Collection Policy
- Core File Exporter
- Configuring the Core File Exporter
- Disabling the Core File Exporter
Configuring Settings for the Fault Collection Policy
Fault Collection Policy
The fault collection policy controls the lifecycle of a fault in a Cisco UCS instance, including when faults are cleared, the flapping interval (the length of time between the fault being raised and the condition being cleared), and the retention interval (the length of time a fault is retained in the system).
A fault in Cisco UCS has the following lifecycle:
-
A condition occurs in the system and Cisco UCS Manager raises a fault. This is the active state.
-
When the fault is alleviated, it is cleared if the time between the fault being raised and the condition being cleared is greater than the flapping interval, otherwise, the fault remains raised but its status changes to soaking-clear. Flapping occurs when a fault is raised and cleared several times in rapid succession. During the flapping interval the fault retains its severity for the length of time specified in the fault collection policy.
-
If the condition reoccurs during the flapping interval, the fault remains raised and its status changes to flapping. If the condition does not reoccur during the flapping interval, the fault is cleared.
-
When a fault is cleared, it is deleted if the clear action is set to delete, or if the fault was previously acknowledged, otherwise, it is retained until either the retention interval expires, or if the fault is acknowledged.
-
If the condition reoccurs during the retention interval, the fault returns to the active state. If the condition does not reoccur, the fault is deleted.
Configuring the Fault Collection Policy
Configuring Settings for the Core File Exporter
Core File Exporter
Cisco UCS Manager uses the Core File Exporter to export core files as soon as they occur to a specified location on the network through TFTP. This functionality allows you to export the tar file with the contents of the core file.
Configuring the Core File Exporter
Step 1 | In the Navigation pane, click the Admin tab. | ||||||||||||||
Step 2 | On the Admin tab, expand . | ||||||||||||||
Step 3 | Click Settings. | ||||||||||||||
Step 4 |
In the Work pane, complete the following fields in the TFTP Core Exporter area:
|
||||||||||||||
Step 5 | Click Save Changes. |
Disabling the Core File Exporter
Step 1 | In the Navigation pane, click the Admin tab. |
Step 2 | On the Admin tab, expand . |
Step 3 | Click Settings. |
Step 4 | In the Work pane, click the Settings tab. |
Step 5 | In the TFTP Core Exporter area, click the disabled radio button in the Admin State field. |
Step 6 | Click Save Changes. |
Configuring the Syslog
Step 1 | In the Navigation pane, click the Admin tab. | ||||||||||||||||||||||||
Step 2 | On the Admin tab, expand . | ||||||||||||||||||||||||
Step 3 | Click Syslog. | ||||||||||||||||||||||||
Step 4 | In the Work pane, click the Syslog tab. | ||||||||||||||||||||||||
Step 5 |
In the Local Destinations area, complete the following fields:
|
||||||||||||||||||||||||
Step 6 |
In the Remote Destinations area, complete the following fields to configure up to three external logs that can store messages generated by the Cisco UCS components:
|
||||||||||||||||||||||||
Step 7 | Click Save Changes. |