System log
The System Log subcategory is in the Active Onboard Administrator category. The System Log displays logged information of events within the Onboard Administrator.
Events are logged from the top of the list to the bottom, with the most recent logged event appearing at the top of the list. The system log can be scrolled utilizing the scroll bar on the right side of the log screen (if the log is larger than the display box). The log has a maximum capacity of 18.42 KB and automatically deletes the oldest logged event first (first in, first out).
To clear the list of all logged events in the system log, click the Clear button on the lower-right below the system log display.
Extended system log
You can also retain an extended system log with a maximum capacity of 300 KB. The extended system log can be saved to a USB device upon system reboot.
|
|
CAUTION: Extended system log data is not retained in the event of a power loss. |
Remote system logging
Remote system logging is a feature that can be used to send Onboard Administrator syslog messages to a remote server on the network for persistent storage. The syslog messages are sent from Onboard Administrator using the UDP protocol on a port that can be specified by the user. The default remote syslog port is 514.
Onboard Administrators Remote System Logging feature follows the guidelines in RFC3164.
In most Linux systems, remote system logging can be enabled by starting syslogd with the “-r” option. The remote syslog port must also be opened in the firewall. For more information, see the documentation for your particular distribution. Windows® operating systems do not have native support for remote system logging. Any application that listens on UDP port 514 or the specified syslog port can receive remote system log messages from the OA.
Once configured, Onboard Administrator remote system logging feature can be tested using the GUI Test button on the configuration page or using the CLI TEST SYSLOG command.
Possible events
- Enclosure Event 0×01: Enclosure Status Changed
- Enclosure Event 0×02: Enclosure UID Status Changed
- Enclosure Event 0×03: Enclosure Shutdown
- Enclosure Event 0×04: Enclosure Information Changed
- Enclosure Event 0×05: Enclosure Name Changed
- Enclosure Event 0×06: User Permissions Changed
- Enclosure Event 0×07: Administrator Rights Changed
- Enclosure Event 0×08: Enclosure Shutdown Pending
- Enclosure Event 0×09: Enclosure Topology Changed
- Enclosure Event 0×10: Fan Status Changed
- Enclosure Event 0×11: Fan Inserted
- Enclosure Event 0×12: Fan Removed
- Enclosure Event 0×14: Thermal Subsystem Redundancy Status Changed
- Enclosure Event 0×15: Fan at Max Percentage
- Enclosure Event 0×16: Add Fan to Bay
- Enclosure Event 0×17: Remove Fan from Bay
- Enclosure Event 0×18: Fan Over Consuming Power
- Enclosure Event 0×20: Thermal Status Changed
- Enclosure Event 0×30: Power Supply Status Changed
- Enclosure Event 0×31: Power Supply Inserted
- Enclosure Event 0×32: Power Supply Removed
- Enclosure Event 0×33: Power Supply Subsystem Redundant Status Changed
- Enclosure Event 0×34: Power Supply Subsystem Overloaded
- Enclosure Event 0×35: AC Failure
- Enclosure Event 0×36: Inadequate Power or Cooling
- Enclosure Event 0×40: Interconnect Device Status Changed
- Enclosure Event 0×41: Interconnect Device Reset
- Enclosure Event 0×42: Interconnect Device UID Status Changed
- Enclosure Event 0×43: Interconnect Device Inserted
- Enclosure Event 0×44: Interconnect Device Removed
- Enclosure Event 0×45: Interconnect Device Information Changed
- Enclosure Event 0×46: Interconnect Device Health LED Status Changed
- Enclosure Event 0×47: Interconnect Device Thermal Status Changed
- Enclosure Event 0×48: Interconnect Device CPU Fault
- Enclosure Event 0×49: Interconnect Device Power Mode Changed
- Enclosure Event 0×50: Enclosure Demonstration Mode
- Blade Event 0×100: Blade Device Status Changed
- Blade Event 0×101: Blade Device Inserted
- Blade Event 0×102: Blade Device Removed
- Blade Event 0×103: Blade Device Power State Changed
- Blade Event 0×104: Blade Device Power Management Changed
- Blade Event 0×105: Blade Device UID Status Changed
- Blade Event 0×106: Blade Device Shutdown
- Blade Event 0×107: Blade Device Fault
- Blade Event 0×108: Blade Device Thermal Status Change
- Blade Event 0×110: Blade Device Information Changed
- Blade Event 0×111: Blade Bay Management Processor Changed
- Blade Event 0×112: ILO Ready
- Blade Event 0×114: Keying Error
- Blade Event 0×115: ILO Has IP Address
- LCD Event 0×200: Display Changed
- LCD Event 0×201: Button Pressed
- LCD Event 0×202: Pin Information Changed
- LCD Event 0×203: User Note Information Changed
- LCD Event 0×204: Chat Requested
- LCD Event 0×205: Chat Response Sent
- LCD Event 0×206: LCD Display State Changed
- Enclosure Event 0×1001: Network Information Changed
- Enclosure Event 0×1002: SNMP Information Changed
- Enclosure Event 0×1003: System Log Cleared
- Enclosure Event 0×1004: Session Cleared
- Enclosure Event 0×1005: Time Changed
- Enclosure Event 0×1006: Session Started
- Enclosure Event 0×1007: Blade Connected
- Enclosure Event 0×1008: Blade Disconnected
- Enclosure Event 0×1009: Switch Connected
- Enclosure Event 0x100A: Switch Disconnected
- Enclosure Event 0x100B: Blade Cleared
- Enclosure Event 0x100C: Switch Cleared
- Enclosure Event 0x100D: AlertMail Information Changed
- Enclosure Event 0x100E: LDAP Information Changed
- Enclosure Event 0x100F: EBIPA Information Changed
- Enclosure Event 0×1013: User Information Changed
- Enclosure Event 0×1014: Bay Changed
- Enclosure Event 0×1016: Onboard Administrator Reboot
- Enclosure Event 0×1017: Onboard Administrator Logoff Request
- Enclosure Event 0×1018: User Added
- Enclosure Event 0×1019: User Deleted
- Enclosure Event 0×1020: User Enabled
- Enclosure Event 0×1021: User Disabled
- Enclosure Event 0×1201: Flash Pending
- Enclosure Event 0×1202: Flash Started
- Enclosure Event 0×1203: Flash Progress
- Enclosure Event 0×1204: Flash Complete
- Enclosure Event 0×1210: Non-iLo EBIPA