|
| 1 | +# SEL (rf_sel.py) |
| 2 | + |
| 3 | +Copyright 2019-2025 DMTF. All rights reserved. |
| 4 | + |
| 5 | +## About |
| 6 | + |
| 7 | +A tool to manage the SEL on a Redfish service. |
| 8 | + |
| 9 | +## Usage |
| 10 | + |
| 11 | +``` |
| 12 | +usage: rf_sel.py [-h] --user USER --password PASSWORD --rhost RHOST |
| 13 | + [--details] [--clear] [--debug] |
| 14 | +
|
| 15 | +A tool to manage the SEL on a Redfish service |
| 16 | +
|
| 17 | +required arguments: |
| 18 | + --user USER, -u USER The user name for authentication |
| 19 | + --password PASSWORD, -p PASSWORD |
| 20 | + The password for authentication |
| 21 | + --rhost RHOST, -r RHOST |
| 22 | + The address of the Redfish service (with scheme) |
| 23 | +
|
| 24 | +optional arguments: |
| 25 | + -h, --help show this help message and exit |
| 26 | + --details, -details Indicates details to be shown for each log entry |
| 27 | + --clear, -clear Indicates if the log should be cleared |
| 28 | + --debug Creates debug file showing HTTP traces and exceptions |
| 29 | +``` |
| 30 | + |
| 31 | +The tool will log into the service specified by the *rhost* argument using the credentials provided by the *user* and *password* arguments. |
| 32 | +It will then attempt to locate the SEL via the following logic: |
| 33 | + |
| 34 | +* It will iterate through each log service found in each manager and each system. |
| 35 | +* The first log service found where `LogEntryType` contains `SEL` is considered the SEL for the service. |
| 36 | + |
| 37 | +Once the SEL is found, the tool will either perform the `ClearLog` action if *clear* is provided, or read and display the log entries. |
| 38 | + |
| 39 | +Example: |
| 40 | + |
| 41 | +``` |
| 42 | +$ rf_sel.py -u root -p root -r https://192.168.1.100 |
| 43 | + Id | Timestamp | Message |
| 44 | + 1 | 2012-03-07T14:44:00Z | System May be Melting |
| 45 | +``` |
0 commit comments