The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter includes the following sections:
The system event log (SEL) resides on the CIMC in NVRAM. It records most server-related events, such as over and under voltage, temperature events, fan events, and events from BIOS. The SEL is mainly used for troubleshooting purposes.
The SEL file is approximately 40KB in size, and no further events can be recorded when it is full. It must be cleared before additional events can be recorded.
You can use the SEL policy to backup the SEL to a remote server, and optionally clear the SEL after a backup operation occurs. Backup operations can be triggered based on specific actions, or they can occur at regular intervals. You can also manually backup or clear the SEL.
The backup file is automatically generated. The filename format is sel-SystemName-ChassisID-ServerID-ServerSerialNumber-Timestamp; for example, sel-UCS-A-ch01-serv01-QCI12522939-20091121160736.
1. UCS-A# scope server chassis-id/cartridge-id/server-id
2. UCS-A /chassis/cartridge/server # show sel
Command or Action | Purpose |
---|
The following example displays the system event log from server 2 in cartridge 1 and chassis 1.
UCS-A# scope server 1/1/2 UCS-A /chassis/cartridge/server # show sel 1 | 01/01/1970 01:23:27 | System Event 0x83 | Timestamp clock synch | SEL timestamp clock updated, event is f irst of pair | Asserted 2 | 01/01/1970 01:23:28 | Drive slot(Bay) SAS0_LINK_STATUS | Transition to Degraded | Asserted 3 | 01/01/1970 01:23:28 | Drive slot(Bay) SAS0_LINK_STATUS | Transition to On Line | Deasserted 4 | 01/01/1970 01:23:28 | Platform alert LED_SAS0_FAULT | LED is blinking fast | Asserted 5 | 01/01/1970 01:23:28 | Platform alert LED_SAS0_FAULT | LED is on | Deasserted 6 | 01/01/1970 01:23:28 | Platform alert LED_FPID | LED is on | Asserted 7 | 01/01/1970 01:23:28 | Platform alert LED_FPID | LED is off | Deasserted 8 | 01/01/1970 01:23:29 | Entity presence MAIN_POWER | Device Absent | Asserted 9 | 01/01/1970 01:23:29 | Entity presence MAIN_POWER | Device Present | Deasserted a | 01/01/1970 01:23:29 | Platform alert LED_SAS0_FAULT | LED is on | Asserted b | 01/01/1970 01:23:29 | Platform alert LED_SAS0_FAULT | LED color is green | Asserted c | 01/01/1970 01:23:29 | Platform alert LED_SAS0_FAULT | LED is blinking fast | Deasserted d | 01/01/1970 01:23:29 | Platform alert LED_SAS0_FAULT | LED color is amber | Deasserted e | 01/01/1970 00:00:22 | Drive slot(Bay) SAS0_LINK_STATUS | Transition to Degraded | Asserted f | 01/01/1970 00:00:22 | Entity presence MEZZ_PRS | Device Present | Asserted 10 | 01/01/1970 00:00:22 | Entity presence HDD1_PRS | Device Absent | Asserted
1. UCS-A# scope org org-name
2. UCS-A /org # scope ep-log-policy sel
3. (Optional) UCS-A /org/ep-log-policy # set description description
4. UCS-A /org/ep-log-policy # set backup action [log-full] [on-change-of-association] [on-clear] [timer] [none]
5. UCS-A /org/ep-log-policy # set backup clear-on-backup {no | yes}
6. UCS-A /org/ep-log-policy # set backup destination URL
7. UCS-A /org/ep-log-policy # set backup format {ascii | binary}
8. UCS-A /org/ep-log-policy # set backup hostname {hostname | ip-addr}
9. UCS-A /org/ep-log-policy # set backup interval {1-hour | 2-hours | 4-hours | 8-hours | 24-hours | never}
10. UCS-A /org/ep-log-policy # set backup password password
11. UCS-A /org/ep-log-policy # set backup protocol {ftp | scp | sftp | tftp}
12. UCS-A /org/ep-log-policy # set backup remote-path path
13. UCS-A /org/ep-log-policy # set backup user username
14. UCS-A /org/ep-log-policy # commit-buffer
The following example configures the SEL policy to back up the system event log (in ascii format) every 24 hours or when the log is full and clear the system event log after a backup operation occurs and commits the transaction:
UCS-A# scope org / UCS-A /org # scope ep-log-policy sel UCS-A /org/ep-log-policy # set backup destination scp://user@192.168.1.10/logs Password: UCS-A /org/ep-log-policy* # set backup action log-full UCS-A /org/ep-log-policy* # set backup clear-on-backup yes UCS-A /org/ep-log-policy* # set backup format ascii UCS-A /org/ep-log-policy* # set backup interval 24-hours UCS-A /org/ep-log-policy* # commit-buffer UCS-A /org/ep-log-policy #
Configure the system event log policy. The manual backup operation uses the remote destination configured in the system event log policy.
1. UCS-A# scope server chassis-id/cartridge-id/server-id
2. UCS-A /chassis/cartridge/server # backup sel
3. UCS-A /chassis/cartridge/server # commit-buffer
Command or Action | Purpose |
---|
The following example backs up the system event log for server 2 in cartridge 1 and chassis 1 and commits the transaction.
UCS-A# scope server 1/1/2 UCS-A /chassis/cartridge/server # backup sel UCS-A /chassis/cartridge/server* # commit-buffer UCS-A /chassis/cartridge/server #
1. UCS-A# scope server chassis-id/cartridge-id/server-id
2. UCS-A /chassis/cartridge/server # clear sel
3. UCS-A /chassis/cartridge/server # commit-buffer
Command or Action | Purpose |
---|
The following example clears the system event log from server 2 in cartridge 1 and chassis 1 and commits the transaction:
UCS-A# scope server 1/1/2 UCS-A /chassis/cartridge/server # clear sel UCS-A /chassis/cartridge/server* # commit-buffer UCS-A /chassis/cartridge/server #