Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 04-HH3C-INFOCENTER-MIB | 43.54 KB |
Contents
HH3C-INFOCENTER-MIB
About this MIB
Use this MIB to configure information center settings, including enabling the information center or configuring log buffers and log hosts. You can access this MIB to obtain information about log entries in the log buffer.
MIB file name
hh3c-infocenter.mib
Notifications
hh3cICLogWriteFail
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.119.5.3.0.1 |
Failed to write buffered logs to the log file. |
Error |
Major |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when the device fails to write logs in the buffer to the log file.
System impact
The latest log cannot be saved to the log file.
Status control
This notification cannot be disabled.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
1.3.6.1.4.1.25506.2.119.5.4.1 (hh3cICLogType) |
Log type. |
N/A |
INTEGER |
Standard MIB values. |
|
1.3.6.1.4.1.25506.2.119.5.4.2 (hh3cICFailReason) |
Reason for write failure. |
N/A |
DisplayString |
Standard MIB values. |
Recommended action
Troubleshoot according to the failure reason carried in the trap. For example:
1.Execute the dir command in user view to display the current available space of the storage medium. If the storage space is not enough, use the delete /unreserved command to delete unused files permanently to release storage space.
2.If the storage medium becomes read-only due to a malfunction, please back up the files in the storage medium first, and then try to repair it using the fixdisk command.
3.If the write protection function is enabled, new logs cannot be written to the log file after the file is written to full capacity. At this time, you can disable write protection by using the undo info-center logfile overwrite-protection command.
4.If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.
hh3cICLogFileAging
Basic information
|
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
|
1.3.6.1.4.1.25506.2.119.5.3.0.2 |
Deleted the oldest compressed log file. |
Informational |
Warning |
N/A (N/A) |
ON |
Notification triggers
This notification is generated when the device deletes the oldest compressed log file after all log files are full, and generates a new log file to save new logs. This notification is available for devices that support multiple log files.
System impact
The logs in the deleted log file are lost if the log file has no backup.
Status control
This notification cannot be disabled.
Object
|
OID (object name) |
Description |
Index |
Type |
Value range |
|
(1.3.6.1.4.1.25506.2.119.5.4.3 hh3cICLogFileName) |
Name of the deleted log file. |
N/A |
DisplayString |
Standard MIB values. |
Recommended action
1.As a best practice, back up the log files generated by the system periodically.
2.Execute the display logfile summary command and then identify the maximum storage space reserved for a single log file (the value of the Log file size quota field). To change the file size to a proper value, use the info-center logfile size-quota command.
